Probes Test
Probes are a critical component of the SAP BOBI’s Monitoring application. Probes monitor different services and simulate the different functionalities of BI platform components. By scheduling probes to run at specified intervals, the system administrator can track the availability and performance of key services provided by BI platform. If these probes run slowly, it can adversely impact the Monitoring application’s ability to ascertain service availability and responsiveness in real-time. Using the Probes test, administrators can quickly isolate probes that are running slower than the rest. This knowledge will help administrators investigate the the cause for the slowness and eliminate it, so that the probes can deliver timely health reports to administrators.
In addition to highlighting slow probes, the Probes test also helps administrators track the results of the tests that probes run and in the process, pinpoints the probes where tests failed. Administrators can then use the Monitoring application to figure out which tests failed and thus identify unavailable/unresponsive services.
Target of the test : A SAP BOBI Node
Agent deploying the test : An internal/remote agent
Outputs of the test : One set of measures for each scheduled probe (both default and custom probes) running in the node. Default probes include ‘BI launch pad’, ‘CMS cache’, ‘CMS DB Connection’, ‘CMS logon & logoff’, ‘CMS ping’, ‘Crystal reports service (processing server) and crystal reports service (report application server).
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. |
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. |
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. |
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. |
Measurement | Description | Measurement Unit | Interpretation | ||||||
---|---|---|---|---|---|---|---|---|---|
Execution time |
Indicates the time taken for this probe to execute. |
Secs |
A high value is indicative of a slow probe. Compare the value of this measure across probes to identify the slowest probe. |
||||||
Has passed? |
Indicates whether/not the test run by this probe passed. |
|
The values that this measure can report and their corresponding numeric values are discussed in the table below:
Note: By default, this measure reports the Measure Values listed in the table above to indicate the whether/not the test run by the node passed. In the graph of this measure however, the same is represented using the numeric values only. |