Best practices for adding nodes using command line tools
Use the addNode command to add a standalone node into a cell. The addNode command does the following:
- Copies the base WAS cell configuration to a new cell structure. This new cell structure matches the structure of deployment manager.
- Creates a new node agent definition for the node that the cell incorporates.
- Sends commands to the deployment manager to add the documents from the new node to the cell repository.
- Performs the first configuration synchronization for the new node, and verifies that this node is synchronized with the cell.
- Launches the node agent process for the new node.
- Updates the setupCmdLine.bat or setupCmdline.sh files and the wsadmin.properties file to point to the new cell.
- After federating the node, the addNode command backs up the plugin-cfg.xml file from...<install_root>/config/cells
- The addNode command regenerates a new plugin-cfg.xml file at the Deployment Manger and the nodeSync operation copies the files to the node level.
Tips for using the addNode command:
- Do not put WAS Jar files on the generic CLASSPATH variable (default class path) for the overall system.
In addition, the /etc/nsswitch.conf file is set up to use the /etc/hosts path before trying to look up the server using a name server. This setup can cause failures when trying to add or administrate nodes when the deployment manager or application server is running on the Red Hat system or an Unix/Linux system with the same setup.
If your deployment manager or your application server run on the Red Hat system, or an Unix/Linux system with the same setup, perform the following operations to ensure that one can successfully add and administer nodes:
- Remove the 127.0.0.1 mapping to the local host in the /etc/hosts path.
...so that the hosts line reads...hosts: dns files
- By default, applications that are installed on the node will not copy to the cell. If you install an application after using the addNode command, the application will install on the cell. By specifying the -includeapps option, you force the addNode command to copy applications from the node to the cell. Applications with duplicate names will not copy to the cell.
- Cell-level documents are not merged. Any changes that you make to the standalone cell-level documents before using the addNode command must be repeated on the new cell. For example, virtual hosts.
Port number settings in WAS versions
WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.
IBM is a trademark of the IBM Corporation in the United States, other countries, or both.