Integrating SiteScope Data with BSM's Configuration Items

When a monitor instance is added to a SiteScope reporting data to BSM, that monitor creates a corresponding configuration item (CI) in Run-time Service Model (RTSM). For details on understanding configuration items, see the introduction section in the RTSM Administration Guide.

The SiteScope monitors that populate RTSM include both actual monitors and the groups in which they are created.

Monitor Types and Topology Reporting

SiteScope reports different levels of topology data to RTSM depending on the type of monitor and the options selected for the monitor. SiteScope forwards the topology to create or update a CI under the following conditions:

When working with specific monitors, you do not select a topology and the topology is preconfigured with the necessary data for the integration.

Creating Relationships Between Monitors and CIs

You can also create relationships between SiteScope monitor CIs and existing CIs in RTSM. This relationship enables the monitor to pass HI status information to the CI to which it is attached, even if that CI was not created from a topology forwarded by SiteScope.

You can create these relationships in SiteScope or in SAM Administration. For details, see task step Create relationships between SiteScope monitors and existing CIs in RTSM - optional.

Aging of CIs in RTSM

In RTSM, CIs that have had no activity over a period of time are removed from the database. The CIs created from SiteScope data are also subject to this aging policy. To prevent the aging policy from acting on CIs that SiteScope has sent to BSM, SiteScope synchronizes the data it sends to BSM. The synchronization refreshes the data for those CIs and creates activity on the CIs.

For details on setting the time interval for topology synchronization, see Topology Settings. For details on the aging mechanism, see Working with CIs in the Modeling Guide.

Note:

Synthetic monitors and groups created by the EMS integration monitors that use Measurement field mapping are subject to the aging process regardless of the synchronization.
To prevent CIs for EMS integration monitors being removed from RTSM when aging is enabled, EMS topology is resent during a hard synchronization of SiteScope. In addition, you can enable topology resending as part of an anti-aging process by adding the property _reportEmsCIsAsPartOfAntiAging=true to the <SiteScope root directory>\groups\master.config file.
If you delete a CI from RTSM you must perform a resynchronization or a hard synchronization of SiteScope (in Integration Preferences), or you must wait for a restart of SiteScope so the CI is restored to RTSM. This is due to the CI cache in SiteScope that prevents SiteScope from sending an unchanged CI twice. For details, see the section on BSM Integration Preferences in the Using SiteScope Guide in the SiteScope Help.

Managing Indicator Assignments in System Availability Management

Note: This section is relevant only to those users connecting to SiteScope version 11.00 or later.

SiteScope metrics that are mapped to indicators, are stored and managed in the Indicator Assignments repository in SAM Administration. For details on the Indicator Assignments repository, see Indicator Assignments.

Assigning SiteScope Metrics to Indicators

Note: This section is relevant only to those users connecting to SiteScope version 11.00 or later.

When configuring monitor instances, you can also map a metric to an indicator. Indicators provide a more detailed view of the health of a CI when SiteScope is reporting data to BSM. SiteScope monitor metrics are mapped to indicators on a monitor type basis as follows:

Monitors of supported environments and monitors that have a defined topology have indicators assigned to metrics by default. For details of these monitors, see Monitor Types and Topology Reporting above. For the list of default indicator assignments, see Indicator Mapping Alignment.
For SiteScope monitors that do not have a defined topology, there are no default indicator mappings, since these monitors can be linked to different CI types, and a single mapping cannot be set. For these monitors, you can map metrics to the appropriate indicators for the CI type linked to the monitor. For a list of monitors that do not have a defined topology, see Monitors Not Reporting Topology Data By Default.

You can change the default metrics mappings in SiteScope. If indicator mappings are modified locally in SiteScope, these mappings are not overridden by the centralized repository mappings when SiteScope downloads the latest mappings from BSM. This enables you to:

Override indicators for a monitor instance or some metrics of a monitor.
Configure non-default indicators in templates. Note that the CI type for custom topology and metric mappings is not configurable through variables in templates (they should be predefined in a template).
Configure indicators for alerts. Since the CI type of a triggered alert is not always known when configuring an alert for groups or for monitors reporting a CI per metric (see Monitors Reporting CI Per Metric), you can manually enter the indicator and indicator state for an alert. For details, see HP Operations Manager Integration Settings in the Using SiteScope Guide in the SiteScope Help.

For task details on mapping SiteScope metrics to indicators, see Map Indicators to metrics.

For user interface details, see Indicator Settings in the Using SiteScope Guide in the SiteScope Help.

When are Health Indicators Created?

Events in SiteScope are based on SiteScope monitor metric status changes and alerts being triggered. Events are created after the first event arrives to the CI. For more details, see "Integrating SiteScope with HP Operations Manager Products" in the SiteScope section of the HP Software Integrations site.
Metrics are created when the monitor topology is reported to RTSM. For more details, see Reporting Discovered Topologies to BSM.

Discovery Scripts and the Package Manager

The scripts that enable SiteScope to act as a discovery probe are stored on the BSM server in the SiteScope package. When SiteScope is configured to discover an application's topology, SiteScope downloads the appropriate script from the BSM server. It then uses the script to perform the discovery while monitoring the application.

The SiteScope package includes scripts and other SiteScope-related RTSM resources, such as views and enrichments. You can access this package in BSM in Admin > RTSM Administration > Administration > Package Manager. The package is a factory package, meaning that the out-of-the-box configurations for the package enable it to perform the discoveries in SiteScope. For details on working with packages, see Package Administration in the Modeling Guide.

Note: Advanced users may want to modify the topology scripts within the package. Be warned that the SiteScope package uses scripts from other packages which may be shared by SiteScope and Data Flow Management. Any changes made to the scripts in the package can also affect Data Flow Management.

Any changes made to the topology script that influence the way a topology is reported to BSM can affect all the applications that use those topologies, including BSM applications and Operations Management.

Topology Script Properties File

If you are working in a secure BSM installation that has a certificate, you may have to insert the following line into the <SiteScope root directory>\discovery\discovery_agent.properties file: appilog.agent.Probe.BasicAuth.Realm=authRealm.

Where authRealm is a variable for Basic Authentication Realm. If you want to find out what realm a given URL belongs to, you can open the URL with a Web browser and see the first line in the popup box.

Note: When you modify the discovery_agent.properties, you must restart SiteScope to enable your changes to take effect.