IBM Support

8.1.4.0-IBM-APM-CORE-FRAMEWORK-IF0024

Fix Readme


Abstract

Readme file for: IBM Application Performance Management 8.1.4.0 Core Framework IF24 (8.1.4.0-IBM-APM-CORE-FRAMEWORK-IF0024)
Updates Name/Fix ID: 8.1.4.0-IBM-APM-CORE-FRAMEWORK-IF0024
This Core Framework patch works with both APM and CP4MCM
This Core Framework supports RHEL 9.0 Operating System

Content

Download location
 

Download location

IMPORTANT NOTE:

1. To download this update, login to IBM Fix Central by using the following link:  http://www.ibm.com/support/fixcentral/

2. There are three download options on Fix Central: Download Director, FTPS/SFTP, and using your browser (HTTPS). If you want to download individual packages, you need choose FTPS/SFTP or HTTPS. Download Director will download all the packages.

The following table shows the components, platforms, and file names that apply to this Readme file.

Server-Side Fix Download (APM only, ICAM doesn't need server-side fix)

Platform Fix
Linux x86_64 8.1.4.0-IBM-APM-CORE-FRAMEWORK-SERVER-IF0024
Agent Side Fix Download (For both APM and ICAM)
Platform Fix
AIX pSeries
Linux ppc64le
Linux ppc64
Linux x86_64
Linux s390x
Solaris Sparc
Solaris X86
Windows 32bit
Window 64bit
 

Prerequisites and co-requisites

General description 

This Core Framework patch works with both APM and CP4MCM.

This Core Framework supports RHEL 9 Operating System.

Platforms and prerequisites 

APM: The agent core framework and server core framework are supported on all agent and server platforms. For more information, see IBM® Cloud Application Performance Management System Requirements
ICAM: The agent core framework is supported on all agent and platforms. For more information, see IBM® Cloud App Management System Requirements.

Prerequisites for this interim fix 

This interim fix for the core framework is intended for the following components:

APM:

  • 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

ICAM:

Agent only

Known issues

None

Known limitations

None

Installation information

Before installation

You must install Performance Management Server before you apply the server-side core framework server interim fix.
You must ensure that Monitoring agents are installed and are running before you apply the agent side core framework interim fix.

Installing

The server-side core framework patch is installed on the computer system where the Performance Management server is installed. The server core framework patch updates the core framework that is included in agent installation images.

You must install the agent side core framework patch on the computer systems where your monitoring agents are already installed.

  • If you want to create new agent packages that contain the agent core framework fixes, so that the fixes are included when you install new agents or upgrade agents, then follow the instructions for installing the core framework server patch.
  • If you need to apply the patch to already installed agents, then follow the instructions for installing the agent patch on each agent system.

Installing the core framework server patch on the Performance Management server (APM only, ICAM doesn't need server-side fix)

  1. Download the server patch file.
  2. Unpack it.
  3. Enter the created directory.
  4. Run the apmpatch.sh tool:
    ./apmpatch.sh
  5. Run the following scripts. These scripts are also provided in the following topic in the APM 8.1.4 IBM Documentation:
    http://www.ibm.com/support/knowledgecenter/SSHLNR_8.1.4/com.ibm.pm.doc/install/install_agent_preconfig.htm 
  • Run the <apm-server-home>/make_configuration_packages.sh script if you have not already created the configuration information for the agent installation packages.
  • Run the <apm-server-home>/configure_agent_images.sh script. Pass <apm-server-home>/ccm/AgentFrameworks as the value for the -a option.
    Note: The configure_agent_images.sh script updates your agent packages to include the patched agent core framework in <apm-server-home>/ccm/AgentFrameworks
Either use the configured agent packages to install NEW agents with the patched agent core framework or use those packages to UPGRADE the core framework for the already installed agents. See the following APM 8.1.4 IBM Documentation topics for more information about installing and upgrading agents:
 

Installing the agent patch on each agent system (APM and ICAM)

Note: Ensure that the agent is already installed before you apply the agent side patch. The agent will be restarted whenever the patch is applied.

  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-CORE-FRAMEWORK-AIX-IF0024.tar
    • If the agent is installed on Linux for Power Systems (Big Endian), download 8.1.4.0-IBM-APM-CORE-FRAMEWORK-PLINUX-IF0024.tar
    • If the agent is installed on Linux for Power Systems (Little Endian), download 8.1.4.0-IBM-APM-CORE-FRAMEWORK-PLINUXLE-IF0024.tar
    • If the agent is installed on Linux for System x, download 8.1.4.0-IBM-APM-CORE-FRAMEWORK-XLINUX-IF0024.tar
    • If the agent is installed on Linux for System z, download 8.1.4.0-IBM-APM-CORE-FRAMEWORK-ZLINUX-IF0024.tar
    • If the agent is installed on Solaris, download 8.1.4.0-IBM-APM-CORE-FRAMEWORK-SOLARIS-IF0024.tar
    • If the agent is installed on Solaris x86, download 8.1.4.0-IBM-APM-CORE-FRAMEWORK-SOLARIS_X86-IF0024.tar
    • If the agent is installed on Windows 64-bit, download 8.1.4.0-IBM-APM-CORE-FRAMEWORK-WIN64-IF0024.zip
  2. If you are installing the patch on AIX as a non-root user, then before you install the patch, you must clear the unused shared libraries from the kernel and library memory, by completing the following steps:
    • Stop the agents
    • Login as root, and run the slibclean command
    • Login as the non-root user who installed the agents 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 extract on Windows.

    For example:
    tar -xf 8.1.4.0-IBM-APM-CORE-FRAMEWORK-XLINUX-IF0024.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 install directory>]

    Windows:
    ./apmpatch.bat <APM agent install directory>

    You need to provide the <APM agent install directory> parameter only if the agent is installed in a non-default directory on Linux and AIX operating systems. However, <APM agent install directory> is a required parameter on Windows system.

Performing the necessary tasks after installing the agent core framework update

A successful installation modifies the agent core framework version to 06.40.00.24, gs version to 08.00.55.17, and the JR to 08.06.25.00.

On Linux or AIX:
- Ensure that the <APM-AGENT-HOME>/bin/cinfo -t output for the ax agent version is '06.40.00.24', gs version is 08.00.55.17, and jr version is 08.06.25.00.
- The agent interim fix installation logs are written to the <APM-AGENT-HOME>/logs/ directory.

On Windows:
- Ensure that the <APM-AGENT-HOME>\InstallITM\kincinfo -i command shows that the TEMA component version is 06.40.00.24, gs version is 08.00.55.17, and the jvm component version is 08.06.25.00.
- The agent interim fix installation logs are written to the <APM-AGENT-HOME>\INSTALLITM\ directory.

Uninstalling (if required)

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

For detailed instructions to uninstall monitoring agents, refer to the guide at:

APM
http://www.ibm.com/support/knowledgecenter/SSHLNR_8.1.4/com.ibm.pm.doc/install/uninstall_agents.htm

ICAM
https://www.ibm.com/support/knowledgecenter/SS8G7U_19.3.0/com.ibm.app.mgmt.doc/content/uninstall_agents.html

Troubleshooting installation problems from the Support site

For more information, refer to the troubleshooting and support guides at:

APM
http://www.ibm.com/support/knowledgecenter/SSHLNR_8.1.4/com.ibm.pm.doc/install/trouble_intro.htm 

ICAM (Different versions are available if yours is not 2019.4.0)

Additional information

The Secure Hash Algorithm 1 (SHA256) checksums of the images are as follows:
 
8.1.4.0-IBM-APM-CORE-FRAMEWORK-AIX-IF0024.tar
c42ce52dc7f49fe73a4a965d2092390888fe5997097caea8326f99b69daa92a8
 
8.1.4.0-IBM-APM-CORE-FRAMEWORK-PLINUX-IF0024.tar
602ce0c83ddc2d57c9b39fb5d11c7588c19b3a2766cb6335d48d75a93a2f4028
 
8.1.4.0-IBM-APM-CORE-FRAMEWORK-PLINUXLE-IF0024.tar
7a1c8a726a4dca1713a61fcc7a73bee8de6a1cc5139135af58babeec453a42d1
 
8.1.4.0-IBM-APM-CORE-FRAMEWORK-SOLARIS_X86-IF0024.tar
2b2109f3c42ea1c13b1c08f14cb8ae7a4f56f9a0529f65c8942d74fbc1152f9e
 
8.1.4.0-IBM-APM-CORE-FRAMEWORK-SOLARIS-IF0024.tar
9ae98c0a4686c05d4a8e065d86e1c4ab9174be049a4898e09288ce4e58dc9abd
 
8.1.4.0-IBM-APM-CORE-FRAMEWORK-WIN64-IF0024.zip
2bb82a3bce9000ced25b9ef5770681c8c176150ae321415471444792d0692c6c
 
8.1.4.0-IBM-APM-CORE-FRAMEWORK-XLINUX-IF0024.tar
e8f0eee541b9d9b7b1d3a35c78c710ee0ab3550556eccb20c57a8cc93042b399
 
8.1.4.0-IBM-APM-CORE-FRAMEWORK-ZLINUX-IF0024.tar
a16369c5db5cce4ead075c57f42c869f7a89ea147d9a5e3919953fed06f86487
 
8.1.4.0-IBM-APM-CORE-FRAMEWORK-SERVER-IF0024.tar
985e721687365b322169579c95cd4c754476584ef6f49e3ca328359e5d396cca

New Features

None.

List of fixes

The following problems are addressed by this interim fix.

APARs
  • None

Defects and Enhancements:

 - Updated Expat XML parser to version 2.4.6
 - Added support for RHEL 9.0 Operating System
 - Fixed the defect, RTC 146512 - GUI xml.config for Windows does not truncate config property containing equal sign

Superseded fixes:

  • None

APARS and defects included from superseded fixes:

  • Supporting Windows Server 2022, Windows 11, and AIX 7.3
  • Windows builds use VS 2013 for compiling C and C++ code
  • GitHub 19175: Fixed error reported by agent on zLinux processing central configuration load list
  • RTC 144764: History situations not refreshing as expected
  • RTC 144825: Visual C++ uplift for TEMA-based agent
  • GitHub 13317: Report on agent's hung data collection thread with no additional tracing in KBB_RAS1
  • Add TEMA prereq checker support for Debian 10
  • RTC 144152 Prepare Java v8.0.6.25 source packages for agent framework
  • RTC 142982: Fix invalid memory free error (IBM i systems)
  • RTC 143206: Make sure HISTORY situations are retained whenever new thresholds are downloaded
  • GitHub 8154 / RTC 141798: Garbled characters in threshold display item for multibyte character data
  • RTC 143669: Failed to install agent patch on Solaris
  • IJ26647:APM 8.1 AGENT STATUS NOT REPORTED CORRECTLY WITH 'XX-AGENT.SH STATUS' COMMAND WHEN UNDERSCORE IS IN AGENT HOSTNAME
  • IJ09774: APM Db2 AGENT FAILS TO START CORRECTLY AFTER REBOOT
  • IJ12656: Missing klo_* EIF event slots
  • IJ12808: SUSE12, NO ITMAGENTS1.SERVICE AND ITMAGENTS2.SERVICE IN APM 8.1.4
  • IV98883: The agent2server.sh may start agents using the wrong user ID
  • IJ00965: Failed to stop agent during upgrade
  • IJ00973: Fix the agent installation issue caused by special characters validation
  • IJ01900: Kcirunas.cfg file should not be over-written
 

Defects:

  • GitHub 11512: Apply workaround where APM_BLANK_INVALID_CHARACTERS=Y applies to data in EIF events as well as subscriptions
  • RTC 142438: Agents crashing on Solaris
  • RTC 142892: Prepare Java v8.0.6.15 source packages for APM V8 agent framework
  • GitHub 3904: Trace reflex action command nonzero return code
  • GitHub 5690: Fix central config load list file name for ITM multi-instance agents
  • Pull req 72: Suppress incorrect XML validation error message
  • GitHub 5979: Unchanged subnode situations restarted multiple times on new private_situations.xml download
  • RTC 141275: Fix thread handle leak when running Windows commands
  • GitHub 7595: Remove trailing spaces before processing regex private sit. string
  • GitHub 7707/7811/7957: Agent crashes recycling thresholds
  • GitHub 8158: Pass prereq checking on Ubuntu 20.04
  • RTC 141941: Framework support for Ubuntu 20.04
  • GitHub 8272: asfSubscription file getting corrupted
  • 136805: Vulnerability on APM MQ monitoring agent
  • 137153: APM SaaS Db2 agent alerts cannot be cleaned on APM console
  • 137660: Uplift JRE version to 8.0.5.35 in Agent Framework
  • 138139: Add support for RHEL8
  • GIT#9752: Close a timing window where it is possible that an updated private situation is not downloaded to the agent
  • GIT#7097: Provide a workaround where no attribute group data is sent to the server because of a non-UTF8 character in one field
  • GIT#9065: When connecting an ITM or SMA agent to ICAM in dual mode, continue to run any private situations defined in the ITM environment (typically this is done with autonomous agents) rather than private situations from ICAM. Also provide a configuration variable to instead run ICAM private situations and not ITM private situations
  • GIT#7168: When connecting an ITM or SMA agent to ICAM, continue to download files from a centralized configuration server defined in the ITM environment
  • GIT#10320: Fail is reported when upgrading agent on Windows because of the same version
  • GIT#10460: AgentSVT-Script error when config ICAM agent instance on Ubuntu 18
  • 129793: kqi crash when kqi start on zlinux.
  • 135941: Add agent support for Solaris.
  • 136335: Add agent support for Windows Server 2019.
  • 136890: Wdev Threshold "Execute Command" execute at every interval instead of at first occurrence.
  • 137029: Uplift JRE version to 8.0.5.30 in Agent Framework.
  • GIT#5970: Quicker agent configuration when switching agent to and from ICAM.
  • GIT#6479: TEMA crashes intermittently when run in Agent Builder testing mode.
  • GIT#6904: Determine Db2 instance name without checking DB2INSTANCE.
  • GIT#7252: Agents hang processing cached data after long server outage.
  • 135420: Uplift JRE version to 8.0.5.25 in agent framework.
  • 135531: Failed to install APM Agents on SUSE 15 Platform
  • Issue 6256: Windows 32-bit agent crashes
  • Issue 6182: pdcollect haven't collected global.environment file in config directory
  • Issue 6588: Configuration of fresh installed MQ/IIB agent failed on Windows
  • 114957: Db2 event missing details when sent to Alert Notification.
  • 123708: If the agent downloads a bad event destination file then it stops sending events to the APM server.
  • 124187: Fix lock handling of private situation files to prevent the agent from crashing and not updating the active private situation file if the agent detects a modified situation file when it is restarted.
  • 124264: If the OS watchdog restarts a non-factory agent, the agent may download its threshold file to the wrong directory and will not trigger events.
  • 125222: Uplift Java to 8.0.4.10
  • 125424: Change extension pack license to agent license.
  • 125602: Exchange agent is unable to re-point agent to the new MIN using agent2server.bat.
  • 125688: No events generated for websites (SLA subscription)
  • 129633: Uplift JRE packaged by agent installer to 8.0.5.5
  • 126719: Improve regular expression evaluation in APM situations
  • 129757: Further improvements in regular expression evaluation
  • 129793: Fix potential TEMA crash where TEMA referenced freed memory from a situation definition
  • 133713: Failed to detect the installed agent version on AIX
  • 134218: Add call to ism-agent.bat while uninstalling agent through smai-agent.bat
  • 132196: After installing 8.1.4 IF03, service oslc failed to start
  • 134475: Uplift JRE version to 8.0.5.20 in agent framework
  • WF#2794: Improve messages in lz_asfActivity.log and *.LG0
  • WF#4203: Some agent threshold definitions not distributed correctly
  • 133634: Add support for pLinux Big Endian
  • Git#5217: TEMA update for Agent/Server communication in HTTPS
  • GIT#8665: TEMA Situations Sometimes Do Not Reach The Agent Because of A Timing Issue in Temaconfig
  • 1138331: Upcoming hotfix and includes a fix for RTC defect
  • Git#10037: Support History and Warehouse statements in private situations

  • 139188 - Uplift JRE version to 8.0.5.40 in Agent Framework
  • 139169 - Add agent support for solaris x86
  • Git#10647: In ICAM use extra-precise last modified time from HTTP header of downloaded private situations file from Central Configuration when requesting an updated copy
  • Git#11104: Fix for defect where SQLite private situations are not saved when downloaded from Central Configuration.
  • Git#11109: Fix for defect where updated ITM-defined private situations file starts running and reporting events to ICAM when only ICAM-defined private situations file should be running
  • Git#10445: Event Summary does not show AND OR conditions clearly
  • Git#10613: Support for private situation full name - for long threshold names (part of epic 10413)
  • Git#11640: Start ICAM situations when switching ITM agents from dual to ICAM-only mode
  • 138077: Fix some errors, possible agent crash, in situation with COUNT when zero rows pass filters
  • Git#9849: Clean up attribute substitution into reflex action command
  • Git#11912: Adjust threshold reflex command action to respect the "consecutive samples" setting
  • Git#12216: Remove and no longer create Last-Modified directory from OS agent log_discovery directory
  • Git#12227: Closed a window where an agent (in dual mode) might report ITM private situation events to ICAM server
  • 139475: RHEL 8 on pLinuxLE v81409 and ICAM v2019.3.0 Db2 agent did not point to APM Server and ICAM server
  • Git#12219: Can configure endpoint agent with KDE_GATEWAY_SUBSTITUTION to support KDE_GATEWAY on ICAM & APM
  • Git#12703: Support wild cards on private sit MISSING arguments
  • Git#10626: Support *CHANGE in private situations
  • Git#10627: Support *PCTCHANGE in private situations
  • 141196 - Uplift JRE version to 8.0.6.05 in Agent Framework
  • 140203: TEMA downloads but does not process private_situations.xml if there are many files in download list
  • GitHub 1775: Allow TEMA to download any custom file using default IRA_LOCALCONFIG_DIR
  • GitHub 1818 (formerly 13669): Do not cycle situations for thresholds that do not change

Document change history

Version Date Description of change

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSVJUL","label":"IBM Application Performance Management"},"Component":"core framework","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}},{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS8G7U","label":"IBM Cloud App Management"},"Component":"core framework","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
03 November 2022

UID

ibm16620645