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 a z/OS ND environment

Migrating a cluster

After you have migrated your dmgr and managed nodes, complete a number of cluster-related tasks before you can start the migrated servers.


Procedure

  1. Migrate the cluster-scoped configuration information. From the WAS_HOME/profiles/ profile_name/bin directory on the target dmgr node, run the BPMMigrateCluster.sh script by using the following syntax:

    • Migrate all clusters found on the dmgr node:

      BPMMigrateCluster.sh -all snapshot_directory dmgr_target_profile_name

    • Migrate a single cluster:

      BPMMigrateCluster.sh snapshot_directory cluster_name dmgr_target_profile_name

    where snapshot_directory is the snapshot directory of the dmgr profile, cluster_name is the name of a cluster, and dmgr_target_profile_name is the dmgr profile.

    For example, for a single cluster:

    cd /WebSphere/V8T8DM/DeploymentManager/profiles/default/bin

    ./BPMMigrateCluster.sh /tmp/migrate/PN9dmgr/dmgr_backup PN9Cluster1 default

    For more information about this command and its parameters, see BPMMigrateCluster command-line utility.

  2. Configure the additional features that are not configured during the runtime migration procedure:

    • If the source version is 6.x or 7.0.x, configure the Process Server, Performance Data Warehouse, and Process Portal in the cluster by following the procedure in Configure the Process Server and Performance Data Warehouse.

    • If the source version is 7.5.0.1, configure Process Portal in the cluster by running the BPMConfigureProcessServer command from the WAS_HOME/profiles/ profile_name/bin directory.

      For example:

      cd /WebSphere/V8T8DM/DeploymentManager/profiles/default/bin

      ./BPMConfigureProcessServer.sh -dbDesign /u/dbutil/v80/bpm.dmgr.T1.dbDesign -processPortalClusterName WCLT1Z1 -appClusterName WCLT1Z1

      For more information about this command and its parameters, see BPMConfigureProcessServer command-line utility.

  3. Synchronize all of the migrated nodes that participate in the cluster. For each migrated node in the cluster, run the syncNode command from the WAS_HOME/bin directory.

    For example:

    cd /WebSphere/V8T3N1/AppServer/bin

    ./syncNode.sh dmgr_host_name dmgr_soap_port_number

    When prompted, enter the authentication details of a user (for example, wsadmin) that has the permission required to update the server configuration. These authentication details are required if security is enabled.

    To verify that the command ran successfully, you can review the log file, which is saved to WAS_HOME/profiles/default/logs/syncNode.log by default. For more information about the syncNode command, see Runtime migration tools reference.

  4. If you are migrating from IBM BPM V7.5.0.1, upgrade the Process Server and Performance Data Warehouse databases by completing the following steps:

    1. To ensure that you can successfully run the SQL files for the DB2 for z/OS schema upgrade, alter the following table spaces to increase the buffer pool size to 8K:

      • WLPT33
      • WLPT52

      For information about altering table spaces, see

    2. Upgrade the database schema:

      1. From the INSTALL_ROOT/profiles/ profile_name/dbscripts/ProcessServer/DB2zOS/ database_name directory, obtain the upgradeSchema_ProcessServer.sql script that corresponds to the product version you are migrating from.

        For example, if you are migrating from IBM BPM V7.5.0.x, copy the script named upgradeSchema750_ProcessServer.sql to your working directory.

        Review the script, and, if necessary, edit the file to replace the following symbolic variables with the actual values for the schema name, database name, storage group, and buffer pool for large objects and tables: @SCHEMA@, @DB_NAME@, @STOGRP@, @BPLOB4K@, @BPTABLE4K@, and @BPTABLE8K@.

        Locate the two CREATE PROCEDURE statements in the upgradeSchema750_ProcessServer.sql script, and cut and paste these statements into a new text file with a .sql extension. In this new file, also include the DB2 --#SET TERMINATOR @ control statement to set the SQL terminator to the @ character, as required for stored procedures. Save your amendments to the .sql scripts.

        Connect to the DB2 for z/OS database, and run the upgradeSchema750_ProcessServer.sql script against the database by using your preferred tool. For a V7.5.0.x migration, also run the newly-created .sql script to create the stored procedures.

      2. From the INSTALL_ROOT/profiles/ profile_name/dbscripts/PerformanceDW/DB2zOS/ database_name directory, obtain the upgradeSchema_PerformanceDW.sql script that corresponds to the product version you are migrating from.

        For example, if you are migrating from IBM BPM V7.5.0.x, copy the script named upgradeSchema750_PerformanceDW.sql to your working directory.

        Review the script, and, if necessary, edit the file to replace the following symbolic variables with the actual values for the schema name, database name, storage group, and buffer pool for large objects and tables: @SCHEMA@, @DB_NAME@, @STOGRP@, @BPLOB4K@, @BPTABLE4K@, and @BPTABLE8K@. Then connect to the DB2 for z/OS database, and run the script against the database by using your preferred tool.

    3. Upgrade the database data:

      1. Go to the IBM_BPM_home/BPM/Lombardi/tools/upgrade/UpgradeProcessData directory.

        For example:

        cd /usr/lpp/zWebSphere/V8R0/BPM/Lombardi/tools/upgrade/UpgradeProcessData

      2. In the upgrade.properties file, set the database.is.db2zos property to true.

        For example:

        database.is.db2zos=true

      3. To update the Process Server database, run the upgradeProcessData.sh command against one of the cluster servers. You need only run the script once against a single cluster server by using the following syntax:

        upgradeProcessData.sh -wasHome WAS_HOME -profileName profile_name -nodeName node_name -serverName server_name

        where:

        • WAS_HOME is the top directory for the WebSphere Application Server node.
        • profile_name is the name of the dmgr profile.
        • node_name is the name of any cluster node.
        • server_name is the name of the Process Server that needs the database upgrade.

        For example:

        ./upgradeProcessData.sh -wasHome /WebSphere/V8T8DM/DeploymentManager -profileName default -nodeName t1node1 -serverName WZT1Z1

        For more information about the parameters that you can use with the upgradeProcessData command, see upgradeProcessData command-line utility.

  5. Migrate the instance data for Business Space 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:

: Migrating a z/OS ND environment


Previous topic: Migrating a managed node