Chapter 3. Hardware and software requirements

Chapter 3. Hardware and software requirements The following sections provide specific information about the memory, software, and hardware requirements for installing IBM Tivoli Monitoring. This section does not show agent-specific requirements (such as supported application levels or any hardware requirements unique to a certain agent). For this information, see the user's guide (for agents on distributed systems) or configuration guide (for agents on mainframe systems) for the agent that you are installing. You can perform prerequisite scanning for agents before carrying out an installation. The two mechanisms available are a manually executed stand-alone prerequisite scanner and a remote prerequisite scanner facility that extends the capabilities of IBM Tivoli Monitoring's remote deployment component. For more information, see Prerequisite Scanner for IBM Tivoli Monitoring agents on page 48. Supported operating systems The following tables show which operating systems are supported for the different IBM Tivoli Monitoring components: monitoring, automation, portal, portal client, monitoring agent, Warehouse Proxy, Warehouse Proxy Summarization and Pruning Agent, and Tivoli Performance Analyzer. 1. In the following tables, an indicates a supported component on the platform. If the platform being discussed supports 64 bit applications but only a 32 bit version of the Tivoli Monitoring component is supported on that platform, the is replaced by "32 bit." 2. The tables in this section show support information for monitoring components. For prerequisite information about applications that are installed into the Dashboard Application Services Hub, such as the Tivoli Authorization Policy Server, and the IBM Infrastructure Management Dashboards for Servers, see the Hardware and software requirements in the Jazz for Service Management information center at http://pic.dhe.ibm.com/infocenter/tivihelp/v3r1/topic/com.ibm.psc.doc_1.1.0/install/ psc_c_install_prereqs.html. The tivcmd Command Line Interface for Authorization Policy is also supported on the same operating systems as IBM Dashboard Application Services Hub. The tivcmd Command Line Interface for Authorization Policy is also supported on the same 32 bit and 64 bit Window operating systems, and the 32 bit and 64 bit Linux Intel based operating systems, that are supported by the IBM Tivoli Monitoring portal client as shown in the tables below. However, on a 64 bit zseries Linux system, you must install the 32 bit version of the tivcmd CLI. Table 10 shows the support for monitoring components on Windows computers. Table 10. Supported Windows operating systems Operating system Monitoring and automation 1 4 client 2 OS monitoring agent 3 Warehouse Proxy Agent Summarization and Pruning Agent Tivoli Performance Analyzer Windows Server 2003 Standard Edition R2 on Intel x86-32 (32 bit) Windows Server 2003 Standard Edition R2 on x86-64 (64 bit) Windows Server 2003 Enterprise Edition R2 on Intel x86-32 (32 bit) Copyright IBM Corp. 2005, 2013 75

Table 10. Supported Windows operating systems (continued) Operating system Windows Server 2003 Enterprise Edition R2 on x86-64 (64 bit) Windows Server 2003 Datacenter Edition R2 on Intel x86-32 (32 bit) Windows Server 2003 Datacenter Edition R2 on Intel x86-64 (64 bit) Monitoring and automation 1 4 client 2 OS monitoring agent 3 Warehouse Proxy Agent Summarization and Pruning Agent Tivoli Performance Analyzer Windows Server 2008 Standard Edition on Intel x86-32 (32 bit) 2, Windows Server 2008 Standard Edition on Intel 32 bit 32 bit x86-64 (64 bit) 2 Windows Server 2008 Enterprise Edition on Intel x86-32 (32 bit) 2, Windows Server 2008 Enterprise Edition on Intel 32 bit 32 bit x86-64 (64 bit) 2, Windows Server 2008 Datacenter Edition on Intel x86-32 (32 bit) 2 Windows Server 2008 Datacenter Edition on 32 bit 32 bit Intel x86-64 (64 bit) 2 Windows 7 Enterprise Edition on Intel x86-32 (32 bit) Windows 7 Enterprise Edition on Intel x86-64 (64 bit) Windows 7 Professional Edition on Intel x86-32 (32 bit) Windows 7 Professional Edition on Intel x86-64 (64 bit) Windows 7 Ultimate Edition on Intel x86-32 (32 bit) Windows 7 Ultimate Edition on Intel x86-64 (64 bit) Windows 8 Pro on Intel x86-32 (32 bit) Windows 8 Pro on Intel x86-64 (64 bit) Windows 8 Enterprise on Intel x86-32 (32 bit) Windows 8 Enterprise on Intel x86-64 (64 bit) 76 IBM Tivoli Monitoring: Installation and Setup Guide

Table 10. Supported Windows operating systems (continued) Operating system Monitoring and automation 1 4 client 2 OS monitoring agent 3 Warehouse Proxy Agent Summarization and Pruning Agent Tivoli Performance Analyzer Windows Server 2008 R2 Standard Edition on Intel 32 bit 32 bit x86-64 (64 bit) 2, Windows Server 2008 R2 Enterprise Edition on Intel 32 bit 32 bit x86-64 (64 bit) 2, Windows Server 2008 R2 Datacenter Edition on 32 bit 32 bit Intel x86-64 (64 bit) 2 Windows Server 2008 R2 Server Core on Intel x86-64 (64 bit) Windows Server 2012 Essentials Edition on Intel x86-64 (64 bit) Windows Server 2012 Standard edition on Intel x86-64 (64 bit) Windows Server 2012 Datacenter edition on Intel x86-64 (64 bit) 32 bit 32 bit 32 bit 32 bit 32 bit 32 bit 1. The Tivoli Enterprise Server runs an instance of embedded WebSphere Application Server V8, so the system must also meet the minimum requirements for WebSphere. For information on the minimum service pack level required to install and run the embedded WAS in Tivoli Enterprise Server, see http://www-01.ibm.com/support/ docview.wss?uid=swg27021246. 2. The Tivoli Enterprise desktop client is supported on marked platforms. The Tivoli Enterprise browser client can run from the marked platforms in the browser versions documented in Supported browser versions on page 90. The Tivoli Enterprise Java webstart client can run from the marked platforms. 3. The OS monitoring agent column indicates the platforms on which an operating system monitoring agent is supported. This column does not indicate that any agent runs on any operating system. For example, to monitor a Linux computer, you must use a Linux monitoring agent, not a Windows monitoring agent. For information about the operating systems supported for non-os agents, see the documentation for the specific agents you are using in your environment. 4. Beginning with V6.3, Microsoft Visual C++ 2008 Redistributable Package (32 bit and 64 bit) is a prerequisite for the Tivoli Enterprise Server on Windows systems (and the System Monitor Agent on Windows). For more information go to the Microsoft Download Center at http://www.microsoft.com/en-us/download/default.aspx. Table 11 shows the support for monitoring components on UNI (non-linux), IBM i, and z/os computers. Table 11. Supported UNI, IBM i, and z/os operating systems Operating system Monitoring and automation client OS monitoring agent 1, 2 Warehouse Proxy Agent 3 Summarization and Pruning Agent Tivoli Performance Analyzer AI V6.1 (64 bit) 4 12 32 bit AI V7.1 (64 bit) 413 32 bit Solaris V10 (SPARC) (32/64 bit) 5 32 bit 32 bit 32 bit 32 bit Solaris V10 (Intel x86-64) (64 bit) 5 32 bit Chapter 3. Hardware and software requirements 77

Table 11. Supported UNI, IBM i, and z/os operating systems (continued) Operating system Solaris V11 (SPARC) (32/64 bit) Solaris V11 (Intel x86-64) (64 bit) Monitoring and automation client OS monitoring agent 1, 2 Warehouse Proxy Agent 3 Summarization and Pruning Agent Tivoli Performance Analyzer 32 bit 32 bit 32 bit 32 bit 32 bit Solaris Zones (SPARC) (32/64 bit) 8 32 bit 32 bit 32 bit 32 bit Solaris Zones (Intel x86-64) (64 bit) 8 32 bit HP-U 11i v2 (64 bit) 10 11 on PA-RISC HP-U 11i v3 (64 bit) on PA-RISC 1011 HP-U 11i v2 on 9, 10, 11 Integrity (IA64) HP-U 11i v3 on 9, 10, 11 Integrity (IA64) i5/os 5.4 (64 bit) 6 IBM i 6.1 (64 bit) 6 IBM i 7.1 (64 bit) 6 z/os 1.12 (31/64 bit) 7,8 31 bit 14 z/os 1.13 (31/64 bit) 7,8 31 bit 14 1. The OS monitoring agent column indicates the platforms on which an operating system monitoring agent is supported. This column does not indicate that any agent runs on any operating system. For example, to monitor a Linux computer, you must use a Linux monitoring agent, not a Windows monitoring agent. For information about the operating systems supported for non-os agents, see the documentation for the specific agents you are using in your environment. 2. If you are installing the OMEGAMON E for Messaging agent on a 64-bit operating system, you must install the 32-bit version of the agent framework. 3. Configuration of the Warehouse Proxy Agent requires an Window System (also known as the 11 GUI) on the computer where you are configuring it. Alternatively, you can run the following command to use an terminal emulation program (such as Cygwin) that is running on another computer: export DISPLAY=my_windows_pc_IP_addr:0.0 where my_windows_pc_ip_addr is the IP address of a computer that is running an terminal emulation program. 4. Version 11.1 of the AI L C/C++ runtime must be installed. See the following Web site for installation instructions: http://www-01.ibm.com/support/docview.wss?uid=swg24031426. 5. There are some limitations on installing into Solaris 10 when zones are configured. See Installing into Solaris zones on page 135. 6. SNMP version 3 is not supported on IBM i. 7. For information about installing the monitoring on z/os, see the program directory that comes with that product. 8. The OS monitoring agent for z/os computers is part of the IBM Tivoli OMEGAMON for z/os product. 78 IBM Tivoli Monitoring: Installation and Setup Guide

Table 11. Supported UNI, IBM i, and z/os operating systems (continued) Operating system Monitoring and automation client OS monitoring agent 1, 2 Warehouse Proxy Agent 3 Summarization and Pruning Agent Tivoli Performance Analyzer 9. You cannot upgrade either the OS or Log Alert agents that you currently have running on an HP-U 11i v2 (B.11.23) on an Integrity (IA64) computer in PA-RISC mode prior to v6.1 fix pack 4. Fix packs prior to fix pack 4 did not run in native 64-bit mode by default. You must first uninstall the agent if the version is previous to the V6.1 fix pack 4 version. 10. The 32-bit kernel still requires a 64-bit processor. Ensure that any HP-U managed system is based on PA-RISC2 architecture. From the native kernel mode (for example, 64 bit if the system is 64-bit based), run the following command: file /stand/vmunix. This returns the native architecture type. For example: /stand/vmunix: PA-RISC1.1 executable -not stripped. Verify the architecture is at least PA-RISC2. 11. Prerequisite patches for HP-U R11: PHSS_26946, PHSS_33033, and PHCO_34275 or later. 12. The Tivoli Enterprise runs an instance of embedded WebSphere Application Server V8, so users of AI must also meet the minimum requirements for WebSphere. For information on the minimum service pack level required to install and run the embedded WAS in Tivoli Enterprise Server, see http://www-01.ibm.com/support/ docview.wss?uid=swg27021246. 13. On AI 7.1 TL1, Service Pack (SP) 2 or later is required for all components. If you cannot upgrade to SP 2, you can download the fix for APAR IV09585. For more information, see the IBM Tivoli Monitoring Troubleshooting Guide. You must restart your system after you have upgraded to SP 2 or downloaded the fix for APAR IV09585. 14. The Tivoli Enterprise Automation Server is not supported on z/os. Table 12 shows the monitoring components supported on Linux operating systems. client 1, Table 12. Supported Linux operating systems Operating system Monitoring and automation 8 78 8 OS monitoring 2, 3, 8 agent Asianux 3.0 for Intel x86-32 (32 bit) 6 Asianux 3.0 on Intel x86-64 (64 bit) 6 Red Flag 5.0 for Intel x86-32 (32 bit) 6 Warehouse Proxy Agent, 8 Summarization and Pruning Agent 8 Tivoli Performance Analyzer 8 RedHat Enterprise Linux 5 Intel x86-32 9 (32 bit) 4 6 RedHat Enterprise Linux 5 on Intel 9 32 bit x86-64 (64 bit) 4 6 RedHat Enterprise Linux 5 on iseries and pseries (64 bit) 4 RedHat Enterprise Linux 5 on zseries 6 9 (64 bit) 4 6 RedHat Enterprise Linux 5 on zseries (31 bit) RedHat Enterprise Linux 6 Intel x86-32 (32 bit) 4 6 RedHat Enterprise Linux 6 on Intel 32 bit x86-64 (64 bit) 4 6 Chapter 3. Hardware and software requirements 79

Table 12. Supported Linux operating systems (continued) Operating system RedHat Enterprise Linux 6 on iseries and pseries (64 bit) 5 Monitoring and automation 8 client 1, 78 8 OS monitoring 2, 3, 8 agent RedHat Enterprise Linux 6 on zseries (31 bit) 4 6 Warehouse Proxy Agent, 8 Summarization and Pruning Agent 8 RedHat Enterprise Linux 6 on zseries 6 (64 bit) 4 6 SuSE Linux Enterprise Server 10 10 Intel x86-32 (32 bit) 6 SuSE Linux Enterprise Server 10 10 on Intel x86-64 (64 bit) 6 SuSE Linux Enterprise Server 10 for iseries and pseries (64 bit) SuSE Linux Enterprise Server 10 5 10 for zseries (64 bit) 6 Tivoli Performance Analyzer 8 SuSE Linux Enterprise Server 11 on Intel x86-32 (32 bit) 6 SuSE Linux Enterprise Server 11 on Intel x86-64 (64 32 bit bit) 46 SuSE Linux Enterprise Server 11 for iseries and pseries (64 bit) SuSE Linux Enterprise Server 11 5 for zseries (64 bit) 6 VMWare ES Server 3.0.1 on Intel x86-32 (32 bit) VMWare ES Server 3.0.1 on Intel x86-64 (64 bit) VMWare ES Server 3.5 on Intel x86-32 (32 bit) VMWare ES Server 3.5 on Intel x86-64 (64 bit) VMWare ES Server 4.0 on Intel x86-32 (32 bit) native Linux OS agent native Linux OS agent native Linux OS agent native Linux OS agent native Linux OS agent 80 IBM Tivoli Monitoring: Installation and Setup Guide

Table 12. Supported Linux operating systems (continued) Operating system VMWare ES Server 4.0 on Intel x86-64 (64 bit) Monitoring and automation 8 client 1, 78 8 OS monitoring 2, 3, 8 agent native Linux OS agent Warehouse Proxy Agent, 8 Summarization and Pruning Agent 8 Tivoli Performance Analyzer 8 1. The Tivoli Enterprise desktop client is supported on marked platforms. The Tivoli Enterprise browser client can run from the marked platforms in the browser versions documented in Supported browser versions on page 90. The Tivoli Enterprise Java webstart client can run from the marked platforms. 2. The OS monitoring agent column indicates the platforms on which an agent is supported. This column does not indicate that any agent runs on any operating system. For example, to monitor a Linux computer, you must use a Linux monitoring agent, not a Windows monitoring agent. An "" symbol in the column indicates that an operating system agent is available for the specific operating system that is named in the row where the "" is located. 3. The Linux OS Monitoring Agent requires the installation of the latest versions of the following libraries: libstdc++ libgcc compat-libstdc++ These libraries are available on the Linux operating system installation media and Service Packs. Each library can have multiple packages, and each should be installed. If you are on a 64 bit system you must have the 32 bit and 64 bit versions of these libraries. 4. Several Linux operating systems now enable now enables SELinux (security-enhanced Linux) by default, which interferes with the installation, configuration, and operation of IBM Tivoli Monitoring. To ensure the proper operation of the V6.1.x and V6.2.x, and V6.3 releases, the SELinux setting must be either disabled, or changed from enforcing mode to permissive mode when enabled. When the permissive mode is chosen, the system log will contain entries regarding which Tivoli Monitoring binaries have triggered the SELinux security condition. However, under the permissive mode, these entries are for auditing purpose only, and will operate normally. 5. For Linux on System z, a 64 bit Tivoli Enterprise Server requires running a 64 bit DB2 instance under Linux. 6. The Tivoli Enterprise runs an instance of embedded WebSphere Application Server V8, so the system must also meet the minimum requirements for WebSphere. For information on the minimum service pack level required to install and run the embedded WAS in Tivoli Enterprise Server, see http://www-01.ibm.com/support/ docview.wss?uid=swg27021246. 7. When installing as a nonroot user, 32 bit libpam is required for the Tivoli Enterprise Server on a 64 bit Intel Linux installation. 8. The following libraries are required to run Manage Tivoli Enterprise Monitoring Services (CandleManage) on Linux systems: v libcursor v libfixes v libi 9. RedHat Enterprise Linux V5.6 or later is required for the Tivoli Enterprise Server. 10. SuSE Linux Enterprise Server 10.3 or later is required for the Tivoli Enterprise Server. The following table lists the operating system patches required for the IBM Global Security Toolkit (GSKit), which is used to provide security between monitoring components. GSKit is installed automatically when you install Tivoli Management Services components and the tivcmd Command Line Interface. Table 13. Operating system requirements for IBM GSKit Operating system Patch required Solaris V9 111711-08 Solaris V10 none Solaris V11 none HP-U V11i PHSS_26946, PHSS_33033, PHCO_34275 AI V6.x xlc.aix61.rte 9.0 Chapter 3. Hardware and software requirements 81

Table 13. Operating system requirements for IBM GSKit (continued) Operating system Patch required Windows Server 2003 none Red Hat Enterprise Linux 6 x86 (32 bit) ksh-20100621-2.el6.i686.rpm Red Hat Enterprise Linux 6 x86-64 (64 bit) ksh-20091224-1.el6.x86_64.rpm glibc-2.12-1.7.el6.i686.rpm libgcc-4.4.4-13.el6.i686.rpm SuSE Linux Enterprise Server 10 Intel SuSE Linux Enterprise Server 11 Intel nss-softokn-freebl-3.12.7-1.1.el6.i686.rpm none none Supported databases for Tivoli Enterprise Server IBM Tivoli Monitoring includes an embedded version of the Apache Derby database for default use as the Tivoli Enterprise Server database. The database is installed when installing the portal, and it runs within the portal 's Java virtual machine. The embedded Derby database is intended for use only by small to medium-size businesses. It is not intended for large IBM Tivoli Monitoring environments or for sites running a large number of Tivoli Enterprise clients. Derby has been tested with up to 20 portal clients, and it does require higher CPU and memory usage than DB2 for Linux, UNI, and Windows. If the embedded Derby database is not suitable for your environment, you can use one of the supported databases in Table 14. Note that the database and the portal must be installed on the same computer. IBM Tivoli Monitoring V6.3 includes DB2 Enterprise Server Edition 10.1 for use with the portal and the Tivoli Data Warehouse. Table 14. Supported databases for the portal operating system database ("TEPS") 1, 2 IBM DB2 for Linux, UNI, and Windows MS SQL Server AI v V9.7 and fix packs v V9.8 and fix packs v V10.1 and fix packs Linux v V9.7 and fix packs v V9.8 and fix packs v V10.1 and fix packs Windows v V9.7 and fix packs v MS SQL Server 2008 v V9.8 and fix packs v MS SQL Server 2008 R2 v V10.1 and fix packs v MS SQL Server 2012 82 IBM Tivoli Monitoring: Installation and Setup Guide

Table 14. Supported databases for the portal (continued) operating system database ("TEPS") 1, 2 IBM DB2 for Linux, UNI, and Windows MS SQL Server 1. "TEPS" is the default database name for the database used by the portal. 2. Your portal database must be located on the computer where the portal is installed. 3. On Linux, the portal database must be installed with the operating system language set to UTF-8. 4. If you transition from one supported database system to another for the Tivoli Enterprise Server, your existing portal data is not copied from the first system to the new one. 5. The Tivoli Enterprise Server automatically prunes closed events out of the database after 24 hours, to prevent long-term database growth. Supported databases for Tivoli Data Warehouse The following tables show the supported databases for the Tivoli Data Warehouse. Table 15 shows the supported databases for the Tivoli Data Warehouse. If you run the database for the Tivoli Enterprise Server and the database for the warehouse in the same instance of IBM DB2 for Linux, UNI, and Windows, you must follow the support requirements in Table 14 on page 82. IBM Tivoli Monitoring V6.3 includes DB2 Enterprise Server Edition 10.1 for use with the portal and the Tivoli Data Warehouse. Table 15. Supported databases for the Tivoli Data Warehouse Tivoli Data Warehouse database ("WAREHOUS") 1 IBM DB2 for Linux, UNI, and Windows IBM DB2 on z/os 5 MS SQL Server Oracle Supported versions: Supported versions: Supported versions: Supported versions: v V9.7 and fix packs version 9.1 or v MS SQL Server v 11g Release 1 v V10.1 and fix packs higher. Support applies to any 2008 Enterprise Edition v 11g Release 2 Windows, Linux, or UNI platform that can run the Warehouse Proxy v MS SQL Server 2008 R2 Enterprise Edition Agent. DB2 Connect Server Edition is also required on the workstation. v MS SQL Server 2012 Enterprise Edition 1. "WAREHOUS" is the default database name for the database used by Tivoli Data Warehouse. Support is for 32-bit or 64-bit databases. Your Tivoli Data Warehouse database can be located on the same computer as your monitoring or on a remote computer. 2. See the Oracle company support Web site (http://www.oracle.com/index.html) for information about installing and configuring Oracle on Solaris V10. 3. DB2 on z/os is not supported for the Tivoli Enterprise Server. Table 16 on page 84 shows the supported databases for the Tivoli Data Warehouse database compression feature. Chapter 3. Hardware and software requirements 83

Table 16. Supported databases for Tivoli Data Warehouse database compression Tivoli Data Warehouse database compression IBM DB2 MS SQL Server Oracle V9.7 or higher, with the IBM DB2 Storage Optimization feature. MS SQL Server 2008 Enterprise Edition or higher. 11g Release 1 or higher, with the Oracle Advanced Compression feature. DB2 on z/os is not supported for this feature. Table 17 shows the supported databases for the Tivoli Data Warehouse database range partitioning feature. Table 17. Supported databases for Tivoli Data Warehouse database range partitioning Tivoli Data Warehouse range partitioning IBM DB2 IBM DB2 on z/os Oracle Enterprise Edition 9.7 or higher. DB2 for z/os 9.1 or higher. 11g Release 1 or higher, with the partitioning option. Required hardware for distributed systems The following sections describe the processor, disk, memory, and other hardware requirements for the IBM Tivoli Monitoring infrastructure components on distributed systems. A distributed system is defined here as any hardware that is not zseries. Following is a list of the IBM Tivoli Monitoring components covered in this section: v Hub monitoring v Remote monitoring v Tivoli Enterprise Monitoring Automation Server v v client v IBM Dashboard Application Services Hub with IBM Infrastructure Management Dashboards for Servers v Tivoli Data Warehouse v Warehouse Proxy Agent v Summarization and Pruning Agent Processor requirements For best performance, processor speeds should be as fast as possible. Choosing faster processors should result in improved response time, greater throughput, and lower CPU utilization. For Windows or Linux on AMD and Intel systems, an x64 processor is recommended. Multiprocessor systems are generally recommended for the IBM Tivoli Infrastructure components. The infrastructure components (monitoring, portal, portal client) run as multithreaded processes and are able to run threads concurrently across multiple processors if they are available. CPU utilization for most components is bursty, and steady-state CPU utilization is expected to be low in most cases. For components supporting large environments, using multiprocessor systems can improve throughput. When the infrastructure components are installed in a virtualized environment (PowerVM, VMWare, and so on), virtual machines with multiple logical processors are recommended, but dedicated processors are 84 IBM Tivoli Monitoring: Installation and Setup Guide

not usually required. Capping the CPU usage of these virtual machines is not generally recommended, so that processing for bursts of activity can utilize spare capacity on the system. When multiple infrastructure components are installed in a single system or virtual machine, additional processors might be needed for best performance. For large environments, consider using four or more processors for the Tivoli Data Warehouse database and the Summarization and Pruning Agent. Although it is not required, the Summarization and Pruning Agent can run on a machine separate from the Tivoli Data Warehouse database. In this case, ensure that a high-speed network connection exists (100 Mbps or faster) between the Summarization and Pruning Agent and the database. Memory and disk requirements The following table shows estimated memory and disk storage for IBM Tivoli Monitoring components on distributed systems. The estimated memory usage for each component does not include the operating system and any concurrently running applications. To estimate the memory requirements for a machine, add the memory requirements for each component that will run on the machine, and add at least 1 GB for the operating system and to allow memory for filesystem caching. Add the sizings for individual components to calculate a total for more than one component installed on the same computer. For example, if the hub monitoring and portal are installed on the same machine, the base component memory requirement is 1600 MB with an additional 220 MB per 1000 managed systems. For an environment with 2000 managed systems, the combined component memory requirement is 1600 +2*220= 2040 MB. The machine should be configured with at least 4 GB RAM (2040 MB + 1 GB for the OS and filesystem caching + extra memory for dynamic requests and some situation evaluation on the hub monitoring ). Table 18. Estimated memory and disk storage for IBM Tivoli Monitoring components on distributed systems Component Memory requirements 1 Disk storage Additional memory requirements 2 Base memory requirement requirements Tivoli Enterprise Monitoring Server 100 MB 120 MB per 1000 managed systems in environment. Extra memory for situations evaluated at monitoring. 7 1.5 GB 35 Extra memory for large dynamic data requests. 8 Remote Tivoli Enterprise Monitoring Server 100 MB 120 MB per 100 managed systems connecting through the. 1.0 GB xlinux 35 1.5 GB All other systems 35 Tivoli Enterprise Monitoring Automation Server Extra memory for situations evaluated at monitoring. 100 MB 70 MB per 1000 managed systems in environment. 100 MB this does not include all of the additional Jazz for Service Management components 9 Chapter 3. Hardware and software requirements 85

Table 18. Estimated memory and disk storage for IBM Tivoli Monitoring components on distributed systems (continued) Component Memory requirements 1 Disk storage Additional memory requirements 2 Base memory requirement requirements Tivoli Enterprise Server 1500 MB 6 100 MB per 1000 managed systems in environment (for AI systems, use 150 MB per 1000 managed systems). 4 Extra 800 MB if the dashboard data provider is enabled. Extra memory for large dynamic data requests. 8 client (browser or desktop) 400 MB Extra 200 MB for large environments. Tivoli Data Warehouse 4 GB depending on database configuration parameters 8-16 GB depending on database configuration parameters 4.0 GB plus an additional 1.2 GB in your computer's temporary directory to install the ewas and the Eclipse Help Server 56 150 MB Warehouse Proxy Agent 200 MB 150 MB Summarization and Pruning Agent 500 MB 150 MB Tivoli Performance Analyzer 200 MB Add 1.5 GB for large environments. Dashboard Application Services Hub (for use with IBM Infrastructure Management Dashboards for Servers) 1000 MB 3.0 GB 9 See Estimating the required size of your database on page 504. Depends on Tivoli Data Warehouse configuration for Tivoli Performance Analyzer attribute groups 86 IBM Tivoli Monitoring: Installation and Setup Guide

Table 18. Estimated memory and disk storage for IBM Tivoli Monitoring components on distributed systems (continued) Component Memory requirements 1 Disk storage Additional memory requirements 2 Base memory requirement requirements 1. The memory and disk sizings shown in this table are the amounts required for the individual component beyond the needs of the operating system and any concurrently running applications. For the total system memory required by small, medium-size, and large environments, see Sizing your Tivoli Monitoring hardware on page 34. 2. The disk storage estimates apply to any size monitoring environment and are considered high estimates. The size of log files affect the amount of storage required. 3. The disk storage requirements for the hub and remote monitoring s do not include storage for the agent depot, which can require an additional 1 GB or more. 4. The memory requirement for the portal does not include database processes for the portal database. DB2 memory usage varies from machine to machine, and can be controlled through various tuning parameters, including bufferpool size. DB2 systems frequently have self-tuning enabled to control the bufferpool size. On systems with a large amount of memory this can result in bufferpools that are much larger than necessary for the TEPS database. A good starting bufferpool size for the TEPS database is 10,000 4K pages (about 40MB). Manual control of the TEPS bufferpool size is recommended to reduce memory usage. You can use the DB2 ALTER command to change the buffer pool size. For example: CONNECT TO TEPS; ALTER BUFFERPOOL IBMDEFAULTBP IMMEDIATE SIZE 10000; CONNECT RESET; 5. Tivoli Monitoring components require additional disk storage when the self-describing agent feature is enabled. The self-describing agent disk storage usage sizes should be multiplied by the number of products in your environment that are expected to perform self-describing agent installations. This estimate is only applicable when the self-describing agent feature is enabled. The disk storage is used by the directory indicated in the Tivoli Enterprise Monitoring Server variable TEMS_MANIFEST_PATH, or the Tivoli Enterprise Server variable TEPS_MANIFEST_PATH. v The hub monitoring requires an estimated 3 to 5 MB of additional disk storage for each product that is performing self-describing agent installations. WebSphere and OMEGAMON agents require more storage, so use the 5 MB per product estimate if you are installing those agents. Otherwise, you can use the 3 MB average size per product. v The remote monitoring requires an estimated 2 MB of additional disk storage for each product that is performing self-describing agent installations. v The portal requires an estimated 3 to 6 MB of additional disk storage for each product that is performing self-describing agent installations since it maintains the new and previous version of an agent product's application support. WebSphere and OMEGAMON agents require more storage, so use the 6 MB per product estimate if you are installing those agents. Otherwise, you can use the 3 MB average size per product. 6. On AI only: IBM Tivoli Monitoring V6.3 will install IBM Installation Manager on the system to install the IBM HTTP Server required by the Tivoli Enterprise Server. If IBM Installation Manager is not already installed on this system, the installation requires 300 MB in the /usr directory. 7. Use the following formula to estimate the additional memory required for a situation evaluated at the monitoring : 2 * number of agents running the situation * number of row instances evaluated per situation interval * row size for attribute group. The row size for an attribute group is available in the agent user's guide. As an example, assume an environment has 3000 Linux agents, each running a situation that uses the COUNT function to calculate the number of disks reported by the Linux_Disk attribute group. Assume also that the agents report on average of 15 rows for Linux_Disk, and the row size for Linux_Disk is 250 bytes. The additional memory required at the monitoring for this situation would be: 2 * 3000 * 15 * 250 = 22,500,000 bytes. 8. Requests to the monitoring for a large amount of data can increase the dynamic memory usage significantly. For example, if a user request results in 10,000 rows of Linux_Disk data (250 bytes each) being returned, the additional memory usage would be: 10,000 * 250 = 2,500,000 bytes. In sizing the memory requirements for the monitoring, consider increasing the memory estimate by 50% to allow room for dynamic memory requests. 9. See the Jazz for Service Management hardware and software requirements at http://pic.dhe.ibm.com/infocenter/tivihelp/ v3r1/topic/com.ibm.psc.doc_1.1.0/install/psc_c_install_prereqs.html. Additional requirements This section contains some additional system requirements. v The best network connection possible is needed between the hub monitoring and portal and also between the Tivoli Data Warehouse, Warehouse Proxy Agent, and Summarization and Pruning Agent. Chapter 3. Hardware and software requirements 87

v A video card supporting 64,000 colors and 1024 x 768 resolution is required for the portal client. Required hardware for System z The Tivoli Enterprise Monitoring Server can be installed on either a z/os or Linux operating system running on System z hardware. The Tivoli Enterprise Server is supported on Linux for zseries, but not z/os. The supported product versions for z/os and Linux for zseries are listed in Table 11 on page 77. The following paragraphs summarize the hardware requirements for IBM Tivoli Monitoring components that run on zseries: v Tivoli Enterprise Monitoring Server on z/os The Tivoli Enterprise Monitoring Server can run natively on any zseries hardware under z/os V1.10 or later. If you enable the self-describing agent feature in your environment, your monitoring s must have access to a HFS or zfs file system through UNI System Services (USS). A recommendation is to allocate 25 to 50 MB for this file system. The amount of storage required for the packages of a self-describing agent depends on the monitoring type: Hub monitoring = 3.25 MB Remote monitoring = 2MB This average number takes into account the following factors: The average amount of storage needed by the monitoring self-describing agent process to backup the existing monitoring product files in the $TEMS_MANIFEST_PATH/SDMBACKUP directory. The hub monitoring self-describing agent process stores all existing self-describing agent package files including a self-describing agent's TEP(S) JAR files, which are the largest JAR files, often in the 1 to 2 MB range. The remote monitoring only has to store a self-describing agent's monitoring JAR files, which are typically around 50K. The amount of USS disk space required is also influenced by the following additional factors: The amount of space fluctuates depending on how many self-describing agents register with the z/os monitoring, and whether multiple self-describing agent installations are in progress. The JAR files are extracted into individual files in subdirectories under the monitoring USS home directory, and those individual files are copied to &rhilev.&rte.rkandatv and then automatically deleted. You must allocate enough space for both the JAR files and the extracted contents of those JAR files. The recommended USS disk space must be sufficient to handle these spikes in disk usage. v Tivoli Enterprise Monitoring Server or Tivoli Enterprise Server on Linux for zseries Any zseries hardware provides adequate processing capability for a monitoring or portal running under Linux for zseries. The Linux operating system must be configured to utilize a 64-bit kernel.the memory and disk requirements for the Tivoli Monitoring components on Linux for zseries are similar to those for Linux running on distributed systems; these are documented in Table 18 on page 85. 88 IBM Tivoli Monitoring: Installation and Setup Guide

Required software The following table lists the software required for IBM Tivoli Monitoring. Table 19. Required software for IBM Tivoli Monitoring Product Distributed systems: IBM Runtime Environment for Java Distributed systems: IBM Runtime Environment for Java Distributed systems: Oracle Java SE Runtime Environment z/os systems: IBM 31-bit or 64-bit SDK for z/os, Java Technology Edition z/os systems: z/os UNI System Services For Linux computers: a Korn shell interpreter AI only: xlc Runtime Environment Database Supported version JRE V1.6 Monitoring Component where the software is required 3 desktop client browser client JRE V1.7 3 3 3 1 JRE V1.6.xx, V1.7.xx IBM Java SDK for z/os at V6 or later ksh package provided by the Linux distribution or pdksh-5.2.14 Component xlc.aix61.rte level 11.1 is required for monitoring and portal. For monitoring agent, level 9 or higher is required. 4 45 1 Monitoring agent 2 A supported RDBMS is required for the Tivoli Enterprise Server and the Tivoli Data Warehouse. Supported database platforms for the portal are listed in Table 14 on page 82. Supported database platforms for the Tivoli Data Warehouse are listed in Table 15 on page 83. Each database requires a driver. For detailed information, see Chapter 19, Tivoli Data Warehouse solutions, on page 503 and subsequent chapters about the Tivoli Data Warehouse. Chapter 3. Hardware and software requirements 89

Table 19. Required software for IBM Tivoli Monitoring (continued) Product Supported version Monitoring Component where the software is required desktop client browser client Monitoring agent 1. 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. 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 is dependent on whether the portal was installed or upgraded. On a pristine install of the portal, IBM JRE 1.7 is the default JRE for portal browser clients. However, if the portal was upgraded, IBM JRE 1.6 remains the default JRE. 2. The Korn shell (any version) is also required when installing the monitoring agent on AI, HP-U, or Solaris systems. 3. IBM JRE 1.7 is installed with the monitoring, portal, and portal desktop client components on distributed systems. IBM JRE 1.6 is also installed on the portal for use by portal browser clients. 4. If the self-describing agent function is enabled, you must install this software on the z/os systems where your monitoring s are installed. 5. A file system (either HFS or zfs) and user security must be configured for UNI System Services on the z/os systems where monitoring s are installed in order to use the self-describing agent function. Supported browser versions The following table shows the supported browser versions for the Tivoli Enterprise browser client and the Infrastructure Management Dashboards for Servers application in the Dashboard Application Services Hub. Table 20. Supported browser versions for the Tivoli Enterprise browser client and the Infrastructure Management Dashboards for Servers application in the Dashboard Application Services Hub Browser version Supported version Tivoli Enterprise browser client Infrastructure Management Dashboards for Servers application Microsoft Internet Explorer V8.0 with all critical Microsoft updates applied Microsoft Internet Explorer V9.0 with all critical Microsoft updates applied Microsoft Internet Explorer V10.0 with all critical Microsoft updates applied Mozilla Firefox Extended Support Release 10 Mozilla Firefox Extended Support Release 17 Required software for event integration with Netcool/OMNIbus This section contains the required software for event integration with Netcool/OMNIbus. The following products must be installed and configured before you install event synchronization and configure event forwarding for Netcool/OMNIbus: v IBM Tivoli Netcool/OMNIbus Probe for Tivoli EIF version 10 or later and the non-native probe version 12 or later v Netcool/OMNIbus 7.2.1 FP10 or later fix pack 90 IBM Tivoli Monitoring: Installation and Setup Guide

v Netcool/OMNIbus 7.3.0 FP5 or later fix pack v Netcool/OMNIbus 7.3.1 or later fix pack v Netcool/OMNIbus 7.4 or later fix pack 1. If you are installing IBM Tivoli Monitoring event synchronization on a Linux operating system, you must ensure that the libp and libtst 32-bit shared libraries are installed on the computer system before installing event synchronization. 2. If you want to configure SSL between the probe and monitoring agents, version 12.0 or later of the Netcool/OMNIbus Probe for Tivoli EIF is required. 3. If you are using the virtualization rules and triggers and predictive rules and triggers provided with Netcool/OMNIbus, you must use Netcool/OMNIbus Version 7.3.0 FP 6 or later, or Netcool/OMNIbus Version 7.3.1 FP2 or later, as those fix packs have the required updates to the rules files and triggers for integration with IBM Tivoli Monitoring. Required software and memory requirements for a dashboard environment If you are installing a dashboard environment with monitoring dashboard applications such as the IBM Infrastructure Management Dashboards for Servers, IBM Infrastructure Management Dashboards for VMware, IBM Infrastructure Management Capacity Planner for VMware, IBM Infrastructure Management Capacity Planner for PowerVM, or creating custom monitoring dashboards, and optionally using the Tivoli Authorization Policy Server, install the following Jazz for Service Management version 1.1 components: v IBM WebSphere Application Server V8.5.0.1 1. If you already have IBM WebSphere Application Server V8.0.0.2 or a later fix pack, or WebSphere Application Server V8.5.0.1 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 (http://pic.dhe.ibm.com/infocenter/tivihelp/v3r1/topic/ com.ibm.psc.doc_1.1.0/install/psc_c_install.html). 2. The dashboard environment must be installed on a Dashboard Application Services Hub that was installed on a WebSphere Application Server Full Profile. A Dashboard Application Services Hub that is installed on a Liberty Profile is not supported by IBM Tivoli Monitoring. See the WebSphere Application Server detailed system requirements at: http://www-01.ibm.com/ support/docview.wss?rs=180&uid=swg27006921. v Jazz for Service Management extension for IBM WebSphere v Dashboard Application Services Hub V3.1 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: v Hardware, operating system, and software requirements for Dashboard Application Services Hub. v 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 of Dashboard Application Services Hub from an IBM Installation Manager local or network repository. IBM Tivoli Monitoring includes the Jazz for Service Management media. Chapter 3. Hardware and software requirements 91

After installing and configuring the Jazz for Service Management prerequisite components that are listed above, you can use the IBM Installation Manager Version 1.6.1 or later or the IBM Tivoli Monitoring installation launchpad to install the following IBM Tivoli Monitoring components into the Dashboard Application Services Hub: v IBM Infrastructure Management Dashboards for Servers application v Tivoli Authorization Policy Server The tivcmd Command Line Interface (CLI) for Authorization Policy component should also be installed on the computer systems that are used by the administrators who create and work with authorization policies. The tivcmd CLI does not require any Jazz for Service Management components to coexist on the same system. You must use IBM Installation Manager version 1.6.1 or later or IBM Tivoli Monitoring installation launchpad to install the tivcmd CLI. See Using IBM Installation Manager to install IBM Tivoli Monitoring components for a dashboard environment on page 296 for more details on the installation options for installing the dashboards for s application, the authorization policy, and the tivcmd CLI. Detailed instructions for installing each of these components are available here: v Installing and configuring the IBM Infrastructure Management Dashboards for Servers on page 304 v Installing and configuring the Tivoli Authorization Policy Server and tivcmd Command-Line Interface for Authorization Policy on page 312 1. A minimum of 200-300 MB of free space is required on the system where you are installing the Tivoli Authorization Policy Server. 2. On Linux systems, you must install the GTK support packages before you use the IBM Tivoli Monitoring installation launchpad or the IBM Installation Manager graphical user interface. The package get utilities for your Linux distribution can be used to install the latest versions of the GTK libraries and the GTK library dependencies. 3. Both the Jazz for Service Management components and the IBM Tivoli Monitoring components for a dashboard environment must be installed in the same user mode; install both as a root user or install both as a non-root user. Information cannot be exchanged between these components when there is a combination of root and non-root installations. In addition to installing the Jazz for Service Management components and IBM Tivoli Monitoring components, you must also perform the following configuration tasks: 1. You should also install an LDAP and configure the WebSphere Application Server for Dashboard Application Services Hub and your Tivoli Enterprise Server to use a federated user repository and single sign-on. An LDAP and single sign-on are not required if all dashboard operators can use the same permissions for display monitoring resources in Dashboard Application Services Hub and you do not need single sign-on support for launching to the Tivoli Enterprise. 2. Enable the dashboard data provider when you configure the Tivoli Enterprise Server. From Dashboard Application Services Hub, configure a connection to the dashboard data provider. 3. If you are using the Authorization Policy Server, you must also enable authorization policies during portal configuration. However, the recommended approach is to set up your dashboard environment with authorization policies disabled. After you have a dashboard user who can view monitoring data by using the IBM Infrastructure Management Dashboards for Servers application, or custom dashboards, and your administrators have created authorization policies for your dashboard operators, then reconfigure the portal to enable authorization policies. 92 IBM Tivoli Monitoring: Installation and Setup Guide

For more information about the configuration tasks to perform after the installation tasks are complete, see the IBM Tivoli Monitoring Administrator's Guide section on Preparing your dashboard environment. See also Supported browser versions on page 90 for the list of browsers that are supported by IBM Infrastructure Management Dashboard for Servers. If you have IBM SmartCloud Monitoring version 7.2 or later or IBM Tivoli Monitoring for Virtual Environments version 7.2 or later, you can install their dashboard monitoring applications (IBM Infrastructure Management Dashboards for VMware, IBM Infrastructure Management Capacity Planner for VMware, IBM Infrastructure Management Capacity Planner for PowerVM) into Dashboard Application Services Hub. You can also install any other monitoring dashboard applications that use the IBM Tivoli Monitoring V6.3 or later dashboard data provider. Required software and memory requirements for a reporting environment that uses Tivoli Common Reporting If you are planning to use Tivoli Common Reporting and report packages that are provided with monitoring agents or custom reports for monitoring agents, first install and configure the Tivoli Data Warehouse. For more information, see Chapter 19, Tivoli Data Warehouse solutions, on page 503. You can install the reports for IBM Tivoli Monitoring Version 6.3 operating system agents with Tivoli Common Reporting 3.1 or 2.1.1. IBM Tivoli Monitoring V6.3 includes Tivoli Common Reporting 3.1, so you must use version 3.1 when to set up a new reporting environment. Tivoli Common Reporting 3.1 is a Jazz for Service Management component. To use this version of Tivoli Common Reporting, install and configure the following Jazz for Service Management components if they are not already in your environment: v IBM WebSphere Application Server V8.5.0.1 If you already have IBM WebSphere Application Server V8.0.0.2 or a later fix pack or WebSphere Application Server V8.5.0.1 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 the Jazz for Service Management Installation Guide for more details on installing into an existing WebSphere Application Server. v Jazz for Service Management extension for IBM WebSphere v Dashboard Application Services Hub V3.1 v Tivoli Common Reporting V3.1 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: v System requirements for Dashboard Application Services Hub and Tivoli Common Reporting. v 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. Jazz for Service Management also supports installation of Dashboard Application Services Hub from an IBM Installation Manager local or network repository. You must use the Tivoli Common Reporting installation program to install Tivoli Common Reporting. After installing and configuring Tivoli Common Reporting and its prerequisites, go to Chapter 28, Using Tivoli Common Reporting and monitoring agent reports, on page 685 for more information. Chapter 3. Hardware and software requirements 93

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, you must install the following Jazz for Service Management version 1.1 prerequisite components if they are not already in your environment: v IBM WebSphere Application Server V8.5.0.1 If you already have IBM WebSphere Application Server V8.0.0.2 or a later fix pack or WebSphere Application Server V8.5.0.1 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 the Jazz for Service Management Installation Guide for more details on installing into an existing WebSphere Application Server. v Jazz for Service Management extension for IBM WebSphere v DB2 database for the Registry Services database if you do not already have a database in your environment v Registry Services V1.1 v Security Services V1.1 (optional) 1. IBM Tivoli Monitoring includes the Jazz for Service Management version 1.1 media. 2. 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 on page 141 for more details on using Security Services and single sign-on with the Performance Monitoring service provider. 3. Registry Services and Security Services must be installed into the same WebSphere Application Server. 4. Registry Services support two types of authentication: a. Basic authentication which requires users and client applications to provide a user ID and password to Registry Services. b. 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: v System requirements for Registry Services and Security Services. v 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 94 IBM Tivoli Monitoring: Installation and Setup Guide

connection information for Registry Services. For more information, see Installing and configuring Tivoli Enterprise Monitoring Automation Server on page 218. Required software and memory requirements for non-linear trending in Tivoli Performance Analyzer This section contains the software and memory requirements for non-linear trending in Tivoli Performance Analyzer. The following are prerequisite criteria for using the non-linear trending feature in Performance Analyzer: v You must install SPSS Forecast Server V20. v A minimum of 100 MB of free space is required in the ITPA agent home directory for the output data files generated by SPSS. Chapter 3. Hardware and software requirements 95