IBM BPM, V8.0.1, All platforms > Migrating and upgrading your IBM BPM environment > Upgrading from IBM BPM V8.0 to IBM BPM V8.0.1 > Upgrading an ND environment

Upgrading managed nodes

Complete these steps to upgrade managed nodes in a ND environment.


Procedure

To upgrade managed nodes:

  1. Start the dmgr. The dmgr must be running when you apply the refresh pack to an installation with a managed profile.

    The only exception to this rule is for managed profiles that are hosted by the same installation as their dmgr profile. The managed node configuration is updated as part of the dmgr profile in this scenario and a separate log file is not written.

    Skip Step 2 in this section for managed nodes that are hosted by the same installation as their dmgr.

  2. Complete the following steps if the managed profile is hosted by an installation other than its dmgr profile:

    1. Ensure that all the servers and their node agents are stopped.

    2. Install the refresh pack by using either the IBM Installation Manager or the silent installation method. Refer to the technote Update Instructions for V8.0.1 for the IBM BPM (BPM) products, which contains specific instructions for using both the IBM Installation Manager graphical user interface (GUI) and the silent installation methods to install Refresh Pack V8.0.1.

      When you perform the upgrade in an ND environment, the connection to the dmgr requires a user ID and password because WebSphere administrative security is enabled. Depending on your configuration you might have to enter the credentials in a separate prompt near the end of the update process. Refer to the security information in the "Upgrading an ND environment" topic for details.

      The managed node (profile) is automatically updated during refresh pack installation. Log files are saved as: profile_root/logs/BPMProfileUpgrade. profile_name. timestamp.log where profile_root is the root directory of the managed profile.

    3. Check for any errors as explained in the "Identifying Profile Update Errors" section of Recovering from profile update errors before continuing.

      Attention: The Installation Manager on the Microsoft Windows XP operating system does not recognize profile update errors. When you upgrade an installation on the Windows XP operating system, you must look at the "Identifying profile update errors" section of Recovering from profile update errors, even if Installation Manager ended with the following message: "The packages are updated".

  3. Complete the following steps for the managed profile:

    1. Ensure that all the servers and their node agents are stopped.

    2. Install the new version of IBM BPM as described in Obtaining and installing the product code.
    3. Manually update the profile as follows:
      1. Verify that the dmgr has been started. This step is necessary because the BPMProfileUpgrade.ant script must connect to the central configuration repository on the dmgr to make the updates.

      2. From the INSTALL_ROOT directory:

        bin/ws_ant.sh -f util/BPMProfileUpgrade.ant -profileName profile_nameĀ -Dupgrade=true -Duser= userID -Dpassword= password

        where profile_name is the name of the federated profile (which for z/OS is default), userID is a user ID that has administration authority, and password is the password for that user ID.

  4. Before you update the databases, ensure that you have applied Mandatory Interim Fix JR44669. See Required interim fix for APAR JR44669. To download the fix, see Required interim fixes for IBM BPM.
  5. Non-clustered environments only: Update the Process Server database for each non-clustered server where the Business Process Definition engine is configured.

    • If you are using DB2 on z/OS, you must manually alter a set of table spaces and upgrade the database schema before you upgrade the database data:

      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:

        • WLPT36
        • WLPT44
        • WLPT64

        For information about altering table spaces, see

      2. From the INSTALL_ROOT/profiles/ profile_name/dbscripts/ProcessServer/DB2zOS/ database_name directory, copy the script named upgradeSchema800_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@. Then connect to the DB2 for z/OS database, and run the script against the database by using your preferred tool.

      3. From the INSTALL_ROOT/profiles/ profile_name/dbscripts/PerformanceDW/DB2zOS/ database_name directory, copy the script named upgradeSchema800_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.

      4. Go to the [IBM_BPM_home]/BPM/Lombardi/tools/upgrade/UpgradeProcessData directory and set the database.is.db2zos property to true in the upgrade.properties file.

        For example:

        database.is.db2zos=true

      5. To update the Process Server database:

        • BPM\Lombardi\tools\upgrade\UpgradeProcessData\upgradeProcessData.bat -profileName profile_name -nodeName node_name -serverName server_name
        • BPM/Lombardi/tools/upgrade/UpgradeProcessData/upgradeProcessData.sh -profileName profile_name -nodeName node_name -serverName server_name

        where profile_name is the name of the dmgr profile, and node_name and server_name are the node name and server name of the Process Server that needs the database upgrade. For more information about the parameters that you can use with the upgradeProcessData command, see upgradeProcessData command-line utility.

    • For all other database types to update the Process Server database:

      • BPM\Lombardi\tools\upgrade\UpgradeProcessData\upgradeProcessData.bat -profileName profile_name -nodeName node_name -serverName server_name
      • BPM/Lombardi/tools/upgrade/UpgradeProcessData/upgradeProcessData.sh -profileName profile_name -nodeName node_name -serverName server_name

      where profile_name is the name of the dmgr profile, and node_name and server_name are the node name and server name of the Process Server that needs the database upgrade. For more information about the parameters that you can use with the upgradeProcessData command, see upgradeProcessData command-line utility.

    If Performance Data Warehouse is configured on a different server, for example, when using one of the "Remote Support" topology patterns, you must also supply the -perfNodeName pdw_node_name and -perfServerName pdw_server-name parameters, where pdw_node_name and pdw_server-name are the node name and server name of the Performance Data Warehouse server.

  6. Non-clustered environments only: If you have configured Business Process Choreographer, you must upgrade the BPEDB database manually to create the SCHEMA_STATUS table.

    1. Change to the directory where the Business Process Choreographer database scripts are generated. Run the following command on the installation that hosts the dmgr:

      • cd profile_root\dbscripts\ProcessChoreographer\ db_type\ db_name\ schema_name
      • cd profile_root/dbscripts/ProcessChoreographer/ db_type/ db_name/ schema_name

      where profile_root is the root directory of the dmgr profile, db_type is the database type, db_name is the database name, and schema_name is the (possibly empty) schema name.

    2. If the database server is remote and you do not have a local database client, copy the upgradeSchema_SchemaStatus.sql script to the database server so that you can run it there.

    3. Run the upgradeSchema_SchemaStatus.sql script to create the SCHEMA_STATUS table in the Business Process Choreographer database. If the table already exists, there will be an error that you can ignore.
  7. Non-clustered environments only: If Business Space is configured on a non-clustered server on this node, manual steps are required for updating existing Business Space templates and spaces. Perform the following steps:

    1. In the custom profile where the managed server is located, open the custom_profile_root\BusinessSpace\ node_name\ server_name\mm.runtime.prof\public\oobLoadedStatus.properties file and update the importTemplates.txt or importSpaces.txt properties:
      importTemplates.txt=true
      importSpaces.txt=true

    2. If you have created the Business Space database after it was deleted, or if you need to reload the theme for any other reason, update the following property:
      importThemes.txt=true

  8. If any of the nodes contain cluster members, upgrade the clusters as described in Upgrading clusters.

    If your environment does not contain a cluster, go to step 9.

  9. For each node, restart the node agent and wait for the node synchronization to complete.

  10. If you have disabled automatic synchronization, ensure that all your nodes are correctly synchronized before starting the cluster members.

  11. Start all the servers and cluster members, as needed.

Upgrading an ND environment


Related concepts:
Topologies of a ND environment


Related tasks:
Upgrading an ND environment
Executing SQL upgrade scripts


Related reference:
Recovering from profile update errors