Databases Reference
In-Depth Information
Defining reports and data required
We are interested in the number of auctions in each state as well as the total value of
auctions in progress. This leads us to the following reporting requirements:
Display current number of auctions in each state
Display value of all auctions in each state
Allow filtering of reports by bidder and seller
Allow filtering of reports by auction end date
These reports will require the following data:
Auction identifier, so that we can correlate status changes back to a
particular auction
Auction state, so that we can track the number of auctions in each state
Current highest bid, so that we can calculate the worth of all auctions
Current highest bidder, so that we can filter reports by a particular bidder
Seller, so that we can filter reports by a particular seller
Auction end date, so that we can filter auctions by completion date
Having completed our analysis, we can proceed to define our data objects, capture
events, and build our reports.
We will follow a middle-out approach to building our dashboard. We will take the
following steps:
1. Define our data within the Active Data Cache
2.
Create sensors in BPEL and map to data in the ADC
3.
Create suitable reports
4.
Run the reports
Defining data objects
Data in BAM is stored in data objects. Individual data objects contain the information
that is reported in BAM dashboards and may be updated by multiple events.
Generally, BAM will report against aggregations of objects, but there is also the
ability for reports to drill down into individual data objects.
 
Search WWH ::




Custom Search