Licensed Materials - Property of IBM
Copyright IBM Corp. 2005  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 Response Time Tracking (ITCAMfRTT)
INTERIM FIX : 6.0.0.2-TIV-RTT-IF0046
RELEASE     : ITCAMfRTT v6.0
DATE        : 2007/09/17
LAST UPDATE : 2007/09/17

You should print and read this document and all associated references 
before applying this maintenance package. The online 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:
  Cumulative Interim Fix: 6.0.0.2-TIV-RTT-IF0046

  Supersedes:
    6.0.0.0-TIV-RTT-FP0001
    6.0.0.0-TIV-RTT-IF0023
    6.0.0.1-TIV-RTT-IF0033
    6.0.0.1-TIV-RTT-IF0041
    6.0.0.0-TIV-RTT-LA0014
    6.0.0.0-TIV-RTT-LA0016
    6.0.0.1-TIV-RTT-LA0025
    6.0.0.0-TIV-RTT-LA0027
    6.0.0.0-TIV-RTT-LA0029
    6.0.0.1-TIV-RTT-LA0032
    6.0.0.1-TIV-RTT-LA0035
    6.0.0.1-TIV-RTT-LA0036
    6.0.0.1-TIV-RTT-LA0037
    6.0.0.0-TIV-RTT-LA0038
    6.0.0.0-TIV-RTT-LA0040
    6.0.0.0-TIV-RTT-LA0041
    6.0.0.0-TIV-RTT-LA0044
    6.0.0.2-TIV-RTT-IF0045
    
    For additional information regarding the superseded package contents,
    please review the corresponding web document in the ITCAMfRTT Support Portal at:
    http://www-306.ibm.com/software/sysmgmt/products/support/IBMTivoliCompositeApplicationManagerforResponseTimeTracking.html

  New Content:
    c  IZ04181  MA HANGS RANDOMLY WHEN PINGING MANAGEMENT SERVER
    c  IY96951  MA FLAGGED FOR UPDATE VIA CLI DOES NOT UPDATE IF REBOOTED BEFORE UPDATE OCCURS
    c  IY97464  MA STATUS PING NOTIFICATION NOT REGISTERED
    c  IY98228  JMXSERVICE NOT RELIABLY PERSISTING COMPLETE MA STATE ON SHUTDOWN
    c  IY99018  AGENT STATUS PING USING OLD UUID AFTER OFFLINE INSTALL
    c  173219   Hostname needs to be regenerated for ghosted offline MA install
    c  176645   DoD: Offline install should not fail if MS unreachable
    c  176901   Offline MA install needs to use short hostname rather than FQDN
    c  178197   Dupe agent install or uninstall hangs with large agent group
    c  178720   MAs hangup on remote calls

  Content From Superseded Fixes:
    c  IY75133  WEB DETAILER CAUSES TIMEOUT WHILE ACCESSING SOME SECURE SITES  
    c  IY76699  TMTP UI COMPONENT MANAGEMENT VALUES CHANGE TO 1
    c  IY77100  TEST DATABASE CONNECTION DURING FIXPACK INSTALLATION  
    c  IY77174  TMTP ZOS MA J2EE /VAR/IBM/TIVOLI/BWM/LOGS DIRECTORY SPACE  GROW
    c  IY77262  MA AGENT STATUS GOES AND STAYS OFFLINE ON MS GUI "WORK WITH    
    c  IY77297  RTROBO.EXE CRASH WITH GUI PLAYBACK SCRIPT  WITH TMTP GENWIN
    c  IY77399  ADD FUNCTION TO EXCLUDE VP OVERHEAD TIME IN OVERALL              
    c  IY77591  J2EE INSTRUMENTATION PROBE THROWS NULL POINTER EXCEPTION  
    c  IY77873  MS DB PURGE DOES NOT DELETE J2EE EJB EDGE DATA; SOME DATA      
    c  IY77691  HARMLESS BWMCR4702W, BWMCR4701W AND BWMCR4501E ERRORS FILLING
    c  IY78437  MULTI FILE UPLOADER - ASSOCIATED FILE LIST NOT UPDATED  
    c  IY78596  ONLINE HELP FROM QOS DEPLOYMENT SCREEN ON MS GUI IS MIS-LEADING  
    c  IY78757  LOG VIEWER IN CLUSTERED MS FAILS TO PRESENT CONTENTS  
    c  IY78837  GENWIN VU AUTO INSTRUMENTATION FAILS IF PAGE REDIRECTS WITH 302 (duplicate of IY81967)  
    c  IY78858  SPECIAL STRING IN HTTP REQUEST CAUSES GENWIN VU                  
    c  IY79182  ENVIRONMENT VARIABLES NOT AVAILABLE TO GENWIN PLAYBACKS  
    c  IY79323  J2EE INSTRUMENTATION CAN BLOCK WEBSPHERE SERVER PMI STARTUP  
    c  IY79334  J2EE DEPLOYMENT ON WEBSPHERE  ON Z/OS  FAILS WITH EXCEPTION
    c  IY79339  MA AGENT STATUS CHANGES INTERMITTENTLY TO UNAVAILABLE  
    c  IY79594  'DO NOT SAVE ENCRYPTED PAGES TO DISK' IE OPTION UNCHECKED WHEN   
    c  IY79773  CAT TN3270 BEHAVIOR MODULE WITH ITCAM MA LISTENING POLICY NOT    
    c  IY80309  QOS NOT HADLING GZIP COPRESSION CORRECTLY  
    c  IY80463  STI: URL UNAVAILABLE RECOVERY EVENT RECIEVED BEFORE THE URL       
    c  IY80464  STI LOGS ERROR "BWMST0203E BAD PARAMETERS WERE PASSED.."
    c  IY80642  AFTER STI 5.3 FIXPACK2 APPLIED, STI PLAYBACK TRANSACTION,        
    c  IY80643  MA ARM .ZIP DATA FILES LARGER THAN 25MB ARE NOT TRANSFERRED TO   
    c  IY80790  J2EE INSTRUMENTED SERVERS CAN'T RESTART AFTER ONE IS UNDEPLOYED
    c  IY80926  ABEND ON TAPMAGENT CAN BLOCK ARM INSTRUMENTED APPLICATION CALLS  
    c  IY81624  SWARM.H INSTRUMENTED VU SCRIPT PLAYBACK WITH TESTMANAGER
    c  IY81962  SPACE IN USERNAME CAUSES STI PLAYBACK FAILURE
    c  IY81581  INCORRECT STI BAR CHARTS  
    c  IY81630  J2EE DEPLOYMENT TO Z/LINUX (SUSE 8 SP3) CAUSES WAS ON MA TO      
    c  IY81734  ARM METRICS PRECISION IS NOT ACCURATE IN ORACLE DATABASE  
    c  IY81841  RTAUTHENTICATION DATAPOOL NOT UPLOADED TO THE MANAGEMENT SERVER  
    c  IY81967  UNABLE TO COMPILE AUTO-INSTRUMENTED VU SCRIPT
    c  IY82170  MA JMXSERVICE COULD NOT BE STARTED IF STOP.SER FILE IS PRESENT
    c  IY82782  GAD - SOAP PORT PROBLEM - PMR 54297,999,724 (J2EE DISCOVERY FAILS ON Z/OS)
    c  IY82935  J2EE INSTRUMENTATION PROBE THROWS NULL POINTER EXCEPTION AT      
    c  IY83874  AUTO-INSTRUMENT INSERTS ARM STOP FOR OVERALL TRANS IN WRONG..
    c  IY83784  (TD) -MA DIES WITH 18+ GENWIN PLAYBACK POLICIES                     
    c  IY84352  MS FILE HANDLER LEAK ON TMTP-UPGRADES.PROPERTIES
    c  IY87067  MS CLUSTER SECURITY CONFIGURATION FAILS. CANNOT CREATE OBJECT.
    c  IY88754  AGENT UPDATE FAILS - MAX_OUTGOING_BYTES SETTING INCORRECT  
    c  IY89148  LOGVIEWER FOR Z/OS MA PRESENTS EMPTY CONTENT PAGE  
    c  IY89157  J2EE CREATESTATICCLASSINFO MESSAGES IN WEBSPHERE SYSPRINT
    c  IY89159  MA REMAINS IN INSTALLING STATE AFTER FAILURE TO UPDATE
    c  IY89256  SETMAPASSWORD.SH SCRIPT ABORTS WITH SYNTAX ERRORS  
    c  IY89275  FIXPACK INSTALLER TO PROMPT FOR DATABASE CONNECTION INFO (Fixed in IY77100)
    c  IY90510  EWLM UNABLE TO LOAD ARM ADAPTER MODULE ON LINUX-IX86  
    c  IY90769  JMXSERVICE IS TAKING > 100MB OF RAM
    c  IY90946  DAYLIGHT SAVINGS TIME WILL AFFECT ITCAMFRTT COMPONENTS 
    c  IY90915  J2EE DEPLOYMENT NO LONGER WORKS ON WAS 6.1.0.3  
    c  IY91817  UPDATE TO IBM JVM COMPONENTS
    c  IY93372  NO PING TIMESTAMPS UPDATED IN DB AFTER LA0038 APPLIED DUE TO     
    c  IY94921  TAPMAGENT CRASHES AFTER LA0038 APPLIED
    c  IY95689  UPDATE JAR FILE TOO LARGE AND CONTAINS UNNECESSARY INTERPS
    c  IY95692  MA FLAGGED FOR UPDATE WHILE OFFLINE IMMEDIATELY FAILS UPDATE AT RESTART
    c  IY96006  OFFLINE MA INSTALLATION FAILS IF MS OR ORACLE HOSTNAME CANNOT BE RESOLVED
    c  IY96116  UUID NEEDS TO BE REGENERATED FOR GHOSTED OFFLINE MA INSTALL
    c  170548   ARM DATA UPLOADS > 1MB STILL FAILING AFTER LA0038 APPLIED
    d  170349   DoD MAs fail to update: Not running with Administrator privileges
    d  168385   FFDC needs to be disabled on the agent
    d  168437   Memory exception with invalide correlator
    f  146266   Enable MA function without downcalls
    f  147434   Re-registration of MAs 
    d  147279   Need to fix BDH throttling
    d  147650   No component or system events on Solaris cluster with Oracle DB
    d  147744   ITCAMRTT6.0 errors in cluster install when cluster has "."
    d  148201   Events not working: GenericEventLog naming exceptions
    d  150097   BDH ARMErrorHandler needs to use random retry intervals
    d  150261   SQL Exceptions on GenericEventLogDBManager in cluster w/Oracle
    d  150350   Instance Sequencing not working
    d  150368   BDH chunking is not being used for downloads
    d  150564   Cluster Update: add update functionality to itcamfrtt.jacl
    d  159926   DoD: Need support for duplicate agent names

II. PREREQUISITES:
    ITCAMfRTT v6.0

III. DESCRIPTION:
  NEW APAR Fixes:
    c  IY82170  MA JMXSERVICE COULD NOT BE STARTED IF STOP.SER FILE IS PRESENT
    c  IY95689  UPDATE JAR FILE TOO LARGE AND CONTAINS UNNECESSARY INTERPS
    c  IY95692  MA FLAGGED FOR UPDATE WHILE OFFLINE IMMEDIATELY FAILS UPDATE AT RESTART

  APAR Fixes:
    c  IY89159  MA REMAINS IN INSTALLING STATE AFTER FAILURE TO UPDATE
    c  IY90769  JMXSERVICE IS TAKING > 100MB OF RAM
    c  IY93372  NO PING TIMESTAMPS UPDATED IN DB AFTER LA0038 APPLIED
    c  IY94921  TAPMAGENT CRASHES AFTER LA0038 APPLIED
    c  IY90769  JMXSERVICE IS TAKING > 100MB OF RAM
    c  IY76699  TMTP UI COMPONENT MANAGEMENT VALUES CHANGE TO 1
    c  IY77174  TMTP ZOS MA J2EE /VAR/IBM/TIVOLI/BWM/LOGS DIRECTORY SPACE  GROW
    c  IY77262  MA AGENT STATUS GOES AND STAYS OFFLINE ON MS GUI "WORK WITH    
    c  IY77873  MS DB PURGE DOES NOT DELETE J2EE EJB EDGE DATA; SOME DATA      
    c  IY79133  IF MA RESOLVES TO SHORT HOSTNAME, REQUESTURL IS NOT POPULATED   
    c  IY79323  J2EE INSTRUMENTATION CAN BLOCK WEBSPHERE SERVER PMI STARTUP  
    c  IY79334  J2EE DEPLOYMENT ON WEBSPHERE  ON Z/OS  FAILS WITH EXCEPTION
    c  IY79339  MA AGENT STATUS CHANGES INTERMITTENTLY TO UNAVAILABLE  
    c  IY80790  J2EE INSTRUMENTED SERVERS CAN'T RESTART AFTER ONE IS UNDEPLOYED
    c  IY80926  ABEND ON TAPMAGENT CAN BLOCK ARM INSTRUMENTED APPLICATION CALLS 
    c  IY81734  ARM METRICS PRECISION IS NOT ACCURATE IN ORACLE DATABASE

    c145718  Win MA running in foreground requires start/stop script  
        GenWin MAs are required to run in the foreground to be able to 
        interact with Rational Robot playback application.
        Users are currently required to kill the processes to effectively
        stop an MA. 
        start_tmtpd.bat and stop_tmtpd.bat scripts are provided to control the
        start and stop actions for the ITCAMfRTT processes running as console
        processes.

  New Features:

    The following scripts are now available on Windows MAs:
      MA_BASEDIR/bin/w32-ix86/start_tmtpd.bat
      MA_BASEDIR/bin/w32-ix86/stop_tmtpd.bat

      c145718  Win MA running in foreground requires start/stop script  
          GenWin MAs are required to run in the foreground to be able to 
          interact with Rational Robot playback application.
          Users are currently required to kill the processes to effectively
          stop an MA. 
          start_tmtpd.bat and stop_tmtpd.bat scripts are provided to control the
          start and stop actions for the ITCAMfRTT processes running as console
          processes.

    f 147434  Re-registration of MAs (See "Management Agent Installation" 
              section below)
    f 146266  Enable MA function without downcalls.
    
    Feature 146266 enables two new funtions.

	1.) NO DOWNCALL MODE
	    This mode prevents the MS from making calls down to the agent and
	    may be desirable to users from a security perspective.  However, this 
	    mode exhibits restricted functionality in other areas:
		a.) Behaviors may not be deployed.
		b.) Real time data rollup will not be available.
		c.) Agent unavailability will not be detected.
		d.) Viewing agent logs from the MS will not work.
		e.) Root Cause Analysis events will not work.

	2.) MODIFIABLE GLOBAL PING INTERVAL
		The ping interval for agents can now be changed at run time for all
		agents by editing the 'ping.interval' system property in the ITCAM UI.
       

IV. INSTALLATION INSTRUCTIONS:
   IMPORTANT NOTES:
        1. INSTALLING ON TOP OF NON-SUPERSEDED INTERIM FIXES.
            If you are installing this package on systems where previous interim fixes
            or fixpacks have been applied, that are not superseded by this package, you 
            may loose the fixes provided by IBM Support. 
            Please review carefully the binaries changed sections of the packages or 
            contact IBM Support for further assistance.

        2. J2EE EJB EDGES ENABLED AND DISABLED
            The installer will replace the 
                  MS_BASEDIR/APPL/j2eeinst.jar
            with the one that corresponds to EJB edges disabled.
            The user must point this file to that of the desired behavior for your
            environment.

        3. GenWin Management Agents that are running in the foreground (jmxservice -R), will
           not be able to receive the update from the Management Server, unless they already
           have FP0001 or LA0010 applied.
           Here is the list of possible solutions:
           a. Install Interim Fix 6.0.0.0-TIV-RTT-LA0010 to each agent.

           b. Stop the MA and restart the MA running as a Windows Service, then proceed to 
              update the MA from the MS GUI.

           c. Use the silent install method described in C) below.

    A) INSTALLATION IN A NON-CLUSTER ENVIRONMENT.
   	The Interim Fix is applied directly to the ITCAMfRTT Management Server

    	1. Download the corresponding executable file for your Management Server
           	HP-UX:      6.0.0.2-TIV-RTT-IF0046_hpux.bin
           	Solaris:    6.0.0.2-TIV-RTT-IF0046_sol.bin
           	Linux-ppc:  6.0.0.2-TIV-RTT-IF0046_linuxppc.bin
           	Linux-ix86: 6.0.0.2-TIV-RTT-IF0046_lin.bin
           	AIX:        6.0.0.2-TIV-RTT-IF0046_aix.bin
           	Linux-390:  6.0.0.2-TIV-RTT-IF0046_lin390.bin
           	Windows:    6.0.0.2-TIV-RTT-IF0046_w32.exe
           Optionally, you may download the generic 6.0.0.2-TIV-RTT-IF0046.jar file

        2. Create a backup of your Management Server database.

        3. For Unix Management Servers connected to a DB2 database:
           When applying this package to Management Servers running in a Unix Platform 
           (AIX, Solaris, Linux, Linux s390, Linux ppc, HPUX), and connected to a DB2
           database server, it is necessary to prepare the DB2 environment for the session 
           that will invoke the installation program.
           Execute the db2profile script of the DB2 client installation as in the 
           following example:
               # .  /usr/db2inst1/sqllib/db2profile
           *Note the (.) dot before the command.

        4. Launch the downloadable executable file.
           For example:
               # /tmp/6.0.0.2-TIV-RTT-IF0046_aix.bin
           Follow the instructions from the Installation Wizard.

        5. Restart the WebSphere Application Server

        6. Proceed to deploy the update to the endpoints in your environment by using
           the ITCAMfRTT GUI:
                  System Administration / Agent Updates

           On the contrary, you may use the instructions for a manual installation
           of this maintenance package to the Management Agents.
           See section below D) MANUAL INSTALLATION ON THE MANAGEMENT AGENTS

           For z/OS MAs, please refer to the z/OS section below: 
                "VII. INSTALLATION INSTRUCTIONS FOR zOS and OS400".

    B) INSTALLATION FOR MANAGEMENT SERVERS IN A WEBSPHERE CLUSTER ENVIRONMENT.
        This Interim Fix is applied to all the server members of the cluster that are
        running the ITCAMfRTT Management Server application.

        1. Download the following compressed file:
                6.0.0.2-TIV-RTT-IF0046.cluster.zip 

        2. Expand it into a temporary directory.

	3. Create backup copies of the following files, which are usually located
	   in the $CLUSTER_INSTALL_CD/utilities directory (for example, 
	   /mnt/ITCAM/cluster/utilities):

		- itcamfrtt.jacl
		- resource_scripts.jacl

	4. Copy the two jacl scripts from the temporary directory into the location 
	   where the original jacl scripts were found (see step 3).

        5. Create a backup of the TMTP_SHARED_ROOT directory.

        6. Copy the MS_SHARED contents to the shared directory defined for your
               cluster environment. This shared directory is pointed by WebSphere's
               TMTP_SHARED_ROOT environment variable.
                cp -rp temp/MS_SHARED/* /opt/ibm/tivoli/MS/$(TMTP_SHARED)
    
	7. Go to the jacl scripts directory and run the following command to update 
	   your cluster configuration PRIOR to updating the ITMTP application ear file:

		wsadmin.sh -username {WAS_USER} -password {WAS_PASSWORD} -f itcamfrtt.jacl update

	   Make sure to use the full path to the wsadmin.sh command, for example:

		/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/bin/wsadmin.sh ...

	   The script will make required changes to the WebSphere configuration, and then
	   it will uninstall the ITMTP-Cluster application and reinstall it (which is required). 
	   Whem prompted for the location of the tmtpCluster.ear file, select the appropriate 
	   tmtpCluster.ear file as follows:

            	For an MS running on a DB2 database, use:
                   temp/ear.cluster/DB2UDB_V81/tmtpCluster.ear 
            	For an MS running on an Oracle database, use:
                   temp/ear.cluster/ORACLE_V9I/tmtpCluster.ear 
       
        Please consult the WebSphere Administrator for specific tasks regarding
        the upgrade and deployment of applications in the WebSphere Cluster Environment.


        8. Update the Management Server database:
            
           IMPORTANT: Create a backup of the Management Server database.
            
           a) Run the database updates by following the prodecure in Section C) below.          
            
        9. Proceed to deploy the update to the endpoints in your environment by using
           the ITCAMfRTT GUI:
              System Administration / Agent Updates
           
           See section below D) MANUAL INSTALLATION ON THE MANAGEMENT AGENTS

            For z/OS MAs, please refer to the z/OS section below: 
                       VII. INSTALLATION INSTRUCTIONS FOR zOS and OS400
                       
     C) MANUALLY UPDATING THE MANAGEMENT SERVER DATABASE
	NOTE: Update the database with the correct build number by executing the update sql
           script which came with this update (choose the script which is appropriate to
           your database vendor).

	NOTE: if either LA0016 or FP0001 has been installed on 
	   this system and the Update_<DB_INTERP>.SQL script has previously been run on 
	   the tablespace in use by this MS, run the Update_apps_<DB_INTERP>.sql script 
	   instead (again, choosing the script that is appropriate to your database
	   vendor):
                    
         FOR DB2:
             $ db2 connect to <TMTP_DATABASE> user <DB2USER> using <PASSWORD>
             $ db2 set current schema <DB2SCHEMA>
	     $ db2 -td@ -vf <TEMP_CLUSTER_EXTRACT_DIR>/Update_DB2.SQL
			- OR - 
	     $ db2 -td@ -vf <TEMP_CLUSTER_EXTRACT_DIR>/Update_apps_db2.sql

             Where: <DB2USER> and <DB2SCHEMA> are usually the same value that corresponds to the
                    user that was used when installing the Management Server.
                    <MS_BASEDIR> is the Management Server base directory.
             For example:
                 $ db2 connect to TMTP user db2inst1 using mypassword
                 $ db2 set current schema db2inst1
		 $ db2 -td@ -vf /tmp/6.0.0.0-TIV-RTT-IF0044.cluster/Update_apps_db2.sql

             Please verify that the .sql commands are executed correctly.

         FOR ORACLE:
              $ sqlplus <ORA_USER>/<ORA_PASSWORD>@<ORA_CONNECTSTRING>
	     SQL> @<TEMP_CLUSTER_EXTRACT_DIR>/Update_Oracle.SQL

             Where: <ORA_USER>/<ORA_PASSWORD> are the oracle user name and password to authenticate
                    to the Oracle server.
                    <MS_BASEDIR> is the Management Server base directory.

             For example:
             $ sqlplus oracle/mypassword@oracle_sid
	     SQL> @/tmp/IF0044/Update_Oracle.SQL
			- OR - 
	     SQL> @/tmp/IF0044/Update_apps_oracle.sql

             You will need to restart the Websphere Application Server for the management server after 
             updating the database.  

	  FURTHER ACTIONS TO ENABLE IY81734 - MILLISECOND GRANULARITY (ORACLE ONLY):
		a) From an existing Oracle client installation, upload the ojdbc14.jar file to 
		   the ITCAM MS server installation directory. This file is usually under 

			${ORACLE_HOME}/oracle92/jdbc/lib

		   Preferably, this file should be copied to the lib/ext directory of the MS:

			cp ojdbc14.jar <MS_BASEDIR>/MS/lib/ext

		   This file can either be downloaded from the Oracle support site (contact your 
		   Oracle Support Representative for further information) or it can be taken from
		   an existing Oracle Client installation that is on the WAS server. Alternatively,
		   the existing copy can be used in the existing location, just point the WAS Classpath
		   to this location rather than the <MS_BASEDIR>/MS/lib/ext location.

		b) Using WebSphere Admin Console, modify the JDBC driver classpath. Navigate to the: 

			Resources->JDBC Providers->Oracle JDBC Thin Driver - TMTP 

		   Change the Classpath environment variable to point to the ojdbc14.jar location:

			${TMTP_ROOT}/lib/ext/ojdbc14.jar
		
		NOTE: This change must be done on EACH server in the cluster. The location of the 
		      ojdbc14.jar does not have to be identical (although that is recommended), but
		      the WAS Classpath must point to the correct location on EACH individual server.

	  FURTHER ACTIONS TO ENABLE "NO DOWNCALL" MODE ON THE MS:
		a.) Start the management server to pick up two new general system properties 
		    (downcalls.disabled and ping.interval)
		b.) Access ITCAMfRTT console
		c.) Go to My Work->System Administration->System Properties
		d.) Select General Properties from the drop down list
		e.) Set downcalls.disabled to "true"
		f.) Recycle the management server
	   
		The above steps will put the server in upcall only mode and from this point on the server 
		have limited function as such(no behavior deployment, no real time data rollup, no log 
		viewing, etc.). 
	
    D) MANAGEMENT AGENT INSTALLATION:
       This package can optionally be installed directly on the Management Agents
       using the silent install option of the 6.002.4400_MA.jar package. Also note that a 
       Windows-only patch package has been provided, designated 6.002.4400_MA_w32.jar, which
       contains only the Windows update files.

       For z/OS MAs, please refer to the z/OS section below:
              VII. INSTALLATION INSTRUCTIONS FOR zOS and OS400

       1) Retrieve the 6.002.4600_MA.jar
          After installing this fixpack in the Management Server, using the steps outlined
          in A) or B) above, the 6.002.4600_MA.jar for ITCAMfRTT v6.0 MAs can be located at:
              <MS_SHARED>/fixpacks/6.0/6.002.4600_MA.jar
          Proceed to upload this file to a temporary location.

       2) Run the silent install option:
           Usage:
               <MA_BASEDIR>\jre142\jre\bin\java -Dtmtp.user.dir=<MA_BASEDIR> -jar 6.002.4600_MA.jar -silent

           For example, if the MA_BASEDIR is C:\ITCAM\RTT\MA, the command will be as follows:
               C:\ITCAM\RTT\MA\jre142\jre\bin\java -Dtmtp.user.dir=C:\ITCAM\RTT\MA -jar 6.002.4600_MA.jar -silent

       After the installation finishes, verify that the MA is online and that the Management Server has
       updated its version to the new value.

        IF0046 installation instructions with firewall blocking downcall port

        Copy the IF0046 MA update from the 6.0.0.2-TIV-RTT-IF0046_MA_update in this patch 
	to the MA install directory on the MA. Run the following command on the MA to 
	manually update to IF0044:

        <MA_BASEDIR>/java/jre/bin/java -Dtmtp.user.dir=<MABASEDIR> -jar 6.002.4600_MA.jar -silent

	To enable the MA to work behind a firewall and without downcalls from the MS:
	
	    1. Stop the MA service
	    2. Edit <MA_HOME>/config/endpoint.properties to set endpoint.port=0 (instead of 1976)
	    3. Start the MA service

	To re-register an MA against an MS after the hostname has changed:

	    a.) Change the hostname of the computer
	    b.) Reboot the computer to make sure that the hostname changes have taken effect
	    c.) Stop the management agent
	    d.) Execute the configMa.bat file (found in the MA/bin/{INTERP} directory)
	    e.) Start the management agent
 
	NOTE: To use the automatic ping interval update:
	    - Access the ITCAMfRTT console
	    - Go to My Work->System Administration->System Properties
	    - Select General Properties from the drop down list
	    - Set ping.interval to a value in seconds.
	The agents will pick up this value with their next ping.

    E) UPDATE FOR THE STI COMPONENT.
       This component will be upgraded to the FixPack level of code when the MA is updated using the 
       Work With Updates view of the GUI.

    F) UPDATE FOR THE GENWIN COMPONENT.
       For this component to be updated, it needs to be Removed and Deployed.
       Proceed to the System Administration/Monitoring Components view of the GUI to Remove and Deploy
       the component.

    G) UPDATE FOR THE J2EE COMPONENT.
       For this component to be updated, it needs to be Removed and Deployed.
       Proceed to the System Administration/Monitoring Components view of the GUI to Remove and Deploy
       the component.

    H) UPDATE FOR THE QOS COMPONENT.
       For this component to be updated, it needs to be Removed and Deployed.
       Proceed to the System Administration/Monitoring Components view of the GUI to Remove and Deploy
       the component.
       On certain Unix interps, it will be necessary to restart the Management Agent after the 
       MA has been updated to the new maintenance level. Please refer to d154844 below.

    I) UPDATE FOR THE CAT COMPONENT.
       For this component to be updated, it needs to be Removed and Deployed.
       Proceed to the System Administration/Monitoring Components view of the GUI to Remove and Deploy
       the component.

    Review the section "VIII. KNOWN DEFECTS OR LIMITATIONS" below. 

V. UNINSTALLATION INSTRUCTIONS:

    A) ON THE MANAGEMENT SERVER:
       1. Execute the 
            MS_BASEDIR/6.0.0.2-TIV-RTT-IF0046/_uninst/uninstall.bin 
          and follow the instructions from the installer GUI.

       2. Update the Enterprise application using the RTM CD_ROM image as explained in step
          IV.B.5 above:
         CLUSTER: Choose the appropriate ear file from:
              CDROM/RTTMSclustr/ear/DB2UDB_V81/tmtpCluster.ear 
              CDROM/RTTMSclustr/ear/ORACLE_V9I/tmtpCluster.ear 
         STANDALONE: Choose the appropriate ear file from:
                CDROM/RTTMScommon/disk2/ear/DB2UDB_V81/tmtp.ear
                CDROM/RTTMScommon/disk2/ear/ORACLE_V9I/tmtp.ear

       3. Restore the BACKUP database.

    B) ON THE MANAGEMENT AGENTS:
        1. Execute the package uninstall.jar located in the MA base directory as follows
          C:> java -jar <MA_BASEDIR>/6.0.0.2-TIV-RTT-IF0046/_uninst/uninstall.jar -silent

        2. Once the package is removed, remove the 6.0.0.2-TIV-RTT-IF0046 directory:
          $ rm -rf <MA_BASEDIR>/6.0.0.2-TIV-RTT-IF0046

        3. Restart the Management Agent.

    Please contact IBM Support for further assistance.

    C) UNINSTALLING THE "NO DOWNCALL MODE" FEATURE:

    	1.) To disable the feature:
    		a.) On the MS:
    			- Set the downcalls.disabled to "false" using ITCAMfRTT console
			- Restart the management server
		b.) On the MA:
			- Reset endpoint.port=1976 in MA/config/endpoint.properties
			- Restart the management agent
    	2.) To completely uninstall the feature:
		a.) Clustered Management Server Uninstallation:
			If a backupConfig.sh was performed as recommended in step 3a above, use 
				restoreConfig.sh WebSphereConfig_DATE.zip 
			from the <WAS_PROFILE>/bin directory for the Deployment Manager and AppServers.   
			Otherwise, reinstall the tmtpCluster.ear file as documented in the ITCAM Installing 
			a management server in a WebSphere cluster environment:

          		http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/index.jsp?topic=/com.ibm.itcamrtt.doc/ITCAMfTT_InstallCluster.htm
	  		NOTE: Contact ITCAMfRTT support for clustered management unstallation instructions on non-WAS 6.0. 
		
    Please contact IBM Support for further assistance.
                    
VI. MODIFIED FILES:

    A) Management Server:
       A full redeployment of the ITCAMfRTT application binaries for 
       the Management Server is performed as part of the installation.

       The binaries changed on the Management Server can also be determined
       by listing the MS_BASEDIR/6.0.0.2-TIV-RTT-IF0046/staging directory.

    B) Management Agents:
       The binaries changed on the Management Agents can be determined
       by listing the MA_BASEDIR/6.0.0.2-TIV-RTT-IF0046/staging directory.


VII. INSTALLATION INSTRUCTIONS FOR zOS and OS400

   A) zOS: Applying this package for z/OS Management Agents.

     1. Download the zOS package: 
         6.0.0.2-TIV-RTT-IF0046_zos.tar 

        The tar package contains files with the structure of the MA directory 
        under:
             /usr/lpp/tmtp/V6R0M0/MA 

     2. Stop the MA
          # /etc/tmtp/MA/config/stop_tmptd.sh

     3. It is recommended to create a backup of the 
            /usr/lpp/tmtp/V6R0M0/MA directory. 
        For example:
            # tar cvf MA.tar.backup /usr/lpp/tmtp/V6R0M0/MA

        This backup can be used in case is necessary to rollback the changes introduced 
        by this maintenance package.

     4.  Untar the 6.0.0.2-TIV-RTT-IF0046_zOS.tar file to the base MA directory.
         Specify the 'o' option of the tar command to override and preserve the
         ownership of the user and group running the MA on your system.
         For example:
           # cd /usr/lpp/tmtp/V6R0M0/MA
           # tar xvfo /tmp/6.0.0.2-TIV-RTT-IF0046_zOS.tar

     5. The package contains the files used to deploy the J2EE component:
            MA/lib/j2eeinst.jar.EJBs
            MA/lib/j2eeinst.jar.noEJBs

        Verify that the j2eeinst.jar file in the
            MA/app/instrument directory
         corresponds to the desired behavior when deploying the
         J2EE component to this MA.
         For performance considerations the
             MA/lib/j2eeinst.jar.noEJBs 
         file is used the default file copied over the MA/app/instrument location.
  
         However, if your monitoring requirements need the enablement of EJB
         edges, you can copy the j2eeinst.jar.EJBs file to the
         app/instrument directory as follows:
             # cp lib/j2eeinst.jar.EJBs app/instrument

         Otherwise, no action is necessary.

      6. Start the MA.
              # /etc/tmtp/MA/config/start_tmtpd.sh

    B) OS400: Applying this package for OS400 Management Agents.

       OS400 Agents need to be uninstalled and reinstalled using the OS400 
       installation package available in the download location.

       1. Uninstall the current OS400 MA.

       2. Download the 
            6.0.0.2-TIV-RTT-IF0046_OS400_SETUP.zip 
        package from the FixPack location. 

       3. Execute a normal installation of the OS400 MA.
       
       In some cases, if the MA install fails you may have to manually remove the previous 
       OS400 TMTP libraries:  
                                              
         a. Use the 'worksysval qsyslibl' command.  Select 2 to change.    
         b. Remove QTIVTMTP                                                
         c. Execute the command 'dltlib qtivtmtp'                          
         d. If part (c) fails with the error "Library QTIVTMTP on library  
            list and cannot be deleted."                                   
            then, Re-IPL the system and execute part (c) again.
         e. Re-attempt the MA install

        Please contact IBM Support to receive individual updates of APARs contained in 
        this package.

VIII. KNOWN DEFECTS OR LIMITATIONS:  

    d149160  Agents do not appear on "Agent Updates" panel after IF3 install  
        Symptom: After an Agent completes the update and changes its version to the most 
                 up to date version, it disappears from the Agent Updates view.
        Cause:   A defect in the GUI display panel.
        Workaround: None. The agent has been updated successfully, it can be 
                 observed in the Agents view of the GUI.

    d147113 FixPack installer blocks on tmtp-upgrades.properties
        Symptom: The MS installer fails with an error message on the tmtp-upgrades.properties
                 file in Windows Management Servers.
       The WAS process locks the tmtp-upgrades.properties file which prevents the installer
           from continuing. In order to proceed past this issue, initiate the following 
           procedure:
       1. Stop the WebSphere Application Server hosting the Management Server
            i.e: stopServer server1 -username root -password mypasswd
       2. Move the MS/config/tmtp-upgrades.properties file to a diferent name
            i.e. mv MS/config/tmtp-upgrades.properties MS/config/tmtp-upgrades.properties.BAK
       3. Start WAS
            i.e: startSserver server1 -username root -password mypasswd
       4. Reattempt the 6.0.0.0-TIV-RTT-IF0044 installation procedure

    d149481 FixPack installer fails to install the EAR package
        Symptoms: An error panel is presented in the fixpack installation that
                  provides an error message while updated the EAR package.

        Cause:    The requestTimeout property of the SOAP port is too small.

        Solution:
            Increase the com.ibm.SOAP.requestTimeout property to 600 in the 
            WebSphere/profiles/<profileName>/properties/soap.client.props file,
            and restart the WebSphere application server.
            When starting or stopping a server using a wsadmin interactive scripting
            session, you receive an exception indicating read timed out, for example: 
            WASX7015E: Exception running command: "$AdminControl startServer server1
            Node1"; 
            exception information:
            com.ibm.websphere.management.exception.ConnectorException 
            org.apache.soap.SOAPException: [SOAPException: faultCode=SOAP-ENV:Client;
            msg=Read timed out; targetException=java.net.SocketTimeoutException: Read timed out] 
            This exception occurs because the timeout value is too small. Increase the
            timeout value specified by the com.ibm.SOAP.requestTimeout property in the
            soap.client.props file in the install_root/profiles/profile_name/properties
            directory. The value you choose depends on a number of factors such as the size 
            and the number of the applications installed on the server, the speed of your machine, 
            and the level of usage of your machine. 
            The default value of the com.ibm.SOAP.requestTimeout property is 180 seconds. 
    
      d149537  MA fails after applying IF0044. Windows Sockets error: 10106: create  
        Symptom: After applying the fixpack update to a Windows MA that is running as console, 
            (using 6.0.0.0-TIV-RTT-LA0010) the agent goes offline and remains in 'Installing' 
            state in the Agent Updates page. 
            The SystemRoot environment is not pointing to the C:\WINDOWS directory.
        Cause: The Windows MA running as console is not receiving the proper environment
               entries. Specifically, the SystemRoot environment variable is not pointing to 
               the location C:\WINDOWS or is missing.
        Solution: Restart the MA.

      cIY84908  AFTER APPLYING FIXPACK THE LANGUAGE PACK CONFIGURATION IS LOST
        Symptom: The ITCAMfRTT MS GUI no longer displays localized multi-language content.
        Cause  : Due to a limitation of the EAR deployment of the ITCAMfRTT Management Server, 
                the Language Pack files installed to enable NLS support, will be lost 
                when the ITMTP.ear directory is replaced with the content of the fixpack.
        Solution: Reinstall the Language Pack.

        If any ITCAMfRTT Language Pack has been installed on the Management
        server, customer is required to re-install the language pack.

      d154884  Deploy QoS component failes if the MA is not restarted.
        Symptom: On some UNIX-based management agents, after updating the agent to IF23,
                 if the agent is not restarted after updating, QoS deployments will fail.
        Cause:   PATH environment is not inherited until restart in some UNIX 
        environments.
        Workaround: Restart the agent after updating to IF23 for agents needing a QoS
        deployment. 

      d149441  IF3: exception and ascii output during successful OS400 update  
            The 6.0.0.2-TIV-RTT-IF0046 MA package does not support AS400 Management Agents.
            Please contact IBM Support to receive an AS400 PTF package.

