Developing and deploying a custom Java probe in BI Platform 4.0: Tutorial & Sample
Considerations before you get started
- For large productive landscapes it’s recommended that you upgrade your BI Platform to SP4 Patch 12, SP6 Patch 1, or SP7. Several corrections were made to improve stability and performance of the Monitoring Service (Adaptive Processing Server). See note 1833881.
- Create a dedicated Adaptive Processing Server to run your Monitoring Services. Best practice is to run no more than two dedicated Monitoring Services (two APS instances) as they work in a Active/Passive cluster. For details on creating a dedicated Adaptive Processing Server, refer to Best Practices for SAPBO BI 4.0 Adaptive Processing Servers
- If you plan to keep historical details about the success or failure of your custom probe, you will need to enable the trending database. For details, see the BI Platform 4.0 Administrator’s Guide.
Health Probe, Diagnostic Probe, or Hybrid Probe
It is important to understand the different types of probes that can be created as they each have different requirements and serve a slightly different function. Additionally, when you are ready to register your probe with BI Platform 4.0, you will need to define the type of probe so that the monitoring service will understand how to execute the probe.
- A health probe generates metrics of data types such as integer, Boolean, or string. An example of a health probe is the default CMS Logon/Logoff probe which checks that a user may successfully logon/logoff the Central Management Server.
- A diagnostic probe generates reports containing current system information. An example of a diagnostic probes is the default Stop/Start server probe. This probe checks all the servers, records the state of each server, restarts the servers and collects information about servers again.
- A hybrid probe functions as both a health probe and a diagnostic probe
Source code walk-through
Step #3 – Your class must be a subclass of AbstractProbe and it must also implement the IHealthProbe interface so that it will inherit the required methods and objects needed for a probe
public class probeHTTP extends AbstractProbe implements IHealthProbe
Step #4 – Initialize a new IProbeInfoObject and invoke the constructors of IProbeInfoObject. You will need this object to get access to the input parameters later.
public IProbeInfoObject probeObject = null;
public probeHTTP(IProbeInfoObject probeInfoObject)
probeObject = probeInfoObject;
Step #5 – You must create an executeHealthProbe method which returns IHealthProbeResult for a health probe. For a diagnostic probe, it must return IDiagnosticProbeResult. Notice that when the probe is executed, the Enterprise session is passed in by the Probe Scheduling Service (Adaptive Job Server). You can use this Enterprise session to access the CMS Infostore so that you can perform actions on the BI Platform (such as query the CMS repository for metrics, start servers, change settings, etc).
public IHealthProbeResult executeHealthProbe(IEnterpriseSession session)
HealthProbeResult probeResult = new HealthProbeResult(getProbeInfoObject());
Socket socket = null;
boolean available = false;
Step #6 – To parameterize your probe you need to create a new java.util.Map object. Call getInputParameters( ) to create a map of the probe parameters that have been selected by the administrator in the Central Management Console (see Step #4). In this example, there are two parameters (Web Server Host Name, Port Number)
Map<String,Object> inputParams = null;
inputParams = probeObject.getInputParameters();
String hostname = (String) inputParams.get(“hostname”);
String portnum = (String) inputParams.get(“portnum”);
int portnumint = Integer.parseInt(portnum);
Step #7 – This example attempts to create a connection to the specified host and port number. If it succeeds, our probe executes probeSucceeded( ). If it fails, an exception is thrown and the probe executes probeFailed( ). The probeResult specifies to the Probe Scheduling Service if the health probe itself was a success or failure.
socket = new Socket(hostname, portnumint);
catch (Exception e)
Compile and register your probe
- Add the required jar files to your CLASSPATH. I have attached my CLASSPATH to this document as an example (classpath.txt). The BI 4.0 Java SDK libraries are located in the directory <BOBJ_HOME>\SAP BusinessObjects Enterprise XI 4.0\java\lib.
- Compile your Java class and export it from Eclipse as a jar file.
- Create a folder named probes in the directory <BOBJHOME>\SAP BusinessObjects Enterprise XI 4.0\java\lib.
- Add your custom jar and it’s dependencies to the new probe directory.
- Restart the Monitoring Service (Adaptive Processing Server) and Probe Scheduling Service (Adaptive Job Server)
- Repeat steps 3,4, and 5 for each node running the Monitoring Service and Probe Scheduling Service
- Register your custom probe as per the BI4 Java SDK Developer’s Guide or via the Central Management Console > Monitoring Application.
- During registration, specify the class name including the package name as com.businessobjects.monitoring.probe.yourClassName.
- Configure the input parameters to match the name and data type as defined in the java.util.Map in your source code.
- For an example, refer to Image A
Schedule the custom probe
- In the Central Management Console browse to Monitoring > Probe tab and locate your new probe.
- Right click on the probe and choose properties then check your input parameters (Image B)
- Schedule the probe to Run Now and see the results (Image C and Image D)