APAR status
Closed as documentation error.
Error description
The following statements in "Configuring servers to invoke services synchronously" (https://www.ibm.com/support/knowledgecenter/en/SS8JB4/com.ibm.w bpm.main.doc/topics/tdev_invkremotesynch.html) are misleading: "A service component invoking another service synchronously can communicate with the target only by configuring the export Java? Naming and Directory Interface (JNDI) name on the target system to a JNDI name on the invoking system." In fact, the configuration must be done on the invoking system only. The target system is configured automatically during deployment. "Note: For simplicity, only the servers involved in this communication in each cell is shown and each server resides on a different physical machine. However, the configuration for cross-cluster asynchronous invocation can apply for the configuration in the same cell too." This note is about asynchronous invocation rather than synchronous invocation. Also, configuration is required only if the service you are invoking is in a different cell than the target system.
Local fix
n/a
Problem summary
No additional information is available.
Problem conclusion
The content will be updated the next time the documentation is refreshed.
Temporary fix
Comments
APAR Information
APAR number
JR62075
Reported component name
BPM
Reported component ID
5737A5700
Reported release
860
Status
CLOSED DOC
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2020-03-09
Closed date
2020-03-31
Last modified date
2020-03-31
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSFPJS","label":"IBM Business Process Manager"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.6.0.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
14 September 2022