Portal V7.0 cluster: Setting up unique ports

Update the ports for the deployment manager, node agents and application servers.

You may still have your source servers running and broadcasting services within your network. Note that after migration, the deployment manager name for example remains unchanged. To avoid conflicts with the new target environment server and services you need to set unique ports.

As a rule of thumb, increase by 100 the original port number. You still need to make sure the same ports are not used in the source environment.

  1. Open the WebSphere® Integrated Solutions Console.
  2. Click System administration > Deployment manager > Ports.
  3. Update the following ports:
    • CELL_DISCOVERY_ADDRESS
    • DCS_UNICAST_ADDRESS
  4. Click System administration > Node agents > node_agent > Ports.
    1. Update the following ports:
      • DCS_UNICAST_ADDRESS
      • NODE_DISCOVERY_ADDRESS
      • NODE_IPV6_MULTICAST_DISCOVERY_ADDRESS
      • NODE_MULTICAST_DISCOVERY_ADDRESS
    2. Repeat this step on all node agents
  5. Click Servers > Server types > WebSphere application servers > application_servers > Ports.
    Note: The default value for application_servers is WebSphere_Portal however you may have more servers defined. You need to update the ports on all application servers listed.
  6. Update the following ports:
    • DCS_UNICAST_ADDRESS
  7. Fully resynchronize the primary node:
    1. Click System administration > Nodes
    2. Select the check box for the primary node.
    3. Click on Full Resynchronize.
    Note: For resynchronizing the primary node, the node agent on the primary node has to be running.
  8. Restart the deployment manager and node agent.
Parent topic: Portal V7.0 clustered environment