ECID Is Not Propogated While Instantiating BPM Instance Using Ws Client
Last updated on MAY 16, 2012
Applies to:Oracle Business Process Management Suite - Version 126.96.36.199.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.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms