Use the addNode command to add a standalone node into a cell.
For
information about port numbers, see port
number settings in WebSphere Application Server versions.
You can only include Version 5.x nodes in a Version 6.x mixed-release cell through migration. First, migrate the deployment manager from Version 5.x to Version 6.x; and then, either keep the nodes at Version 5.x or migrate them to Version 6.x.
If in the hosts file mappings exist from the 127.0.0.1 IP address to a host name other than localhost, remove the mappings. The following example illustrates what might happen if the mappings are not removed: When a node agent communicates with the deployment manager, it sends its IP address to the deployment manager. The node agent resolves the node agent host name to 127.0.0.1 if the operating system returns a mapping for the host name from the hosts file. This resolution prevents the deployment manager from sending a message to the node agent because the 127.0.0.1 IP address is also the IP address for the local machine of the deployment manager.
The
hosts file is located at /etc/hosts.
The
hosts file is located at \WINDOWS\system32\drivers\etc\hosts.
hosts=local,bind
com.ibm.SOAP.requestTimeout=180If you need to change the default you can edit this line to set the timeout to a value more appropriate for your situation (Note: setting the above value to 0 will disable the timeout check altogether). If the timeout value is set too high you will have to wait a long time to determine if the addNode command will successfully complete its request to the deployment manager. If the value is set too short the deployment manager will not have sufficient time to complete the request before the addNode command concludes that the deployment manager is not responding and will respond with an error. Other factors that may affect server timeouts include the processing load or excessive paging on the deployment manager and network latency. Some of these conditions may be transient.
You will come into contact with the issue if you have a federated node and run the addNode command again for a different deployment manager. This causes the deployment manager to be corrupted and you will not be able to start the deployment manager afterwards because of the incomplete node directory.
washome/profiles/dmgrProfile/config/cells/dmgrCell/]nodeName