Migrating a profile to the same version on a remote system (new hardware)

Use this procedure for migrating a server profile to the same version on new hardware.

Procedure

Follow the steps in this procedure to migrate a profile to the remote system.

  1. Optional: Required only for a federated profile. If the profile that is being migrated is a federated profile, synchronize the profile with the new deployment manager.
    1. Obtain the deployment manager host and port number.
    2. Edit the source_node_profile_root/properties/wsadmin.properties file. Change the com.ibm.ws.scripting.host value to the new host. Change the com.ibm.ws.scripting.port value to the new port.
    3. Run the syncNode command from the bin directory. For example:
      For Windows operating system
      source_node_profile_root\bin\syncNode.bat myV8DmgrHost.mycompany.com 8879 -username myuser -password mypass
      For Linux operating systemFor UNIX operating systemThis topic applies only to the z/OS platform
      source_node_profile_root/bin/syncNode.sh myV8DmgrHost.mycompany.com 8879 -username myuser -password mypass
      For more information about manually synchronizing all nodes, see Manually synchronize all nodes in the Websphere Application Server information center.
  2. Snapshot the migration source profile.

    On the migration source system, use the BPMSnapshotSourceProfile command from the bin directory to create a snapshot directory containing the configuration files that will be migrated. Use the -remoteMigration option to indicate that the target profile will not be created on the same machine. This option saves additional configuration information from the source profile that will be used during remote migration.

    For example, to snapshot a source profile named sourceProfile1 located in the ProcServer8010 installation root directory to the /MigrationSnapshots/ProcServer8010 snapshot directory, use the following syntax:

    • For Linux operating systemFor UNIX operating systemBPMSnapshotSourceProfile.sh -remoteMigration true /opt/ibm/WebSphere/ProcServer8010 sourceProfile1 /MigrationSnapshots/ProcServer8010
    • For Windows operating systemBPMSnapshotSourceProfile.bat -remoteMigration true "C:\Program Files\IBM\WebSphere\ProcServer8010" sourceProfile1 c:\MigrationSnapshots\ProcServer8010
    Linux Unix Important: On a UNIX system, ensure that all extracted files have execute permission for the logged-in user. If they do not, use the chmod command to grant execute permission for all extracted files.

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

  3. Copy the migration source snapshot directory to the migration target system.

    Create a compressed file of the source snapshot directory, copy it to the target system, and extract it there.

  4. Create the target profile.

    On the migration target system, create the target profile using the BPMCreateTargetProfile command. This profile will not be ready for use until the BPMMigrateProfile command is used to migrate the source profile to the new target profile.

    For example, to create a target profile for the migration using the source profile named sourceProfile1 that was copied to the /MigrationSnapshots/ProcServer8010 snapshot directory, use the following syntax:

    • For Linux operating systemFor UNIX operating systemBPMCreateTargetProfile.sh -remoteMigration true /MigrationSnapshots/ProcServer8010 sourceProfile1
    • For Windows operating systemBPMCreateTargetProfile.bat -remoteMigration true C:\MigrationSnapshots\ProcServer8010 sourceProfile1

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

  5. Migrate the source profile to the target profile.

    Migrate the source profile to the target profile using the BPMMigrateProfile command. This command will read the configuration information from the snapshot directory specified by the BPMSnapshotSourceProfile command and copied over to the target system, and migrate it to the target profile.

    For example, to migrate the source profile named sourceProfile1 in the /MigrationSnapshots/ProcServer8010 directory to the target profile, use the following syntax:

    • For Linux operating systemFor UNIX operating systemBPMMigrateProfile.sh -username source_profile_user_name -password source_profile_password /MigrationSnapshots/ProcServer8010 sourceProfile1
    • For Windows operating systemBPMMigrateProfile.bat -username source_profile_user_name -password source_profile_password C:\MigrationSnapshots\ProcServer8010 sourceProfile1

    On the Windows operating system, even if security is enabled, the -username and -password parameters do not have to be specified if the server is running as a Windows service. In this case, 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 the BPMMigrateProfile command topic.

  6. Check the migration status.

    Use the BPMMigrationStatus command to verify the current state of the migration.

    • For Linux operating systemFor UNIX operating systemBPMMigrationStatus.sh
    • For Windows operating systemBPMMigrationStatus.bat

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

  7. Scan the file system under the profile directory for occurrences of the old hostname value. Analyze the configuration where the old hostname is still being used and replace it with the new hostname, unless the old hostname is needed, such as if the database is still present on the old hostname machine.

Results

The profile is migrated from an earlier version of IBM® Business Process Manager to IBM Business Process Manager V8.0.1 on a remote system.