IBM Tivoli Composite Application Manager for Transactions Internet Service Monitoring 7.2.0.3 Interim Fix 26 README Tivoli Composite Application Manager for Transactions 7.2.0.3 7.2.0.3-TIV-CAMIS-IF0026 Readme

To download this update, you must first login to IBM Fix Central. Once logged in, you may select from the individual download packages.
http://www.ibm.com/support/fixcentral/

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

This upgrade for ITCAM for Transactions Internet Service Monitoring may be applied to the following base versions.

• 7.2.0.3

For up-to-date ITCAM for Transactions v7.2.0.3 software prerequisites, please visit:
Prerequisites for ITCAM for Transactions V7.2.0.3

ITM Minimum Prerequisites for this MDV:
Same requirements as ITCAM for Transactions v7.2.
For more information refer to the Compatible software for ITCAM for Transcations 7.2.0.3

For additional download packages or ITM support information, visit the ITM support portal at:
http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Monitoring_V6

*******************************************************************
* A change introduced by this Fix Pack might negatively
* affect existing product function.
*
* Please refer to APAR(s) IV12935 for a description of the
* problem(s) and corrective action(s).
*
* Evaluate these APARs for the potential impact in your environment.
*******************************************************************

Using old profiles on ISM 7.2 or aboveProfiles may need to be resynced after upgrade, see here for more information:
https://www-304.ibm.com/support/docview.wss?uid=swg21507274

Change of Summarized Data

Remote Deployment to Windows Running MTEMS

SOAP Monitor Does Not Support Nested Arrays or multiRef Values

WMS monitor is not supported on Windows 2008

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:
http://www-01.ibm.com/support/docview.wss?uid=swg21321186

For Linux 64-bit, if upgrading from the original ISM 7.1.0.0 release with no fix packs applied, you must uninstall the 7.1.0.0 ISM component and perform a new install. This does not apply to other releases. For more detailed information, refer to the following support document:
http://www-01.ibm.com/support/docview.wss?uid=swg21330976

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.
http://www-01.ibm.com/support/docview.wss?uid=swg21587068

Prior to installation

The update installer should perform the following steps for you automatically. You can, if necessary, perform them manually.

1. Stop ITM agents and infrastructure (including TEMS and TEPS).
2. 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.

Installing

This maintenance package is applied directly to the Tivoli Enterprise Management Agent (TEMA). In addition, apply application support from this fixpack 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 fixpack remotely using ITM TEMS depot and tacmd AddBundles command. For more information, please refer to the ITCAM for Transactions v7.2.0.2 Installation and Configuration Guide, available here:
http://publib.boulder.ibm.com/infocenter/tivihelp/v24r1/topic/com.ibm.itcamt.doc_7.2.0.2/rt/Install_Guide/remotedeploy.html
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:

1. Tivoli Enterprise Monitoring Server
2. Tivoli Enterprise Portal Server
3. Tivoli Enterprise Portal Desktop Client
4. Tivoli Enterprise Portal Server Browser client (for Linux and UNIX Only)

Performing the necessary tasks after installation

A successful installation modifies the ISM version to 7.2.0.3. Ensure that the Version of Internet Service Monitoring in the MTEMS is '07.20.03.23'.

On Windows the installation logs are written to the following directory:
ITM\InstallITM\

On Unix the installation logs are written to the following directory:
ITM/logs/

Troubleshooting installation problems from the Support site

For more detailed information, refer to the Installation and Configuration Guide:
http://publib.boulder.ibm.com/infocenter/tivihelp/v24r1/topic/com.ibm.itcamt.doc_7.2.0.2/ism/dita/ag/topic/ISM_install_chapter.html

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:
ITM\TMAITM6\ism\platform\win32\bin\preuninstall.cmd
The product may then be removed using the Control Panel's Add/Remove Programs.

On UNIX,the product may be removed using the script:
ITM/bin/uninstall.sh

For detailed instructions, please refer to the ITCAM for Transactions v7.2.0.2 Installation and Configuration Guide, available here:
http://publib.boulder.ibm.com/infocenter/tivihelp/v24r1/topic/com.ibm.itcamt.doc_7.2.0.2/ism/dita/ag/topic/ISM_uninstall_chapter.html

The Secure Hash Algorithm 1 (SHA1) checksum of the images are as follows:
SHA1(7.2.0.3-TIV-CAMIS-AIX-IF0026.tar)= 1cef0007c19164c0150b98b452680c0c088ff27a
SHA1(7.2.0.3-TIV-CAMIS-Linux-IF0026.tar)= 97f0486a60fb1e68398fb3f0a5588fc87f08daa5
SHA1(7.2.0.3-TIV-CAMIS-Solaris-IF0026.tar)= 6cb222aaf9ffa1c02ae53b55db5dd74619de9b1d
SHA1(7.2.0.3-TIV-CAMIS-Windows-IF0026.zip)= 5ac1cae1f7ffe6b903db7d83eeb57fd52585ee9f

New Features

The following new features are included in ITCAM for Transactions Internet Service Monitoring 7.2.0.3 IFix 26:

• 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 Elevated privileges vulnerability (CVE-2014-0907)
• 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)

• Security Fixes - Security Bulletin: IBM Tivoli Composite Application Monitoring for Transactions is affected by multiple OpenSSL vulnerabilities

A) APAR Content:

N/A

From superseded fixes:

IV00137 ITCAM ISM ICMP MONITOR DOES NOT HONOUR PACKET INTERVAL SETTING FOR AN ELEMENT
IV01021 PROFILE SCHEDULE OPTION NOT WORKING FOR TRANSX MONITORS
IV02077 EVERY POLL RESULT ARE SENT TO ITM RATHER THAN THE LAST TEST OF THE POLL
IV03671 ISM HTTP(S) PROXY INFORMATION IS LOST AFTER MODIFYING HTTP(S) PROFILE
IV15338 ISM 7.2 Config GUI thinks ITM 6.2.2 Derby Database is DB2
IV38087 SECURITY APAR CVE MULTIPLE OPENSSL VULNERABILITIES
IZ62276 SNMP MONITOR DOES NOT USE IPADDRESS PROPERTY
IZ63477 HOST COLUMN DISPLAYS HTTP PROXY NAME INSTEAD OF ENDPOINT SERVER NAME
IZ63803 SIZE LIMITATION OF DESCRIPTION FIELD ENFORCED TO PREVENT TRUNCATION
IZ64416 SOAP MONITOR TO HANDLE NAMESPACE REQUIREMENTS AND EMPTY MESSAGES
IZ65350 REMOVED WARNINGS ABOUT UNRECOGNIZED SLC CONDITION 'IGNORE'
IZ66116 BRIDGE, AGENT AND MONITORS ENTER RECONNECT LOOP WITH 4096 BYTE EVENTS
IZ67329 UNABLE TO USE CHINESE CHARACTERS IN RULES FILES
IZ67379 LDAP FAILURE WHEN CONNECTION TO MULTIPLE SSL SERVERS
IZ67839 CONFIG TOOL DID NOT SAVE CHANGES WHEN JUST THE SLC WAS MODIFIED
IZ68001 BRIDGE, AGENT AND MONITORS ENTER RECONNECT LOOP WITH 4096 BYTE STRINGS
IZ68181 GUI QUERY OF DB2 SYSTOOLS.POLICY CAUSES MANY TEPS ERRORS
IZ69681 HTTP/S HANG DURING REGEXPS, WAITING FOR ALL CONNECTIONS TO CLOSE
IZ70031 SNMP MAY NOT RESOLVE OID INDEXES
IZ71076 HTTP/S UNABLE TO CONFIGURE PROXY NO-CACHE OPTION IN GUI
IZ72151 KISAGENT HISTORY FILES BECOME CORRUPTED ON JANUARY 1ST
IZ73215 ICMP FAILS TO RESOLVE HOSTNAMES ON SOLARIS 9
IZ74141 DOCUMENTATION ERRONEOUSLY STATED THAT YOU CAN MODIFY SMTP SUBJECT
IZ75530 HTTPS MONITOR CORES WHEN CALCULATING COOKIE EXPIRY (AIX 6.1)
IZ77654 GAPS IN AMC/KT3 DATA FOR ISM
IZ78116 ERRORS ENCOUNTERED WHEN MIGRATING ISM 2.4 PROFILES TO 7.2
IZ80288 DUPLICATE RADIUS 'L' COLUMN
IZ80387 ISM IS NO LONGER USING DELTA CALCULATIONS FOR SUMMARIZATION
IZ81470 PREVENT CUSTOM ACTIONS BREAKING THE AGENT
IZ82384 ISM POP3 SPECIFIC METRICS SHOULD BE IN EMAIL HEADER NOT BODY
IZ83484 MONITORS PROCESSING OF INVALID AND/OR MALFORMED COOKIES
IZ85741 HTTP MONITOR CORES IF USING INCORRECT REGULAR EXPRESSION USING REG EXP 1="((?!GENY).)*" IN PROFILE/ELEMENT
IZ87532 MONITOR READS PROFILE BEFORE ISMBATCH IS COMPLETE ON RESYNCH
IZ88650 ISM CONFIG GUI SNMP OBJECTGROUPNAMES ARE UNSORTED
IZ89288 ICMP MONITOR DOES NOT ALLOW A PACKET SIZE GREATER THAN 64 BYTES
IZ91309 THE ICMP MONITOR DOES NOT UPDATE PING SENDTIME ON SUBSEQUENT SAMPLES
IZ92920 ISM MONITORS CAN CORE WHEN A RANGE BASED DVC VALUE IS SPECIFIED
IZ95887 MONITORS RUN BY TRANSX CAN CRASH IF ELEMENTS SENT BACK ARE TOO LARGE
IZ97327 ISM CONFIG GUI NOT DEPLOYING OIDGROUP WITH SPACE OR - CHARACTER

B) Additional Non APAR Defects:

None
From superseded fixes:

3164 SNMP failed to bind to second IPv6 address
3165 ICMP pauses polling if host names do not resolve
3515 ismbatch returns successful while there is an error within the line
3833 ISM throws an internal error using Derby DB on ITM 6.2.2 FP2
3854 IPv6 address not working with HTTP pointing to an IIS page
3899 ISM does not upgrade table columns using Derby DB on ITM 6.2.2 FP2
3908 ICMP: TotalTime field does not include LookupTime
4112 RADIUS service is named differently to other monitors in Windows
4124 TRANSX HTTP/S Parameters Value is inconsistent
4126 TRANSX HTTP/S Parameter's Value is not always a list if DYNAMIC type is chosen
4385 Memory consumption constantly increasing for HTTP agent under constant load. (Memory leak)
4426 LDAP monitor tests causing connection timeout failures on Windows
4451 Scheduling Not Working For Saturdays
00003163 sip monitor should accept port as a parameter
00012090 Progress bar for config tool load screen
00015797 Transx HTTP steps don't provide an option to enable dynamiccontent
00019636 Dynamic Content not matching names successfully
00021322 Transx is logging weirdly
00022173 Soap Monitor profile inputs will silently continue if the first parameter element has an error and the second doesn't.
00022178 SOAP Monitor isn't able to test SOAP services without inputs like axis2 getVersion
00022189 SAA SNA Element History drill down link is labelled incorrectly
00019934 HTTP/S always used the initial hostname to choose cookies
00019936 HTTP/S Transx cookie values overwritten by initial value after a redirect
00019938 HTTP/S cookie domains should not be case sensitive
00019947 Corrected logging level of "hostname: Opening connection to port xxx" message
00019948 Unable to set HTTPS proxy port to a value below 65535
00020286 SAA reported totalTime values 1000 times smaller than actual
00020746 DHCP monitor was not started automatically by KISAgent
00021391 ProfileUpgrade removes HTTP parameter types

C) Enhancements

N/A
From superseded fixes:

HTTP(s) monitor now supports IPv6 addresses and hostnames
MR0713106219 ISMBatch: Ability to set "@Identifiers updated" field for each element.
SNMP monitor now supports IPv6 addresses and hostnames