The system requirements are broken down into various components including the server-based CLM applications that are deployed on one or more servers and various optional tools and clients. Server Requirements are further broken down into Non-Clustered and Clustered support where applicable. Please Note as announced with CLM v4.0.6: IBM will be simplifying the approach to high availability for the Rational CLM platform. Customers and IBM are increasingly using other technologies, such as cloud and virtualization strategies, that provide a solution which adapts to business demands for both availability and scale in a cost-effective manner. Please see Approaches to implementing high availability and disaster recovery for Rational Jazz environments for guidance and best practice. IBM will be removing support for WebSphere Application Server based application clustering from the CLM platform. For further details, please contact Support or your Technical Sales representative.

The RRC Converter application will not run on AIX, IBM i, Linux for Power, Solaris or z/OS systems. The server-side converter.war, needed to view graphical artifacts, must be deployed on a supported Windows, x86 Linux or zLinux platform. If your RRC installation is on a platform not currently supported by the converter application, this document describes the delegated converter configuration option: RM Converter Application Configuration and Troubleshooting Guide.

Rational Team Concert promotion and deployment support for z/OS require the REXX runtime or REXX alternate libraries (REXX.**.SEAGLPA, or REXX.**.SEAGALT). If you do not have either the REXX Library or the REXX Alternate Library installed, you can install the REXX Alternate Library to fulfill the REXX Library requirement. The REXX Alternate Library is shipped as part of the z/OS operating system beginning with release 1.9. The Alternate Library is also available as a free download from http://www.ibm.com/support/entry/portal/.

Reminder - RRDI may be installed on a separate server (platform). Additional RRDI platforms are included in the list above.

"and future OS fixpacks" includes Service Releases (SR's) and Updates (RHEL). Fix pack is IBM terminology for a minor release that includes fixes (vs. features).

Please check that the system requirements or release notes of the respective hypervisor (edition and version) supports the host operating system (edition and version) you plan to use for deploying the CLM application(s).

A2.2 Server Virtualization Clustered Support

Supported host operating systems may be virtualized for application clustering using only the following hypervisor with operating system options:

A3. Memory Requirements

CLM Server Memory Requirements

For CLM 4.0 and later you need a 64-bit operating system and a minimum of 4 GB of server memory allocated to the Java virtual machine running the Jazz Team Server and all three applications (Change and Configuration Management, Quality Management, Requirements Management) on one server for small deployments. Larger deployments or loads may require significantly more memory.

The Java virtual machine max heap memory setting is configured to -Xmx4000M for 64-bit platforms and -Xmx1200M for 32-bit platforms (for small-scale evaluation or demonstration purposes only). Note that the Java virtual machine heap size should only represent a fraction of the physical memory (RAM) of the server.

For 64-bit deployments where less memory is available, it is possible - although strongly discouraged - to configure the Java virtual machine memory size to a lower setting (e.g. -Xmx1200M to match the 32-bit setup) - be aware that it may results in memory outages and/or performance degradation. For the Tomcat installation, the server.startup script file to edit is located under JazzInstallDir/server/, and controlled by the line: set JAVA_OPTS=%JAVA_OPTS% -Xmx4000M. For a WebSphere Application Server installation, please consult the WebSphere Administrative Console, and modify Servers>Application Servers>server1>Java and Process Management>Process Definition>Java Virtual Machine>Maximum Heap Size.

Memory requirements can be reduced by running a subset of applications such as just CCM to support RTC-only functionality. Additionally if applications and/or the Jazz Team Server are running on different machines, memory requirements for specific machines may be reduced.

RRDI Server Memory Requirements

8 GB RAM. More memory generally improves performance; required memory depends on the number of concurrent users, amount of data being requested, and the size of the database. Optimum swap space is double the physical memory.

A4. Network Infrastructure

IPv6

IPv4

A5. Application Servers

A5.1 Application Server Non-Clustered Support

The following application servers can be used to host CLM applications (non-clustered):

Application Server Notes

Bundling: WAS and DB2 bundles are only available on Passport Advantage and in the CLM Media (not on Jazz.net). Customers upgrading from CLM 3.0.1 and 4.0 are entitled to continue using WAS 7.0.x and WAS 8.0.x as long as CLM supports those versions.

WebSphere Application Server support for CLM and RRDI is 64-bit only to align with 64-bit server platforms.

Clustering is supported with WAS ND (v7.0.0.29 or v8.0.0.6) but also requires the bundled WXS v7.1.1.1. WAS 8.5 and 8.5.5 are not supported for clustering.

There is a known issue with BIRT reports running WAS v8.0.0.x and v8.5.x please see this Tech Note for WAS patch. This issue applies only to WAS 8.x and 8.5.5.x. It is fixed in WAS 8.5.5

A6.2 High Availability Database Support

When clustering we also suggest setting up High Availability support with these databases:

DB2 9.7 HADRDB2 HADR is included with Enterprise Server Edition but requires additional DB2 licenses for anything other than cold standby. See note below.

DB2 10.1 HADRNew for CLM v4.0.3DB2 HADR is included with Enterprise Server Edition but requires additional DB2 licenses for anything other than cold standby. See note below.

DB2 9 for z/OS 9.1

DB2 10 for z/OS 10.1(with PTF UK77844)

Oracle Real Application Clustering (Oracle 11g Release 2)

Database Support Notes

Database support is 64-bit only to align with 64-bit server platforms. For RRDI the 32-bit database client library is required (even though the database server is 64-bit).

WAS and DB2 bundles are only available on Passport Advantage and in the CLM Media (not on Jazz.net). Customers upgrading from CLM 3.0.1 and 4.0.X are entitled to continue using DB2 9.7 as long as CLM supports that version.

The DB2 HADR functionality is included and can be used with the Limited Use Workgroup and Enterprise Server Editions. However, there must be entitlement coverage for the secondary/standby server. There is a 1:1 entitlement ratio for DB2 with the entitlement purchased by the customer of the bundling product. For eg. 500 PVUs of Portal entitles customer to use a maximum of 500 PVUs of DB2 in support of Portal. The entitlement requirement for the standby server depends on the standby configuration used, and is defined in the DB2 license. ie. Hot standby requires equivalent entitlement as the Primary. Warm standby requires 100 PVUs/25 AUs, regardless of Primary. Cold standby server is free. Definition of hot/warm/cold standby configurations is also in the DB2 license.

A13. Report Customization

A14. Load Balancer for Clustering

IBM HTTP Server 8.0

IBM HTTP Server 7.0 Fixpack 23

Websphere Application Server Network Deployment v8.0.0.3

WebSphere Application Server Network Deployment v7.0 Fixpack 23

B. Client Requirements

Reminder: The platforms listed below are the starting point for CLM support and unless otherwise indicated support includes this level and all future OS fixpacks. For RedHat Updates are equivalent to fix packs

Client Operating System Notes

If you are running the Eclipse client on Linux please ensure that you have a compatible xulrunner or webkitgtk installed and configured on your system. Failure to do so can result in various issues including failure to start. See Article for additional details and instructions.

Smart Card Support for ALL CLM Products (Windows Only)

MAC OSX is supported for RTC, RQM and RRC Only (not DNG or RRDI)

SLED 10 is no longer supported for RRDI, and for the RTC Eclipse Client using IES 4.2.2. This platform is out of support from SUSE.

Browser Support Notes

The RRC and DOORS NG Graphical Editor is supported in 32-bit mode using Internet Explorer and Firefox on Windows (Only). Chrome and Safari browsers will show graphical artifacts in preview mode, but will not support editing.

Macromedia Flash Player 10,11* and future releases, mods and fixpacks is supported for graphical view in Work Item Statistics dashboard viewlet

B3. RTC Clients Memory and Hardware Requirements

For both the Eclipse and VS.Net clients and for each instance of an RTC clients these are the minimum requirements:

C. Additional RTC Clients and Optional Tools

C1.RTC Clients N-1 Compatibility

For upgrades, after upgrading the Server, teams may choose to gradually upgrade the clients. CLM supports N-1 (keeping the clients one release behind) to allow for this more gradual update of workstations.

This applies to all the RTC clients including the Eclipse, VS.Net SCM CLI, Windows Shell and ISPF Clients. For clarity we also include the table below:

Server

Compatible Clients

CLM 4.0.x Server

RTC Eclipse Client v4.0.y, (x>=y)RTC Eclipse Client v3.0.y or Later

RTC VS.Net Client v.4.0.y, x>=y VS.Net Client v.3.0.y or later

RTC SCM CLI v.4.0.y, x>=y RTC SCM CLI v.3.0.y or later

RTC ISPF Client v.4.0.y, x>=y RTC ISPF Client v.3.0.y or later

RTC Windows Shell Client v.4.0.y, x >=y (this was introduced in 4.0)

RTC MSSCCI Provider v.4.0.y, x >=y (this was introduced in 4.0)

C2. RTC Build System Toolkit

The Build System Toolkit is a 32 bit client that can be run on the RTC Server and the Client Operating Systems. Please see the downloads page for the specific executable on your platform. For the RTC Eclipse client platforms there is an Installation Manager install. For z/OS there is a SMP/E install. For IBM i there is a LICPGM install. For all other platforms there are Plain Zips.

The Build System Toolkit is supported using the the versions of Java that RTC supports on the selected install platform. When installed on z/OS, the Build System Toolkit is also supported using Java 7.

C3. RTC SCM Command-Line Tool

The SCM Command-Line Tool is supported on all Server Platforms except for IBM i.

C4. RTC ISPF Client and ISPF Gateway

The Rational Team Concert ISPF Client is supported on all zOS platforms as specified under Server Operating Systems.

Prior to RTC 4.0.5, the Rational Team Concert ISPF client required cURL, an open source tool supplied through IBM Ported Tools Supplementary Toolkit for z/OS. Information on IBM Ported Tools can be found at: IBM Ported Tools for z/OS Product and Feature Information. If you already have IBM Ported Tools installed, cURL for z/OS is available by ordering the PTF for APAR OA2. Release 4.0.5 and later do not have this dependency.

For 4.0.5 the ISPF client supports the same Java versions as the CLM Server on z/OS. For 4.0.6, the ISPF client supports those plus Java 7 on z/OS.

Rational Team Concert uses the ISPF Gateway component of ISPF for access to z/OS files. For the ISPF Gateway component to function correctly, you must install a number of PTFs for the listed APARs. If you do not install the appropriate PTF, you might encounter problems with ISPF Gateway usage. For the supported ISPF releases, the PTFs are as follows:

for APAR OA35689:

z/OS 1.9: UA63763

z/OS 1.10: UA59950

z/OS 1.11: UA59951

z/OS 1.12: UA59951

z/OS 1.13: - code is at appropriate level

for APAR OA38740:

z/OS 1.10: UA65381

z/OS 1.11: UA65382

z/OS 1.12: UA65382

z/OS 1.13: UA65383

for APAR OA39666:

z/OS 1.11: UA65909

z/OS 1.12: UA65909

z/OS 1.13: UA65910

C5. Rational Team Concert (RTC) Shell Client (introduced in v4.0)

The RTC Shell is distributed as a downloadable file through IBM® Installation Manager.

C7.4 CQ Synchronizer Gateway Java Runtime Environment

D. CLM Integrations, Migrations and Adapters

D1. CLM Products Integrating With One Another

For 4.0.x versions all CLM products must be at the same 4.0.x level. If one product is upgraded to a new 4.0.x then all products must be upgraded whether they share a JTS or not.

The 4.0.x products can be integrated with products in the 3.0.x release as shown in the following table. Note that this excludes DNG which only integrates with other 4.0.x products at the same version level as DNG.

CLM v3.0.1.6 iFix2 includes fixes for high priority security issues so that version is recommended but not required.

Change and Synergy are closely linked and share the same repository. Change integrates with RTC, RQM, RRC. For RTC that integration is made via Rational Synchronization Server. For the RQM and RRC integrations Change uses OSLC.Note: DNG's rich client support is limited to viewing and navigating OSLC links. Use the web client for creating and deleting OSLC links