BSM End-to-End Workflow: Step 6. Configure BSM Applications
Configure how BSM manages and displays the incoming data in the different BSM applications.
Set User Permissions
In User Management in Platform Administration, you can define permissions and recipients:
- Define user permissions. To restrict the scope of user access to defined areas, create users and user groups, and assign permissions for your application's views and pages, according to the type of user. For details, see "How to Configure Users and Permissions — Workflow" in the Platform Administration Guide.
- Create recipients of alerts or reports. You can create the recipients of emails, pager, or SMS messages triggered by alerts, or scheduled reports, while creating the users. You can also create recipients separately and assign them to users later. For details, see "How to Configure and Manage Recipients" in the Platform Administration Guide.
Define Alerts
You define triggers for alerts in various BSM components, to proactively inform defined recipients when predefined performance limits are breached:
- Application alerts. There are two types of application alerts: CI Status alerts for high level information, and End User Management (EUM) alerts for low level of information. Both types of alerts can be configured to generate events (which are displayed in Operations Management).
- CI Status alerts are triggered by a change in status of the relevant KPI, calculated in Service Health. For details, see "How to Create a CI Status Alert Scheme and Attach it to a CI" in the BSM Application Administration Guide.
- EUM alerts can be triggered based on Business Process Monitor and Real User Monitor data, including synthetic transactions and real user transactions. For details, see "How to Create EUM Alert Schemes" in the BSM Application Administration Guide.
- Service level agreement (SLA) alerts are configured in Service Level Management Administration. The SLA alerts are triggered by the relevant change in SLA status. The alerts can be configured to generate events (which are displayed in Operations Management). For details, see "How to Define an SLA Alert Scheme" in the BSM Application Administration Guide.
- SiteScope alerts are triggered by an event or change of status in some element or system in your infrastructure. An alert definition contains settings that tell SiteScope what monitors can trigger the alert, what condition to watch for, and what information to send to recipients. For details, see "How to Configure an Alert" in the Using SiteScope Guide in the SiteScope Help.
Configure Operations Management (OMi)
You can customize and streamline the way Operations Management (OMi) handles events, and automate event handling. Some of the more commonly used configuration options are as follows:
- Configure event forwarding to and from Operations Management. You configure event forwarding by specifying the following as event forwarding targets: Operations Manager servers, external event-processing servers, servers connected using BSM Connector, and other BSM servers. For details, see "Connected Servers" in the BSM Application Administration Guide.
- Configure alerts. By default, threshold breaches of EUM and SiteScope measurements generate events in Operations Management. In addition, you can set the alerts triggered by various BSM applications to generate events that are consumed in Operations Management. For example, Operations Management can collect, view, correlate, and manage events generated from EUM alerts triggered on EUM components.
- Configure topology-based event correlation rules. BSM provides many out-of-the-box correlation rules to enable the correlation of symptoms with cause events. You can also configure additional rules that will accommodate correlating events based on customer-specific business logic. For details, see "How to Configure Topology-based Event Correlation Rules" in the BSM Application Administration Guide.
- Configure event forwarding to users or groups. Incoming events can automatically be assigned or forwarded to the people responsible for handling the problems. For details, see "How to Create an Event Forwarding Rule" in the BSM Application Administration Guide.
- Configure automatic execution. You can configure the automatic execution of tools, custom actions, performance measurements, and Run Books, to help Operations Management end-users manage the events, and to automate and streamline problem solving. For details, see "How to Create Tools", "How to Create a Custom Action Script", and "How to Create a Run Book Automation Rule" in the BSM Application Administration Guide.
- Configure actions to be executed on events. Actions are carried out when an event matches a user-defined set of criteria after a specified time. For details, see "How to Create a Time-Based Event Automation Rule" in the BSM Application Administration Guide.
- Synchronize the topology. To populate RTSM with CI topology and service data from HPOM, you need to perform Topology Synchronization. Synchronization regularly updates all specified servers with the topology and service data from the HPOM management server. For details, "How to Run Topology Synchronization" in the BSM Application Administration Guide.
To learn more about Operations Management, see Operations Management (OMi).
Configure Service Health
You can customize the way BSM calculates information in Service Health. This customization can be done on different levels:
For details, see "How to Customize Calculations in Service Health" in the BSM Application Administration Guide.
To learn more about Service Health, see Service Health.
Define MyBSM Workspaces
In MyBSM, you can create role-based workspaces for different types of users, such as operations users, and senior management. Workspaces provide smooth interaction between different BSM applications and reports.
MyBSM contains out-of-the-box pages from different BSM applications; you can also create pages to suit your needs.
For each page, you can:
- Select from a list of components that are of interest to the specific users or user groups. Components include available reports, views, diagrams, graphs, summaries, and other types of data displays.
- Define the layout of components on the page, and their interaction with other components.
- Organize pages and components by categories.
For details on how to set up MyBSM, see "How to Set Up the MyBSM Workspace" in the BSM User Guide.
To learn more about MyBSM, see MyBSM.
Define Service Level Agreements
In Service Level Management (SLM) administration, you can define services and service level agreements (SLAs):
Tip: If you have a CMS system with a central UCMDB, it is recommended that you create and model your Business Service CIs in the CMS, and then synchronize them into the RTSM for consumption in the SLM module.
- Define your organization's business services. Define the services provided by, or consumed by, your organization, that represent the service offerings in your service catalog; for example, project management services, application development for departmental applications, Web development services, email services, backup services, and so forth. For details, see "How to Define a Service for an SLA – Use-Case Scenario" in the BSM Application Administration Guide.
- Create your application-related SLAs. Create and manage SLAs, OLAs (operational level agreements), and UCs (underpinning contracts) that represent contracts entered into by your organization or department with service providers and customers. For details, see "How to Use SLM to Monitor Your Service Agreements" in the BSM Application Administration Guide.
To learn more about Service Level Management, see Service Level Management (SLM).
Configure End User Management
In End User Management Administration, configure the applications, business transaction flows, and transactions for monitoring by Business Process Monitor, Real User Monitor, or both.
For details, see "How to Set up Business Process Monitors" and "How to Install Real User Monitor Components" in the BSM Application Administration Guide.
To learn more about End User Management, see End User Management (EUM).
Configure System Availability Management
In System Availability Management Administration, you can access and manage SiteScopes from within BSM:
- Add SiteScopes. You can register and configure one or more SiteScopes. For details, see "Configuring the Connection" in the BSM Application Administration Guide.
- Manage multiple SiteScopes. You can configure SiteScope monitors, alerts, and reports and make any other configuration changes for the SiteScope. All the configuration changes that are done from System Availability Management Administration are reflected in the SiteScope itself. For details, see "How to Manage Multiple SiteScopes in SAM" in the BSM Application Administration Guide.
To learn more about System Availability Management, see System Availability Management (SAM).
Configure Service Health Analyzer
Configure the following in Service Health Analyzer (SHA), so that it can analyze the current and historical data for CIs, detect anomalies, and send out SHA events.
- Define the CIs to be monitored by SHA. For details, see "How to Select CIs to be Monitored by Service Health Analyzer."
- Configure the SHA event template to determine the structure of the SHA event. For details, see "How to Configure the Service Health Analyzer Event Template."
- Configure verification tools to assist in identifying suspect CIs. For details, see "How to Configure Verification Tools."
The topics above can be found in the BSM Application Administration Guide.
To learn more about SHA, see Service Health Analyzer (SHA).
Configure Business Process Insight
You configure Business Process Insight (BPI) by defining business activities to represent business processes within your business. You then attach existing monitor CIs that receive data from one of the BSM data collectors, such as BPM or RUM monitors, to critical points in the business process, in order to learn about the actual metrics.
- Use the BPI Modeler component to create and deploy business processes. For details, see "How to Model Your Business" in the BSM Application Administration Guide.
- Use the BPI Monitor Definer component to map business data to your business processes and business process activities. For details, see "How to Manage the BPI Monitor Definer" in the BSM Application Administration Guide.
- BPI sends data samples to BSM by configuring the Data Sample settings in the BPI Server Admin Console. Sending data samples to BSM enables you to use the BPI application to report and view the health of the business processes that you create. For details on configuring the Data Sample settings, see the "Component Configuration - HP Business Service Management Settings" section in the Business Process Insight Server Administration Guide.
To learn more about BPI, see Business Process Insight (BPI).
Configure Transaction Management
In Transaction Management Administration, configure transaction monitoring and tracing for business transactions, as follows:
- Define the Business Transaction CIs and Transaction Management workflow. Create new (or use existing) Business Transaction CIs to represent the transactions you want to monitor, and determine which products are used to collect the transaction data: Real User Monitor, Diagnostics, TransactionVision. For details, see "How To Choose a Transaction Management Workflow" in the BSM Application Administration Guide.
For RUM Business Transaction CIs, you must also ensure that the required Business Transaction CIs are configured for monitoring in the EUM application. For details, see "Viewing TransactionVision Data From End User Management Reports" in the BSM User Guide.
- Set up transaction tracing on business transactions. Define transaction tracing rules and properties on the Business Transaction CIs. The tracing rules control the process by which unclassified transactions become business transactions. For details, see "How to Set Up a Business Transaction for Tracing" in the BSM Application Administration Guide.
- Set up custom event correlation for a business transaction. Define the correlation and modification rules to expand or modify event collection criteria. For details, see "Custom Correlation" in the BSM Application Administration Guide.
To learn more about Transaction Management, see Transaction Management.
Define Customized Reports and Report Scheduling
In the User Reports application, you can:
- Define customized reports for your organization's requirements. Use the Report Manager to define Custom Reports, Trend Reports, and Service Reports, to focus on the data you are most interested in tracking. For details, see "How to Create and Manage User Reports Using Report Manager" in the BSM User Guide.
- Send scheduled reports to recipients. Use the Report Manager to set schedules for sending automatically generated reports to specified recipients. For details, see "Scheduling Reports" in the BSM User Guide.
- Create queries to the profile database. Use Custom Query Builder to assist you in creating queries to run reports. For details, see "How to Create a Custom Query" in the BSM User Guide.
To learn more about User Reports, see User Reports.
Advanced Configuration: Application Management Solutions
The following Application Management solutions can be configured for specific, advanced monitoring needs:
- Application Management for Siebel. For details on configuring the application, see "How to Deploy Application Management for Siebel" in the BSM Application Administration Guide. To learn more, see Application Management for Siebel.
- Application Management for SOA. For details on configuring the application, see "How to Monitor the SOA Environment" in the BSM Application Administration Guide. To learn more, see Application Management for SOA.
- Application Management for SAP. For details on configuring the SAP solution, see "How to View SAP Information in Service Health" in the BSM Application Administration Guide. To learn more, see Application Management for SAP.