ECID Is Not Propogated While Instantiating BPM Instance Using Ws Client
(Doc ID 1450329.1)
Last updated on FEBRUARY 21, 2019
Applies to:Oracle Business Process Management Suite - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
While instantiating BPM process using ws interface, ECID and Conversation Id
are sent as part of SOAP header; instead of propgating ecid sent by client, BPM engine is generating new ecid.
Only MessageID is getting propogted to BPM process instance as conversation ID.
Example: Login into EM console. Go to soa-infra and select the composite -> click Test. Enter this SOAP message to instantiate BPM process:
Go to Instances tab and slect newly created instance. You will observe that:
Supplied message id is propogated and used in new instance but new ECID is generated and is used.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document