Extending a network deployment environment using the BPMConfig command
After you have created a deployment environment, you can
run the BPMConfig command at a later time to extend the deployment environment,
for example to add additional nodes or cluster members.
Before you begin
Before running the BPMConfig command:
- You must have installed the product on the computer where you want to extend the deployment environment.
- You must have an existing deployment environment.
- The deployment manager must be running.
Important: To use an external Content Platform Engine, the host name must have a domain name suffix,
for example MyDmgrHost.my_domain.com.
About this task
Run the BPMConfig command
with the
-create -de
option to add additional managed
nodes (profiles) to your existing environment. When it runs, the BPMConfig command:- Creates any local profiles specified in the configuration properties file that do not already exist. BPMConfig cannot augment existing WebSphere® Application Server profiles with Business Automation Workflow. If you want to use existing WebSphere Application Server profiles, you must augment them first. See Creating or augmenting managed-node profiles on Linux.
- Federates the node of the profile and adds the managed node to the deployment environment.
- Creates any missing cluster members.
Note: The bootstrap command bootstrapProcessServerData is
not run in this particular scenario because the database already exists.
The value of the bpm.de.deferSchemaCreation property
is ignored.
Procedure
To extend an existing deployment environment to include additional nodes (profiles) or cluster members: