BAM Calculated Fields

In my previous blog, I have made a start with the study of the BAM components. I have started with the Data Objects (BAM Data Objecten). In this post I will continue with them.

1-project-dataobjects

In order to be able to make the desired dashboard for the POC, there is a need for yet a number of calculated fields. These calculated fields are defined as part part of the Data Object. Several of the required calculated fields are also present in the standard Data Objects. These can be taken over. Because the field names do not match directly these must still be adapted. In the standard Data Objects are all calculated fields defined as attribute. To give them some context I have defined some of them as dimensions and measure. But this affects the different queries where this is not immediately obvious. It is stated at the different query types but it is rather unclear.  Continue reading

Advertisements

BAM Data Objecten

In previous posts, I’ve focused on the components around BAM (starting with Impact of ACM Implementation on BAM). Now is will start with a number of posts that are related to the components of BAM. Hereby I will use the image below. The image comes from the BAM documentation of Oracle. This post will mainly be about Data objects.

1-project-dataobjects

From the Oracle Documentation (https://docs.oracle.com/middleware/1213/bam/bam-user-guide/GUID-22D3700F-121C-4FCC-B0EE-A5AA54689CC7.htm#BAMUG98195)

A BAM data object models data for use within BAM. It contains the data to be monitored. The data can be saved in raw format in a database or in an external table. The data can also be a stream from an ongoing activity. Continue reading