7.18 Create or Edit Sensor Action Dialog
Use the Create or Edit Sensor Action Dialog to manage (create or edit) BAM sensor actions.
You create Oracle BAM sensor actions to publish sensor data directly to data objects on Oracle BAM Server. You must have performed one of the following tasks before you can create an Oracle BAM sensor action:
-
Created an Oracle BAM connection in the Application Resources pane of the current JDeveloper application. How?
-
Created a variable sensor. Since you map the sensor data to Oracle BAM Server data objects, only one variable is allowed for the sensor. If the variable has message parts, then there should be only one message part. This variable must not be defined inline in the WSDL. Only XSD element definitions are supported. How?
-
Created an activity sensor containing exactly one sensor variable. How?
Note:
Oracle BAM sensor actions can only be created from the Structure window by right-clicking Sensor Actions and selecting Create then choose BAM Sensor Action.
Element | Description |
---|---|
Action Name |
Enter a unique and recognizable name for the sensor action. |
Enable |
Select to enable the sensor action. When disabled no sensor action data is sent to Oracle BAM. |
Sensor |
Select a BPEL sensor to monitor. This is a sensor that you previously created for mapping sensor data to a data object in Oracle BAM Server. The data is published in data objects on the Oracle BAM Server. This list only displays sensors that have one sensor variable of an element type or a message type with one message part. The sensor variable data is captured in data objects on Oracle BAM Server. |
Data Object |
Click the Browse icon to open the BAM Data Object Chooser dialog, and select the data object in Oracle BAM Server in which you want to publish the sensor variable data. If you have not already created a connection to Oracle BAM Server in order to select data objects, click the icon in the upper right corner of the BAM Data Object Chooser dialog. Data objects are published in WSDL files. You must have an accessible connection to Oracle BAM Server in order to select data objects. |
BAM Operation and Keys |
Select the operation to perform. |
Operation |
Select to Delete, Update, Insert, or Upsert a row in the Oracle BAM Server database. Upsert first attempts to update a row if it exists. If the row does not exist, it is inserted. |
Available Keys |
If you selected Delete, Update, or Upsert, you must also select a column name in the Oracle BAM Server database to use as a key to determine the row with which this sensor object corresponds. A key can be a single column or a composite key consisting of multiple columns. Select a key and click the > button. To select all, click the >> button. |
Selected Keys |
Displays the keys selected. |
Map File |
Provide a file name to create a mapping between the BPEL sensor (selected in the Sensor list) and Oracle BAM Server data object (selected in the Data Object list). You can also invoke a mapper dialog by clicking the Create Mapping icon (second icon) or Edit Mapping icon (third icon). Note: After you click the Create Mapping icon (second icon) or Edit Mapping icon (third icon), or click OK on this dialog, you must explicitly save the Oracle BPEL Process Manager file. |
Filter |
Enter an XPath expression to filter sensor action data that is sent to Oracle BAM. At runtime the XPath expression entered in the field is evaluated, and it must return true for the sensor action to be fired. Enter filter logic as a boolean expression. A filter enables you to monitor sensor data within a specific range. For example, you may want to monitor loan requests in which the loan amount is greater that $100,000. In this case, you can enter an expression such as the following:
|
BAM Connection Factory JNDI |
Specify the JNDI name for the Oracle BAM Server connection factory. |
Enable Batching |
The data cached by default by the Oracle BAM component of the Oracle BPEL Process Manager runtime is flushed (sent) to Oracle BAM Server periodically. The Oracle BAM component may decide to send data prior to a batch time out if the cache has a number of data objects between automatically defined upper and lower limit values. Disable batching by unselecting this check box. The decision to periodically send the data is based on upper and lower limit parameter settings in the Fusion Middleware Control. |
Related Topics
BAM Data Object Chooser Dialog
Developing SOA Applications with Oracle SOA Suite, "Integrating BPEL Sensors Using Oracle BAM Sensor Action"