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.

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.

TrueSight Operations Management components

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

When both TrueSight App Visibility Manager 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.

Note

For a proof-of-concept deployment, see Guidelines for installing on a single computer in the Installation-process-overview.

TrueSight Infrastructure Management components

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

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

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 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	Install BMC Impact Integration Web Services and all other integrations on servers separate from the TrueSight Infrastructure Management Server (for example on an Integration Service host) unless specifically stated otherwise in the BMC documentation. 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. Note: The Integration Service running on an Infrastructure Management Server cannot be configured as a staging Integration Service.
All	If you are deploying on virtual machines, follow the Considerations-for-deploying-Infrastructure-Management-on-a-VM. To ensure high availability of the Infrastructure Management system, follow the High-availability-deployment-and-best-practices-for-Infrastructure-Management.

Infrastructure Management single-server deployment architecture

TrueSight Operations Management components

TrueSight Infrastructure Management components

Best practices for deploying Infrastructure Management

On this page