BODS Service Category Status Test
Business Object data services are comprised of a few different kind of services including core service, enterprise information management services and promotion management services.
This test enables reports the status of each of the category of services.
Target of the test : A SAP BODS Node
Agent deploying the test : An internal/remote agent
Outputs of the test : One set of result for the BODS node being monitored.
|
Parameter |
Description |
|---|---|
|
Test period |
How often should the test be executed. |
|
Host |
Host name of the server for which the test is to be configured. |
|
Port |
Enter the port to which the specified host listens. This should be the port at which the web application server hosting SAP BOBI listens. |
|
Monitoring Hosts |
In large SAP environments, SAP BODS installations can have several BI platform server hosts working together in a cluster. A node is a collection of BI platform servers running on the same host and managed by the same Server Intelligence Agent (SIA). One or more nodes can be on a single host. An Adapative Processing Server hosts a lot of BI services and processes non-Object/post processing requests. Multiple APSes may be defined on multiple nodes within a deployment. A single APS acts a primary server to process requests pertaining to the services hosted by the APS from the target SAP BODS. In some environments, eG Enterprise failed to collect metrics from the target BODS continuously. This was because, when the APSes failed over, the APS that was acting as a primary server corresponded to a different BODS node and the eG agent failed to establish connection with the APS that was currently processing the service requests. To ensure that the metrics are collected seamlessly from the target BOBI, the eG agent should be equipped with the IP addresses of the target BOBI node as well as the IP addresses of all the Adaptive Processing Servers associated with the target BODS node. For this purpose, specify a comma-separated list of IP addresses corresponding to the APSes in the MONITORING HOSTS text box. |
|
JMX Remote Port |
Specify the RMI port number of the BOBI monitoring application.To know the RMI port number of the monitoring application, refer to Enabling the Monitoring Application of the SAP BOBI Platform section in How does eG Enterprise Monitor the SAP BOBI Platform? topic in Monitoring SAP Business Objects document. |
|
JNDI Name |
Specify the lookup name for connecting to the JMX connector of the BOBI monitoring application. To know the JNDI name, refer to Enabling the Monitoring Application of the SAP BOBI Platform section in How does eG Enterprise Monitor the SAP BOBI Platform? topic in Monitoring SAP Business Objects document. |
|
JMX User and JMX Password |
Enter the credentials of an enterprise authenticated BOBI user belonging to the default monitoring users group. |
|
Confirm Password |
Confirm the password by retyping it here. |
|
Node Name |
Specify the name of the BOBI node being monitored. |
|
Provider |
This parameter appears only if the Mode is set to JMX. This test uses a JMX Provider to access the MBean attributes of the target Java application and collect metrics. Specify the package name of this JMX Provider in the PROVIDER textbox. By default, this parameter is set to default indicating that this test automatically discovers the JMX provider and report metrics. |
|
Timeout |
Specify the maximum duration (in seconds) for which the test will wait for a response from the server in the TIMEOUT textbox. The default TIMEOUT period is 1000 seconds. |
|
Detailed Diagnosis |
To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:
|
|
Measurement |
Description |
Measurement Unit |
Interpretation |
||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
|
Core services |
Indicates the health state of the Core services |
|
This service category is dependent on the Central Management Server, Adaptive Processing Server, Event Server, Adaptive Job Server, Input File Repository Server and Output File Repository Server. The numeric values that correspond to these measure values are as follows:
Note: By default, this measure reports the Measure Values listed in the table above to indicate the Core Services. In the graph of this measure however, the same is indicated using the numeric equivalents only. |
||||||||
|
Enterprise Information Management Services |
Indicates the health state of the Enterprise Information Management specific adaptive processing server |
|
This measure is used for monitoring an Enterprise Information Management specific instance of the Adaptive Processing Server. The services hosted include those for logging, metadata browsing and viewing and adhoc processing of EIM queries. The numeric values that correspond to these measure values are as follows:
Note: By default, this measure reports the Measure Values listed in the table above to indicate the Enterprise Information Management Services. In the graph of this measure however, the same is indicated using the numeric equivalents only. |
||||||||
|
Promotion Management Services |
Indicates the health state of the promotion specific adaptive job server and adaptive processing server |
|
These servers are used for handling promotion specific job scheduling and processing. The numeric values that correspond to these measure values are as follows:
Note: By default, this measure reports the Measure Values listed in the table above to indicate the Promotion Management Services. In the graph of this measure however, the same is indicated using the numeric equivalents only. |
