BSM End-to-End Workflow: Step 3. Set Up Data Sources

Install the following HP components (if they are not already installed) and configure them to monitor your business and communicate with BSM.

Business Process Monitor

Business Process Monitor (BPM) emulates end users by running the transactions included in a business transaction flow or application from various locations.

These transactions are contained within HP Virtual User Generator scripts, which are later stored in the BSM database for consumption and usage by the BPM monitors. If you own HP Software load testing tools like HP LoadRunner or HP Performance Center, you can consider reusing some of the scripts made for these tools for initial use in your BPM monitors.

To learn more about BPM, see Business Process Monitor (BPM).

  1. Install BPM instances. Install required number of BPM instances on host machines. For details, see "Deploying Business Process Monitor" in the Business Process Monitor Administrator's Guide.
  2. Install a script recording tool. Install either HP Virtual User Generator or HP QuickTest Professional. For details, see "Supported Recording Tools" in the Business Process Monitor Administrator's Guide, and in the relevant product documentation.
  3. Configure BPM data collection. Define BPM entities (applications, business transaction flows, and transactions) to monitor the business processes in your IT environment. For details, see "How to Set up Business Process Monitors" in the BSM Application Administration Guide.

Real User Monitor

Real User Monitor (RUM) monitors both user- and system- initiated network traffic between client machines and servers, and between servers. RUM passively collects network and server performance and availability data in real time.

To learn more about RUM, see Real User Monitor (RUM).

  1. Install RUM engines. Install RUM engines on host machines. For details, see "Installing the HP Real User Monitor Engine" in the Real User Monitor Administration Guide.
  2. Install RUM probes. Install RUM probes on host machines to listen to network traffic. For details, see "Installing the HP Real User Monitor Probe" in the Real User Monitor Administration Guide.
  3. Configure RUM data collection. Define the applications and associated entities (business transaction flows, transactions, actions, events, and so forth) that you want Real User Monitor to monitor. For details, see "How to Discover and Define Real User Monitor Applications" in the BSM Application Administration Guide.

SiteScope

SiteScope monitors collect key performance measurements and report topology on a wide range of back- and front-end infrastructure components.

To learn more about SiteScope, see SiteScope.

  1. Install SiteScope: Install SiteScope on one or more server machines. For details, see the "Installing SiteScope" part of the HP SiteScope Deployment Guide PDF.
  2. Connect SiteScope to BSM: Set up communication between SiteScope and BSM. For details, see "Integrating SiteScope with BSM" in the Using SiteScope Guide.
  3. Configure SiteScope data collection. Create SiteScope groups and subgroups to organize the monitors to be deployed, and then create monitors in these groups.
    • For details on configuring SiteScope to report metrics to BSM, see "HP Integration Settings" in the Using SiteScope Guide.
    • For details on configuring SiteScope to send events to BSM, see "How to Configure SiteScope to Communicate with BSM" in the BSM Application Administration Guide.

TransactionVision

TransactionVision delivers a transaction tracing solution to the Transaction Management application.

To learn more about TransactionVision, see TransactionVision.

  1. Plan your installation and install TransactionVision Processing Servers and Agents: Install TransactionVision-specific components in the BSM deployment environment. For details, see the TransactionVision Deployment Guide PDF.
  2. Configure TransactionVision data collection: Deploy and configure the TransactionVision Analyzers, Job Managers and Query Managers. Define communication links, data collection filters, and business transaction rules. For details, see "How to Administer TransactionVision" in the BSM Application Administration Guide.

Diagnostics

HP Diagnostics monitors performance and availability of your enterprise applications and BPM transactions, providing visibility across your enterprise's application infrastructure.

To learn more about HP Diagnostics, see Diagnostics.

  1. Install HP Diagnostics. Install the HP Diagnostics servers, Java and .NET agents, and remote monitoring collectors. For details, see the Diagnostics Installation and Configuration Guide (supplied with the HP Diagnostics software).
  2. Configure HP Diagnostics data collection. For Java agents, instrument the application servers; for .NET agents, instrument the application domains for monitoring; for collectors, define the specific instances on the remote systems to be monitored. You then configure the agent and collector data collection settings for your environment. For details, see the Diagnostics Installation and Configuration Guide.
  3. Connect HP Diagnostics with BSM. Register and set up communication between HP Diagnostics and BSM. For details, see the BSM - Diagnostics Integration Guide in the HP Software Product Manuals Web site (http://h20230.www2.hp.com/selfsolve/manuals).

Operations Manager

Operations Manager (HPOM) monitors physical and virtual infrastructure, and consolidates detected fault and system performance events.

To learn more about Operations Manager, see Operations Manager.

  1. Install Operations Manager and configure data collection. For details, see the Operations Manager documentation (supplied with the Operations Manager software).
  2. Connect Operations Manager with BSM. Set up communication of events and topology between Operations Manager and BSM. For details, see the BSM - Operations Manager Integration Guide in the HP Software Product Manuals Web site (http://h20230.www2.hp.com/selfsolve/manuals).

Network Node Manager i

Network Node Manager i (NNMi) monitors fault, availability, performance, and advanced network services for your physical and virtualized network infrastructure.

To learn more about NNMi, see Network Node Manager i (NNMi).

  1. Install NNMi and configure data collection. For details, see the NNMi documentation (supplied with the NNMi software).
  2. Connect NNMi with BSM. Set up communication of network performance-related events and topology between NNMi and BSM. For details, see the BSM - NNMi Integration Guide in the HP Software Product Manuals Web site (http://h20230.www2.hp.com/selfsolve/manuals).

BSM Connector (BSMC)

BSM Connector (BSMC) integrates events, metrics, and topology data from third-party systems into BSM.

To learn more, see BSM Connector (BSMC).

  1. Install BSM Connector. Install BSM Connector locally on the third-party system that provides the integration data. Alternatively, install BSM Connector on any system that meets the installation requirements if you want to access remote data sources such as databases or log files, or receive SNMP traps or Web service messages. For details, see "How to Create a Connection to a BSM Connector Server" in the BSM Application Administration Guide.
  2. Configure BSM Connector data collection. Within BSMC, create and activate policies that collect the integration data from the third-party domain manager or application.

Alternatively, you can set up and activate policies from within BSM using the BSM Connector Integrations user interface. For details, see "BSM Connector Integration Administration" in the BSM Application Administration Guide.

Data Flow Probe

The Data Flow Probe is required to run the Discovery process, which discovers the IT resources and components on your network, and saves them as CIs and relationships in the Run-time Service Model (RTSM). The Probe is also required for topology synchronization between the RTSM and other data sources, such as a CMS.

To learn more, see Discovery and Dependency Mapping (DDMA).

  1. Install the Data Flow Probe. Install the Data Flow Probe on a server machine. For details, see "Installing the Data Flow Probe on Windows" (for Windows) or "Installing the Data Flow Probe on Linux" (for Linux) in the Data Flow Probe Installation Guide.
  2. Configure Discovery data collection. Launch the Data Flow Probe and activate Discovery jobs. For details, see "Get Started with the Data Flow Probe" in the Data Flow Management Guide.