Rational Reporting for Development Intelligence 2.0 Release Candidate 2 Milestone

The following notes detail issues in the Rational Rational Reporting for Development Intelligence 2.0 RC2 milestone that users and consumers of Rational Team Concert, Rational Quality Manager and Rational Requirements Composer should be aware of.

OS Platform Support

For this milestone, RRDI is supported on the Windows, AIX, SuSE/z, and Linux/x86 32- and 64-bit systems. They include Windows 2003, 2008, 2008 R2, AIX 6.1, 7.1, and SuSE 10 and 11 (for x86 and system Z architecture) and RedHat 5.7 and 6 (for x86 architecture).

Special Consideration for Windows 2008 and 2008 R2 Systems

On the Windows 2008 and 2008 R2 systems, the (one-time) Setup server configuration command, [RRDI-install-location]\setup\tool\JazzTeamServer\server\server.config.bat, should be run as an Administrator (e.g. running from the Command Prompt windows which was opened by "Run as Administrator" command).

Special Consideration for RedHat 6 Systems

The user account for running the setup and application server should include the environment setting of LD_PRELOAD with the value of /usr/lib64/libfreebl3.so for the RedHat 6 64-bit system, and /usr/lib/libfreebl3.so for the RedHat 6 32-bit system.

Database Management System Support

RRDI supports the use of the DB2, SQL Server, and Oracle. A user account for running the setup would need to have the privileges to connect to the database and complete the configuration of the database. For example, the user account on Linux for running the setup of a DB2 database and application server should have the environment setting from the a DB2 profile (the script can be found in the [DB2-instance-user-home-directory]/sqllib/db2profile).

Special Considerations for Content Store Configuration

The database must have the correct code page. (DB2: codeset = 'UTF-8'; Oracle: NLS_CHARACTERSET = 'AL32UTF8'; SQL Server: Collation contains '_CI_').

For using a DB2 database as the content store:

• It must have the correct values for Timeout and Application heap size. (locktimeout >= 240 and applheapsz = 1024).
• It must have two buffer pools created in the database: one buffer pool with page size of 4k (4096) and the other buffer pool with page size 32k (32768).
• It must have three table spaces created in the database: a 4k (4096) regular (DATATYPE='A') table space, a 32k (32768) system temporary (DATATYPE='T') table space, and a 4k (4096) user temporary (DATATYPE='U') table space.

Application Server Support

RRDI requires the installation of a WebSphere Application Server (WAS) base edition version 7 (Fixpack 15 or above) or 8 as a prerequisite. The architecture of the RRDI installation (32-bit or 64-bit) must match the one for the WAS installation.

RRDI Setup server configuration scripts have changed

While the user runs the server.config.bat (for Windows) or server.config-*.sh (for AIX and Linux), besides the Full DNS name for the host system, the user would also specify a new administrator username (and associated password) for registering the Setup server (this provides more security on the Setup server than the hard-coded username/password provided in the previous milestones).

RRDI Setup scenarios have changed

The user can just go through the Set up Rational Reporting scenario for the necessary configuration steps for report server configuration and Jazz user authentication for logging onto the report server. The Jazz user authentication enabling through the Run Postsetup Tasks scenario may not work properly for the RC2 milestone due to the RRDI issue 193540.

Special Consideration for live data reporting on AIX and Linux for x86

The user would need to install and build unixODBC driver packages on the AIX and Linux systems for live data reporting. The unixODBC package would need to be built in the 64-bit mode (with CFLAGS=-m64 environment setting) for AIX, and in the 32-bit mode (with CFLAGS=-m32 environment setting).

RRDI 193540 Failed to enable JazzNS in post setup tasks

The Rational Reporting User Authentication (also known as Jazz User Authentication or Jazz Namespace) configuration step does not work properly in the Run Postsetup Taks scenario. The user should perform this configuration while going through the steps in the (main) Set Up Rational Reporting scenario.