Avoid port conflicts that can occur when WebSphere Process Server
coexists on the same machine with installations of other WebSphere products.
Why and when to perform this task
If you create a WebSphere Process Server managed node on the same
system on which a managed node of another WebSphere 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 when the existing profile is one
of the following types:
- WebSphere Process Server
- WebSphere Enterprise Service Bus
- WebSphere Application Server, version 6.0 or later
- WebSphere Application Server Network Deployment, version 6.0 or later
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:
- WebSphere Business Integration Server Foundation
- WebSphere Application Server, versions prior to version 6.0
- WebSphere Application Server Network Deployment, versions prior to version
6.0
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
- Create the WebSphere Process Server stand-alone process server
or custom profile.
Use the Profile wizard to create the profile.
If you are creating a custom profile, do not federate it as you create it.
Select the check box on the Profile wizard panel to federate the profile later.
See the procedure described in Creating profiles using the Profile wizard.
- Check for ports in use to determine 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.
- 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):
On Linux and UNIX platforms: Type cd profile_root/bin
On Windows platforms: From a command line,
type cd profile_root\bin
- Use the addNode command with the -startingport parameter
to federate the profile into the deployment manager cell and to assign ports
from a beginning value.
Restriction: You
can federate a stand-alone server to a deployment manager only if no other
servers are already federated to that deployment manager.
For example,
assume you are working on a Solaris system and 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.
You can also assign ports individually
using the
addNode command with the
-portprops filename parameter.
This parameter identifies a flat file of key words and port number assignments
that you must create. The following example of a file called by the
-portprops parameter
shows all key words and example 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
For more information on the addNode command
and its parameters, see the topic addNode command in the WebSphere Application
Server Network Deployment, version 6.0, information center.
Last updated: Wed 01 Nov 2006 07:47:12
(c) Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)