Download
Abstract
This fix pack updates the IBM Tivoli Monitoring framework component, the IBM SDK Java Technology Edition Java Runtime Environment (JRE), and the Java and MS Authenticode certificates.
Download Description
(C) Copyright International Business Machines Corporation 2018.
All rights reserved.
Component: Tivoli® Log File Agent,
Version 6.3.0
Component ID: 5724C04LF
Fix Pack: 0003, 6.3.0-TIV-ITM_LFA-FP0003
Date: October 3, 2018
Contents:
1.0 General description
2.0 Problems fixed
3.0 Architecture and prerequisites
4.0 Image directory contents
5.0 Installation instructions
6.0 Additional installation information
7.0 Known problems and work-arounds
8.0 Additional product information
9.0 Copyright and trademark information
10.0 Notices
1.0 General description
===============
This fix pack updates the IBM Tivoli Monitoring framework component,
the IBM SDK Java Technology Edition Java Runtime Environment (JRE),
and the Java and MS Authenticode certificates.
NOTE: See section 3.0 Architecture and prerequisites.
In addition, it resolves the APARs and defects listed in the
"Problems Fixed" section below and includes the superseded fixes
listed in section 2.4.
2.0 Problems fixed
============
The following problems are addressed by this fix.
2.1 APARs
-------------
APAR: IJ06011
Abstract: LOG FILE AGENT DETECTS AN EVENT WITH A DIFFERENT FORMAT
BECAUSE A LOG ENTRY IS TRUNCATED AT THE MIDDLE OF A LINE.
Additional information: When monitoring a log file along with
Windows Event logs, a truncated event might be detected with
an unexpected format or not detected at all, depending on the
data and formats used. This occurs because multiple lines are
being read in at one time and the truncated line is all that
fits in the end of the read buffer. The truncated or partial
record is then processed as if it was complete.
The reading of multiple lines, even though there are no multi-
line formats, is correctly triggered because of the Windows
Event Log monitoring. However, the truncated or partial record
should have been saved until the complete line is read in,
before processing it for a match.
This is related to changes made for APAR IV82170 in Fix Pack 01.
2.2 Defects
--------------
None.
2.3 Enhancements
----------------------
Enhancement: 218733
Abstract: Uplift TEMA, and JRE to v6.2.3 FP5 and certificates
Additional Information: This fix pack includes updates to the
following components which might be installed into the
IBM Tivoli Monitoring installation directory (for example,
CANDLEHOME), if a higher version does not already exist.
- IBM Tivoli Monitoring framework (ax/gl) component to version
6.2.3 Fix Pack 0005. This raises the prequisite level. See
section 3.0 Architecture and prerequisites.
- IBM SDK Java Technology Edition Java Runtime Environment (JRE).
For all platforms, except PowerPC little-endian,
the JVM (64-bit) version is: 06.16.65.00.
For PowerPC little-endian (lpl266), IBM Tivoli Monitoring v6.3.0
and above, the JVM version is: 07.10.25.00.
- Updated Java and MS Authenticode (jar) signing certificates.
These certificates are fully SHA-2.
2.4 Superseded fixes
-------------------------
6.3.0-TIV-ITM_LFA-FP0002
6.3.0-TIV-ITM_LFA-FP0001
6.3.0-TIV-ITM_LFA-IF0005
6.3.0-TIV-ITM_LFA-IF0004
6.3.0-TIV-ITM_LFA-IF0003
6.3.0-TIV-ITM_LFA-IF0002
6.3.0-TIV-ITM_LFA-IF0001
2.5 APARs and defects included from superseded fixes
---------------------------------------------------------------
See 6.3.0-TIV-ITM_LFA-FP0002.README for a complete list of all
APARs and fixes included from superseded fixes.
3.0 Architecture and prerequisites
======================
This fix is supported on all operating systems listed in the Tivoli
Log File Agent User's Guide, version 6.3.0.
The following link is for the Tivoli operating system and application
support matrix. Please refer to this matrix for the latest
certification information.
Please refer to the IBM Software Product Compatibility Reports (SPCR)
for the latest operating system certification information:
http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.html
3.1 Prerequisites for this fix
--------------------------------
The prerequisite level for this fix is as follows:
- IBM Tivoli Monitoring 6.2.3 Fix Pack 5 (6.2.3-TIV-ITM-FP0005)
This fix pack is a complete install image and as such, can be
installed on a pristine system. This fix is also cumulative, and can
be installed on any fix level for this version, release, and mod
level above the prerequisite.
For details, see the Troubleshooting Wiki:
https://www.ibm.com/developerworks/mydeveloperworks/wikis/home?lang=en#/wiki/Tivoli%20Monitoring/page/Log%20File%20Agent
4.0 Image directory contents
====================
This fix image contains the following files:
- 6.30-TIV-ITM_LFA-FP0003.tar.gz
- 6.30-TIV-ITM_LFA-FP0003.README
5.0 Installation instructions
==================
5.1 Before installing the fix
-------------------------------
- The prerequisites listed under section 3.1 entitled 'Prerequisites
for this fix' must be installed before this fix can be installed.
- For the purpose of this README, the symbol <CANDLEHOME> is the
IBM Tivoli Monitoring installation directory. The default value
for CANDLEHOME is '/opt/IBM/ITM' on UNIX systems and 'C:\IBM\ITM'
on Windows systems.
- Before installing this fix on UNIX systems, set the environment
variable CANDLEHOME to the IBM Tivoli Monitoring installation
directory.
For example:
> CANDLEHOME=/opt/IBM/ITM
> export CANDLEHOME
- Because there is no uninstall utility for this fix, make sure to
perform a backup of your environment before installing this fix.
- NOTE: Before installing the LO x86-64 bit agent, you must
un-install the WINNT 32-bit version of the agent and the 32/64
bit compatibility package.
5.2 Local agent update
--------------------------
For installation instructions, see the Log File Agent User's Guide
v6.3.0:
http://www.ibm.com/support/knowledgecenter/SSTFXA_6.3.0/com.ibm.itm.doc_6.3/logfile/logfileagent_user.htm?lang=en
Note:
1. The PowerPC little-endian installation image is located in the
PPC_LE directory of the installation image. Invoke ./install.sh
from this directory.
2. On Windows systems, when the installation completes, the
Readme.txt displays "Welcome to IBM Tivoli Monitoring V6.2.3 Fix
Pack 5." This is the installer level and Readme and is not an
error.
5.3 Remote agent update
----------------------------
1. Transfer the archive file 6.3.0-TIV-ITM_LFA-FP0003.tar.gz to a
temporary directory on the IBM Tivoli Enterprise Monitoring
Server system. For the purpose of this README, the symbol <TEMP>
represents the fully qualified path to this directory. Note: On
Windows systems, this path includes the drive letter.
2. Expand the archive file using the "tar" command on UNIX systems or
an extract utility on Windows systems. This step creates a directory
structure that contains fixes for all of the supported platforms.
3. To add the agent fix bundles into the remote deploy depot, use
the "tacmd addBundles" command found in $CANDLEHOME/bin on UNIX
systems or in %CANDLE_HOME%\bin on Windows systems. For more
information on the "tacmd addBundles" command, see the IBM Tivoli
Monitoring Administrator's Guide.
Note:
1. The prerequisite Log File Agent bundles must also be in the
depot, to ensure successful completion of the remote agent update.
2. The 6.3.0-TIV-ITM_LFA-FP000<n> bundles must be removed from the
depot, using the "tacmd removeBundles" command.
For example: tacmd removeBundles -t lo -v 06300000<n>
On UNIX systems,
if the fix was expanded to <TEMP>/KLO_DVD-201809270938-82701:
> $CANDLEHOME/bin/tacmd addBundles -n
-i <TEMP>/KLO_DVD-201809270938-82701
On Windows systems,
if the fix was expanded to <TEMP>\KLO_DVD-201809270938-82701:
> %CANDLE_HOME%\bin\tacmd addBundles -n
-i <TEMP>\KLO_DVD-201809270938-82701
where:
-n indicates that prerequisite bundles are not automatically
added. The -n parameter must be used because the fix
directory does not contain any prerequisites that the fix
might require. Please see Section 3.1 for the prerequisites
for this fix.
-i is the directory that contains the deployment bundles to be
added to the depot.
4. To log in to the Tivoli Enterprise Monitoring server, and deploy
the fix to the appropriate nodes where the agent is running, use
the following "tacmd" commands. For more information on the
"tacmd login" and "tacmd updateAgent" commands, see the IBM Tivoli
Monitoring Administrator's Guide.
On UNIX systems:
> $CANDLEHOME/bin/tacmd login -s <server>
-u <itmuser>
-p <password>
> $CANDLEHOME/bin/tacmd listSystems
The output shows the Managed System Name for the OS agent on the
remote system to be updated. Use this value as the target of the
"tacmd updateAgent" command.
> $CANDLEHOME/bin/tacmd updateAgent -t lo
-n <Managed system name>
-v 06300300
On Windows systems:
> %CANDLE_HOME%\bin\tacmd login -s <server>
-u <itmuser>
-p <password>
> %CANDLE_HOME%\bin\tacmd listSystems
The output shows the Managed System Name for the OS agent on the
remote system to be updated. Use this value as the target of the
"tacmd updateAgent" command.
> %CANDLE_HOME%\bin\tacmd updateAgent -t LO
-n <Managed system name>
-v 06300300
Note:
- The component (-t) for the "tacmd updateAgent" command is
specified as two characters (LO), not three characters (KLO).
- The node (-n) for the "tacmd updateAgent" command is the managed
system name of the operating system (OS) agent to be updated.
The target node for the "tacmd updateAgent" command is always
an OS agent.
5.4 Agent support update
------------------------------
Fix pack 6.3.0-TIV-ITM_LFA-FP0003 includes new certificates
in the agent support files which need to be installed. If you have
already installed these updates, there are no additional installation
steps. Otherwise, install the updates to the Tivoli Enterprise
Monitoring Server, Tivoli Enterprise Portal Server, or Tivoli
Enterprise Portal Desktop. For more information about installing
application support, see Installing and enabling application support
in the IBM Tivoli Monitoring Installation and Setup Guide.
6.0 Additional installation information
========================
6.1 Installation instructions for agent baroc file
-----------------------------------------------------
There are no updates to the baroc files included in this fix or any
of the superseded fixes. No additional installation steps are
required.
6.2 Verifying the update
----------------------------
1. To verify the agent was updated correctly, use the "tacmd" command
to view the agent's current version after the agent is restarted.
You are required to log in to a Tivoli Enterprise Monitoring
Server prior to viewing the agent version.
For example:
On UNIX systems, where $CANDLEHOME is the IBM Tivoli Monitoring
installation directory, the default location is '/opt/IBM/ITM'.
> $CANDLEHOME/bin/tacmd login -s <server>
-u <itmuser>
-p <password>
> $CANDLEHOME/bin/tacmd listSystems -t LO
On Windows systems, where %CANDLE_HOME% is the IBM Tivoli
Monitoring installation directory, the default location
is 'C:\IBM\ITM'.
> %CANDLE_HOME%\bin\tacmd login -s <server>
-u <itmuser>
-p <password>
> %CANDLE_HOME%\bin\tacmd listSystems -t LO
Note: The component (-t) for the "tacmd listSystems" command is
specified as two characters (LO), not three characters (KLO).
When the agent update is successful, the agent version is:
06.30.03.00.
After the agent is restarted, you can also use the GUI to verify
the agent was successfully updated.
For the agent on Windows systems, the version number is
06.30.03.00.
2. To verify all the agent components were updated correctly, use
the "cinfo" command on Linux or UNIX systems or the "kincinfo"
command on Windows systems. The sample output below shows the
minimum versions of IBM Tivoli Monitoring framework component,
IBM SDK Java Technology Edition Java Runtime Environment (JRE),
and the LO component versions of the Tivoli Enterprise Portal
Server, Tivoli Enterprise Monitoring Server, and Tivoli
Enterprise Portal Desktop after this fix pack has been
successfully installed.
Note: The displayed date of the build might not be accurate. This
is a known problem.
On UNIX or Linux systems (except PowerPC little-endian):
---------------------------------------------------------
To validate that all components have been installed, run the
following command:
./cinfo -i
For example:
> $CANDLEHOME/bin/cinfo -i
*********** Wed Sep 27 23:42:54 WST 2018 ******************
User: root Groups: root ...
Host name : linux100 Installer Lvl:06.23.05.00
CandleHome: /opt/IBM/ITM
***********************************************************
...Product inventory
ax IBM Tivoli Monitoring Shared Libraries
li6263 Version: 06.23.05.00
gs IBM GSKit Security Interface
li6243 Version: 07.40.47.00
jr Tivoli Enterprise-supplied JRE
li6263 Version: 06.16.65.00
lo Tivoli Log File Agent
li6263 Version: 06.30.03.00
ui Tivoli Enterprise Services User Interface
li6263 Version: 06.23.05.00
On PowerPC little-endian systems:
---------------------------
# /opt/IBM/ITM/bin/cinfo -i
*********** Wed Sep 27 11:50:10 EDT 2018 ******************
User: root Groups: root
Host name : ppcLe01 Installer Lvl:06.30.07.00
CandleHome: /opt/IBM/ITM
***********************************************************
...Product inventory
ax IBM Tivoli Monitoring Shared Libraries
lpl266 Version: 06.30.07.00
gs IBM GSKit Security Interface
lpl266 Version: 08.00.50.69
jr Tivoli Enterprise-supplied JRE
lpl266 Version: 07.10.25.00
lo Tivoli Log File Agent
lpl266 Version: 06.30.03.00
lz Monitoring Agent for Linux OS
lpl266 Version: 06.30.07.00
ui Tivoli Enterprise Services User Interface
lpl266 Version: 06.30.07.00
On Windows systems:
---------------------
To validate that all components have been installed, run the
following command:
kincinfo -i
For example:
> %CANDLE_HOME%\InstallITM\kincinfo -i
********* Wednesday, September 27, 2018 11:53:04 AM *********
User : admin Group : NA
Host Name : WINSERVER Installer : Ver: 062305000
CandleHome : C:\IBM\ITM
Installitm : C:\IBM\ITM\InstallITM
*************************************************************
...Product Inventory
IN Install INS/Windows Install Component
WINNT Version: 06.23.05.00 Build: 201402060625
IN TEMA(32-bit) INS/ITM 6.x Agent Install Component
WINNT Version: 06.23.05.00 Build: 201402060625
IN TEMA(64-bit) INS/ITM 6.x Agent Install Component Extensions
WINNT Version: 06.23.05.00 Build: 201402060625
AC KAC(64-bit) CMA/32/64 Bit Agent Compatibility Package
WIX64 Version: 06.23.05.00 Build: 201402060625
GL KGL(64-bit) CMA/Tivoli Enterprise Monitoring Agent Framework
WIX64 Version: 06.23.05.00 Build: d4099a
GL KGL(32-bit) CMA/Tivoli Enterprise Monitoring Agent Framework
WINNT Version: 06.23.05.00 Build: d4099a
GS KGS(64-bit) GSK/IBM GSKit Security Interface
WIX64 Version: 07.40.47.00 Build: d4029a
GS KGS(32-bit) GSK/IBM GSKit Security Interface
WINNT Version: 07.40.47.00 Build: d4029a
IN KIN(32-bit) INS/IBM Tivoli Base Windows Installer
WINNT Version: 06.23.05.00 Build: 201402060625
JM KJM(32-bit) JVM/Embedded JVM
WINNT Version: 05.09.00.00 Build: d0111a
JM KJM(64-bit) JVM/Embedded JVM
WIX64 Version: 06.16.65.00 Build: 201806061413
LO KLO(64-bit) CMA/Tivoli Log File Agent
WIX64 Version: 06.30.03.00 Build: 201809271341
LO TEMS App Support/Tivoli Log File Agent
WINNT Version: 06.30.03.00 Build: 201809271341
LO TEPS App Support/Tivoli Log File Agent
WINNT Version: 06.30.03.00 Build: 201809271341
LO TEPB App Support/Tivoli Log File Agent
WINNT Version: 06.30.03.00 Build: 201809271341
LO TEPD App Support/Tivoli Log File Agent
WINNT Version: 06.30.03.00 Build: 201809271341
UI KUI(32-bit) CLI/Tivoli Enterprise Services User Interface
WINNT Version: 06.23.05.00 Build: 201402060625
Note: For additional updates to the JM component, see section 7.0
Known problems and workarounds.
3. To verify the agent you are running contains the updates from the
fix, see the following lines in the agent log
<hostname>_lo_<instance>_kloagent_<timestamp>.log located in
$CANDLEHOME/logs on UNIX systems and
%CANDLE_HOME%\tmaitm6\logs on Windows systems:
<timestamp> Component: ira
<timestamp> Driver: agent_fac_63:201809261709/...
<timestamp> Timestamp: Sep 26 2018 ...
7.0 Known problems and work-arounds
=========================
- Problem: After installing the fix pack on Windows systems with an
IBM Tivoli Monitoring v6.2.3 FPnn base install, an obsolete
KJM(32-bit) JVM/Embedded JVM is not updated nor removed.
For example, the cinfo output shows:
JM KJM(32-bit) JVM/Embedded JVM
WINNT Version: 05.09.00.00 Build: d0111a
Work-around: Install the IBM Tivoli Monitoring 6 JRE Update
(6.X.X-TIV-ITM_JRE_CANDLEHOME-20180726) to update
obsolete 32-bit JVM component to the latest PSIRT
version/level.
8.0 Additional product information
======================
None.
9.0 Copyright and trademark information
==================================
A current list of IBM trademarks is available on the Web at "Copyright
and trademark information" at www.ibm.com/legal/copytrade.shtml.
10.0 Notices
=======
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION
"AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Some jurisdictions do not allow disclaimer of express or implied
warranties in certain transactions, therefore, this statement may not
apply to you.
This information could include technical inaccuracies or typographical
errors. Changes are periodically made to the information herein; these
changes will be incorporated in new editions of the publication. IBM
may make improvements and/or changes in the product(s) and/or the
program(s) described in this publication at any time without notice.
Microsoft, Windows, and Windows Server are trademarks of Microsoft
Corporation in the United States, other countries, or both.
Java and all Java-based trademarks and logos are trademarks or
registered trademarks of Oracle and/or its affiliates.
UNIX is a registered trademark of The Open Group in the United States
and other countries.
Linux is a registered trademark of Linus Torvalds in the United States,
other countries, or both.
Other company, product, or service names may be trademarks or service
marks of others.
Third-Party License Terms and Conditions, Notices and Information
-----------------------------------------------------------------
The license agreement for this product refers you to this file for
details concerning terms and conditions applicable to third party
software code included in this product, and for certain notices and
other information IBM must provide to you under its license to
certain software code. The relevant terms and conditions, notices and
other information are provided or referenced below. Please note that
any non-English version of the licenses below is unofficial and is
provided to you for your convenience only. The English version of the
licenses below, provided as part of the English version of this file,
is the official version.
Notwithstanding the terms and conditions of any other agreement you
may have with IBM or any of its related or affiliated entities
(collectively "IBM"), the third party software code identified below
are "Excluded Components" and are subject to the following terms and
conditions:
- the Excluded Components are provided on an "AS IS" basis
- IBM DISCLAIMS ANY AND ALL EXPRESS AND IMPLIED WARRANTIES AND
CONDITIONS WITH RESPECT TO THE EXCLUDED COMPONENTS, INCLUDING, BUT
NOT LIMITED TO, THE WARRANTY OF NON-INFRINGEMENT OR INTERFERENCE
AND THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE
- IBM will not be liable to you or indemnify you for any claims
related to the Excluded Components
- IBM will not be liable for any direct, indirect, incidental,
special, exemplary, punitive or consequential damages with respect
to the Excluded Components.
Prerequisites
The prerequisite level for this fix is as follows:
- IBM Tivoli Monitoring 6.2.3 Fix Pack 5 (6.2.3-TIV-ITM-FP0005)
This fix pack is a complete install image and as such, can be
installed on a pristine system. This fix is also cumulative, and can
be installed on any fix level for this version, release, and mod
level above the prerequisite.
Installation Instructions
Please refer to the full README contained in the Download Description section above for general installation instructions.
Product Synonym
log adapter, logfile
Problems (APARS) fixed
Was this topic helpful?
Document Information
Modified date:
08 October 2018
UID
ibm10734043