Deployment architecture

For event and impact reporting, BMC ProactiveNet propagates events and component status changes from BMC ProactiveNet Servers to BMC ProactiveNet Report Engine. For performance reporting, BMC ProactiveNet propagates performance data and its supported configurations from multiple instances of BMC ProactiveNet Server to multiple instances of BMC ProactiveNet Report Engine.

In BMC ProactiveNet Performance Management Reporting version 9.5, you can continue to gather event data from multiple BMC ProactiveNet Server Cells into multiple BMC ProactiveNet Report Engines. However, for performance reporting, a separate instance of the Report Engine is required for each BMC ProactiveNet Server. Multiple BMC ProactiveNet Servers cannot use a single Report Engine instance.

BMC ProactiveNet Report Engine then aggregates and summarizes the data and stores the processed data in the Oracle or SQL database. The impact reports are supplemented with associated service information and the performance reports are supplemented with associated BMC ProactiveNet Server configuration information.

The following figure depicts the architecture of BMC ProactiveNet Performance Management Reporting.

architecture1.png

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

  • The deployment in the following table is a recommendation. It is also possible to install all the required products on a single computer.
  • 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.01

  • 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.

Related topics

Planning-worksheet

System-requirements

Performance-and-scalability-recommendations

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*