Taking a snapshot of the source
Take
a snapshot of your source environment to extract information such
as configuration customizations, applications, LTPA keys, and service
integration bus (SIB) messages. 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
For each deployment environment in your source environment, complete the following steps:
Results
Depending on your environment,
you might see some of the following folders under your snapshot_folder/cell_name:
Folder | Contents |
---|---|
Adapters | Adapter configurations at the application level |
Applications | WebSphere® Application Server applications and HTM_PredefinedTask system applications |
BLAs and CompositionUnits | Assets used by business-level applications |
Configurations |
|
Messages | Service integration bus (SIB) messages that have not yet been processed in the source environment |