IBM Application Performance Management 8.1.4.0 8.1.4.0-IBM-APM-WAS-AGENT-IF0004 Readme

IMPORTANT NOTE: To download this update, you must first login to IBM Fix Central. Once logged in, you may select from the individual download packages. When selecting fixes, ensure your download options are set to "Include requisites: Yes".
http://www.ibm.com/support/fixcentral/

Below is a list of components, platforms, and file names that apply to this Readme file.

General description
This is an interim fix for the Monitoring agent for WebSphere Applications provided with IBM Cloud Application Performance Management family of products, Version 8.1.4.0.
It includes fixes for the WebSphere Applications agent and upgrades the agent from version 07.30.14.00, 07.30.14.01,07.30.14.02 or 07.30.14.03 to 07.30.14.04.

Platforms and prerequisites
The Monitoring Agent for WebSphere Applications is supported on the platforms documented here.

The interim fix for the WebSphere Applications agent is intended to be applied to the Monitoring Agent for WebSphere Applications version 07.30.14.00,07.30.14.01,07.30.14.02 or 07.30.14.03 which is provided with:

IBM Cloud Application Performance Monitoring Base Private, Version 8.1.4.0
IBM Cloud Application Performance Monitoring Advanced Private, Version 8.1.4.0.

IBM Cloud Application Performance Monitoring Base, Version 8.1.4.0
IBM Cloud Application Performance Monitoring Advanced, Version 8.1.4.0.

None

None

Prior to installation

The WebSphere Applications agent version 07.30.14.00 or 07.30.14.01 or 07.30.14.02 or 07.30.14.03 must be installed and running before applying the agent interim fix.

Installing

Installing the agent interim fix

1. Download the patch bundle from Fix Central for each OS type where your agent is installed:
   
   • If the agent is installed on AIX, download 8.1.4.0-IBM-APM-WAS-AGENT-AIX-IF0004.tar
     
   • If the agent is installed on Linux x86_64, download 8.1.4.0-IBM-APM-WAS-AGENT-XLINUX-IF0004.tar
     
   • If the agent is installed on Linux for IBM Power Little Endian, download 8.1.4.0-IBM-APM-WAS-AGENT-PLINUXLE-IF0004.tar
     
   • If the agent is installed on Linux s390x, download 8.1.4.0-IBM-APM-WAS-AGENT-ZLINUX-IF0004.tar
     
   • If the agent is installed on Windows, download 8.1.4.0-IBM-APM-WAS-AGENT-WIN64-IF0004.zip
     
   
   
2. If you are installing the patch on AIX as a non-root user, you must clear unused shared libraries from the kernel and library memory before you install the patch by following these steps:
   
   
   • Stop the WebSphere Applications agent
     
   • Login as root, and run the slibclean command
     
   • Login as the non-root user who installed the agent and continue with the patch installation
     
   
   
3. Unpack the patch bundle on each computer system where the agent is already installed by using the tar utility on Linux/AIX or unzip on Windows.
   
   e.g.
   
   tar -xf 8.1.4.0-IBM-APM-WAS-AGENT-XLINUX-IF0004.tar
   
   
4. Enter the created directory
   
   
5. Run the apmpatch.sh/bat tool as the same user who installed the agent:
   
   Linux/AIX:
   ./apmpatch.sh <APM-AGENT-HOME>
   
   Windows:
   ./apmpatch.bat <APM-AGENT-HOME>
   
   where the <APM-AGENT-HOME> value specifies the directory where the agent is installed. This value is a required parameter for Windows. However, for Linux and AIX, it only needs to be provided if the agent is installed in a non-default directory.
   
   
6. Agent data collector configuration.
   
   
   • If data collector is already configured then after patch is installed, run the following tool to migrate the configuration/runtime of the existing WebSphere Applications data collector to the updated data collector.
     
     Linux/AIX:
     <APM-AGENT-HOME>/yndchome/ 7.3.0.14.04/bin/migrate.sh
     
     Windows:
     <APM-AGENT-HOME>\dchome\7.3.0.14.04\bin\migrate
     
     After the migration is done, restart the WebSphere application server.
     
     Note: The migration script will ask you to input required properties/settings. See this link for more details on the script prompts.
     
     
   • If the WAS data collector is not configured, copy the offering.id file from the previous data collector home directory to the current data collector home directory.
     
     Linux/AIX:
     Copy <APM-AGENT-HOME>/yndchome//offering.id to <APM-AGENT-HOME>/yndchome/7.3.0.14.04
     
     Windows:
     Copy <APM-AGENT-HOME>\dchome\\offering.id to <APM-AGENT-HOME>\dchome\7.3.0.14.04
     
   
   
7. If was server are running as a non-root user,please make sure the directory \dchome\7.3.0.14.04\runtime && \dchome\7.3.0.14.04\logs have the write/read for the non-root user.

Performing the necessary tasks after installation of the interim fix

A successful installation modifies the WebSphere Applications agent version to 07.30.14.04.

On Linux or AIX:
- Ensure that the <APM-AGENT-HOME>/bin/cinfo -t output for the Monitoring Agent for WebSphere Applications is '07.30.14.04'.
- The agent interim fix installation logs are written to the <APM-AGENT-HOME>/logs/ directory.

On Windows:
- Ensure that version number 07.30.14.04 is displayed for the Monitoring Agent for WebSphere Applications on the Performance Management window.
- The agent interim fix installation logs are written to the <APM-AGENT-HOME>\INSTALLITM\ directory.

Troubleshooting installation problems from the Support site

For more detailed information, refer to the Troubleshooting and support Guide:
http://www.ibm.com/support/knowledgecenter/SSHLNR_8.1.4/com.ibm.pm.doc/install/trouble_intro.htm

Uninstalling if necessary

This maintenance package cannot be rolled back. If necessary you can uninstall and reinstall the monitoring agent and patches.

For detailed instructions to uninstall monitoring agents, please refer to the IBM Application Performance Management guide, here:
http://www.ibm.com/support/knowledgecenter/SSHLNR_8.1.4/com.ibm.pm.doc/install/uninstall_agents.htm

The Secure Hash Algorithm 1 (SHA1) checksum of the image is as follows:
SHA1(8.1.4.0-IBM-APM-WAS-AGENT-WIN64-IF0004.zip) = 47261da43a423257ee54d2881ccbdd3cc853d544
SHA1(8.1.4.0-IBM-APM-WAS-AGENT-AIX-IF0004.tar) = 2481dfec22218778413ff3668b48c2ffe56b2858
SHA1(8.1.4.0-IBM-APM-WAS-AGENT-PLINUXLE-IF0004.tar) = fd5ab0c43a99d7f6bd4a3bba889a4874a525ac92
SHA1(8.1.4.0-IBM-APM-WAS-AGENT-XLINUX-IF0004.tar) = 9ee830983ea9002414e865e73bd13ca2df0a0782
SHA1(8.1.4.0-IBM-APM-WAS-AGENT-ZLINUX-IF0004.tar) = eb53281496adced23bc2bd04c6f3d4305339b7af

Image Contents
The following files implement this fix.
- 8.1.4.0-IBM-APM-WAS-AGENT-README-IF0004.readme.html - This README file

- 8.1.4.0-IBM-APM-WAS-AGENT-PLINUXLE-IF0004.tar - For extracting patch files use the tar utility.

Extracting the above bundle (.tar) creates the following directory and patch files:

8.1.4.0-IBM-APM-WAS-AGENT-PLINUXLE-IF0004/
|-- apmpatch.sh
|-- patches
|-- patch.properties

- 8.1.4.0-IBM-APM-WAS-AGENT-XLINUX-IF0004.tar - For extracting patch files use the tar utility.

Extracting the above bundle (.tar) creates the following directory and patch files:

8.1.4.0-IBM-APM-WAS-AGENT-XLINUX-IF0004/
|-- apmpatch.sh
|-- patches
|-- patch.properties

- 8.1.4.0-IBM-APM-WAS-AGENT-ZLINUX-IF0004.tar - For extracting patch files use the tar utility.

Extracting the above bundle (.tar) creates the following directory and patch files:

8.1.4.0-IBM-APM-WAS-AGENT-ZLINUX-IF0004/
|-- apmpatch.sh
|-- patches
|-- patch.properties

- 8.1.4.0-IBM-APM-WAS-AGENT-AIX-IF0004.tar - For extracting patch files use the tar utility.

Extracting the above bundle (.tar) creates the following directory and patch files:

8.1.4.0-IBM-APM-WAS-AGENT-AIX-IF0004/
|-- apmpatch.sh
|-- patches
|-- patch.properties

- 8.1.4.0-IBM-APM-WAS-AGENT-WIN64-IF0004.zip - For extracting patch files use the WinZip or similar zip utility.

Extracting the above bundle (.zip) creates the following directory and patch files:

8.1.4.0-IBM-APM-WAS-AGENT-WIN64-IF0004/
|-- apmpatch.bat
|-- patches
|-- patch.properties

New Features

The following changes are included in WebSphere Applications agent interim fix:

• Implement RFE (113862,113863):
  http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=11… or 113863
  
  
  • 129474: T-[Unique Peru] Need to support monitor REST requests
    
  • 129948: D-[Unique Peru] Update the web services group widgets attributes for cover all the JAX-WS & JAX-RS webservice data
    
  • 129473: D-[Unique Peru] Need to show Jax-WS & Jax-RPC webservice data
    
  • 129472: D-[Unique Peru] WebService Counters PMI should be enabled by default
    



• Implement RFE (91503):
  https://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=9…
  
  
  • 130906: S-WAS Agent Remove auto-disabling of WebSphere Method trace on JVM restart
    

The following problems are addressed by this interim fix.

APARs

• 129644: D-[Walgreens ] WAS 8.1.4 support the KYN_J2C_CONNCTION_POOLS
• 129645: D-[Walgreens] It is need to bundle empty logs directory as part of the DC to resolve the logs can not be writed with no-root
  
• 129750: D-[Walgreens ] WAS 8.1.4 make the DC configuration script questions more clear
  
• 130827: D-[Walgreens] WAS814 TEMA dump unnecessary log when diagnostic disabled
  


• 126813: [GDPR] D- WAS8.1.4: secure.filter.on doesn't work in datacollector.properties file
  

• 128993: D-WAS agent data collector configuration removed the GC log settings specified by user
• 130701: [IBM BANORTE:TS000080861] WAS Agent - Errors CNTR0020E, SRVE0296E and JVMVRFY012
• 128079: WAS-Agent 8.1.4: MSN Change for V8 Agents,Need to update code to fix long hostname truncation problem
• 128997: WAS814IF02: DC less monitoring data can't be displayed on apm dashboard
• 128452: [Gunes Sigorta] WAS 8.1.4: WAS Data Collector enable the healthcenter which will generate temp files,the data collector need to handle them.

• IV92951: WebSphere configuration fails when localhost is specified as hostname in serverindex.xml
• IV98546: When the WAS DC creates a separate thread to obtain JDBC metadata if the datasource name is not available through JNDI or other means, the WAS XA resource manager logs messages J2CA0027E and J2CA0030E
• IV99656: 8.1.4 MIN SERVER CRASHES DUE TO WAS AGENT
• IJ00240: APM 8.1.4 AND WEBSPHERE AGENT INSTANCES ARE MISING IN THE AGENT CONFIGURATION FOR V8.1.3 CUSTOMERS GOING TO V8.1.4
• IJ01107: INCORRECT WAS AGENT DATA COLLECTOR BUNDLE PATH LED TO MISSING INFORMATION IN TRANSACTION TOPOLOGY DIAGRAM.
• IV99518: APM BPM/WAS agent security issue - #CS6M577FG

Agent defects:

• 124828: Events cannot be triggered when the WAS agent is installed on a Linux for System Z
• 125841: WAS agent generates lots of .dat files that eventually fill up the file system where the agent is installed
• 126026: WebSphere Configuration issue at Kaiser for configure tool
• 126561: APM 8.1.4 and websphere agent configuration tab issue
• 126850: No heapusage/GC data in apm UI for any of WAS agents
• 126911: D:agentfactory generate the duplicate column in the asf_asf_definition.xml in WAS Agent 8.1.4 IFix
• 126562: APM 8.1.4 and transaction topology issue
• 126813: WAS8.1.4: secure.filter.on doesn't work in datacollector.properties file
• 128396: D-814SVT: WAS Deep dive data cannot be showed after enabled
• 125434: WAS814IF01: can't take heap snapshot on windows with was 8
• 117132: US - WAS Agent should support Transaction Tracking in zlinux platform
• 126271: US - WAS Agent should support Transaction Tracking in pLinux LE platform

• 
  

After you apply WAS agent 8.1.4.0 IF02 or above, to enable transaction tracking for application servers on zLinux or pLinux LE, complete the following steps:

1.1 Apply the following APM core framework patch on the target system. You can download the 8.1.4.0-IBM-APM-CORE-FRAMEWORK-APM-IF0001 patch from Fix Central. Detailed instructions can be found in the Readme file of the core framework patch.

• Linux for System z: 8.1.4.0-IBM-APM-CORE-FRAMEWORK-ZLINUX-IF0001.tar
• Linux for Power Systems (Little Endian): 8.1.4.0-IBM-APM-CORE-FRAMEWORK-PLINUXLE-IF0001.tar

1.2 Run the following command to make sure that the Transaction Framework Extension (TFE) is listening on the default port 5457:

netstat -an |grep 5457

      The following result is expected:

tcp        0      0 0.0.0.0:5457            0.0.0.0:*               LISTEN

1.3 Go to the <APM-AGENT-HOME>/yndchome/7.3.0.14.04/bin directory and use appropriate configuration script to enable transaction tracking for the data collector.

• If the application server was previously configured, use reconfig.sh to reconfigure the data collector. A known limitation is the default or previously configured IP and port of Transaction Framework Extension cannot be displayed during configuration. You must manually enter them. The default IP is 127.0.0.1 and the default port is 5457.
• If the application server has never been configured, use simpleconfig.sh or config.sh to enable transaction tracking for the data collector.