BUSINESS OBJECTS ENTERPRISE XI

You can read the recommendations in the user guide, the technical guide or the installation guide for BUSINESS OBJECTS ENTERPRISE XI 3.0. You'll find the answers to all your questions on the BUSINESS OBJECTS ENTERPRISE XI 3.0 in the user manual (information, specifications, safety advice, size, accessories, etc.). Detailed instructions for use are in the User's Guide. User manual BUSINESS OBJECTS ENTERPRISE XI 3.0 User guide BUSINESS OBJECTS ENTERPRISE XI 3.0 Operating instructions BUSINESS OBJECTS ENTERPRISE XI 3.0 Instructions for use BUSINESS OBJECTS ENTERPRISE XI 3.0 Instruction manual BUSINESS OBJECTS ENTERPRISE XI 3.0

Manual abstract: Business Objects owns the following U.S. @@@@@@All other names mentioned herein may be trademarks of their respective owners. Business Objects products in this release may contain redistributions of software licensed from third-party contributors. Some of these individual components may also be available under alternative licenses. A partial listing of third-party contributors that have requested or permitted acknowledgments, as well as required notices, can be found at: http://www.businessobjects.com/thirdparty 2008-12-04 Third-party Contributors Contents Chapter 1 Preface 7 About this guide......8 Comments welcome....8 Chapter 2 Developing a monitoring strategy 9 Determining which components to monitor......10 Performance goals and service level agreements (SLAs)....11 BusinessObjects architecture...12 Surveying end users...

...14 Interviewing system architects and administrators.....15 Components recommended by BusinessObjects..16 Defining metrics, targets, and monitoring activities....17 Defining monitoring responses.....20 Integrating monitoring probes into your strategy....20 Staging your monitoring implementation.....21 Chapter 3 BusinessObjects monitoring probes 23 Introduction to monitoring probes......24 Monitoring probes overview....26 Deploying monitoring probes.

...29 Deploying the monitoring probes package on Windows.. 30 Deploying the monitoring probes package on UNIX...31 Deploying the monitoring.war file..32 Configuring monitoring probes for authentication......38 Running monitoring probes.....40 Running a monitoring probe in command line mode...40 BusinessObjects Enterprise XI Release 2 Monitoring Guide 3 Contents Running a monitoring probe in web mode... 42 Monitoring probe attributes and parameters 44 Monitoring probe output

.49 Specifying probe attributes and parameters dynamically.....52 Working with monitoring probes....53 User account guidelines for running monitoring probes......53 Running probes in command line mode versus web mode. 54 Defining performance measures for monitoring probes..55 Defining monitoring probe execution frequency.....56 Security and audit considerations......57 Monitoring the Central Management Server (CMS) and authentication servers...57 Monitoring report engines and data sources...

.58 Probe failure......60 Monitoring probe connectors and probe integration....61 Using server groups to monitor individual BusinessObjects Enterprise services.....62 Monitoring probe limitations and known issues.....63 Uninstalling monitoring probes. 65 Uninstalling monitoring probes on Windows 65 Uninstalling monitoring probes on UNIX

.65 Chapter 4 Monitoring BusinessObjects using system and application tools 67 Chapter 5 Monitoring BusinessObjects with IBM Tivoli 71 Configuring Tivoli to monitor a BusinessObjects application metric....72 Configuring Tivoli to monitor BusinessObjects using a probe... 80 Preparing a probe configuration file (Tivoli)..80 Preparing the agent metafile....82 Configuring Tivoli to run a monitoring probe....84 4 BusinessObjects Enterprise XI Release 2 Monitoring Guide Contents Chapter 6 Monitoring BusinessObjects with Microsoft Operations Manager (MOM) 89 Installing a MOM agent on a BusinessObjects server.....90 Configuring MOM to monitor a BusinessObjects application metric.....91 Create a rule group for BusinessObjects Enterprise application metrics... 91 Creating a data provider

.92 Configuring monitoring for an application metric... 93 Configuring MOM to monitor BusinessObjects using a probe...98 Creating a rule group for monitoring probes....98 Preparing a probe configuration file (MOM)....100 Inputting the probe response script.. 101 Specifying the Event Rule and Data Provider 103 Viewing probe events in the MOM Operator Console...108 Chapter 7 Components and metrics reference 113 BusinessObjects Enterprise components and metrics...114 Web Application Server components and metrics.....120 System level components and metrics......121 Database components and metrics.

.124 Availability monitoring example......124 Chapter 8 Monitoring probe reference 129 CMS Logon Logoff probe...130 Crystal Reports service through Page and Cache Server probe... 131 Crystal Reports Service through Report Application Server 134 Desktop Intelligence Service probe..136 Web Intelligence Service probe... 138 CMS ping probe

..141 BusinessObjects Enterprise XI Release 2 Monitoring Guide 5 Contents CMS cache probe....142 CMS database connection probe....144 Appendix A Get More Help 147 6 BusinessObjects Enterprise XI Release 2 Monitoring Guide Preface 1 1 Preface About this guide About this guide The objective of this guide is to provide information about developing and implementing a monitoring solution for BusinessObjects Enterprise. Information includes guidelines and recommendations for developing a monitoring strategy, usage information for BusinessObjects monitoring probes, and instructions for implementing a monitoring solution using system and application tools, IBM Tivoli, and Microsoft Operations Manager. Comments welcome Your feedback is important to us. You can send your comments about this guide to: mailto:jc. raveneau@sap.com 8 BusinessObjects Enterprise XI Release 2 Monitoring Guide Developing a monitoring strategy 2 2 Developing a monitoring strategy Determining which components to monitor This section of the guide describes a process for developing a monitoring strategy that includes: Determining which components to monitor Defining metrics, targets, and monitoring activities Defining monitoring responses Integrating BusinessObjects monitoring probes into your strategy Implementing your monitoring solution in stages Note: If your requirement is to quickly implement a basic monitoring solution, it is recommended that you start with availability metrics for key components of your system. Components recommended by BusinessObjects on page 16 describes key components for a typical BusinessObjects Enterprise system. Staging your monitoring implementation on page 21 provides information about implementing availability monitoring as a first step. The Availability monitoring example on page 124 shows components, metrics, targets, and monitoring activities for an availability monitoring solution. Determining which components to monitor The first step in developing a monitoring strategy is determining which system components to monitor. The diagram below shows information sources you can draw upon to identify and prioritize system components. 10 BusinessObjects Enterprise XI Release 2 Monitoring Guide Developing a monitoring strategy Determining which components to monitor 2 Recommendations for how to use each source of information are provided in the following topics: Performance goals and service level agreements (SLAs) on page 11 BusinessObjects Enterprise components and metrics on page 114 Surveying end users on page 14 Interviewing system architects and administrators on page 15 Components recommended by BusinessObjects on page 16 Performance goals and service level agreements (SLAs) Performance goals are commonly defined in Service Level Agreements (SLAs) between IT departments and business units.

The following list includes examples of performance goals that you may find in a typical SLA: Availability schedules (e.g. 24/7 availability with planned system outages for maintenance) User login wait time (e.g. 7 seconds maximum wait time) Availability of report outputs (e.g. report output refreshed daily by 6AM) Maximum wait times for viewing a report (e. g. 10 seconds for simple report) Performance goals can often be broken down into the system and application components involved in delivering a particular service to end users. For example, the process behind viewing a BusinessObjects Web Intelligence report may depend on the following system and application components: BusinessObjects Enterprise XI Release 2 Monitoring Guide 11 2 Developing a monitoring strategy Determining which components to monitor Web application server hardware and software Authentication server hardware and software BusinessObjects Enterprise server hardware BusinessObjects Enterprise application components: Web Intelligcomponents require monitoring. For example, System Architects may be able to help answer the following types of questions: What type of load is the system designed for (e.g. how many concurrent active users and simultaneous requests can system components support?) Which components are at risk if load increases? Which components are low risk? For example, is network bandwidth a low risk component? Are there system dependencies that may not be obvious? Are there single points of failure in the system (i.e. systems or components that have no redundancy) Which machines are likely to require additional CPU resource, memory, or disk space in the near future? System Administrators may be able to provide the following types of information: A history of system performance including previous trouble spots Insight into application components or information flows BusinessObjects Enterprise XI Release 2 Monitoring Guide 15 2 Developing a monitoring strategy Determining which components to monitor System usage patterns including peak usage times Components recommended by BusinessObjects For typical BusinessObjects Enterprise deployments that include Crystal Reports, Web Intelligence, and Desktop Intelligence applications, the components recommended for monitoring are outlined in the diagram below. Components include: BusinessObjects Enterprise components System level components Web application server (WAS) components Database components Your system components may be a subset of the recommended components or may include additional components. For example, you may have custom applications or other BusinessObjects applications you want to include in your monitoring solution. 16 BusinessObjects Enterprise XI Release 2 Monitoring Guide Developing a monitoring strategy Defining metrics, targets, and monitoring activities 2 Information about recommended components is provided in the following reference topics: BusinessObjects Enterprise components and metrics on page 114 Web Application Server components and metrics on page 120 System level components and metrics on page 121 Database components and metrics on page 124 Defining metrics, targets, and monitoring activities After you identify the components you want to monitor, the next step is to establish metrics, targets, and monitoring activities for each component. Metrics are used to measure the health of a component. The metrics you define depend on the components you are monitoring and your requirements. Examples of metrics include user login time, query execution time, CPU usage percentage, availability status for a system service, etc. BusinessObjects Enterprise XI Release 2 Monitoring Guide 17 2 Developing a monitoring strategy Defining metrics, targets, and monitoring activities A target is an expected result for a metric. For example, your business may require that a system login action take no more than 6 seconds or that average CPU usage on your servers is below 85 percent. A result that does not meet a target may indicate a problem. Defining targets often requires that measurements be taken over time to establish an acceptable result range. A `monitoring activity' defines how and when data is collected for a metric. For example, you may decide to collect user login data using an automated script that performs a login action every few minutes, or you may use a monitoring tool to poll your system for CPU usage metrics at a specified interval. The following tables provide examples of metrics, targets, and monitoring activities for a BusinessObjects service (CMS.exe), a web application server, system CPU, and a database. Note: Targets and monitoring activities, including execution and polling frequency, will differ from system to system. For example, you may want to poll your system less frequently if you are concerned about impacting system performance. BusinessObjects component (CMS. exe): Metric Target Monitoring activity Ping every 2 minutes Perform login action every 5 minutes Poll system every 30 seconds Poll system every 30 seconds Poll system every 30 seconds CMS service availabil- 24/7 ity CMS login time CMS CPU usage CMS Disk read time CMS Disk write time < 6 seconds < 30% usage < 95% usage < 5% usage Web application server component 18 BusinessObjects Enterprise XI Release 2 Monitoring Guide Developing a monitoring strategy Defining metrics, targets, and monitoring activities 2 Metric Availability Response time Target 24/7 < 6 seconds Monitoring activity Ping server every 2 minutes Send HTTP request every 5 minutes System component (CPU): Metric Target Monitoring activity Poll system every 30 seconds Poll system every 30 seconds Poll system every 30 seconds Poll system every 30 seconds Poll system every 30 seconds Average CPU utiliza- < 85% usage tion User CPU System CPU Run queue I/O wait time < 90% usage < user CPU < 2 per CPU < 30% Database component Metric Availability Response time Target 24/7 < 6 seconds Monitoring activity Ping server every 2 minutes Run a database query every 5 minutes For components recommended for monitoring by BusinessObjects, metrics and targets are outlined in the following topics: BusinessObjects Enterprise components and metrics on page 114 Web Application Server components and metrics on page 120 System level components and metrics on page 121 Database components and metrics on page 124 BusinessObjects Enterprise XI Release 2 Monitoring Guide 19 2 Developing a monitoring strategy Defining monitoring responses Defining monitoring responses After you define metrics, targets, and monitoring activities, the next step is to define responses if monitoring results do not meet expected targets.

The response you define depends on the metric. For metrics related to availability, you may chose to raise an e-mail alert to initiate immediate action. For less critical metrics, it may be more appropriate to log results to a report that is reviewed weekly by a system administrator. The following table shows example responses for metrics used to measure the health of the BusinessObjects CMS service (CMS. exe). In this example, the response for the availability metric is to raise an e-mail alert after three consecutive failed attempts. For login time, CPU, and disk metrics, data is logged to a report. Metric Target Monitoring activi- Response ty Ping every 2 minutes Perform login action every 5 minutes E-mail notification after 3 consecutive failed attempts Log data to report CMS service 24/7 availability CMS login time CMS CPU usage CMS Disk read time CMS Disk write time < 6 seconds < 30% us- Poll system every age 30 seconds < 95% us- Poll system every age 30 seconds < 5% usage Poll system every 30 seconds Log data to report Log data to report Log data to report Integrating monitoring probes into your strategy BusinessObjects monitoring probes are a set of SDK-based scripts you can use to monitor components of your BusinessObjects Enterprise system. 20 BusinessObjects Enterprise XI Release 2 Monitoring Guide Developing a monitoring strategy Staging your monitoring implementation 2 With BusinessObjects monitoring probes you can: Simulate end user workflows including user login actions and report execution for Web Intelligence, Desktop Intelligence, and Crystal Reports applications. Test availability, functionality, and performance of BusinessObjects services Test the BusinessObjects Central Management Server (CMS) core functionality, CMS cache service, and CMS database connection Test your web application server by running probes in web mode (through a browser) Test Windows AD or LDAP authentication services by running probes under a user account that requires authentication Monitoring probes, which can be run from a command line or web browser, can be quickly integrated into any monitoring strategy to provide a means of monitoring BusinessObjects components. Probes are also designed with XML-based input and output streams that allow for integration with proprietary or industry standard monitoring tools such as IBM Tivoli or Microsoft Operations Manager. The next section of the guide provides in-depth information about deploying, running, and working with BusinessObjects monitoring probes. Related Topics Introduction to monitoring probes on page 24 Deploying monitoring probes on page 29 Working with monitoring probes on page 53 Monitoring BusinessObjects with IBM Tivoli on page 71 Monitoring BusinessObjects with Microsoft Operations Manager (MOM) on page 89 Staging your monitoring implementation It is generally recommended that monitoring be implemented in stages. Your monitoring requirements may dictate a different approach, but as a guideline the following staged implementation is recommended: BusinessObjects Enterprise XI Release 2 Monitoring Guide 21 2 Developing a monitoring strategy Staging your monitoring implementation Stage 1: Availability monitoring Availability monitoring is defined as monitoring availability of BusinessObjects services and core system components. Availability monitoring can largely be achieved through process based monitoring (to ensure the process/service is "alive") and the use of BusinessObjects monitoring probes. For an example of availability monitoring, see Availability monitoring example on page 124. Stage 2: Stability monitoring Stability monitoring adds metrics for key system indicators that help you detect early signs of system instability. For example, in this stage you might add monitoring for CPU, memory, and disk usage by BusinessObjects services. Key indicators may differ for your system but the goal is the same, which is to add metrics to your monitoring solution that allow you to react before an outage occurs. Stage 3: Performance monitoring In this stage, a wider range of system metrics are added to the monitoring solution. The goal is to use a wide array of data from system metrics, monitoring probes, and key indicators to better understand how system components interact, where bottlenecks occur, and how sizing and tuning parameters can be adjusted to improve or maintain system performance. 22 BusinessObjects Enterprise XI Release 2 Monitoring Guide BusinessObjects monitoring probes 3 3 BusinessObjects monitoring probes Introduction to monitoring probes Introduction to monitoring probes BusinessObjects Enterprise monitoring probes provide you with the ability to monitor your BusinessObjects system using simulated application workflows which are run through SDK-based scripts. Monitoring probes are provided in a Monitoring Add-on package that is distributed as a.zip file for Windows deployments and a tar.gz file for UNIX deployments. The package is available for download from the Business Objects Labs website at: http://labs.businessobjects.com/enterprise_moni toring/ The files required to run monitoring probes are deployed to your system when you extract the Monitorig Add-on package to your BusinessObjects root installation directory. There are eight monitoring probes you can use to monitor different aspects of your BusinessObjects system: CMS Logon Logoff probe Crystal Reports Service through Page and Cache Server probe Crystal Reports Service through Report Application Server probe Desktop Intelligence Service probe Web Intelligence Service probe CMS Ping probe CMS Cache probe CMS Database Connection probe Monitoring probes are described in the Monitoring probes overview on page 26. Running a monitoring probe involves executing a monitoring probe command with the appropriate attributes and parameters. The monitoring probe command is monitoring.bat on Windows systems and monitoring.sh on UNIX systems. You can run a monitoring probe from a command line (command line mode) or from within a URL (web mode). All monitoring probes share the same attributes which include user, password, system, authtype, and classname. Monitoring probes that run against Crystal Reports, Web Intelligence, and Desktop Intelligence report engines include document ID, document name, document refresh, and file export parameters. 24 BusinessObjects Enterprise XI Release 2 Monitoring Guide BusinessObjects monitoring probes Introduction to monitoring probes 3 Attributes and parameters can be defined dynamically or in an XML-based configuration file that is called when a monitoring probe is run. The following is an example of a monitoring probe configuration file: <probeconfig user='bobjuser' password='bobjpassword' sys tem='servername' authtype='secenterprise' classname='probecr PageServer'> <!-- Uncomment one of the search options: cuid, docid, name-> <!-- Enter in the correct value afterwards--> <!-- CUID identifier for document--> <!-<param type='java.

lang. String' value='ashedjiwzsbamtwnfiwgybs' /> --> <!-- DOCID identifier for document--> <!-<param type='int' value='656' /> --> <!-- NAME of document--> <param type='java.lang.string' value='mail Labels' /> <!--Document display options--> <!-- REFRESH document select true or false --> <param type='boolean' value='false' /> <!-- PDFEXPORT document select true or false --> <param type='boolean' value='false' /> </probeconfig> Monitoring probe output is an XML-based data stream with information that includes a success flag, execution duration, and error description (if an error is encountered). The following screen capture shows output from a monitoring probe run in web mode: BusinessObjects Enterprise XI Release 2 Monitoring Guide 25 3 BusinessObjects monitoring probes Introduction to monitoring probes XML based input and output streams are intended to provide flexibility for integrating monitoring probes with industry-standard and proprietary monitoring solutions. Related Topics Monitoring probe attributes and parameters on page 44 Running a monitoring probe in command line mode on page 40 Running a monitoring probe in web mode on page 42 Monitoring probes overview The following table describes the current set of monitoring probes and the application workflows they simulate. 26 BusinessObjects Enterprise XI Release 2 Monitoring Guide BusinessObjects monitoring probes Introduction to monitoring probes 3 Monitoring probe CMS Logon Logoff Description Tests the availability of the Central Management Server (CMS) and the ability of users to log on to the system through client applications. The probe logs on a single user, tests session validity, and logs off the user. Tests the availability of the Crystal Reports service through Crystal Reports Page Servers and Cache Servers. Using the Crystal Reports Page and Cache Servers, the probe opens a report, refreshes the report, optionally exports the report to PDF format, and closes the report. Tests the availability of the Crystal Report service through the Report Application Servers. Using the Report Application Servers, the probe opens a report, optionally exports the report to PDF format, and closes the report. Tests the availability of the Desktop Intelligence service through Desktop Intelligence Report Servers. The probe opens a Desktop Intelligence document, refreshes it, optionally exports the document to XLS and PDF format, and closes the document. Tests the availability of the Web Intelligence service through Web Intelligence Report Servers. The probe opens a Web Intelligence document, refreshes it, optionally exports the document to XLS and PDF format, and closes the document. Crystal Reports service through Page and Cache Server Crystal Reports service through Report Application Server Desktop Intelligence Service Web Intelligence Service BusinessObjects Enterprise XI Release 2 Monitoring Guide 27 3 BusinessObjects monitoring probes Introduction to monitoring probes Monitoring probe CMS ping Description Sends an empty query to the CMS. The test is considered successful if the CMS returns a parse failure error. Because query parsing is part of CMS core functionality, the test is expected to complete quickly. Tests the availability and health of the CMS cache by executing the following query: select SI_NAME from CI_SYSTEMOBJS where SI_ID=4 CMS cache This query returns the system InfoObject that contains the CMS cluster name. After a warmup period, it is expected that the CMS retrieves the system InfoObject from the cache rather than the repository database. If the query fails, the cache may not be functioning properly or the cluster definition may be incorrect. CMS database connection Tests the availability of the repository database by executing the following query: select SI_NAME from CI_SYSTEMOBJS where SI_OBTYPE=13 This query returns the system InfoObject which contains the CMS cluster name. The CMS retrieves the system InfoObject from the repository database. If this query fails there may be a connection problem between the CMS server and repository database. Note: Crystal Reports, Desktop Intelligence, and Web Intelligence probes require a report to run whereas CMS related probes do not. Probes that use reports have report related parameters. 28 BusinessObjects Enterprise XI Release 2 Monitoring Guide BusinessObjects monitoring probes Deploying monitoring probes 3 Deploying monitoring probes Monitoring probe deployment includes one or more of the steps described in the following table: Deployment step Description Step 1: Deploying the monitoring Deploying the monitoring probes package probes package (on Windows or is required to run monitoring probes. After UNIX). deploying the monitoring probes package to your system, you can run monitoring probes in command line mode. After deploying the monitoring probes package, you have the option of deploying the monitoring. war file which allows you to run monitoring probes through a web browser (web mode). Step 2: Deploying the monitor ing.war file To deploy the monitoring.war file, you must: 1. Update the monitoring.war file 2. Deploy the monitoring.war file to your web application server. If you do not plan to use monitoring probes in web mode, you can skip this step. Step 3: Configuring monitoring probes for authentication If you want to use monitoring probes with Windows AD or LDAP authentication, you must perform additional configuration steps. If you do not plan to run monitoring probes with Windows AD or LDAP authentication, you can skip this step. Related Topics Deploying the monitoring probes package on Windows on page 30 Deploying the monitoring probes package on UNIX on page 31 BusinessObjects Enterprise XI Release 2 Monitoring Guide 29 3 BusinessObjects monitoring probes Deploying monitoring probes Deploying the monitoring.war file on page 32 Configuring monitoring probes for authentication on page 38 Deploying the monitoring probes package on Windows Monitoring probes require Java Development Kit (JDK) 1.4.2 or 1.5.1. If you are using a BusinessObjects Enterprise Java application (e.g. Java InfoView), it is recommended that you use the same JDK for the monitoring probes. Deploying the monitoring probes package on Windows involves extracting the monitoring probes package (monitoring.zip) to the root directory of your BusinessObjects installation. 1. Extract the contents of the monitoring.zip file to the BusinessObjects root installation directory. The default BusinessObjects root installation directory is: X:\Program Files\Business Objects\, where X: is the system drive. Extracting the contents of the monitoring.zip deploys the following: a monitoring.

jar file to <BOE_INSTALL_DIR>\common\3.5\java\lib a monitoring. war file to <BOE_INSTALL_DIR>\BusinessObjects Enterprise 11.5\java\applications a monitoring folder to <BOE_INSTALL_DIR> (the BusinessObjects root directory). The <BOE_INSTALL_DIR>\monitoring directory will appear as follows in Windows Explorer: 30 BusinessObjects Enterprise XI Release 2 Monitoring Guide BusinessObjects monitoring probes Deploying monitoring probes 3 2. Locate the monitoring.bat file in the <BOE_INSTALL_DIR>\monitoring directory. Open the file in a text editor. 3. In the monitoring.bat file, ensure that the values for the BOE_HOME and JAVA_DIR variables reflect your environment. BOE_HOME must be set to your BusinessObjects root installation directory. JAVA_DIR must be set to the JDK root installation folder. The default settings appear as follows: rem ---- BOE_HOME : root folder of your Business Objects Enterprise installation set BOE_HOME=C:\Program Files\Business Objects rem ---- JAVA_DIR : root folder of your JDK set JAVA_DIR=%BOE_HOME%\j2sdk1.4.2_08 rem set JAVA_DIR=%JAVA_HOME% 4. Save and exit the file. Deploying the monitoring probes package on UNIX Monitoring probes require Java Development Kit (JDK) 1.4.2 or 1.5.1. See the If you are using a BusinessObjects Enterprise Java application (e.g. Java InfoView), it is recommended that you use the same JDK for the monitoring probes. BusinessObjects Enterprise XI Release 2 Monitoring Guide 31 3 BusinessObjects monitoring probes Deploying monitoring probes Deploying the monitoring probes package on UNIX involves extracting the contents of the monitoring probes package (monitoring.tar. gz) to the root directory of your BusinessObjects installation. 1. Copy the BusinessObjects monitoring package (monitoring.tar.gz ) to the BusinessObjects Enterprise root directory. 2. In the BusinessObjects Enterprise root installation directory, unpackage monitoring.tar.gz using the following command: gunzip monitoring.tar.gz tar -xvf monitoring.tar Unpackaging the monitoring.tar.gz deploys the following: a monitoring.jar file to bobje/lib a monitoring. war template file to bobje/enterprise115/java/ap plications a monitoring folder under the bobje directory 3. Locate the monitoring.sh file under bobje/monitoring and open the file in a text editor: vi monitoring.sh 4. In the monitoring.sh file, ensure that the values for the BOE_HOME and JAVA_HOME variables reflect your environment. BOE_HOME must be set to your BusinessObjects root installation directory. JAVA_HOME must be set to the JDK root installation folder. The default settings appear as follows: BOE_HOME="/apps/xir2" JAVA_HOME="{BOBJE_DIR}/jdk" 5. Save and exit the file. Deploying the monitoring.war file If you want to use the BusinessObjects monitoring probes in web mode, you must perform the following steps after you deploy the monitoring probes package to your system: Step 1: Update the monitoring.war file, as described in Updating the monitoring.war file on page 33. 32 BusinessObjects Enterprise XI Release 2 Monitoring Guide BusinessObjects monitoring probes Deploying monitoring probes 3 Step 2: Deploy the updated monitoring. war file to your web application server. Refer to the deployment instructions for your web application server: Deploying the monitoring.war file to Tomcat on page 35 Deploying the monitoring.war file to WebLogic on page 36 Deploying the monitoring.war file to WebSphere on page 37 Note: The monitoring. war should be deployed to the web application server where InfoView is deployed. Monitoring probes should work with all web application servers supported by BusinessObjects Enterprise but instructions are only provided for web application servers that have been tested with the monitoring probes. Deployment of the monitoring.war file follows the standard procedure for BusinessObjects web component deployment. If instructions for your web application server are not provided in this guide, refer to the web component deployment instructions in the BusinessObjects Enterprise Installation Guide. Updating the monitoring.war file This task assumes that you have deployed the BusinessObjects Enterprise monitoring probe package (monitoring.zip or monitoring.tar.gz) to your system. The monitoring.war file must be updated with libraries from your BusinessObjects environment before you deploy the monitoring.war file to your web application server. This task describes how to update the moni toring.war file using the updatewar.bat or updatewar.sh utilities that are provided with the monitoring probe package. Note: Because BusinessObjects libraries are updated when a BusinessObjects FixPack or Service pack is applied, the monitoring.war file must be updated and each time you upgrade your BusinessObjects system. 1. Locate the updatewar.bat file (for Windows deployments) or the update WAR.sh file (for UNIX deployments) in the monitoring directory under your BusinessObjects root installation directory. BusinessObjects Enterprise XI Release 2 Monitoring Guide 33 3 BusinessObjects monitoring probes Deploying monitoring probes 2. Open the updatewar. bat (for Windows deployments) or updatewar.sh (for UNIX deployments) 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 monitoring.bat file appears as follows: rem ---- BOE_HOME : root folder of your Business Objects Enterprise installation set BOE_HOME=C:\Program Files\Business Objects 3. Save and exit the file. 4. To update the monitoring.war file, run updatewar.bat (for Windows deployments) or the updatewar.sh (for UNIX deployments) from the monitoring directory. 5. As an optional step, you can verify the that monitoring.war file is correctly updated by extracting the contents of the monitoring.war file to a temporary folder using a Winzip or jar program. The lib folder under the WEB-INF directory should contain. jar files from your BusinessObjects installation. If the lib folder is empty, the update was not successful. The web.xml file under the WEB-INF directory should have the directory for the monitoring root installation folder correctly set. For example, the setting should appear as follows (with BOE_HOME set to your BusinessObjects installation root directory: <param-name>businessobjects.monitoring.root</param-name> <paramvalue>boe_home/monitoring</param-value> The next step is to deploy the monitoring.war file to your web application server. Related Topics Deploying the monitoring.war file to Tomcat on page 35 Deploying the monitoring. war file to WebSphere on page 37 Deploying the monitoring.war file to WebLogic on page 36 34 BusinessObjects Enterprise XI Release 2 Monitoring Guide BusinessObjects monitoring probes Deploying monitoring probes 3 Deploying the monitoring.

war file to Tomcat Before you deploy the monitoring.war file to your application server, you must update the monitoring.war file with libraries from your BusinessObjects environment, as described in Updating the monitoring. war file on page 33. The following instructions are for a BusinessObjects Enterprise Tomcat installation on Windows and assume the following default installation directory for Tomcat: C:\Program Files\Business Objects\Tomcat\ If you have a non-default installation directory, you must adjust the following instructions accordingly. 1. Before configuring Tomcat to use monitoring probes in web mode, you must deploy the monitoring probes package to your BusinessObjects Enterprise system. 2. Stop the Tomcat service. 3. Copy the monitoring.war file from C:\Program Files\Business Objects\BusinessObjects Enterprise 11.5\java\applications to C:\Program Files\Business Objects\Tomcat\webapps 4. Restart the Tomcat service. 5. 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: BusinessObjects Enterprise XI Release 2 Monitoring Guide 35 3 BusinessObjects monitoring probes Deploying monitoring probes Before attempting to run a probe in web mode from this web page, ensure that you have updated the probe configuration file. Refer to Running a monitoring probe in web mode on page 42 for more information. Deploying the monitoring.war file to WebLogic Before you deploy the monitoring.war file to your application server, you must update the monitoring.war file with libraries from your BusinessObjects environment, as described in Updating the monitoring.war file on page 33. This monitoring probe web configuration is tested on Redhat Linux Version 4 with Weblogic 9.2. 1. Before configuring WebLogic to use monitoring probes in web mode, the monitoring probes package must be deployed to your BusinessObjects Enterprise system. 2. Login to the Weblogic Administration Console. 3. Under Deployments, browse to the folder where the monitoring.war file is located. 36 BusinessObjects Enterprise XI Release 2 Monitoring Guide BusinessObjects monitoring probes Deploying monitoring probes 3 4. 5. 6. 7. Accept the default entries on all dialogs and select OK. Click Finish to complete the war file deployment. Activate the changes and start the monitoring application. Open a browser and logon to the following URL to view a default launch web page for the monitoring probes: http://<servername>:<serverport>/monitoring where <servername>:<serverport> are your web application server name and port number. See "Deploying the monitoring.war file to Tomcat" for a screen capture of the web page. Deploying the monitoring.war file to WebSphere Before you deploy the monitoring.war file to your application server, you must update the monitoring.war file with libraries from your BusinessObjects environment, as described in Updating the monitoring.war file on page 33. This monitoring probe web configuration is tested on AIX 5. 3 with WebSphere 6.0.2.2. 1. Before configuring WebSphere to use monitoring probes in web mode, the monitoring probes package must be deployed to your BusinessObjects Enterprise system. 2. Login to the WebSphere Application Server Administration Console. 3. Under Deployments, browse to the folder where the monitoring. war file is located. 4. Install the monitoring.war file as an application. Accept the default entries on all installation dialogs. 5. Click Finish to complete the war file deployment. 6. Activate changes and start the monitoring application. 7. Open a browser and logon to the following URL to view a default launch web page for the monitoring probes: http://<servername>:<serverport>/monitoring where <servername>:<serverport> are your web application server name and port number. See "Deploying the monitoring.war file to Tomcat" for a screen capture of the web page. BusinessObjects Enterprise XI Release 2 Monitoring Guide 37 3 BusinessObjects monitoring probes Deploying monitoring probes Configuring monitoring probes for authentication If you use Windows AD or LDAP authentication in your BusinessObjects environment, you must perform additional configuration steps to run monitoring probes. If you do not use Windows AD or LDAP authentication, you can skip this step. Related Topics Configuring monitoring probes for Windows Active Directory authentication on page 38 Configuring monitoring probes for LDAP authentication on page 39 Configuring monitoring probes for Windows Active Directory authentication This configuration assumes that BusinessObjects is already configured to work with Windows Active Directory - Kerberos authentication. In the following example, Windows Active Directory - Kerberos configuration files (Krb5.ini and bsclogin.conf) are located in C:\winnt. The location may differ on your system. To configure monitoring probes for Windows Active Directory authentication, perform the following steps: 1. Open the monitoring.bat file in a text editor. The monitoring.bat file is located in the monitoring directory under your BuisnessObjects root installation directory. 2. Uncomment the following line by removing "rem" from the line: rem set KERBEROS_OPTIONS=-Djava.security.auth.login. con fig=c:\winnt\bsclogin.conf -Djava.security.krb5.conf=C:\win nt\krb5. ini 3. If the name and location of your Kerberos configuration files are different than the default value for the KERBEROS_OPTIONS variable, provide the correct name and location. 4. Save and exit the file. 38 BusinessObjects Enterprise XI Release 2 Monitoring Guide BusinessObjects monitoring probes Deploying monitoring probes 3 5. Before running a probe, set the authentication type attribute to "secwinad", as in the following configuration file example for the CMS Logon Logoff probe: <probeconfig user='jdoe' password='jdoepwd' system='plbvm01' authtype='secwinad' classname='probelogonlogoff' /> Note: Windows Active Directory - Kerberos authentication is case sensitive. If the user name and system values are not entered correctly, the probe will not be permitted to run. Configuring monitoring probes for LDAP authentication This configuration assumes that BusinessObjects is already configured to work with LDAP - Kerberos authentication. In the following example, LDAP - Kerberos configuration files (Krb5.ini and bsclogin.conf) are located in C:\winnt. The location may differ on your system. To configure monitoring probes for LDAP authentication, perform the following steps: 1. Open the monitoring.bat file in a text editor. The monitoring.bat file is located in the monitoring directory under your BuisnessObjects root installation directory. 2. Uncomment the following line by removing "rem" from the line: rem set KERBEROS_OPTIONS=-Djava.

security.auth.login.con fig=c:\winnt\bsclogin.conf -Djava.security. krb5.conf=c:\win nt\krb5.ini 3. If the name and location of your Kerberos configuration files are different than the default value for the KERBEROS_OPTIONS variable, provide the correct name and location. 4. Save and exit the file. 5. If you plan to use monitoring probes in web mode, you must update the Java Options for Apache Tomcat through the "Tomcat Properties" dialog. Select Start > Programs > Tomcat > Tomcat Configuration. On the BusinessObjects Enterprise XI Release 2 Monitoring Guide 39 3 BusinessObjects monitoring probes Running monitoring probes "Tomcat Properties" dialog, select the Java tab. Enter the following lines in the Java Options text box: -Djava.security.auth.login.config=C:\winnt\bscLogin.conf Djava.security.krb5.conf=C:\winnt\Krb5.ini 6. Click Apply and OK on the "Tomcat Properties" dialog. 7. Before running a probe, set the authentication type attribute to "secldap", as in the following configuration file example for the CMS Logon Logoff probe: <probeconfig user='jdoe' password='jdoepwd' system='plbvm01' authtype='secldap' classname='probelogonlogoff' /> Note: LDAP authentication is case sensitive. If the user name and system values are not entered correctly, the probe will not be permitted to run. Running monitoring probes Running a monitoring probe in command line mode This task assumes you have deployed the monitoring probe package to your BusinessObjects Enterprise system. The following task describes how to run the CMS Logon Logoff probe in command line mode. 1. Locate the configuration template file for the CMS Logon Logoff probe (template_probe1.xml). Probe configuration files are located in <BOE_INSTALL_DIR>\monitor ing\probes on Windows, and bobje/monitoring/probes on UNIX. 2. Open the template_probe1.xml file in a text editor. The content of the template file appears as follows: <probeconfig user='bobjuser' password='bobjpassword' sys tem='servername' authtype='secenterprise' classname='probel ogonlogoff' /> 40 BusinessObjects Enterprise XI Release 2 Monitoring Guide BusinessObjects monitoring probes Running monitoring probes 3 3. Modify the probe attributes as required for your system. For attribute descriptions, see Monitoring probe attributes and parameters on page 44. To run the probe on your system, you must specify a valid user name, password, system name, and authtype. Note: CMS related probes do not use reports and therfore have no report related parameters. If you run a Crystal Reports, Desktop Intelligence, or Web Intelligence probe, a report is required and report related parameters must be set in the probe configuration file. 4. Save the configuration file in the probes directory. On Windows: <BOE_INSTALL_DIR>\monitoring\probes On UNIX: bobje/monitoring/probes 5. From the monitoring directory, run the monitoring command, calling the CMS Logon Logoff probe configuration file: monitoring.bat -probefile template_probe1.xml Note: If you are running the probe on a UNIX system, use the monitoring.sh command instead of monitoring.bat. If successful, the monitoring probe result output should appear similar to the following: <probe name="cms Logon Logoff" description="this probe tests the availability of the CMS and the ability for users to log on to the BOE system through any client applications. It suc cessively logs one user on, tests the session validity, and logs the user off."> <probeconfig user="jdoe" system="plbvm01" authtype="secenter prise" classname="com. businessobjects.monitoring.probes.probel ogonlogoff"> <connector>none</connector> </probeconfig> <result success="true" startdatetime="2008-04-25 17:23:34.109 PDT" error="" duration="1953"/> </probe> The XML based output shows a success flag, a start time, no error, and the time it took for the probe to complete. Related Topics Crystal Reports service through Page and Cache Server probe on page 131 BusinessObjects Enterprise XI Release 2 Monitoring Guide 41 3 BusinessObjects monitoring probes Running monitoring probes Running a monitoring probe in web mode This task assumes you have deployed the monitoring probe package to your BusinessObjects Enterprise system and that you have deployed the moni toring.war file to your application server. The following task describes how to run the CMS Logon Logoff probe in web mode. 1. Locate the configuration template file for the CMS Logon Logoff probe (template_probe1. xml). Probe configuration files are located in <BOE_INSTALL_DIR>\monitor ing\probes on Windows, and bobje/monitoring/probes on UNIX. 2. Open the template_probe1.xml file in a text editor. The content of the template file appears as follows: <probeconfig user='bobjuser' password='bobjpassword' sys tem='servername' authtype='secenterprise' classname='probel ogonlogoff' /> 3. Modify the probe attributes as required for your system. For attribute descriptions, see Monitoring probe attributes and parameters on page 44. To run the probe on your system, you must specify a valid user name, password, system name, and authtype. Note: CMS related probes do not use reports and therfore have no report related parameters. If you run a Crystal Reports, Desktop Intelligence, or Web Intelligence probe, a report is required and report related parameters must be set in the probe configuration file. 4. Save the configuration file in the probes directory. On Windows: <BOE_INSTALL_DIR>\monitoring\probes On UNIX: bobje/monitoring/probes 5. 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: 42 BusinessObjects Enterprise XI Release 2 Monitoring Guide BusinessObjects monitoring probes Running monitoring probes 3 6. Click on the following link: Template Probe 1: CMS Logon Logoff Note: Alternatively, you can specify a URL similar to the following in your Web browser's address field that directly calls the probe configuration file: http://webserver:8080/monitoring/monitoring?probefile=tem plate_probe1.xml If successful, the monitoring probe output appears in the browser window: BusinessObjects Enterprise XI Release 2 Monitoring Guide 43 3 BusinessObjects monitoring probes Running monitoring probes The XML based output shows a success flag, a start time, no error, and the time it took for the probe to complete. Related Topics Crystal Reports service through Page and Cache Server probe on page 131 Monitoring probe attributes and parameters This topic describes monitoring probe attributes and parameters.

The following example, from a "ProbeWebi" configuration file, shows all possible monitoring probe attributes and parameters, each of which is described in the tables that follow. <probeconfig user='bobjuser' password='bobjpassword' sys tem='servername' authtype='secenterprise' classname='probedes ki'> <!-- Uncomment one of the search options: cuid, docid, name-> <!-- Enter in the correct value afterwards--> <!-- CUID identifier for document--> 44 BusinessObjects Enterprise XI Release 2 Monitoring Guide BusinessObjects monitoring probes Running monitoring probes 3 <!-<param type='java.lang.string' value='ashedjiwzsbamtwnfiwgybs' /> --> <!-- DOCID identifier for document--> <param type='int' value='5852' /> <!-- NAME of document--> <!-<param type='java.lang.string' value='mail Labels' /> --> <!--Document display options--> <!-- REFRESH document select true or false --> <param type='boolean' value='true' /> <!-- PDFEXPORT document select true or false --> <param type='boolean' value='false' /> <!-- XLSEXPORT document select true or false --> <param type='boolean' value='false' /> </probeconfig> Attributes All BusinessObjects monitoring probes share the same attributes which are described in the following table. BusinessObjects Enterprise XI Release 2 Monitoring Guide 45 3 BusinessObjects monitoring probes Running monitoring probes Probe attributes user password Valid arguments BusinessObjects user name used to perform the test. Example: user='jdoe' Password for the BusinessObjects user. Example: pass word='jdoepwd'. If your BusinessObjects user does not have a password assigned, use empty quotes, as follows: password='' system CMS machine name: <cmsmachinename>:<portnum ber>. <cmsmachinename> can be the machine name, fully qualified domain name (FQDN), or IP address. Example: system='plbvm01' or system='plbvm01:6400' Note: <portnumber> is not required if the default port number (6400) is used. In a clustered CMS environment, any CMS can be specified. The request is automatically forwarded to other CMS servers, if required. authtype Authentication type for your BusinessObjects Enterprise system. Example: authtype='secenterprise' Authentication types include: BusinessObjects Enterprise authentication: secenter prise classname LDAP authentication: secldap Windows Active Directory authentication: secwinad 46 BusinessObjects Enterprise XI Release 2 Monitoring Guide BusinessObjects monitoring probes Running monitoring probes 3 Probe attributes Valid arguments Classname for the monitoring probe. Classnames for all eight probes are: CMS Logon Logoff probe: ProbeLogonLogoff Crystal Reports service through Page and Cache Server probe: ProbeCRPageServer Crystal Reports service through Report Application Server probe: ProveCRRAS Desktop Intelligence service probe: ProbeDeski Web Intelligence service probe: ProbeWebi CMS ping probe: ProbeCMSQuery1 CMS cache probe: ProbeCMSQuery2 CMS database connection probe: ProbeCMSQuery3 Note: The `classname' attribute is already specified in the probe configuration file templates that are located in the probes directory of the monitoring probes package. Parameters Monitoring probes that run against reporting engines require a report to run, and include some or all of the reportrelated parameters described in the table below. Monitoring probes that do not run against reporting engines (CMS Logon Logoff, CMS Ping, CMS cache, and CMS database connection) do not include report-related parameters. Note: There are three ways to specify a report document when configuring a probe. You can identify a document using its CUID, document id, or document name. Only use one of the three parameters. BusinessObjects Enterprise XI Release 2 Monitoring Guide 47 3 BusinessObjects monitoring probes Running monitoring probes Probe param- Valid arguments eters CUID A CUID uniquely identifies an object such as report. Using the CUID to identify a monitoring probe report is advantageous if you expect to move the report to a different environment (e.g from one BusinessObjects cluster to another or from a test system to a production system). The CUID remains unchanged, which means you do not have to update the monitoring probe parameters after a report is moved. Param type: 'java.lang.string' Value: e.g. 'ASHeDJIWZSBAmtwnFIWGybs ' Note: Only one of the following can be specified to identify your report: CUID, document id, or document name. The two unused options must be commented out. document id Param type: 'int' Value: e.g. '5852' Note: Only one of the following can be specified to identify your report: CUID, document id, or document name. The two unused options must be commented out. document name Param type: 'java.lang.string' Value: document_name, e.g. 'ABC report' Note: Only one of the following can be specified to identify your report: CUID, document id, or document name. The two unused options must be commented out. REFRESH document Param type: 'boolean' Value: 'true' or 'false' Param type: 'boolean' Value: 'true' or 'false' PDFEXPORT document 48 BusinessObjects Enterprise XI Release 2 Monitoring Guide BusinessObjects monitoring probes Running monitoring probes 3 Probe param- Valid arguments eters XLSEXPORT document Param type: 'boolean' Value: 'true' or 'false' Monitoring probe output The monitoring probe output stream is XML based to provide integration flexibility. This topic provides examples of probe output for command line mode and web mode, and explains output parameters. The monitoring probe output described in this topic is based on the input specified in the following ProbeCRPageServer configuration file example: <probeconfig user='jdoe' password='jdoepassword' system='plb vm01' authtype='secenterprise' classname='probecrpageserver'> <!-- Uncomment one of the search options: cuid, docid, name-> <!-- Enter in the correct value afterwards--> <!-- CUID identifier for document--> <!-<param type='java.lang. String' value='ashedjiwzsbamtwnfiwgybs' /> --> <!-- DOCID identifier for document--> <!-<param type='int' value='656' /> --> <!-- NAME of document--> <param type='java.

Powered by TCPDF (www.tcpdf.org) lang.string' value='mail Labels' /> <!--Document display options--> <!-- REFRESH document select true or false --> <param type='boolean' value='false' /> <!-- PDFEXPORT document select true or false --> <param type='boolean' value='false' /> </probeconfig> BusinessObjects Enterprise XI Release 2 Monitoring Guide 49 3 BusinessObjects monitoring probes Running monitoring probes Command line output When the ProbeCRPageServer probe run from the command line, output appears similar to the following: <probe name="crystal Reports Service through Page and Cache Server" description="this probe tests the availability of the Crystal Report service through Page and Cache servers. Using the Page and Cache servers, it successively opens a Crystal report, refreshes it, optionally export it to the PDF format and then closes it."> <probeconfig user="jdoe" system="plbvm01" authtype="secenter prise" classname="com. businessobjects.monitoring.probes.probe CRPageServer"> <param type="java.lang.string" value="mail Labels"/> <param type="boolean" value="false"/> <param type="boolean" value="false"/> <connector>none</connector> </probeconfig> <result success="true" startdatetime="2008-01-31 24:59:59.234 PDT" error="" duration="6718"/> </probe> Web mode probe output When the ProbeCRPageServer probe run from a web browser (web mode), output appears similar to the following: 50 BusinessObjects Enterprise XI Release 2 Monitoring Guide BusinessObjects monitoring probes Running monitoring probes 3 Output parameter definitions Probe output includes the following parameters: Output param- Values eter name description probeconfig Monitoring probe name Monitoring probe description Input attributes and parameters passed to the probe including user, system, authtype, document id/document name, refresh options, and export options Connector name (if any) Boolean flag to indicate if the probe was successful or not ("true" or "false") connector success BusinessObjects Enterprise XI Release 2 Monitoring Guide 51 3 BusinessObjects monitoring probes Running monitoring probes Output param- Values eter startdatetime Date and time the probe execution started (e.g. 2008-01-31 24:59:59.234 PDT) Note: PDT is a time zone abbreviation. error Error returned by the BusinessObjects Enterprise system Note: Error code and description are only returned if the probe encounters an error. duration Duration of probe execution (time in milliseconds it takes the probe to complete) Specifying probe attributes and parameters dynamically In addition to using a configuration file to specify probe attributes and parameters, you can specify probe attributes and parameters dynamically in both command line mode and web mode. The following example shows a command line statement for the CMS Logon Logoff probe with attributes specified dynamically: monitoring.bat -probeconfig "<probeconfig user='jdoe' password='jdoepwd' system='plbvm01' authtype='secenterprise' classname='probelogonlogoff' />" This example shows the same CMS Logon Logoff probe with attributes specified dynamically within a URL: http://webserver:8080/monitoring/monitoring?probecon fig=http://webserver:8080 /monitoring/monitoring?probeconfig=<probeconfig user='jdoe' password='jdoepwd' system='plbvm01' authtype='secenterprise' classname='probelogonlogoff' /> 52 BusinessObjects Enterprise XI Release 2 Monitoring Guide BusinessObjects monitoring probes Working with monitoring probes 3 where webserver:8080 is the name and port number where the monitoring web application component (monitoring.war) is deployed. Note: On UNIX, probes are run using the monitoring.sh command instead of the monitoring.bat command. Attributes and parameters are defined in the same way regardless of operating system. Dynamic usage examples for each probe are provided in the monitoring probe reference section. Working with monitoring probes The topics in this section provide information and guidelines for using monitoring probes. You will find answers to questions such as: What are the user account requirements for running monitoring probes? When do you run monitoring probes in command line mode versus web mode? How do you define performance measures for monitoring probes? How often should you run monitoring probes? Are there any considerations related to security or auditing? How can you monitor the CMS and authentication using monitoring probes? How can you monitor report engines (for Crystal Reports, Desktop Intelligence, and Web Intelligence) using monitoring probes? Can I integrate monitoring probes with industry-standard or proprietary monitoring solutions? What are the limitations and known issues? User account guidelines for running monitoring probes At a minimum, a BusinessObjects user account with default Enterprise authority is required to run a monitoring probe. The following additional requirements and guidelines may also apply: BusinessObjects Enterprise XI Release 2 Monitoring Guide 53 3 BusinessObjects monitoring probes Working with monitoring probes For security and audit considerations it is recommended that you define a BusinessObjects user account specifically for running monitoring probes. For more information, see Security and audit considerations on page 57. For BusinessObjects monitoring probes that use a report, the BusinessObjects user account must have the rights necessary to execute the report you define. You may want to make use of existing profiles or groups if testing of user rights integrity is part of your monitoring strategy. For more information, see Monitoring report engines and data sources on page 58. If your system uses an LDAP or Windows Active Directory authentication service, and you plan to run monitoring probes under the same authentication service, ensure that the BusinessObjects user account belongs to a user group that is mapped to your LDAP or Windows Active Directory group. Running probes in command line mode versus web mode Whether you run probes in command line mode, web mode, or in combination depends on your monitoring goals. The following table outlines a number of possible monitoring goals with a recommendation for which mode to use: 54 BusinessObjects Enterprise XI Release 2 Monitoring Guide BusinessObjects monitoring probes Working with monitoring probes 3 Monitoring goal Mode To perform a simple check of BusinessObjects Enter- Command line mode prise server availability on the physical machine where BusinessObjects Enterprise servers are running To isolate testing of BusinessObjects Enterprise Command line mode servers in a web application environment by checking BusinessObjects server availability on the physical machine where BusinessObjects servers are running To test availability of BusinessObjects Enterprise servers through your web application server Web mode To determine if a problem exists at a BusinessObjects Combination of comserver tier or web application server tier by running the mand line and web same probe in command line mode and web mode.