Rational Reporting for Development Intelligence 2.0 Release Candidate 4 Milestone
Rational Reporting for Development Intelligence 2.0.5 is required for use with CLM v4.0.5x.
Rational Reporting for Development Intelligence 2.0.6 is required for use with CLM v4.0.6x.
Rational Reporting for Development Intelligence 5.0.2 is required for use with CLM v5.0x.
The following notes detail issues in the Rational Rational Reporting for Development Intelligence 2.0 RC4 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. For DB2, RRDI supports the Express Server Edition, but it does not support the Express-C Edition. The DB2 for z/OS support will be added in a later milestone.
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
While the user runs the server.config.bat (for Windows) or server.config-*.sh (for AIX and Linux), please provide the Full DNS name for the host system, and the username (and associated password) of a new administrator for the Setup server. The administrator user credential would be used for registering and logon for the Setup server.
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 190695 Small open file limit on Linux system may cause RRDI report server or setup server fail to start
Check the open file limit on Linux by running the 'ulimit -n' command. If its value is 1024 or less, the RRDI report server or setup server may not be able to start properly. The user would want to increase this limit by running 'ulimit -n
RRDI 194162 Unable to run the Cognos configuration script during setup with fully-qualified service name for Oracle content store
While configuring an Oracle database as the content store for the report server, the user should provide the SID of the database for the service name for the configuration. Otherwise, the Build and Deploy step may fail to run the Cognos configuration script.
RRDI 190687 Cognos configuration utility unable to run content store test connection if ojdbc6.jar is used
When an Oracle database serves as the content store, Cognos Configuration tool (cogconfig.bat for Windows and cogconfig.sh for Linux and AIX) is unable to use ojdbc6.jar file for performing content store connection test, and would use ojdbc5.jar file by default instead. To resolve the issue on the system where ojdbc5.jar file is not present, the user would create a symbolic link from ojdbc5.jar to ojdbc6.jar if a symbolic link mechanism is available on the OS (e.g. Linux and AIX), or rename the ojdbc6.jar to ojdbc5.jar elsewhere.