Product Readmes
Abstract
After you successfully upgrade your IBM Business Automation Workflow V18.0.0.1 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
Tab navigation
- Depending on the version of IBM BPM version you are upgrading from, you must also look at earlier post-upgrade tasks:
- Post-installation tasks for IBM Business Process Manager V8.5.6 CF02 and V8.5.6 CF01
- Post-upgrade tasks for IBM Business Process Manager V8.5.7
- Post-upgrade tasks for IBM Business Process Manager V8.5.7 CF2016.12, CF2016.09, CF2016.06
- Post-upgrade tasks for IBM Business Process Manager V8.5.7 CF2017.06 and CF2017.03
- Post-upgrade tasks for IBM Business Process Manager V8.6
- Post-upgrade tasks for IBM Business Process Manager V8.6 CF2017.12
- Post-upgrade tasks for IBM Business Process Manager V8.6 CF2018.03
For example, if you are upgrading from IBM BPM V8.5.7 CF2017.06, also look at the Post-upgrade tasks for IBM Business Process Manager V8.6, the Post-upgrade tasks for IBM Business Process Manager V8.6 CF2017.12, and the Post-upgrade tasks for IBM Business Process Manager V8.6 CF2018.03.
- If you are upgrading from IBM BPM V8.6 CF2018.03 and you previously downloaded the documentation for offline use, manually delete the previous install_root/BPM/KnowledgeCenter/usr/content/v8r6m0 directory and install the new IBM Business Automation Workflow content as described in Accessing the IBM Business Automation Workflow documentation offline.
- After IBM Workflow Center (formerly IBM Process Center) is successfully upgraded, update your process applications 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 process application, such as to the user interfaces, which you might need to modify.
- Installing cumulative fixes can modify the existing system toolkits for the associated version. If your applications are associated with the latest system toolkits, they will automatically include the changes.
- Change the security parameter names in your scripts. For more information, see the "Security-hardening properties with the ProcessServer prefix" entry in Table 1. Deprecated features for IBM BPM V8.6.0 of Deprecated and removed features.
- IBM Cloud Product Insights was automatically removed during the upgrade. If you had Cloud Product Insights configured, perform the following steps to completely remove the configuration:
1. Delete the was-product-insights.properties file from the following directories on the deployment manager where you added them:
Server directory: <profile_root>/config/cells/<cellName>/nodes/<nodeName>/servers/<serverName>
Cluster directory: <profile_root>/config/cells/<cellName>/clusters/<clusterName>
Node directory: <profile_root>/config/cells/<cellName>/nodes/<nodeName>
Cell directory: <profile_root>/config/cells/<cellName>
2. If you have an Advanced or AdvancedOnly deployment environment (DE) configured, check your Business Flow Manager state observer logging settings in the administrative console by following the instructions in Enabling logging for Business Process Choreopgrapher. For Cloud Product Insights, the Dynamic Event Framework logging state observer has been enabled. Disable it when you don’t have other monitoring solutions that need events.
3. Check your WebSphere Application Server security audit configuration. For Cloud Product Insights security auditing has been enabled. If you don't need security auditing, disable it by following the instructions in Enabling the security auditing subsystem.
Post-upgrade steps for IBM Business Automation Workflow V18.0.0.1
| Interim fix (APAR) | Description | Tasks to enable the function |
| JR59216
In some cases, the namespace of a web service is applied to business objects |
In some cases, the namespace of an inbound web service is used for business objects in the generated WSDL file. As a result, the requests and responses of the inbound web service are affected. Instead of the web service's namespace, the business object's namespace should be used if a custom namespace is set. |
After installing Business Automation Workflow V18.0.0.1, the business object namespace is used for business objects. If you need a different behavior you can change it as described in JR59216. |
|
The database disk runs out of space quickly |
As the result of fix JR52069, the LSW_INST_MSG_EXCL table constantly grows when the intermediate message event is in a loop with "Durable Subscription" selected while the process instance is active. |
To enable this fix, add following lines to the 100Custom.xml file for IBM Workflow Center and IBM Workflow Server: <server> by following this procedure: 1. Stop the servers of your IBM Business Automation Workflow deployment environment. 2. Start the scripting client in disconnected mode as described in updateBPMConfig command. 3. Run the following commands: wsadmin> AdminTask.updateBPMConfig( [ '-create', '/server' ] ) wsadmin> AdminTask.updateBPMConfig( [ '-create', '/server/bpd-engine' ] ) wsadmin> AdminTask.updateBPMConfig( [ '-create', '/server/bpd-engine/enable-legacy-behavior-for-dur-msg-when-msg-event-is-in-loop', '-xNodeValue', 'true' ] ) wsadmin> AdminConfig.save() 4. Restart the servers of your Business Automation Workflow environment. For more information, see Modifying runtime server configuration properties and The 100Custom.xml file and configuration. |
Product Synonym
Business Automation Workflow
Was this topic helpful?
Document Information
Modified date:
06 July 2018
UID
swg27051077