IBM Tivoli OMEGAMON XE for WebSphere Application Server Interim Fix 7 Readme

(C) Copyright International Business Machines(R), 2005. All rights reserved.

Patch: 1.3.0-TIV-OXEWAS-IF0007



CONTENTS
---------
1.0 ABOUT THIS FIX PACK
  1.1 Supported operating systems
  1.2 Dependencies
  1.3 Fix Pack Contents
2.0 PROBLEMS FIXED
3.0 APPLYING THE FIX PACK
4.0 APPLYING THE FIX PACK ON TEMS/TEPS
5.0 KNOWN DEFECTS
6.0 WEBSPHERE APPLICATION SERVER V6 TOLERATION SUPPORT
7.0 STATIC CONFIGURATION ANALYZER



1.0 ABOUT THIS FIX PACK
-----------------------
This is a cumulative interim fix pack for IBM Tivoli OMEGAMON XE for WebSphere
Application Server v130.  


  1.1 Supported operating systems

    The following operating systems are supported by this fix pack:

    WEAX4007 - AIX 4.3.3 and later
    WEHX4007 - HP-UX 11.0
    WELI4007 - LINUX INTEL 2.4
    WELS4007 - LINUX S390 2.2 and later
    WESL4007 - SOLARIS 2.8 and later
    WEWS4007 - Microsoft Windows


  1.2 Dependencies

    This fix pack has no dependencies.


  1.3 Fix Pack Contents

    This fix pack contains the following files:

    1.3.0-TIV-OXEWAS-IF0006.README
    Patch 1.3.0-TIV-OXEWAS-IF0006 includes:

    - 1.3.0-TIV-OXEWAS-IF0006.README

    - weax4007.tar.Z  (AIX 4.3.3 and later)
           4190   Apr 05 2006   classes/Candle_WA_Enabler.class
          38203   Apr 06 2006   classes/WasAnalyzer.jar
          99109   Apr 06 2006   classes/kweconfiganalyzer.jar
         255494   Apr 07 2006   classes/kwepmiclient.jar
        1380292   Apr 05 2006   classes/kwewa.jar
            853   Dec 22 2006   aix433/we/bin/analyzekwe.sh
         670320   Apr 05 2006   aix433/we/bin/KWEMSGS
        6215576   Apr 07 2006   aix433/we/bin/kweagent
           4190   Apr 05 2006   aix433/we/classes/Candle_WA_Enabler.class
          38203   Apr 06 2006   aix433/we/classes/WasAnalyzer.jar
          99109   Apr 06 2006   aix433/we/classes/kweconfiganalyzer.jar
         255494   Apr 07 2006   aix433/we/classes/kwepmiclient.jar
        1380292   Apr 05 2006   aix433/we/classes/kwewa.jar
          90827   Apr 28 2006   aix433/we/lib/libkweprof.a
          86692   Apr 06 2006   aix433/we/lib/libkweprof.a.4.3.3
         355942   Mar 21 2006   aix433/we/tables/ATTRLIB/kwe.atr

    - wehx4007.tar.Z  (HP-UX 11.0)
           4190   Apr 05 2006   classes/Candle_WA_Enabler.class
          38203   Apr 06 2006   classes/WasAnalyzer.jar
          99109   Apr 06 2006   classes/kweconfiganalyzer.jar
         255494   Apr 07 2006   classes/kwepmiclient.jar
        1380292   Apr 05 2006   classes/kwewa.jar
            853   Dec 22 2006   hp11/we/bin/analyzekwe.sh
        1319920   Apr 06 2006   hp11/we/bin/KWEMSGS
        6173176   Apr 07 2006   hp11/we/bin/kweagent
           4190   Apr 05 2006   hp11/we/classes/Candle_WA_Enabler.class
          38203   Apr 06 2006   hp11/we/classes/WasAnalyzer.jar
          99109   Apr 06 2006   hp11/we/classes/kweconfiganalyzer.jar
         255494   Apr 07 2006   hp11/we/classes/kwepmiclient.jar
        1380292   Apr 05 2006   hp11/we/classes/kwewa.jar
         216552   Apr 06 2006   hp11/we/lib/libkweprof.sl
         355942   Mar 21 2006   hp11/we/tables/ATTRLIB/kwe.atr

    - weli4007.tar.Z  (LINUX INTEL 2.4)
           4190   Apr 05 2006   classes/Candle_WA_Enabler.class
          38203   Apr 06 2006   classes/WasAnalyzer.jar
          99109   Apr 06 2006   classes/kweconfiganalyzer.jar
         255494   Apr 07 2006   classes/kwepmiclient.jar
        1380292   Apr 05 2006   classes/kwewa.jar
            853   Dec 22 2006   li6243/we/bin/analyzekwe.sh
         670320   Apr 06 2006   li6243/we/bin/KWEMSGS
        4261996   Apr 07 2006   li6243/we/bin/kweagent
           4190   Apr 05 2006   li6243/we/classes/Candle_WA_Enabler.class
          38203   Apr 06 2006   li6243/we/classes/WasAnalyzer.jar
          99109   Apr 06 2006   li6243/we/classes/kweconfiganalyzer.jar
         255494   Apr 07 2006   li6243/we/classes/kwepmiclient.jar
        1380292   Apr 05 2006   li6243/we/classes/kwewa.jar
         216775   Apr 05 2006   li6243/we/lib/libkweprof.so
         355942   Mar 21 2006   li6243/we/tables/ATTRLIB/kwe.atr

    - wels4007.tar.Z  (LINUX S390 2.2 and later)
           4190   Apr 05 2006   classes/Candle_WA_Enabler.class
          38203   Apr 06 2006   classes/WasAnalyzer.jar
          99109   Apr 06 2006   classes/kweconfiganalyzer.jar
         255494   Apr 07 2006   classes/kwepmiclient.jar
        1380292   Apr 05 2006   classes/kwewa.jar
            853   Dec 22 2006   ls3223/we/bin/analyzekwe.sh
         670320   Apr 06 2006   ls3223/we/bin/KWEMSGS
        5041092   Apr 07 2006   ls3223/we/bin/kweagent
           4190   Apr 05 2006   ls3223/we/classes/Candle_WA_Enabler.class
          38203   Apr 06 2006   ls3223/we/classes/WasAnalyzer.jar
          99109   Apr 06 2006   ls3223/we/classes/kweconfiganalyzer.jar
         255494   Apr 07 2006   ls3223/we/classes/kwepmiclient.jar
        1380292   Apr 05 2006   ls3223/we/classes/kwewa.jar
         282174   Apr 05 2006   ls3223/we/lib/libkweprof.so
         355942   Mar 21 2006   ls3223/we/tables/ATTRLIB/kwe.atr
            853   Dec 22 2006   ls3226/we/bin/analyzekwe.sh
         670320   Apr 06 2006   ls3226/we/bin/KWEMSGS
        5041092   Apr 07 2006   ls3226/we/bin/kweagent
           4190   Apr 05 2006   ls3226/we/classes/Candle_WA_Enabler.class
          38203   Apr 06 2006   ls3226/we/classes/WasAnalyzer.jar
           4190   Apr 05 2006   ls3226/we/classes/candle_wa_enabler.class
          99109   Apr 06 2006   ls3226/we/classes/kweconfiganalyzer.jar
         255494   Apr 07 2006   ls3226/we/classes/kwepmiclient.jar
        1380292   Apr 05 2006   ls3226/we/classes/kwewa.jar
          38203   Apr 06 2006   ls3226/we/classes/wasanalyzer.jar
         282174   Apr 05 2006   ls3226/we/lib/libkweprof.so
         355942   Mar 21 2006   ls3226/we/tables/ATTRLIB/kwe.atr

    - wesl4007.tar.Z  (SOLARIS 2.8 and later)
           4190   Apr 05 2006   classes/Candle_WA_Enabler.class
          38203   Apr 06 2006   classes/WasAnalyzer.jar
          99109   Apr 06 2006   classes/kweconfiganalyzer.jar
         255494   Apr 07 2006   classes/kwepmiclient.jar
        1380292   Apr 05 2006   classes/kwewa.jar
            853   Dec 22 2006   sol283/we/bin/analyzekwe.sh
         670320   Apr 05 2006   sol283/we/bin/KWEMSGS
        9846792   Apr 07 2006   sol283/we/bin/kweagent
           4190   Apr 05 2006   sol283/we/classes/Candle_WA_Enabler.class
          38203   Apr 06 2006   sol283/we/classes/WasAnalyzer.jar
          99109   Apr 06 2006   sol283/we/classes/kweconfiganalyzer.jar
         255494   Apr 07 2006   sol283/we/classes/kwepmiclient.jar
        1380292   Apr 05 2006   sol283/we/classes/kwewa.jar
         385524   Apr 05 2006   sol283/we/lib/libkweprof.so
         355942   Mar 21 2006   sol283/we/tables/ATTRLIB/kwe.atr

    - wews4007.exe  (Microsoft Windows)
           4190   Apr  5 2006   CMA/Candle_WA_Enabler.class
         670320   Apr  5 2006   CMA/KWEMSGS
          38203   Apr  6 2006   CMA/WasAnalyzer.jar
           1171   Dec  2 2006   CMA/analyzekwe.bat
        9846792   Apr  7 2006   CMA/kweagent.exe
          28738   Apr  5 2006   CMA/kwecgwav.exe
          99109   Apr  6 2006   CMA/kweconfiganalyzer.jar
          24640   Apr  5 2006   CMA/kwekey.dll
         255494   Apr  7 2006   CMA/kwepmiclient.jar
          32768   Apr  5 2006   CMA/kweprof.dll
        1380292   Apr  5 2006   CMA/kwewa.jar
         445405   Mar 21 2006   CNPS/dockwe
         377970   Mar 21 2006   CNPS/CMSATR/kwe.atr
         388132   Mar 21 2006   CNPS/RKDSCATL/kwe.cat



2.0 PROBLEMS FIXED
------------------
The following APARS are addressed in this fix pack

  IY84452   Packaging error in 1.3.0-TIV-OXEWAS-IF0006

The following APARS are addressed in previous fix packs

  IY83710   PmiClient.getInstrumentationLevel deprecated in WAS6
  IY78316   KWE0123E Reason: "Unable to open verbose:gc log file" 
  IY79817   KWE0072E Take Action command SETIL fails 
  IY79989   NullPointerException instrumenting xsltc classes 
  IY80717   KWE0115W KWE0002E java.lang.NullPointerException 
  IY80819   Incorrout Average Session Lifetime and Lifetime of Sessions 
  IY81192   WebSphere 5.1 does not start with Omegamon Classloader 
  IY81414   Incorrout node agent status 
  IY81438   Abend when DefaultExclude="Yes" 
  IY82154   javacore after applying PK20342 
  IY82871   Resolve WAS environmental variables properly 
  IY83276   Quality and Serviceability Improvements 
  IY83619   WASInstanceRoot missing in kwe.xml 
  IY83642   OutOfMemoryExceptions in WAS 
  IY79214   org.eclipse.emf.ecore.xmi.PackageNotFoundException in KWERAS1_Java.log 
  IY79216   CTG9630E CTG connection failed. DB2 connection failed. 
  IY76775   WebSphere 6.0 Express edition support 
  IY76707   Memory leak in Heap Analysis 
  IY75782   Thread deadlock instrumenting for lock analysis 
  IY76710   org.apache.bcel.generic.ClassGenException: Branch target offset too large 
  IY77028   Java security incorrectly initialized 
  IY78119   Rename BCEL packages to org.apache.kwe.bcel 
  IY78120   MSGKWEWA067I Internal trace file opened when InternalTrace="false" 
  IY78313   Memory leak in kweagent 
  IY78314   Slow response time in workspaces 
  IY78315   MSGKWE0123E Unable to open verbose:gc log file 
  137304    JmsPackage missing in WebSphere Application Server v6 
  IY73461   Web servers not supported 
  IY73462   Garbage Collection data missing in WebSphere Application Server v6 
  IY73625   Exception java.lang.NoSuchMethodError in method sqlNamingManagerGetObjectInstanceEntry 
  IY73380   Deadlock in method MessageDigest.getInstance 
  OA12588   Missing Workloads invoking methods doPost and doGet 
  IY72494   Percent of CPU Used missing on AIX 
  IY74643   Servlet data missing from All Workloads Workspace
  IY74644   Optimize performance using JMX notifications 
  136809    Global security on WebSphere Application Server V6 not supported 
  137304    Missing XMI packages on WebSphere Application Server V6 
  137391    Improve messages 
  IY70232   Error calculating historical rates 
  IY70577   Abend reading non-WAS5 Advanded Format messages that contain "source=" 
  IY71925   Class instrumentation sorts class fields 
  IY71926   Avoid unecessary class instrumentation 
  IY71927   High memory usage 
  IY71928   Invalid localtime using Europe's DST rules 
  Internal  Excessive heap consumption used by the workload analysis feature 
  Internal  WebSphere Application Server V6 not supported 
  IY67393   Java excepcion in BCEL during instrumentation 
  IY68102   Clustered environments not supported 
  OA09946   wsinstance not supported 
  OA10880   Incorrect timestamp in Linux for zSeries 
  OA10421   Wrong PMI classpath in WebSphere Application Server V5 with security on 
  OA10537   Message PMIJMXBRIDGEL NO PMIMODULE FOUND in SystemOut.log 
  OA10850   Deadlock in class RememberedDataSource 

 

3.0 APPLYING THE FIX PACK
-------------------------
The following sections provide information about installing this fix pack.

  1. In the list of files in section "1.3 Fix Pack Contents," identify
     the fix pack file that corresponds to the target operating system.

  2. Copy the fix pack file you identified in Step 1 to the INSTALL_DIR
     directory.

  3. Stop IBM Tivoli OMEGAMON XE for WebSphere Application Server.

  4. Stop all monitored application servers.

  5. Make backup copies of all of the files listed under the appropriate
     operating system in section "1.3 Fix Pack Contents."

  6. At a shell prompt, run the following command from the INSTALL_DIR
     directory:

    - For Unix system:
      uncompress -c <FIXPACK> | tar xvf - 

    - For Windows system:
      <FIXPACK> -d -o -in CMA\*

    where <FIXPACK> is the name of the file identified in Step 1.

  7. Run the class loader setup script:

    - For Unix system:
      <INSTALL_DIR>/bin/setupCandleWAEnabler.sh

    - For Windows system:
      <INSTALL_DIR>/CMA/setupCandleWAEnabler.bat

    where <INSTALL_DIR> is the IBM Tivoli OMEGAMON installation directory

    For more detail, See Launching the Class Loader Script for Workload Analysis 
    in the User’s Guide.

  8. Restart the application servers stopped in Step 4.

  9. Restart IBM Tivoli OMEGAMON XE for WebSphere Application Server.


4.0 APPLYING THE FIX PACK ON TEMS/TEPS
--------------------------------------
The following sections provide information about installing this fix pack on 
TEMS/TEPS.

  1. Copy wews4007.exe to the TEPS_INSTALL_DIR directory.

  2. At a shell prompt, run the following command from the TEPS_INSTALL_DIR
     directory:

     wews4007 -d -o -in CNPS\*

  3. FTP the new attribute file and catalog file to the TEMS.

     From the same shell prompt, open a FTP ASCII session to the TEMS host and 
     issue the following commands:

      - For Unix systems:
        cd <TEMS_INSTALL_DIR>/tables/<TEMS_NAME>
        put CNPS\CMSATR\kwe.atr ATTRLIB/kwe.atr
        put CNPS\RKDSCATL\kwe.cat RKDSCATL/kwe.cat

      - For Windows systems:
        cd <TEMS_INSTALL_DIR>\CMS
        put CNPS\CMSATR\kwe.atr ATTRLIB\kwe.atr
        put CNPS\RKDSCATL\kwe.cat RKDSCATL\kwe.cat

      - For z/OS systems:
        cd 'hilev.TKANDATV'
        put CNPS\CMSATR\kwe.atr kweatr
        put CNPS\RKDSCATL\kwe.cat kwecat

     Exit the FTP session.

  4. On z/OS only, copy 'hilev.TKANDATV' to 'hilev.rte.RKANDATV'.

  5. Restart TEMS and TEPS.



5.0 KNOWN DEFECTS
-----------------
Historical data collected prior to applying this fixpack will be displayed
inaccurately for the following columns:

- Average Session Lifetime in Application Server workspace
- Lifetime of Sessions in Servlet Session workspace



6.0 WEBSPHERE APPLICATION SERVER V6 TOLERATION SUPPORT 
------------------------------------------------------
The following sections provide information for monitoring WebSphere Application
Server V6.
 
  1. This fixpack monitors all the existing features that IBM Tivoli Omegamon XE
     for WebSphere Application Server version 130 supports for WebSphere
     Application Server V6.  Newly introduced features are not supported.
    
  2. A separate agent instance is required to monitor each profile in a 
     stand-alone configuration.  In a Network Deployment configuration, the 
     deployment manager profile does not require an instance.  Only the profiles
     whose nodes are added to the deployment manager require an instance.
    
     The agent's configuration file (kwe.xml) must be setup as follows:
    
     - The parameter WASAppServerRoot indicates the directory path name to the
       location where WebSphere Application Server product is installed.

     - A new parameter called WASInstanceRoot indicates the directory path name
       to the the profile to be monitored by the agent.
      
     For example:

     <KWEAGENT
        AgentID="MyFirstProfile"
        ...
        WASAppServerRoot="/opt/websphere/AppServer"
        WASInstanceRoot="/opt/websphere/AppServer/profiles/MyFirstProfile"
        ...
      >
      </KWEAGENT>
      
  3. The interpretation of the PMI instrumentation levels are limited to the
     instrumentation levels supported in previous WebSphere Application Server
     versions.  The following mapping relates the new statistic sets to previous
     instrumentation levels:
    
     WAS 6.0             pre-WAS 6
     Statistic Sets      Instrumentation Levels
     -----------------------------------------------------
     None                None
     Basic               Low
     Extended            Medium
     All                 High
     Custom              Max
        
    - During "Take Action" commands, selecting "Max" will select the "All" 
      statistic set.
    - Selecting a level for an individual PMI module or CNP data row, will change
      the overall statistic set to "Custom" and will enable parameters specific 
      to the selected statistic set.
    - It is recommended that the Custom statistic set and enabling desired
      parameters be done through the Administrative Console.


          
7.0 STATIC CONFIGURATION ANALYZER
---------------------------------    

This tool analyzes an agent configuration file (kwe.xml) and the WAS environment it will 
be monitoring. It will read and further analyze the instrumentation file that is configured 
for each WAS instance and provide advisory messages (errors, warnings) as well as 
performance improvement messages based on the Best Practices document 
(http://www-1.ibm.com/support/docview.wss?uid=swg21209953).  The analysis messages will be 
written to a report file.

This tool supports WebSphere Application Server versions 5.0.x, 5.1.x and 6.0.x.  Versions
4.0.x and 3.5.x are NOT supported.

  1. Supported Features

    (i)   Analyzes the agent configuration file (kwe.xml) for syntax and semantic errors, 
          warnings.
    (ii)  Analyzes the WAS environment that is pointed to by the agent configuration file.
    (iii) Analyzes the instrumentation file (kweiuser.xml) selected for workload analysis 
          in the monitored WAS instances.  It provides performance improvement messages based 
          on the Best Practices document.
    (iv)  Provides information about PMI and workload analysis workspaces regarding which 
          ones will contain data.
    (v)   Checks for global security and tests whether the credentials provided will be 
          sufficient for the agent to make the connection.

  2. Requirements

    (i) JRE version 1.2 and above.  
        If this JRE is not available in the default environment, edit the analyzekwe.sh (or .bat)
        file and point the java_home (or JAVA_HOME in .bat file) to point to the Java directory
        contained in the WebSphere installation directory.
        
  3. Installation
  
     This tool will be automatically installed when the fixpack is installed. 
     
     The configuration analyzer files that will be installed are:
     
     - On Windows system:
         <INSTALL_DIR>/CMA:
           kweconfiganalyzer.jar
           WasAnalyzer.jar
           analyzekwe.bat
        
     - On Unix system:
         <INSTALL_DIR>/classes:
           kweconfiganalzyer.jar
           WasAnalyzer.jar
        
         <INSTALL_DIR>/bin:
           analyzekwe.sh
       
     where <INSTALL_DIR> is the IBM Tivoli OMEGAMON installation directory
       
  4. Usage
   
     - On Windows system:
        - Change directory to <INSTALL_DIR>/CMA directory.
        - Execute:
          analyzekwe <location of the agent configuration file (kwe.xml)>
          e.g:  analyzekwe kwe.xml
       
     - On Unix system:
        - Change directory to <INSTALL_DIR>/bin directory.
        - Execute:
          ./analyzekwe.sh <location of the agent configuration file>
          e.g.: ./analyzekwe.sh ../config/kwe.xml
          
     where <INSTALL_DIR> is the IBM Tivoli OMEGAMON installation directory
     
  5. Report
  
      The configuration analyzer report will be generated in the logs directory:
      
      - On Windows system, it is usually <INSTALL_DIR>/CMA/Logs
      - On Unix system, it is usually <INSTALL_DIR>/logs
      
      where <INSTALL_DIR> is the IBM Tivoli OMEGAMON installation directory.
      
      The report file name will have a ".rpt" extension with the agent configuration file's
      full name (with extension) as the file name.  For example, the report file for kwe.xml
      will be named "kwe_xml.rpt".
      
      The report lists the results of the analysis in seperate sections as follows:
        (i)   Agent configuration file (kwe.xml) analysis.
        (ii)  Analysis of the WAS installation directory as specified in th WASInstallRoot
              keyword of the agent configuration file.
        (iii) Analysis of Individual server instances contained in the WAS installation.
        (iv)  PMI analysis for each server.
        (v)   Workload analysis instrumentation file (kweiuser.xml) analysis,
              if the workload analysis is enabled.
      
         
  6. Limitations
   
     (i)  Only WebSphere Application Server versions 5.0.x, 5.1.x and 6.0.x are supported.
          Versions 4.0.x and 3.5.x are NOT supported.
     (ii) Under Windows, the tool does not currently check the registry for existing 
          WAS installation.  If the WASAppServerRoot is not specified in the agent configuration
          file (kwe.xml), the tool will flag it as an error. This will be corrected in a future 
          release of this tool.
     (ii) The tool analyzes only the static PMI data (since this is a static analyzer). Any
          runtime changes to the PMI levels will not be analyzed.


