An Introduction to Oracle Business Activity Monitoring (BAM) – Part 3: Dashboard Design

This is the third part of my introduction to Oracle Business Activity Monitoring (BAM). The first part focused on getting the information into a state that could be consumed by BAM.The second part focused on consuming the data into BAM.

So, we’ve gotten to the point where we are producing messages that are being consumed by a data object. At this point, the BAM Composer could be handed over to a business analyst. From here, the business analyst would generally create a Project, add one or more data objects to the project, create Business Queries, create Business Views from the Business Queries and finally assemble the Business Views into Dashboards. In the exercise below, I will cover all of these steps.

Step 1: Create a New Project

  1. Switch to the Designer tab in BAM Composer.
  2. The virtual machine already has a sample project open, Process Analytics v2. Click the down arrow to the right of the project name and select Create.
    bam2-08_new_project
  3. Name the project Payment and set the Description to Payment Activities:
    bam2-09_new_project

Step 2: Add a Data Object to the Project

  1. Click the Data Objects to add the Payment data object:
    bam2-10_data_objects

Step 3: Create a Business Query

Business Queries are used to populate Business Views. We will create a Flat SQL Query to list the incoming requests and a Group SQL Query to count the requests by card type (AMEX, VISA, etc.) For more see Understanding Business Queries.

Incoming Requests

A list of incoming requests.

  1. Click the Business Queries to create a new Flat SQL Query named IncomingRequests.
    bam2-11_incoming_requests
  2. Select the e2e_1201_composite/Payment Data Object.
  3. Select all fields but BEAM_ID, DATAOBJECT_CREATED and DATAOBJECT_MODIFIED.
  4. Use the arrows to order the fields. I’ve ordered mine as follows:
    bam2-12_incomingrequests
  5. Click Save and you’ll see the results of your query:
    bam2-13_incomingrequests

Requests By Type

A count of requests by card type (American Express, Visa, Master Card, etc.).

  1. Click the Business Queries to create a new Group SQL Query named RequestsByType.
  2. Select the e2e_1201_composite/Payment Data Object.
  3. Select COUNT(*) as the Measures (Y-axis).
  4. Select Card Name as the Dimension.
  5. Click Save and you’ll see the results of your query:
    bam2-14_requestsbytype

Requests By Authorization (Optional)

A count of requests by authorization status (Authorized, Denied). This step is informational only, as I don’t use this query in my example going forward.

  • Click the Business Queries to create a new Group SQL Query named RequestsByAuthorization.
  • Select the e2e_1201_composite/Payment Data Object.
  • Select COUNT(*) as the Measures (Y-axis).
  • Select Payment Status as the Dimension.
  • Click Save and you’ll see the results of your query. Note, you can also click the Bar Graph icon to see your data in graph format (this will look more exciting when we add more sample data:
    bam2-15_requestsbyauth

Step 4: Business Views

Business Views are used the create dashboards. Here we will spruce up the Incoming Requests and Requests By Type to our liking. I’ll show some basic examples, but feel free to adjust to your preferences.

Incoming Requests

  1. Click the Business Views to open the create dialog.
  2. Name the Business View IncomingRequests and set the Display Name to Incoming Requests.
  3. Select the Table category and select List as the View Type and click Create:
    bam2-16_incomingrequests_bv
  4. Set the Query to IncomingRequests:
    bam2-17_incomingrequests_bv
  5. Select Properties. Select the Text tab.
    1. Set the Title Text font to Helvetica 14.
    2. Set the Column header text color to Blue.
      bam2-18_properties
    3. Click Apply and Close and Save to see the changes.
      bam2-19_properties
  6. Select Runtime-Interaction.
    1. Select the Active Data tab and Turn this query into a continuous query.
    2. Set Active Data Collapsing to 2 seconds.
    3. Click Apply, Close and Save.
      bam2-20_runtime_interaction

Requests By Type

  1. Click the Business Views to open the create dialog.
  2. Name the Business View RequestsByCardType and set the Display Name to Requests By Card Type.
  3. Select the Pie category and and select the Pie Chart View Type and click Create.
  4. Select RequestsByType as the Query.
  5. Select Properties.
    1. Set the Predefined Style to Alta. Click Apply to see the effect of the changes.
    2. Select the Titles tab and set the Title Text to Helvetica 14. Click Apply to see the effect of the changes.
    3. Select the Slice tab and set the Slice Label to Slice Name and Value. Click Apply to see the effect of the changes.
      bam2-20_slice_label
    4. Select the Legend tab. Set Display Legend to No. Click Apply, Close and Save to see the effect of the changes.

      Your pie chart should look something like the following:
      bam2-21_pie_chart

Step 5: Dashboards

Dashboards are assembled from the Business Views.

  1. Click the Dashboards to open the create dialog.
  2. Name the Dashboard PaymentRequests and set the Display Name to Payment Requests.
  3. Set the Description to A live dashboard of incoming payment requests by card type.
  4. Select Type 4 as the style template and click Create:
    bam2-22_create_dashboard
  5. Drag Incoming Requests to the top pane and Requests By Type to the bottom pane and click Save:
    bam2-23_dashboard
  6. Switch to the Home Tab and open the Payment  Requests Dashboard.
    bam2-24_dashboard

    The dashboard URL can be shared with and bookmarked. The green icon in the top right indicates the business view is active. The table data can also be downloaded.

Step 6: Test

Let’s generate some more activity so we can see the dashboard in action.

  1. In another browser window (leave the dashboard open), open Enterprise Manger Fusion Middleware Control.
  2. Navigate to the Test Web Service page for the ValidatePayment composite.
  3. Expand the Additional Test Options and:
    1. Enable Stress Test.
    2. Set Concurrent Threads to 1.
  4. Load the PaymentInfoSample_Authorized_soap.xml for the Input Arguments. However, change the CardName from AMEX to Visa.
    bam2-25_load
  5. Before clicking Test Web Service, make sure you have the Dashboard open and visible in another window so you can see the dashboard update in real time. The stress test should take 10 seconds to complete as configured. Every 2 seconds (our Active Data Collapsing setting) the dashboard should update. At the conclusion of the test, the dashboard should look something like the following:
    bam2-25_results

Once the foundation is put in place, the directions you can go are kind of limitless.

 

 

Advertisements

One thought on “An Introduction to Oracle Business Activity Monitoring (BAM) – Part 3: Dashboard Design

  1. Pingback: An Introduction to Oracle Business Activity Monitoring (BAM) – Part 1: Message Production | W Brian Leonard

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s