Page tree
Skip to end of metadata
Go to start of metadata

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 for Infrastructure Management.

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 for Infrastructure Management.

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:

Product or componentFunction
Atrium Single Sign-On and the TrueSight SSO Admin Console

Deploy TrueSight Single Sign-On for user and tenant management and for authentication to the TrueSight console.

Note: TrueSight Single Sign-on can be installed on the same server with the TrueSight Presentation Server if necessary.

For information about deploying TrueSight Single Sign-On, see BMC Atrium Single Sign-On 9.0 .

TrueSight Presentation Server and the TrueSight console

Deploy a single Presentation Server to present data from the data providers. The TrueSight console hosted on the Presentation Server provides monitoring functions, role-based access control, solution administration, and configuration for TrueSight App Visibility Manager, a BMC Synthetic Transaction Execution Adapter Agent (TEA) Agent, and TrueSight Infrastructure Management.

Best practice: Install the Presentation Server separately from the Infrastructure Management Server.

For details about the TrueSight console and the Presentation Server, see TrueSight Operations Management overview.

When both TrueSight App Visibility and TrueSight Infrastructure Management  are installed, the App Visibility portal can be connected to the Infrastructure Management Server Cell or a Remote Cell. For instructions, see Adding and editing components.


BMC TrueSight Infrastructure Management components

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

Product or componentFunction
TrueSight Infrastructure Management Server and Infrastructure Management console

Deploy a TrueSight Infrastructure Management Server to collect and compute information related to events, performance, services, and applications. The Infrastructure Management Server hosts the Infrastructure Management operator console, the Infrastructure Management administrator console, and the Infrastructure Management Service Level Object (SLO) console. The Infrastructure Management Server requires a database, either the locally embedded Sybase database or a remote Oracle database. For more information about deploying Infrastructure Management, see Deployment use cases and best practices for Infrastructure Management.  For multiple tenants, see Service provider and tenant deployment for TrueSight Operations Management.

(Optional) Atrium CMDB and the BMC CMDB Extensions
(Optional) Event Enrichment Cell (Remote Cell)

Installed separately from the TrueSight Infrastructure Management Server, a Remote Cell functions as part of a larger distributed network of cells that pre-process and propagate events to the TrueSight Infrastructure Management Server Cell. You can install the Remote Cell on its own host or an Integration Service host. Networks of Remote Cells can be organized to serve any business hierarchy (such as geographical, functional, or organizational) or configured to meet technical issues (such as network or system limitations). You can configure a Remote Cell for high availability by configuring a primary cell server and a secondary cell on a separate server to be used for failover if the primary cell server fails.

If service impact management is implemented, the Remote Cell can also associate events with service model components and calculate the components’ statuses. If service impact management is not implemented, then the cell is simply an event management cell.

Infrastructure Management Integration Service host

A single Integration Service host is required for managing events from event sources such as PATROL Agents, event adapters, and SNMP traps, and for forwarding performance data to the Infrastructure Management Server.

For more information, see Infrastructure Management Integration Service .

PATROL Agents and monitoring solutions

PATROL Agents collect performance data and generate events for availability metrics. Monitoring solutions consist of one or more knowledge modules (KMs). (A KM is a set of instructions that the PATROL Agent uses to monitor objects in your environment.)  For a list of Knowledge Modules supported with the current version of Infrastructure Management, see List of Monitoring Solutions and KMs in Infrastructure Management

Determine what will be monitored in the environment and how that data will be used. Specifically identify from which systems, applications, and components in your environment you need performance metrics (and historic trend data), and from which components you need events and alerts. Next, determine the location of all PATROL Agents and the respective Integration Services. At least one Integration Service should exist for each secure network zone, and generally the Integration Service must be closer 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. For additional details, see the following topics:

You configure PATROL Agents from the TrueSight console. The configuration information is sent to the PATROL Agent through the Infrastructure Management Server and the Integration Service following the same path and ports that data flows up through.

For information about deploying the PATROL Agent, see Best practice approach to infrastructure monitoring administration and BMC PATROL Agent 9.6

Transaction response time and third-party transaction monitors

User transaction monitors collect performance data, such as response time, for web applications and web pages. Third party data adapters provide a mechanism for external applications to feed data into Infrastructure Management. Data adapters facilitate the synchronization of performance data collected by specific monitoring solutions into Infrastructure Management for further analysis.

For more information, see  User Transaction monitors or BMC adapters and third-party data adapters .


  • 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 TrueSight Infrastructure Management architecture and components.

For the list of ports required in this deployment, see Network port schematics for Infrastructure Management.

For information about additional Infrastructure Management integrations, see Integrating.

Best practices for deploying Infrastructure Management

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

DatabaseReview 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 TrueSight Self-Monitoring 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 PATROL for TrueSight Self-Monitoring 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 from the operator console. 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
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.


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.

NoteThe Integration Service running on an Infrastructure Management Server cannot be configured as a staging Integration Service.


Related topics

Infrastructure Management deployment integrated with Cloud Lifecyle Management

Disaster recovery deployment architecture (SAP SQL Anywhere)

Disaster recovery deployment architecture (Oracle)