In a network deployment environment, only managed nodes are used to host applications and modules. To create a managed node you can federate a stand-alone server profile or custom profile to the deployment manager. The federation process adds the node defined by the profile as a new managed node in the network deployment cell.

1. Ensure that the deployment manager is running. To start the deployment manager, either select Start the deployment manager from its First Steps console or enter 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):
   
   
   
   • On Linux and UNIX platforms: profile_root/bin/startManager.sh
   
   
   • On Windows platforms (from a command line): profile_root\bin\startManager.bat
   
   
   
   


2. To federate a stand-alone server profile, use the addNode command, optionally with the -include* arguments. In the install_root/bindirectory, issue the addNode command with the -profileName option and optionally with the -include* arguments.
   
   
   
   • On Linux and UNIX platforms: install_root/bin/addNode.sh -profileName profile_name deployment_manager_host deployment_manager_SOAP_port -includeapps -includebuses
   
   
   • On Windows platforms (from a command line): install_root/bin/addNode.bat -profileName profile_name deployment_manager_host deployment_manager_SOAP_port -includeapps -includebuses
   
   
   
   

   The deployment_manager_host argument is required. All of the other arguments are optional. The default port number is 8879 for the default SOAP port of the deployment manager. If you have multiple WebSphere^® installations or multiple profiles, the SOAP port might be different than 8879.

   
   
   Tip:To determine the correct port number, use the deployment manager administrative console to display the SOAP_CONNECTOR_ADDRESS value on the Ports panel:

   
   
   1. Click System Administration > Deployment Manager Communications > Ports
   
   
   2. Read the port number for the port name SOAP_CONNECTOR_ADDRESS
   
   
   
   

   profile_name

   The name of the stand-alone server profile that you want to federate to the deployment manager.

   -includeapps

   By default the addNode command does not carry over applications (and SCA modules) from the stand-alone server to the network deployment cell. In general, you should install applications using the deployment manager. The -includeapps option tells the addNode command to carry over the applications from the stand-alone server profile. If the application already exists in the cell, a warning is printed and the application does not install in the cell.

   -includebuses

   Copies the service integration bus configuration from the stand-alone server profile to the network deployment cell. This configuration is used to create the SCA.SYSTEM bus and SCA.APPLICATION bus for the deployment manager cell.

   For example:
   

   C:\Program Files\IBM\WebSphere\ESB\bin>addNode -profileName default esbdmgr01host 8879 -includeapps -includebuses

   
   


3. To federate a custom profile, use the addNode command without the -include* parameters. In the install_root/bindirectory, issue the addNode command with the -profileName option.
   
   
   
   • On Linux and UNIX platforms: install_root/bin/addNode.sh -profileName profile_name deployment_manager_host deployment_manager_SOAP_port
   
   
   • On Windows platforms (from a command line): install_root/bin/addNode.bat -profileName profile_name deployment_manager_host deployment_manager_SOAP_port
   
   
   
   where profile_nameis the name of the custom profile that you want to federate to the deployment manager. For example:
   

   C:\Program Files\IBM\WebSphere\ESB\bin>addNode -profileName Custom01 esbdmgr01host 8879

   
   

ADMU0116I: Tool information is being logged in file C:\Program
           Files\IBM\WebSphere\ESB\profiles\Custom01\logs\addNode.log
ADMU0128I: Starting tool with the Custom01 profile
ADMU0001I: Begin federation of node customhostNode02 with Deployment Manager at
           esbdmgr01host:8879.
...
ADMU0015I: Backing up the original cell repository.
...
ADMU0012I: Creating Node Agent configuration for node: customhostNode02
ADMU0014I: Adding node customhostNode02 configuration to cell: esbdmgr01hostCell01
ADMU0016I: Synchronizing configuration between node and cell.
ADMU0018I: Launching Node Agent process for node: customhostNode02
ADMU0020I: Reading configuration for Node Agent process: nodeagent
ADMU0022I: Node Agent launched. Waiting for initialization status.
ADMU0030I: Node Agent initialization completed successfully. Process id is:
           5684
ADMU9990I:
ADMU0300I: Congratulations! Your node customhostNode02 has been successfully
           incorporated into the esbdmgr01hostCell01 cell.
...
ADMU0003I: Node customhostNode02 has been successfully federated.