Skip to Content

This quick tutorial is the third in a series. The first two tutorials are available at: 

If you’ve read the first two monitoring tutorials, you should be familiar with BusinessObjects monitoring probes and how they work. In this tutorial we’ll look at how monitoring probes have been designed for integration with enterprise monitoring solutions (such as IBM Tivoli, Microsoft Operations Manager, etc.).

If you look in the monitoring probes configuration file directory (Business Objectsmonitoringprobes) you’ll notice a couple of sets of configuration files with files names like these:

  • template_probe1_4tivoli.xml
  • template_probe1_4mom.xml

When you open one of these monitoring probe configuration files in a text editor, you’ll  see that they are the same as standard monitoring probe configuration files except for a set of ‘connector’ tags, as shown in the following example:

image

What this set of connector tags allow you to do is specify an XSL style sheet, which will format your monitoring probe’s XML based output stream into the output format required by your monitoring solution.

The Monitoring Add-on package comes with two ready-made XSL style sheets (a.k.a “connectors”) – one for IBM Tivoli and one for Microsoft Operations Manager (MOM).  The style sheets (totext4mom.xsl and totext4tivoli.xsl) can be found in your Business Objectsmonitoringconnectors directory. Open them up and take a look.

The great thing about having monitoring probe output in XML format is that if  you happen to be using a monitoring solution other than IBM Tivoli or Microsoft Operations Manager (perhaps you are using an open source monitoring application or even your own home grown solution), you can create your own XSL style sheet to format the monitoring probes’ output stream into whatever output format you require.

A final note about integrating monitoring probes with enterprise monitoring solutions: The BusinessObjects Enterprise Monitoring Guide includes step-by-step examples for deploying a monitoring probe with IBM Tivoli and Microsoft Operations Manager. If you use either of these monitoring solutions, this information will get you started with adding BOE monitoring probes. The Monitoring Guide can be accessed here: BusinessObjects Enterprise XI 3.0 Monitoring Guide

To report this post you need to login first.

8 Comments

You must be Logged on to comment or reply to a post.

  1. Christine Scavarda

    Hi,<br/><br/>I installed the package on Solaris with BO XI 3.1 but nothing works 🙁 I updated monitoring.sh but when I execute: <br/>./monitoring.sh -probefile template_probe1.xml<br/>nothing happhens, I get the prompt and that’s all.<br/>There is anything in the logs directory.<br/><br/>When I try with the Web Application I go tan HTTP 500 error with this :<br/><BEA-101017> <[weblogic.servlet.internal.<br/>WebAppServletContext@fafef2 – appName: ‘monitoring’, name: ‘monitoring.war’, context-path: ‘/monitoring’] Root cause of ServletException.<br/>java.lang.NoClassDefFoundError: com/thoughtworks/xstream/converters/Converter<br/>        at com.businessobjects.monitoring.core.ProbeController.getInstanceFromFile(ProbeController.java:67)<br/>        at com.businessobjects.monitoring.servlet.MonitoringServlet.service(MonitoringServlet.java:103)<br/>        at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)<br/>        at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226)<br/>        at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)<br/>        at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)<br/>        at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)<br/>        at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(Unknown Source)<br/>        at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)<br/>        at weblogic.security.service.SecurityManager.runAs(Unknown Source)<br/>        at weblogic.servlet.internal.WebAppServletContext.securedExecute(Unknown Source)<br/>        at weblogic.servlet.internal.WebAppServletContext.execute(Unknown Source)<br/>        at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366)<br/>        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)<br/>        at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)<br/><br/><br/>Thanks for your Help<br/>

    (0) 
    1. Hi Christine,
      Thanks for your post. I need a little more information about your setup to offer advice. Please email me directly at dan.price@sap.com We’ll post back to the blog once we identify the issue.
      (0) 
      1. Christine Scavarda
        Hi Dan,

        I think I found the solution,  the xstream-1.1.2.jar fiel was missing in my /lib folder of BO XI 3.1 distribution, I don’t know why but I get it from another system install and now it works.

        (0) 
  2. Alexander Schuchman
    Our enterprise tivoli is an older version, so it doesn’t support these probes unfortunately.
    Just giving our two cents since I’m sure other companies also are potentially using old tivoli releases.
    (0) 
    1. Patrice Le Bihan
      The integration point used by the probes is the Universal Agent with a Script Data Provider. I am not 100% sure but I believe it is available on older versions of IBM Tivoli Monitoring. You may want to check with IBM representatives on this.

      As a general rule, any tool that can be fed by the probe script (monitoring.sh or monitoring.bat) will integrate well with the probes.

      (0) 
  3. Raj Shekhar
    Everything except crystal probes runs fine and the XML output is generate indicating success/failure. When the crystal probe for either page/ras is run, it returns blank in command line mode. In web mode, it however returns XML output. I am not sure what could be the problem here. Any help is appreciated.

    Thanks!

    (0) 

Leave a Reply