Deployment architecture

BMC TrueSight Infrastructure Management systems propagate events and component status changes from BMC TrueSight Infrastructure Management Server to the BMC TrueSight Report Engine. The BMC TrueSight Report Engine then aggregates and summarizes the events and component status changes, and stores the processed data in the Reporting Database.

Deployment scenarios

BMC TrueSight Reporting can be deployed for following scenarios:

Scenario 1: Collecting only Event and Impact data from BMC TrueSight Infrastructure Management Server

For event and impact reporting, BMC TrueSight Infrastructure Management Server propagates events and component status changes from one or multiple BMC TrueSight Infrastructure Management Server Cells into single BMC TrueSight Report Engines.

Scenario 2: Collecting Event, Impact, and Performance data from BMC TrueSight Infrastructure Management Server

To collect event, impact, and performance data, you must use separate BMC TrueSight Report Engine for each instance of BMC TrueSight Infrastructure Management Server.

Note

If you want to collect only performance data, do not register BMC TrueSight Infrastructure Management Cell.

Scenario 3: Collecting data from BMC TrueSight Infrastructure Management Server and Remote Cell

Register the remote cell to receive event and impact data. However, to collect data from the remote cell, you must have at least one instance of BMC TrueSight Infrastructure Management Server configured with the Report Engine.

Prerequisites for BMC TrueSight Reporting

The following table lists the supporting products and product versions required to use BMC TrueSight Reporting.

Notes

BMC recommends you to install all components, that is, BMC TrueSight Infrastructure Management Server, Report Engine, Reporting database, and SAP BusinessObjects, on separate computers. However, it is also possible to install all these components on a single computer for test environment.
Ensure that the system time of BMC TrueSight Infrastructure Management Server and report engine is correct for their respective time zones.
An error may occur when the Oracle server is installed on the same computer with Oracle client, due to incorrect sequence of Oracle path in PATH variable. To avoid this issue, set the client entry before the Oracle server entry in the path variable. For more information, see the following example:
PATH : D:\oracle\product\11.2.0\client_1\bin;D:\oracle\product\11.2.0\db_1\bin;

Products and components required for reporting

General recommendations

This section contains guidelines and recommendations for using BMC TrueSight Reporting 9.6.00

All the components of BMC TrueSight Reporting must be present in the same LAN/subnet as that of BMC TrueSight Infrastructure Management Server.
After you successfully install BMC TrueSight Report Engine, for performance data in the reports, you must wait for a minimum of 3 hours, and for server capacity reports, you must wait for 24 hours because the server capacity report shows daily summarized data.
If you have multiple reporting engines running, all hosts should have same timezone.
BMC recommends that you do not install multiple instances of SQL Server databases on Report Engine database host, for better performance.
SAP BusinessObjects on Solaris operating systems that use SQL Server as Reporting Engine database is not supported.
Installing SAP BusinessObjects 4.1 SP3 Patch3 in a pure IPv6 environment, on Solaris platform, is not supported.