Federating nodes to the deployment manager
After creating a custom profile, you can use the addNode command to federate the node into a deployment manager cell. This is only required if you specified the -federateLater parameter with the manageprofiles command or if the deployment manager was not running during the initial profile creation. You can manage all federated nodes from the deployment manager. (You can also use the BPMConfig command to federate nodes.)
Before you begin
Before using this procedure, ensure that
the following prerequisites are met:
- You have installed IBM® Business Process Manager and created a deployment manager and a managed-node profile. This procedure assumes you did not federate the managed-node profile during its creation or augmentation by using the BPMConfig command, Profile Management Tool, or manageprofiles command-line utility. (The BPMConfig command federates the node of the custom profile unless you specify the command with the -federateLater option.)
- The deployment manager is running. If it is not, start it either
by selecting Start the deployment manager from
its Quick Start console or by entering the following command, where profile_root represents
the installation location of the deployment manager profile:
- profile_root/bin/startManager.sh
- The deployment manager has been created or augmented to be an IBM Business Process Manager deployment manager.
- The deployment manager is at the same release level or higher than the managed-node profile you created or augmented.
- The deployment manager has a JMX administrative port enabled. The default protocol is SOAP.
Procedure
Results
The managed-node profile is federated into the deployment manager.
What to do next
After federating the managed-node profile, federate further profiles or go to the administrative console of the deployment manager to create your IBM BPM deployment environment.