Configuring multiple WebSphere Application Server nodes on a single host machine.
 Technote (troubleshooting)
 
Problem(Abstract)
A WebSphere® Application Server node does not necessarily equate to a single host machine. It is possible to configure multiple nodes on a single host machine. Each node consists of its own set of configuration files and port assignments and can be run and administered independently of other nodes on the host machine.
 
Resolving the problem
There are two options for creating multiple nodes on a single host machine:
Multiple installations of WebSphere Application Server

You can install the product multiple times, in multiple locations, on a single host machine to create multiple nodes. This is referred to as coexistence.

  1. Choose different directories. If you use the installation wizard, make sure you select Install a new copy and specify a unique path where you want the new instance installed.

  2. Choose open port numbers. If you use the installation wizard, make sure you choose Modify ports for coexistence and verify that the suggested ports are not in use.

  3. For more information, refer to WebSphere Application Server coexistence.

Multiple instances of WebSphere Application Server with a single installation using wsinstance

Another option is to create multiple nodes from a single installation of the product with the wsinstance command. Each node has its own set of configuration and application files and its own port assignments. However, both nodes use the same WebSphere binaries and Java™ environment. This is referred to as a configuration instance.

  1. Run the wsinstance script (wsinstance.bat for windows or wsinstance.sh for UNIX®) located in the $WAS_HOME/bin/wsinstance directory in either the base or Network Deployment products.

  2. Use the following command to create the new node:

    wsinstance -name node name -host host name -path install directory -create

  3. If you don't use the -startingPort Port number flag or create a Host Name_Node Name_portdef.props file, the ports are only incremental one from the default installation ports. The -startingPort Port number flag places the first port at Port number, then uses the next thirteen consecutive ports. In the portdef.props file, you can define the initial ports for the new node. The portdef.props file must be located in the wsinstance directory when you run the wsinstance command.

  4. Run the wsinstance command with the following flag added to the end to debug the instance creation process: -debug com.ibm.*=all=enabled > Output File

    The output is printed to the screen unless you redirect the standard output to a file.

  5. For more information, refer to wsinstance command.

Starting and administering the nodes

  1. For the coexistence option, start and administer the node using the normal tools from the $WAS_HOME/bin directory, making sure that you are in the installation path for the intended node.

  2. For the configuration instance option, use the scripts from the $WAS_HOME/bin directory. First, however, initialize the environment for the intended node using the setupCmdLine script (setupCmdLine.bat for Windows or setupCmdLine.sh for UNIX), located in the $WAS_HOME/bin directory.

Adding nodes to a WebSphere Deployment Manager cell

If you are going to federate a node into a deployment manager cell, remember these things:

  1. You cannot federate a configuration instance of the base product into a deployment manager cell. A deployment manager cannot manage a configuration instance.

  2. You must use the -startingPort Port number option with the addNode command if the node you are adding uses non-default ports. Keep in mind that this also affects the JMS server ports.

  3. If you already federated a node into a WebSphere cell and need to modify port assignments, edit the serverindex.xml file located in the $WAS_HOME/config/cells/CELL NAME/nodes/NODE NAME directory.
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Install
Operating system(s): Windows
Software version: 5.0
Software edition:
Reference #: 1083439
IBM Group: Software Group
Modified date: Jan 31, 2005