
COMPONENT_NAME: IBM Tivoli Monitoring for Web Infrastructure 5.1.2: 
WebSphere Application Server 
Component ID: 5724C01WS
(c) COPYRIGHT 2004 Tivoli Systems, International Business Machines Corp.
All Rights Reserved
Licensed Materials - Property of IBM
US Government Users Restricted Rights - Use, duplication or
disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Date: 
    02 July, 2004

Patch: 
    5.1.2-WAS-FP02
    IBM Tivoli Monitoring for Web Infrastructure 5.1.2: 
               WebSphere Application Server - Fix Pack 02

Component: 
    IBM Tivoli Monitoring for Web Infrastructure 5.1.2:
    WebSphere Application Server 


Table of Contents:
  o Section 1. General Description
      - Section 1.1 General Description
      - Section 1.2 Function Added    
      - Section 1.3 Products Certified
      - Section 1.4 Applications Supported
      - Section 1.5 Platforms Supported
      - Section 1.6 Dependencies
      - Section 1.7 Fixpacks superceded by this patch     
      - Section 1.8 Patch contents
  o Section 2. Problems Fixed
      - Section 2.1 Problems Fixed
      - Section 2.1.1 Problems Fixed (from 5.1.2-WAS-FP01)
      - Section 2.2 Files replaced or added by this fix pack
  o Section 3. Installation Notes
      - Section 3.1 Applying the patch
      - Section 3.2 Additional installation instructions - Warehouse Enablement
      - Section 3.3 Additional installation instructions - Resource Models
  o Section 4. Additional Notes
  o Section 5. Limitations and Known Problems  
      - Section 5.1 Limitations
      - Section 5.2 Known Problems


########################################################################
# Section 1. General Description                                       #
########################################################################

1.1 General Description:
    This fix pack adds Tivoli endpoint support for Linux on PowerPC (iSeries
    and pSeries).
    
    This fix pack also includes changes incorporated from FP01 
    (5.1.2-WAS-FP01).  This includes changes to the data warehouse modeling 
    for WebSphere Application Server version 3.5, 4 and 5 and Tivoli Data 
    Warehouse performance improvements provided in 5.1.0-WAS-0206LA.

    Details about the Tivoli Data Warehouse modeling changes for IBM 
    WebSphere Application Server versions 3.5, 4, and 5 can be found 
    in the IBM Tivoli Monitoring for Web Infrastructure: WebSphere 
    Application Server, Version 5.1.2 Warehouse Enablement Pack, 
    Version 1.1.0.3 Implementation Guide.  This document is 
    available as part of the fix pack: 
      /tedw_apps_etl/fixpack_v1103/izy/doc/WAS512_for_TEDW.pdf
 

1.2 Function Added:
    None


1.3 Products Certified:
    IBM WebSphere Application Server version 5.1 has been certified, however this
    fix pack is not required for IBM WebSphere Application Server version 5.1 support.
    It can be managed with IBM Tivoli Monitoring for Web Infrastructure:
    WebSphere Application Server, version  5.1.2 or version 5.1.2 with fix pack 01 or
    fix pack 02.


1.4 Applications Supported: 
    All applications previously supported.


1.5 Platforms Supported: 
    All platforms previously supported in addition to the following platforms which 
    are being supported with this fix pack:
     Endpoint:
       - SUSE LINUX Enterprise Server version 8 (United Linux 1.0) for PowerPC 
         (iSeries and pSeries)
       - Red Hat Enterprise Linux AS 3.0 Update 1 for PowerPC (iSeries and pSeries)

 
1.6 Dependencies: 
    IBM Tivoli Monitoring for Web Infrastructure 5.1.2: WebSphere Application Server 

    IBM Tivoli Monitoring 
      IBM Tivoli Monitoring Version 5.1.1 Fix Pack 06 (5.1.1-ITM-FP06) -or-
      IBM Tivoli Monitoring Version 5.1.2 
    IBM Tivoli Monitoring Version 5.1.2 Limited Availability Patch 0006
      (5.1.2-ITM-0006LA) - IBM Tivoli Monitoring Warehouse Enablement Pack.
      This patch can be applied against IBM Tivoli Monitoring Version 5.1.1 Fix Pack 06
      or IBM Tivoli Monitoring Version 5.1.2.
    NOTE:  IBM Tivoli Monitoring Version 5.1.2 Limited Availability Patch 0006 also
      requires IBM Tivoli Monitoring Version 5.1.2 Limited Availability Patch 0003 and
      0004.
    IBM Tivoli Monitoring for Web Infrastructure 5.1.2: WebSphere Application Server 
      z/OS APAR OA06103

    If you are managing WebSphere Application Server on an endpoint running Linux on 
    PowerPC (iSeries or pSeries), the following products are required:
      - Tivoli Management Framework (TMF) 4.1.1 
      - IBM Tivoli Monitoring Component Services Version 5.1.1 Fix Pack 02 
        (5.1.1-ICS-FP02) or higher

    If you are using Tivoli Management Framework 4.1.1 the following patches
    may be needed:
      4.1.1-TMF-0003 - required if Tivoli Management Environment 4.1.1 was installed
      as a fresh install (and not upgraded).  The symptom is a 
      "FRW0G0040E Transaction..." error when trying to create a server object without
        this fix.
      4.1.1-TMF-0007 - required.  Installation of the fix pack fails
        when trying to create the policy region without this fix.


1.7 Fix packs superceded by this patch: 
    5.1.2-WAS-FP01

     
1.8 Patch Contents:
    - this README file
    - A tar image for this patch


########################################################################
# Section 2. Problems Fixed                                            #
########################################################################
2.1 Problems Fixed:
 Defect:     131651 - proxy Admin Status resource model is not updating status.

2.1.1 Problems Fixed (from 5.1.2-WAS-FP01):
                      
    APAR:      IY51267 - Provide common data modeling for IBM WebSphere Application 
               Server version 5 across Tivoli products.  
    Symptoms:  TDW logging of IBM WebSphere Application Server version 5 is not logged
               consistently across Tivoli products. 
    Additional Information: The modeling for IBM WebSphere Application Server versions 
               3.5 and 4 data will be changed back to be consistent with how that
               data was modeled in IBM Tivoli Monitoring for Web Infrastructure:
               WebSphere Application Server, versions 5.1.0 and 5.1.1. 


    APAR:      IY49528 - TDW performance improvements
    Symptoms:  Incorporate IBM Tivoli Monitoring for Web Infrastructure:
               WebSphere Application Server TDW performance improvements from 
               WAS PAC 5.1.0 limited availability patch (5.1.0-WAS-0206LA).

             
    APAR:      IY50223 - Allow proxy monitoring when WebSphere Application Server 
               version 4 on z/OS is installed in a non-default location.  
    Symptoms:  Discovery of WebSphere Application Server resources on z/OS fails
               when WebSphere Application Server is installed in a non-default 
               location.  This affects only the proxy monitoring.


    APAR:      IY53915 - Data provider encounters an error after upgrading
    Symptoms:  Resource models go into Error state and the data provider gets a 
               NoSuchMethodError if the ./LCFNEW/ITM/PACS directory contains an old 
               copy of DataCollectorFactory.jar.


    Defect:    123876 - Install of IBM Tivoli Monitoring for Web Infrastructure:
               WebSphere Application Server Web Enablement Pack fails for TDW 1.2
    Symptoms:  Install on TDW 1.2 fails when the code tries to delete from the RPI 
               tables which do not exist in TDW 1.2.


    Defect:    128261 - Use the IBM Tivoli Monitoring DMXProcess ILT
    Symptoms:  Update the Resource Use resource model to use IBM Tivoli Monitoring
               (ITM) DMXProcess ILT as shipped in ITM 5.1.1 fix pack 6.


    Defect     124243 - EJB_11 and EJB_12 avgMethodCPUTime mean, total, and count are 
               incorrect for proxy systems.
    Symptoms:  EJB_11 and EJB_12 avgMethodCPUTime mean, total, and count are swapped 
               with those values for avgMethodRt mean, total, and count.
        

    Defect:    110469 - IZY WEP has the AVA code in upper case in the step name 
               parameter.   
    Symptoms:  The process parameters were updated to the proper case to 
               ensure portability in case-sensitive environments.     
    
  
    Defect:    128537 - Deployment manager discovery can assign incorrect SOAP ports 
               for servers.
    Symptoms:  If more than one application server is named the same within a cell but 
               on different nodes and are configured to use different SOAP ports, then 
               discovery would assign the same port for each of the servers.
                

    Defect:	   129959 - Performance enhancements for IZY Warehouse Enablement Pack.
    Symptoms:  The pruning step deletes cause performance problems.

2.2 Files replaced or added by this fix pack:
       # generic_unix 
       TME/WSAPPSVR/512WAS02.init
       TME/WSAPPSVR/itmwas_mn_update_ep.init
       TME/WSAPPSVR/itmwas_tool_dep.sh
       TME/WSAPPSVR/itmwas_tool_dep_fp2.sh
       # dm resource models
       TME/WSAPPSVR/Rm/WebSphereAS_ApplicationServerStatus_10.tar
       TME/WSAPPSVR/Rm/WebSphereAS_AppServerResourceUse_12.tar
       TME/WSAPPSVR/Rm/WebSphereAS_AdminServerStatus_10.tar
       TME/WSAPPSVR/Rm/WebSphereAS_DBPools_10.tar
       TME/WSAPPSVR/Rm/WebSphereAS_DynamicCache_12.tar
       TME/WSAPPSVR/Rm/WebSphereAS_EJBs_10.tar
       TME/WSAPPSVR/Rm/WebSphereAS_HTTP_Sessions_10.tar
       TME/WSAPPSVR/Rm/WebSphereAS_J2CConnector_12.tar
       TME/WSAPPSVR/Rm/WebSphereAS_JVMRuntime_10.tar
       TME/WSAPPSVR/Rm/WebSphereAS_NodeAgentStatus_12.tar
       TME/WSAPPSVR/Rm/WebSphereAS_ThreadPool_10.tar
       TME/WSAPPSVR/Rm/WebSphereAS_Transactions_10.tar
       TME/WSAPPSVR/Rm/WebSphereAS_WebApps_10.tar
       # utility tasks
       TME/WSAPPSVR/tasks/itmwas_disable_probe_resources.sh
       TME/WSAPPSVR/tasks/itmwas_enable_probe_resources.sh
       # task library tasks
       TME/WSAPPSVR/tasks/itmwas_uninstall_prod.sh
       TME/WSAPPSVR/tasks/itmwas_util_functions.sh
       TME/WSAPPSVR/tasks/itmwas_zosutils.sh
       # msg_cat  
       C/itmwas_sh.cat
       # lcf_bundle.40:
       bin/linux-ppc/TME/WSAPPSVR/utils/wsepmprobe
       bin/linux-ppc/TME/WSAPPSVR/utils/wseputil
       bin/linux-ppc/TME/WSAPPSVR/WebSphereObject
       bin/linux-ppc/TME/WSAPPSVR/WSAdministrationServer
       bin/linux-ppc/TME/WSAPPSVR/WSApplicationServer
       bin/linux-ppc/TME/WSAPPSVR/IWebSphereObject
       bin/linux-ppc/TME/WSAPPSVR/IWSApplicationServer
       bin/linux-ppc/TME/WSAPPSVR/IWSNodeAgent
       bin/linux-ppc/TME/WSAPPSVR/IWSDeploymentManager
       bin/generic_unix/TME/WSAPPSVR/tasks/itmwas_util_functions.sh
       bin/generic_unix/TME/WSAPPSVR/DataCollectorFactory.jar
       bin/generic_unix/TME/WSAPPSVR/utils/discovery/itmwasdiscovery.jar
       bin/generic_unix/TME/WSAPPSVR/tasks/itmwas_zosutils.sh
       msg_cat/C/itmwas_sh.cat
       tedw_apps_etl/fixpack_v1103 (new directory of files)
       tedw_apps_etl/fixpack_v1103/izy/misc/tools/izy_v110_migration.bat
       tedw_apps_etl/fixpack_v1103/izy/misc/tools/izy_v110_migration.sql
       WORKBENCH/ALL/WebSphereAS_*.jrm
       WORKBENCH/ALL/itmwas.jar
       WORKBENCH/ALL/iltCode.jar


########################################################################
# Section 3. Installation notes                                        #
########################################################################

3.1 Applying the patch:
    1)  Extract the patch:
    
        Extract the contents into a scratch directory. For the purpose
        of these instructions, assume that the symbol $patch (%patch% on
        Windows) points to this directory.

        On a Unix system:

        # cd $patch
        # tar -xvf 5.1.2-WAS-FP02.tar

        On a Windows system:


        > %SystemRoot%\system32\drivers\etc\Tivoli\setup_env
        > X:
          where 'X' is drive letter where %patch% is found
        > cd %patch%
        > tar -xvf 5.1.2-WAS-FP02.tar

        NOTE:  If you are extracting the tar image on a Windows
        system, you will find an executable for tar in the Tivoli 
        Management Environment installation on Windows under 
        bin/w32-ix86/tools/tar.exe.

    2)  If this patch is to be installed using Software Installation 
        Service (SIS), follow these instructions. If not, skip to 
        step 3 below.

        NOTE: Software Installation Service can install Tivoli products 
              on any hardware platform supported by Tivoli, but there are some
              hardware platforms on which Software Installation 
              Service cannot be run. Please check your Software Installation 
              Service User's Manual for the list of platforms
              on which Software Installation Service can be run.
 
        NOTE: You must have the install_product and super authorization
              roles to successfully install this patch.

        a)  From the Tivoli Desktop, pull down
            Desktop --> Install --> Software Installation Service.
        b)  Software Installation Service will initialize, and bring up 
            the Get Installation Password Dialog.  Enter your Installation Password.
        c)  Click the Install Button on the dialog which contains
            the Tivoli image.
        d)  Click the Select Product Button on the Install Spreadsheet
            Dialog.
        e)  Click the Import Product Button on the Select Product
            Dialog.
        f)  Locate the media to 5.1.2-WAS-FP02 using the file browser, and
            select the PATCHES.LST file by double-clicking it.
        g)  Select 5.1.2-WAS-FP02  in the Import Product Dialog, and click
            the Import Button.
        h)  When the import is complete, click the OK Button on the
            Global Progress Dialog.
        i)  Select 5.1.2-WAS-FP02 in the Select Product Dialog, if it is
            not already selected, and click the OK Button.
        j)  Now click the Select Machine Button on the Install
            Spreadsheet Dialog.
        k)  Select the machine(s) you would like to install 5.1.2-WAS-FP02 
            to, and click the OK Button.
        l)  Click the appropriate cell(s) in the Install Spreadsheet
            Dialog. (NOTE: This should yield an "X" in the cell(s)
            for the machines where you want to install 5.1.2-WAS-FP02 ).
        m)  Click the Install Button.
        n)  Select the install algorithm you want to use on the
            Installation Algorithm Dialog, and click OK.
        o)  Software Installation Service will perform the installation(s) 
            you designated in the Install Spreadsheet Dialog.
        p)  Installation is complete. Check the Additional
            Installation Instructions section below.

    3)  You can use the following steps to install the patch using the original
        Tivoli desktop install mechanism. If not, skip to step 4 below.
        NOTE: You must have the install_product and super authorization
        roles to successfully install this patch.

        a)  From the Tivoli Desktop, pull down
            Desktop --> Install --> Install Patch.
        b)  Press the "Select Media..." button to display the "File
            Browser" dialog.
        c)  Enter the path ($patch or %patch%) to the directory containing the patch,
            file 512WAS02.IND, in the "Path Name:" field.
        d)  Press the "Set Media & Close" button to return to the
            "Install Patch" dialog.
        e)  The patch install list now contains the name of the patch.
            Select the patch by clicking on it.
        f)  Select the clients to install this patch on. This should be the TME
            server and on each managed node where the product is installed.
        g)  Press the "Install" button to install the patch.

    4)  The patch can also be installed using the wpatch command line utility.
        Refer to the Tivoli Management Framework Reference Manual or
        Tivoli Enterprise Console Installation Guide.


3.2 Additional installation instructions - Tivoli Data Warehouse (from 5.1.2-WAS-FP01)

     The IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server, 
     Version 5.1.2 Warehouse Enablement Pack, Version 1.1.0.3 Implementation Guide
     contains information about installing and configuring the warehouse enablement 
     pack for this fix pack.  The WEP updates for this fix pack are located on the
     installation media under tedw_apps_etl/fixpack_v1103.

     Note:  When placing the IZY_m10_Fact_Process in production mode or running the 
     steps manually in test mode, ensure the IZY_m10_s010_Fact step is first step in 
     the sequence and the IZY_m10_Cleanup_Process is the last step.  

     If you have IBM Tivoli Service Level Advisor (ITSLA), the Implementation Guide 
     section 3.9, "Migrating from a previous release of the warehouse pack", should 
     be consulted for details about a migration script that must be run if data had 
     previously been collected in the warehouse with IBM Tivoli Monitoring for Web 
     Infrastructure: WebSphere Application Server version 5.1.0 or 5.1.1 and 
     consumed by IBM Tivoli Service Level Advisor.


3.3 Additional installation instructions - Resource Models
         
     1) Once the patch has been installed, any IBM Tivoli Monitoring for Web 
        Infrastructure 5.1.2 - WebSphere Application Server resource models
        previously distributed should be redistributed to pick up the changes.

        Before redistributing to Windows endpoints, shut down the IBM Tivoli
        Monitoring engine.  To stop the engine, use the following command:
           "wdmcmd -stop -e <endpoint label>"
           
        It is not necessary to shut down the engine on Unix endpoints running
        WebSphere resource models. 

     2) If IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server 
        version 5.1.2 was upgraded from a previous version, you will need to stop
        and restart the IBM Tivoli Monitoring engine for each of the endpoints where
        objects had been previously discovered.  One of the jar files has changed, 
        and the updated version will not get used until the engine is restarted.


########################################################################
# Section 4. Additional Notes                                          #
########################################################################

4.1 Additional Notes: 

     It is recommended (required if running the z/OS proxy) when running the 
     DMLinkJre task, to link to the version of Java that is shipped with 
     IBM Tivoli Monitoring.  Problems can occur if you link to the version 
     that IBM WebSphere Application Server ships with, particularly
     version 5.1, since that level of the Java Runtime Environment (1.4)
     is not supported by IBM Tivoli Monitoring at this time.
    
     The sample resource models shipped with this fix pack have been built with
     Resource Model Builder version 1.1.2.  The files have an extension of .jrm 
     and are provided in the 5.1.2-WAS-FP02.tar file in the WORKBENCH subdirectory 
     where you untarred that file. 

     If a custom resource model has been created with the workbench tool, the
     resource models must be rebuilt with Resource Model Builder 1.1.2 using the
     new versions of these jar files:
       - iltCode.jar
       - itmwas.jar       
     These files are provided in the 5.1.2-WAS-FP02.tar file and can be 
     found in WORKBENCH subdirectory where you untarred that file.  
     Any custom package (tar file) must be built and reloaded into the Tivoli 
     Management Region (TMR) by using the following command:
       wdmrm -add <resource-model-tar-file>

########################################################################
# Section 5. Limitations and Known Problems                            #
########################################################################

5.1 Limitations and Workarounds:
    The Resource Use resource model is not supported for Linux PowerPC (linux-ppc)
    endpoints.
 
    If managing IBM WebSphere Application Server on a Red Hat Enterprise Linux 
    AS 3.0 Update 1 for PowerPC endpoint, the LD_ASSUME_KERNEL environment variable 
    needs to be set for several of the event adapter tasks.  If the environment 
    variable is not set, the tasks will report that the adapter is not running even 
    when it is running and operational.  The tasks affected are the 
    Configure_WebSphere_TEC_Adapter, Start_WebSphere_TEC_Adapter, and 
    Stop_WebSphere_TEC_Adapter tasks.
    

5.2 Known Problems (from 5.1.2-WAS-FP01):
   Defect 168452 - An error may occur in the trace_WebSphereAS_Ilt.log on the 
   getParameter method.  A ClassCastException: java.lang.Long may be displayed.  This 
   error is not a problem and the ILT will continue to run accurately.

   Defect 127872 - Duplicate Summary report names are displayed on Crystal reports.

   Defect 128796 - Y-axis header overlaps scale entries on Crystal reports.

   Defect 132159 IZY_m10_Cleanup_Process is incorrectly named.   It should be named 
   so that it executes last in the sequence of steps. See Additional installation 
   instructions - Tivoli Data Warehouse.

   Defect 167391 - TDW parameters can become corrupted after uninstalling the WEP.
   This is a problem with the iwh2imp tool, which is part of the Tivoli Data Warehouse
   product.