IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Introduction > Components of the monitoring architecture
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Tivoli Enterprise Monitoring Automation Server
The Tivoli Enterprise Monitoring Automation Server is an optional component that can be installed on the same system as the hub monitoring server. It extends the functionality of the hub monitoring server.
The automation server includes the Open Services Lifecycle Collaboration Performance Monitoring (OSLC-PM) service provider. The Performance Monitoring service provider registers resources types such as Computer System, Software Server, Database, Software Module and Service Instance on behalf of monitoring agents. These resources types are defined using the Common Resource Type Vocabulary (CRTV). Agents provide a template that maps their monitoring data to CRTV resources. The template is installed with the monitoring server application support of the agent. Products such as IBM Tivoli Monitoring 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. In the query responses, Registry Services returns links to the service providers that can be queried to retrieve more information about the managed resources.
The Performance Monitoring service provider also supports the OSLC-PM RESTful API for retrieving linked data about monitored resources. It accommodates HTTP GET requests for the RDF/XML, compact XML and HTML content types. When RDF/XML and HTML content is requested, the API returns resource metrics defined by the OSLC-PM domain and the IBM Tivoli Monitoring private namespace. For more information about OSLC and Loosely Coupled Integration, see the following links:
- OSLC community
- Performance Monitoring working group
- IBM Tivoli Monitoring OSLC private namespace schema
- Reconciliation working group and Common Resource Type Vocabulary
- Loosely coupled integration at ISM Connect
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. The application servers for OSLC clients also must be configured for single sign-on with Security Services and include an LTPA token in HTTP GET requests sent to the service provider. When the Performance Monitoring service provider receives an HTTP GET request from an OSLC client, it forwards the LTPA token to Security Services to authenticate the request. If the request does not contain a LTPA token or Security Services indicates that the token is not valid or has expired, the Performance Monitoring service provider returns an HTTP status code indicating that the request could not be authenticated. For the V6.3 release of IBM Tivoli Monitoring, the Performance Monitoring service provider assumes that Registry Services and Security Services are installed into the same WebSphere Application Server.
See the Performance Monitoring service provider topic in the IBM Tivoli Monitoring Administrator's Guide and Install Tivoli Enterprise Monitoring Automation Server.
For more information about Registry Services and Security Services, see the Jazz for Service Management Information Center.
For more information about OSLC product integration scenarios, see Cross Product Integration scenarios.
Parent topic:
Components of the monitoring architecture