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 Portal 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 2.

The following paragraphs summarize the hardware requirements for IBM Tivoli Monitoring components that run on zSeries:

• 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 servers must have access to a HFS or zFS file system through UNIX 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 server type:

  • Hub monitoring server = 3.25 MB
  • Remote monitoring server = 2 MB

  This average number takes into account the following factors:

  • The average amount of storage needed by the monitoring server self-describing agent process to backup the existing monitoring server product files in the $TEMS_MANIFEST_PATH/SDMBACKUP directory.
  • The hub monitoring server 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 server only has to store a self-describing agent's monitoring server 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 server, and whether multiple self-describing agent installations are in progress.
  • The JAR files are extracted into individual files in subdirectories under the monitoring server 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.
• Tivoli Enterprise Monitoring Server or Tivoli Enterprise Portal Server on Linux for zSeries

  Any zSeries hardware provides adequate processing capability for a monitoring server or portal server 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 1.