Taking a snapshot of the source

Take a snapshot of your source environment to extract information such as configuration customizations. You will import this snapshot to the target environment in a later step.

Figure 1. Sample environment after the source is shut down for migration. The source environment can still read from the databases but can no longer write to them. The target is not running but contains a stand-alone environment.

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

Before you begin

Ensure that the stand-alone server has been started.

About this task

Run the BPMExtractSourceInformation utility to take a snapshot of your previous environment so that you can apply the same changes to your new environment.

Important: If you decide to make configuration changes to the source environment based on your configuration in the new installation, remember that you must run the utility again to take a new snapshot.

Procedure

If you have not done so already, update the migration properties file with the configuration information for the source environment. You need a different migration properties file for each deployment environment. Check all the properties and edit them if required, following the instructions in the file.
- If you installed the new version of the product on the same computer as the source environment, the file is found in BPM_home_8.5/util/migration/resources/migration.properties.
- If you installed the new version of the product on a different computer and copied the migration files to the source environment, the file is found in remote_migration_utility/util/migration/resources/migration.properties.
Optional: Update other configuration files in the BPM_home_8.5\util\migration\resources directory, following the instructions in the files.
- Update the logging.properties file to specify where information is logged during the extraction process.
- Update the soap.client.props file to change the com.ibm.SOAP.requestTimeout property if the SOAP invocation is timing out at the current setting.
- Update the ssl.client.props file to change the keystore and truststore.
Do not update any of the other files.
Take a snapshot of the source environment.
- If you installed the new version of the product on the same computer as the source environment, run the following command in the target environment:
```
BPM_home_8.5/bin/BPMExtractSourceInformation.sh -backupFolder snapshot_folder -propertiesFile migration_properties_file
```
- If you installed the new version of the product on a different computer and copied the migration files to the source environment, run the following command on the source computer:
```
remote_migration_utility/bin/BPMExtractSourceInformation.sh -backupFolder snapshot_folder -propertiesFile migration_properties_file
```
where:
- snapshot_folder is the directory where the extracted information is stored.
- migration_properties_file is the full path to the migration properties file in which you specified the configuration information for the source environment.
For example:
```
BPMExtractSourceInformation -backupFolder /tmp/snapshot -propertiesFile /opt/BPM85/util/migration/resources/migration.properties
```
Note: If you receive an SSL Signer Exchange Prompt message while running this command, click Y to add the signer to the truststore.
A log location will appear at the end of the command prompt. If there are any errors or exceptions, they will appear in that log. If you have any errors and need to rerun this step, you must remove all contents from the directory you identified with the -backupFolder parameter in the command.
Shut down the source environment before you proceed with the migration.

Results

Depending on your environment, you might see some of the following folders under your snapshot_folder/cell_name:

Table 1. Contents of snapshot folder
Folder	Contents
Configurations	The PerformanceTuningParameters.properties file that you can use to complete your target configuration manually if required Security configurations such as fileRegistry.xml file (if you use a file-based user registry) The process-center(process-server) and performance-data-warehouse folders that contain merged customization files. If XML customization files such as 100Custom.xml and 101Custom.xml exist in the source, the BPMExtractSourceInformation command merges them into a single file named 100SourceCustomMerged.xml.