Monitoring
Alert
An alert is a notification generated by the monitoring application, when a user-defined threshold value set for different metrics applied to a watch is breached. You can choose to receive alerts either through email or view on the "Dashboard" page.
19.2.1 Architecture
This section provides a high-level overview of the monitoring architecture and briefly explains the roles the components play. The monitoring architecture is represented graphically below:
603
The high-level components in the architecture are listed below:
• The Platform Java Server (PJS)
• The Java Management Extensions (JMX) agent/server
• MBeans
• JMX Clients
2012-12-12
Monitoring
• The Management consoles
• Trending Database
The monitoring service is hosted on the Platform Java Server. The application is based on JMX technology.
The Monitoring Platform Java Service provides the core services available in the monitoring application.
The Monitoring Platform Java Service provides the following services:
• Provides the JMX agent service.
• Creates MBeans dynamically for the SAP BusinessObjects servers.
• Provides lifecycle management for the MBeans.
• Provides a mechanism for registering new probes.
• Allows users to create complex threshold conditions using the metrics of the servers.
• Provides a threshold notification mechanism and sends alerts.
• Provides a trending function by storing historical data.
The Probe Scheduling Service that is hosted on the Adaptive Job Server manages the running and scheduling of probes. Hence, the Adaptive Job Server should be running for the probes to run.
The monitoring application also exposes a JMX or Remote Method Invocation (RMI) URL end point.
Other enterprise applications such as SAP Solution Manager and IBM Tivoli Monitoring can connect to the monitoring application and access the SAP BusinessObjects metrics by using a JMX Remote
API. The monitoring application uses a dedicated Derby database for storing historical data for the purpose of trending. For information on the trending database schema, see
Trending DB schema
.
19.2.1.1 Trending DB schema
The following Trending Database diagram and table explanations show you the tables where the metric, probe, and watch data will be recorded and how these tables are related.
604 2012-12-12
Monitoring
605
Table 19-1: TREND_DETAILS
This table records information about managed entities, probes, and watches. For example, CUID and metric names.
Description Column name
DetailsId
Primary key
Autogenerated
CUID (64)
MetricName
Type (32)
Name
CUID of the InfoObject (or) the unique id of non-InfoObject
Name of the Metric
Subscription or Metric types
Name of the watch
NOT NULL
NOT NULL
NOT NULL
NOT NULL
Table 19-2: TREND_DATA
This table records the trending data from metrics, watches, and probes. For example, metric value and time.
Column name Description Primary key
DataId
DetailsId
Time
Value
Auto generated
Foreign key
Time at which data was collected
NOT NULL
Value of the metric / subscription
No
Table 19-3: MANAGED_ENTITY_STATUS_DETAILS
This table records the information about subscription breaches and alert delivery information. For example, breach time and alert delivery time.
Column name
StatusDetailsId
DetailsId
Time
AlertType
Description Primary key
Auto generated
Foreign key
Time at which data was collected
NOT NULL
Subscription notification delivery type (for example, email)
No
2012-12-12
