WebSphere WebSphere Enterprise Service Bus, Version 6.0.1 Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Federating custom nodes to a deployment manager

After creating a custom profile, you must have access to a running deployment manager to federate the node. Federating the custom profile makes the node operational. If the custom profile is on a machine that does not have a deployment manager, the deployment manager must be accessible over the network to allow the federation of the node.

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 ESB profile.
  • Security is enabled on the deployment manager node.
  • 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 creation 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 ESB 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. Start the deployment manager. Start the deployment manager either by selecting Start the deployment manager from its First Steps console or by entering the following command (where profile_root represents the installation location of the deployment manager profile, by default install_root/profiles/deployment_manager_profile_name on Linux and UNIX platforms or install_root\profiles\deployment_manager_profile_name on Windows platforms):
    • LINUX platforms UNIX platforms On Linux and UNIX platforms: profile_root/bin/startManager.sh
    • For Windows platforms On Windows platforms (from a command line): profile_root\bin\startManager.bat
  2. 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):
    • LINUX platforms UNIX platforms On Linux and UNIX platforms: profile_root/bin
    • For Windows platforms On Windows platforms (from a command line): profile_root\bin
  3. Issue the addNode command. Issue one of following commands, depending on platform:
    • LINUX platforms UNIX platforms On Linux and UNIX platforms: ./addNode.sh deployment_manager_host deployment_manager_SOAP_port
    • For Windows platforms On Windows platforms (from a command line): addNode.bat deployment_manager_host deployment_manager_SOAP_port
    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.
  4. Within the same directory, issue the startNode command. Issue one of following commands, depending on platform:
    • LINUX platforms UNIX platforms On Linux and UNIX platforms: ./startNode.sh
    • For Windows platforms On Windows platforms (from a command line): startNode.bat

Result

The custom node is federated into the deployment manager cell, as a managed node.

What to do next

You can now change the configuration of the managed node, such as to create servers on that node.
Related reference
addNode command
startNode

Task topic

Terms of Use | Rate this page

Timestamp iconLast updated: 12 Dec 2005
http://publib.boulder.ibm.com/infocenter/dmndhelp/v6rxmx/index.jsp?topic=/com.ibm.websphere.wesb.doc\doc\tins_federate_mn_node.html

(C) Copyright IBM Corporation 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)