January 10, 2013 6 Comments
The Monitoring Application is a new application in SAP BusinessObjects 4.0. You will find the application in the CMC under Manage. This is the 3rd, and final, article in the series on Monitoring. In Part 1, we covered how to set up the application. Make sure you do this before trying to use the application. In Part 2, we covered how to use the application. Now, in Part 3, we will discuss the creation of the Monitoring universe, so you can track the health of the system over time.
By default, the monitoring trending data are stored in four tables in a Derby (Java) database. However, with SP04, we now have the option to transfer this data to the Audit database. This provides several advantages:
- The Derby tables will only store three months worth of data. The Audit DB tables will store as much data as you want.
- Connecting to the audit tables, to build a universe, is much easier than connecting to Java tables.
Therefore, it is recommended to migrate the data from the Derby tables, to the Audit database. Let’s talk about how to do that.
Migrating the Trending Data
The Trending database contains four tables:
We’ll cover what’s in these tables later. Prior to migrating the trending data from the Derby database to the Audit database, these four tables need to be created in the Audit database. SAP provides the scripts to create the tables. They are on the BusinessObjects server in the following location:
<Parameter Name=”CharSet Table” Platform=”Unix”>datadirect</Parameter>
<Parameter Name=”Driver Name”>SQL (Server|Native Client)</Parameter>
<Parameter Name=”SSO Available” Platform=”MSWindows”>True</Parameter>
- MOT_TREND_DETAILS: Dimension table; stores information about metrics, probes, and watches
- MOT_TREND_DATA: Fact table; collects trend data about metrics watches, and probes, including DateTime and value (By default, values are collected every 15 seconds)
- MOT_MES_DETAILS: Fact table; records information about threshold breaches and alert notifications
- MOT_MES_METRICS: Dimension table; stores information about Watches and the metrics that are part of each Watch
- MetricName: Obviously, this is simply the name of the metric. This will be a dimension object in the universe
- Type: There are three possible types of metrics: “Subscription”, “ManagedEntityStatus”, or “Probe”.
- Name: If the Type is “ManagedEntityStatus”, this will provide the name of the Watch. Otherwise, it will simply contain the same text as the Type, in caps.
- Time: This is the time at which the data was collected. It is a BIGINT or NUMBER or FIXED field.
- Value: This is the value of the metric at the time it was collected.
- MessageKey: If an error is thrown, this will contain the error message key. If it was successful, this will be null. For Watches, it can also contain either “watchEnabled” or
- Time: This is the time at which the data was collected. It is a BIGINT or NUMBER field.
- AlertType: This represents the notification delivery type. It is a SMALLINT or NUMBER data type.
- Name: This is the name of the watch.
As you can see, the universe will be fairly simple. Of course, you may want to create some filter objects, so that you can do reporting based on specific historical periods, such as current month, current year, etc.
I hope you have found this series as useful as I have, in researching it and learning it all. Let me know if you learn anything that I haven’t covered here.