addNode.sh

 

Overview

The addNode.sh command incorporates a WAS installation into a cell.

addNode.sh must be run from the $WAS_HOME/bin directory. Depending on the size and location of the new node you incorporate into the cell, this command can take a few minutes to complete.

Syntax is:

addNode.sh  

deploymgr_host  

deploymgr_port  

[parameters]

The default port number is 8879.

 

Automatic Restart of Node Agents

If you recycle the system that hosts an appserver node, and did not set up the node agent to be an operating system daemon, issue a startNode command to re-establish the node as a member of the deployment cell.

 

Parameters

The options for the addNode.sh command follow:

-nowait

Tells the addNode.sh command not to wait for successful initialization of the launched node agent process.

-quiet

Suppresses the progress information that the addNode.sh command prints in normal mode.

-logfile filename

Specifies the location of the log file to which information gets written.

-replacelog

Replaces the log file instead of appending to the current log.

-trace

Generates trace information into a file for debugging purposes.

-newtracefile

By default the addNode.sh program appends to the existing trace file. This option causes the addNode.sh command to overwrite the trace file.

-noagent

Tells addNode.sh not to launch the node agent process for the new node.

-username name

Specifies the user name for authentication if security is enabled. Acts the same as the -user option.

-user name

Specifies the user name for authentication if security is enabled. Acts the same as the -username option.

-password password

Specifies the password for authentication if security is enabled.

-conntype type

Specifies the Java Management Extensions connector type to use for connecting to the deployment manager. Valid types are Simple Object Access Protocol (SOAP) or Remote Method Invocation (RMI).

-includeapps

By default the addNode.sh program does not carry over applications from the stand-alone servers on the new node to the cell. This option tells addNode.sh to attempt to include applications from the new node. If the application already exists in the cell, a warning is printed and the application is not installed into the cell.

By default, during application installation, application binaries are extracted in the $WAS_HOME/installedApps/cellName directory. After addNode.sh, the cell name of the configuration on the node that you added changes from the base cell name to the deployment manager cell name. The application binaries are located where they were before addNode.sh was performed, for example, $WAS_HOME/installedApps/old_cellName .

If the application was installed by explicitly specifying the location for binaries as the following: 

${APP_INSTALL_ROOT}/${CELL}
where variable ${CELL} specifies current cell name, then upon addNode.sh the binaries are moved to the following directory: 

${APP_INSTALL_ROOT}/currentcellname

Note: You have to use the -includeApps option to migrate all the applications to the new cell. Federating the node to a cell using addNode.sh command does not merge any cell level configuration including virtualHost information. If the virtual Host and aliases for the new cell does not match WebSphere Application Server, you will not be able to access the applications running on the servers. You have to manually add all the virtualHost and host aliases to the new cell using the administrative console running on the deployment manager.

-startingport portnumber

Allows you to specify a port number to use as the base port number for all node agent and jms server ports created during addNode.sh. This allows you to control which ports are defined for these servers, rather than using the default port values. The starting port number is incremented in order to calculate the port number for every node agent port and jms server port configured during addNode.sh.

-help

Prints a usage statement.

-?

Prints a usage statement.

 

Examples

This program does the following:

  • It copies the base WAS cell configuration to a new cell structure. This new cell structure matches the structure of deployment manager.

  • It creates a new node agent definition for the node that the cell incorporates.

  • It sends commands to the deployment manager to add the documents from the new node to the cell repository.

  • It performs the first configuration synchronization for the new node (ensures it is in sync with the cell).

  • It launches the node agent process for the new node.

For information about port numbers, see port number settings in WAS versions.

Note: The default Red Hat installation creates an association between the hostname of the machine and the loopback address -- 127.0.0.1. In addition, the /etc/nsswitch.conf file is set up to use /etc/hosts before trying to look up the server using a name server. This can cause failures when trying to add or administrate nodes when the deployment manager or appserver is running on Red Hat.

If your deployment manager or your appserver is running on Red Hat, perform the following operations on your Red Hat machines to ensure that you can successfully add and administrate nodes:

  • Remove the 127.0.0.1 mapping to the local host in /etc/hosts

  • Edit /etc/nsswitch.conf so that the hosts line reads: 

    hosts:         dns files

The following examples demonstrate correct syntax: 

addNode.sh testhost 8879

addNode.sh deploymgr 8879 -trace (produces addNode.sh.log file)

addNode.sh host25 8879 -nowait (does not wait for node agent process)
where 8879 is the default port.

Example output: 

$WAS_HOME/binaddnode dmgr_host
ADMU0116I: Tool information is being logged in file
           $WAS_HOME/logs/addNode.sh.log
ADMU0001I: Begin federation of node node_name with Deployment Manager at dmgr_host:8879.
ADMU0009I: Successfully connected to Deployment Manager Server: dmgr_host:8879.
ADMU0505I: Servers found in configuration:
ADMU0506I: Server name: servername
ADMU2010I: Stop all server processes for node node_name
ADMU0512I: Server servername cannot be reached. It appears to be stopped.
ADMU0024I: Deleting the old backup directory.
ADMU0015I: Backing up the original cell repository.
ADMU0012I: Creating Node Agent configuration for node: node_name
ADMU0014I: Adding node node_name configuration to cell: cell_name
ADMU0016I: Synchronizing configuration between node and cell.
ADMU0018I: Launching Node Agent process for node: node_name
ADMU0020I: Reading configuration for Node Agent process: nodeagent
ADMU0022I: Node Agent launched. Waiting for initialization status.
ADMU0030I: Node Agent initialization completed successfully. Process id is:
           2340
ADMU0523I: Creating Queue Manager for node node_name on server jmsserver
ADMU0525I: Details of Queue Manager creation may be seen in the file:
           createMQ.node_name_jmsserver.log
ADMU9990I:
ADMU0300I: Congratulations! Your node node_name has been successfully
           incorporated into the cell_name cell.
ADMU9990I:
ADMU0306I: Be aware:
ADMU0302I: Any cell-level documents from the stand-alone node_name
configuration have not been migrated to the new cell.
ADMU0307I: You might want to:
ADMU0303I: Update the configuration on the cell_name Deployment Manager
           with values from the old cell-level documents.
ADMU9990I:
ADMU0306I: Be aware:
ADMU0304I: Because -includeapps was not specified, applications installed on
           the stand-alone node were not installed on the new cell.
ADMU0307I: You might want to:
ADMU0305I: Install applications onto the cell_name  cell using wsadmin
           $AdminApp or the Administrative Console.
ADMU9990I:
ADMU0003I: Node node_name has been successfully federated.

Port number settings in WAS versions

 

IBM is a trademark of the IBM Corporation in the United States, other countries, or both.