The addNode script

The addNode script incorporates an instance of the base WebSphere Application Server product into a Network Deployment cell. For usage instructions and examples, see Add nodes to a Network Deployment instance.

Note: Depending on the size and location of the new node that you incorporate into the cell, this script can take several minutes to complete.

Product

The addNode script is available in the WebSphere Application Server product only.

Authority

To run this script, your user profile must have *ALLOBJ authority.

Syntax

The syntax of the addNode script is:

addNode dmgr_host [ dmgr_port ] [ -instance instance ]
 [ -nowait ] [ -quiet ] [ -logfile logfilename ] [ -replacelog ] [ -trace ]
 [ -noagent ] [ -username username ] [ -password password ]
 [-conntype conntype ] [ -includeapps ] [ -startingport startportnumber ]
 [ -help | -? ]

Parameters

The parameters of the addNode script are:

• dmgr_host
  This is a required parameter. The value dmgr_host specifies the name of the machine that hosts the deployment manager (Network Deployment instance) for the Network Deployment cell.

• dmgr_port
  Optional. The value dmgr_port specifies the SOAP or RMI port on which the deployment manager for the Network Deployment cell is listening. By default, the script uses the SOAP connector type on port 8879. If you specify a port other than the SOAP port for your deployment manager, specify the -conntype parameter. The deployment manager must be started and actively listening on the port specified for this parameter.

• -instance
  Optional. The value instance specifies the name of the instance to add to the Network Deployment cell. If you do not specify this parameter, the script adds the default instance to the Network Deployment cell.

• -nowait
  Optional. If you specify this parameter, the script returns control to the addNode script and does not wait for the node agent to start successfully. The default is to wait for the node agent to start successfully.

• -quiet
  Optional. If you specify this parameter, the script does not display informational messages. The default is to display informational messages while the script runs.

• -logfile
  Optional. The value filename specifies the location and name of the log file for the script. The default value is /QIBM/UserData/WebAS5/Base/instance/logs/addNode.log where instance is the name of the instance that contains to which the server for which you want to display status.

• -replacelog
  Optional. If you specify this parameter, the script replaces the log file if it exists. By default the script appends to the log file if it exists.

• -trace
  Optional. If you specify this parameter, the script outputs additional trace information to the log file for the script. You should only specify this parameter if errors occur when you try to add a node. The default is to not log additional trace information.

• -noagent
  Optional. If you specify this parameter, the script does not launch the node agent process automatically after the node is added to the cell. The default is to start the node agent process automatically as part of the addNode script.

• -username
  This parameter is required if security is enabled for the server. The value username specifies the user name for authentication.

• -password
  This parameter is required if security is enabled for the server. The value password specifies the password for authentication.

• -conntype
  Optional. If you specify the -port parameter, the -conntype parameter specifies the connector type to use. Valid values are SOAP or RMI. The default value is SOAP.

• -includeapps
  Optional. By default, when the script adds the node to the Network Deployment cell, it does not include the applications that are installed on the application server. If you specify this parameter, the script installs the applications into the Network Deployment cell when it adds the node. If the application already exists in the cell, the script prints warning and the application is not installed into the cell.

• -startingport
  Optional. The value startportnumber specifies the first of a block of port numbers that the script uses for the node agent and JMS server ports that it creates. This parameter allows you to control which ports are defined for these servers. If you do not specify this parameter, the script assigns the default port numbers to the node agent and JMS server. If you are using multiple instances, it is recommended that you specify this parameter. For information on the default ports, see WebSphere Application Server node agent default port definitions and WebSphere Application Server JMS server default port definitions.

• -help or -?
  This optional paramter prints the usage statement for the script.

Examples

These examples demonstrate correct syntax:

addNode testhost 8879

This example adds the default instance (node) to a Network Deployment cell. The cell is managed by the deployment manager that runs in the default Network Deployment instance. The default Network Deployment instance is hosted on the iSeries server named testhost. Port 8879 is the default SOAP port for the default instance of Network Deployment.

addNode myiseries 11381 -instance testinst -startingport 10380

This example adds the testinst node (instance) to the Network Deployment cell that is managed by the deployment manager on the iSeries server myiseries. The SOAP port for the Network Deployment instance is 11381. To assign the ports for the new node agent and JMS servers, the script starts with port 10380 and increments by one for each port needed.

Note: In most cases, you do not need to change the default SOAP port for a Network Deployment instance. If the value of dmgr_port is not 8879, then you are probably adding the node to a non-default Network Deployment instance.