How to remove the link between composite instances in the Audit Trail of Enterprise Manager (Doc ID 2018926.1)

Last updated on AUGUST 09, 2017

Applies to:

Oracle SOA Suite - Version 11.1.1.7.0 and later
Information in this document applies to any platform.

Goal


Composite A is invoked as a web service and calls Composite B. After the one way web service call to Composite B is successful, then Composite A calls itself.

This leaves an audit trail in Enterprise Manager as follows

A->B->A

In previous BPEL 10g code, the following java API call disconnected the current instance from its parent in Composite A

mScope.getCubeInstance().setParentId(null);

What is the equivalent API call in BPEL 11g and 12c?
 

Solution

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