IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Hardware and software requirements
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Required software and memory requirements for using the OSLC Performance Monitoring service provider
If you plan to use the IBM Tivoli Monitoring OSLC Performance Monitoring service provider to integrate with other products by using OSLC linked data interfaces, install the following Jazz for Service Management version 1.1 or later prerequisite components if they are not already in your environment:
- IBM WebSphere Application Server V8.5.0.1
If you already have IBMWebSphere Application Server V8.0.0.2 or a later fix pack, V8.5.0.1 or a later fix pack, or V8.5.5.0 or a later fix pack in your environment, you can use it instead of installing WebSphere Application Server V8.5.0.1 from the Jazz for Service Management media. See Installing Jazz for Service Management for more details on installing into an existing WebSphere Application Server.
- Jazz for Service Management extension for IBM WebSphere
- DB2 database server for the Registry Services database if you do not already have a database server in your environment
- Registry Services V1.1 or later. In V6.3 fix pack 2, the OSLC Performance Monitoring service provider supports the Hot Standby environment for the Hub monitoring server and requires Registry Services V1.1.0.1 or later when this capability is enabled. If Registry Services is not V1.1.0.1 or later, the Automation Server will not start when the Hub monitoring server is enabled for Hot Standby.
- Security Services V1.1 or later (optional)
- IBM Tivoli Monitoring includes the Jazz for Service Management media.
- If you want the Performance Monitoring service provider to authenticate HTTP requests from OSLC clients, you should install and configure Security Services. Security Services enable non WebSphere based applications such as the Performance Monitoring service provider to participate in LTPA based single sign-on. See Single sign-on capability for more details on using Security Services and single sign-on with the Performance Monitoring service provider.
- Registry Services and Security Services must be installed into the same WebSphere Application Server.
- Registry Services support two types of authentication:
- Basic authentication which requires users and client applications to provide a user ID and password to Registry Services.
- HTTP client certificate authentication which requires the use of HTTPS and also requires users and client applications to provide a client certificate to Registry Services.
Because the Performance Monitoring service provider cannot be configured to provide an HTTP client certificate to Registry Services, you must configure Registry Services to use basic authentication when authentication is enabled. In this case, you must also configure Tivoli Enterprise Monitoring Automation Server with a user ID and password that you can use to authenticate with Registry Services.
For information about the WebSphere Application Server system requirements, see http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg27006921.
See Installing Jazz for Service Management (http://pic.dhe.ibm.com/infocenter/tivihelp/v3r1/topic/com.ibm.psc.doc_1.1.0/install/psc_c_install.html) for the following information:
- System requirements for Registry Services and Security Services.
- Installation technologies that are supported for the Jazz for Service Management components. Jazz for Service Management provides a launchpad application to guide you through a typical or custom installation procedure and also supports installation from an IBM Installation Manager file or network repository.
After you install and configure Registry Services and optionally Security Services, install and configure the Tivoli Enterprise Monitoring Automation Server. As part of the configuration, you configure connection information for Registry Services. See Install Tivoli Enterprise Monitoring Automation Server.
Parent topic:
Hardware and software requirements