Starting the target environment

Disable the automatic starting of all applications and schedulers in the target environment, start the deployment manager, start the managed node or nodes, and then start the servers.

Figure 1. Sample environment after the target is started. The source environment is not running. The target can read from the databases.

The details of the diagram are provided in the figure caption.

Procedure

If you use a file-based user registry in the source environment, merge the file-based user registry into the target environment.
1. To merge the file-based user registry, run the following command:
```
BPM_home\bin\BPMMergeFileRegistry.bat -backupFolder snapshot_folder -propertiesFile migration_properties_file
```
  where snapshot_folder is the directory in which the extracted information is stored and migration_properties_file is the full path to the migration properties file in which you specified the configuration information for the target environment.
2. If you have not done so already, update the migration.properties file to specify the configuration information for the target environment. The migration.properties file is found in the BPM_home\util\migration\resources\migration.properties folder.
Disable the automatic starting of all applications and schedulers in the target environment by running the following command:
```
BPM_home\bin\BPMManageApplications.bat -autoStart false -target -propertiesFile migration_properties_file
```
where:
- migration_properties_file is the full path to the migration properties file in which you specified the configuration information for the target environment.
- -target specifies that the command will disable the target environment.
This command ensures that no new events or processes enter the system before you are ready.
Start the deployment manager in the target environment.
Start the nodes.
Important: If you have an environment with the Business Space component (for Process Portal) installed on multiple managed nodes in a cell, start only one node first and start the other nodes only after the first node has already started.
Start the clusters.
Check to make sure that all clusters, servers, and messaging engines have started.