IBM Rational Portfolio Manager 7.1.1.2 Interim Fix 002 Readme for UNIX

Contents

• Description
• Problems Solved
• Known Problems
• Platforms NOT supported in Rational Portfolio Manager, version 7.1.1.2 interim fix 002
• Prerequisites for installing Rational Portfolio Manager, version 7.1.1.2 interim fix 002
• Installing Rational Portfolio Manager, version 7.1.1.2 interim fix 002 for UNIX
• Contacting IBM Rational Software Support
• Notices and trademarks

Description

This is the second interim fix for Rational Portfolio Manager. This interim fix contains defect fixes to Rational Portfolio Manager 7.1.1.2.

To install this interim fix, in addition to the installation instructions contained in this Readme file, you also need to refer to the Rational Portfolio Manager 7.1.1.2 Installation and Upgrade Guide. This guide is available at http://www.elink.ibmlink.ibm.com/publications/servlet/pbi.wss?CTY=US&FNC=SRX&PBL=SC23-6196-02

You can also find the Rational Portfolio Manager 7.1.1.2 Installation and Upgrade information in the Rational Portfolio Manager 7.1.1.2 Information Center. The Information Center is available at http://publib.boulder.ibm.com/infocenter/ratportm/v7r1m1/index.jsp.

Problems Solved

Known Problems

Platforms NOT supported in Rational Portfolio Manager, version 7.1.1.2 interim fix 002

1. DB2 8.2 on Red Hat Enterprise Linux 4 - 32bit
2. Oracle 10g leveling library not available for Red Hat Enterprise Linux 4 - 32bit

Prerequisites for installing Rational Portfolio Manager, version 7.1.1.2 interim fix 002

Before you begin

1. Back up your existing database before applying the interim fix, to ensure a full recovery in case of crashes or failures.
2. Ensure you have a copy of the Rational Portfolio Manager 7.1.1.2 Installation and Upgrade Guide for reference during the installation.
3. Ensure you have the following database connection information for updating the database component:

   For DB2 database

   • Database name
   • Instance owner
   • Instance owner password
   • Connected user and password, if applicable

   For Oracle database

   • ORACLE_HOME
   • ORACLE_SID or TNS string
   • Rational Portfolio Manager schema owner
   • Rational Portfolio Manager schema owner password

Installing Rational Portfolio Manager, version 7.1.1.2 interim fix 002 for UNIX

1. Downloading the interim fix package

1. Download the interim fix package from here to a directory on your server.
2. Extract the interim fix package using the command:

   gunzip <IFix-package-name>.tar.gz

3. Untar the interim fix package by using the command:

   tar -xvf <IFix-package-name>.tar

   Note: In this Readme, the path where you extract the package, for example, /home/db2inst1/rpm/7.1.1.2-RATIONAL-RPM-Aix-iFix-002 is referred to as ${IFIX_PACKAGE}.
4. Stop the Rational Portfolio Manager Web application and the associated alert server.

2a. For DB2 users: Updating the database component

1. Open a terminal shell.
2. In the shell, navigate to the appropriate code subdirectory based on the appropriate target platform as shown in the following table:

   Table 3. List of target platforms

   Target platform	Navigate to Directory
   Aix 32bit	${IFIX_PACKAGE}/Database/csp_Aix32
   Aix 64bit	${IFIX_PACKAGE}/Database/csp_Aix64
   Redhat 3 32bit	${IFIX_PACKAGE}/Database/csp_Linux3_32
   Redhat 4 32bit	${IFIX_PACKAGE}/Database/csp_Linux4_32
   Redhat 4 64bit	${IFIX_PACKAGE}/Database/csp_Linux4_64
   SunOS 32bit	${IFIX_PACKAGE}/Database/csp_SunOS32

3. From the shell window, restart DB2 by running the following commands in sequence:

   db2 force applications all
   db2stop force
   db2start

4. From the shell window, update the DB2 package:
   1. Connect to the database (substitute the actual values for database name, instance owner, and instance owner password):

      db2 connect to <database_name> user <instance_owner> using <instance_owner_pwd>

   2. Retrieve the Rational Portfolio Manager shared object (SO) library file name stored in DB2, by running the following query:

      db2 "select procname, implementation from syscat.procedures where procname = 'SP_GET_VERSION'"

      The following table shows a sample result of a query, where the returned library file is 'myrpm'.

      PROCNAME	IMPLEMENTATION
      SP_GET_VERSION	/home/db2inst1/sqllib/function/myrpm!SP_GET_VERSION

      If the above query returns a library file name other than ibmrpm.so, rename the ibmrpm.so file found in the directory path in Step 2 to the name returned in the query. For example as per the above sample query, the returned library name is 'myrpm' and you need to rename ibmrpm.so to myrpm.so.

      To rename ibmrpm.so to myrpm.so, use the command mv ibmrpm.so myrpm.so.

5. Run the following command:

   ./bindall <database_name> <instance_owner> <instance_owner_pwd> <<connected_user>> <<connected_user_pwd>>

   Note: Parameters <<connected_user>> and <<connected_user_pwd>> are required only if the Rational Portfolio Manager database was setup using scenario #2 - connected user. For more information on scenario #2, refer to Rational Portfolio Manager 7.1.1.2 Installation and Upgrade guide.
6. Verify that the bindall script copied the .so file identified in Step 4b into $DB2DIR/function directory. If not, copy the file manually.
7. In the shell window, change the path to ${IFIX_PACKAGE}/Database/updateSQL
8. If Interim fix 001 (iFix001) was previously applied to the Rational Portfolio Manager database, perform this step; otherwise proceed to the next step.
   1. Open the updateTMT_SETTINGS.sql file with a text editor.
   2. In the updateTMT_SETTINGS.sql file, SECTION : iFix001, delete the following lines:

      update TMT_SETTINGS set description = '7.1.1.2 iFix001' where element_id = 'APPLICATION_VERSION';
      INSERT INTO TMT_SETTINGS(LEVEL_ID,TYPE_ID,MAX_RANK,CHILD_COUNT,DELETED_COUNT,ELEMENT_ID,ELEMENT_NAME,PARENT_ID,REC_USER,REC_STATUS,REC_DATETIME,RANK,SETTING_VALUE,DESCRIPTION)
      VALUES(0,1,0,0,0,'ATTRIBUTE_CUST_FIELDS_FEATURE___',null,null,'PMO_SUPERVISOR','I','2008-06-20 11:27:00.000000','00000026',3,'Enable/Disable Attr and CustFlds feature flag for IGS. the first bit controls Attributes (0: disable, 1: enable), the second bit controls Custom Fields(0: disable, 1: enable)');

   3. Save the file.
9. To update the server information, in the shell window, perform the following steps:
   1. Connect to the database (substitute the actual values for database name, instance owner, and instance owner password):

      db2 connect to <database_name> user <instance_owner> using <instance_owner_pwd>

   2. Run the command:

      db2 -tvf updateTMT_SETTINGS.sql -z updateTMT_SETTINGS.log

   3. Check updateTMT_SETTINGS.log for any errors.
      • If there are no errors, continue to the next step.
      • If you encounter errors, contact IBM Rational Software Support.
10. To verify if the application of the interim fix was successful, in the shell window, perform the following steps:
    1. Connect to the database (substitute the actual values for database name, instance owner, and instance owner password):

       db2 connect to <database_name> user <instance_owner> using <instance_owner_pwd>

    2. Enter the following stored procedure call that should return the value as 7.1.1.2:

       db2 "call sp_get_version()"

       Important: If the stored procedure call does not return the value as 7.1.1.2, then contact IBM Rational Software Support.
    3. Enter the following command, which should return a 32-digit alphanumeric character string, to indicate successful application of the interim fix:

       db2 "values(get_unique_id())"

       Note: If the command does not return such a value, then contact IBM Rational Software Support.

2b. For Oracle users: Updating the database component

1. Open a terminal shell.
2. In the shell window, change the path to ${IFIX_PACKAGE}/Database/Oracle
3. Grant script execution rights by running the following command:

   chmod 777 applyIFix.sh

4. Apply the interim fix by running the script:

    ./applyIFix.sh

   Enter the following information when you are prompted:

   • ORACLE_HOME
   • ORACLE_SID or TNS string
   • Rational Portfolio Manager schema owner
   • Rational Portfolio Manager schema owner password
5. Check log files produced in ${IFIX_PACKAGE}/Database/Oracle/logs for errors.
   Note: If the log file lists invalid objects or other errors, then contact IBM Rational Software Support.
6. In the command window, change the path to ${IFIX_PACKAGE}/Database/updateSQL directory.
7. If Interim fix 001 (iFix001) was previously applied to the Rational Portfolio Manager database, perform this step; otherwise proceed to the next step.
   1. Open the updateTMT_SETTINGS.sql file with a text editor.
   2. In the updateTMT_SETTINGS.sql file, SECTION : iFix001, delete the following lines:

      update TMT_SETTINGS set description = '7.1.1.2 iFix001' where element_id = 'APPLICATION_VERSION';
      INSERT INTO TMT_SETTINGS(LEVEL_ID,TYPE_ID,MAX_RANK,CHILD_COUNT,DELETED_COUNT,ELEMENT_ID,ELEMENT_NAME,PARENT_ID,REC_USER,REC_STATUS,REC_DATETIME,RANK,SETTING_VALUE,DESCRIPTION)
      VALUES(0,1,0,0,0,'ATTRIBUTE_CUST_FIELDS_FEATURE___',null,null,'PMO_SUPERVISOR','I','2008-06-20 11:27:00.000000','00000026',3,'Enable/Disable Attr and CustFlds feature flag for IGS. the first bit controls Attributes (0: disable, 1: enable), the second bit controls Custom Fields(0: disable, 1: enable)');
      

   3. Save the file.
8. From the shell window, update the server information:
   1. Set the variable ORALCE_SID to the appropriate value for the Rational Portfolio Manager database. For example, the command for bash shell is export ORACLE_SID=IBMRPM
   2. Connect to the Rational Portfolio Manager database by running the following command:

      sqlplus <schema_owner>/<password>

   3. At the sqlplus command line, run the following commands in order:

      ALTER SESSION SET NLS_DATE_FORMAT='YYYY-MM-DD';
      ALTER SESSION SET NLS_TIMESTAMP_FORMAT ='YYYY-MM-DD HH24:MI:SS.FF6';
      @updateTMT_SETTINGS.sql;	
      	commit;
      exit;

      Note: If you encounter errors running the commands at the sqlplus command line, contact IBM Rational Software Support.
9. Update the Oracle leveling library with the appropriate one from the directory, ${IFIX_PACKAGE}/Database/Oracle/Leveling
   Note: For more information on shared library configuration, refer to Rational Portfolio Manager 7.1.1.2 Installation and Upgrade guide, Chapter 3. Installing IBM Rational Portfolio Manager database.

3. Updating the middleware component

Update the middleware component as specified in the Rational Portfolio Manager 7.1.1.2 Installation and Upgrade guide, Chapter 4. Installing IBM Rational Portfolio Manager middleware.

4. Restarting Rational Portfolio Manager

Restart the Rational Portfolio Manager Web application and the associated alert server.

Contacting IBM Rational Software Support

IBM Rational Software Support provides you with technical assistance.

For contact information and guidelines or reference materials that you need when you require support, read the IBM Software Support Handbook at http://techsupport.services.ibm.com/guides/handbook.html.

For product news, events, and other information, visit the product home page for Rational Portfolio Manager Software at http://www.ibm.com/software/awdtools/portfolio/index.html.

Before you contact IBM Rational Software Support, gather the background information that you need to describe your problem. When describing a problem to an IBM software support specialist, be as specific as possible and include all relevant background information so that the specialist can help you solve the problem efficiently. To save time, know the answers to these questions:

• What software versions were you running when the problem occurred?
• Do you have logs, traces, or messages that are related to the problem?
• Can you reproduce the problem? If so, what steps do you take to reproduce it?
• Is there a workaround for the problem? If so, be prepared to describe the workaround.

Notices and trademarks

© Copyright IBM Corporation 2000, 2008. All Rights Reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this documentation in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this documentation. The furnishing of this documentation does not give you any license to these patents. You can send license inquiries, in writing, to:

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OR CONDITIONS OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this documentation and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.

Trademarks and service marks

The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both:

• IBM
• Rational
• DB2
• WebSphere

Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Other company, product, or service names may be trademarks or service marks of others.