IBM Tivoli Composite Application Manager for Transactions Internet Service Monitoring 7.4 Interim Fix 13 README Tivoli Composite Application Manager for Transactions 18.104.22.168 22.214.171.124-TIV-CAMIS-IF0013 Readme
Readme file for: 126.96.36.199-TIV-CAMIS-IF0013
Product/Component Release: 188.8.131.52
Update Name: 184.108.40.206-TIV-CAMIS-IF0013
Fix ID: 220.127.116.11-TIV-CAMIS-AIX-IF0013, 18.104.22.168-TIV-CAMIS-LINUX-IF0013, 22.214.171.124-TIV-CAMIS-SOLARIS-IF0013, 126.96.36.199-TIV-CAMIS-WINDOWS-IF0013
Publication Date: 3 Jul 2014
Last modified date: 3 Jul 2014
To download this update, you must first login to IBM Fix Central. Once logged in, you may select from the individual download packages.
Below is a list of components, platforms, and file names that apply to this Readme file.
|Tivoli Composite Application Manager for Transactions||AIX
|Tivoli Composite Application Manager for Transactions||Linux
|Tivoli Composite Application Manager for Transactions||Solaris
Prerequisites and co-requisites
This upgrade for ITCAM for Transactions Internet Service Monitoring supersedes 188.8.131.52 IF 3 and 184.108.40.206 IF 11 and may be applied to the following base versions.
For Windows 2008 SP2 you must first install the following Microsoft Patch:
You cannot run an application that is signed with a SHA-256 certificate on a computer that is running Windows Vista SP2 or Windows Server 2008 SP2
For up-to-date ITCAM for Transactions v7.4 software prerequisites, please visit:
Prerequisites for ITCAM for Transactions V7.4
For additional download packages or ITM support information, visit the ITM support portal at:
Non APAR Defect 13042 - ISM agent doesn't start after upgrading Windows BoxProblem Description
Non APAR Defect 10767 - ISM support file upgrades overwrites ismconfig.propsProblem Description
Change of Summarized DataProblem Description
Remote Deployment to Windows Running MTEMSProblem Description
SOAP Monitor Does Not Support Nested Arrays or multiRef ValuesProblem Description
For AIX, if upgrading from an ISM 6.0.1 release, you must uninstall the product and perform a new install. This does not apply for other ISM 6 releases. For more information, refer to the following support document:
For Linux 64-bit, if upgrading from the original ISM 220.127.116.11 release with no fix packs applied, you must uninstall the 18.104.22.168 ISM component and perform a new install. This does not apply to other releases. For more detailed information, refer to the following support document:
For Windows installation, if you encounter the message "Another version of this product is already installed" follow the instructions in the following support document to diagnose and resolve the problem. Note that although this technote refers to ITM, the diagnosing and resolving steps are applicable to ITCAM for Transactions Internet Service Monitoring.
Prior to installation
The update installer should perform the following steps for you automatically. You can, if necessary, perform them manually.
- Stop ITM agents and infrastructure (including TEMS and TEPS).
- Ensure the Databridge and Monitors have stopped.
1. Stop ITM agents and infrastructure (including TEMS and TEPS):
The ITM agents and infrastructure only need to be stopped when either the application support packages are being installed or ISM is being installed on the ITM machine. If ISM is being installed on a machine that does not contain any ITM infrastructure, the ITM infrastructure does not need to be stopped.
Use the Manage Tivoli Enterprise Monitoring Services (MTEMS) dialog or the command line tools (`ITM\bin\tacmd` or `ITM/bin/itmcmd`) to stop any running ITM agents or infrastructure (including TEMS and TEPS).
On Windows systems, you can start the MTEMS application from your Start menu or by running `ITM\InstallITM\kinconfg.exe`. Alternatively, if you have installed ITM, use the command `ITM\bin\tacmd stopAgent <type>`.
On UNIX systems, you can run MTEMS using the `ITM/bin/itmcmd manage` command. Alternatively, use the commands `ITM/bin/itmcmd agent stop <type>` and `ITM/bin/itmcmd server stop <TEMS name>`.
2. Ensure the Databridge and Monitors have stopped:
When the KISAgent is stopped, it automatically signals for the monitors and databridge to be shutdown. If this does not occur or has been disabled by configuration changes, you may need to perform this step manually.
On Windows systems use the Windows Services dialog to look for any 'NCO * Internet Service Monitor' services. To stop the databrige and monitors ensure that each of these 'NCO *' services are stopped.
On UNIX systems run `ps -ef |grep nco_m_` and issue a `kill <pid>` command for each entry shown. If the databridge or monitors were heavily loaded, they may take some time to shutdown. You may also use `kill -9 <pid>` to immediately stop the databridge or monitors, but this may result in loss or corruption of data being processed.
This maintenance package is applied directly to the Tivoli Enterprise Management Agent (TEMA). In addition, apply application support from this interim fix to the following ITM components:
- - Tivoli Enterprise Management Servers (TEMS), including any remote or failover TEMS configurations
- - Tivoli Enterprise Portal Server (TEPS)
- - Tivoli Enterprise Portal (TEP), including any locally installed desktop TEP clients
On Windows systems, extract the files from the archive and double-click WINDOWS\setup.exe. Follow the prompts to install the update.
On UNIX systems, extract the installer from the archive using the tar -xvf <filename.tar> command. Then, execute the installer using the ./install.sh command. Follow the prompts to install the update.
It is also possible to deploy this interim fix remotely using ITM TEMS depot and tacmd AddBundles command. For more information, please refer to the ITCAM for Transactions v22.214.171.124 Installation and Configuration Guide, available here:
Installing application support for TEPS/TEMS
For each monitoring agent installed, you must install agent-specific application support on IBM Tivoli Monitoring components. You can choose to install application support on all components at one time, or you can install the application support on components separately. If installing components separately, the following order is recommended:
- Tivoli Enterprise Monitoring Server
- Tivoli Enterprise Portal Server
- Tivoli Enterprise Portal Desktop Client
- Tivoli Enterprise Portal Server Browser client (for Linux and UNIX Only)
Note: When installing application support any ITM components on the current machine is automatically stopped, including any TEMS or TEPS. Follow the Starting and stopping servers and agents guide to manually stop ITM agents and infrastructure. You should warn other users before beginning the installation.
For step by step application support installation information refer to the documentation:
Installing Internet Service Monitoring on Windows systems
Installing on Linux or UNIX systems
Performing the necessary tasks after installation
A successful installation modifies the ISM version to 126.96.36.199. Ensure that the Version of Internet Service Monitoring in the MTEMS is '07.40.00.13'.
On Windows the installation logs are written to the following directory:
On Unix the installation logs are written to the following directory:
Troubleshooting installation problems from the Support site
For more detailed information, refer to the Installation and Configuration Guide:
Uninstalling if necessary
This maintenance package cannot be rolled back.
On Windows, you must run the following command prior to uninstalling the product to remove the Windows Services created during the install:
The product may then be removed using the Control Panel's Add/Remove Programs.
On UNIX,the product may be removed using the script:
For detailed instructions, please refer to the ITCAM for Transactions v188.8.131.52 Installation and Configuration Guide, available here:
The Secure Hash Algorithm 1 (SHA1) checksum of the images are as follows:
The ITM kisagent logs show that the Release ID of this interim fix is: ITCAM_ISM_7.4_Integration,ITCAM_ISM_184.108.40.206_0129
The following new features are included in ITCAM for Transactions Internet Service Monitoring 7.4 Interim Fix 13:
- Security Fixes - Security Bulletin: IBM Tivoli Composite Application Manager for Transactions is affected by the following OpenSSL vulnerabilities: (CVE-2014-0224, CVE-2014-0221, CVE-2014-0195 and CVE-2014-3470)
- Security Fixes - Security Bulletin: IBM Tivoli Composite Application Manager for Transactions is affected by Elevated privileges vulnerability (CVE-2014-0907)
- Security Fixes - Security Bulletin: IBM Tivoli Composite Application Manager for Transactions is affected by vulnerabilities in OpenSSL (CVE-2014-0160 and CVE-2014-0076)
- Security Fixes - Security Bulletin: IBM Tivoli Composite Application Manager for Transactions is affected by vulnerabilities in OpenSSL (CVE-2013-4353, CVE-2013-6450 and CVE-2013-6449)
- Multi user ISM configuration - RFE 13434 - Multi user ISM configuration.
List of fixes
A) APAR Content:
IV55317 Parenthesis ( and ) are not supported in ISM 7.4 for OID group names.
IV57413 ISM OBJECT SERVER MODULE ON WINDOWS DOES NOT CONNECT TO SECURE OBJECT SERVER MODULE.
IV59957 MULTIPLE CONTENT TYPE HEADERS IN A HTTP RESPONSE CAN CAUSE THE ISM HTTP(S) MONITOR TO CRASH.
IV60157 UNDER TRANSX HTTP(S) COOKIES CAN'T BE TRANSFERRED BETWEEN STEPS.
IV60769 IF0011 KIS_RESOURCES.JAR HAS INCORRECT VERSION INFO RESULTING IN APPLICATION SUPPORT MISMATCH ERROR.
From superseded fixes:
IV44842 ISM monitors such as HTTPS and SOAP may crash on AIX
IV46127 HTTP and HTTPS Core dumps.
IV46773 Invalid data passed into the KISAgent can cause a core dump
IV46786 SOAP monitor can create duplicate namespaces in SOAP messages
IV47366 ismconfig is unable to connect to ITM using secure ports
IV49848 NTP monitor returns incorrect offset values
IV49869 Large cookies can cause TRANSX ISM monitor to crash with core
IV50219 ISM NCO__M_<monitor> may produce core file when ISM agent is stopped, if monitor is too slow to stop
IV52160 Failure retests do not get executed on the SIP monitor
IV52162 ISM SIP monitor can crash at the end of a test
IV53691 NTLM doesn't work with Long DomainName host combos
IV54496 KIS SDA FAILING ON ZOS RETURN_CODE 129 REASON=62 QUALIFIER=562
IV54952 AN ISM ELEMENT WITH NO SLC GROUP WILL CAUSE THE MONITOR TO REFUSE TO LOAD THE CONFIGURATION
IV55578 ISM Config CLI does not create OIDs in oidgroup correctly when making a SNMP profile via CLI.
IV55810 ISM Config GUI is very slow when there are MANY Profiles
IV56117 ISM MONITORS NEED TO BE ABLE TO DISABLE TLS 1.2 AND TLS 1.1 FOR COMPATIBILITY WITH OLDER CRYPTOGRAPHY IMPLEMENTATIONS
IV56387 ICMP Monitor Monitoring periods do not work.
IV56684 ISM DNS MONITOR TRANSACTION ID IS ALWAYS SET TO ZERO.
IV57345 WHEN HTTP/S MONITOR HAS THE OUTPUTRESULT PROPERTY ENABLED LONG URLS CAN CAUSE THE MONTOR TO CRASH
B) Additional Non APAR Defects:
From superseded fixes:
19176 improper message for Resync Agent - Resyncing an this agent will cause locally stored profiles to be removed
18874 ismconfig cli failed to copy profile
19744 the later ismconfig gui overwrites the previous gui's the same named profile under specific steps
19745 the later ismconfig gui can not display the previous gui created element for the same profile under specific steps
19769 The profile still exist after cancelling copy profile.
19771 The profile still exist after cancelling creating profile
19901 Failure to delete and copy ISM profiles on ISM Configuration GUI
20061 The parameters and Regexp data lost in the transx http step after reopen the ISM GUI.
From superseded fixes:
19790 Add new CLIConfig command to bulk unlock profiles
Document change history
|Version||Date||Description of change|
|1.0||19 June 2014||Initial Version|
|1.1||23 June 2014||Added Build Number|
|1.2||3 July 2014||Update APAR Info|