        Tivoli Monitoring for Transaction Perfomance
                       v5.1
          Fix Pack 2 for Web Transaction Performance

DATE:                   Jul 25, 2003
COMPONENT:              TMTP - Web Transaction Performance
DESCRIPTION/DRIVER:     Cumulative Patch - 5.1-WTP-FP02

IMPORTANT: THIS IS THE LATEST INFORMATION AND INSTRUCTIONS AVAILABLE 
           FOR THIS PACKAGE AS OF 2003/07/31.

PROBLEMS RESOLVED:
  APARs:
    IY32769  SCHEDULER OVERRUN INDICATOR FOR STI ENDPOINTS
    IY33552  STI TIMES OUT BEFORE TRANSACTION COMPLETES                       
    IY38274  STI NEEDS TO STOP EXECUTING WHEN IT ENCOUNTERS ERROR  
    IY40226  STI DESIRED CONTENT CONSTRAINT FIELD FAILS WITH JAPANESE TEXT  
    IY41049  CANNOT DELETE EVENTS PRIOR TO 01/01/03 USING THE GUI  
    IY41134  JAVASCRIPT INTERACTION BETWEEN FRAMES CAUSES STIP TIMEOUT  
    IY41951  RECEIVE SPORADIC "URL NOT AVAIL" MESSAGES WITH CLIENT CERT STI   
    IY42272  STI APPLICATION ERROR: COULD NOT RUN THE TRANSACTION THIS ITERA  
    IY42325  STI CANNOT RUN TRANSACTIONS DUE TO ACCESS VIOLATIONS.  
    IY42945  STI-UNHANDLED COM EXCEPTIONS CAUSES ENDPOINT TO CRASH  
    IY43394  LANG PACK LAYS DOWN MULTIPLE VERSIONUPDATE.PROPERTIES  
    IY43609  STI ENDPOINT HANGS AFTER SEVERAL DAYS OF RUN: THE SERVICE IS     
    IY43642  SCALABILITY FOR WSC COLLECTIONS NEEDS TO BE IMPROVED  
    IY43988  STI51 REPORTS USER EXPERIENCE TIME WITH HUGE VALUE >1M SECONDS,  
    IY44214  IE DROPS CONTENTS OF POST REQUEST IN STI PLAYBACK  
    IY44260  TIMS QOS EVENT DRILL DOWN DETAILS DOESN'T REPORT REQUESTIP       
    IY44281  STI JOBS FAIL SPORADICALLY AFTER FP1 INSTALL.  PBCC-TRACE.LOG    
    IY44998  STI TIMES OUT WHEN IT TRIES TO NAVIGATE JASVASCRIPT URLS  
    IY45078  STI CURRENT TIME PARAMETER NEEDS TO BE DYNAMIC  
    IY45229  STI PBACK AND .NET ASP APPLI USING VIEWSTATE FAILURE  

  Internal Defects:
    116442  Endpoint Times should be GMT for TEDW  
    119493  DateConverter.java file inclusion to source tree  
    120354  STI Freezes when COM interface APIs fail.  

ARCHITECTURE(s): ALL SUPPORTED PLATFORMS

PATCHES SUPERSEDED BY THIS PATCH: 
    5.1-WTP-FP01    TMTP 5.1 Fixpack 1.

DEPENDENCIES: 
    TMTP 5.1 RTM.

SPECIAL CONSIDERATIONS: 

 RE-APPLY INTERIM FIXES FOR STI WEBDETAILER COMPONENT:
     Interim Fixes that corresponds to the following problems:
        IY43907, 
        IY38575, 
        IY43495
     will be overriden by the Fix Pack installation.
     In case you are subscribed to any of them, follow the corresponding 
     instructions to reapply the Interim Fixes.
     No action is required if such problems are not occurring in your
     environment.

 NEW INSTALLATIONS OF STI ENDPOINTS AFTER APPLYING THIS FIX PACK TO THE 
 INTERNET MANAGEMENT SERVER:

     IMPORTANT: 2 reboots are required to install a new STI endpoint.

     To avoid conflicts between the reboot actions executed by the 5.1 RTM 
     installation program (i.e. the installation program of the TMTP 5.1 CD-ROM)
     and the autoupdate mechanism of this Fix Pack, the invocation of the RTM install
     program must include the following parameter: "-P startService.active=false",
     like in the following example:

        F:\> setup_Endpoint_w32.exe -P startService.active=false

     This install option switch will prevent the Endpoint service from being started, 
     before the machine is rebooted by the user at the last panel of the installation 
     program.
     When the machine reboots and brings up the Endpoint service, the autoupdate
     mechanism will be triggered and, depending on the autoupdate configuration
     selected on the installation panels of this Fix Pack, the machine will be rebooted 
     automatically or will need to be rebooted manually.

     Refer to the "ADDITIONAL INSTRUCTIONS FOR THE ENDPOINT UPDATE" section below.

 IY32769. SCHEDULER OVERRUN INDICATOR FOR STI ENDPOINTS.
     FILE         = stm.properties
     RTM Location = lib/stm.jar
     USER Location= configuration
     KEY          = uploadOverrunMessages
                    # Enable upload of Scheduler Overrun Messages to TIMS/GUI.
                    # DEFAULT value: false

     Enable this property to generate a message every time an STI job misses an
     execution at it's desired frequency interval. Usefull to alert  scheduler 
     overload conditions that lead to missing monitoring and statistic data points.
     NOTE: Only supported locale for this message is "en" (English).
     
 d112659 - New logging properties for STI Endpoints.
    To configure the logging level, use the file:
        <BASEDIR>/Endpoint/configuration/sti-playback.properties
    The default value is set to WARNING.

    The possible levels of logging are as follows:
        FATAL
        ERROR
        WARNING
        INFO
        DEBUG_MIN
        DEBUG_MID
        DEBUG_MAX
    The level of logging will also include those with a higher severity.
    Refer to the sti-playback.properties file for additional details.

 IY35829, IY37898:
  IMPORTANT NOTE FOR STI RECORDER:
    STI Recorder installations will need to be reinstalled.
    The patching mechanism will not upload code to STI Recorder instances.

FILES REPLACED OR ADDED BY THIS FIX PACK:
 MANAGEMENT SERVER AND GUI:
  <BASEDIR>/ManagementServer/TIMS/lib/local/*.update
  <BASEDIR>/ManagementServer/TIMS/lib/properties/versionupdate.properties
  <BASEDIR>/ManagementServer/TIMS/lib/properties/xsversion.properties
  <BASEDIR>/ManagementServer/TIMS/lib/fw-common.jar
  <BASEDIR>/ManagementServer/TIMS/lib/report.jar
  <BASEDIR>/ManagementServer/TIMS/lib/webui.jar

 ENDPOINTS:
 All types (QoS, STI, WSC):
  <BASEDIR>/Endpoint/configuration/versionupdate.properties
  <BASEDIR>/Endpoint/lib/fw-common.jar
  <BASEDIR>/Endpoint/lib/stm.jar

 STI:
  <BASEDIR>/Endpoint/bin/w32-ix86/cclog.dll
  <BASEDIR>/Endpoint/bin/w32-ix86/libtos.dll
  <BASEDIR>/Endpoint/bin/w32-ix86/libtio.dll
  <BASEDIR>/Endpoint/bin/w32-ix86/libtthred.dll
  <BASEDIR>/Endpoint/bin/w32-ix86/libmsg21.dll
  <BASEDIR>/Endpoint/bin/w32-ix86/playback.dll
  <BASEDIR>/Endpoint/bin/w32-ix86/IEListener.dll
  <BASEDIR>/Endpoint/bin/w32-ix86/wd_elogp.dll
  <BASEDIR>/Endpoint/bin/w32-ix86/wd_HTTPp.dll
  <BASEDIR>/Endpoint/bin/w32-ix86/wd_LSPi.dll  
  <BASEDIR>/Endpoint/bin/w32-ix86/wd_ITEMp.dll
  <BASEDIR>/Endpoint/bin/w32-ix86/wd_PRECp.dll 
  <BASEDIR>/Endpoint/bin/w32-ix86/wd_FEEDp.dll 
  <BASEDIR>/Endpoint/bin/w32-ix86/wd_Archp.dll 
  <BASEDIR>/Endpoint/bin/w32-ix86/pd_FEEDp.dll 
  <BASEDIR>/Endpoint/bin/w32-ix86/wd_agent.exe 
  <BASEDIR>/Endpoint/bin/w32-ix86/wd_evgen.exe 
  <BASEDIR>/Endpoint/bin/w32-ix86/wd_WS2i.exe  
  <BASEDIR>/Endpoint/bin/w32-ix86/wd_agctl.exe 
  <BASEDIR>/Endpoint/bin/w32-ix86/wd_PROXY.exe 
  <BASEDIR>/Endpoint/bin/w32-ix86/wd_WS2s.lsp 
  %SystemRoot%\system32\wd_sdk.dll
  %SystemRoot%\system32\wd_ete.dll

 WSC:
  <BASEDIR>/Endpoint/lib/WSCDBPatch.tar
  <BASEDIR>/Endpoint/bin/wscdbpatch.sh 
  <BASEDIR>/Endpoint/bin/wscdbpatch.bat
  <BASEDIR>/Endpoint/lib/cswa.jar
  <BASEDIR>/Endpoint/lib/cswaproperties.jar

 QOS:
  No relevant files are affected.

APPLYING THE PATCH:

   NOTE: ALWAYS MAKE SURE THAT YOU HAVE A VIABLE BACKUP BEFORE 
   INSTALLING ANY SOFTWARE.

  This Fix Pack makes use of the Autoupdate feature of TMTP 5.1
  which simplifies the deployment process, by installing the patch only 
  to the Management Server machine.
  Installation of this Fix Pack is performed in the same manner
  as the TIMS installation. Please refer to the TMTP 5.1 Installation
  Guide for additional reference.

  The installer will discover the base directory for the Management Server. 
  You will be prompted to confirm it. In case a failure in the discovery 
  process has occurred, verify that a valid installation of the Management 
  Server is present. If so, you will need to modify the directory to reflect the 
  location where the Management Server is located. The directory
  specified at this time needs to be the directory immediately above
  "ManagementServer". For example, if the Management Server is installed 
  in /opt/Tivoli/Internet/ManagementServer then the installation directory 
  selected must be /opt/Tivoli/Internet. The ManagementServer directory 
  is a sub directory of the install location.

  1) INSTALL USING THE NATIVE PLATFORM LAUNCHERS.
     Download the appropriate executable for your TIMS:
       AIX    : 5.1-TMTP-FP02_aix.bin 
       Solaris: 5.1-TMTP-FP02_sol.bin 
       Win32  : 5.1-TMTP-FP02_w32.exe

     On Unix platforms, the installer will search a valid supported JVM 
     to be used when executing the installation.
     To aid in this process, you can specify the location of the JVM by
     specifying the installer option -is:javahome like in this example:
         $ 5.1-TMTP-FP01_sol -is:javahome <DIR>
         where <DIR>=/opt/java131

     The Windows installer, 5.1-TMTP-FP01_w32.exe, contains a bundled JVM 
     that will be used to launch the installation.

     This installation will replace files on the Management Server and
     create the  <BASEDIR>/ManagementServer/TIMS/update directory
     that the autoupdate feature will use to populate files to connected 
     Endpoints.

  2) INSTALL USING THE JAR FILE.
      In case you have problems using the native platform launchers, you can 
      use the java command line in a generic form.
     a) Download the generic 5.1-TMTP-FP01.jar file.
     b) Ensure that a Java JRE (1.3.1 or later) is in your path. 
     c) Place the 5.1-TMTP-FP02.jar file to any location and 
        execute:
           java -jar <LOCATION>/5.1-TMTP-FP02.jar

  *** See ADDITIONAL INSTRUCTIONS FOR THE ENDPOINT UPDATE ***


  INSTALLATION LOGGING:
  
  The installation program creates a log of all activities that it 
  performs during installation. The log file will be created at the 
  BASEDIR specified in the destination panel. 
  The log file name is 5.1-TMTP-FP01_log.txt.
  For example, if your TIMS is installed in /opt/Tivoli/Internet,
  the log file will be /opt/Tivoli/Internet/5.1-TMTP-FP01_log.txt

  Whenever a failure to install the patch occurs, verify the logging messages
  on this file. It will provide usefull information to troubleshoot the 
  problem.

ADDITIONAL INSTALLATION INSTRUCTIONS: 

 At a configurable update interval whose default is 15 Mins, 
 defined in:
     FILE         = endpointupdate.properties
     RTM Location = lib/properties.jar
     USER Location= configuration
     KEY          = endpoint.autoUpdateInterval
 the Endpoint contacts the Management Server to verify if 
 an update is available from the TIMS. If the TIMS and the Endpoint are 
 at the same version and patch level, defined in:
     FILE:        = versionupdate.properties
     RTM Location = lib/properties.jar
     USER Location= configuration
     KEY          = patchLevel
 then, no update is necessary and no action is taken.

 If changes have been deployed to the TIMS since the Endpoint's 
 last update, the Auto-Update Subsystem schedules a random time within the 
 update interval (15 mins default) to perform the Endpoint update. 
 This randomization will prevent a simultaneous onslaught of download 
 requests to the Management Server.  
 At the scheduled update time, the Endpoint downloads the appropriate files 
 from the TIMS and performs the update.  

 The user can optionally disable the autoupdate mechanism by setting 
 the Auto-Update enable flag to false in:
     FILE:        = versionupdate.properties
     RTM Location = lib/properties.jar
     USER Location= <BASEDIR>/configuration
     KEY          = endpoint.update

 Once a property value is changed, the Endpoint or ManagementServer
 processes should be restarted.

 Please refer to the TMTP 5.1 User's Guide for additional information.

  ===== ADDITIONAL INSTRUCTIONS FOR THE ENDPOINT UPDATE ======
  
  A) Restart of STI Endpoints.
     If autoupdate is configured to not reboot the STI endpoints, 
     all endpoints must be restarted manually.
     This is also true, every time a new STI endpoint is 
     installed.

  B) WSC Endpoints. Applying the patch.
    (Win32 and Unix platforms)
    
    NOTE: If you have already performed these instructions below from Fix Pack 1 
    for TMTP 5.1, it is not necessary to apply the following instructions.

    Extract the WSCDBPatch.tar file and execute the script to update the database.
    1. Extract the contents of the tar file using winzip or the Unix tar command:
       a) cd <BASEDIR>/Endpoint
       b) tar -xvf <BASEDIR>/Endpoint/WSCDBPatch.tar

    2. The previous step, extracts 3 files located at:
        <BASEDIR>/Endpoint/bin/wscdbpatch.bat
        <BASEDIR>/Endpoint/bin/wscdbpatch.sh
        <BASEDIR>/Endpoint/lib/local/support/WSCDBPatch.class
    
    3. Finally, execute the extracted script:
       a) cd bin
       b) ./wscdbpatch.sh  # For Unix Platforms
          wscdbpatch.bat   # For Win32

    IMPORTANT: In Windows platforms, change the DB2_HOME value 
               contained in the script if you are
               not using the default DB2 install directory.
               Modify wscdbpatch.bat: 
                    set DB2_HOME=<DB2_INSTALL>
                Example: set DB2_HOME=C:\IBM\DB2\sqllib

ROLLBACK MECHANISM.
 WARNING: The Rollback mechanism is not supported for this Fix Pack.
          The Endpoints will not rollback automatically at this moment.

 5.1-TMTP-FP01 can be removed and the system restored to the prior
 running version if you follow the steps outline below. 

 IS VERY IMPORTANT THAT YOU CONTACT IBM TIVOLI SUPPORT PRIOR TO 
 PERFORM THIS ACTION.

 Uninstallation of the Fix Pack can be done as follows:

 ON THE MANAGEMENT SERVER:
 1. Execute the uninstall.bin (or uninstall.exe) file located in:
     <BASEDIR>/5.1-TMTP-FP02/uninstall.<bin/exe>

 2. Follow the instructions for the Uninstall program.

 ON THE ENDPOINTS:
 1. Stop the Endpoint processes.

 2. Copy the autoupdate backup files located at:
            <BASEDIR>/Endpoint/backup999/* 
    and replace the existing ones in the 
            <BASEDIR>/Endpoint 
    directory. 
    Where 999 is the Julian day when autoupdate was executed.
    This directory structure was created by the last run of the autoupdate
    mechanism, and contains a backup for the files replaced on the Endpoint. 

 3. Remove the following file:
        <BASEDIR>/Endpoint/configuration/versionupdate.properties

 4. STI Endpoints.
    The WebDetailer component should not be uninstalled.
    Contact IBM Support for detailed procedures.

 5. Start the Endpoint processes.

FIXES FROM PREVIOUSLY RELEASED PATCH(es): 
    5.1-WTP-FP01:
  APARs:
    IY32771  STIP JOB SKIPS URLS AFTER A DNS ERROR (500)                      
    IY34838  TWSA DATABASE NEEDS SOME COLUMN UPDATES TO GET CORRECT DATA IN   
    IY35829  WSI RECORDER EFIX9 LEVEL : RECORDER GENERATES AN INVALID XML <R  
    IY38274  STI NEEDS TO STOP EXECUTING WHEN IT ENCOUNTERS ERROR
    IY38759  STIP FAILS WITH "MEMORY COULD NOT BE 'WRITTEN' " AND DRWATSON
    IY37898  5.1 RECORDER ADDS "TARGET" LINE IN TRANS.XML FILE FOR POPUP
    IY40226  STI DESIRED CONTENT CONSTRAINT FIELD FAILS WITH JAPANESE TEXT  
    IY42325  STI CANNOT RUN TRANSACTIONS DUE TO ACCESS VIOLATIONS.          

  Internal Defects:
    d112436  Recorder needs to handle fullscreen popup window  
    d112514  logging does not always obey the multi-file/size properties  
    d112659  convert logging to use Tivoli's cclog C++ logging library  
    d114638  Need scripts for periodic purging of data from WSC  
    d116214  lpwinsvc32ctl goes down without explanation  
    d116267  STI:One of the conditions to check for dynamic request is wrong  
    d116303  (Ref: IY38759) Trap in LSP with wd_PROXY 
    d116304  (Ref: IY38759) Fix problems with socket keep alive under SSL  
    d116305  (Ref: IY38759) add error log to wd_SDK  
    d116306  (Ref: IY38759) wd_Agent does not load wd_elogp.dll   
    d116318  Problem with function return code  
    d116327  (Ref: IY38759) revised wd_ete.dll fifo roll over logic  
    d116339  (Ref: IY38759) Port 114317/115086. Try-catch blocks in entry points  
    d116344  (Ref: IY38759) STI:target attribute causing URL not available event  
    d116364  (Ref: IY38759) STI Endpoint abends with Dr. Watson  
    d116444  (Ref: d112659) STIP. ccLog fails and aborts lpwin32 process                   
    d116564  (Ref: IY38759) STIP. Heap corruption causes hang/crashes.                     
    d116565  STI. DocumentComplete events not received. IExplorer remain
    d116629  (Ref: IY38759) STIP. Change linkage option to dynamic Multithreaded DLLs      
    d116670  (Ref: d112659) STI. Enpoint crash with CCLog enabled. CCgRelease calls.       
    d116744  (Ref: IY38759) STIP. FP01 Windows NT hangs or crashes.                         
    d116837  WD. Network apps performance downgraded. Filtering needed.
    d116873  (Ref: d112659) STIP. Logging: Harmless errors. Logger API Calls.     
    d117456  STIP. Logging misleading ERROR entries.                        
    d117549  Need to replace property names stm.properties

KNOWN DEFECTS OR LIMITATIONS: 
  STI Endpoints:
    d116272  Crash of wd_proxy after several days on Windows XP SMP
        Symptom: The Web Detailer Proxy process (wd_proxy.exe)
                 coredumps with an invalid handler exception.
        Cause  : Undetermined. 
                 Problem is not reproduceable in most environments.
        Workaround: Restart the "Web Detailer Proxy" service.
                 Please contact IBM Tivoli support for further references.

    d116722  WinXP. DNS resolution records not generated. DNS Client account
        Symptom: No DNS activity appear in the page records.
        Cause  : Problem is related to a reinforced security scheme in Windows XP 
                 for the DNS Client Service. The DNS Client Service under XP logs 
                 in using the system user acount 'NT AUTHORITY/NetworkService'.
        Workaround: Change the logon property of the DNS Client Service
                 to use the 'Local System account'.
        Remarks: This will revert the security of the DNS Client to Windows 2000
                 level.
    d118083  FP01. Bogus event throw when auto-update reboots STI Endpoints.
        Symptom: The following event is generated to the System Event Log:
                 "An endpoint auto-update process has failed due to an error. 
                 Automatic update of endpoint <EP_NAME> has failed "
        Cause  : The autoupdate mechanism is configured to automatically reboot 
                the STI Endpoints, 
        Woraround: This event is harmles. No further action is needed.
        Remarks: Verify that the STI endpoints get back on-line and that their 
                 version is set to WTP-FP02.
    d121799. JAPANESE URL IS GARBLED IN STI JOB.
        Symptom: The Recorder and Playback do not support Unicode/Double Byte 
                 encodings for URL values.
        Cause  : URL fields need to be internationalized.
        Workaround: Unknown.

    d121800. CONNEXION FAILS TO JAPANESE URL IN SI JOB.
        Symptom: Site Investigator jobs that contain Unicode/Double Byte
                 encodings in the initial URL, fail with conexion problems.
        Cause  : URL fields need to be internationalized.
        Workaround: Unknown.

    IY38575  PAGE ANALYZER VIEWER REPORT IS MISSING DATA  
    IY43495  WEBDETAILER CAN NOT RUN IN MULTIPROCESSOR BOXES.  
    IY43907  WebDetail in SSL mode is not sending a Doc Complete to STI  
    117158  LSP problem with Video playback  
    117159  wd_Proxy 'Automaticaly detect settings' needs to match IE  

