Extracting data source information from the source environment

Optionally, extract the data source information from your source environment so that you can make the same changes in the new version while you create the deployment environment. Using this information ensures that you can access the previous databases from your new deployment environment.

Figure 1. Sample environment after V8.5 is installed on the target. The source environment is running and transferring data to and from its databases. The target has been created but does not contain a deployment environment.

For each deployment environment in your source environment, complete the following steps:

1. Update the migration properties file with the configuration information for the source 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.
   For each deployment environment, you must use a different migration properties file where you assign values to the following parameters:

   • source.application.cluster.name
   • source.support.cluster.name
   • source.messaging.cluster.name
   • source.web.cluster.name

   These cluster name parameters must have different values between deployment environments. However, within the same migration properties file, the values can be the same. If you are migrating from a stand-alone environment, leave the cluster name parameters empty.
   If you are migrating from a two-cluster environment, enter values for the application and messaging cluster names, for example:

   • source.application.cluster.name=ApplicationCluster
   • source.support.cluster.name=
   • source.messaging.cluster.name=MessagingCluster
   • source.web.cluster.name=

   In addition, you must specify values for the following parameters in each file:

   • admin.username
   • admin.password
   • bpm.home
   • profile.name
2. 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.
3. Extract the database configuration from 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/BPMExtractDBConfiguration.sh -output output_properties_file -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/BPMExtractDBConfiguration.sh -output output_properties_file -propertiesFile migration_properties_file

   where:
   • output_properties_file is the file name, including the full path, for the database configuration information. The properties are extracted into this file as name-value pairs. Make sure that the file does not already exist. If you are running this command more than once because you have more than one deployment environment, remember to specify different output file names.
   • migration_properties_file is the full path to the migration properties file in which you specified the configuration information for the source environment (the file that you updated in Step 1).
   Note: If you receive an SSL Signer Exchange Prompt message while running this command, click Y to add the signer to the truststore.
   For example:
   

   BPMExtractDBConfiguration -output /tmp/db_config -propertiesFile /tmp/remoteUtil/util/migration/resources/migration.properties

   

   BPMExtractDBConfiguration.sh -output /u/working_dir/source_dbconfig.properties -propertiesFile /u/working_dir/util/migration/resources/migration.properties

   If you installed the new version of the product on the same computer as the source environment, the log file is in BPM_home_8.5/logs/migration. 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 in remote_migration_utility/logs/migration.