IBM Support

IBM Tivoli Composite Application Manager for Transactions Internet Service Monitoring 7.4 Interim Fix 10 README Tivoli Composite Application Manager for Transactions 7.4.0.1 7.4.0.1-TIV-CAMIS-IF0010 Readme

Readme file for: 7.4.0.1-TIV-CAMIS-IF0010
Product/Component Release: 7.4.0.1
Update Name: 7.4.0.1-TIV-CAMIS-IF0010
Fix ID: 7.4.0.1-TIV-CAMIS-AIX-IF0010, 7.4.0.1-TIV-CAMIS-LINUX-IF0010, 7.4.0.1-TIV-CAMIS-SOLARIS-IF0010, 7.4.0.1-TIV-CAMIS-WINDOWS-IF0010
Publication Date: 8 August 2016
Last modified date: 8 August 2016

Download location

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.

Fix Download for AIX

Product/Component Name: Platform: Fix:
Tivoli Composite Application Manager for Transactions AIX
7.4.0.1-TIV-CAMIS-AIX-IF0010

Fix Download for Linux

Product/Component Name: Platform: Fix:
Tivoli Composite Application Manager for Transactions Linux
7.4.0.1-TIV-CAMIS-LINUX-IF0010

Fix Download for Solaris

Product/Component Name: Platform: Fix:
Tivoli Composite Application Manager for Transactions Solaris
7.4.0.1-TIV-CAMIS-SOLARIS-IF0010

Fix Download for Windows

Product/Component Name: Platform: Fix:
Tivoli Composite Application Manager for Transactions Windows
7.4.0.1-TIV-CAMIS-WINDOWS-IF0010

Prerequisites and co-requisites

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

  • 7.4.0.1

Its a cumulative upgrade; any updates in the following releases will be included in this upgrade.

  • 7.4.0.0
  • 7.4.0.0-IF03
  • 7.4.0.0-IF11
  • 7.4.0.0-IF13
  • 7.4.0.0-IF18
  • 7.4.0.0-IF23
  • 7.4.0.0-IF26
  • 7.4.0.0-IF28
  • 7.4.0.1
  • 7.4.0.1-IF02
  • 7.4.0.1-IF03
Note: After this upgrade has been applied, the new revision level for ISM will be 7.4.0.1-IF0010.

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 & V7.4.0.1

For additional download packages or ITM support information, visit the ITM support portal at:
https://www.ibm.com/support/entry/portal/product/tivoli/ibm_tivoli_monitoring_v6?productContext=-304407452

Known issues

APAR IV79459 - SOAP monitor crashes when processing fault code in server response

Problem Description
Using ITCAM4Tx ISM agent v7.4, SOAP monitor crashes and soap.log ends with the message : Aborted.
Root cause
The crash is occurring in the AXISC 3rd party library when its processing the Fault code in the server's response.
Workaround
Using ISM 7.4.0.1-IF02+, use the HTTP monitor and it's "body" parameter and put the SOAP request in that, rather than use the SOAP monitor.

APAR IV82041 - ISM with new line or carriage return in regular expression not working

Problem Description
Its not possible to configure a profile element to handle a multi-line response from a server (embedded CR/LF).
Root cause
This is a design restriction.
Workaround
Use multiple regular expression checks combined in SLC.

Non APAR Defect 13042 - ISM agent doesn't start after upgrading Windows Box

Problem Description
The Windows ISM agent is stopped after an upgrade.
Root cause
The installer does not support changes to the release information and registry keys. Support for this should be in the installer but older installers did not support these actions.
Workaround
Reconfigure the ISM agent after the upgrade to resolve the problem.

Known limitations

Remote Deployment to Windows Running MTEMS

Problem Description
Attempting to remotely deploy the ISM agent to a Windows machine actively running the Manage Tivoli Enterprise Monitoring Services (MTEMS) program fails. Before remote deploying, please close the MTEMS program on the target machine.

SOAP Monitor Does Not Support Nested Arrays or multiRef Values

Problem Description
The SOAP monitor is unable to handle parameters containing nested (two or more dimension) arrays or those that are referenced externally in the 'multiRef' style.

Installation information

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.
https://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 fix pack 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 fix pack remotely using ITM TEMS depot and tacmd AddBundles command. For more information, please refer to the ITCAM for Transactions v7.4.0.1 Installation and Configuration Guide, available here:
https://www-01.ibm.com/support/knowledgecenter/SS5MD2_7.4.0.1/com.ibm.itcamt.doc/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)
The procedure for installing agent-specific application support on the components is similar to installing the monitoring agent. The main difference is to select the application support components required.

It is strongly recommended that all ISM components, agents and support, be brought up to the same revision level as soon as is practical.
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 7.4.0.1. Ensure that the Version of Internet Service Monitoring in the MTEMS is '07.40.01.10'.

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://www.ibm.com/support/knowledgecenter/SS5MD2_7.4.0.1/com.ibm.itcamt.doc/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.4.0.1 Installation and Configuration Guide, available here:
http://www.ibm.com/support/knowledgecenter/SS5MD2_7.4.0.1/com.ibm.itcamt.doc/ism/dita/ag/topic/ISM_uninstall_chapter.html

Additional information

The Secure Hash Algorithm 1 (SHA1) checksum of the images are as follows:
SHA1(7.4.0.1-TIV-CAMIS-AIX-IF0010.tar)=316587d98b1f7b905eb0f402c7fa754452a73f0d
SHA1(7.4.0.1-TIV-CAMIS-Linux-IF0010.tar)=ba7c728f4ac794d3b22001257dbebfdb185e669a
SHA1(7.4.0.1-TIV-CAMIS-Solaris-IF0010.tar)=59af624887a24e54abc944d857a77eb4a48ff4a7
SHA1(7.4.0.1-TIV-CAMIS-Windows-IF0010.zip)=90c09b42b88bf2c81aea2501d009369712ac442c

The ITM kisagent logs show that the Release ID of this interim fix pack is: ITCAM_ISM_7.4.0.1_0327

New Features


The following new features are included in ITCAM for Transactions Internet Service Monitoring 7.4.0.1 Interim Fix 10:



The following new features were included in ITCAM for Transactions Internet Service Monitoring 7.4.0.1 Interim Fix 3 (Included in this 7.4.0.1 Interim Fix 10):

The following new features were included in ITCAM for Transactions Internet Service Monitoring 7.4.0.1 Interim Fix 2 (Included in this 7.4.0.1 Interim Fix 010):

The following new features were included in ITCAM for Transactions Internet Service Monitoring 7.4.0.0 Fix Pack 1 (Included in this 7.4.0.1 Interim Fix 10):
ISM 7.4.0.0 Fix Pack 1 modified the default behaviour to disable the DHE/EDH ciphers in all monitors. To enable the DHE/EDH ciphers, update the monitor properties: SSLCipherSuite and BridgeSSLCipherSet . For example, to enable DHE/EDH ciphers in the HTTPS monitor, update the https.props file to include:
SSLCipherSuite : "AES:3DES:DES:!EXP:DHE:EDH"
BridgeSSLCipherSet : "AES:3DES:DES:!EXP:DHE:EDH"


The following new features were included in ITCAM for Transactions Internet Service Monitoring 7.4.0.0 Interim Fix 28 (Included in this 7.4.0.1 Interim Fix 10):
ISM 7.4.0.0 Interim Fix 28 modified the default behaviour to disable the RC4 ciphers in all monitors. To enable the RC4 ciphers, update the monitor properties: SSLCipherSuite and BridgeSSLCipherSet . For example, to enable RC4 ciphers in the HTTPS monitor, update the https.props file to include:
SSLCipherSuite : "AES:RC4:3DES:DES:!EXP"
BridgeSSLCipherSet : "AES:RC4:3DES:DES:!EXP"


The following new features were included in ITCAM for Transactions Internet Service Monitoring 7.4.0.0 Interim Fix 26 (Included in this 7.4.0.1 Interim Fix 10):
ISM 7.4.0.0 Interim Fix 26 modified the default behaviour to disable the EXPORT (EXP) ciphers in all monitors. To enable the EXP ciphers, update the monitor properties: SSLCipherSuite and BridgeSSLCipherSet . For example, to enable EXP ciphers in the HTTPS monitor, update the https.props file to include:
SSLCipherSuite : "AES:3DES:DES:EXP"
BridgeSSLCipherSet : "AES:3DES:DES:EXP"


The following new features were included in ITCAM for Transactions Internet Service Monitoring 7.4.0.0 Interim Fix 23 (Included in this 7.4.0.1 Interim Fix 10):
ISM 7.4.0.0 Interim Fix 23 modified the default behaviour to disable the SSLv2 and SSLv3 protocols in all monitors. To enable SSLv2/SSLv3, update the monitor properties: SSLDisableSSLv2 and SSLDisableSSLv3 . For example, to enable SSLv2 and SSLv3 in the HTTPS monitor, update the https.props file to include:
SSLDisableSSLv2 : 0
SSLDisableSSLv3 : 0


The following new features were included in ITCAM for Transactions Internet Service Monitoring 7.4.0.0 Interim Fix 18 (Included in this 7.4.0.1 Interim Fix 10):
ISM 7.4.0.0 Interim Fix 18 added the ability to verify SSL certificates in the HTTP(s), IMAP4, LDAP, POP3, SIP, SMTP and SOAP monitors. This is disabled by default. To enable this, modify the verifycertificate flag in the profile element. SSL certificate trust stores are defined by the monitor properties: SSLTrustStoreFile and SSLTrustStorePath . The default values are:
SSLTrustStoreFile : "$ISMHOME/certificates/trust.pem"
SSLTrustStorePath : "$ISMHOME/certificates/"


The following new features were included in ITCAM for Transactions Internet Service Monitoring 7.4.0.0 Interim Fix 13 (Included in this 7.4.0.1 Interim Fix 10):


The following new features were included in ITCAM for Transactions Internet Service Monitoring 7.4.0.0 Interim Fix 11 (Included in this 7.4.0.1 Interim Fix 10):


The following new features were included in ITCAM for Transactions Internet Service Monitoring 7.4.0.0 Interim Fix 3 (Included in this 7.4.0.1 Interim Fix 10):
  • Multi user ISM configuration - RFE 13434 - Multi user ISM configuration.

List of fixes

A) APAR Content:

IV84128: Regression - ELEMENT VALUES IN THE ISM LDAP MONITOR CAN BE OVERRIDDEN BY RETRIEVED LDAP OBJECTS ATTRIBUTES
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
IV55317 Parenthesis ( and ) are not supported in ISM 7.4 for OID group names.
IV55517 SOAP monitor input validation does not accept attribute names with '-' character.
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
IV56290 ISM SOAP monitor sometimes reuses xmlns:ns1 identifier for different namespaces in generated SOAP Request.
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
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.
IV60658 DNS QUERY ID NOT DIFFERENT BETWEEN RETEST
IV60769 IF0011 KIS_RESOURCES.JAR HAS INCORRECT VERSION INFO RESULTING IN APPLICATION SUPPORT MISMATCH ERROR.
IV60778 DISABLE ISM CONFIGURATION GUI "RESYNC AGENT" WITH A CUSTOM PROPERTY IN TEP
IV61935 Invalid data passed into the KISAgent can cause a core dump in ServiceLevelCollector.
IV63262 TACMD LISTSYSTEMS COMMAND SHOWS INCORRECT VERSION FOR ISM
IV65580 ELEMENT VALUES IN THE ISM LDAP MONITOR CAN BE OVERRIDDEN BY RETRIEVED LDAP OBJECTS ATTRIBUTES
IV65736 ISM DOES NOT SUPPORT THE ITM \"CHANGE\" FUNCTION
IV65798 THE ISM SOAP MONITOR DOES NOT ENABLE HTTPS BY DEFAULT
IV67332 SOAP monitor input parameters may not save correctly when larger than 254 characters long
IV68183 LDAP monitor process crashes after reconfig to use SIMPLE-SSL (internal)
IV68183 LDAP monitor process crashes after reconfig to use SIMPLE-SSL
IV72576 Race condition in LDAP monitor causing double free in OpenSSL
IV73214 rping monitor not reusing control table rows in Juniper router.
IV73738 BPS calculations in SNMP monitor incorrect for very low BPS
IV76652 HTTP Monitor only sends 3 bytes in the body of a post
IV76913 Bridge accepts SSLv2 and SSL v3 connections
IV76923 RPING timeout value is set incorrectly
IV79154 Uplift from SHA1 to SHA-512 for certificate hash
IV79885 ismbatch shouldn't error when removing non-existent OID group or adding existing OID group
IV81603 Incomplete ITCAM for ISM prerequisites stating omnibus 8.1 support

B) Additional Non APAR Defects:

None.
From superseded fixes:

10767 ismconfig.props need saved manually before upgrade
18874 ismconfig cli failed to copy profile
19176 improper message for Resync Agent - Resyncing an this agent will cause locally stored profiles to be removed
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.
24582 ismbatch accepts non-IP format as dns server but fails to be parsed
24694 Fix all Valgrind Leaks + Errors in HTTPS Monitor
24840 Add AES to the default cipher suite
25217 Remove KIS Table Columns that aren't in use anymore
25397 Fix Transx Timeout Debug Messages on Windows
26189 ism7401 failed to install on new platform - redhat 7.0 64bit
26583 NTLM doesn't seem to work against servers that don't want unicode
27582 Bridge and Monitors failed to connect to KISagent

C) Enhancements

None.
From superseded fixes:

19790 Add new CLIConfig command to bulk unlock profiles

Document change history


Version Date Description of change
1.0 8 August 2016 Initial Version


















Document information

More support for: Tivoli Composite Application Manager for Transactions

Reference #: 00002826

Modified date: 08 August 2016