In the previous tutorial (BusinessObjects Enterprise Monitoring Probes Quick Tutorial) we deployed the BusinessObjects Enterprise Monitoring probes and ran a monitoring probe from the command line. In this tutorial, we'll run a monitoring probe in web mode (i.e. run a probe through a browser). Again, we're working on a Windows system. **For UNIX instructions, see the Monitoring Guide.
To run the monitoring probes in web mode, you need to perform some additional configuration after deploying the Monitoring Add-On. So, let's get into it:
The first configuration step is to update the monitoring.war file. To do this, you must run a script (updateWAR.bat) that will update the monitoring.war file with BusinessObjects Enterprise libraries. All of the files you need are already on your system (deployed when you installed the Monitoring Add-On package).
To update the monitoring.war file:
1. Locate the updateWar.bat file in the monitoring directory under
your BusinessObjects root installation directory.
2. Open the updateWar.bat file in a text editor and ensure that the BOE_HOME
variable is set to your BusinessObjects root installation directory.
For example, on Windows, the default setting in the UpdateWar.bat file
is as follows:
rem ---- BOE_HOME : root folder of your Business Objects Enterprise installation
set BOE_HOME=C:Program FilesBusiness Objects
(If you installed BusinessObjects to the default directory, you don't have to change anything here!)
3. Save and exit the file.
4. Open and command window, navigate to the monitoring directory, and run updateWAR.bat file.
Next, you need to deploy the monitoring.war file:
The following instructions are for a BusinessObjects Enterprise Tomcat
installation on Windows and assume the following default installation directory
for Tomcat: C:Program FilesBusiness ObjectsTomcat
1. Stop the Tomcat service.
2. Copy the monitoring.war file from C:Program FilesBusinessObjectsBusinessObjects Enterprise 12.0javaapplications to
C:Program FilesBusiness ObjectsTomcatwebapps
3. Restart the Tomcat service.
4. Open a browser and logon to the following URL:
http://servername:serverport/monitoring
where servername:serverport are your web application server name and port number. The following web page should appear:
In the previous tutorial you configured the CMS Logon Logoff probe configuration file. You should now be able to click on the link for CMS Logon Logoff probe to have it run successfully. The output is returned to your browser and will appear similar to the following:
Note: To run the other probes, you will have to update the configuration files for those probes.
A few extra bits of information about running probes in web mode:
- You will want to ensure that the monitoring.war file is deployed to the same web application server where InfoView is deployed.
- Monitoring probes should work with all web application servers supported
by BusinessObjects Enterprise but have only been tested with Tomcat, Web Logic, and WebSphere. The Monitoring Guide includes instructions for these three application servers. - Deployment of the monitoring.war file follows the standard procedure for BusinessObjects web component deployment. If you use a different web server than those mentioned above, refer to the web component deployment instructions in the BusinessObjects Enterprise Installation Guide.
- Because BusinessObjects libraries are updated when a BusinessObjects FixPack or Service pack is applied, the monitoring.war file must be updated and redeployed to your web application server each time you upgrade your BusinessObjects system.
- Some monitoring probe users have customized the monitoring probe web page to only show the probes they run in their environment. Quite easy to do and something you might consider for your monitoring implementation.
1 Comment
