Installing IBM Business Process Manager V8.5.7 Cumulative Fix 2017.03

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, and IBM Business Process Manager Advanced - Process Server Version 8.5.7.x.

To upgrade Process Federation Server, see IBM Process Federation Server Version 8.5.7 Cumulative Fix 2017.03 - IBM Business Process Manager.

Table of Contents

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

© Copyright International Business Machines Corporation 2016. 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 cumulative fix

By installing the cumulative fix, you will raise the fix level of your product, either IBM Business Process Manager Express, IBM Business Process Manager Standard, IBM Business Process Manager Advanced, or IBM Business Process Manager Advanced - Process Server, to Version 8.5.7 CF2017.03.

The fixes addressed in this cumulative fix are explained in the Fix list for the IBM Business Process Manager Version 8.5 products.

Installation instructions

Cumulative fix prerequisites

To use this cumulative fix, 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, or Version 8.5.7 CF2016.12 of IBM Business Process Manager Express, IBM Business Process Manager Standard, IBM Business Process Manager Advanced, or IBM Business Process Manager Advanced - Process Server product 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 have V8.5.0.x, V8.5.5, or V8.5.6.x of IBM BPM, you can upgrade directly to the cumulative fix if you make both the Version 8.5 Refresh Pack 7 upgrade repository and the cumulative fix repository available to IBM Installation Manager during the upgrade.
• Installing the cumulative fix requires WebSphere Application Server V8.5.5, Fix Pack 11 or a later version.
• 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.
• If you need to install DB2 or LDAP, make sure that you install the latest version.

Hardware and software prerequisites for IBM Business Process Manager Express, IBM Business Process Manager Standard, IBM Business Process Manager Advanced, and IBM Business Process Manager Advanced - Process Server are available on the web on their respective Hardware and Software Support pages.

Installing the cumulative fix
To install the cumulative fix, follow these instructions to download the fix pack repositories, choose your installation path, and review the post-installation 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.5.0.x, V8.5.5, V8.5.6.x, or V8.5.7.x, complete the steps in Upgrading profiles.
• If you are migrating from a version earlier than IBM BPM V8.5.0.x, use Installation Manager to install the cumulative fix, but do not create profiles or a deployment environment. After installing the cumulative fix, 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.
  
  
2. If you are installing IBM BPM V8.5.7 CF2017.03 in a new environment, include the cumulative fix with the V8.5.7 repository while installing the product. For more information, see the Interactive Installation and Configuration Guide.
   
   Important: When you are installing WebSphere Application Server Network Deployment V8.5.5.11, you must select Java 6 as the embedded JDK in WebSphere Application Server. For an interactive installation, under WebSphere Application Server Network Deployment, expand End of Service for Java SE, and select the Continue to use Java SE 6 on the default Java SDK check box. You cannot use Java 8 because it is currently not supported for IBM BPM. If you want to move off Java 6, install IBM WebSphere SDK, Java Technology Edition, Version 7 or 7.1, after you have finished the upgrade.
   
   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, or V8.5.7.x, 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-installation task information for additional actions you might need to take.

If you selected to install with Java 6 only, you might see a warning "Returning with return code: INSTCONFPARTIALSUCCESS" and there might be an iscdeploy command error in the log.
You can fix the error by running the following command:
On Windows: install_root\bin\iscdeploy -restore
On Linux or UNIX: install_root/bin/iscdeploy.sh -restore

Your IBM Business Process Manager installations are now updated to V8.5.7 CF2017.03.

You will see "8.5.7.201703" 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 cumulative fix 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, these steps are not needed. You can download the required WebSphere Application Server fix pack and IBM BPM cumulative fix from the live repository.
• New installations require the IBM BPM V8.5.7 installation media, as noted in the IBM Knowledge Center for IBM BPM.
  
  

1. Download the appropriate fix repository by following the Downloading the cumulative fix document. Download bpm.8570.cf2017.03.delta.repository.zip to a temporary disk location.
   
   
2. If you are upgrading from a version earlier than V8.5.7, download the appropriate refresh pack using the Version 8.5 Refresh Pack 7 for the IBM Business Process Manager products document. For IBM BPM Advanced, Standard, or Express, download bpm.8570.delta.repository.1.zip and bpm.8570.delta.repository.2.zip to a temporary disk location.
   
   
3. You must have WebSphere Application Server V8.5.5, Fix Pack 11 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-FP011-part1.zip, 8.5.5-WS-WAS-FP011-part2.zip, and 8.5.5-WS-WAS-FP011-part3.zip for WebSphere Application Server V8.5.5.11.
   For information about the fixes and download links, see Fix list for IBM WebSphere Application Server V8.5.
   
   
4. Install the latest security fixes for WebSphere Application Server V8.5.5.11:
1. Java updates January 2017: https://www.ibm.com/support/docview.wss?uid=swg21998379
   Install the appropriate interim fix for the Java version you want to use:
   - Interim Fix PI76779: Will upgrade you to IBM SDK, Java Technology Edition, Version 6R1 Service Refresh 8 Fix Pack 41 (required)
   - Interim Fix PI76507: Will upgrade you to IBM SDK, Java Technology Edition, Version 7 Service Refresh 10 FP1 (optional)
   - Interim Fix PI76505: Will upgrade you to IBM SDK, Java Technology Edition, Version 7R1 Service Refresh 4 FP1 (optional)
2. Cross-site scripting vulnerability in the WebSphere Application Server administrative console:
   https://www.ibm.com/support/docview.wss?uid=swg21998667
   - Interim Fix PI73367
3. Denial of service vulnerability in WebSphere Application Server: https://www.ibm.com/support/docview.wss?uid=swg21997477
   - Interim Fix PI73519
4. Privilege Escalation Vulnerability in WebSphere Application Server:
   https://www.ibm.com/support/docview.wss?uid=swg21999293
   - Interim Fix PI74857
5. Remote code execution in WebSphere Application Server MQ JCA Resource adapter: https://www.ibm.com/support/docview.wss?uid=swg21996748
   - Interim Fix PI74862
   
   
5. Download any required interim fixes from IBM Fix Central that are specific to IBM BPM V8.5.7 CF 2017.03. Select your installation type and 8.5.7.201703 to search for recommended fixes on this site.
   Note: Applying this cumulative fix will remove any previously installed interim fixes. If a fix is included in the cumulative fix, 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\refreshpack, or staging_directory\IFix1.
   Note: If a cumulative fix or refresh pack 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-FP011 files to staging_directory\WAS85511. Because CF2017.03 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 IBM BPM cumulative fix installation updates. 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.
  
  
• 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 this process for all new repositories.
   
   
4. Click OK to save the new repository settings.
   
   
3. Click Update.
   
   
4. Select the package group where you have installed IBM Business Process Manager Express, IBM Business Process Manager Standard, IBM Business Process Manager Advanced, or IBM Business Process Manager Advanced - Process Server and click Next.
   
   
5. After Installation Manager checks the service repositories, the Update Packages window opens and the IBM Business Process Manager Express, IBM Business Process Manager Standard, IBM Business Process Manager Advanced, or IBM Business Process Manager Advanced - Process Server 8.5.7 cumulative fix 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 11 or later, it is also shown.
   
   
6. Ensure that these fix packs 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 interim fix 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 cumulative fix will remove any previously installed interim fixes. If a fix is included in the cumulative fix, 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. A panel about the end of service for Java SE 6 is displayed. If you want to move off Java 6, install IBM WebSphere SDK, Java Technology Edition, Version 7 or 7.1, after you upgrade IBM BPM. See Switching the edition of Java used in IBM BPM for instructions. You cannot use Java 8 because it is currently not supported for IBM BPM.
   
   
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, continue following the upgrade procedure 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. If you want to upgrade additional installations, repeat the steps, or return to step 4 for installations using the same Installation Manager.

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 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 can be used to get the package ID for products that can be installed with IBM BPM 8.5.7:

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)
IBM WebSphere SDK Java Technology Edition 7	com.ibm.websphere.IBMJAVA.v70
IBM WebSphere SDK Java Technology Edition 7.1	com.ibm.websphere.IBMJAVA.v71 (or com.ibm.sdk.71_64bit for Little Endian systems)

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.
   
   
   The following command is an example of upgrading IBM BPM Advanced Process Server on Windows:
   C:\Program Files (x86)\IBM\Installation Manager\eclipse\tools\imcl install com.ibm.bpm.PS.v85 -acceptLicense -installationDirectory C:\IBM\BPM\v8.5 -repositories C:\BPM857CF\bpm.8570.cf2017.03.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.5.700201703.20170328_1810 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 upgrade procedure 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 cumulative fix

Rolling back the cumulative fix

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

Note: The following procedure rolls back only the IBM BPM installation. If you have an existing IBM BPM deployment environment, 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 profiles using the manageprofiles command-line utility for more information.


Rolling back the cumulative fix 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 an existing IBM BPM deployment environment, see 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 cumulative fix 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 IBM Business Process Manager Version 8.5.x, before you upgraded to the cumulative fix. 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.
   
   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 steps for existing environments. You can continue from step 4 in Rolling back the IBM BPM environment.
   

Rolling back IBM Process Designer

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

1. After rolling back your Process Center to a previous version, use Installation Manager to uninstall 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 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 Express Support page
IBM Business Process Manager Standard Support page
IBM Business Process Manager Advanced Support page
IBM Business Process Manager Advanced Process Server Support page

Trademarks and service marks

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