Profile upgrade instructions for WebSphere Process Server and WebSphere Enterprise Service Bus V7.0.0 Fix Pack 3 (V7.0.0.3) installations with existing profiles

Product readme


Abstract

This document provides instructions for upgrading to IBM WebSphere Enterprise Service Bus and IBM WebSphere Process Server, Version 7.0.0 Fix Pack 3 (V7.0.0.3)

Content



This document provides instructions for upgrading existing profiles to IBM WebSphere Enterprise Service Bus and IBM WebSphere Process Server, Version 7.0.0 Fix Pack 3 (V7.0.0.3)


Table of Contents



Common steps for all configurations

Attention notice: Installation Manager on Windows XP does not recognize profile update errors. When upgrading an installation on Windows XP, you must look at the Identifying Profile Update Errors section, even if Installation Manager ended with the message: "The packages are updated".
  1. Back up existing profiles in WebSphere Enterprise Service Bus or WebSphere Process Server.

    This fix pack updates the core product files and all the existing profiles that require maintenance update.

    Before upgrading an existing installation, run the backupConfig command to back up the configuration files of each profile that the fix pack can update. See Backing up and restoring administrative configurations in the Information Center for more information about running this command.

  2. (WebSphere Process Server only) Back up default XSL transformation files

    If you have applied any changes to the following default XSL transformation files located in the <install_root>/ProcessChoreographer/Staff directory you should back them up before installing V7.0.0 Fix Pack 3 (V7.0.0.3) on WebSphere Process Server:
    • EverybodyTransformation.xsl
    • LDAPTransformation.xsl
    • SystemTransformation.xsl
    • UserRegistryTransformation.xsl
    • VMMTransformation.xsl
      These files will be overwritten during the installation of V7.0.0 Fix Pack 3 (V7.0.0.3) and the changes applied to these files will be lost.

      After you have upgraded your installation and before you start the server or a cluster, replace the XSL transformation files with the backup version.

  3. Stop all the Java processes

    Before installing V7.0.0 Fix Pack 3 (V7.0.0.3), stop all Java processes associated with Java SDK shipped with WebSphere Process Server, including the node agent process, the Deployment Manager process, and all server processes that belong to serviceable products, such as the IBM HTTP Server.

    Note: The product might not continue to run successfully if you install V7.0.0 Fix Pack 3 (V7.0.0.3) while a WebSphere Application Server-related Java process is running.

  4. (For Windows Servers only) Stop the WebSphere Windows services

    WebSphere Application server fix pack installation might update the WASServiceMsg.dll file. If any of the WebSphere servers (including node agents and Deployment Manager) are configured to start automatically using Windows services, the WASServiceMsg.dll file gets locked by the Microsoft Windows operating system.

    If you see a "WASServiceMsg.dll file can not be replaced" error during the fix pack installation of WebSphere Application Server, you should change the starting option for all the WebSphere services so that they start manually and you should restart the Windows server before installing the WebSphere Application Server fix pack.

    Refer to the WASServiceMsg.dll is locked when installing fix packs Technote for details.

  5. (WebSphere Process Server only) Remove old versions of the predefined human tasks:
    The Business Process Choreographer predefined human task applications will be updated during the installation of WebSphere Process Server V7.0.0 Fix Pack 3 (V7.0.0.3). If Business Process Choreographer is configured in your environment, after successfully installing WebSphere Process Server V7.0.0 Fix Pack 3, follow step 4 of Postmigration tasks for Business Process Choreographer to remove the old version of the predefined human tasks.

  6. (WebSphere Process Server only) Work item sharing for existing Business Process Choreographer configuration:
    WebSphere Process Server Version 7.0.0.3 introduces work item sharing, which provides a more efficient handling of work items. If you have problems with query performance or the size of the WORK_ITEM_T table, consider migrating to using shared work items. To be able to use shared work items, you must perform a database migration on the existing work items. Refer to the information center for details about activating support for shared work items and the restrictions that apply.

Steps for upgrading a stand-alone environment

For each stand-alone profile, perform the following steps:
  1. Back up the configuration and stop the stand-alone server following the common steps instructions above.

  2. Install V7.0.0 Fix Pack 3 (V7.0.0.3) using either IBM Installation Manager or silent installation as explained in the fix pack installation instructions.


    Note: The stand-alone profile is automatically updated during fix pack installation and no additional steps are required to update the profile.

  3. Check for any errors as explained in the Identifying Profile Update Errors section before continuing.

  4. Restart the stand-alone application server.
Steps for upgrading in a network deployment environment

Notes and restrictions when upgrading in a network deployment environment

When upgrading from V7.0.0.2 or earlier V7.0.0 releases in a network deployment environment, some additional steps must be completed. Perform the appropriate steps for your environment.
  • If minimum downtime is the objective during this upgrade, special precautions should be taken. These are documented separately in Clustered servers in a network deployment environment where minimum downtime is required during the upgrade.

  • The Deployment Manager has to be the highest level in the cell. Upgrade the installation that contains the deployment manager before upgrading the nodes.

  • In a cluster where Business Process Choreographer is configured, cluster members at different versions cannot be started at the same time.

    • You must stop all members at the older version before starting any of the upgraded members.

    • After an upgraded member has been started you must no longer start ‘old' members.

  • You must not upgrade more than one installation at a time.

  • The Deployment Manager should be up and running when managed nodes are upgraded. This is necessary because the fix pack installer must connect to the central configuration repository on the Deployment Manager to make the updates.

    Note: The only exception to this rule is for managed nodes hosted by the same installation as their Deployment Manager profile. The managed node configuration will be updated as part of the Deployment Manager profile in this scenario.




Security-enabled network deployment environments

When you apply the fix pack in a network deployment environment where WebSphere administrative security is enabled, the connection to the deployment manager requires a user ID and password to be supplied. The IBM Installation Manager does not prompt for these credentials when you start updating an installation containing managed profiles. However, depending on your configuration, you may have to enter the credentials in a separate prompt near the end of the upgrade process.

Note: The credential panel appears twice during the upgrade process, and has a default timeout period of one minute. If you miss this prompt, or your security configuration is set up such that no prompt is displayed, or if you are running the silent installation script, follow the instructions in the Identifying Profile Update Errors section.

For more information on how to configure security for WebSphere administration scripts (which the WebSphere Process Server scripts depend on), see Configuring security with scripting in the WebSphere Application Server Information Center.




Upgrading the Deployment Manager

  1. Back up your configuration.

  2. Stop all the Java processes associated with the WebSphere Process Server installation as documented in the common steps instructions above.

  3. Install V7.0.0 Fix Pack 3 (7.0.0.3) on to the Deployment Manager’s installation using either IBM Installation Manager or silent installation, as explained in the fix pack installation instructions. The Deployment Manager profile is automatically updated during fix pack installation.

  4. Check for any errors, as explained in the Identifying Profile Update Errors section, before continuing.





Upgrading managed nodes
  1. Start the Deployment Manager. The Deployment Manager must be running when you apply the fix pack to an installation with a managed profile.

    Note: The only exception to this rule is for managed profiles hosted by the same installation as their Deployment Manager profile. The managed node configuration will be updated as part of the Deployment Manager profile in this scenario and a separate log file is not written.

    Skip step 2 in this section for managed nodes which are hosted by the same installation as their Deployment Manager.


  2. Perform the following steps if the managed profile is hosted by an installation other than its Deployment Manager profile:

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

    2. Install V7.0.0 Fix Pack 3 (V7.0.0.3) using either the IBM Installation Manager or silent installation as explained in the fix pack installation instructions.


      Note: When applying the fix pack in a network deployment environment where WebSphere administrative security is enabled, the connection to the Deployment Manager requires a user ID and password. Depending on your configuration you may have to enter the credentials in a separate prompt near the end of the update process. Please refer to Security enabled network deployment environments for details.


      The managed node (profile) is automatically updated during fix pack installation.
      Log files are saved as :<profile_root>/logs/BPMProfileUpgrade.<profileName>.<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, before continuing.

  3. 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. Follow step 2a of Updating Business Space templates and spaces after installing or updating widgets. Do not perform the node synchronization and server restart until you have read the following steps.

  4. If any of the nodes contain cluster members, follow the steps described under Upgrading Clusters before starting the servers.

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

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

  7. Start all the servers and cluster members as needed.




Upgrading clusters :

After upgrading the Deployment Manager and all the managed nodes containing cluster members, follow these steps to upgrade each of the clusters in your network deployment environment before starting the cluster members (servers).

Note: If minimum downtime is the objective during this upgrade, special precautions should be taken. These are documented separately in Clustered servers in a network deployment environment where minimum downtime is required during the upgrade.

  1. Stop the Deployment Manager now, if it is running.

  2. On the Deployment Manager change directories to <install_root>.

  3. Depending on the platform, run one of the following commands for each cluster:

    On Windows:
    bin\ws_ant.bat -f util\BPMProfileUpgrade.ant -profileName <profileName> -Dupgrade=true –Dcluster=<clusterName>

    On UNIX and Linux:
    bin/ws_ant.sh -f util/BPMProfileUpgrade.ant -profileName <profileName> -Dupgrade=true –Dcluster=<clusterName>

    where <profileName> is the name of the Deployment Manager’s profile and <clusterName> is the name of the cluster.

  4. Check the following log file for errors: <profile_root>/logs/BPMProfileUpgrade.<profileName>.<clusterName>.<timestamp>.log where <profile_root> is the root directory of the Deployment Manager’s profile.


    If there is an error, fix the cause, then rerun step 3.

  5. If Business Space is configured on the cluster, manual steps are required for updating existing Business Space templates and spaces. Follow steps 1a and 1b of Updating Business Space templates and spaces after installing or updating widgets. Do not perform the node synchronization and server restart until you have read the following steps.

  6. When all clusters have been successfully upgraded, restart the Deployment Manager.

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

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

  9. Start all the servers and cluster members as needed.



Identifying profile update errors

If an error message "The packages are updated with warnings" is displayed on the Installation Manager summary panel (GUI installation) or on the command line (silent installation), check the log file <install_root>/logs/wbi/install .FP7003 /installconfig_wps_profileMaintenance.log.
If it contains the message Result of executing [...]BPMProfileMaintenance.ant was: false
then a profile update error has occurred.
If multiple profiles in the installation are being updated, search for the first occurrence of "profileName=" prior to the error to know which profile this error is associated with.

Fix the cause, then follow the appropriate steps in the Recovering after profile update errors section.

When upgrading an installation on Windows XP, you must check the installconfig_wps_profileMaintenance.log file, even if the Installation Manager reported that the packages are updated.

Note: For network deployment environments the most likely cause of an error is that a connection to the Deployment Manager cannot be established.



Recovering after profile update errors


Stand-alone profiles and Deployment Manager profiles
  1. Make sure the stand-alone application server or the Deployment Manager is stopped.

  2. Change directories to <install_root> where the profile update error has occurred and run one of the following commands as appropriate for your platform.

    On Windows:
    bin\ws_ant.bat -f util\BPMProfileUpgrade.ant -profileName <profileName> -Dupgrade=true

    On UNIX and Linux:
    bin/ws_ant.sh -f util/BPMProfileUpgrade.ant -profileName <profileName> -Dupgrade=true

    Where <profileName> is the name of the stand-alone profile or Deployment Manager profile that had update errors.




Federated profiles
  1. Make sure the Deployment Manager has been started. This is necessary because the BPMProfileUpgrade.ant script must connect to the central configuration repository on the Deployment Manager to make the updates.

  2. Change directories to <install_root> where the profile update error has occurred and run one of the following commands as appropriate for your platform:

    On Windows:
    bin\ws_ant.bat -f util\BPMProfileUpgrade.ant -profileName <profileName> -Dupgrade=true

    On UNIX and Linux:
    bin/ws_ant.sh -f util/BPMProfileUpgrade.ant -profileName <profileName> -Dupgrade=true

    where <profileName> is the name of the federated profile that had update errors.

    If you are updating a federated node when WebSphere administrative security is enabled, you must also supply the “-Duser=<userID> -Dpassword=<password>” parameters, where <userID> is a user ID from the user registry that has administration authority and <password> is the password for that user ID.

Rolling back V7.0.0 Fix Pack 3

You can use the IBM Installation Manager for WebSphere Software to roll back this fix pack.

If you roll back the fix pack, the IBM Installation Manager does not roll back fix pack updates from profiles because you may have configured the profile after installing the maintenance.

Warning: Profiles may not be usable after rolling back the fix pack.

To restore an original profile, use the restoreConfig command to restore your backup.

Before running the restoreConfig command, export any custom enterprise applications that you have installed since you ran the backupConfig command. After running the restoreConfig command, re-install the exported enterprise applications and redo any other applicable configuration changes that you made since you ran the backupConfig command.


Additional information

You can find additional information on any of these topics in the WebSphere Process Server or the WebSphere Enterprise Service Bus Information Centers. For more information about the update strategy or to obtain updates to WebSphere Process Server or WebSphere Enterprise Service Bus, see the Recommended Fixes pages for WebSphere Process Server and WebSphere Enterprise Service Bus .





Trademarks and service marks:

For trademark attribution, visit the IBM Terms of Use Web site.


Cross reference information
Segment Product Component Platform Version Edition
Business Integration WebSphere Enterprise Service Bus Install AIX, HP-UX, Linux, Linux iSeries, Linux pSeries, Linux xSeries, Linux zSeries, Solaris, Windows 7.0.0.3

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

WebSphere Process Server
Installation & Configuration

Software version:

7.0.0.3

Operating system(s):

AIX, HP-UX, Linux, Solaris, Windows

Reference #:

7019233

Modified date:

2010-09-03

Translate my page

Machine Translation

Content navigation