Infrastructure Management single-server deployment architecture
A single 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.
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
TrueSight Operations Management components
All TrueSight Operations Management deployments require the following products or components:
|Product or component||Function|
|Remedy Single Sign-On and SSO Admin on TrueSight console|
Deploy Remedy Single Sign-On for user and tenant management and for authentication to the TrueSight console.
Note: Remedy Single Sign-on can be installed on the same server with the TrueSight Presentation Server if necessary.
For information about deploying Single Sign-On, see Installing Remedy SSO.
TrueSight Presentation Server and the TrueSight console
Deploy a single TrueSight Presentation Server to present data from the component products. The TrueSight console hosted on the TrueSight Presentation Server provides monitoring functions, role-based access control, solution administration, and configuration for TrueSight App Visibility Manager, a Synthetic Transaction Execution Adapter Agent (TEA) Agent, and TrueSight Infrastructure Management.
Best practice: Install the TrueSight Presentation Server separately from the Infrastructure Management Server.
For details about the TrueSight console and the TrueSight Presentation Server, see.
For a proof-of-concept deployment, see Guidelines for installing on a single computer.
TrueSight Infrastructure Management components
To enable TrueSight Infrastructure Management as a data provider, deploy the following components.
|Product or component||Function|
|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 TrueSight Infrastructure Management Server hosts the TrueSight Infrastructure Management operator console, the TrueSight Infrastructure Management administrator console, and the TrueSight Infrastructure Management Service Level Object (SLO) console. The TrueSight Infrastructure Management Server requires a database, either the locally embedded Sybase database or a remote Oracle database. For more information about deploying TrueSight 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
|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 release of TrueSight 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 and
|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.
- 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 .
For the list of ports required in this deployment, see Network port schematics for Infrastructure Management.
For information about additional Infrastructure Management integrations, see .
Best practices for deploying Infrastructure Management
|Component||Deployment best practice|
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|
|Integrations and Impact Integration Web Services|
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|
Note: The Integration Service running on an Infrastructure Management Server cannot be configured as a staging Integration Service.