WebSphere Enterprise Service Bus, Version 6.2.0 Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows


Federating stand-alone server profiles to a deployment manager

Learn how to use the addNode command to federate a stand-alone server profile into a deployment manager cell. After federation, a node agent process is created. Both this node agent 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. A stand-alone server profile can be federated only if there are no other federated profiles.

Before you begin

Ensure that the following prerequisites are met:
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 stopped.
  • The stand-alone server does not use a database driver that supports remote access, such as Derby Network or Java toolbox JDBC.
  • The deployment manager has not yet been augmented into a WebSphere ESB deployment manager.
  • The deployment manager is not at the same release level or higher than the stand-alone server profile you created or augmented.
  • The deployment manager does not have a JMX administrative port enabled.
  • 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 node 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 before creating another profile with the same profile name.

About this task

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. However, you will be limited to a single cluster configuration for this deployment environment. See Deployment environment patterns for a description of the single cluster pattern.

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 for information on creating custom profiles.

Use the addNode command to federate a stand-alone server profile's node into a deployment manager cell by performing the following steps.

Procedure
  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, the directory is /QIBM/UserData/WebSphere/ESB on i5/OS platforms:
    • For i5/OS operating system profile_root/bin/
    • For Linux operating systemFor UNIX operating system profile_root/bin
    • For Windows operating system profile_root\bin
  2. Issue the addNode command.
    Issue one of following commands if security is not enabled. The port parameter is optional and can be omitted if you used the default port numbers when creating the deployment manager profile:
    • For i5/OS operating system addNode deployment_manager_host deployment_manager_SOAP_port -includeapps -includebuses
    • For Linux operating systemFor UNIX operating system ./addNode.sh deployment_manager_host deployment_manager_SOAP_port -includeapps -includebuses
    • For Windows operating system addNode.bat deployment_manager_host deployment_manager_SOAP_port -includeapps -includebuses
    Issue one of the following commands if security is enabled:
    • For i5/OS operating system addNode deployment_manager_host deployment_manager_SOAP_port -username userID_for_authentication -password password_for_authentication -localusername localuserID_for_authentication -localpassword localpassword_for_authentication -includeapps -includebuses
    • For Linux operating systemFor UNIX operating system ./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 -includeapps -includebuses
    • For Windows operating system 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 -includeapps -includebuses
    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.

Results

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.1.x, information center.

task Task topic

Terms of use | Feedback


Timestamp icon Last updated: 21 June 2010


http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/topic//com.ibm.websphere.wesb620.doc/doc/tins_federate_ss_node.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).