Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

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

high_level_architecture.png

BMC TrueSight Operations Management components

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

Failed to execute the [excerpt-include] macro. Cause: [Error number 2 in 0: No wiki with id [confluencePage:page] could be found]. Click on this message for details.

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. Cause: [Error number 2 in 0: No wiki with id [confluencePage:page] could be found]. Click on this message for details.

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

Infrastructure Management Server

Integrations and Impact Integration Web Services

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

All

Architectural changes compared to version 9.6 of Infrastructure Management

The following changes in the Infrastructure Management architecture:

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

Related topics

Infrastructure-Management-deployment-integrated-with-BMC-Cloud-Lifecyle-Management

Disaster-recovery-deployment-architecture-Sybase

Disaster-recovery-deployment-architecture-Oracle

 

 

 

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