For customers who are upgrading to BMC TrueSight Operations Management, this getting started topic describes how solution administration differs from BMC TrueSight Infrastructure Management and BMC TrueSight App Visibility Manager. Solution Administrators should read this topic to understand how they will perform tasks differently in the BMC TrueSight Operations Management Console.
Before BMC TrueSight Operations Management 10.0, administration of the monitoring systems was performed in the individual product consoles, as follows:
After upgrading to BMC TrueSight Operations Management, Solution Administrators will use the Operations Management console for system configuration, data provider configuration, and role-based access control. Security administrators or Solution Administrators will use the BMC Atrium SSO Admin Console to define users and tenants.
Central Monitoring Administration for configuring Infrastructure Management monitoring is available from the Operations Management console only. (Note: The to configure events and adapters. For further information, see .) is still required
System configuration will be migrated to the BMC TrueSight Operations Management console as indicated in the following topics:
|Migrating component and information||Reference|
|BMC App Visibility Manager (formerly BMC Application Diagnostics) policy and configuration files||Preparing for an App Visibility upgrade and checking compatibility|
BMC Transaction Management Application Response Time scripts and configurations
Note: Migration from BMC Synthetic Transaction Monitoring 2.6.00 (Borland Silk Performer Synthetic Transaction Monitoring for BMC Software ) is not currently supported.
|Migrating from BMC TM ART|
|BMC TrueSight Infrastructure Management Central Monitoring Administration repository|
|BMC TrueSight Infrastructure Management policies, user management data, and files.|
Each quick tour provide a visual overview of these functions and links to how-to information.
BMC Atrium Single Sign-On provides user account and tenant management to BMC TrueSight Operations Management. Solution Administrators create users, user groups and tenants as realms in the BMC Atrium SSO Admin Console. User Groups are then assigned to Authorization Profiles in the Operations Management console. For more information, see in the BMC Atrium Single Sign-On documentation.
The Presentation Server provides role-based access control to data, system features, and features enabled by the data providers. In the Operations Management Console, Solution Administrators define roles and authorization profiles that control data access and the users' ability to perform functions. For more information, see Managing users and access control.
The initial configuration of the Presentation Server occurs during installation. After installation, the Solution Administrator connects the data providers to the Presentation Server and integrates other components that extend the functionality of the system. For more information, see Configuring after installation and Integrating.
The Presentation Server and Operations Management console provide the following common features for enabling IT Operations to monitor your IT infrastructure and critical applications:
Solution Administrators and specialists use Central Monitoring Administration to download BMC PATROL Agents and Knowledge Modules, download Integration Service hosts, manage the monitoring infrastructure, and set up monitoring policies to collect events and performance data from monitored systems. For more information, see Central Monitoring Administration for Infrastructure Management. (Note: The is still required to configure events and adapters. For further information, see .)
To enable application monitoring, you configure the BMC TrueSight App Visibility components, set up application discovery, and set SLAs (thresholds to generate events).
Solution Administrators or specialists configure how to generate the synthetic transactions to synthetically monitor application health, which is monitored from Application monitoring. For complete information about this process, see Setting up and managing synthetic transaction monitoring.