Add a node to the deployment manager profile

Use the addNode script to add WebSphere Application Server nodes to the cell which your deployment manager profile is managing. Repeat the steps below for each node (or application server profile) you want to manage using your deployment manager profile.

Perform these steps on the iSeries server that hosts your WebSphere Application Server node.

1. Run the STRQSH (Start Qshell) command from the CL command line.

2. At the Qshell prompt, call the addNode script. Specifying the host name and Simple Object Access Protocol (SOAP) port for the Deployment Manager. For example,

     /QIBM/ProdData/WebSphere/AppServer/V6/Base/bin/addNode hostName soapPort -includeapps

   where hostName is the host name of the server on which you installed Network Deployment and soapPort is the SOAP port for the deployment manager profile. For the deployment manager profile, the default soap port is 8879.

   By default, any applications installed on the application server profile are removed from the application server profile when it is added to a cell. If this is the only node that you are adding, or if you know that there are no conflicts with applications installed on other nodes, you can specify the -includeapps parameter when invoking addNode. When this parameter is specified, addNode does not remove any installed applications.

   Note: The host_name and soapPort parameters are positional and must be the first two parameters. Additional parameters such as -includeapps must be specified after the soapPort value.

   For more information about the addNode script, see The addNode command.

3. Verify that the node agent is running.
   The addNode command creates a new server, the node agent, under the application server profile being added to the Network Deployment domain. The node agent server is started as a side effect of adding the node to the domain. This topic describes how to verify that the node agent has started.

Verify that the node agent is running