Deployment architecture

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

Deployment scenarios

BMC ProactiveNet Performance Management Reporting can be deployed for following scenarios:

Scenario 1: Collecting only Event and Impact data from BMC ProactiveNet Server

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

Scenario 2: Collecting Event, Impact, and Performance data from BMC ProactiveNet Server

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

Note

If you want to collect only performance data, do not register BMC ProactiveNet Cell.

Scenario 3: Collecting data from BMC ProactiveNet 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 ProactiveNet Server configured with the Report Engine.

For information about port numbers used by various components, see Components-overview.

Prerequisites for BMC ProactiveNet Performance Management Reporting

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

Notes

BMC recommends you to install all components, that is, BMC ProactiveNet 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 ProactiveNet 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 ProactiveNet Performance Management Reporting 9.5.02

All the components of BMC ProactiveNet Performance Management Reporting must be present in the same LAN/subnet as that of BMC ProactiveNet Server.
For the custom reports with performance and event data to display correct data, ensure that you provide the logical name of the BMC ProactiveNet Server in the BMC ProactiveNet Server Registration page when you install BMC ProactiveNet Report Engine. You can find the logical name of the BMC ProactiveNet Server as the NGP_Server_Name entry in the <BMCProactiveNetServerInstallationDir>\pw\custom\conf\pronet.conf file.
After you successfully install BMC ProactiveNet 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 reporting engines 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.
Installing SAP BusinessObjects on UNIX operating systems and using SQL Server as Reporting Engine database is not supported