Infrastructure Management single-server deployment architecture

A single BMC TrueSight Infrastructure Management Server manages the entire environment for data collection, event management, service impact management, root cause analysis, and all other Infrastructure Management functionality.

A single-server deployment can manage small to medium environments. For information on how to size your deployment, see Sizing-and-scalability-considerations-and-best-practices.

Best practice

BMC strongly recommends that the environments you set up for Infrastructure Management development and test be separate from the production environment. For a multiple server deployment, see Infrastructure-Management-multiple-server-deployment-architecture.

High-level architecture with a single Infrastructure Management Server

The following illustration depicts the basic Infrastructure Management deployment, focusing on the core components only. It does not cover all possible functions or integrations. For example, Infrastructure Management Performance Management Reporting is not included. For additional deployment scenarios, see Deployment-use-cases-and-best-practices.

High-level architecture for a single-server deployment

BMC TrueSight Operations Management components

All BMC TrueSight Operations Management deployments require the following products or components:

Failed to execute the [excerpt-include] macro.

BMC TrueSight Infrastructure Management components

To enable BMC TrueSight Infrastructure Management as a data provider, deploy the following components.

Failed to execute the [excerpt-include] macro.

Notes

A maximum of 900 PATROL Agents can be connected to an Integration Service.
If you want to monitor a hybrid infrastructure in IPv6 systems, the PATROL Agent has to be on a dual stack.

For a description of these components, see BMC-TrueSight-Infrastructure-Management-architecture-and-components.

For the list of ports required in this deployment, see Network-ports.

For information about additional Infrastructure Management integrations, see Integrating.

Best practices for deploying Infrastructure Management

Component	Deployment best practice
Administration console	Install and use the administration console on a host separate from the Infrastructure Management Server. Use the instance of the administration console that is installed with the Infrastructure Management Server for emergency use only.
Database	Review the Considerations-for-selecting-the-database-for-the-Infrastructure-Management-Server. If using an Oracle database, follow the Considerations-and-best-practices-for-deploying-the-Oracle-database.
Infrastructure Management Server	Install a BMC PATROL Agent and the BMC PATROL for BMC ProactiveNet Self Monitoring 1.1 knowledge module on the Infrastructure Management Server to monitor the Infrastructure Management Server externally. The Infrastructure Management Server includes in-built self monitoring; however, the Self Monitor KM provides a way to monitor the Infrastructure Management Server externally. During installation of the Infrastructure Management Server, install the Infrastructure Management Self-Monitoring Service to monitor the health of all the components of Infrastructure Management. For more information, see Viewing-the-health-of-the-Infrastructure-Management-components. For a description of this feature using a use case, see Detect-problems-using-the-automated-self-health-monitoring-capability. Set up a separate event/notification path for external monitoring of the Infrastructure Management infrastructure so that you are not dependent on the infrastructure to generate and process alarms related to it being down or running in a degraded state.
Integrations and Impact Integration Web Services	Install BMC Impact Integration Web Services and all other integrations on servers separate from the BMC TrueSight Infrastructure Management Server (for example on an Integration Service host) unless specifically stated otherwise in the BMC documentation. This does not apply to the Integration for BMC Remedy Service Desk. Review Considerations-and-best-practices-for-interoperability-with-PATROL-components.
Integration Service	Follow the Integration-Service-host-deployment-and-best-practices-for-event-processing-and-propagation. Determine the location of all PATROL Agents and the respective Integration Services. At least one Integration Service must exist for each network, and generally the Integration Service must be close to the PATROL Agents connecting to it. This requirement minimizes the number of connections to the Infrastructure Management Server and makes firewall management easier because there is one connection per Integration Service. Tip Develop a clear strategy for assigning the PATROL Agents to each Integration Service. The Infrastructure Management Server does not auto-balance the load between PATROL Agents and Integration Services, so the initial assignment is important. Although at least one Integration Service must exist per network, a convention based on name or function (or simple round-robin assignment) within the network is acceptable as long as you are consistent and avoid overloading any one Integration Service.
Staging Integration Service	Follow the Staging-Integration-Service-host-deployment-and-policy-management-for-development-test-and-production-best-practices.
All	If you are deploying on virtual machines, follow the Considerations-for-deploying-on-a-virtual-machine. To ensure high availability of the Infrastructure Management system, follow the Infrastructure-Management-high-availability-deployment-and-best-practices.

Architectural changes compared to version 9.6 of Infrastructure Management

The following changes in the Infrastructure Management architecture:

Infrastructure Management is now deployed as part of BMC TrueSight Operations Management.

The Infrastructure Management Central Server has been replaced by the Presentation Server that is installed with Operations Management.
Note
In this release, the Central Server has been replaced by the Presentation Server for most deployments; however, a Central Server is still required for distributed service models and for the BMC Cloud Lifecyle integration. For details, see Exceptions requiring a Central Server deployment.

There are no child servers in Operations Management. Operations Management data comes from the Infrastructure Management Servers and BMC TrueSight App Visibility servers.
Although you can install a standalone Infrastructure Management server, you can only use the Infrastructure Management functionality with a Presentation Server.

Central Monitoring Administration is now hosted on the Presentation Server and is accessible through the TrueSight console and not through Infrastructure Management.
The central monitoring repository now resides in the Presentation Server.
Version 9.0 of the BMC PATROL Agent is not supported with a BMC TrueSight Operations Management system and must be upgraded to version 9.5 or later.
Support for service models will continue with the current Infrastructure-Management-deployment-with-BMC-Atrium-CMDB. The Presentation Server and the TrueSight console will deliver new application model capabilities. For further information, see TrueSight Operations Management 10.0.00 features.