WebSphere Application Server Network Deployment, Version 6.0.x   Operating Systems: AIX, HP-UX, Linux, Solaris, Windows
             [TIP: Focusing the table of contents and search results]

Avoiding port conflicts in coexisting Version 5.x and Version 6.0.x node agents

Avoid port conflicts that can occur when you have Version 5.x and Version 6.0.x managed nodes on the same machine.

About this task

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.

Procedure

  1. Create the Version 6.0.x application server profile or the custom profile.

    Do not federate the custom node as you create the custom profile. Select the check box on the Profile creation wizard panel to federate the node later.

  2. Check for ports in use to determine a starting port number for the Version 6.0.x node agent process.

    Use the netstat -a command to check existing port assignments. Analyze the port assignments to determine 12 sequential free ports.

    This procedure assumes that no port assignments exist between 3320 and 3380.

  3. Change directories to the bin directory of the new profile.

    Assume that you create an application server profile named V6MngNode in the default installation root directory on a Linux system.

    cd /opt/IBM/WebSphere/AppServer/profiles/V6MngdNode/bin
  4. Use the addNode command with the -startingport parameter to federate the application server or custom node into the deployment manager cell and to assign ports from a beginning value.
    Assume that the deployment manager has the following characteristics:
    • Host name is the domain name system address: nittany.ibm.raleigh.com
    • JMX connector type: remote method invocation (RMI)
    • RMI port assignment: 8879
    • Security status: Enabled
    • Applications to install: DefaultApplication and the samples
    In a Linux environment, for example, issue the following command:
    ./addNode.sh nittany.ibm.raleigh.com -conntype RMI 8879 
      -includeapps -user lions44 -password PSU -startingport 3333

    The \ character is a continuation character for using more than one line to submit commands.

Results

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.

What to do next

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.

The following example of a portprops file shows all key words and their default port assignments:
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.




Related tasks
Setting up Version 5.x and Version 6.0.x coexistence
Task topic    

Terms of Use | Feedback

Last updated: Mar 8, 2007 8:14:28 PM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/tins_portconflicts.html

© Copyright IBM Corporation 2004, 2006. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)