Skip to Content

SAP BusinessObjects 4.0 Monitoring Configuration – Part(2)

Hi All,

This is the continuation of my previous blog SAP BusinessObjects 4.0 Monitoring Configuration  SAP BusinessObjects 4.0 Monitoring Configuration – Part(1)

Schedule monitoring probes from the CMC

  1. Log on to the Central Management Console. http://Server:8080/BOE/CMC
  2. Go to Monitoring > Probes

   3. Select the CMS Logon Logoff probe and click on Schedule


     4. When the Schedule options appear, set the probe to run every 3 minutes from the current time to 24 hours later. We want the CMS Logon Logoff probe

           to run every 3 minutes. Go to the Schedule section and set it to run every 3 minutes for the next 24 hours


      5. Select the InfoView probe and set it to run every 5 minutes for the next 24 hours.

      6. You should now see 2 probes set as scheduled from the Probes dashboard.


     7. If the Infoview probe shows a failure, it is probably because the username/password it is using is not correct.

    • Right-click on the probe and select Properties
    • Edit the username/password, Click Save and Close. Right-click on the probe and select Run Now.
    • Click the refresh icon, next to the Enable Auto-Refresh button.
    • If you wish the probe screen to automatically update, select the ‘Enable Auto-Refresh’ button.

Creating a watch

The CMS probe is now scheduled and you want to base a watch on it so it generates an alert if the Logon Logoff action takes longer than 200 milliseconds.

  1. Go to Monitoring > Watchlist


     2. Click on New and define a name, description for your new watch as showed in the screenshot. Set the number of states to Two (OK, Danger) and           check the 2 options Show on Dashboard.


     3. Click on Next

    • Browse the available metrics and select Probes > BI40SIA.CMSLogonLogoff > execution time.
    • On the right panel, set the Danger operator to ‘>=’ and value to 200 (or choose a value that appears just above the current average so that you get some alerts)


     4. Click on Next. Leave the settings to default: alert notifications will be sent every time the threshold is reached and notifications

          will be sent to the ‘Administrator’ or to any user.


     5. Click on Save to save this new watch.

     Alert notification

     We will get the notification when the threshold is reached. To see the alerts when your CMS probe has been running for a few hours

      you may have sent alerts to the Administrator. If required we can cascade the alerts to e-mail recepients as well.

  1. Log on to BI Launch Pad
  2. From the Home Page, notice the new Alerts from the Alerts module – if you have alerts you will see something similar to this.


  3. Click on one of the alerts to view the details


Hope you find this interesting. Thanks for reading.

SAP BusinessObjects 4.0 Monitoring Blogs

SAP BusinessObjects 4.0 Monitoring Configuration – Part(1)

SAP BusinessObjects 4.0 Monitoring Configuration – Part(2)

SAP BusinessObjects 4.0 Monitoring Configuration – Part(3)

You must be Logged on to comment or reply to a post.
  • Thanks Mani for the nice blog. I was looking one for BI4 monitoring and your blog helped me to kick start the setup.


    I have done the setup somehow email notification is not working . Is it working for you ? any other troubleshooting tips for email notfication ?




    • Raj,


      Many Thanks for reading my blog.


      • Have you added your User/UserGroup as a member of Monitoring Users Usergroup?
      • Does SMTP setup has been done for the required servers?
      • Have you setup dedicated APS for your monitoring service?
      • What is the error message you are getting while sending email notification?
      • Try enable tracing on your APS which hosting monitoring service and share us the required screens which enables to troubleshoot the issue further.


      Below SAP Notes could also help you.


      1728800 – User not receiving email alerts for watchlist

      1684257 – How to set alerts for Watchlist in BI 4.0

      1742550 – How to enable alert notifications for the watchlist created in Central                Management Console for Non-Admin Groups.




  • Don’t know if you will continue (part 3), but it could be good to talk about “what means metrics exactly” I don’t found much information.


    Ex: In Dashboardprocessingserver, what mean “Used disk space”.  For me it show 250 Gb…what !!!


    Ex2 : In WebIntelligenceProcessingserver, what mean “CPU Usage _%_”, for me, it show 0 or 1.  What !!!!


    It’s like all Business Intelligence world, lot of information but what mean all this. 

    • Part 3 is on its way Patrick.


      By the way metric is an property of an individual BusinessObjects  servers which you can monitor, probe, watch and analyse.

  • Superb article, sir! What defines a healthstate within the server metric? So I see values ranging from 1 to 4. What exactly is a healthstate comprised of? It sounds generic.

    • Health State

      Highlights the current status of the service:

      • “0” – Indicates that the health of the metric is bad.
      • “1” – Indicates that the health of the metric is deteriorating and needs immediate attention.
      • “2” – Indicates that the health of the metric is good.
        • Hi Cartel,


          I re-read your query and compared with the metrics available in CMC.


          The health status of a watch is determined by its metrics. You would define them as x, y or z. Execution time and passed are the metrics define it for CMS logonlogoff. The healt would be either 0 or 1 for it.