SAP BusinessObjects Monitoring
Last updated
Last updated
SAP BusinessObjects (BOBJ) is a suite of business intelligence (BI) tools and applications designed to help businesses analyze data and make well-informed decisions. These tools encompass a range of functionalities, including reporting, dashboards, data visualization, and data exploration, which collectively enable users to derive insights from their data assets.
Monitoring SAP BOBJ helps maintain the reliability, performance, and security of BI platforms. By continuously monitoring the SAP BOBJ environment, organizations can proactively identify and address potential issues that may impact system availability, responsiveness, or data integrity.
Before configuring an SAP BOBJ system for monitoring in IT-Conductor, follow the instructions below.
Create a new SAP BOBJ monitoring account.
Assign it to the standard "Monitoring Users" user group and "Everyone" group.
To configure SAP BOBJ monitoring in IT-Conductor, follow the instructions below.
Visit and enter your login credentials.
Navigate to Dashboards → Administrator to access the Administrator's Dashboard.
Locate the BusinessObjects Systems actions panel and click the title to access the complete list.
Click the New BusinessObjects System button to start adding a new system for monitoring.
Description - refers to any relevant information about the system being added.
Organization - refers to an administrative structure that defines objects with a common goal or purpose. If you previously created an organization, please select it.
Role - refers to the environment where the system will be used.
Site - refers to a logical object that describes a particular area or location, depending on the context in which it is used.
Auth Type - refers to the authentication type to be used to access the BOBJ system.
Availability Ping - refers to the mechanism used to check the availability of the BOBJ system.
Description - refers to any relevant information about the user account being added.
Application - refers to the name given to the system being added.
Person - refers to the name of the user who is adding the system.
Authentication Type - refers to the authentication type to be used to access the BOBJ system.
Domain - refers to a logical group that contains one or more BOBJ servers and services. Specify the System ID value in this field.
Password - refers to the password of the previously created user.
Retype Password - refers to the same password provided in the Password field.
7. Verify if the system was added to the BusinessObjects Systems actions panel and check its status.
8. Navigate to the service grid and verify if the system was added under the BusinessObjects Systems node.
Select the BOBJ system in the service grid, then click Retrievers. You will be redirected to a page listing all available BOBJ retrievers.
Click Job Executions in the list of retrievers.
In IT-Conductor, you can create threshold overrides with or without a template.
Name - refers to the identifier assigned to the override configuration.
Description - refers to any details about the purpose or functionality of the override.
Target Object Class - refers to the specific type or class of object to which the override settings will apply.
Application Role - refers to the application environment where the override will be used.
Organization - refers to an administrative structure that defines objects with a common goal or purpose. If you previously created an organization, please select it.
Site - refers to a logical object that describes a particular area or location, depending on the context in which it is used.
Object Criteria - refers to specific conditions or criteria used to target and apply the override.
Value Attribute - refers to a specific parameter or attribute associated with an object that can be modified or overridden.
Comments - refers to any additional notes, explanations, or contextual information related to the override.
Scheduling - refers to the specific time frame during which the threshold override is in effect. You can either select a pre-defined schedule under the Schedule dropdown menu or select specific days and define the Start and End times.
Aggregation Interval - refers to a specific period or interval used for consolidating data or events within the BOBJ system.
Consecutive Interval - refers to a specific period during which a series of events or conditions occur continuously without interruption or gaps.
Aggregation - refers to the aggregation method to calculate the key metrics or statistics from collected data.
Warning Value - refers to the Warning limit or threshold set for the override configuration. If selected in the Alert On field, this metric will be utilized.
Alarm Value - refers to the Alarm limit or threshold set for the override configuration. If selected in the Alert On field, this metric will be utilized.
Reset After - refers to the number of minutes after which an active alert will automatically reset or clear once the triggering condition is no longer present.
Alert On - refers to the setting that prompts the system to issue an alert when the Warning Value or the Alarm Value is met or exceeded.
Recovery On - refers to the setting that prompts the system to restore normal operation after the Warning Value or the Alarm Value falls below the specified thresholds.
Select the override template you want to copy on the Failed Jobs Threshold Default Settings Templates page.
To view the availability and performance metrics of a SAP BOBJ system, locate the BusinessObjects Systems node in the service grid.
Availability - refers to the operational state and accessibility of the BOBJ system.
Connection Failures - refer to the events where attempts to establish a connection are unsuccessful.
Heartbeat - refers to the periodic signal sent to the system, enabling real-time detection of system downtime.
Missing Account - refers to the absence of a required user account or resource within the BOBJ system.
Retriever Failures - refer to the errors or issues encountered during the retrieval process of essential data or information within the BOBJ system.
Authentication in SAP BOBJ is critical for ensuring data security, regulatory compliance, and user access control. Organizations can protect sensitive information, prevent unauthorized access, and enforce security policies across their BI environment by effectively authenticating users.
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 service grid. You can track performance metrics from the backend system since they provide data to the BOBJ environment and impact the service.
Crypto keys are essential components of security infrastructure within SAP BOBJ, playing a crucial role in protecting data, securing communications, and verifying the identity and integrity of users and resources within the BI environment.
You may have one or more enterprise nodes in a cluster. Each node contains server-processing services such as Adaptive Job Server, Adaptive Processing Server, and Web Intelligence.
Failed Jobs refers to the number of jobs that failed on the server. IT-Conductor monitors failed job executions in BOBJ by querying for scheduled jobs that couldn't be completed within a specific period.
License keys monitor the expiration of the BOBJ SAP license and their quota of number/types of users.
Probes are where you can schedule probes to run at specified intervals. The probes often ping different services to ensure the service is up and responding.
To view a more detailed analysis of metrics and time-synchronized data, click Health in the service grid, and you will be redirected to the Health Explorer page.
Fill out all the necessary information in the New BusinessObjects System wizard. Once completed, click to add the system.
Gateway - allows communication between the customer's site network and the IT-Conductor cloud platform. Select the previously configured gateway from the dropdown menu. See for more details.
Provide the account information in the New Account screen and click to complete the configuration.
User Name - refers to the user created aligned with the .
Note: The status will remain on Ready for a few minutes. Refresh the panel if needed. If there are configuration issues, such as incorrect connection parameters or an invalid account, the status will remain Ready. Click to display the logs and troubleshoot. If everything is configured correctly, the status will change to In Progress.
In IT-Conductor, you need to activate Job Executions first before creating threshold overrides. Once activated, follow the instructions in .
Click to activate the Job Executions retriever.
Note: Ensure Job Executions retriever is activated. See and follow the instructions if it has not been activated yet.
Navigate back to the BOBJ system in the service grid and select Failed Jobs. Then click on the Failed Jobs page. You will be redirected to the Failed Jobs Overrides page.
To create an override without a template, click on the Failed Jobs Overrides page.
Fill out all the necessary information on the Create New Override for Failed Jobs page. Once completed, click to create the new override.
To create an override using a template, click on the Failed Jobs Overrides page.
Modify the parameters to match your specific requirements, then click to save.
To access a historical view of each of these metrics, click and a pop-up chart will be displayed.
To view more information about the authentication mode, click .
Note: To enable this feature, activate the Jobs Executions retriever in IT-Conductor. See for more details.
