Licensed Materials - Property of IBM
Copyright IBM Corp. 2008  All Rights Reserved.
US Government Users Restricted Rights - Use, duplication or
disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

PRODUCT     : IBM Tivoli Composite Application Manager for Transactions (ITCAMfTransactions)
FIXPACK     : 7.1.0.0-TIV-CAMRT-FP0001
RELEASE     : ITCAMfTransactions v7.1
DATE        : 2008/12/19
LAST UPDATE : 2008/12/19

You should print and read this document and all associated references
before applying this maintenance package. The on-line page where this
package was downloaded is the most up to date information and supersedes
all other versions of this document.

I. MAINTENANCE DELIVERY VEHICLE (MDV):
    7.1.0.0-TIV-CAMRT-FP0001
    
    Superseded Packages:
        Interim Fix: 7.1.0.0-TIV-CAMRT-IF0001
    
    For additional information regarding the superseded package contents,
    please review the corresponding web documents in the ITCAMfTransactions v7.1 Support Portal at:
    
    http://www-306.ibm.com/software/sysmgmt/products/support/IBMTivoliCompositeApplicationManagerforTransactions.html

II. PREREQUISITES:
    ITCAMfTransactions v7.1 RTM
        For up to date ITCAMfTransactions v7.1 software prerequisites, please visit the 
        ITCAMfTransactions v7.1 Information Center at the following URL:
            http://publib.boulder.ibm.com/infocenter/tivihelp/v24r1/index.jsp?topic=/com.ibm.itcamt.doc_7.1/prereq71/en_US/HTML/Version71.html

    ITM Minimum Prerequisites:
        ITM 6.2 FixPack 1 Interim Fix 1 or better
        ITM v6.2.1 or better

    For additional download packages or ITM support information, visit the ITM support portal at:
        http://www-306.ibm.com/software/sysmgmt/products/support/IBMTivoliMonitoringV6.html
    
III. CONTENT DESCRIPTION:
  A) APAR Content:
    IZ31322  ADD HTTPS SUPPORT FOR APACHE 2.2 TO WRT COMPONENT  
             A new configuration option while installing the WRM agent has been included.
    IZ35008  SERVER TIME METRIC FROM RPT 7.0.2 SCRIPTS ARE ZERO IN RT 6.2
             This APAR also applies to RPT v7.0.1 installs.
    IZ36944  ITCAMFRT V7.1 ERROR BWMCR8510E WHEN INSTALLING RPT USING WRAPPER
    IZ40122  ITCAMFTRANS V7.1 PROVIDE WEBSEAL CLIENT IP ADDRESS SUPPORT  
             This new capability is implemented with Tivoli Access Manager v6.1 (WebSeal).
             WRT WebSeal support for real Client IP addresses if using virtual host junctions.
    IZ40166  ITCAMFTRANS V7.1 PROVIDE SUPPORT FOR ITM 6.2.1  
    IZ37159  ITCAMFTR V7.1 RRT AGENT TO SUPPORT RPT V8.0
             Support for Rational Performance Tester 8 including encrypted data pools. 
             information see section E) below
    IZ38384  AMCE KEYBOARD SHORTCUT CONFLICTS WITH ISM  
    IZ38741  AMC TEP ICON DISAPPEAR ON ACTION CODE CONFLICTS WITH ITPA  
    IZ40086  ITCAMFTRANS V7.1 ENABLE RPT SCHEDULES FOR CITRIX PLAYBACK
             Rational Performance Tester 8 Schedules can be used to schedule the 
             ordering of test playback.
    IZ40121  ITCAMFTRANS T5 WRT SUPPORT FOR HTTP POST INFORMATION
             The Web Response Time component supports monitoring of
             HTTP Post data for some web servers.

  B) Additional Internal Defects:
        190672  AMC (KT3) German workspaces have unexpected line breaks
        191036  AMC Editor user security permissions (acess control list) incorrect
        191084  HPUX data not collected by Robotic (T6) agent
        191129  AMC (KT3) workspaces not showing servers data from the CAT (KT4) component
        190494  Missing flyovers for attributes
        191277  AMC Editor has wrong headings for type/value
        191320  Error when loading AMCE Editor when there is not enough permission
        191322  Missing Links in Transaction Reporter (KTO) topology

  C) New Capabilities included in this update:

        With the release of this fixpack, we have updated the documentation at this URL:

        http://publib.boulder.ibm.com/infocenter/tivihelp/v24r1/index.jsp?topic=/com.ibm.itcamt.doc_7.1/welcome.htm
         
        For a summary of the new functionality, see Product Overview document's "New in this release" section.

        1) Rational Performance Tester 8 support

        This fixpack now supports the use of RPT 8 schedules. The use of RPT schedules is
        limited to ordering of RPT 8 tests for playback. For instance, certain Citrix systems
        require a HTTP test for login, followed by a Citrix test to do an activity after login.
        Using CAM for Transaction's RPT 8 schedule functionality, a RPT 8 schedule can be created
        and uploaded. This schedule is then scheduled for playback as any other Robotic Response
        Time script would be. For more information see the updated Administrator's Guide section
        "Executing scripts in a specific order with Rational Performance Tester schedules".

        Also, this fixpack includes the ability to use encrypted data pools with RPT 8. Data pools
        often contain sensitive information such as login identities. If you use RPT 8 to
        encrypt the data pool and then use it in a test for playback, upon export of the test
        to the Application Management Console (T3) you must type in the datapool password. This
        datapool password is then encrypted and stored with the test for playback on the
        Robotic Response Time (T6) agent.

        RPT v8.0 supplied with this fixpack will not support the IPv6 in HTTP(S), SAP, Siebel 
        and Citrix scripts along with new protocols in RPT 8 such as SIP, TCP Sockets.

        2) Web Response Time Enhancements 

        The Web Response Time (T5) agent can now capture and report on HTTP Post forms. This
        allows you to monitor your HTTP post form data and use the value from the form to report
        on transaction names. For more information see the Administrator's Guide section
        "HTTP POST form processing configuration"

        The Web Response Time agent can be configured to report records when there is zero
        traffic. This allows you to be alerted when your volume for a particular application
        or server falls to zero. For more information see the Administrator's Guide section
        "Reporting zero records for periods of inactivity"

        The Web Response Time agent can now monitor the number of unique IP addresses seen
        per data collection interval (default 5 minutes). These counts of unique IP addresses
        are added to four new attributes added to the main attribute groups. For more information
        see the Administrator's Guide section "Enabling unique user counts to track visitors 
        per period"
        
        3) ITCAM for Response Time 6.2 situation upgrade to 7.1 configuration

        The configuration from ITCAM for Response Time 6.2 can now be upgraded to ITCAM
        for Transactions 7.1 via a command line tool. This tool creates the appropriate
        Applications, Transactions and Profiles based on your ITCAM for RT 6.2 situation
        configuration. For more information see the "Upgrading situations to profiles 
        automatically" section of the Administrator's Guide.

IV. INSTALLATION INSTRUCTIONS:
    
    This maintenance package is applied directly to the Tivoli Enterprise Management Agents (TEMAs)
    it is also required to be applied to the following ITM components:
        - Tivoli Enterprise Management Servers (TEMS) in the ITM infrastructure, including any Remote TEMS 
          or failover TEMS configurations. 

        - Tivoli Enterprise Portal Server (TEPS).
    
    The fixpack upgrade images can only be used to upgrade from the 7.1 GA version of the product,
    not from Response Time 6.2 images. If you are at 6.2, you must upgrade to 7.1 GA then to this
    fixpack.


    Download the corresponding executable file bundles for your TEMA:
        T3 (End User Response Time) Agent
           AIX    : 7.1.0.0-TIV-CAMRT-FP0001_T3.aix.tar
           HP-UX  : 7.1.0.0-TIV-CAMRT-FP0001_T3.hp.tar
           Linux  : 7.1.0.0-TIV-CAMRT-FP0001_T3.linux.tar
           Itanium: 7.1.0.0-TIV-CAMRT-FP0001_T3.ia64-amd64.tar   (TEMS & TEPS support only)
           Solaris: 7.1.0.0-TIV-CAMRT-FP0001_T3.sun.tar
           Windows: 7.1.0.0-TIV-CAMRT-FP0001_T3.Windows.zip

        T4 (Client Response Time) Agent
           AIX    : 7.1.0.0-TIV-CAMRT-FP0001_T4.aix.tar
           HP-UX  : 7.1.0.0-TIV-CAMRT-FP0001_T4.hp.tar
           Linux  : 7.1.0.0-TIV-CAMRT-FP0001_T4.linux.tar
           Itanium: 7.1.0.0-TIV-CAMRT-FP0001_T4.ia64-amd64.tar   (TEMS & TEPS support only)
           Solaris: 7.1.0.0-TIV-CAMRT-FP0001_T4.sun.tar
           Windows: 7.1.0.0-TIV-CAMRT-FP0001_T4.Windows.zip

        T5 (Web Response Time) Agent
           AIX    : 7.1.0.0-TIV-CAMRT-FP0001_T5.aix.tar
           HP-UX  : 7.1.0.0-TIV-CAMRT-FP0001_T5.hp.tar
           Linux  : 7.1.0.0-TIV-CAMRT-FP0001_T5.linux.tar
           Itanium: 7.1.0.0-TIV-CAMRT-FP0001_T5.ia64-amd64.tar   (TEMS & TEPS support only)
           Solaris: 7.1.0.0-TIV-CAMRT-FP0001_T5.sun.tar
           Windows: 7.1.0.0-TIV-CAMRT-FP0001_T5.Windows.zip

        T6 (Robotic Response Time) Agent
           AIX    : 7.1.0.0-TIV-CAMRT-FP0001_T6.aix.tar
           HP-UX  : 7.1.0.0-TIV-CAMRT-FP0001_T6.hp.tar
           Linux  : 7.1.0.0-TIV-CAMRT-FP0001_T6.linux.tar
           Itanium: 7.1.0.0-TIV-CAMRT-FP0001_T6.ia64-amd64.tar   (TEMS & TEPS support only)
           Solaris: 7.1.0.0-TIV-CAMRT-FP0001_T6.sun.tar
           Windows: 7.1.0.0-TIV-CAMRT-FP0001_T6.Windows.zip

        RPT (Rational Performance Tester Wrapper Installer)
           Windows: 7.1.0.0-TIV-CAMRT-FP0001_RPTWrapper.zip 
	   Windows: 7.1.0.0-TIV-CAMRT-FP0001_RPTBase.zip

    A) INSTALLING THE UPDATE ON WINDOWS TEMAs.

       1. Download the corresponding Windows upgrade package (T3, T4, T5, T6)
           Extract it to a temporary directory (i.e. C:\TEMP\T6).

       2. USING THE WIZARD INSTALLATION GUI.
           a. Execute the setup.exe command to start the Installation Wizard.
              The setup.exe is located under the WINDOWS directory in the chosen temporary directory.
              For example: 
                  C:\TEMP\T6\WINDOWS\setup.exe 
        
           b. Follow the Installation Wizard panels by responding to each option that corresponds to the 
              TEMA agent being upgraded.
              Default values are provided. Is possible to select or specify different options that must match 
              the appropriate settings for your environment. 
              Also, you may be required to fill in the values when a blank option is not permitted.
        
           NOTE:  During the interactive installation, you can choose to add the TEMA to the TEMS depot so you can 
                  do remote installs for the platform you are adding into the depot.
     
       3. USING THE SILENT INSTALL CLI.
           a. Prepare the silent install file to configure appropriate values for the installation program to use
              while running the installation process.

              The silent installation file is located under the silent directory of the temporary directory 
              image. (i.e. C:\TEMP\T3\silent\T3V710_Silent.txt)

              Edit the silent install file to provide appropriate values for the desired configuration. 
              By default, all options are commented out, and the installer uses the values from the previous TEMA 
              configuration. The silent install file describes each option, and you can also find information in the 
              monitoring agent's User Guide.

           b. Open a Command Prompt window and execute the following command to launch the silent installer:
               C:> start /wait c:\temp\t3\windows\setup.exe /z "/sfc:\temp\tema\silent\T3V710_silent.txt" /s /f2"c:\temp\install_output.txt"
            
               The silent install file that needs to be used will depend on the TEMA that is being updated.
               The example command is for the T3 End User Response Time agent (T3).
        
           For additional information on the options for the silent installation of the TEMA agents, 
           please consult the ITCAMfTransactions v7.1 User's Guide.

       4. REBOOT THE COMPUTER.
           After the installation of the upgrade of a TEMA in Windows, it is necessary to reboot the computer to allow the system to
           properly register the latest settings in the Operating System registry.

           In environments where the TEPS and RT TEMA agents coexist in the same ITM instance, the update for the TEMAs will 
           offer the option to restart the computer, it is strongly recommended to install the support packages for the TEPS first and
           allow for the TEPS to restart before restarting the computer as part of the TEMA update.

    B) INSTALLING THE UPDATE ON UNIX BASED TEMAs.

       1. Download the corresponding Unix platform (aix, hp, linux, sun) upgrade package (T3, T4, T5, T6)
            and extract it to a temporary directory (i.e. /tmp/T3).

       2. USING THE SCRIPT BASED INSTALLATION PROCEDURE.
           a. Execute the install.sh to start the Installation Wizard.
              The install.sh command is located directly under the main directory of the upgrade image.
              For example:
                  # /tmp/T3/install.sh

           b. Follow the text wizard panels by responding to each option that corresponds to the 
              TEMA agent to be upgraded.

              Default values are provided, you may select different options or you may be required to 
              fill in the values when a blank option is not permitted.
        
          NOTE:  During the interactive installation, you can choose to add the TEMA to the TEMS depot so you can 
                 do remote installs for the platform you are adding into the depot.  The software prompts you for this 
                 option after you choose what you want to install.

           c. After the Installation Wizard completes, you must configure your agents.  
              This is done by issuing the itmcmd ITM command as follows:
              $ITM_HOME/bin/itmcmd config -A <AGENT_TYPE>
              Where <AGENT_TYPE> is t3, t4, t5 or t6 

              For example, to configure the Robotic Response Time agent (t6), issue:
                  # $ITM_HOME/bin/itmcmd config -A t6

       3. USING THE SILENT INSTALL CLI.
           a. Prepare the silent install file to configure appropriate values for the installation program to use
              while running the installation process.

              The silent installation file is located under the silent directory of the temporary directory 
              image. (i.e. /tmp/T3/silent/T3V710_Silent.txt)

              Edit the silent install file to provide appropriate values for the desired configuration. 
              By default, all options are commented out, and the installer uses the values from the previous TEMA 
              configuration. The silent install file describes each option, and you can also find information in the 
              monitoring agent's User Guide.

           b. Execute the following command to launch the silent installer:
                 ./install.sh -q -h /opt/IBM/ITM -p /tmp/T3/silent/T3V710_Silent_Unix.txt
            
               The silent install file that needs to be used, will depend on the TEMA that is being updated.
               The example command is for the T3 End User Response Time agent (T3).
        
           For additional information on the options for the silent installation of the TEMA agents, 
           please consult the ITCAMfTransactions v6.2 User's Guide.


    C) UPDATING TEMA AGENTS USING THE TEMS DEPOT REPOSITORY.
       To facilitate the deployment of the updates to the TEMA agents, is possible to add
       the upgrade images to the TEMS repository and transfer the updates to the agents. 
       Follow the instructions below:
        
        1. ADD THE UPDATE IMAGES TO THE TEMS DEPOT.
            a. Expand the TEMA tar or zip file into a temporary directory on the TEMS machine. 
                For example: C:\temp\tema
            
            b. Log onto the TEMS using the following command:
                tacmd login -u sysadmin -p password -s <TEMS.HOST.NAME>
            
            c. Issue the following command:
                Unix   : tacmd addBundles -i <directory>\unix
                Windows: tacmd addBundles -i <directory>\windows\deploy
                
                <directory> is the full path to the directory where you extracted the file. 
                For example:
                       tacmd addBundle -i C:\temp\T3\WINDOWS\deploy
    
            d. The tacmd command asks whether or not to include the bundles and the prerequisites in the depot. 
                Choose Yes.

        2. UPDATE A TEMA AGENT VIA THE TEMS REPOSITORY:
 
               Execute the following command: 
               C:\IBM\ITM\cms>tacmd login -u sysadmin -p <password> -s <hostname>
            
               For example: C:\IBM\ITM\cms>tacmd login -u sysadmin -p password -s utms15.tivlab.austin.ibm.com
            
               You must specify the -s option with a host name or address or you will see the following message: 
               KUIC00001E: The host name is not specified.
            
               Optionally, you can specify PROTOCOL and PORT as PROTOCOL://]HOST[:PORT].
            
               The system responds:
                   Validating user...
               KUIC00007I: User sysadmin logged into server on https://utms15.tivlab.austin.ibm.com:1889.
                   C:\IBM\ITM\cms>tacmd updateAgent -t t6 -n Primary:UTMA7:NT -v 7100
               KUICUA012I: Are you sure you want to update the T6 agents that manage utma7:T6 to version ? 
               Updating these agents stops any that are running, applies the changes, and restarts them.

        3.  Enter Y for yes or N for no.
            The system responds:    
                KUICUA011I: Updating the T6 agents.
                KUICUA009I: The T6 agents were updated.

    D) ADDITIONAL INSTALLATION INSTRUCTIONS.
       D.a T3 APPLICATION MANAGEMENT CONSOLE (END USER DASHBOARD) AGENT.

           After doing an upgrade from 7.1 to 7.1 fp1, the T3 agent needs to be reconfigured
           in order to start correctly.

       D.b T4 CLIENT RESPONSE TIME AGENT.

           After doing an upgrade from 7.1 to 7.1 fp1, the T4 agent needs to be reconfigured
           in order to start correctly.

       D.c T5 WEB RESPONSE TIME AGENT.
          
           After doing an upgrade from 7.1 to 7.1 fp1, the T5 agent needs to be reconfigured
           in order to start correctly.

       D.d T6 ROBOTIC RESPONSE TIME AGENT
          
           After doing an upgrade from 7.1 to 7.1 fp1, the T6 agent needs to be reconfigured
           in order to start correctly.

           Refer to section E) below for updates to the RPT Workbench.
     
    E)  IBM RATIONAL PERFORMANCE TESTER (RPT) CONTENT AND WORKBENCH, HOTFIX INSTALLATION INSTRUCTIONS
    
        This fixack refreshes the Rational Performance Tester (RPT) shipped with ITCAM for 
	Transactions v7.1. RPT v8.0 is shipped with this package along with fixes for the ITCAM 
	Export Plugin, ITCAM Simplified Test Editor and RPT hotfixes for the issues identified below.

        RPT v8.0 playback with this fixpack will not support the IPv6 for any script type. In addition
	new protocols in RPT 8 such as SIP, TCP Sockets are not yet supported.

        RPT 7.0.X scripts recorded with the 7.1 GA version of the product will continue to playback on agents
        running this fixpack.

        USING THE INCLUDED RPT WRAPPER INSTALLER TO INSTALL RPT 8 AND HOTFIXES

        ITCAM for Transactions 7.1 packages an installer for RPT 8.0.0 as well as the RPT plugin to support
        exporting the scripts to the Application Management Console. This installer can be run using
        the same way as the RPT 7.0.1 installer packaged with the GA product.

	There are two .zip files containing RPT 8 and the RPT wrapper installer. To install them, extract
	7.1.0.0-TIV-CAMRT-FP0001_RPTWrapper.zip and 7.1.0.0-TIV-CAMRT-FP0001_RPTBase.zip to the same
	directory. When they are extracted you should have a directory with two subdirectories:
		disk1/
		RPTBase/
	
	Then execute <extracted directory>\disk1\setup.exe to launch the install that will setup both
	RPT 8 and the ITCAM for Transactions RPT plugin.

        For further RPT installation details, consult the product documentation available in the Info Center:
                 http://publib.boulder.ibm.com/infocenter/tivihelp/v24r1/index.jsp?topic=/com.ibm.itcamt.doc_7.1/rt/Install_Guide/install_rpt.html

        NOTE: At the end of the install of the RPT 8.0.0 and plugin, there can be a popup documenting additional
        steps needed to finish configuration of the hotfixes. For more information see section "MANUAL 
        INSTRUCTIONS FOR INSTALLING HOTFIXES" below.

        RPT HOTFIXES:

        RPT Hotfixes that are required for ITCAM environments are available with this package and are included
        in the 7.1.0.0-TIV-CAMRT-FP0001_RPTWrapper.zip file. 

        After the RPT Workbench environment is updated to RPT v8 using the wrapper installer, hotfixes 
        bundled with this package will have been applied to the workbench environment.
        
        The following RPT v8.0.0 hotfixes are bundled with this package:
                R1175811_ARM_Transaction_Reporting-8               (added by  this Interim Fix for APAR IZ35008)
                R1380811_ITCAM_Dash_Names                          (included with this fixpack)
                R1383371_ITCAM_JARs                                (included with this fixpack)

        MANUAL INSTRUCTIONS FOR INSTALLING HOTFIXES:

        Steps 1-8 update existing RPT projects to use the hotfix. If you have a new install
        of RPT with no projects, these steps are not needed.

        Steps 9-15 are done by our RPT wrapper solution installer that installs the ITCAM
        perspective and export plugin.

        Steps 

        1) Start RPT with the workspace that contains the project(s) that you want to use 
        with the hotfix.

        2) For each project, right-click on the project name and select Properties (at the 
        bottom of the menu).

        3) In the Properties window, click on Java Build Path in the list on the left and 
        then click on the Libraries tab.

        4) Remove (with the Remove button) all the JARs and class folders in the Libraries
        tab EXCEPT for the last entry, "JRE System Library [jdk]".

        5) Click OK to dismiss the Properties window. If you have the Problems view open, 
        you may see various Errors; ignore these for now. 

        6) If you don't already have the Navigator view shown, use RPT's
        Window->Show View->Navigator to display it.

        7) In the Navigator view, find the project and expand it so that you can see the
        contents of the src\test folder.  This will contain entries for the automatically
        created Java files (containing long hexadecimal GUIDs like DFF5A ... 911DD) and
        custom code.  For example: 

                Testdemo_Test_DFF5A70BD6E0349A57A96A8042D911DD.java 
                PortalTesting_Test_A4F5A31B56E0149A88896B80E1D9159D.java 
                Testdemo_Schedule_DFF5A700D6E0E49A57A96A8041D935D9.java 
                Portal_Schedule_Schedule_A4F5A21B55E01495858CCB80E1D2159D.java 
                MyCustomCode.java 

        The above listing contains automatically-generated Java files for scripts Testdemo 
        and PortalTesting, schedules Testdemo and Portal_Schedule, and custom code 
        MyCustomCode.  

        Delete all the automatically-generated Java files (all the  *_Test_<GUID>.java 
        and *_Schedule_<GUID>.java files).  Don't delete the custom code files (those 
        without GUIDs). 

        8) After you've done the above steps 2-8 for each project that you want to continue 
        using, exit from RPT. 

        9) Unzip the contents of the 3 plugin .zip files documented above in the RPT HOTFIXES 
        section (the R1175811_ARM_Transaction_Reporting-8.zip, R1380811_ITCAM_Dash_Names.zip,
        R1383371_ITCAM_JARs). There will be five .jar files total when you finish the extract of
        the 3 .zip files
        

        10) If you don't already have them, create the following "dropins" directories: 

                C:\Program Files\IBM\SDP\dropins 
                C:\Program Files\IBM\SDP\rptse\dropins 

        11) Copy the five .jar files extracted from step 9 above to both of the directories 
        created in step 10

        12) Using a text editor (Notepad or Wordpad will work), open the bundles.info file
        at the following location: 

                C:\Program Files\IBM\SDP\configuration\org.eclipse.equinox.simpleconfigurator\bundles.info 

        13) At the bottom of bundles.info, add the following 5 lines EXACTLY as they appear here: 

com.ibm.rational.test.lt.arm,7.2.251.v200811061522,file:dropins\com.ibm.rational.test.lt.arm_7.2.251.v200811061522.jar,4,false
com.ibm.rational.test.lt.armbroker,7.2.251.v200811061522,file:dropins\com.ibm.rational.test.lt.armbroker_7.2.251.v200811061522.jar,4,false
com.ibm.rational.test.lt.execution.http,7.4.205.v200811061522,file:dropins\com.ibm.rational.test.lt.execution.http_7.4.205.v200811061522.jar,4,false
com.ibm.rational.test.common.models.behavior,7.1.2.200812021659,file:dropins\com.ibm.rational.test.common.models.behavior_7.1.2.200812021659.jar,4,false
com.ibm.rational.test.lt.execution,7.2.102.200811171435,file:dropins\com.ibm.rational.test.lt.execution_7.2.102.200811171435.jar,4,false
                

        14) Save the changes to bundles.info. 

        15) Repeat steps 12 through 14 for the second bundles.info file at the following location: 

                C:\Program Files\IBM\SDP\rptse\configuration\org.eclipse.equinox.simpleconfigurator\bundles.info 

        16) Restart RPT and do a recording and playback of a new, simple test in
        each project to re-generate the Java Build Path Libraries. 

        17) You can then verify that the hotfix is in place by checking 
        Help->About ...->Plug-in Details and check that the plugins have the following versions

                com.ibm.rational.test.lt.execution.http           7.4.205.v200811061522
                com.ibm.rational.test.lt.arm                      7.2.251.v200811061522
                com.ibm.rational.test.lt.armbroker                7.2.251.v200811061522
                com.ibm.rational.test.common.models.behavior      7.1.2.200812021659
                com.ibm.rational.test.lt.execution                7.2.102.200811171435
                
        
        There may be additional hotfixes that are released and required for ITCAM environments after this Interim Fix
        package has been released. For the most current RPT Hotfix information and download locations. 
        You may refer to the following document located in the ITCAMfTransactions Support Portal at
                  http://www-01.ibm.com/support/docview.wss?uid=swg21281906
        
        NOTES:

        Modifying the RPT wrapper installer's "disk1" directory name to another directory starting with
        "disk" will cause the install to fail (192153)

        Please ensure that all RPT tests that are already exported to the AMC/T3 agent before installing the
        new RPT Workbench package are recompiled and successfully played back before uploading them to 
        the AMC/T3 agent
     
        When recompiled RPT tests are exported to the AMC/T3 agent a new runtime will be exported to the AMC/T3 and 
        the agents will receive updated RPT tests within a short time period. If this behavior is not desired then 
        RPT tests have to be updated on the AMC/T3 in a maintenance window and not immediately after installing the 
        new version using the RPT Wrapper installer package shipped as part of this Interim Fix


V. UNINSTALLATION INSTRUCTIONS:

    This maintenance package can not be rolled back.
    The uninstallation instructions require that the TEMA agent be uninstalled and reinstalled.

    A) UNINSTALLING THE TEMA ON WINDOWS:
        1.    Go to the Windows Control Panel.
        2.    Choose "Add or Remove Program". 
        3.    Click on the TEMA you want to uninstall
        4.    Choose "Change/Remove" to uninstall it.
            
    B) UNINSTALLING THE TEMA ON UNIX:
        1.    Issue the following command from the /IBM/ITM/bin directory:
            ./uninstall.sh
        
        2.    Follow the instructions to uninstall the TEMA that you want to remove.
    
    If the ITM OS Agent is installed on the machine where the uninstall procedure is required,
    you may proceed as follows:
        1.    Log onto the TEPS.
        2.    Right click on the TEMA you want to remove. 
        3.    Choose Remove and follow the dialog buttons for removal.
    
    
VI. KNOWN DEFECTS OR LIMITATIONS:

    A) 6.2 Workspaces showing in a 7.1 Upgrade environment (192325)
        
        If a T3 agent has been upgraded from ITCAM RT 6.2 to ITCAM Transactions 7.1, 
        then the 6.2 workspaces may still be visible. If this is the case, the T3 
        agent should be stopped and all offline entries for T3 (including KT3A) would
        be removed, then the T3 agent can be started and the 7.1 workspaces will be 
        visible.

    B) RPT will not start when moving to RPT 7.0.2 (192448)

        If you are using RPT 7.0.1 from the ITCAM for Transactions 7.1 GA or IF1 
        release and move to RPT 7.0.2 your RPT may not start and you will see the 
        error "RPT License install command return code = 1". If this is the case,
        then you need to manually edit the following files:

                DefaultInputFile.xml
                LicenseInputFile.xml
                UpdateInputFile.xml
                ModifyInputFile.xml

        In each file, replace the line:

                <agent-input clean="true"> 
        with

                <agent-input acceptLicense="true" clean="true">           

    C)  Not all Robotic scripts are visible in the first page of the Robotic 
        Scripts workspace (190977)

        The Robotic Scripts workspace shows all the scripts uploaded to the 
        Server in table form. However, the table can be divided between
        multiple pages of data even if the number of scripts is small. The
        workaround is use ITM's page mechanism to view all the data.

    D)  When running a test in RPT, you get error IWAY0159E (192526)

        When running tests in RPT, the following message is displayed: "An error 
        occured while connecting to one or more profiling agents. Reason: IWAY0159E 
        The data collection infrastructure does not appear to be running on 
        localhost:100002. Please ensure it is running and try again."

        This is saying the Data Collection Infrastructure is not running. You
        can ingore this warning message and continue as normal and no error
        will occur.

    E)  When using the Browser client, you see old workspaces/Application 
        Management Console Editor after upgrade (192643)

        Be sure to clear your Browser's java cache after upgrading
        the product so that you see the latest workspaces and configuration
        tool.

    F)  All Client Response Time (T4) monitored applications need to be
        stopped before upgrade (192642)

        All programs monitored by the Client Application Tracker need to
        stopped before attempting an upgrade of the Client Response Time
        (T4) agent. Else, there will be a pop up warning that files are
        in Use. If you receive that pop up, stop the application suggested
        and press continue.

    G)  Special considerations for installing on 64-bit for AIX TEMS (193310, 
	193190)

	The ITCAM File Transfer Enablement (T1) has support for both
	32-bit TEMS as well as 64-bit TEMS on AIX. You should install the
	appropriate T1 support for your TEMS version.

	First determine if your TEMS is running in 32-bit or 64-bit
	mode. The steps to do that are:

	  1) Run ITM's cinfo class on the TEMS box
  
		<ITM_HOME>/bin/cinfo

	  2) Choose the option to show installed products

	  3) Find the entry similar to the below
		  ms	Tivoli Enterprise Monitoring Server
			aix523  Version: 06.20.01.02

	  4) If the version ends in 3, then you have a 32-bit TEMS. For
	  example aix523 and aix533 are both 32-bit TEMS.

	  5) If the version ends in 6, then you have a 64-bit TEMS. For
	  example aix526 and aix536 are both 64-bit TEMS.

	Now knowing the TEMS version, in the ITCAM for Transaction install 
	agent, you should choose the correct version of the File Transfer 
	Enablement for you TEMS version: either 32-bit or 64-bit.

	For more info on File Transfer Enablement see the Installation
	and Configuration Guide section "Enabling script file 
	transfer (UNIX and Linux)"

    H)  Web Response Time's Render time attribute can occasionally be zero 
        (193170)

        For URL's that contain the Java Script to enable Web Response Time's
        Render Time attribute, the render time can occasionally be zero. This
        can occur when the URL is frequently accessed within the same second
        from the same IP address.

    I)  Configuration upgrade utility only runs on ITM 6.2 fp1 not ITM 6.2.1
        (193092)

        The sit2profile utility that moves a RT 6.2 configuration to ITCAM
        for Transactions 7.l does not work in a ITM 6.2.1 environment. So
        before migrating to ITM 6.2.1, first upgrade to this fixpack, run
        the utility then migrate to ITM 6.2.1

    J)  Monitoring Websphere data using Request Metrics shows blank EJB names
        (193252)

        Some versions of Websphere's Request metrics return EJB names that 
        do not match the Application Management Configuration Editor, and 
        therefore show up blank in the subtransaction workspaces and the 
        Transaction Reporter topology. The workaround is to edit the
        default value in the AMC Editor. These are the steps:

        1) Open the Application Management Configuration Editor
        2) From the "Applications" tree, expand the 
                Websphere Application Server node
        3) Expand the Transaction Tracking node
        4) Click "All Websphere EJB Subtransactions"
        5) Click the Reporting tab on the right
        6) Change the default Transaction Name field to:
                $EJB name$$EJBName$

    K)  RPT Scripts containing non-ASCII characters do not record data (193280)

        If your RPT playback is completing but no data is displayed and
        the script's name contains non-ASCII (international) characters,
        be sure to check the following.
        
        You need to verify that RPT 8 Hotfix R1380811_ITCAM_Dash_Names is
        installed on your RPT 8. See Section E, above, for more information.

        In addition, you need the correct language fonts on your RPT 8
        installation machine.
       
    L)  RPT Web Services fail to succesfuly playback (193284)

	Web Services record and playback using RPT v7.0 and RPT v8.0 results
	in an IllegalAccessException from the Playback Engine during the 
	execution of RPT WebServices scripts. This issue is being investigated 
	and a fix will be announced and provided in a future Interim Fix package.

    M)  RPT 8 Test Navigator does not show new tests without refresh (192958)

	Newly recorded tests do not show up in the test navigator panel in 
	RPT 8. To see them, right click on the Project and chose refresh.
	The test will now be in the Navigator

    N)  RPT 8 test names with "." signs fail to export (193292)

	If a test name contains a "." character (say "ibm.com") the
	test will fail to export. The workaround is to remove the "."
	character in the test name.

    O)  Considerations for upgrading Web Response Time agent monitoring IIS https (193348)

	If your Web Response Time (T5) agent is monitoring https traffic from IIS, the
	IIS server needs to be stopped before the WRT upgrade is started.

