Upgrading your dynamic domain manager in SSL mode

About this task

If your environment is at Version 9.5 Fix Pack 4 or later, and you want to upgrade to Version 10.1 Fix Pack 3 or later enabling SSL at the same time, perform the steps listed below to upgrade your dynamic domain manager.

If your environment is at a version earlier than Version 9.5 Fix Pack 4, you need to upgrade first to Version 9.5 Fix Pack 4, and then perform the steps listed below.

Procedure

  1. Install a master domain manager at Version 9.5 Fix Pack 4 or later, if not already present in your environment.
  2. Install a backup dynamic domain manager at Version 10.1 Fix Pack 3.
  3. To switch master domain manager capabilities from the master domain manager to the backup dynamic domain manager, launch a switchmgr command from the backup dynamic domain manager at Version 10.1 Fix Pack 3, as follows: 
    conman switchmgr domain_name:newmgr_name
    where
    domain_name
    Specifies the domain in which you want to switch managers.
    newmgr_name
    Specifies the name of the new domain manager, that is the current backup dynamic domain manager at Version 10.1.
  4. On the previous backup dynamic domain manager, browse to the BrokerWorkstation.properties file located in:
    On Windows systems
    <TWA_home>\broker\config
    On UNIX systems
    <TWA_DATA_DIR>/broker/config
  5. Add or uncomment the Broker.Workstation.PortSSL property and set it to true.
  6. Modify the backup dynamic domain manager workstation definition by adding the SECUREADDR and SECURITYLEVEL arguments. Ensure the SECUREADDR and TCPADDR arguments are set to the same value. For more information, see Workstation definition.
  7. Modify the previous master domain manager workstation definition by changing the type argument from mdm to fta. For more information, see Workstation definition.
  8. Modify the previous backup dynamic domain manager workstation definition by changing the type argument from fta to mdm. For more information, see Workstation definition.
  9. Run a production plan to make the changes effective: 
     JnextPlan -for 0000
  10. Stop and start WebSphere Application Server Liberty Base, as described in Application server - starting and stopping.