Federating custom nodes to a deployment manager

Use the addNode command to federate a WebSphere Process Server custom node into a deployment manager cell.

Before you begin

Do the following before using this procedure:
Attention: Do not federate a custom node at this time if any one of the following is true:
  • The deployment manager is not running or you are not sure if it is running.
  • The deployment manager is a WebSphere Application Server Network Deployment profile that has not yet been augmented into a WebSphere Process Server profile.
  • The SOAP connector is disabled.
  • The deployment manager is reconfigured to use the non-default remote method invocation (RMI) as the preferred Java Management Extensions (JMX) connector. (Select System administration > Deployment manager > Administration services in the administrative console of the deployment manager to verify the preferred connector type.)
If you federate a custom node when the deployment manager is not running or is not available for other reasons, profile federation will fail and the resulting custom profile will be unusable. You must then move this custom profile directory out of the profile repository (by default, the profiles directory in install_root, where install_root is the WebSphere Process Server installation directory) before creating another custom profile with the same profile name.

Why and when to perform this task

Use the addNode command to federate a custom node into a deployment manager cell by doing the following.

Steps for this task

  1. Go to the bin directory of the custom node you want to federate. Open a command window and go to one of the following directories, depending on platform (where profile_root represents the installation location of the custom profile, by default install_root/profiles/profile_name on Linux and UNIX platforms or install_root\profiles\profile_name on Windows platforms):
    • Icon indicating Linux platforms Icon indicating UNIX platforms On Linux and UNIX platforms: profile_root/bin
    • Icon indicating Windows platforms On Windows platforms (from a command line): profile_root\bin
  2. Issue the addNode command. Issue one of following commands if security is not enabled:
    • Icon indicating Linux platforms Icon indicating UNIX platforms On Linux and UNIX platforms: ./addNode.sh deployment_manager_host deployment_manager_SOAP_port
    • Icon indicating Windows platforms On Windows platforms (from a command line): addNode.bat deployment_manager_host deployment_manager_SOAP_port
    Issue one of the following commands if security is enabled:
    • Icon indicating Linux platforms Icon indicating UNIX platforms On Linux and UNIX platforms: ./addNode.sh deployment_manager_host deployment_manager_SOAP_port -username userID_for_authentication -password password_for_authentication
    • Icon indicating Windows platforms On Windows platforms (from a command line): addNode.bat deployment_manager_host deployment_manager_SOAP_port -username userID_for_authentication -password password_for_authentication
    An output window opens. If you see a message similar to the following, your custom node was federated successfully:
    ADMU0003I: Node DMNDID2Node03 has been successfully federated.

Result

The custom node is federated into the deployment manager. For more information on the addNode command and its parameters, see the topic addNode command in the WebSphere Application Server Network Deployment, version 6.0, information center.

What to do next

After federating the custom node, go to the administrative console of the deployment manager to customize the empty node.

Last updated: Wed 01 Nov 2006 07:47:12

(c) Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)