Product Readmes
Abstract
After you successfully upgrade your IBM Business Process Manager V8.6 2018.03 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 the following tasks.
Content
Tab navigation
Important notes
- Depending on the version of IBM BPM version you are upgrading from, you must also look at earlier post-upgrade tasks:
- Postinstallation 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 2016.09 and 2016.06
- Post-upgrade tasks for IBM Business Process Manager V8.5.7 2016.12
- Post-upgrade tasks for IBM Business Process Manager V8.5.7 2017.06 and 2017.03
- Post-upgrade tasks for IBM Business Process Manager V8.6
- Post-upgrade tasks for IBM Business Process Manager V8.6 2017.12
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 and the Post-upgrade tasks for IBM Business Process Manager V8.6 CF2017.12.
- After IBM Process Center is successfully upgraded, update your process applications to the latest IBM BPM toolkit levels so you can integrate the latest improvements and defect fixes associated with the toolkit objects. After you update to the latest IBM BPM 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 fix packs can modify the existing system toolkits for the associated version. If your applications are associated with the latest system toolkits, they 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.
Post-upgrade steps for V8.6 CF2018.03
| Interim fix (APAR) | Description | Tasks to enable the function |
| JR58201 When a task is interrupted by an intermediate event, its status might not be correctly updated in IBM Process Portal. |
When the <cancel-fire-on-close-regardless> property is set to true, the terminate event is triggered regardless of the task's status. The terminate event is triggered only if it isn't already closed. | To fire task events regardless of the task status, such as when a task is marked as closed but it's still open in the Process Portal index or you use the APIs to simultaneously close and cancel a task, add the following lines to the 100Custom.xml file for IBM Process Center and IBM Process Server
1. Stop the servers of your IBM BPM deployment environment. 2. Start the scripting client in disconnected mode as described in updateBPMConfig command. 3. Run the following commands: 4. Restart the servers of your IBM BPM environment. For more information, see Modifying runtime server configuration properties and The 100Custom.xml file and configuration. |
| JR59039 After you migrate a BPEL application from IBM BPM V8.0.1.3 to V8.6 CF2018.03, it fails with a java.lang.VerifyError |
This fix uses the more recent XSLT implementation from the Java runtime environment with stricter syntax validation. As a result, you might see errors like "CWSXM3110E: Exception while initializing the XSL transformation engine with stylesheet 'xslt/Map_CustomMessage_req_1.xsl'" with the following corresponding FFDC entry "None of the transformer factories could work with the supplied stylesheet" after you upgrade to IBM BPM V8.6 CF2018.03. |
Because the new XSLT implementation does stricter syntax validation your stylesheets must comply with the XSL Transformations (XSLT) Version 1.0 specification (https://www.w3.org/TR/1999/REC-xslt-19991116) or XSL Transformations (XSLT) Version 2.0 (Second Edition) (https://www.w3.org/TR/2009/PER-xslt20-20090421). For example, you might need to change the Custom XML from <xsl:variable name="locationData" select=""> Tip: Check the SystemErr.log file for additional error details. |
| JR59199 You can't configure email notification to allow communication with the mail server via SSL. |
You might need the ability to add configuration to the email notification mechanism of IBM Business Process Manager (BPM) Standard to allow communication with the mail server via SSL. |
To allow communication with the mail server via SSL, add the <use-ssl > parameter to the 100Custom.xml file for Process Center and Process Server. If your mail server uses a custom port, also add the <mail-smtp-port> parameter, for example 1. Stop the servers of your IBM BPM deployment environment. 2. Start the scripting client in disconnected mode as described in updateBPMConfig command. 3. Run the following commands: 4. Restart the servers of your IBM BPM environment. 5. In the <install_root>/BPM/Lombardi/lib directory, add the version of jaxamail.jar you want to use (minimum 1.4.5). If your mail server uses a SSL protocol other than TLSv1.2, add the <ssl-protocols> parameter too, specifying a whitespace-separated list of SSL protocols. Note: You can remove the <mail-smtp-port> setting to revert to using the default port. For more information, see Modifying runtime server configuration properties and The 100Custom.xml file and configuration. |
Product Synonym
BPM
Was this topic helpful?
Document Information
Modified date:
14 September 2022
UID
swg27050793