Installing IBM Business Process Manager Version 8.6 Cumulative Fix 2017.12

This cumulative fix is a cumulative maintenance package that applies to all distributed operating systems. It is a single package that bundles a number of individual fixes.

The cumulative fix is to be used on IBM Business Process Manager Express, IBM Business Process Manager Standard, IBM Business Process Manager Advanced, or IBM Business Process Manager Advanced - Process Server Version 8.5.7, or IBM Business Process Manager Express Server or IBM Business Process Manager Server Version 8.6.

To upgrade Process Federation Server, see Downloading IBM Process Business Process Manager - Process Federation Server Version 8.6.

Table of Contents

• Problems addressed in this upgrade
• Installation instructions
• Upgrade prerequisites
• Installing the upgrade
• Downloading the repositories to the local system
• Upgrading an installation interactively
• Upgrading an installation silently using the command line (imcl)
• Rolling back the upgrade
• Rolling back the installation interactively
• Rolling back the installation silently using the command line (imc)
• Rolling back IBM Process Designer
• Reference
• Trademarks and service marks

© Copyright International Business Machines Corporation 2017. All rights reserved.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Problems addressed in this upgrade

By installing this upgrade, you will raise the fix level of your product to Version 8.6 CF2017.12.

The fixes addressed in this upgrade are explained in the Fix list for the IBM Business Process Manager Version 8.6 products.

Installation instructions

Upgrade prerequisites

To install this upgrade, you must have Version 8.5.0.0, Version 8.5.0.1, Version 8.5.0.2, Version 8.5.5.0, Version 8.5.6.0, Version 8.5.6.0 CF01, Version 8.5.6.0 CF02, Version V8.5.7.0, Version 8.5.7 CF2016.06, Version 8.5.7 CF2016.09, Version 8.5.7 CF2016.12, Version 8.5.7 CF2017.03, Version 8.5.7 2017.06, or Version 8.6 of IBM Business Process Manager Express, IBM Business Process Manager Standard, IBM Business Process Manager Advanced, or IBM Business Process Manager Advanced - Process Server, IBM Business Process Manager Express Server, or IBM Business Process Manager Server installed.

Important:

• Before you install, if you have any of these interim fixes installed:
• Interim fix JR52730 on IBM BPM V8.5.0.1
• Interim fix JR52393 on IBM BPM V8.5.0.0, V8.5.0.1, V8.5.5.0, or V8.5.6.0
• Interim fix JR50538 on IBM BPM V8.5.5.0
• Interim fix JR49893 on IBM BPM V8.5.0.1
see WebSphere Application Server or IBM Business Process Manager upgrade might fail with 'The system cannot find the path specified' errors.

If you have this interim fix installed:
• Interim fix JR51926 on IBM BPM V8.5.5.0
  see Upgrading from IBM Business Process Manager V8.5.5 fails with "Can not delete file 'C:\IBM\BPM855 exp\BPM\Lombardi\process-server\applications\Teamworks.ear'"
• If you are on a UNIX or Linux system, make sure that you check the ulimit setting. See Preparing Linux systems for installation or Preparing AIX systems for installation.
• If you are upgrading from V8.5.x, you must add a local IBM BPM V8.6 delta repository into Installation Manager or upgrade the installation binary to V8.6 before you upgrade to this cumulative fix.
• Installing this upgrade requires WebSphere Application Server V8.5.5, Fix Pack 12 or a later version.
• Installing this upgrade requires IBM WebSphere SDK Java Technology Edition Version 8.0 (Java 8).
  Note: WebSphere Application Server Version V8.5.5.9 and later support Java 8. Before you install Java 8, make sure your WebSphere Application Server is V8.5.5.9 or later.
  Tip: Save an extra manual step by installing Java 8 before or at the same time as you install IBM BPM V8.6.
• To avoid problems such as certificate issues, ensure you have IBM Installation Manager V1.8.6 (the minimum level required is V1.8.0). You can obtain links to the latest versions from Installation Manager and Packaging Utility download links.

Hardware and software prerequisites for IBM Business Process Manager and for IBM Business Process Manager Express are available on the web on their respective detailed system requirements pages.

Installing the upgrade
To install the upgrade, follow these instructions to download the fix pack repositories, choose your installation path, and review the post-upgrade tasks.

1. Download the fix pack repository to a local directory. For more information, see Downloading the repositories to the local system. If you are installing the fix pack interactively by using IBM Installation Manager to connect to the live repository, this step is not required.
   
   
2. Choose one of the installation paths based on your environment.
1. If you have an existing IBM BPM deployment environment, follow the instructions based on your current version:
• If you are upgrading from IBM BPM V8.6, complete the steps in Upgrading profiles from V8.6.
• If you are upgrading from IBM BPM V8.5.0.x, V8.5.5, V8.5.6.x, or V8.5.7.x, complete the steps in Upgrading profiles from V8.5.x.
• If you are migrating from a version earlier than IBM BPM V8.5.0.x, use Installation Manager to install the upgrade, but do not create profiles or a deployment environment. After installing the upgrade, follow the migration instructions to migrate your earlier version.
  
  Note: To continually run production applications during the upgrade and regression test period, you can roll out maintenance incrementally in an IBM BPM installation that consists of a Process Center and multiple Process Servers. See Performing a rolling upgrade in the product documentation. Also, see Testing the IBM Business Process Manager upgrade for methods to find potential upgrade problems.
  
  
2. If you are installing IBM BPM V8.6 CF2017.12 in a new environment, include the cumulative fix with the IBM BPM V8.6 repository from Passport Advantage while installing the product. For more information, see the Interactive Installation and Configuration Guide.
   
   Note: If you are using the launchpad to install and you have Internet access, you can include the cumulative fix from the live repository during installation. Otherwise, you must install the upgrades from a local directory. For example, for a typical installation on Windows, you could add fixpack.BPM_CF=local_repository_path to bpm_updates.properties to include the cumulative fix, as described in step 1 of Installing and configuring Process Center in the product documentation.
   
   
3. If you installed IBM BPM V8.5.0.x, V8.5.5, V8.5.6.x, V8.5.7.x, or V8.6 but you have not yet created a deployment environment, choose one of the following options to update the product:
   Upgrading an installation interactively
   Upgrading an installation silently using the command line (imcl)
   
   
3. Review the optional post-upgrade task information for additional actions you might need to take.

Your IBM Business Process Manager installations are now V8.6 CF2017.12.

You will see "8.6.0.201712" in the versionInfo command output, the SystemOut.log header, and the administrative console Welcome screen. For information about determining the installed version, see Product version and history information.


Downloading the repositories to the local system
Download the upgrade repositories to a local directory so that they can be used with Installation Manager during the upgrade process.
Notes:

• If you are installing interactively by using Installation Manager to make the updates and you have Internet access, you do not need to download the required WebSphere Application Server fix pack and IBM BPM cumulative fix from Fix Central.
• New installations require the IBM BPM V8.6 installation media, as noted in the IBM Knowledge Center for IBM BPM.
  
  

1. Download the cumulative fix repository by following the Downloading document. Download bpm.8600.cf2017.12.delta.repository.zip to a temporary disk location.
   
   
2. You must have WebSphere Application Server V8.5.5, Fix Pack 12 or later installed or you must install it during the upgrade process. To upgrade the WebSphere Application Server fix pack, download the applicable version for your environment.
   For example, download 8.5.5-WS-WAS-FP012-part1.zip, 8.5.5-WS-WAS-FP012-part2.zip, and 8.5.5-WS-WAS-FP012-part3.zip for WebSphere Application Server V8.5.5.12. Ensure that all the files are extracted to the same root directory; for example, staging_directory\WAS85512.
   For information about the fixes and download links, see Fix list for IBM WebSphere Application Server V8.5.
   
   
3. You must have IBM WebSphere SDK Java Technology Edition Version 8.0 (Java 8) and the required fix PI73197: Enable Java 8 Support for EJBDeploy on WebSphere Application Server installed or you must install them during the upgrade process. Download the 8.0.x.x-WS-IBMWASJAVA-platform repository for your operating system. For example, download the 8.0.4.5-WS-IBMWASJAVA-Win.zip repository for a Windows operating system.
   
   
4. Install the latest security fixes for WebSphere Application Server V8.5.5.12:
1. Edge Caching Proxy may be vulnerable to HTTP response splitting:
   http://www.ibm.com/support/docview.wss?uid=swg22006815
2. Multiple vulnerabilities affect Java Server Faces (JSF):
   http://www.ibm.com/support/docview.wss?uid=swg22008707
3. Multiple vulnerabilities in IBM Java SDK:
   http://www.ibm.com/support/docview.wss?uid=swg22010560
4. Ship Java 8 SR5 FP5 for WebSphere Application Server traditional and Liberty:
   http://www.ibm.com/support/docview.wss?uid=swg24044232
5. Information disclosure in WebSphere Application Server:
   http://www.ibm.com/support/docview.wss?uid=swg22004792
   
5. Download any required interim fixes from IBM Fix Central that are specific to IBM BPM V8.6 CF2017.12. Select your installation type and 8.6.0.201712 to search for recommended fixes on this site. Download all recommended fixes.
   Note: Upgrading will remove any previously installed interim fixes. If a fix is included in the upgrade, then you do not have to reinstall the interim fix.
   
   
6. Extract each set of cumulative fix or interim fix repository zip files to its own local directory, although a common staging directory can be used. For example, staging_directory\BPMcumfix, staging_directory\WAS, or staging_directory\IFix1.
   Note: If a repository consists of multiple .zip files, ensure that they are all extracted to the same root directory. For example, extract the three 8.5.5-WS-WAS-FP012 files to staging_directory\WAS85512. Because the cumulative fix consists of a single .zip file, you can point Installation Manager directly to the .zip file without extracting it.
7. Return to the installation instructions and continue with the appropriate steps based on your existing setup.

Upgrading an installation interactively
These steps upgrade one installation of IBM BPM. If you have an existing IBM BPM deployment environment, follow the profile upgrade steps first. Ensure that these steps are followed only after you are directed here by the profile upgrade steps.

1. Start IBM Installation Manager. For more information about where Installation Manager is installed and the type of installation, see Installation directories for the product and profiles.
   Note: Installation Manager must be at a minimum level of Version 1.8.0 before you start the upgrade. Installation Manager detects an available update if you are connected to the Internet on the workstation where you plan to upgrade.
   
   
• On Windows, right-click IM_INSTALL_LOCATION\IBMIM.exe and select Run as administrator.
  
  
• On Linux or UNIX, start Installation Manager using the IM_INSTALL_LOCATION/IBMIM command.
  
  
2. Add the repositories to the Installation Manager preferences. Click File > Preferences. Under Repositories, select one of the following options:
• If you have Internet access, ensure that the Search service repositories during installation and updates option is selected.
  Important: If you are upgrading from V8.5.x, make sure you add a local V8.6 delta repository into Installation Manager or upgrade the installation binary to V8.6 before you proceed.
  
  
• If you do not have Internet access, add the location of the local repositories that you downloaded in the Downloading the repositories to the local system section.
1. Click Add Repository.
   
   
2. Type or browse to the repository.config file for the repository that you extracted and click OK. If the fix consists of a single .zip file, you can just point to the .zip file.
   
   
3. Repeat steps a. and b. for all new repositories that you downloaded in the Downloading the repositories to the local system section.
   
   
4. Click OK to save the new repository settings.
   
   
3. If you have not yet installed Java 8, click Install. Select the version of IBM WebSphere SDK Java Technology Edition that you want to install. Click Next. Select the package group where you installed IBM BPM V8.5.x and click Next. On the Summary panel, click Install to install Java 8.
   
   
4. Click Update. Select the package group where you installed IBM BPM V8.5.x or V8.6 and click Next.
   
   
5. After Installation Manager checks the service repositories, the Update Packages window opens and IBM Business Process Manager or IBM Business Process Manager Express V8.6 2017.12 is shown, unless there is a later fix available from the live update repository. If you are also installing WebSphere Application Server V8.5.5 Fix Pack 12 or later, it is also shown.
   
   
6. Ensure that these repositories are all selected. Clear the Show recommended only check box to make sure that you can see all the added fixes. Click Next. If you have Internet connectivity or have added local repositories, another Update Packages window opens. A list of interim fixes is displayed.
   
   
7. Ensure that the interim fixes are all selected and then click Next.
   Note: Applying this upgrade will remove any previously installed interim fixes. If a fix is included in the upgrade, then you do not have to reinstall the interim fix.
   
   
8. Read and accept the terms of the license agreements by selecting the appropriate button and click Next. The Features window opens. All the installed features will be selected.
   
   
9. Click Next.
   
   
10. Click Next. All the features that need to be updated are shown in the Summary window. The disk space that is required to perform the update is shown at the bottom.
    
    
11. Click Update to start the update. The updates are downloaded either from the live update repository or from your local repository. The updates are installed. After the installation of the updates is complete, you receive a confirmation.
    
    
12. If you included a WebSphere Application Server fix in the upgrade, and you have Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy files installed, they might have been overwritten. If so, reinstall the policy files before continuing. Otherwise, secure connections might fail if, for example, they rely on certain minimum key lengths.
    
    
13. If you have an existing IBM BPM deployment environment, follow the links below to return to the profile upgrade instructions to continue upgrading your profiles. If you want to upgrade additional installations, repeat the steps, or return to step 4 for installations using the same Installation Manager.
• If you are upgrading from V8.6, continue following the profile upgrade instructions from step 8 under Upgrading network deployment profiles or step 7 under Upgrading stand-alone profiles.
• If you are upgrading from V8.5.x, continue following the profile upgrade instructions from step 9 under Upgrading network deployment profiles for IBM Business Process Manager Advanced or IBM Business Process Manager Standard or step 7 under Upgrading stand-alone profiles for IBM Business Process Manager Express.

Upgrading an installation silently using the command line (imcl)
Installation Manager offers a command-line interface to update your product installation silently. These steps upgrade one installation of IBM Business Process Manager. If you have an existing IBM BPM deployment environment, ensure that these steps are followed only after you are directed here by the profile upgrade steps.

1. Gather the following information about your environment and the fixes you want to apply.
   
   
• IM_INSTALL_LOCATION
  The location where Installation Manager is installed. See table 7 in Installation directories for the product and profiles for more information about Installation Manager default installation directories.
• INSTALL_DIR
  The full path to the installation directory of the product you are upgrading.
• REPOSITORIES
  The full directory path to the unpacked repositories associated with each fix package that you are applying. The directories are the local staging directories that you used at the end of the Downloading the repositories to the local system steps.
  If you are installing fixes from multiple repositories, include each directory path and separate them with commas. For example:
  C:\BPMFixStaging\BPMfixpack,C:\BPMFixStaging\WASfixpack,C:\BPMFixStaging\IFix1
• LOG_FILE
  A full path and name for a log file to capture the logging output of the command.
• FIX_PACKAGES
  A list of the package associated with V8.6 CF2017.12 and any refresh pack, fix pack, cumulative fix, or interim fix that you are applying.
  If you are applying multiple fixes, separate them with spaces.
  
  
  For interim fix package IDs, check the readme file for the fix ID. Alternatively, you can run the listAvailablePackages command on a repository to see the fixes that it includes. You will need the currently installed package ID and version, as described in the next paragraph. For information about the command, see Listing available packages by using imcl commands.
  
  
  For a refresh pack, fix pack, or cumulative fix, the package ID depends on the package ID of the product that is already installed. If you are unsure of the exact packages that you have installed, you can use the following command to list the current products associated with a particular installation:
  On Windows: install_root\bin\versionInfo
  On Linux: install_root/bin/versionInfo.sh
  This command lists all products associated with the installation and includes a package output for each. The package line has the package ID followed by an underscore and the version ID.
  
  
  The following table shows the package ID for products that could be installed with IBM BPM:

Product being updated	Package ID
IBM Business Process Manager Express	com.ibm.bpm.EXP.v85
IBM Business Process Manager Standard	com.ibm.bpm.STD.v85
IBM Business Process Manager Advanced	com.ibm.bpm.ADV.v85
IBM Business Process Manager Advanced - Process Server	com.ibm.bpm.PS.v85
WebSphere Application Server	com.ibm.websphere.ND.v85 (or com.ibm.websphere.ND.le.v85 for Little Endian systems)
Java	com.ibm.websphere.IBMJAVA.v80

2. Using the information gathered in the previous step, run the imcl command from the tools directory under the Installation Manager installation location. For more information, see Installing packages by using imcl commands.
   IM_INSTALL_LOCATION/eclipse/tools/imcl install FIX_PACKAGES -acceptLicense -installationDirectory INSTALL_DIR -repositories REPOSITORY -log LOG_FILE
   
   By including the -acceptLicense parameter, you agree to the terms and licenses of this product.
   
   You must add one of these features to the IBM BPM package ID:
   BPMServer.NonProduction - For test, staging, or development use
   BPMServer.Production - For production use
   
   The following command is an example of upgrading IBM BPM Advanced on Windows:
   C:\Program Files (x86)\IBM\Installation Manager\eclipse\tools\imcl install com.ibm.websphere.ND.v85 com.ibm.websphere.IBMJAVA.v80 com.ibm.bpm.ADV.v85,BPMServer.Production -acceptLicense -installationDirectory C:\IBM\BPM\v8.5 -repositories C:\temp\was85512,C:\temp\8.5.5.12-ws-wasnd-ifpi82630.zip;C:\tmp\8.5.5.9-ws-was-ifpi73197.zip;C:\temp\8.0.4.5-WS-IBMWASJAVA-Win.zip,C:\temp\bpm.8600.cf2017.12.delta.repository.zip -log silent_update.txt
   
   
3. When the silent installation completes, check the log files to ensure that the installation completed successfully. A success message that is similar to the following text displays on the command line for each package that was installed:
   Updated to com.ibm.bpm.ADV.v85_8.6.201712.20171211_1726 in the C:\IBM\BPM\v8.5 directory
   
   
4. If you included a WebSphere Application Server fix in the upgrade, and you have Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy files installed, they might have been overwritten. If so, reinstall the policy files before continuing. Otherwise, secure connections might fail if, for example, they rely on certain minimum key lengths.
   
   
5. Repeat the process for each installation in the environment. When you are finished, if you have an existing IBM BPM deployment environment, continue following the profile upgrade instructions.
• If you are upgrading from V8.6, continue following the profile upgrade instructions from step 8 under Upgrading network deployment profiles or step 7 under Upgrading stand-alone profiles.
• If you are upgrading from V8.5.x, continue following the profile upgrade instructions from step 9 under Upgrading network deployment profiles for IBM Business Process Manager Advanced or IBM Business Process Manager Standard or step 7 under Upgrading stand-alone profiles for IBM Business Process Manager Express.

Rolling back the upgrade

Rolling back the upgrade

You can roll back the upgrade by using one of the following options:
Rolling back the installation interactively
Rolling back the installation silently using the command line (imcl)

Note: The following procedure rolls back only the IBM BPM installation. If you have existing profiles and were upgrading from V8.6, see Rolling back the IBM BPM environment for instructions. If you have existing profiles and were upgrading from V8.5.x, see Rolling back the IBM BPM environment for instructions. New profiles created after the upgrade cannot be reused; you must delete and re-create the profiles after you complete the rollback process. See Removing a managed node profile from a deployment environment for more information.


Rolling back the installation interactively

1. Close all programs that were installed by using Installation Manager.
   
   
2. Start Installation Manager. For information about where Installation Manager is installed, see Installation directories for the product and profiles,
   
   
3. From the Start page of the Installation Manager, click Roll back to start the Roll back packages wizard.
   
   
4. On the Roll Back Packages page, from the Package Group Name list, select the package group that contains the packages that you want to roll back and click Next.
   
   Important: On Linux, to avoid problems, do not roll back all packages at once. Roll back IBM BPM, followed by the Java Development Kit (JDK), followed by WebSphere Application Server.
   
   
5. Select the version of the package that you want to roll back to and click Next.
   
   
6. Read the summary information and click Roll Back to roll back the package.
   
   When the rollback process completes, a message that confirms the success of the process is displayed near the top of the page.
   
   
7. Optional: Click View log file to open the log file for the current session in a new window.
   
   
8. Click Finish to close the wizard.
   
   
9. If you are rolling back the IBM BPM environment (profiles and database), reinstall all the previous interim fixes for IBM Business Process Manager and IBM WebSphere Application Server. You must reinstall all the interim fixes that you previously had installed before you upgraded and then rolled back.
   
   
10. Close Installation Manager.
    
    
11. If you have existing profiles, continue with the profile rollback steps for existing environments. For upgrading from V8.6, continue from step 6 in Rolling back the IBM BPM environment. For upgrading from V8.5.x, continue from step 6 in Rolling back the IBM BPM environment.

Warnings displayed during the rollback process
You might see warnings similar to the following warning in the Installation Manager rollback log (install_root/logs/wbi/uninstall/uninstallconfig_server.log):
<message>/opt/IBM/WebSphere/AppServer/properties/version/nif/config.wbi/uninstall.ngi/99SRunISCDeploy.ant:33: exec returned: 127
    at org.apache.tools.ant.taskdefs.ExecTask.runExecute(ExecTask.java:591)
    at org.apache.tools.ant.taskdefs.ExecTask.runExec(ExecTask.java:617)
    at org.apache.tools.ant.taskdefs.ExecTask.execute(ExecTask.java:452)

You can fix them by running the following command:

• On Windows: install_root\bin\iscdeploy -restore
• On Linux or UNIX: install_root/bin/iscdeploy -restore

Rolling back the installation silently using the command line (imcl)

Installation Manager offers a command-line interface to silently roll back your product installation to the previous version. In the instructions, it is assumed that you completed all the necessary backup tasks, which are described in Upgrading profiles from V8.6 or Upgrading profiles from V8.5.x, before you upgraded. The previous profile is restored after you complete the rollback task.

1. Gather the following information about your environment and the target version you want to roll back to.
   
   
• IM_INSTALL_LOCATION
  The location where Installation Manager is installed. See table 7 in Installation directories for the product and profiles for more information about Installation Manager default installation directories.
• INSTALL_DIR
  The full path to the installation directory of the product that you upgraded.
• LOG_FILE
  A full path and name for a log file to capture the logging output of the command.
• PACKAGE_VERSION_IDS
  The package and version IDs for the target version you want to roll back to. You will need the package ID followed by an underscore and the specific version ID. If you are rolling back multiple packages in the installation, separate each package and version ID with a space. If you supply only the package ID, the package is rolled back to the most recent previous version.
  
  To find the IDs of the packages you can roll back to, run this command:
  IM_INSTALL_LOCATION/tools/imcl listInstalledPackages -rollbackVersions  -installationDirectory INSTALL_DIR -log LOG_FILE
• REPOSITORIES
  Optionally, you might need to supply the fix repositories for the target of the rollback if you did not use the option to save files for rollback and do not have access to the live repository. Download and unpack the fix repositories for the target version. Gather the full directory path to your unpacked repositories associated with each fix package that you are applying. If you are rolling back multiple products, separate the repository directory paths with commas.
  
  
2. Using the information gathered in the previous step, run the imcl command to rollback to the previous target version of a product in the installation. If you have existing profiles, be sure that you have stopped the servers as specified in Rolling back the IBM BPM environment (for upgrading from V8.6) or Rolling back the IBM BPM environment (for upgrading from V8.5.x).
   
   IM_INSTALL_LOCATION/eclipse/tools/imcl rollback PACKAGE_VERSION_IDS  -installationDirectory INSTALL_DIR  -log LOG_FILE
   
   If you need to include local repositories for the target version, add the -repositories REPOSITORIES option.
   
   Important: On Linux, to avoid problems, do not roll back all packages at once. Roll back IBM BPM, followed by the Java Development Kit (JDK), followed by WebSphere Application Server.
   
   When the rollback completes, a success message similar to the following message displays on the command line:
   Rolled back to com.ibm.bpm.ADV.v85_8.5.7000.20160301_1551 in the C:\IBM\BPM\v8.5 directory. 
   
   
3. Check the log files to ensure that the rollback completed successfully.
   
   
4. If you are rolling back the IBM BPM environment (profiles and database), reinstall all the previous interim fixes for IBM Business Process Manager and IBM WebSphere Application Server. You must reinstall all the interim fixes that you previously had installed before you upgraded and then rolled back.
   
   
5. Repeat the process for each installation in the environment. Once you are finished, continue with the profile rollback step for existing environments. For upgrading from V8.6, continue from step 6 in Rolling back the IBM BPM environment. For upgrading from V8.5.x, continue from step 6 in Rolling back the IBM BPM environment.
   

Rolling back IBM Process Designer

IBM BPM does not support rolling back the desktop IBM Process Designer using Installation Manager. Instead, complete the following steps to roll back the desktop Process Designer.

1. After rolling back your Process Center to a previous version, use Installation Manager to uninstall the desktop Process Designer.
   
   
2. Delete the directory in which Process Designer was installed.
   
   
3. Reinstall Process Designer with a new zip file that is downloaded from Process Center. For instructions, see Installing the desktop IBM Process Designer.

Reference

You can find additional information about any of these topics in the IBM Business Process Manager product documentation.

For further information about the update strategy or obtaining updates, see the support page for your product.

IBM Business Process Manager Support page
IBM Business Process Manager Express Support page

Trademarks and service marks

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