Rational Team Concert 4.x sizing report for z/OS

This article provides the Rational Team Concert 4.x sizing report specifically for z/OS. We are adopting the Rational Team Concert test harness to simulate actual client workload and validate our scalability requirements. Read the Collaborative Lifecycle Management 2012 Sizing Report first for more information about the Rational Team Concert test harness.

Since version 4.0 was released, we have focused on performance testing using standard topologies. For more information related to the system requirements, see System Requirements for Collaborative Lifecycle Management 2012.

This sizing report is specifically for:

  1. Single-Tier Mode: Linux for System z standalone topology, which deploys the application server on Linux for System z and DB2 on Linux for System z.
  2. Dual-Tier Mode: standard topology – E5, which deploys the application server on Linux for System z and DB2 on z/OS

Small-scale enterprise deployment

For this sizing report, a small-scale deployment is a configuration of between 100 and 700 users on either a single-tier or a double-tier setup. For a single-tier setup, the application server and database are running on the same LPAR. For dual-tier setup, the application server and database are running on different LPARs.

The following table lists the system configurations we used for a small-scale single-tier setup scenario:

Application server and database – Linux for System z (single-tier configuration)
DiskDS8000 with PAV enabled
Operating System SUSE Linux Enterprise Server 10 (S390x)
Application serverWebSphere Application Server Network Deployment v8.0.0.3
DatabaseDB2 9.7.0.5

The following table lists the system configurations we recommend for a small-scale single-tier setup scenario:

Application server and database – Linux for System z (single-tier recommendation)
CPU1000 mips or higher
Memory6GB or higher
The following tables list the system configurations we used for a small-scale dual-tier setup scenario:
Application server – Linux for System z (dual-tier configuration)
DiskDS8000 with PAV enabled
Operating System SUSE Linux Enterprise Server 10 (S390x)
Application serverWebSphere Application Server Network Deployment v8.0.0.3
Database – IBM System z10 (dual-tier configuration)
DiskDS8000 with PAV enabled
Operating System z/OS 1.12
DatabaseDB2 on z/OS v9.1
The following tables list the system configurations we recommend for a small-scale dual-tier setup scenario:
Application server – Linux for System z (dual-tier recommendation)
CPU800 mips or higher
Memory6GB or higher
Database (dual-tier recommendation)
CPU100 mips or higher
Memory6G or higher

Large-scale enterprise deployment

For this sizing report, a large-scale deployment is a configuration of between 700 and 2000 users on either a single-tier or a double-tier setup. For a single-tier setup, the application server and database are running on the same LPAR. For dual-tier setup, the application server and database are running on different LPARs.

The following table lists the system configurations we used for a large-scale single-tier setup scenario:

Application server and database – Linux for System z (single-tier configuration)
DiskDS8000 with PAV enabled
Operating System SUSE Linux Enterprise Server 10 (S390x)
Application serverWebSphere Application Server Network Deployment v8.0.0.3
DatabaseDB2 9.7.0.5

The following table lists the system configurations we recommend for a large-scale single-tier setup scenario:

Application server and database – Linux for System z (single-tier recommendation)
CPU2000 mips or higher
Memory10 GB or higher
The following tables list the system configurations we used for a large-scale dual-tier setup scenario:
Application server – Linux for System z (dual-tier configuration)
DiskDS8000 with PAV enabled
Operating System SUSE Linux Enterprise Server 10 (S390x)
Application serverWebSphere Application Server Network Deployment v8.0.0.3
Database – IBM System z10 (dual-tier configuration)
DiskDS8000 with PAV enabled
Operating System z/OS 1.12
DatabaseDB2 on z/OS v9.1
The following tables list the system configurations we recommend for a large-scale dual-tier setup scenario:
Application server – Linux for System z (dual-tier recommendation)
CPU1600 mips or higher
Memory10GB or higher
Database (dual-tier recommendation)
CPU200 mips or higher
Memory6GB or higher

Rational Build Agent

The Rational Build Agent is required for System z builds. For additional information, see Working with Enterprise Extensions builds.

The following table lists the system configurations we used for the Rational Build Agent:

IBM System z/OS
DiskDS8000 with PAV enabled
Operating System z/OS 1.12

The following table lists the system configurations we recommend for the Rational Build Agent:

IBM System z/OS
CPU100 mips or higher
Memory2GB or higher