IBM Support

Post-upgrade tasks for IBM Business Automation Workflow 21.0.3

Fix Readme


Abstract

After you successfully upgrade your IBM Business Automation Workflow 21.0.3 environment, some additional configuration steps might be required.

Consider the following tasks if any of the fixes in the table affect your environment or how you use the product.

Content

The following tabs primarily provide information about IBM Business Automation Workflow 21.0.3. However, the Upgrading IBM Case Manager tab provides information about upgrading IBM Case Manager V5.3.3 to IBM Business Automation Workflow 21.0.3.
Updating to the latest toolkit
After IBM Workflow Center is successfully upgraded, update your projects to the latest IBM Business Automation Workflow toolkit levels so you can integrate the latest improvements and defect fixes associated with the toolkit objects. After you update to the latest Business Automaton Workflow toolkit levels, you might notice small behavior changes in your project, such as to the user interfaces, which you might need to modify. You need to modify your project only if it includes a toolkit snapshot with a different snapshot ID than the toolkits included with the current product version.
Installing cumulative fixes can modify the existing system toolkits for the associated version. If your applications are associated with the Business Automation Workflow system toolkits, they will automatically include the changes. In some cases, the snapshot name might change even though the ID stays the same.
 
Updating to the latest API
Upgrade embedded product JAR files in any custom applications, plugins, services etc. for the purpose of using product APIs.  For example, if you use Case API in a custom application, ensure the Case API jar file in your custom application is updated as part of the upgrade.
Run the BPMRegenTheme command
If you use the UI toolkit in your process applications, run the BPMRegenTheme command after you upgrade. If you don't use the UI toolkit in your process applications, ensure that your process application user interface is tested after the upgrade because some of the CSS updates might affect the look and feel of the user interface. 
Notes:
  • To update all the named snapshots for your process applications and toolkits, you can use the wildcard as mentioned in the documentation.
  • The procedure is different for a tip than a snapshot. You must follow specific instructions for the theme changes to take effect on the tip of the process app or toolkit. For the instructions for both the tip and snapshot, see BPMRegenTheme command.
Updating the Oracle LOB 
If your environment was originally created with an Oracle database before Business Process Manager V8.5.5, you might need to manually update the LOB storage formats to SECUREFILE from BASICFILE. Continuing to use the BASICFILE format might lead to performance problems. For more information, see BLOB columns in the Oracle database are in BASICFILE format after migration or upgrade to IBM Business Automation Workflow.

Upgrading the User Management Service
Complete these steps: 

  1. Download the User Management Service (UMS) version 21.0.3 from IBM Passport Advantage as part of CC70PML.
  2. In a separate installation directory, install UMS as described in Installing the User Management Service.
  3. Copy the wlp/usr folder from the previous UMS installation to the new UMS installation directory.
  4. To use the new features, update your server configuration by completing the following two steps:
     

    a. Change to the wlp/bin directory in the new UMS installation.
    b. Create a new server from the ibmUserManagement template by running the 
         following command:

    server create <server_name> --template=ibmUserManagement:ibmUserManagement

  5. In the new UMS installation directory wlp/usr/servers/<server_name>/configDropins/overrides, apply the customizations from the previous installation.
  6. Review new variables introduced in the template files.
  7. Stop the UMS server in the previous installation directory.
  8. Start the UMS server from the new installation directory.

Note: The new UMS server should automatically use the same connection URL and database as the previous server so no additional steps are needed for Business Automation Workflow to connect to the new server.

Upgrading from Business Process Manager
If you are upgrading from IBM BPM, review the Post-upgrade tasks for IBM Business Automation Workflow 18.0.0.1.
Fix-specific post-upgrade instructions
Depending on the version you are upgrading from, also look at earlier post-upgrade pages to see the fix-specific post-upgrade instructions for each release between the source and this version:  
Post-upgrade steps for IBM Business Automation Workflow 21.0.3 interim fixes
 
Interim fix (APAR) Description Tasks to enable the function
When you use the Business Process Rules Manger web interface to modify a specific business rule, the changes are not applied or shown correctly when Synchronize with the name is not selected.
Update the Business.Rules.Manager application:
  1. In the WebSphere Application Server Integrated Solutions Console, go to Applications > Application Types > WebSphere enterprise applications.
  2. Update the Business.Rules.Manager_xxx application by selecting Replace the entire application and using the brmanager.ear application .ear file located in <BAW_ROOT>/installableApps.
  3. Restart the Business.Rules.Manager application.
JR64520
The use of log4j 1.x is removed from the following Case components:
  • Case Builder
  • Case Forms
  • Case Manager
  • Case Event Emitter
  • Case Configuration Tool
  • ICMBPMServices
  • WSCPEServices

JR64520 does not remove all instances of log4j, there are some remaining instances. 
To remove the remaining instances, perform one of the following:

  • Install DT269709 to automatically remove remaining log4j jar files.
  • Manually remove the remaining unused log4j jar files from the application ear and war files. These files are located in the config folders for the deployment manager and all application nodes in the environment.  
    The log4j jar files are packaged inside ear and war files. You can use the zip or jar utility to open and remove the files.
    /config/cells/<cell_name>/applications/CaseBuilder_<cluster_name>.ear/CaseBuilder_<cluster_name>.ear/CaseBuilder.war/WEB-INF/lib/log4j-1.2.15.jar
    /config/cells/<cell_name>/applications/CaseForms_<cluster_name>.ear/CaseForms_<cluster_name>.ear/CaseForms.war/WEB-INF/lib/log4j.jar
    /config/cells/<cell_name>/applications/CaseManager_<cluster_name>.ear/CaseManager_<cluster_name>.ear/CaseManager.war/WEB-INF/lib/log4j-1.2.15.jar
    /config/cells/<cell_name>/applications/ICMBPMServices_<cluster_name>.ear/ICMBPMServices_<cluster_name>.ear/ICMBPMServices.war/WEB-INF/lib/log4j-1.2.15.jar
JR64216 A slowdown may occur due to JR64216 included in this release:
When multiple users log in at the exact same time, the system may become very slow. Multiple threads try to acquire the same lock. The behavior is not a real deadlock and usually resolves by itself after some time, but the slowdown is significant.		 Install DT169750 to resolve the slowdown.

[{"Type":"MASTER","Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS8JB4","label":"IBM Business Automation Workflow"},"ARM Category":[{"code":"a8m0z000000GmmTAAS","label":"Upgrade and Migration-\u003EUpgrade Planning"}],"ARM Case Number":"","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"21.0.3"}]

Product Synonym

Business Automation Workflow

Document Information

Modified date:
18 March 2024

UID

ibm16516664

Page Feedback