On this page:

Related pages:

This section describes the steps to enable metrics collection for the SAP Business Objects (BO) using SNP CrystalBridge® Monitoring.

Prerequisites

  • Java installed on application servers of SAP system that will be used to monitor BO system remotely.
  • If application servers run on Windows, PowerShell must be available.
  • Access rights:
    • On monitored BO system: Central Management Console - Enabling remote monitoring.
    • On SAP system where monitoring is executed - Execute SXPG commands.

Enable Remote Monitoring on Business Objects System

  1. Navigate to Central Management Console of the SAP BO system and log in. The default URL is http://<bo_host>:<port>/BOE/CMC/.

  2. Navigate to the Monitoring Properties. Follow the steps according to your SAP BO version.

    1. From the drop-down menu that is locate at the top, select Applications.
    2. In the tree view, double click Monitoring Application.
    3. Right click Monitoring Application an select Properties.
    1. From the drop-down menu that is locate at the top, select Applications.
    2. In the tree view, double click BI Admin Studio.
    3. Right click BI Admin Studio an select Properties.

  3. Select the option Enable Monitoring Application

  4. Select the option Enable RMI protocol for JMX

  5. Enter the RMI port number. Ensure that the port is accessible from the CrystalBridge® Monitoring central instance.

  6. Enter the RMI JMX agent endpoint URL. This URL will be used to establish communication with the SAP BO system

  7. Create a new user on the SAP BO system to use for communication via JMX. The user needs to be a member of the Monitoring users group (read-only access is sufficient).

Install JMX Connector on SAP ABAP System

You need to install Java middleware on the SAP system with SNP CrystalBridge® Monitoring to monitor the BO system remotely.

  1. Create a new user, for example, DVD_JMX_USER, in transaction SU01 and assign authorization role /DVD/JMX_JCO_RFC to this user. This user will communicate via RFC between the SAP system and the JMX connector.
     

  2. Execute report /DVD/JMX_JCO_SETUP, check Setup JCO service and fill out the required fields. You can use Get default configuration values to populate input fields with default values.

    • JCO server

      • Program ID - the name under which JCo service gets registered on SAP AS Gateway. The default value is DVD_JMX_PROGID.

      • Connection count - value greater than 1 allows parallel outbound processing of server instances. The maximum is 100, and the default value is 10.

      • Worker thread count - defines the maximum number of JCo Server worker threads in the thread pool. To enable parallel outbound processing, use a value greater than 1. It is recommended to use a value of 4 to process a high number of small messages. The maximum value is 100, and the default value is 20.

      • Worker thread min. count - defines the minimum number of JCo Server worker threads for receiving calls from SAP. The default value is 5. If JCo Server is idle, the specified number of minimum threads is kept running in the thread pool.

      • Gateway host - IP address of the gateway host. It is automatically detected for the main SAP AS.

    • Gateway service - port that SAP gateway of SAP AS listens on. It is automatically detected for the main SAP AS.

    • JCO client

      • Client - the number of SAP logon client of the SAP ABAP system where the monitoring is executed.

      • User - SAP user created via SU01 to communicate with JMX connector.

      • Password - the password of the SAP user created in SU01 to communicate with the JMX connector.

      • System number - system instance number of the SAP ABAP system where the monitoring is executed.

      • Peak limit - the maximum number of connections available in the connection pool.

      • Application server host - the fully qualified name or IP address of the application server that hosts the SAP ABAP system. It is recommended to choose the same application server as for deploying of JCo service.

    • Installation properties

      • Installation directory on AS - full directory path where java application for JMX connector and all corresponding files will be copied.

      • Java path on AS - full path to the installation directory of Java on the Application server. It is not required on Windows systems if java is added to the PATH variable.

      • AS name to deploy JCo - the name of the application server on which the JMX connector will be installed.

  3. Press Execute (F8) to save configuration values.

  4. Check Install and start JCO service and execute. This will copy files from the SNP CrystalBridge® Monitoring out-of-box content on the application server and use java to launch the JMX connector.

  5. After execution, select the Check deployment checkbox and execute to ensure that the JMX connector is installed and that it starts.

Add BO System to Monitoring Cockpit and Start Monitoring

You need to add the BO system to the SNP CrystalBridge® Monitoring cockpit for monitoring after the JMX connector is set up and remote monitoring is enabled on the BO system.

  1. Go to transaction /DVD/MON.

  2. Click on Add System and select SAP Business Objects.

  3. Fill out the fields in the following screen:

    • System name - the name of the monitored BO system.

    • Description - a short description of the monitored BO system.

    • Connection ID - custom value. This ID will be set in the configuration file for the JMX connection. It can be the same value as the system name.

    • Service URI - URI of service that can be retrieved in the Central Management Console of the BO system where you enabled remote monitoring.

    • User name - the name of the user that is created on the BO system in the Central Management Console.

    • Password - password of the user that is created on the BO system in the Central Management Console.

  4. Press Check JMX connection. A success message is displayed if the configuration is complete.

  5. Press Generate BOBJ KPIs to open the BOBJ KPI generator program.

    • Replicate KPIs to AppD metrics - automatically creates AppDynamics metric mappings for all generated KPIs of the BO system. If left unchecked, metric mappings can be manually added using transaction /DVD/APPD_CC. See Monitoring Connector Mapping.

      Manual metric selection

      It is recommended to select only relevant BO KPIs to be mapped to AppDynamics metrics. Replicating all the generated BO KPIs as metrics on big installations and production environments can lead to exceeding metric limits on the controller.

    • TEST mode - check this option before executing the program to see the list of KPIs that will be generated from the BO system. Changes are not saved to the database. 

  6. After the program is executed (F8) the output will display the list of all generated KPIs.

  7. Go back (F3) to the system definition screen and Confirm the setup.

  8. The following screen shows the list of all auto-detected servers of the BO system. Make sure that the Monitor flag is selected and press Confirm.

  9. System definition for SAP BO monitoring is added. You can start the monitoring by selecting the system under System landscape and clicking on Start default monitoring in the menu bar. This schedules a periodic background job that collects BO metrics every 5 minutes based on monitoring profile XBO_5MIN.

  10. Proceed with the setup steps described in Replicate Metrics to External System.