IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Pre-deployment phase > Understanding Tivoli Monitoring and your network > Determine where to place the Tivoli Monitoring components
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Tivoli Enterprise Monitoring Automation Server, Performance Monitoring service provider, Registry Services, and Security Services
The Tivoli Enterprise Monitoring Automation Server is installed with the Hub monitoring server on Windows and UNIX based operating systems. It extends the Hub monitoring server by providing the Open Services Lifecycle Collaboration Performance Monitoring (OSLC-PM) service provider. The service provider registers monitoring resources such as computer systems, software servers, and databases with the Registry Services and also responds to HTTP GET requests for resource health metrics from OSLC clients.
Registry Services is a Jazz for Service Management component that is installed into WebSphere Application Server. Products that discover and manage shared IT resources can register these IT resources and the services they offer with Registry Services. Other products (OSLC clients) 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 have more information about the managed 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. 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 an LTPA token or Security Services indicates that the token is not valid or has expired, the Performance Monitoring service provider returns an HTTP 401 status code to indicate that the request could not be authenticated.
For the current 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 Installing Jazz for Service Management for recommendations on whether to install Registry Services and Security Services features on the same systems as other Jazz for Service Management components: http://pic.dhe.ibm.com/infocenter/tivihelp/v3r1/topic/com.ibm.psc.doc_1.1.0/install/psc_c_install.html.
Parent topic:
Determine where to place the Tivoli Monitoring components