Fix Readme
Abstract
After you successfully upgrade your IBM Business Automation Workflow 23.0.2 environment, some additional configuration steps might be required.
If any of the fixes in the table affect your environment or how you use the product, consider performing the following tasks.
Content
Updating to the latest API
Upgrade embedded product JAR files in any custom applications, plugins, services, and so on, for the purpose of using product APIs. For example, if you use Case API in a custom application, ensure that the Case API jar file in your custom application is updated as part of the upgrade.
- 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.
Complete these steps:
- Download the User Management Service (UMS) 23.0.2 from IBM Passport Advantage as part of CC70PML.
- In a separate installation directory, install UMS as described in Installing the User Management Service.
- Copy the wlp/usr folder from the previous UMS installation to the new UMS installation directory.
- 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 server from the ibmUserManagement template by running the following command:
server create <server_name> --template=ibmUserManagement:ibmUserManagement - In the new UMS installation directory wlp/usr/servers/<server_name>/configDropins/overrides, apply the customizations from the previous installation.
- Review new variables introduced in the template files.
- Stop the UMS server in the previous installation directory.
- Start the UMS server from the new installation directory.
Note: The new UMS server automatically uses 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.
- Business Automation Workflow requires HTTPS by default. If you use HTTP for some communication, try to remove HTTP usage before you upgrade, and ensure that HTTPS communications work. If you are not able to, see Re-enabling HTTP access in Business Automation Workflow temporarily.
- Post-upgrade tasks for IBM Business Automation Workflow 18.0.0.1
- Post-upgrade tasks for IBM Business Automation Workflow 18.0.0.2
- Post-upgrade tasks for IBM Business Automation Workflow 19.0.0.1
- IBM Business Automation Workflow 19.0.0.2 has no post-upgrade steps.
- Post-upgrade tasks for IBM Business Automation Workflow 19.0.0.3
- Post-upgrade tasks for IBM Business Automation Workflow 20.0.0.1
- Post-upgrade tasks for IBM Business Automation Workflow 20.0.0.2
- IBM Business Automation Workflow 21.0.2 has no post-upgrade steps.
- Post-upgrade tasks for IBM Business Automation Workflow 21.0.3
- Post-upgrade tasks for IBM Business Automation Workflow 22.0.1
- Post-upgrade tasks for IBM Business Automation Workflow 22.0.2
- Post-upgrade tasks for IBM Business Automation Workflow 23.0.1
- Post-upgrade tasks for IBM Business Automation Workflow 23.0.2
Known Issue | Description | Steps/Enablement |
DT213513 | A fix is included that will allow project to be opened and edited using web Process Designer even after duplicate dependencies have been detected. |
Add
within properties section of 100Custom.xml to enable bypass and remain within web Process Designer after duplicate dependencies dialog is dismissed. Without setting bypass-duplicate-dependencies-guard to true the fix has no effect.
|
DT237067 | A fix is included that corrects the context root in Process Admin Console URL when the contextRootPrefix is updated again. |
Post Installation Manager install instructions
(These need to be run once after all the fixes have been installed using Installation Manager, before starting servers.) For existing deployment environment, after applying the interim fix, please do the following to fix the problem.
You may use BPMConfig command to update the context root prefix. You will need to use the same context root prefix as before, that will fix the incorrect context root for the WorkflowAdmin.war file.
Please note that the component is ProcessServer because the ProcessAdminEar belongs the ProcessServer component. BPMConfig -update -profile mydeploymentmgrprofilename -de mydeploymentenvname -contextRootPrefix /contextrootprefix4ProcessServer https://www.ibm.com/docs/en/baw/19.x?topic=utilities-bpmconfig-command-line-utility#BPMconfig__update Post Install instructions
(After starting servers) For existing deployment environment, after applying the interim fix, you have two options to fix the problem.
1. Option 1 is the same as that in step 4 since BPMConfig command can be running with or without deployment manager running.
You may use BPMConfig command to update the context root prefix. You will need to use the same context root prefix as before, that will fix the incorrect context root for the WorkflowAdmin.war file. Please note that the component is ProcessServer because the ProcessAdminEar belongs the ProcessServer component. BPMConfig -update -profile mydeploymentmgrprofilename -de mydeploymentenvname -contextRootPrefix /contextrootprefix4ProcessServer https://www.ibm.com/docs/en/baw/19.x?topic=utilities-bpmconfig-command-line-utility#BPMconfig__update 2. You may log in to the WAS Admin Console to fix the context root manually for WorkflowAdmin.war.
If there is no customized context root prefix is specified, the context root for WorkflowAdmin.war has correct value which is /ProcessAdmin. |
DT237988 | A fix is included that will provide a setting to enable the legacy behaviour of not showing milliseconds for dates within complex types. |
To enable the previous behavior after the fix is installed, add this to 100Custom.xml (if the common element is already there, add dateandtime-include-milliseconds-base to it).
|
DT238179 | A fix is included that allows Workplace to open without errors. The fix must be included before installing Business Automation Workflow. If installation is already complete, then the workaround must be used. |
Install with recommended fixes. If installation is already complete, then use the Ops REST API to set a default version on the Workplace toolkit. POST /std/bpm/container/{container}/versions/{versions}/make_default - Designate a default snapshot on a workflow server. |
DT245916 | A fix is included that adds configuration parameter to toggle behaviour implemented by JR63169. |
If you require an initial script generated for the default value to populate list variables with elements, add
within properties section of 100Custom.xml.
|
Product Synonym
Business Automation Workflow
Was this topic helpful?
Document Information
Modified date:
15 December 2023
UID
ibm17056430