Composite Sensors in Oracle SOA Suite 12c by Jennie DeRosa

Overview

Implementing composite sensors within a SOA solution provides the ability to define trackable fields on messages and enables you to find a specific composite instance by searching for a field or fields within a message. For example, a sensor could be defined for an invoice number within a message, thus allowing us to search and find the instance where the invoice number in question is found.

While this functionality is not new within Oracle SOA Suite 12c, there are some improved capabilities that have been included in this release, which will be covered in this article.

Composite Sensors Review

Composite sensors can be defined within a SOA composite application in several components:

• Service component (exposed service)
• Reference component (external reference)
• Mediator or BPEL component that have subscribed to a business event (publishing an event cannot have a sensor)

Within these components, a composite sensor can be defined in a couple of different ways. One way is to specify an existing variable as the sensor (as shown below). Another way is to define by an expression with the help of the expression builder. The third way is to define using properties (e.g. message header properties). 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 Facebook Wiki

Technorati Tags: SOA Community,Oracle SOA,Oracle BPM,OPN,Jürgen Kress