Click OK. How to Allow the End User to Select Notification Channels

17-2 Oracle Fusion Middleware Developers Guide for Oracle SOA Suite You can define the following types of sensors, either through Oracle JDeveloper or manually by providing sensor configuration files. ■ Activity sensors Activity sensors are used to monitor the execution of activities within a BPEL process. For example, they can monitor the execution time of an invoke activity or how long it takes to complete a scope. Along with the activity sensor, you can also monitor variables of the activity. ■ Variable sensors Variable sensors are used to monitor variables or parts of a variable of a BPEL process. For example, variable sensors can monitor the input and output data of a BPEL process. ■ Fault sensors Fault sensors are used to monitor BPEL faults. You typically add or edit sensors as part of the BPEL modeling of activities, faults, and variables. These sensors are exposed through the following public SQL views: ■ BPEL_ACTIVITY_SENSOR_VALUES ■ BPEL_FAULT_SENSOR_VALUES ■ BPEL_VARIABLE_SENSOR_VALUES These views can be joined with the BPEL_PROCESS_INSTANCES view to associate the sensor value with the BPEL process instance that created the sensor values. For more information, see Appendix D, Understanding Sensor Public Views and the Sensor Actions XSD. When you model sensors in Oracle JDeveloper, two new files are created as part of the BPEL process archive: ■ bpel_process_name _sensor.xml Contains the sensor definitions of a BPEL process ■ bpel_process_name _sensorAction.xml Contains the sensor action definitions of a BPEL process See Section 17.2.2, How to Configure Sensors and Section 17.2.3, How to Configure Sensor Actions for how these files are created. After you define sensors for a BPEL process, you must configure sensor actions to publish the sensor data to a specified destination. If no sensor action is defined for a sensor, then nothing happens at runtime. The following information is required for a sensor action: ■ Name ■ Publish type The publish type specifies the destination in which the sensor data must be presented. You can publish sensor data to the following destination types. – Database Publishes the sensor data to the reports schema in the database. The sensor data can then be queried using SQL. Using Oracle BPEL Process Manager Sensors 17-3 – JMS queue Publishes the sensor data to a JMS queue. The XML data is posted in accordance with the Sensor.xsd file. This file is included with Oracle JDeveloper in the JDEV_ HOME \jdeveloper\integration\seed\soa\shared\bpel directory. – JMS topic Publishes the sensor data to a JMS topic. The XML data is posted in accordance with the same Sensor.xsd file used with JMS queues. – Custom Publishes the data to a custom Java class. – JMS Adapter Uses the JMS adapter to publish to remote queues or topics and a variety of different JMS providers. The JMS queue and JMS topic publish types only publish to local JMS destinations. ■ List of sensors The sensors for a sensor action. Oracle BAM sensors publish information and events from Oracle BPEL Process Manager to Oracle BAM. Oracle BAM can display the data in rich real-time dashboards for end-to-end monitoring of an application. For more information, see Section 50.7, Integrating BPEL Sensors Using Oracle BAM Sensor Action.

17.2 Configuring Sensors and Sensor Actions in Oracle JDeveloper

In Oracle JDeveloper, sensor actions and sensors are displayed as part of Monitor view.

17.2.1 How to Access Sensors and Sensor Actions

To access sensors and sensor actions: 1. Select Monitor at the top of Oracle BPEL Designer, as shown in Figure 17–1 . Figure 17–1 Monitor View Figure 17–2 shows the sensor actions and sensors in the Structure window.