Right-click Variable, and select Create. Click the Edit icon to the right of the Target field to create a variable sensor for a

17-8 Oracle Fusion Middleware Developers Guide for Oracle SOA Suite Figure 17–6 Creating a Fault Sensor Based on your selection, the Namespace and Local Parts fields are automatically filled in. A new entry is created in the bpel_process_name_sensor.xml file, as shown in Example 17–3 : Example 17–3 bpel_process_name_sensor.xml file sensor sensorName=IdentityServiceFault classname=oracle.tip.pc.services.reports.dca.agents.BpelFaultSensorAgent kind=fault target=is:identityServiceFault faultConfig sensor

17.2.3 How to Configure Sensor Actions

When you create sensors, you identify the activities, variables, and faults you want to monitor during runtime. If you want to publish the values of the sensors to an endpoint for example, you want to publish the data of the LoanApplicationSensor variable sensor created in Figure 17–5 to a JMS queue, then create a sensor action, as shown in Figure 17–7 , and associate it with the LoanApplicationSensor variable. To configure a sensor action:

1. In the Structure window, right-click the Sensor Actions folder.

2. Select Create Sensor Action.

3. Enter the details described in Table 17–1 . Table 17–1 Sensor Actions Dialog Field Description Name Enter a name or accept the default name. Publish Type Select the destination to which to publish sensor data. For more information, see section Section 17.1, Introduction to Sensors. JMS Connection Factory If your publish type is JMS Queue, JMS Topic, or JMS Adapter, specify the connection factory. Using Oracle BPEL Process Manager Sensors 17-9 Figure 17–7 Creating a Sensor Action A new entry is created in the bpel_process_name_sensorAction.xml file, as shown in Example 17–4 : Example 17–4 bpel_process_name_sensorAction.xml file action name=BAMFeed enabled=true publishType=JMSQueue publishTarget=jmsbamTopic sensorNameLoanApplicationSensorsensorName property name=“JMSConnectionFactory“ weblogic.jms.ConnectionFactory property action Publish Target If your publish type is JMS Queue, JMS Topic, Custom, or JMS Adapter , specify the publish target. The publish target represents different things depending on the publish type specified: ■ If the publish type is a database, this field is left blank. ■ If the publish type is JMS Queue, JMS Topic, or JMS Adapter , this represents the JMS destinations JNDI name. ■ If the publish type is Custom, this represents the fully-qualified Java class name. Filter Enter filter logic as a boolean expression. A filter enables you to monitor sensor data within a specific range. For an example of a configured filter, see Figure 17–9 and Example 17–6 . Enable Deselect this checkbox to disable a sensor action. By default, sensor actions are enabled. If you disable a sensor action by deselecting this checkbox, the action does not publish data. Note: You cannot specify a less than sign in the Filter field of the Sensor Action dialog. If you do, Oracle JDeveloper translates the sign to lt; in the bpel_process_name_sensorAction.xml file. In addition, you cannot specify a sign by directly editing the filename _sensorAction.xml file. This action causes an error. Table 17–1 Cont. Sensor Actions Dialog Field Description