IBM BPM, V8.0.1, All platforms > Migrating and upgrading your IBM BPM environment > Migrating from previous versions > Migrating your IBM BPM Advanced V7.5.x or WebSphere Process Server V7.x or V6.2.x runtime > Runtime migration subprocedures

Migrating a profile using the command-line utilities

Use this procedure for migrating a profile using the command-line utilities.

See Migrating a stand-alone environment, Migrating an ND environment with full downtime, and Migrating an ND environment with minimal downtime.


Procedure

Follow these steps to migrate a profile using the command-line utilities.

  1. Optional: Extract the application deployment configuration.

    If you have applications that use WebSphere Adapters, extract the application deployment configuration using the BPMQueryDeploymentConfiguration command from the target_INSTALL_ROOT/bin directory.

    The user-specified snapshot directory should not be located in the source or target product installation directories, so those directories can be removed later if necessary without impacting the configuration files in the snapshot directory.

    Use the following syntax to extract the deployment configuration for a source profile named sourceProfile1 located in the ProcServer620 installation root directory to the /MigrationSnapshots/ProcServer620 snapshot directory:


    The BPMQueryDeploymentConfiguration command generates ApplicationMigrationInformation.xml to the following directory: <snapshot directory>/profiles/ <profile name>

    Edit the file ApplicationMigrationInformation.xml to mark which WebSphere Adapter instances to update to the new version during runtime migration. See step 2 for information on editing ApplicationMigrationInformation.xml.

    For more information about the BPMQueryDeploymentConfiguration command, see BPMQueryDeploymentConfiguration command-line utility.

  2. Optional: Edit the XML file that contains the application deployment configuration.

    If you extracted the application deployment configuration as described in step 1, edit the ApplicationMigrationInformation.xml file to mark the WebSphere Adapter instances to update to the new version during runtime migration.

    1. Locate the ApplicationMigrationInformation.xml file.

      ApplicationMigrationInformation.xml resides in the following directory: <snapshot directory>/profiles/ <profile name>

    2. Edit the ApplicationMigrationInformation.xml file.

      Edit the value in <update> from "false" to "true" to update a specific WebSphere Adapter instance to the new version. Copy the new version RAR file of the WebSphere Adapter being marked for update into the following directory: INSTALL_ROOT/installableApps.

      Set the <update> true for any application that embeds WebSphere Adapter for SAP or WebSphere Adapter for SAP instances configured at Node or Cluster scope.

      CAUTION:

      If the WebSphere Adapter deployed at node level is used to configure the WebSphere Adapter at cluster scope, the update of the WebSphere Adapter must be applied in a consistent manner. If the WebSphere Adapter at cluster scope needs to be updated to the new version, the corresponding instance of WebSphere Adapter defined at each individual node scope for nodes that are participating in the cluster must be updated as well. Failure to perform the WebSphere Adapter update in a consistent manner for participating nodes and cluster level can lead to failures of applications using WebSphere Adapter instance. For more information on mapping of a cluster-scoped WebSphere Adapter to a node scope WebSphere Adapter, refer to Configure Resource Adapters in the WebSphere Application Server information center.

  3. Optional: Required if a custom resource that relies on third-party libraries, such as a custom MQ JMS provider, is configured in the source environment. The dependent third-party libraries will not be migrated, so you must copy them to the target environment manually in order to make the custom resource work correctly in the target environment.

    For a side-by-side migration:

    1. If the dependent third-party libraries are in a folder under <WAS_INSTALL_ROOT> in the source environment, copy them to the same folder under <WAS_INSTALL_ROOT> in the target environment.

    2. If the dependent third-party libraries are in a folder outside <WAS_INSTALL_ROOT> in the source environment, make sure they are in the same location in the target environment after migration.

    For a remote migration:

    No matter where the dependent third-party libraries are placed in the source environment, copy them to the same folder in the target environment.

    If you are migrating from a Windows system to a Linux or UNIX system, or from a Linux or UNIX system to a Windows system, besides copying the third-party libraries to the target environment, you must also modify the configuration of the custom resource so that it refers to the correct location of the libraries, because of the different file path formats of the operating systems.

  4. Create a copy of the source profile.

    Create a copy of the configuration files in the source profile that will be migrated to the target profile using the BPMSnapshotSourceProfile command from the target_INSTALL_ROOT/bin directory. The user-specified snapshot directory should not be located in the source or target product installation directories, so those directories can be removed later, if necessary, without impacting the configuration files in the snapshot directory.

    If the dmgr profile and node profile are on the same system, put the migration snapshots in separate directories.

    Use the following syntax to copy a source profile named sourceProfile1 located in the ProcServer620 installation root directory to the /MigrationSnapshots/ProcServer620 snapshot directory:

    For more information about the BPMSnapshotSourceProfile command, see BPMSnapshotSourceProfile command.

  5. Create the target profile.

    Create the target profile using the BPMCreateTargetProfile command from the target_INSTALL_ROOT/bin directory. This profile will not be ready for use until the BPMMigrateProfile command is used from the target_INSTALL_ROOT/bin directory to migrate the source profile to the new target profile.

    Use the following syntax to create a target profile for the migration using the source profile named sourceProfile1 copied to the /MigrationSnapshots/ProcServer620 snapshot directory:

    For more information about the BPMCreateTargetProfile command, see BPMCreateTargetProfile command.

  6. Migrate the source profile to the target profile.

    Migrate the source profile to the target profile using the BPMMigrateProfile command from the target_INSTALL_ROOT/bin directory. This command reads the configuration information from the snapshot directory specified by the BPMSnapshotSourceProfile command and migrates it to the target profile.

    Use the following syntax to migrate the source profile named sourceProfile1 copied into the /MigrationSnapshots/ProcServer620 directory to the target profile:

    If the source profile has security enabled, the -username and -password parameters are required. The user name provided must be a member of the operator or administrator role.

    On Windows, even if security is enabled, you do not need to specify the -username and -password parameters if the server is running as a Windows service, because the parameters are automatically passed into the script that the Windows service uses to shut down the system.

    For more information about the BPMMigrateProfile command, see BPMMigrateProfile command.

    CAUTION:

    On Solaris 64-bit operating systems, to avoid OutOfMemory errors during profile migration, determine whether the default JVM heap size of 768 MB will work. Depending on the number of applications that are part of the profile being migrated, this parameter might need adjustment. Use the -javaoption of the BPMMigrateProfile command-line utility to override the default value and specify a custom value for JVM heap size.

  7. Check the migration status.

    Use the BPMMigrationStatus command from the target_INSTALL_ROOT/bin directory to verify the current state of the migration. Use the following syntax:

    For more information about the BPMMigrationStatus command, see BPMMigrationStatus command.


Results

The profile is migrated from an earlier version of IBM BPM to IBM BPM V8.0.1.


What to do next

Verify that the migration was successful. For instructions, see Verifying migration.

Runtime migration subprocedures