Extending the network deployment environment using the BPMConfig command

After you have created a deployment environment using the BPMConfig command, you can run the 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 created the deployment environment by running the BPMConfig command.
The deployment manager must be running.

Important: Run the BPMConfig command with the same properties file on all computers that will participate in the deployment environment. You must first run the command on the computer that has the deployment manager profile and then run it on each computer that has a managed node. At any given time, only one profile creation can be performed on a computer and only one node federation can be performed against a particular deployment manager. For this reason, if you are creating multiple profiles at once on different computers, you must use the federateLater option of the BPMConfig command when creating the managed node profiles and then run the command with the -create -de option sequentially on each computer to federate the managed nodes.

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.
Creates a new managed node for each new node specified in the configuration properties based on the specified values.
Federates the node and adds the node to the deployment environment. If the -create -profile action was issued with the -federateLater option, the node is created but not federated.

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):

If you do not already have a customized configuration properties file based on the existing deployment environment that you want to extend, use the BPMConfig command with the -export parameter to create a configuration properties file that reflects your current deployment environment. Determine the minimum settings for a new node by examining the sample configuration files that are provided in the following directory:
```
install_root/BPM/samples/config
```
Modify the properties file to add the additional nodes (profiles) to extend the existing environment.
When adding managed nodes to an existing deployment environment, define each new node by duplicating the set of bpm.de.node properties that exist in the properties file and specifying the values that apply to the new managed node. For more information about the available properties, read the comments in the sample files, or see the BPMConfig command-line utility and the examples.

Important: If you are using an Oracle database, you must include the database user name and password for all databases, including the optional ones.
Run the BPMConfig command on the computer that has the deployment manager and on each computer that has a managed node, passing it the name of the properties file that you created. For example:
```
install_root/bin/BPMConfig -create -de my_environment.properties 
```
Tip: You can also use the BPMConfig command to add cluster members by running the following command syntax:
```
BPMConfig -create -clusterMembers properties_file
```

What to do next

If the new or updated node is on the same computer as the deployment manager node, then the updated or new node is automatically synchronized with the deployment manager node. Before you start the node, ensure that this synchronization has completed by checking the syncNode.log file found in the PROFILE_ROOT/logs directory. If the new or updated node is on a different computer than the deployment manager node, you need to run the syncNode.bat or syncNode.sh command on the new or updated node and wait for the synchronization to complete before starting the node.