Avoiding port conflicts

You must prevent port conflicts from occurring when you have WebSphere Process Server coexisting on the same machine with another installation of itself or of WebSphere Enterprise Service Bus, WebSphere Business Integration Server Foundation, WebSphere Application Server, or WebSphere Application Server Network Deployment.

Before you begin

Use this procedure to avoid port conflicts when adding a WebSphere Process Server node to a WebSphere Process Server deployment manager cell when a WebSphere Enterprise Service Bus, WebSphere Business Integration Server Foundation, WebSphere Application Server, or WebSphere Application Server Network Deployment managed node exists on the same system.

Why and when to perform this task

If you create a WebSphere Process Server managed profile on the same system on which a managed node of another product exists, in certain cases the addNode command can automatically increment the port assignments of the second nodeagent process so that no conflicts occur. The addNode command increments port assignments automatically only when the existing profile is one of the following types: The Profile Wizard also handles the port assignments successfully when you federate a WebSphere Process Server custom profile during its creation.
The addNode command does not increment port assignments automatically when the existing instance is one of the following types: In this case, neither the addNode command nor the Profile Wizard has a record of the port assignments given to these instances. Port assignments on the second WebSphere Process Server nodeagent process are not incremented and conflicts can occur.

These conflicts can prevent the second node from starting. For instance, if you start the existing managed node first, the WebSphere Process Server node cannot start. If you start the WebSphere Process Server node first, the existing node cannot start.

In those cases in which the addNode command does not increment port assignments automatically, you must perform the following procedure to create a WebSphere Process Server managed node with non-conflicting ports.

Steps for this task

  1. Create the WebSphere Process Server custom profile.

    Use the Profile Wizard to create a custom profile. Do not federate the custom profile as you create it. Select the check box on the Profile Wizard panel to federate the profile later. See the procedures described in Creating and augmenting profiles by using the Profile Wizard.

  2. Check for ports in use to determine a starting port number for the WebSphere Process Server nodeagent process.

    Use the netstat -a command to check existing port assignments. Analyze the port assignments to determine twelve 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.
    Do one of the following to move to the bin directory of the profile (where profile_root represents the installation location of the profile):
    • Icon indicating Linux platforms Icon indicating UNIX platforms On Linux and UNIX platforms: Type cd profile_root/bin
    • Icon indicating Windows platforms On Windows platforms: From a command line, type cd profile_root\bin
  4. Use the addNode command with the -startingport parameter to federate the 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: server_name.ibm.com
    • JMX connector type: remote method invocation (RMI)
    • RMI port assignment: 8879
    • Security status: Enabled
    Issue the following command:
    addNode.sh server_name.ibm.com \
    -conntype RMI 8879 \
    -user user_name \
    -password user_password -startingport 3333
    Important: The \ character is a continuation character for using more than one line to submit commands.

Result

The -startingport parameter supplies the base port number for all nodeagent ports and increments all of the port values from the starting point. The non-conflicting port assignments let the new WebSphere Process Server nodeagent run when the coexisting node is already running.

This procedure results in the ability to start your coexisting node at the same time as your WebSphere Process Server node. The nodeagents can run on the same server.

For more information about the addnode command, see the WebSphere Application Server Network Deployment, version 6.0, information center at http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp.

To change the port settings after installation, edit the serverindex.xml file located in one of the following directories, depending on platform (where profile_root represents the installation location of the profile):

Terms of use |

Last updated: Thu Apr 27 15:20:07 2006

(c) Copyright IBM Corporation 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)