Create or Edit Composite Sensor Dialog

1.18 Create or Edit Composite Sensor Dialog

Use to create a composite sensor for tracking in your service or reference binding component or service component that has subscribed to an event.

Note: You cannot create composite sensors for service components that have published events.

Composite sensors provide a method for implementing trackable fields on messages. This enables you to monitor incoming and outgoing messages during runtime.

Element	Description
Name	Enter a name for the composite sensor. You must enter a name to enable the Edit icon of the Expression field. The name must be unique across all sensors for a given composite application. When you enter a name already in use, a red underline appears, and the tooltip displays `Duplicate` `name`.
Service Configuration or Reference Configuration	This section provides details about the service or reference in which the composite sensor is being created. Depending on the selection of the starting point (either service or reference), this section name displays as Service Configuration or Reference Configuration, and the first field within this section is named Service or Reference.
Service	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.
Reference	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.
Operation	Select the operation for the port type of the service or reference.
Event Configuration	This section provides details about the service component in which the composite sensor is being created. You can create multiple composite sensors per event. For example, an event payload can include both an SSN and a name. However, you cannot create composite sensors based on event headers. Only composite sensors based on payloads are allowed.
Event	Displays the name of the service component. This field is only displayed if you are creating a composite sensor for a service component. This field cannot be edited.
Event Type	Displays the Subscribe event type. This field cannot be edited. The publish event type is not supported.
Expression	Click the Edit icon to invoke a dropdown list for selecting the type of expression to create. You must first enter a name in the Name field to enable the Edit icon. Variables: Select to create an XPath expression value for a variable. Expression: Select to invoke the Expression Builder dialog for creating an expression. This action always captures values as strings. Properties: Select to create an expression value for a normalized message header property. These are the same properties that display under the Properties tab of the invoke activity, receive activity, reply activity, and OnMessage branch of a pick or scope activity.
Filter	Click the Edit icon to invoke the Expression Builder dialog to create a filter expression. You must first create an expression in the Expression field to enable this icon. For example, you may create a filter for tracking purchase order amounts over 10,000. $in.inDict/tns:inDict/ns2:KeyValueOfstringstring/ns2:Value > 10000.00
Composite Sensor Actions	Displays the supported sensor actions. This feature enables you to store runtime sensor data. You can select both Enterprise Manager and either JMS Queue or JMS Topic. Enterprise Manager: (the default selection) Select to make runtime sensor data searchable in the Flow Instances tab of a SOA composite application in Oracle Enterprise Manager Fusion Middleware Control. This selection is the same as the DBSensorAction selection of previous releases. JMS Queue: Select to store composite sensor data (XML payload) in a JMS queue. You must specify the JMS connection factory and queue name. JMS Topic: Select to store composite sensor data (XML payload) in a JMS topic. You must specify the JMS connection factory and topic name. Note: When Enterprise Manager is selected, sensor data is sent to the trackable fields tables. When it is not selected, data is not sent. However, in both cases, Oracle Enterprise Manager Fusion Middleware Control still displays the fields that enable you to search for composite instances based on that sensor. Note: The JMS Queue and JMS Topic selections enable the composite sensor data (XML payload) to be used by other consumers, including Oracle Business Activity Monitoring and Oracle Event Processing. Both selections use the native JMS support provided with Oracle WebLogic Server, and not the Oracle SOA Suite JMS adapter. You can view JMS messages in the Oracle WebLogic Server Administration Console.