Add nodes to deployment manager profiles on IBM i

We can add WebSphere Application Server nodes to the cell that the deployment manager profile is managing.

This article assumes that we are working on the IBM i server that hosts our WAS node.

Use the addNode command to add WAS nodes to the cell which the deployment manager profile is managing.

Tasks

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

2. At the Qshell prompt, issue the addNode command.

   Specify the host name and Simple Object Access Protocol (SOAP) port for the deployment manager. For example:

   app_server_root/bin/addNode
      host_name 
      soap_port 
      -includeapps
   

   The host_name variable is the host name of the server on which we installed the Network Deployment product. The soap_port variable 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 we are adding, or if we know that there are no conflicts with applications installed on other nodes, we can specify the -includeapps parameter when invoking the addNode command. When this parameter is specified, the addNode command does not remove any installed applications.

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

   See the addNode documentation for more information.

The addNode command creates a new server, the node agent, under the application server profile being added to the Network Deployment domain. The nodeagent server is started as a side effect of adding the node to the domain.

What to do next

Repeat the previous steps for each node (or application server profile) to manage using the deployment manager profile.

Verify that the node agent is running after adding the node, as described in Verifying that the node agent is running on IBM i.

Starting and configuring default deployment manager profiles on IBM i

Verifying that the node agent is running on IBM i