Making the switch permanent

Making the switch permanent (DDM)

About this task

In the procedure Switching the manager to the upgraded backup, you switched your manager promoting your new version backup manager to the role of manager.

To make this configuration fully operational and persistent through JnextPlan, complete the following procedure on the new manager, referred to as new_mgr_cpu:
  1. Edit the localopts file and modify the following entry as shown: 
    DEFAULTWS=new_mgr_cpu
    where new_mgr_cpu is the workstation name of the new manager. For more information about localopts file, see Setting local options.
  2. Change the workstation definition of the back-level master by running: 
    composer modify cpu=old_mgr_cpu
    and in the definition substitute type=manager with type=fta
  3. Change the workstation definition of the new manager by running: 
    composer modify cpu=new_mgr_cpu
    and in the definition substitute type=fta with type=manager.
  4. Ensure that the optman cf option is set to all.
  5. Rebuild the plan to activate the changes to the database: 
    JnextPlan -for 0000
  6. Switch the event processor to the new manager by running the following command:
    switcheventprocessor new_mgr_cpu
  7. Restore the previous setting of the optman cf option, if necessary.
  8. Edit the /TWS/mozart/globalopts file and modify the master=old_mgr_cpu entry as shown: 
    master=new_mgr_cpu
    where new_mgr_cpu is the workstation name of the new master. For more information about optman, see Setting global options.

    In this way the reports reptr-pre and reptr-post can run when you run JnextPlan.

  9. Run the FINAL job stream on the new manager.

Results

You have now successfully made the switch permanent.

What to do next

You have now to import to the new dynamic domain manager the security file from the previous dynamic domain manager, as follows:
  1. On the previous dynamic domain manager launch the following command to export the security file:
    dumpsec > <file_name>.txt
  2. Copy the <file_name>.txt file to the new dynamic domain manager.
  3. On the new dynamic domain manager, launch the following command to compile and install the security file:
    makesec <file_name>.txt

For more information about the dumpsec and makesec commands, see Updating the security file.

You can now proceed to Upgrading the database schema for the server components.