Direct links to fixes
APAR status
Closed as program error.
Error description
Evaluating the endpoint service configuration might return incorrect results. For example, if the URL attribute of a default scenario like EXTERNAL_CLIENT is specified, none of the strategies of a specific scenario run.
Local fix
Problem summary
IBM BPM uses an internal component called "endpoint service" to calculate self-referential URLs, which are URLs that point to IBM BPM. Depending on use cases and the configuration, it is possible that different host and port combinations must be returned. Endpoint service configuration allows you to define a list of strategies to apply to calculate this host and port combination. For more information, see "Configuring IBM BPM endpoints to match your topology" (http://www.ibm.com/support/knowledgecenter/SSFPJS_8.5.7/com.ibm .wbpm.imuc.ebpm.doc/topics/tsec_thirdpartyauthentication_endpoin tservice.html). The design of endpoint service is to first fully evaluate strategies associated with a specific scenario to allow fine grained control. Only if evaluation of the entire specific scenario does not result in a host port combination, should endpiont service evaluate a default scenario. See "Optional scenario keys" at http://www.ibm.com/support/knowledgecenter/SSFPJS_8.5.7/com.ibm. wbpm.imuc.ebpm.doc/topics/rcfgep_optscnkey.html for a list of scenarios and their corresponding default scenarios. The implementation of endpoint service, however, mixed all strategies of specific and default scenarios into a single evaluation, possibly resulting in incorrect sequencing.
Problem conclusion
A fix will be included in IBM BPM V8.5.7 cumulative fix 2016.12 that ensures the sequence of evaluating endpoint service scenarios is correct: If it's available, the BPMURL object for the specific scenario is fully evaluated by - returning the value of the url attribute, if it's set - invoking the listed strategy classes in sequence - returning the value of the virtualHost attribute, if it's set The sequence stops as soon as a URL is calculated. If no URL is determined, the same evaluation runs for the default scenario. If there is still no URL calculated, the defaultVH attribute of the current deployment environment is considered before reverting to the local server's host name and HTTPS port. To determine whether the later cumulative fix is available and download it if it is, complete the following steps on Fix Central: 1. Select IBM Business Process Manager with your edition from the product selector, the installed version to the fix pack level, and your platform, and then click Continue. 2. Select Text, enter 'cumulative fix' and click Continue. When you download fix packages, ensure that you also download the readme file for each fix. Review each readme file for additional installation instructions and information about the fix. PRODUCTS AFFECTED IBM Business Process Manager (BPM) Advanced IBM BPM Standard IBM BPM Express
Temporary fix
Comments
APAR Information
APAR number
JR56941
Reported component name
BPM STANDARD
Reported component ID
5725C9500
Reported release
857
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-11-15
Closed date
2016-12-09
Last modified date
2016-12-09
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
BPM STANDARD
Fixed component ID
5725C9500
Applicable component levels
R857 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTDH","label":"IBM Business Process Manager Standard"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"857","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
14 October 2021