Cloning the deployment environment

You can export the configuration properties from an existing deployment environment, modify the properties with the IBM BPM Configuration editor, and then create another deployment environment on a different IBM® Business Process Manager installation that is similar to the exported deployment environment (a clone with modifications).

About this task

After you export the configuration properties, use the IBM BPM Configuration editor to update the exported properties to match your requirements. For example, you can update the database information to use a new set of databases, update the LDAP server to use the testing server, and update performance tuning properties to match the new environment. After you modify the properties file in the editor, you can use the BPMConfig -create command to create a new deployment environment that is a partial clone of the existing deployment environment, based on the modified file.

The following properties are exported:

Cell and deployment environment configuration properties
Deployment manager and managed node configuration properties
Cluster and cluster member configuration properties
Database, data source, and JDBC provider configuration properties
Authentication alias and role mapping configuration properties
LDAP configuration properties
Deployment environment and Process Portal context root prefix (if set in the current deployment environment)
Business Process Choreographer customization properties
Additional performance-tuning configuration properties

The databases and customer applications are not replicated to the new environment. For instructions to replicate the complete environment, see Migrating IBM BPM to new hardware.

Procedure

To clone the deployment environment, complete the following steps:

Run the BPMConfig –export command to extract the configuration data from the IBM BPM deployment environment.

For example:

BPMConfig.sh -export -profile DmgrProfile -de DeploymentEnvironment1 -outputDir /home/user_name/DE1ConfigFolder
BPMConfig.bat -export -profile DmgrProfile -de DeploymentEnvironment1 -outputDir C:\DE1ConfigFolder

Important: Specify a different output directory for each deployment environment. In the case where a cell has multiple deployment environments, a unique output directory is required for each deployment environment.

The configuration files are placed in the output directory that you specify.

Table 1. Configuration files for each deployment environment
Sample name	Description
`de_name`.properties	This properties file contains the configuration information from your source environment. You use this file when you configure the target environment. For more information, see the reference topic about configuration properties for the BPMConfig command.
fileRegistry.xml	If you use a file-based user registry, the user registry file is copied from the source environment to be added to the target environment.
ltpa.jceks	If you use LTPA, the LTPA key file is copied from the source environment to be added to the target environment.
ldap_additional_properties.xml	If you use a federated repository and an unencrypted LDAP connection in the source environment, additional properties of the LDAP server are copied from the source environment to the output directory, where they are later used automatically to create the target environment.
Application-config-bpc.xml and resources-bpc.xml	If you have Business Process Choreographer configured in the source environment, the configuration files are copied from the source environment to the output directory, where they are later used automatically to create the target environment.
Support-config-bpc.xml	If you have Business Process Choreographer Archive Manager configured on the support cluster in the source environment, the configuration is copied from the source environment to the output directory, where it is later used automatically to create the target environment.

Use the IBM BPM Configuration editor to update the exported properties to match your requirements for the new deployment environment. Make sure that the database information for each component points to a new database schema, because database schemas must not be shared between deployment environments.
Save the updated properties file, keeping it in the same output directory. Copy the output directory to the computer where you want to create the new deployment environment.
Install IBM Business Process Manager on the computer where you want to create the new deployment environment.

Validate that all database connections are correctly configured.

BPMConfig -validate -db output_directory/updated_properties_file

Create the new deployment environment.
```
BPMConfig -create -de output_directory/updated_properties_file
```
In the following example, the exported DE1.properties file and all the other files from table 1 are in the current directory.
```
BPMConfig -create -de DE1.properties
```
In the following example, the exported DE2.properties file and all the other files from table 1 are in the /usr/joe/De2CfgBackup directory.
```
BPMConfig -create -de /usr/joe/De2CfgBackup/DE2.properties
```
If you set the bpm.de.deferSchemaCreation property to true, create the database schemas manually using the generated scripts and run the bootstrapProcessServerData command.

Results

A new deployment environment is created based on the exported and modified configuration information.