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. You need
one snapshot for each deployment environment in your source cell.
You do not need a separate snapshot per profile from your source cell.
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 deployment environment.
Before you begin
If the source environment
is a network deployment environment, ensure that the deployment manager,
node agent, and clusters have been started. If the source environment
is a stand-alone environment, 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 modified the 100Custom.xml file
for Process Server or Performance Data Warehouse, make sure that the 100Custom.xml files
on the managed node are in sync with the 100Custom.xml files
on the deployment manager. If not, manually copy the 100Custom.xml files
from the node profile to the deployment manager profile.
You
must perform this step because the BPMExtractSourceInformation utility
reads the 100Custom.xml file from the deployment
manager profile only. The utility extracts the 100Custom.xml files
for Process Server and Performance Data Warehouse from the deployment
manager profile to the snapshot folder.
All customized .xml files
in the \config and \config\system folders
are merged, and 100SourceCustomMerged.xml files
are created in snapshot_folder\cell_name\Configurations\process-center (or process-server)
and snapshot_folder\cell_name\Configurations\performance-data-warehouse.
The XML files are merged in a sequence where those starting with a
letter of the alphabet are merged before those that start with numbers,
which are merged in numeric order. For more information about which
files are merged and the sequence that is used, see the comments in 100SourceCustomMerged.xml.
- 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.
where:
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. If you have a network deployment environment:
- Stop the clusters.
- Stop the nodes.
- Stop the deployment manager.
Results
Depending
on your environment, you might see some of the following folders under
your
snapshot_folder/cell_name: