Required software

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

The following table lists the software required for IBM Tivoli Monitoring.

Required software for IBM Tivoli Monitoring

Product Supported version Component where the software is required
Monitor server Portal server Portal desktop client Portal browser client Monitor agent
Distributed systems: IBM Runtime Environment for Java JRE V1.6 ³ X¹
Distributed systems: IBM Runtime Environment for Java JRE V1.7 X³ X³ X³ X¹
Distributed systems: Oracle Java SE Runtime Environment JRE V1.6.xx, V1.7.xx X X
z/OS systems: IBM 31-bit or 64-bit SDK for z/OS, Java Technology Edition IBM Java SDK for z/OS at V6 or later X⁴
z/OS systems: z/OS UNIX System Services X^{4 5}
z/OS systems: Integrated Cryptographic Service Facility X⁶ X⁷
For Linux computers: a Korn shell interpreter ksh package provided by the Linux distribution X X X X²
AIX only: xlC Runtime Environment Component xlC.aix61.rte level 11.1 is required for monitoring server and portal server. For monitoring agent, level 9 or higher is required. X X X
Database A supported RDBMS is required for the Tivoli Enterprise Portal Server and the Tivoli Data Warehouse. Supported database platforms for the portal server are listed in Table 1. Supported database platforms for the Tivoli Data Warehouse are listed in Table 1.
Each database requires a driver. For detailed information, see Tivoli Data Warehouse solutions and subsequent chapters about the Tivoli Data Warehouse.

If the JRE is not installed on the computer on which the browser is launched, you are prompted to download and install it from the portal server. The Windows user account must have local administrator authority to download and install the JRE. The portal browser clients can use either the 32-bit or 64-bit JRE at version 1.6 or 1.7. The default JRE available from the portal server is dependent on whether the portal server was installed or upgraded. On a pristine install of the portal server, IBM JRE 1.7 is the default JRE for portal browser clients. However, if the portal server was upgraded, IBM JRE 1.6 remains the default JRE.

The Korn shell (any version) is also required when installing the monitoring agent on AIX, HP-UX, or Solaris systems.

IBM JRE 1.7 is installed with the monitoring server, portal server, and portal desktop client components on distributed systems. IBM JRE 1.6 is also installed on the portal server for use by portal browser clients.

If the self-describing agent function is enabled, install this software on the z/OS systems where your monitoring servers are installed.

A file system (either HFS or zFS), and user security must be configured for UNIX System Services on the z/OS systems where monitoring servers are installed in order to use the self-describing agent function.

See Global Security Toolkit for configuration steps that are required if Integrated Cryptographic Service Facility (ICSF) is not installed and enabled on a z/OS system with a monitoring server. Cryptographic coprocessor cards are not required to use ICSF.

If the Integrated Cryptographic Service Facility (ICSF) is not installed and enabled on a z/OS system with a monitoring agent using the Tivoli Enterprise Monitoring Agent framework at V6.3 or later, the monitoring agent cannot validate security tokens included with Take Action requests but the agent will still execute the Take Action request. (The security tokens are used to verify that the request originated from a monitoring server or portal server in your environment and to generate an audit record identifying the user who initiated the request.) Cryptographic coprocessor cards are not required to use ICSF.

Parent topic:
Hardware and software requirements

+
Search Tips | Advanced Search

Product	Supported version	Component where the software is required
Monitor server	Portal server	Portal desktop client	Portal browser client	Monitor agent
Distributed systems: IBM Runtime Environment for Java	JRE V1.6		³		X¹
Distributed systems: IBM Runtime Environment for Java	JRE V1.7	X³	X³	X³	X¹
Distributed systems: Oracle Java SE Runtime Environment	JRE V1.6.xx, V1.7.xx			X	X
z/OS systems: IBM 31-bit or 64-bit SDK for z/OS, Java Technology Edition	IBM Java SDK for z/OS at V6 or later	X⁴
z/OS systems: z/OS UNIX System Services		X^{4 5}
z/OS systems: Integrated Cryptographic Service Facility		X⁶				X⁷
For Linux computers: a Korn shell interpreter	ksh package provided by the Linux distribution	X	X	X		X²
AIX only: xlC Runtime Environment	Component xlC.aix61.rte level 11.1 is required for monitoring server and portal server. For monitoring agent, level 9 or higher is required.	X	X			X
Database	A supported RDBMS is required for the Tivoli Enterprise Portal Server and the Tivoli Data Warehouse. Supported database platforms for the portal server are listed in Table 1. Supported database platforms for the Tivoli Data Warehouse are listed in Table 1. Each database requires a driver. For detailed information, see Tivoli Data Warehouse solutions and subsequent chapters about the Tivoli Data Warehouse.
If the JRE is not installed on the computer on which the browser is launched, you are prompted to download and install it from the portal server. The Windows user account must have local administrator authority to download and install the JRE. The portal browser clients can use either the 32-bit or 64-bit JRE at version 1.6 or 1.7. The default JRE available from the portal server is dependent on whether the portal server was installed or upgraded. On a pristine install of the portal server, IBM JRE 1.7 is the default JRE for portal browser clients. However, if the portal server was upgraded, IBM JRE 1.6 remains the default JRE. The Korn shell (any version) is also required when installing the monitoring agent on AIX, HP-UX, or Solaris systems. IBM JRE 1.7 is installed with the monitoring server, portal server, and portal desktop client components on distributed systems. IBM JRE 1.6 is also installed on the portal server for use by portal browser clients. If the self-describing agent function is enabled, install this software on the z/OS systems where your monitoring servers are installed. A file system (either HFS or zFS), and user security must be configured for UNIX System Services on the z/OS systems where monitoring servers are installed in order to use the self-describing agent function. See Global Security Toolkit for configuration steps that are required if Integrated Cryptographic Service Facility (ICSF) is not installed and enabled on a z/OS system with a monitoring server. Cryptographic coprocessor cards are not required to use ICSF. If the Integrated Cryptographic Service Facility (ICSF) is not installed and enabled on a z/OS system with a monitoring agent using the Tivoli Enterprise Monitoring Agent framework at V6.3 or later, the monitoring agent cannot validate security tokens included with Take Action requests but the agent will still execute the Take Action request. (The security tokens are used to verify that the request originated from a monitoring server or portal server in your environment and to generate an audit record identifying the user who initiated the request.) Cryptographic coprocessor cards are not required to use ICSF.