(DI-1711) BOBJ add-on setup

Owned by Veronika Hunorova (Unlicensed)
Nov 22, 2017
2 min read

General information

SAP Business Object system can be monitored from central instance via JMX connector. The JMX (Java Management Extensions ) technology defines a connector based on RMI. This connector allows you to connect to an MBean in an MBean server from a remote location and view Business Objects server and monitoring metrics. JMX connector is JAVA based and it is implemented in JCo service which runs on SAP application server of Datavard Insights central instance. BO specific collectors are calling JCo service from SAP ABAP to access JMX.

To make SAP BO monitoring up and running the following setup has to be done:

  1. Setup JMX on SAP BO
  2. Setup JCo service on SAP ABAP AS
  3. Setup system for monitoring in Datavard Insights cockpit

 

Setup JMX on SAP Business Object

To use JMX technology and access monitoring metrics on BOBJ system go to BOBJ Central management console. In section Applications double click on Monitoring Application. Check checkbox Enable Monitoring Application, check checkbox Enable RMI protocol for JMX and set port. Port should be accessible from Insights central instance. Remember RMI JMX agent end point URL. It will be used to establish communication with SAP BO system.

Create new user on SAP BO system which will be used for communication via JMX.

The user has to be member of Monitoring users group (read only access is enough).

 

Setup JCo service on SAP ABAP AS

JMX connector is implemented in JAVA as JCo service. The service has to be configured and running before first use. All configuration setup of JCo service for JMX connector has to be done on central instance of Datavard Insights. Execute report /DVD/JMX_JCO_SETUP. Select option Check deployment and execute (F8) it to be sure that JCo service is not already installed and run.

You should get following information

Go back and select option Setup JCo service

All fields of JCo service setup are editable now. Please fill all fields with proper information.

  • Gateway service - port which SAP gateway of SAP AS is listening on. It is automatically detected for main SAP AS.
  • Program ID - name under which JCo service will be registered on SAP AS Gateway. Default value is DVD_JMX_PROGID
  • Connection count - A value of greater than 1 allows parallel outbound processing of server instances. Maximum is 100. 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 you use a value of 4 to process a high number of small messages. The maximum value is 100. 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 are kept running in the thread pool.
  • Gateway host - IP address of gateway host. It is automatically detected for main SAP AS.