SOA Composite Applications Monitoring using Oracle BAM

The Oracle BAM Adapter is a Java Connector Architecture (JCA)-compliant adapter that can be used from a Java EE client to send data and events to the Oracle BAM Server. The Oracle BAM Adapter supports the following operations on Oracle BAM data objects: inserts, updates, upserts, and deletes.

            The Oracle BAM Adapter can perform these operations over Remote Method Invocation (RMI) calls (if they are deployed in the same farm), direct Java object invocations (if they are deployed in the same container), or over Simple Object Access Protocol (SOAP) (if there is a fire wall between them).

Oracle BAM Adapter can be used with various features in SOA composite applications by which you can send data to an Oracle BAM Server:

1.      The Oracle BAM Adapter transfers data from BPEL process monitors to automatically generated Oracle BAM data objects (Monitor Express).

2.      The Oracle BAM Adapter can be used as a reference binding component in a SOA composite application. For example, Oracle Mediator can send data to Oracle BAM using the Oracle BAM Adapter

3.      The Oracle BAM Adapter can also be used as a partner link in a Business Process Execution Language (BPEL) process to send data to Oracle BAM as a step in the process

4.      Oracle BAM sensor actions (which use Oracle BAM Adapter) can be included within a BPEL process to publish event-based data to the Oracle BAM data objects (BAM Sensor Action).

Note:

Before start this you need to complete two tasks:

1.      Complete my previous post Configuring BAM Adapter Properties .

2.      Get Completed   “PO Processing  Application” or do PO Processing application  SOA sample which is from oracle (because this post is written with use case of PO Processing Application).

Using Oracle BAM Monitor Express With BPEL Processes

            The Monitor Express offering from Oracle BAM provides high level instrumentation of BPEL processes, automatically handling Oracle BAM data object deployment and population.

            Activity Monitors and Monitoring Objects are used to capture BPEL process metrics, which are sent to Oracle BAM Server, and then used for analysis and graphic display. All of the connection, design, and deployment configuration is accomplished in Oracle JDeveloper.

                                               

Using the BPEL Designer Monitor view in Oracle JDeveloper, you can create the following types of monitors on a BPEL process:

• Activity Monitors capture running time data for BPEL process activities, scopes, and human tasks. Activity Monitors can help identify bottlenecks in the BPEL process.
• Counter monitoring objects capture the date and time when a particular BPEL activity event is encountered within the BPEL process. Counters may be useful for reporting the number of times a particular activity is executed over a period of tim
• Interval monitoring objects capture the amount of time for the process to go from one BPEL activity event to another. Interval monitoring objects can help identify bottlenecks in the BPEL process
•  Business Indicator monitoring objects capture a snapshot of BPEL variables or expressions at a specified activity event in the BPEL process.

When the SOA composite application is deployed, the Oracle BAM data objects corresponding to the BPEL process monitors are created or updated automatically.

Access BPEL Designer Monitor View

1.       Start JDeveloper.

2.       Open Po Processing Application (which is running end to end flow).

3.       Open composite.xml of Po Processing application. Once it open  you able to see composite shown in below diagram.

4.       Double click on   ApproveLargeOrder BPEL Process.

5.       In BEPL Editor, right side tops you able to see Monitor option select Monitor toolbar.

 

6.       In Monitor view, the structure pane displays the Monitoring Objects folder. You can expand the folder to expose the Business Indicators, Intervals, and Counters folders.

Configure Activity Monitors

7.       In the Monitor view of a BPEL process, click Monitoring Configuration in the BPEL Designer tool bar.

8.      In the Monitoring Configuration dialog, select Enable Activity Monitoring, and choose the Mode to configure the level of monitoring.

Types of modes:

• The All Activities option captures start and end time data for every activity in the BPEL process, including individual activities, scopes, and human tasks. An activity starts when the activation event for the activity is begun, and it ends when the completion event is finished. 
•   The Scopes and Human Tasks Only option captures start and end time data for every scope and human task defined in the BPEL process.
• The Human Tasks Only option captures start and end time data for every human task activity defined in the BPEL process.
•  The BPEL Process Only option captures start and end time data for the BPEL process.

9.      You can disable Activity Monitors by deselecting the Enable Activity Monitoring checkbox.

   

10.      In this Example select Mode as Scopes and Human Tasks Only(Based on your requirement you can choose other modes)

11.        Click OK.

12.      Save the application by using Save Button from JDeveloper Toolbar. 

13. deploy the application and test. you can see my next sequence of posts to In-depth implementation,deploy and test the application.