Friday Feb 06, 2015

ECID propagation between SCA composites and JAX-WS web services by Nicolas Fonnegra

clip_image002The Oracle SOA Suite provides an Audit Trail monitor screen where the message flow between the different SCA composites can be tracked. Depending on the audit level, it can provide a very detailed chronology of the different states of the message, including the first component that receives the messages, its correspondent transformation along the way, and the routing it’s final destination. Nevertheless, a SOA platform is intended to integrate not only internal composites but also external components. The question is how to maintain the audit trail consistency in such scenarios?

The Oracle A-team posted a very helpful blog demonstrating how to propagate the ECID between JCA adapter calls in order to maintain the audit trail consistency. This blog is going to demonstrate how to achieve this result with JAXWS web services.

As the reader might have already figured it out, the key to this problem relies with the ECID. The execution context id (ECID) is the mechanism the SOA Suite uses to keep track of the messages as it passes between the different components. If an SCA calls another one, it will pass through the ECID, helping the audit trail to correlate the different component instances into one flow. Also, if instead of a SCA composite a JAXWS web service, the ECID will be passed in the SOAP header, more specifically in the ReplyTo element: Read the complete article here.

SOA & BPM Partner Community

For regular information on Oracle SOA Suite become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.

Blog Twitter LinkedIn image[7][2][2][2] Facebook clip_image002[8][4][2][2][2] Wiki

Wednesday Oct 17, 2012

Storing SCA Metadata in the Oracle Metadata Services Repository by Nicolás Fonnegra Martinez and Markus Lohn

The advantages of using the Oracle Metadata Services Repository as a central storage for the metadata.

SCA has been available since the release of the Oracle SOA Suite 11g. This technology combines and orchestrates several SOA components inside an SCA composite, making design, development, deployment, and maintenance easier. SCA development is metadata-driven, meaning that metadata artifacts, such as Web Services Description Language (WSDL), XML Schema Definition (XSD), XML, others, define the composite's behavior.fonnegra-storing-sca-metadata-fig02

With the increased number of composites and the dependencies among them, it became necessary to manage all the metadata in an adequate way. This article will address the advantages of using the Oracle Metadata Services (MDS) repository as a central storage for the metadata. The MDS repository is a central part of the Oracle Fusion Middleware landscape, managing the metadata for several technologies, such as Oracle Application Development Framework (Oracle ADF), Oracle WebCenter, and the Oracle SOA Suite. This article is divided into three parts.

The first part provides an overview of SCA and MDS. The second part describes some MDS tasks that help in the management of the SCA metadata files inside the repository. The third part shows how to develop SCA composites in combination with an MDS repository. Read the full article here.

SOA & BPM Partner Community

For regular information on Oracle SOA Suite become a member in the SOA & BPM Partner Community for registration please visit  www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.

Blog Twitter LinkedIn Mix Forum

About





Search

Archives
« March 2015
SunMonTueWedThuFriSat
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
    
       
Today