IBM Support

Readme - IBM Application Performance Management 8.1.4.0 Core Framework Interim Fix 28

Fix Readme


Abstract

This article includes a list of defects fixed with this release and has information related to Prerequisites, Installation, Upgrade, and Release highlights.

Content

Release details

Product name IBM Application Performance Management 8.1.4.0 Core Framework
Release name IBM Application Performance Management 8.1.4.0 Core Framework Interim Fix 28
Build ID 8.1.4.0-IBM-APM-CORE-FRAMEWORK-IF0028
Release date 31st January 2025

APARs fixed

Following is the list of APARs fixed with this release.

  • None

IBM Application Performance Management Core Framework defects

  • GitHub#3 -  Prepare Java Runtime Environment (JRE) Version 8.0.8.30 source packages for the APM V8 agent framework.

  • GitHub#3 - Consume JRE Version 8.0.8.30 in the APM V8 agent framework.

Superseded agent interim fixes APAR and defects

  • Updated Expat XML parser to Version 2.4.6.
  • Added support for the Red Hat® Enterprise Linux Platforms Version 9.0 operating system.
  • RTC 146512 - GUI xml.config file for the Windows operating system does not truncate config property containing equal "=" sign.
  • Support for the Windows Server 2022, Windows 11, and AIX 7.3.
  • Windows builds use Visual Studio 2013 to compile C and C++ code.
  • GitHub#19175: Fixed error reported by the agent on zLinux Operating System processing central configuration load list.
  • RTC 144764 - History situations are not refreshing as expected.
  • RTC 144825 - Visual C++ uplift for Tivoli Enterprise Monitoring Agent (TEMA)-based agent.
  • GitHub 13317 - Report on an agent's hung data collection thread with no additional tracing in the KBB_RAS1.
  • Add TEMA prereq checker support for Debian 10.
  • RTC  147905 - US - As an APM Server Core framework developer, I want to upgrade to JRE Version 8.0.8.20 to address vulnerabilities.
  • RTC 147475 - US - As an APM Server Core framework developer, I want to fix the defect for the APM Sybase agent failing to connect to the APM server with an SSL session negotiation failed error.
  • RTC 147837 - US - As an APM Server Core framework developer, I want to fix the defect for the Windows Operating system agent crashing on startup so that the Windows OS agent doesn't crash.
  • RTC 147872 - US - As an APM Server Core framework developer, I want to upgrade the TEMA version so that the latest TEMA version gets used.
  • RTC 146218 - Ubuntu20 zLinux - Upgrade message "Monitoring Agent for the IBM Db2 will be upgraded from version  08.21.09.00 to 08.22.04.00" is not showing on the terminal.
  • RTC 137692 - After applying version 8 Interim Fix 09/Interim Fix 10 TEMA patch incorrect node name is showing on the APM UI and the IBM Db2 agent service is started with a blank instance name.
  • RTC 144152 Prepare JRE Version 8.0.6.25 source packages for the agent framework.
  • RTC 142982 - Fix invalid memory-free error (IBM i operating system).
  • 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 the 'xx-agent.sh status' command when there is an underscore ("_") in the agent hostname.
  • IJ09774 - APM Db2 agent fails to start correctly after reboot.
  • IJ12656 - Missing klo_* EIF event slots.
  • IJ12808 - SUSE Linux Enterprise Server 12, no itmagents1.service and itmagents2.service in the APM Version 8.1.4.
  • IV98883 - The  agent2server.sh may start agents using the wrong user ID.
  • IJ00965 - Failed to stop the agent during the upgrade.
  • IJ00973 - Fix the agent installation issue caused by special characters validation.
  • IJ01900 -  The Kcirunas.cfg file should not be over-written.
  • RTC 146845 - Prepare JRE Version 8.0.7.20 source packages for APM V8 agent framework.
  • RTC 146882 - MySQL agent installed on the Windows platform, is not showing data on the user interface of the Interim Fix 27 preconfigured with MIN having IF13 and IF25 core framework patch.
  • RTC 146921 - The security file present in the installer does not appear post-installation of the agent under the security folder on Windows.
  • GitHub 11512 - Apply a workaround where the APM_BLANK_INVALID_CHARACTERS=Y applies to data in EIF events as well as subscriptions.
  • RTC 142438 - Agents crashing on the Oracle Solaris operating system.
  • RTC 142892 - Prepare JRE Version 8.0.6.15 source packages for the APM Version 8 agent framework.
  • GitHub 3904 - Trace reflex action command nonzero return code.
  • GitHub 5690 - Fix central config load list file name for the IBM Tivoli Monitoring multi-instance agents.
  • Pull req 72 - Suppress incorrect XML validation error message.
  • GitHub 5979 - Unchanged subnode situations restarted multiple times on the new private_situations.xml file download.
  • RTC 141275 - Fix thread handle leak when running the 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 the Ubuntu 20.04 operating system.
  • RTC 141941 - Framework support for the Ubuntu 20.04 operating system.
  • GitHub 8272 - The asfSubscription file getting corrupted.
  • 136805 - Vulnerability on the APM MQ monitoring agent.
  • 137153 - APM SaaS Db2 agent alerts cannot be cleaned on the APM console.
  • 137660 - Uplift JRE to Version 8.0.5.35 in the agent framework.
  • 138139 - Add support for the Red Hat® Enterprise Linux Server 8.
  • 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 the  IBM Cloud App Management (ICAM) in the dual mode, continue to run any private_situations.xml file defined in the ITM environment (typically this is done with autonomous agents) rather than the private_situations.xml file from ICAM. Also, provide a configuration variable to instead run the ICAM private_situations.xml file and not the ITM private_situations.xml file.
  • 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 the agent on Windows because of the same version.
  • GIT#10460 - AgentSVT-Script error when config ICAM agent instance on Ubuntu 18 operating system.
  • 129793 - kqi crash when kqi starts on zLinux.
  • 135941 - Add agent support for the Oracle Solaris operating system.
  • 136335 - Add agent support for the Windows Server 2019.
  • 136890 - Wdev Threshold "Execute Command" executes at every interval instead of at the first occurrence.
  • 137029 - Uplift JRE to Version 8.0.5.30 in the agent framework.
  • GIT#5970 - Quicker agent configuration when switching agents to and from the ICAM.
  • GIT#6479 - TEMA crashes intermittently when run in Agent Builder testing mode.
  • GIT#6904 - Determine the IBM Db2 instance name without checking the DB2INSTANCE.
  • GIT#7252 - Agents hang processing cached data after a long server outage.
  • 135420 - Uplift JRE to Version 8.0.5.25 in the agent framework.
  • 135531 - Failed to install APM Agents on the SUSE Linux Enterprise 15 operating system.
  • Issue 6256 - Windows 32-bit agent crashes.
  • Issue 6182 - The pdcollect does not collect the global.environment file in the config directory.
  • Issue 6588 - Fresh installed MQ/IIB agent configuration fails on the Windows operating system.
  • 114957 - Db2 event missing details when sent to the 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 the private_situations.xml file files to prevent the agent from crashing and not updating the active private_situations.xml 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 JRE to Version 8.0.4.10.
  • 125424 - Change extension pack license to agent license.
  • 125602 - The exchange agent is unable to re-point the agent to the new MIN using agent2server.bat.
  • 125688 - No events generated for websites (SLA subscription).
  • 129633 - Uplift JRE packaged by agent installer to Version 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 the ism-agent.bat file while uninstalling the agent through the smai-agent.bat file.
  • 132196 - After installing 8.1.4 IF03, service oslc failed to start.
  • 134475 - Uplift JRE to Version 8.0.5.20 in the agent framework.
  • WF#2794 - Improve messages in lz_asfActivity.log and *.LG0.
  • WF#4203 - Some agent threshold definitions are not distributed correctly.
  • 133634 - Add support for pLinux Big Endian.
  • Git#5217 - TEMA update for the Agent-Server communication in the HTTPS.
  • GIT#8665 - TEMA situations sometimes do not reach the agent because of a timing issue in the Temaconfig file.
  • 138331 - Upcoming hotfix and includes a fix for RTC defect.
  • Git#10037 - Support History and Warehouse statements in the private_situations.xml file.
  • 139188 - Uplift JRE to Version 8.0.5.40 in the agent framework.
  • 139169 - Add agent support for Oracle Solaris x86 operating system.
  • Git#10647 - In ICAM use extra-precise last modified time from the HTTP header of downloaded private_situations.xml file file from the central configuration when requesting an updated copy.
  • Git#11104 - Fix for defect where SQLite private_situations.xml file are not saved when downloaded from the central configuration.
  • Git#11109 - Fix for defect where updated the ITM-defined private_situations.xml file starts running and reporting events to ICAM when only ICAM-defined private_situations.xml should be running.
  • Git#10445 - Event Summary does not show AND/OR conditions.
  • Git#10613 - Support for the private_situations.xml file full name for long threshold names (part of epic 10413).
  • Git#11640 - Start ICAM situations when switching the ITM agents from dual to ICAM-only mode.
  • 138077 - Fix some errors, possible agent crash, in a situation with COUNT when zero rows pass filters.
  • Git#9849 - Clean up attribute substitution into the reflex action command.
  • Git#11912 - Adjust threshold reflex command action to respect the "consecutive samples" setting.
  • Git#12216 - Remove and no longer create the Last-Modified directory from the OS agent log_discovery directory.
  • Git#12227 - Closed a window where an agent (in dual mode) might report the ITM private_situations.xml file events to the ICAM Server.
  • 139475 - Red Hat® Enterprise Linux 8 on pLinuxLE v81409 and ICAM v2019.3.0 Db2 agent did not point to the APM Server and ICAM server.
  • Git#12219 - Can configure endpoint agent with the KDE_GATEWAY_SUBSTITUTION to support the KDE_GATEWAY on the ICAM and APM.
  • Git#12703 - Support wild cards in the private_situations.xml missing arguments.
  • Git#10626 - Support *CHANGE in the private_situations.xml.
  • Git#10627 - Support *PCTCHANGE in the private_situations.xml.
  • 141196 - Uplift JRE to Version 8.0.6.05 in the agent framework.
  • 140203 - TEMA downloads, but does not process private_situations.xml if there are many files in the download list.
  • GitHub 1775 - Allow TEMA to download any custom file by using the default IRA_LOCALCONFIG_DIR parameter.
  • GitHub 1818 (formerly 13669) - Do not cycle situations for thresholds that do not change.
  • 143402 - IBM Db2 agent is not getting restarted automatically after upgrade from 2020.2.1 (08.20.09.00) to 2020.2.2 (08.20.11.00) on the Red Hat® Enterprise Linux Platforms.
  • 148135 - US: As an APM Server Core framework developer, I want to upgrade JRE to Version 8.0.8.25 so that vulnerabilities get addressed.

Release highlights

Following is the list of the new features and enhancements for this release.

New features

  • Upgraded framework JRE from Version 8.0.8.25 to Version 8.0.8.30.

Enhancements

  • None

Prerequisites

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

  • This Core Framework patch works with both IBM Cloud Application Performance Management and IBM Cloud Pak for Multicloud Management.
  • This Core framework supports the Red Hat® Enterprise Linux Platforms  9 operating system.

Platforms and prerequisites 

Pre-installation tasks

  • You must install the Performance Management Server before you apply the server-side core framework interim fix.
  • You must ensure that Monitoring agents are installed and running before you apply the agent side core framework interim fix.
  • 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.

Download details

Following are the download details for this release.

Server-side fix download (APM only)

Following are the download details for this release.

  1. Go to the Fix Central download link - 8.1.4.0-IBM-APM-CORE-FRAMEWORK-IF0028.
  2. In the Select fixes page, ensure that the release is selected, and click Continue.
  3. In the Download options page, select an appropriate option from the Select download options.
  4. Ensure you select Include prerequisites and co-requisite fixes (you can select the ones you need later) and click Continue.
  5. Download 8.1.4.0-IBM-APM-SERVER-IF0028.tar image to install a server-side patch.

Agent-side fix download (APM and ICAM)

Following are the download details for this release.

  1. Go to the Fix Central download link - 8.1.4.0-IBM-APM-CORE-FRAMEWORK-IF0028.
  2. In the Select fixes page, ensure that the release is selected, and click Continue.
  3. In the Download options page, select an appropriate option from the Select download options.
  4. Ensure you select Include prerequisites and co-requisite fixes (you can select the ones you need later) and click Continue.
  5. Depending upon the Operating system on which your agent is installed, click the appropriate download link to get agent-side core framework patch image.

Additional information

The Secure Hash Algorithm 1 (SHA1) checksum of the image follows.

  • 8.1.4.0-IBM-APM-CORE-FRAMEWORK-AIX-IF0028.tar=27666906330aae62caaf0b309030d65fd97386df
  • 8.1.4.0-IBM-APM-CORE-FRAMEWORK-PLINUX-IF0028.tar=625f36f3563450f1665862b2b1a33ae810a346ca  
  • 8.1.4.0-IBM-APM-CORE-FRAMEWORK-PLINUXLE-IF0028.tar=c3c8daa2b0ac1bcd5a7cdb9f34697b2e92f7b985  
  • 8.1.4.0-IBM-APM-CORE-FRAMEWORK-SERVER-IF0028.tar=0ea84494bfd0ff755c5e0dcfcbaf8ba4e073a8b6  
  • 8.1.4.0-IBM-APM-CORE-FRAMEWORK-SOLARIS-IF0028.tar=ac3dc0d21c6fbc88e6af18d1ec7d858ff731a7ff
  • 8.1.4.0-IBM-APM-CORE-FRAMEWORK-SOLARIS_X86-IF0028.tar=e51ba48fbc0274782571e36fc4b68ca59615f022  
  • 8.1.4.0-IBM-APM-CORE-FRAMEWORK-WIN32-IF0028.zip=b65db887ce4bd8e46f594e77fdee221511144f3c  
  • 8.1.4.0-IBM-APM-CORE-FRAMEWORK-WIN64-IF0028.zip=0823686b0975cb6150544ec7d929aeef710c73b9  
  • 8.1.4.0-IBM-APM-CORE-FRAMEWORK-XLINUX-IF0028.tar=65d597c91e9e9363a7ecb0522168d3558b98b984  
  • 8.1.4.0-IBM-APM-CORE-FRAMEWORK-ZLINUX-IF0028.tar=a43ca3909e35f909c3cc3268d4750be3d97a638c

The image contains the following files.

  • This readme file
  • 8.1.4.0-IBM-APM-SERVER-IF0028.tar file

Extracting the TAR file creates the following directory and patch files.

Linux

|- - apmpatch_functions
|- - apmpatch.sh
|- - msg
|- - nls_replace
|- - patches
|- - patch.properties

Installation instructions

Installing the core framework server patch on the Performance Management server for APM (ICAM does not need a server-side fix). 

Proceed as follows to install the agent.

  1. Download the server patch file.
  2. Unpack the server patch file.
  3. Enter the created directory.
  4. Run the apmpatch.sh tool: 
    ./apmpatch.sh
  5. Run the following scripts.
    1. Run the <apm-server-home>/make_configuration_packages.sh script If you have not already created the configuration information for the agent installation packages.
    2. 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.
These scripts are also provided in the Configuring the downloaded images topic in the IBM Cloud Application Performance Management 8.1.4 documentation. 
 
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. For more information, see the following documentation topics.
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 the Fix Central for each operating system type where your agent is installed.
    Operating system Download...
    AIX 8.1.4.0-IBM-APM-CORE-FRAMEWORK-AIX-IF0028.tar file
    Linux for Power Systems (Big Endian) 8.1.4.0-IBM-APM-CORE-FRAMEWORK-PLINUX-IF0028.tar file
    Linux for System x 8.1.4.0-IBM-APM-CORE-FRAMEWORK-XLINUX-IF0028.tar file
     Linux for System z 8.1.4.0-IBM-APM-CORE-FRAMEWORK-ZLINUX-IF0028.tar file
    Solaris 8.1.4.0-IBM-APM-CORE-FRAMEWORK-SOLARIS-IF0028.tar file
    Solaris x86 8.1.4.0-IBM-APM-CORE-FRAMEWORK-SOLARIS_X86-IF0028.tar file
    Windows 64-bit 8.1.4.0-IBM-APM-CORE-FRAMEWORK-WIN64-IF0028.zip file
  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.
    1. Stop the agent.
    2. Log in as root, and run the slibclean command.
    3. Log in as the non-root user who installed the agent and then 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.
    Example     
    tar -xf 8.1.4.0-IBM-APM-CORE-FRAMEWORK-XLINUX-IF0028.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 the Linux and AIX operating systems. However, <APM agent install directory> is a required parameter on the Windows system.

Post-installation tasks

Post-installation tasks

Following are the necessary tasks after installing the agent core framework update.

A successful installation modifies the agent core framework version to 06.40.00.25, GS to Version 08.00.55.17, and the JRE to Version 08.08.30.00.

Linux, AIX

  • Ensure that the <APM-AGENT-HOME>/bin/cinfo -t output for the ax agent version is '06.40.00.25', the gs version is 08.00.55.17, and the jr version is 08.08.30.00.
  • The agent interim fix installation logs are written to the <APM-AGENT-HOME>/logs/ directory.

Windows

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

Known issues

Following is the list of the known issues.

  • The upgrade of the agent from version n-1 (preconfigured with Interim Fix 27 patch) to version n (preconfigured with Interim Fix 28 patch) is failing on the Windows platform.
    Symptoms -     When the n-1 agent is preconfigured with the Interim Fix 27 patch and installed on the Windows platform it gets successfully installed. But when version n agent is preconfigured with the Interim Fix 28 patch and the upgrade is done, the installation fails on the Windows platform. The JRE version gets upgraded, but the agent version is not getting upgraded.
    Workaround:     Manually stop the agent before an upgrade and after a successful upgrade start the agent. The agent successfully starts and the agent version is also upgraded.

  • APM Core Framework agent-side patch installation fails on the Windows 2025 platform.
    Symptoms - When 8.1.4.0-IBM-APM-CORE-FRAMEWORK-WIN64-IF0028 installation is done in the agent's candle home,  it gives an installation failed message on the command prompt. JRE version is also not upgraded. 
    Workaround: Manually add the following entry for the Windows Server 2025 support in the core framework component's pre-requisite files.

    regex{Windows Server 202[5].* (DataCenter|Standard|Essentials)}

    Following files need modification from the extracted agent side core framework patch.
    patches\inst\coreframework\prereqchecker\Windows\KGL_06400025
    patches\inst\core-framework\prereqchecker\Windows\KGS_08005517
    patches\inst\java\prereqchecker\Windows\KJM_08083000
    After modifying the above files restart the patch installation.

Known limitations

None

Uninstallation instructions

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

For more information, see:

[{"Type":"MASTER","Line of Business":{"code":"LOB67","label":"IT Automation \u0026 App Modernization"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSVJUL","label":"IBM Application Performance Management"},"ARM Category":[{"code":"a8m500000008b0KAAQ","label":"APM Agents-\u003EAgent Framework"}],"Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"All Versions"},{"Type":"MASTER","Line of Business":{"code":"LOB67","label":"IT Automation \u0026 App Modernization"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SS8G7U","label":"IBM Cloud App Management"},"ARM Category":[{"code":"a8m0z0000001idZAAQ","label":"Cloud App Management Server-\u003EDO NOT CREATE SPECIFIC AGENTS -USE APM"}],"Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"All Versions"}]

Document Information

Modified date:
29 January 2025

UID

ibm17181311

Page Feedback