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.sh -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.
Ensure that the started task members reference the V8.5 file systems by completing the following steps:
1. Replace the started task members for the deployment manager and the managed nodes in your PROCLIB library with the corresponding V8.5 ones by running the following jobs that were created earlier by the z/OS Profile Management Tool:
  - BBODPROC for the deployment manager
  - BBOMPROC for the managed nodes
2. Edit the members in the PROCLIB library to ensure that the correct DB2 libraries are being used. For each node, edit the adjunct and servant started task members. For the deployment manager, edit only the servant member. For example:
```
//STEPLIB DD DISP=SHR,DSN=SYS2.DB2.V10.SDSNEXIT
// DD DISP=SHR,DSN=SYS2.DB2.V10.SDSNLOAD
// DD DISP=SHR,DSN=SYS2.DB2.V10.SDSNLOD2
```
Start the deployment manager in the target environment.
Federate the nodes into the network deployment cell, and start the node agents. For more information, see Federating the empty node into the deployment manager cell.
Define new application servers as members of the cluster, and add them to the managed nodes. For more information, see Adding cluster members.
Go to the target_BPM_home/util/dbUpgrade directory and set the database.is.db2zos property to true in the upgrade.properties file. For example:
```
database.is.db2zos=true
```
To upgrade the databases to V8.5, run the DBUpgrade utility.
Important: Ensure that your deployment manager and all the managed nodes in the source environment have been stopped before running this utility.
```
BPM_home/bin/DBUpgrade.sh -propertiesFile migration_properties_file -backupFolder snapshot_folder
```
where:
- migration_properties_file is the full path to the migration properties file in which you specified the configuration information for the target environment. Ensure that the value of the target.config.property.file property is set to the full path of the configuration properties file that you used to create your target environment. You must also set the value of profile.name.
- snapshot_folder is the directory that contains the information that was extracted from the source environment
For example:
```
BPM_home/bin/DBUpgrade.sh -propertiesFile /opt/BPM85/util/migration/resources/migration.properties -backupFolder /tmp/snapshot
```
If you are migrating from 7.5.x and you get an out-of-memory error indicating too many or too large data records, you can try to increase the heap size of the JVM for the DBUpgrade command, or decrease the value of database.batch.size (the size of the records to be updated as a batch) in the following file: BPM_home/util/dbUpgrade/upgrade.properties. This example shows how to change the heap size of the JVM for the DBUpgrade command:
```
JVM_HEAPSIZE_OPTIONS="-Xms512m -Xmx768m"
$JAVA_EXE $JVM_HEAPSIZE_OPTIONS -cp $CLASSPATH
```
Stop the deployment manager in the target environment.
Disable the automatic starting of all applications and schedulers in the target environment by running the following command:
```
BPM_home/bin/BPMManageApplications.sh -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.