SAP BusinessObjects (BOBJ) Monitoring
Last updated
Last updated
SAP BusinessObjects (BOBJ) monitoring helps check the server’s performance, identify if an application is functioning normally, and monitor the system availability and response time. IT-Conductor provides real-time status and historical trends of servers through performance graphs and reports log, making it easier to manage and troubleshoot any issue.
BusinessObjects rely on connections to the backend or data universes. If you are connected to any SAP System, it will automatically associate with the application in the IT-Conductor service grid. You can track performance metrics from the backend system since they provide data to the BOBJ environment and impacts the service.
You may have one or more enterprise nodes in a cluster. Each node contains servers that essentially process different services such as Web Intelligence, Adaptive Processing Servers, etc.
Busy Threads are also part of the performance metrics, where you can check the utilization of the server’s environment being monitored.
The license key regulates access to particular tasks and applications.
Failed Jobs refer to the number of jobs that failed in the server. Failed jobs cause the most common alerts when the defined threshold value is breached.
The Probe is an area where you can schedule probes to run at specified intervals. The probes often ping different services to ensure the service is up and responding.
Looking into the “Properties” will give you information on how the server is defined. Information such as System ID, which contains the host string and port number, is shown. The role, authentication type, site, and others are also displayed; these are all the inputs after configuring the server in the IT-Conductor platform.
Automated Health is part of the BusinessObject monitoring, which helps monitor various components and services of a particular application. This gives a time-synchronized view of the whole environment using graphical charts and error logs.
