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 procedures

Migrating z/OS stand-alone servers

You can migrate a stand-alone environment. The migration process does not automatically back up the files on the source server, so it is good practice to back up the files on the source server before running the migration.


Procedure

  1. Stop the V7.5, 7.0, or 6.2.0 server.
  2. Back up the IBM BPM database. If necessary, you can recover the V7.5, 7.0, or 6.2.0 data later.
  3. Generate the WebSphere Application Server migration jobs from the z/OS Migration Management Tool component of the WebSphere Customization Toolbox application.

  4. In the IBM BPM product file system, go to the DATASET directory; for example, /was/V8IMbpm3/DATASET. Locate the sample IBM BPM migration jobs named BPZWMG1B, BPZWMG2B, and BPZWMG3B, and take a copy.

    The BPZWMG1B and BPZWMG2B jobs are required only if you had XA Connectors installed on the V7.5, 7.0, or 6.2.0 server. The BPZWMG3B job is mandatory and performs the actual migration.

  5. Edit your copy of the sample jobs to make use of the parameters generated in the previous step by the WebSphere Customization Toolbox panels.
  6. Back up the files on the source IBM BPM server.
  7. Migrate the server. The migration process populates a temporary backup directory using the information it finds in the file system of the source server, and then uses this temporary backup directory to update the file system of the target server. Use the following procedure to migrate the server:

    1. If XA connectors were installed on the V7.5, 7.0, or 6.2.0 server, run the BPZWMG1B and BPZWMG2B jobs.

    2. Run the BPZWMG3B job.

      The BPZWMG3B job runs the wbimgrt2.sh script, which starts the BPMSnapshotSourceProfile.sh and BPMMigrateProfile.sh migration utilities. As part of wbimgrt2.sh processing, the WebSphere Application Server profile is also migrated.

  8. Verify the migration. The migration process produces numerous diagnostic log files that must be checked, including the following files:

    • All of the log files in the /tmp/migration/nnnnnn directory that you specified in the migration job.

    • The log files in the migrated server logs directory; for example: /WebSphere/V8T2Z1/AppServer/profiles/default/logs. In the event of failure, these log files provide details.

    Important: Most of these files are generated as ASCII files, so you must convert them to EBCDIC if you want to view them from TSO. If the tools that you use to view, edit, and run the scripts require the scripts to be in EBCDIC format, use the iconv command to convert the file to EBCDIC.

    For example:

    iconv –t IBM-1047 –f ISO8859-1 WASPreUpgradeSummary.log > 
      WASPreUpgradeSummary_EBCDIC.log  

    The profile migration is now complete.

  9. Upgrade the product databases.

    Databases configured for a stand-alone environment are automatically updated as part of starting the server in the following scenarios:

    1. Common database: The database user configured for the Common database has the needed permissions.
    2. Business Process Choreographer: The environment is not using the default table spaces for the Business Process Choreographer database.

      If the standalone environment is using the sample Business Process Choreographer configuration, or if all of the database objects in the default table spaces specified in the sample SQL scripts have been created, the database uses the default table spaces. This is typically the case for a test environment.

      The database user that is configured for the BPEDB data source is not authorized to perform all of the following operations:

      • Create and alter tables

      • Create and drop indexes and views
      • Query, update, delete, and insert (for the table SCHEMA_VERSION)

    In all other scenarios, the product databases must be upgraded manually. See Manually upgrading the product databases.

    Review the following notes:

    • If you are migrating from version 7.0, it is not necessary to perform a schema upgrade for the Common database. Refer to Migrating databases. Refer to Databases for the database permissions needed to perform schema upgrades.

    • If the source version is 7.0.x, see step 10 to migrate the Business Space database schema. Business Space combines the schema upgrade and data migration into one procedure. However, if your source version is 7.5.x, there are no additional or specific steps required to migrate Business Space data.

    • The Common Event Infrastructure database and Messaging Engine database are automatically migrated by the runtime migration procedure when the profiles are migrated. See Databases. Migrate the messaging engine database if it is needed for your environment. To learn more about when and how to migrate the messaging engine, see Migrating a messaging engine based on a data store in the WebSphere Application Server information center.

  10. Migrate the instance data for Business Space and Business Process Choreographer if it is configured in the source environment.

    Perform one of the following steps to update the data in the databases to work with V8.0.1:

  11. Configure the additional features for IBM BPM V8.0 (for example, Business Process Definitions), because these are not configured during the runtime migration procedure:

    1. Configure a server or cluster as a Process Server or a Performance Data Warehouse by executing the BPMConfigureProcessServer command, following the procedure in the topic Configure the Process Server and Performance Data Warehouse.

    2. Configure the Process Server components using the procedure described in the topic Configure a Process Server.

    3. Configure the Performance Data Warehouse using the procedure described in the topic Configure the Business Performance Data Warehouse component on a server or cluster.

  12. If you have used the same procnames for your source and target servers, update the started task JCL members in USER.PROCLIB by running the BBODCPY1 job from the jcl library that was generated during the installation process of your WebSphere Application Server target server. This job replaces the V7.5, 7.0, or 6.2.0 started task members with the new V8.0.1 members.

  13. Start the target server.


Results

The stand-alone environment is migrated to the target version.


What to do next

Verify that the migration was successful.

Runtime migration procedures


Related tasks:

Stopping stand-alone servers
Verifying migration