Click the Browse icon above the Namespace field to select to create a fault sensor,

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 17-10 Oracle Fusion Middleware Developers Guide for Oracle SOA Suite If you want to publish the values of LoanApplicationSensor and CreditRatingSensor to the reports schema in the database, create an additional sensor action, as shown in Figure 17–8 , and associate it with both CreditRatingSensor and LoanApplicationSensor . Figure 17–8 Creating an Additional Sensor Action A new entry is created in the bpel_process_name_sensorAction.xml file, as shown in Example 17–5 : Example 17–5 bpel_process_name_sensorAction.xml file action name=PersistingAction enabled=true publishType=BPELReportsSchema sensorNameLoanApplicationSensorsensorName sensorNameCreditRatingSensorsensorName action The data of one sensor can be published to multiple endpoints. In the two preceding code samples, the data of LoanApplicationSensor was published to a JMS queue and to the reports schema in the database. If you want to monitor loan requests for which the loan amount is greater than 100,000, you can create a sensor action with a filter, as shown in Figure 17–9 . There is no design-time validation of the filter query. You must ensure the query is correct. Figure 17–9 Creating a Sensor Action with a Filter A new entry is created in the bpel_process_name_sensorAction.xml file, as shown in Example 17–6 :