IBM WebSphere Process Server, Version 6.0, Release Notes

(C) Copyright International Business Machines Corporation 2005, 2006. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

This document contains release notes for:

Description
Supported hardware and software
Important installation and upgrade information
   Upgrading to version 6.0.2
   Upgrading to version 6.0.1
   Installation and configuration information
Updates, limitations, and known problems
   Version 6.0.2
   Version 6.0.1
   Version 6.0.0
IBM Software Support

Description

Based on service-oriented architecture (SOA) and as a single, simplified programming model, WebSphere Process Server, version 6.0, is the next-generation business process server that delivers and supports all styles of integration based on open standards to automate business processes that span people, workflows, applications, systems, platforms, and architectures.

New in WebSphere Process Server, version 6.0.2:

New in WebSphere Process Server, version 6.0.1:

New in WebSphere Process Server, version 6.0:

Base applications

For WebSphere Application Server Network Deployment-related information, see the release notes for that product.

Announcement letters

Supported hardware and software

For supported hardware and software requirements for, see WebSphere Process Server detailed system requirements.

Important installation and upgrade information

Upgrading to WebSphere Process Server, Version 6.0.2

You can upgrade from any version of 6.0.1.0 through 6.0.1.4 to version 6.0.2. You cannot upgrade directly to 6.0.2 from version 6.0.0.x. However, you can upgrade from 6.0.0.x to 6.0.1, and then upgrade from 6.0.1 to 6.0.2.

During the installation of the version 6.0.2 Refresh Pack, the runtime configuration of WebSphere Process Server must be updated. The procedures to do this for stand-alone servers, for Network Deployment environments, and for minimum downtime of clustered environments are described below.

Stand-alone profiles
Network Deployment environment, no clusters
Network Deployment environment, clusters
Network Deployment environment, clusters (minimum downtime)

Stand-alone profiles

For each installation that contains only stand-alone profiles:
  1. Stop all of the application servers.
  2. Install the version 6.0.2 Refresh Pack on the installation that contains the stand-alone profiles.
  3. Restart all of the application servers.

Network Deployment environment, no clusters

  1. Stop the deployment manager.
  2. Install the version 6.0.2 Refresh Pack on the deployment manager's installation.
  3. Start the deployment manager.
  4. For each federated node that is not based off the same installation as the deployment manager, follow these steps:
    1. Stop all servers (application servers and node agents).
    2. Install the version 6.0.2 Refresh Pack on the node's installation. If the message "INSTCONFPARTIALSUCCESS" is returned, check the <install_root>/logs/wbi/WbiProfileUpgrade.log file for errors. If there is an error, fix the cause (most likely, the connection to the deployment manager cannot be established).
      1. On the federated node (not on the deployment manager), change directories to <install_root>/util.
      2. For each profile with an error in WbiProfileUpgrade.log: Depending on the platform, run one of the following commands:
        • Windows: ..\bin\wsadmin -profileName <profileName> -f WbiProfileUpgrade.jacl
        • UNIX and Linux: ../bin/wsadmin.sh -profileName <profileName> -f WbiProfileUpgrade.jacl
          where <profileName> is the name of the profile.
    3. Restart all servers of the node.

Network Deployment environment, clusters

For instructions concerning minimum downtime during cluster upgrade, refer to Network Deployment environment, clusters (minimum downtime).
  1. Stop the deployment manager.
  2. Install the version 6.0.2 Refresh Pack in the deployment manager's installation.
  3. Start the deployment manager.
  4. For each cluster, follow these steps:
    1. Stop all cluster members.
    2. Install the version 6.0.2 Refresh Pack on all installations that host cluster members. If you receive a "INSTCONFPARTIALSUCCESS" message, check the <install_root>/logs/wbi/WbiProfileUpgrade.log file for errors. If there is an error, fix the cause (most likely, the connection to the deployment manager cannot be established)
      1. On the cluster member installation, change directories to <install_root>/util.
      2. For each profile with an error in WbiProfileUpgrade.log: Depending on the platform, run one of the following commands:
        • Windows: ..\bin\wsadmin -profileName <profileName> -f WbiProfileUpgrade.jacl
        • UNIX and Linux: ../bin/wsadmin.sh -profileName <profileName> -f WbiProfileUpgrade.jacl
          where <profileName> is the name of the profile.
      3. On the deployment manager, change directories to <install_root>/util.
      4. Depending on the platform, run one of the following commands:
        • Windows: ..\bin\wsadmin -profileName <profileName> -cluster <clusterName> -f WbiProfileUpgrade.jacl
        • UNIX and Linux: ../bin/wsadmin.sh -profileName <profileName> -cluster <clusterName> -f WbiProfileUpgrade.jacl
          where <profileName> is the name of the deployment manager's profile, and <clusterName> is the name of the cluster.
      5. Restart all cluster members.

Network Deployment environment, clusters (minimum downtime)

The following instructions assume a distributed clustered environment that needs to be updated with minimum downtime of the application servers involved. These instructions assume a sample setup that may need to be adapted to your environment:
  1. Stop the deployment manager.
  2. Install the version 6.0.2 Refresh Pack on the deployment manager's installation.
  3. Start the deployment manager.
  4. For each cluster, follow these steps:
    1. Stop the first half of cluster members (for example, if you have two members, stop one).
    2. Install the version 6.0.2 Refresh Pack on the corresponding installations. Do not restart the servers at this point. If the message "INSTCONFPARTIALSUCCESS" is returned, check the <install_root>/logs/wbi/WbiProfileUpgrade.log file for errors. If there is an error, fix the cause (most likely, the connection to the deployment manager cannot be established).
      1. On the cluster member installation, change directories to <install_root>/util.
      2. For each profile with an error in WbiProfileUpgrade.log: Depending on the platform, run one of the following commands:
        • Windows: ..\bin\wsadmin -profileName <profileName> -f WbiProfileUpgrade.jacl
        • UNIX and Linux: ../bin/wsadmin.sh -profileName <profileName> -f WbiProfileUpgrade.jacl
          where <profileName> is the name of the profile.
    3. Stop the second half of cluster members. There is a short downtime which cannot be avoided.
    4. On the deployment manager, change directories to <install_root>/util.
    5. Depending on the platform, run one of the following commands:
      • Windows: ..\bin\wsadmin -profileName <profileName> -cluster <clusterName> -f WbiProfileUpgrade.jacl
      • UNIX and Linux: ../bin/wsadmin.sh -profileName <profileName> -cluster <clusterName> -f WbiProfileUpgrade.jacl
        where <profileName> is the name of the deployment manager's profile, and <clusterName> is the name of the cluster.
    6. Restart the cluster members of those nodes where version 6.0.2 Refresh Pack has been installed.
    7. Install the version 6.0.2 Refresh Pack on the installations of the remaining cluster members and restart each one after the installation.

Upgrading to WebSphere Process Server, Version 6.0.1

Before you upgrade from WebSphere Process Server, version 6.0.0 to version 6.0.1, read this important information:

Installation and configuration information

Refer to the following Web sites for installation and configuration information for all versions of WebSphere Process Server:

WebSphere Process Server Information Center
PDF version of installation instructions for WebSphere Process Server
WebSphere Process Server support information

Refer to the following sites for updated version-specific installation and configuration information for WebSphere Process Server:

WebSphere Process Server, version 6.0.2

This link provides WebSphere Process Server technotes, and WebSphere Enterprise Service Bus technotes that are also applicable to WebSphere Process Server:

View the latest information and critical fixes for WebSphere Process Server, version 6.0.2

WebSphere Process Server, version 6.0.1

This link provides WebSphere Process Server technotes, and WebSphere Enterprise Service Bus technotes that are also applicable to WebSphere Process Server:

View the latest information and critical fixes for WebSphere Process Server, version 6.0.1

WebSphere Process Server, version 6.0.0

View the latest information and critical fixes for WebSphere Process Server, version 6.0.0

Updates, limitations, and known problems

Updates, limitations, and known problems about WebSphere Process Server, are documented in the form of technotes on the IBM Software Support Web site at http://www.ibm.com/software/integration/wps/support.

As limitations and problems are discovered and resolved, the IBM Software Support team updates the knowledge base. By searching the knowledge base, you can quickly find workarounds or solutions to problems that you experience. The following link launches a customized query of the live Support knowledge base. To create your own query, go to the Advanced search page on the IBM Software Support Web site:

WebSphere Process Server, version 6.0.2

These links provide WebSphere Process Server technotes, and WebSphere Enterprise Service Bus technotes that are also applicable to WebSphere Process Server:

View update, limitation, and problem notes for WebSphere Process Server, version 6.0.2
View the latest information and critical fixes for WebSphere Process Server, version 6.0.2

WebSphere Process Server, version 6.0.1

These links provide WebSphere Process Server technotes, and WebSphere Enterprise Service Bus technotes that are also applicable to WebSphere Process Server:

View update, limitation, and problem notes for WebSphere Process Server, version 6.0.1
View the latest information and critical fixes for WebSphere Process Server, version 6.0.1

WebSphere Process Server, version 6.0.0

View update, limitation, and problem notes for WebSphere Process Server, version 6.0.0
View the latest information and critical fixes for WebSphere Process Server, version 6.0.0

IBM Software Support

IBM Software Support provides assistance with product defects. This section describes the IBM Support Assistant tool, how to contact IBM, and how to get help from IBM.

Note: To submit problems to IBM Software Support, you must have an active software maintenance contract. See Contacting IBM Software Support for information.

IBM Software Support provides assistance with product defects. If you encounter a problem with WebSphere Process Server, Version 6.0, follow these steps:

  1. Download and launch IBM Support Assistant and search the support information for a solution.
  2. If you cannot find the information you need, submit the problem to IBM using the Service component of IBM Support Assistant or by contacting IBM Software Support.

    Note: To submit problems to IBM Software Support, you must have an active software maintenance contract. See Contacting IBM Software Support for information.

IBM Support Assistant

WebSphere Process Server, version 6.0, includes IBM Support Assistant, a tool that helps you use various IBM Support resources from within the offering. It includes the following components to help you with software questions:

IBM Support Assistant, version 3.0, is a stand-alone utility. It includes an installation program and a user guide. Follow these steps to use IBM Support Assistant:

  1. Download and install IBM Support Assistant from the IBM Support Assistant download page.

    Some IBM products include IBM Support Assistant on the installation media. For the latest information on IBM Support Assistant, see the IBM Support Assistant technote on the IBM Software Support site.

  2. Start IBM Support Assistant from the Start menu on Windows(R) operating systems or with the startisa.sh command on all other platforms.

    On Windows operating systems, IBM Support Assistant opens in its own window. On all other platforms, it opens in a Web browser.

  3. Download and install an IBM Support Assistant plug-in for WebSphere Process Server:
    1. Click Find Plug-ins to view search links that can be used to find plug-ins for specific IBM products.
    2. Select WebSphere to initiate a search for all WebSphere product plug-ins.

      This list is also available from the IBM Support search page.

    3. Select WebSphere Process Server to open the download page for the plug-in.
    4. Download and install the plug-in.

To learn more about how to use the IBM Support Assistant, click the User Guide tab in the IBM Support Assistant window.

Contacting IBM Software Support

If you cannot resolve the problem using IBM Support Assistant, contact IBM. However, before you submit a problem to IBM Software Support (through IBM Support Assistant or directly), ensure that your company has an active IBM software maintenance contract, and that you are authorized to submit problems to IBM. The type of software maintenance contract that you need depends on the type of product you have:

If you are not sure what type of software maintenance contract you need, call 1-800-IBMSERV (1-800-426-7378) in the United States. From other countries, go to the "Contacts" page of the IBM Software Support Handbook at http://techsupport.services.ibm.com/guides/contacts.html and click the name of your geographic region for phone numbers of people who provide support for your location.

Submitting a problem report to IBM Software Support

To submit a problem to IBM, first determine the business impact of the problem and gather background information about it. The background information helps IBM Software Support representatives find a solution more quickly. The following sections guide you through the tasks for submitting a problem.

Determine the business impact of the problem

When you report a problem to IBM, you are asked to supply a severity level. Therefore, you need to understand and assess the business impact of the problem that you are reporting. Use the following criteria to determine the severity level:

Severity level Description
Severity 1 The problem has a critical business impact: You are unable to use the program, resulting in a critical impact on operations. This condition requires an immediate solution.
Severity 2 This problem has a significant business impact: The program is usable, but it is severely limited.
Severity 3 The problem has some business impact: The program is usable, but less significant features (not critical to operations) are unavailable.
Severity 4 The problem has minimal business impact: The problem causes little impact on operations, or a reasonable circumvention to the problem was implemented.

Describe the problem and gather background information

When describing a problem to IBM, be as specific as possible. Include all relevant background information so that IBM Software Support specialists can help you solve the problem efficiently. To save time, know the answers to these questions:

Submit the problem

You can submit your problem to IBM Software Support in one of two ways:

If the problem you submit is for a software defect or for missing or inaccurate documentation, IBM Software Support creates an Authorized Program Analysis Report (APAR). The APAR describes the problem in detail. Whenever possible, IBM Software Support provides a workaround that you can implement until the APAR is resolved and a fix is delivered. IBM publishes resolved APARs on the Software Support Web site daily, so that other users who experience the same problem can benefit from the same resolution.