IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Administrator's Guide > Introduction
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Performance Monitoring service provider
The Tivoli Enterprise Monitoring Automation Server component contains the Open Services Lifecycle Collaboration Performance Monitoring (OSLC-PM) service provider, and is installed on the same systems as your hub Tivoli Enterprise Monitoring Server.
The Performance Monitoring service provider registers monitoring resources with the Registry Services. Registry Services is a Jazz for Service Management integration service that provides a shared data repository for products in an integrated service management environment. Products that discover and manage shared IT resources can register these IT resources and the services they offer with Registry Services. Other products can consume data by querying Registry Services for the managed resources or the associated service providers of interest.
The Performance Monitoring service provider registers resources types such as Computer System, Software Server, Software Module, Database, IPAddress, and ServerAccessPoint on behalf of monitoring agents. These resources types are defined using the OSLC Common Resource Type Vocabulary (CRTV). Agents provide a template that maps their monitoring data to CRTV resources. The template is installed with the agent's monitoring server application support.
The Performance Monitoring service provider also supports the OSLC-PM RESTful API for retrieving linked data about monitored resources. It accommodates the RDF/XML, compact XML and HTML content types in HTTP GET requests. When RDF/XML and HTML content is requested, the API returns resource health metrics defined by the OSLC-PM domain and by the IBM Tivoli Monitoring private namespace.
To discover the resources that have health metrics available from the Performance Monitoring service provider, query Registry Services since the Performance Monitoring service provider does not provide OSLC query capability. Registry Services provides a query interface for retrieving service providers records, resource registration records, and reconciled resource records. The reconciled resource records and registration records contain HTTP URLs that can be used to retrieve information about the resource from the service provider that registered the resource. The Jazz for Service Management Integration Guide in the Jazz for Service Management Information Center contains information on querying Registry Services to learn about service providers and resources.
Security Services is an optional Jazz for Service Management component that enables non-WebSphere based applications such as the Performance Monitoring service provider to participate in LTPA based single sign-on. It should be installed and configured if you want the Performance Monitoring service provider to authenticate requests it receives from OSLC clients. This is the only authentication method supported by the service provider. See Authentication through the Tivoli Enterprise Monitoring Automation Server for more details.
You can use the Performance Monitoring service provider with the Tivoli Business Service Manager V6.1.1 dashboard server to display key health metrics from monitoring agents in the service tree without launching in context to the Tivoli Enterprise Portal. The health metrics are available if a resource such as a ComputerSystem or SoftwareServer has been registered with Registry Services by the Performance Monitoring service provider and the resource has also been discovered by the IBM Tivoli Monitoring Discovery Library Adapter or by a Tivoli Application Dependency Discovery Manager sensor when the TADDM OSLC service provider is also being used. The metrics are displayed in a hover preview dialog that also displays information from other service providers that have registered the same resource. For example, the OSLC service provider for Tivoli Application Dependency Discovery Manager provides configuration and change history information for registered resources in the hover preview dialog. For more information on how to setup the integration between the Performance Monitoring service provider, Tivoli Business Service Manager, Registry Services, and other supported service providers, see the Cross Product Integration Scenarios wiki.
You can also create your own OSLC client applications that retrieve resource information from Registry Services and health metrics for those resources from the Performance Monitoring service provider. Alternatively you can create your own OSLC service provider implementation to augment the information available for registered resources. For more information on creating these types of applications, see Get started with Registry Services on the Jazz for Service Management wiki.
If you create your own OSLC client application, take note that the rr:sourceRecord properties that are retrieved from Registry Services for registration or reconciliation records can change if you have a Hot Standby monitoring environment. The rr:sourceRecord property contains the URL that is used to query an OSLC service provider for more details about a resource. When Hot Standby is used, the rr:sourceRecord URL for a resource points to the Performance Monitoring service provider for the acting hub monitoring server. When the standby hub monitoring server becomes the acting hub, the URLs are updated to specify the host name and port number of the Performance Monitoring service provider for the new acting hub. Therefore, one of the following scenarios must take place:
- If your OSLC client application caches the rr:sourceRecord property values, it must periodically query Registry Services to determine whether the cached URLs must be updated.
OR
- If your OSLC client application tries to use a cached rr:sourceRecord URL for a resource and a response is not received from the Performance Monitoring service provider, then it can query Registry Services to determine whether the rr:sourceRecord value changed.
If the Performance Monitoring service provider for the acting and standby monitoring servers are both up and an OSLC client sends a request to the Performance Monitoring service provider for the standby hub monitoring server, the service provider returns an HTTP 301 redirect response if it can determine the host name of the acting hub and Performance Monitoring service provider; otherwise, it returns an HTTP 404 response.
For more information about OSLC and Loosely Coupled Integration, see the following links:
- OSLC community
- Performance Monitoring working group
- Reconciliation working group and Common Resource Type Vocabulary
- Loosely coupled integration at ISM Connect
- IBM Tivoli Monitoring OSLC private namespace schema
For information on installing and configuring the Tivoli Enterprise Monitoring Automation Server and Performance Monitoring service provider, see the IBM Tivoli Monitoring Installation and Setup Guide.
Parent topic:
Introduction