Avoid port conflicts that can occur when you have Version 5.x and Version 6.0.x managed nodes on the same machine.
If you create a Version 6.0.x managed node on the same system where another Version 6.0.x managed node exists, the addNode command increments the port assignments of the second node agent process so that no conflict occurs. The Profile creation wizard also handles the port assignments successfully when you federate a custom node during the creation of the custom profile.
Contrast the Version 6.0.x coexistence scenario just described to the following cross-version scenario where a Version 5.x managed node exists.
Assume that you create a Version 6.0.x managed node on the same system where a Version 5.x managed node exists. Neither the addNode command nor the Profile creation wizard has a record of the Version 5.x port assignments. Port assignments on the second, Version 6.0.x node agent process are not incremented. Conflicts occur.
The conflicts prevent the second node from starting. If you start the Version 5.x node first, the Version 6.0.x node cannot start. If you start the Version 6.0.x node first, the Version 5.x node cannot start.
Perform the following procedure to create a Version 6.0.x managed node with nonconflicting ports.
The -startingport parameter supplies the base port number for all node agent ports and increments all of the port values from the starting point. The nonconflicting port assignments let the new node agent run when the Version 5.x node agent process is already running.
This procedure results in the ability to start your Version 5.x node at the same time as your Version 6.0.x node. The none agents can run on the same server.
Learn more about the addNode command . You can also assign ports individually using the -portprops parameter. The parameter identifies a flat file of key words and port number assignments that you must create.
WC_defaulthost 9081 WC_adminhost 9062 WC_defaulthost_secure 9444 WC_adminhost_secure 9045 BOOTSTRAP_ADDRESS 2810 SOAP_CONNECTOR_ADDRESS 8881 SAS_SSL_SERVERAUTH_LISTENER_ADDRESS 9901 CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS 9201 CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS 9102 ORB_LISTENER_ADDRESS 9900 CELL_DISCOVERY_ADDRESS 7272 DCS_UNICAST_ADDRESS 9354
After migrating a Version 5.x deployment manager to a Version 6.0.x deployment manager, you can migrate the Version 5.x managed nodes incrementally. See Migrating a Version 5.x managed node to a Version 6.0.x managed node for more information.