|Oracle® Fusion Middleware Developer's Guide for Oracle SOA Suite
11g Release 1 (11.1.1)
Part Number E10224-01
This chapter describes how to define composite sensors in an SOA composite application.
This chapter includes the following sections:
Note:Only the database sensor action is supported for this release. For more information about sensor actions, see Chapter 17, "Using Oracle BPEL Process Manager Sensors."
Composite sensors provide a method for implementing trackable fields on messages. Composite sensors enable you to perform the following tasks:
Monitor incoming and outgoing messages.
Specify composite sensor details in the search utility of the Instances page of an SOA composite application in Oracle Enterprise Manager Fusion Middleware Control Console. This action enables you to locate a particular instance.
You define composite sensors on service and reference binding components in Oracle JDeveloper. This functionality is similar to variable sensors in BPEL processes. During runtime, composite sensor data is persisted in the database.
Note the following restrictions on the use of composite sensors:
Functions can only be used with the payload. For example, XPath functions such as
concat() and others cannot be used with properties.
Any composite sensor that uses expressions always captures values as strings. This action makes the search possible only with the
like comparison operator. Also, even if the value is a number, you cannot use other logical operators such as
=, and any combination of these.
Composite sensors only support the predefined DBSensorAction.
Header-based sensors are only supported for web service bindings.
Sensors for Oracle B2B, service data objects (SDOs), web services invocation framework (WSIF), and Oracle Business Activity Monitoring bindings are not supported.
Sensor values can only be one of the following types.
The following scalar types:
Complex XML elements
When creating an XPath expression for filtering, all functions that return a node set must be explicitly cast as a string:
xpath20:upper-case(string($in.request/inp1:updateOrderStatus/inp1:orderStatus) ) = "PENDING"
You add sensors to service or reference binding components of an SOA composite application in the SOA Composite Editor.
To add composite sensors:
Use one of the following options to add a composite sensor in the SOA Composite Editor.
Right-click a specific service or reference binding component to which to add a composite sensor, and select Composite Sensor.
Click the Composite Sensor icon above the SOA Composite Editor.
The Composite Sensors dialog appears, as shown in Figure 51-2.
Figure 51-2 Composite Sensor Dialog
Select the Composite Sensors folder, then click the Add icon.
The Create Composite Sensor dialog appears, as shown in Figure 51-3.
Figure 51-3 Create Composite Sensor Dialog
Enter the details shown in Table 51-1.
Table 51-1 Create Composite Sensor Dialog
Enter a name for the composite sensor. You must enter a name to enable the Edit icon of the Expression field.
Displays the name of the service. This field only displays if you are creating a composite sensor for a service binding component. This field cannot be edited.
Service sensors monitor the messages that the service receives from the external world or from another composite application.
Displays the name of the reference. This field only displays if you are creating a composite sensor for a reference binding component. This field cannot be edited.
Reference sensors monitor the messages that the reference sends to the external world or to another composite application.
Select the operation for the port type of the service or reference.
Click the Edit icon to invoke a dropdown list for selecting the type of expression to create:
Click the Edit icon to invoke the Expression Builder dialog to create an XPath filter for the expression. You must first create an expression to enable this field.
For example, you may create an expression for tracking purchase order amounts over
$in.inDict/tns:inDict/ns2:KeyValueOfstringstring/ns2:Value > 10000.00
Composite Sensor Actions
Displays the supported sensor action (DBSensorAction). This feature enables runtime sensor data to be stored in the database. For this release, only this sensor action type is supported for composite sensors. This field cannot be edited.
Click Apply to add more composite sensors.
Click OK when complete.
A sensor icon displays on the service or reference binding component.
Figure 51-4 Sensor Icon
The Select XPath Expression dialog shown in Figure 51-5 enables you to select an element for tracking.
To add a variable:
Expand the tree and select the element to track.
Figure 51-5 Variables
Click OK when complete.
The Select Properties shown in Figure 51-6 enables you to create an expression for tracking.
To add an expression:
Build an XPath expression of an element to track.
Figure 51-6 Expression
Click OK when complete.
During runtime, composite sensor data can be monitoring in Oracle Enterprise Manager Fusion Middleware Control Console:
Composite sensor data displays in the flow trace of an SOA composite application.
Composite sensor data can be searched for in the Instances page of an SOA composite application.
For more information, see Oracle Fusion Middleware Administrator's Guide for Oracle SOA Suite.