Federating stand-alone server profiles to a deployment manager

Use the addNode command to federate a WebSphere Process Server stand-alone server profile into a deployment manager cell. After federation, a nodeagent process is created. Both this nodeagent and the server process are managed by the deployment manager. If you federate a stand-alone server profile and include all of its applications, the act of federation installs the applications on the deployment manager where they can be redeployed. If you remove a federated server node from a deployment manager, the server returns to its original configuration, which is a stand-alone process server. A stand-alone server profile can only be federated if there are no other federated profiles.

Before you begin

Do the following before using this procedure:
Attention: Do not federate a stand-alone server profile 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 stand-alone server is running or you are not sure if it is off.
  • 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.)
  • Another profile has already been federated to the deployment manager.
If you federate a stand-alone server profile when the deployment manager is not running or is not available for other reasons, profile federation will fail and the resulting profile will be unusable. You must then move this stand-alone server 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 profile with the same profile name.

Why and when to perform this task

You need to perform this task when you have an existing stand-alone server profile and you need to add the capabilities that network deployment offers to that server (central management or clustering). This function provides a growth path for an existing stand-alone server profile. Perform this task once for each cell and only for the first profile federated to the cell. Do not perform this task if the cell already has federated nodes. When you create an environment where you do not have an existing stand-alone server profile, create the environment using custom profiles. See Creating profiles and Configuring a custom profile (managed node) for information on creating custom profiles.

Use the addNode command to federate a stand-alone server profile into a deployment manager cell by doing the following.

Steps for this task

  1. Go to the bin directory of the stand-alone server profile 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 stand-alone server profile, by default, install_root/profiles/profile_name on Linux and UNIX platforms and 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 -localusername localuserID_for_authentication -localpassword localpassword_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-localusername localuserID_for_authentication -localpassword localpassword_for_authentication
    An output window opens. If you see a message similar to the following, your stand-alone server profile was federated successfully:
    ADMU0003I: Node DMNDID2Node02 has been successfully federated.

Result

The stand-alone server profile 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.

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)