Skip to end of metadata
Go to start of metadata

Product versions:
SAP BusinessObjects Enterprise XI R2
SAP BusinessObjects Enterprise XI 3.1

Introduction

This article describes the possible integration points of IBM Tivoli Monitoring for any Enterprise software and more specifically BusinessObjects Enterprise. Please read this article for an overview of the Monitoring options with SAP BusinessObjects Enterprise XI R2 and XI 3.1 : Enterprise Monitoring and BusinessObjects Enterprise XI.

Public documentation of IBM Tivoli Monitoring (ITM) : http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/index.jsp?topic=/com.ibm.itm.doc_6.2.1/welcome.htm

Here is a overview of the ITM architecture and possible integration points.

Like most monitoring tools, ITM has agents that are deployed on the server hosting the application that you want to monitor. The target application is seen as a data source that is feeding the agent with monitoring data, The agent then sends that data back to the Tivoli Enterprise Management Server.
The possible integration points for BOE are Agent Builder and Universal Agent. Universal Agent is the legacy one and likely available with older versions of ITM. Whereas Agent Builder is only available since ITM 6.2.

Universal Agent

A configurable generic agent for Tivoli Monitoring that offers management of your application through the use of one or more data providers. A data provider acts as the interface between the universal agent and your application. A Universal Agent may be created by configuring one of its built-in data providers or by developing an additional data provider specific to monitoring your data source. A metafile is a plain-text file specifying the attributes and format for the information the data provider collects. Built-in Universal Agent data providers are list below:

Type

Description

API Server

Enables you to collect data from resources on remote machines where the IBM Tivoli Universal Agent API client software is supported.

File

Monitors sequential files, such as system or message logs. Provides the most direct, simplest method of collecting data.

HTTP

Allows monitoring of Internet URLs for availability and response time. You can specify URLs to monitor in a startup configuration file or within Tivoli Enterprise Portal situations.

ODBC

Allows data collection from ODBC-compliant databases using SQL Select statements and stored procedures.

Post

TCP/IP socket application with predefined data. Enables you to send ad hoc notifications such as messages, alerts, and status.

Script

Allows data collection from any script or program that sends results to standard output.

SNMP

Provides the functionality of an SNMP manager, including network discovery, trap monitoring, and MIB data collection.

Socket

Listens on a TCP/IP socket for data sent using program-to-program communication. Enables you to collect data from remote devices or machines for which no IBM Tivoli Universal Agent API support is available.

The preferred method to integrate the BOE Monitoring Probes is the script data provider. The probe is the "data source" and will feed the agent with monitoring data from BOE. The HTTP method described above cannot parse the HTTP response from a URL, hence cannot be used with the Pobres in Web Mode.

A detailed step-by-step configuration guide is available, see section "Monitoring BusinessObjects
with IBM Tivoli" as part of the Monitoring Guide.

Agent Builder

The Universal Agent approach works well, it does the job but requires quite a bit of manual steps. The Agent Builder could automate most of that by producing a package ready to deploy on each BOE server to be monitored. It is an Eclipse application that allows you to pre-packaging the configuration.

Some documentation from IBM on the topic : http://www.redbooks.ibm.com/Redbooks.nsf/RedpieceAbstracts/sg247444.html?Open
as well as a nice "getting started" webinar : ftp://www.redbooks.ibm.com/redbooks/SG247444/itm62.html

It then allows the BOE landscape into IBM Tivoli Composite Application Manager (ITCAM), see attached presentation on the topic and public documentation from IBM.

No Agent Builder package exists as of today with BOE.

  • No labels