This topic describes how to federate IBM WebSphere Process
Server, Version 6.0, stand-alone servers to a deployment manager.
Before you begin
Ensure you have installed WebSphere Process Server,
Version 6.0, and that you have created a deployment manager and a
stand-alone server. Why and when to perform this task
Use the addNode command to federate a stand-alone
server into a deployment manager cell by doing the following.Steps for this task
- 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 and 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
- Go to the bin directory
of the stand-alone server 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):

On
Linux and UNIX platforms: profile_root/bin
On Windows platforms (from a command
line): profile_root\bin
- Issue the addNode command. Issue one of following commands, depending on platform:

On Linux and
UNIX platforms: ./addNode.sh deployment_manager_host deployment_manager_SOAP_port
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 stand-alone server was federated successfully:ADMU0003I: Node DMNDID2Node02 has been successfully federated.