IBM Tivoli Composite Application Manager for Transactions Internet Service Monitoring 220.127.116.11 Interim Fix 29 README Tivoli Composite Application Manager for Transactions 18.104.22.168 22.214.171.124-TIV-CAMIS-IF0029 Readme
Readme file for: 126.96.36.199-TIV-CAMIS-IF0029
Product/Component Release: 188.8.131.52
Update Name: 184.108.40.206-TIV-CAMIS-IF0029
Fix ID: 220.127.116.11-TIV-CAMIS-AIX-IF0029, 18.104.22.168-TIV-CAMIS-LINUX-IF0029, 22.214.171.124-TIV-CAMIS-SOLARIS-IF0029, 126.96.36.199-TIV-CAMIS-WINDOWS-IF0029
Publication Date: 26 June 2014
Last modified date: 26 June 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
|Tivoli Composite Application Manager for Transactions||Windows
Prerequisites and co-requisites
This upgrade for ITCAM for Transactions Internet Service Monitoring supersedes 188.8.131.52 IF 20, 184.108.40.206 IF 24 and 220.127.116.11 IF 28 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 v18.104.22.168 software prerequisites, please visit:
Prerequisites for ITCAM for Transactions V22.214.171.124
ITM Minimum Prerequisites for this MDV:
Same requirements as ITCAM for Transactions v7.3.
For more information refer to the Compatible software for ITCAM for Transcations 126.96.36.199
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
Non APAR Defect 13701 - ismconfig.cmd fails to accept multiple white space enclosed in quotes(") in SOAP parametersProblem Description
Non APAR Defect 14498 - Internet Service Monitor 188.8.131.52 upgrade fails with no existing image to upgrade errorProblem Description
mkdir: 0653-357 Cannot access directory /opt/IBM/ITM/licenses.
/opt/IBM/ITM/licenses: A file or directory in the path name does not exist.
cp: /opt/IBM/ITM/licenses/isv730: A file or directory in the path name does not exist.
The CD you are trying to install is a fixpack CD and cannot be installed on a machine without an existing image to upgrade.
If this doesn't exists it cannot detect the previous ISM installation correctly causing the upgrade to stop.
Refer to the technote for more information.
Non APAR Defect 16289 - Remote UpgradeProblem Description
Change of Summarized DataProblem 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 184.108.40.206 release with no fix packs applied, you must uninstall the 220.127.116.11 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 v18.104.22.168 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 22.214.171.124. Ensure that the Version of Internet Service Monitoring in the MTEMS is '07.30.01.29'.
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 v126.96.36.199 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: SM_ISM_7.3_Integration,ITCAM_ISM_7.3_0492
The following new features are included in ITCAM for Transactions Internet Service Monitoring 188.8.131.52 Interim Fix 29:
- 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)
- ISA DC Support - Added ISA DC Support to this release.
- Take Action - System Command Support - The KISAgent now supports system commands as take actions. See the Problem Summary and Conclusion for APAR IV10041 for more information.
- Retest Interval - The ISM command library has been updated to correctly calculate the next "time fire" for a failed test. See the Problem Summary and Conclusion for APAR IV09340 for more information.
- Ping Timeout - Ping Timeouts are now honoured when retries are specified. See the Problem Summary and Conclusion for APAR IV12935 for more information.
- Derby Database - The Derby Database is now detected properly in ITM 6.2.2 and ITM 6.2.3. See the Problem Summary and Conclusion for APAR IV15338 for more information.
- Config CLI - Validation of parameters has been improved and syntax support has been added for Monitoring Periods.
- Migration Tools - Several defects in XML2Cli have been fixed including converting monitoring periods correctly and truncating descriptions to 64 characters.
List of fixes
A) APAR Content:
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
From superseded fixes:
IV00137 ITCAM ISM ICMP monitor does not hounour packet interval setting for an element
IV01021 Transx monitor fails to parse profiles when schedules are defined
IV01384 Profile Upgrade fails with large number of profiles
IV02077 Pipe module does not filter retest events
IV02709 ISM VERSION 7.3 DOES NOT CORRECTLY UPGRADE TRANSX PROFILES
IV02848 ISM Transx monitor may crash processing cookies with quotes (")
IV03605 ISM 7.2 ALLOWS MULTIPLE USERS TO OPEN THE ISM CONFIGURATION CONSOLE
IV03671 ISM HTTP(S) PROXY INFORMATION IS LOST AFTER MODIFYING HTTP(S) PROFILE
IV03871 ISM 7.3 Config GUI should not sort the HTTP(s) parameters
IV04113 Spacing between each ping is too small in some situation.
IV04522 ISM TRANSX MONITOR CAN CRASH WHEN IT ENCOUNTERS EXPIRED COOKIES
IV05485 ISM Config GUI is unable to create the KIS.STEPS Table using Derby DB on ITM 6.2.2 FP2
IV06264 HTTP/S monitor deletes session cookies between redirects. 7.3
IV07660 Profile names should allow for hyphens
IV08202 ICMP monitor can incorrectly include consecutiveFailures token in the event list.
IV08832 LOG MESSAGE FOR DVC IGNORE STATEMENT HAS TOO HIGH A SEVERITY.
IV09340 RETESTINTERVAL PARAMETER INCORRECTLY USED TO CALCULATE NEXT "TIME FIRE"
IV09915 Post installation actions on Windows don't work when installation path contains spaces
IV10041 ISM DOES NOT SUPPORT CUSTOM TAKE ACTIONS
IV10382 ISM GUI CAN'T SPECIFY OIDS LONGER THAT 64 CHARACTERS
IV10958 SMTP monitor Tracking information location setting
IV11280 FTP monitor crash with long configuration fields and datalog enabled
IV11666 ISM PROFILE PROPERTY DOES NOT CAUSE THE MONITOR TO CONDITIONALLY LOAD PROFILES
IV12409 SNMP crash when specifying IPAddress and running under high load
IV12477 RT and ISM language packs have dos format UNIX install scripts
IV12510 INCLUSION OF A '\' CHARACTER CAUSES A BAD URL FAILURE IN THE HTTP(S) MONITOR
IV12513 FAILURE TO VALIDATE ELEMENT DATA WILL CAUSE THE HTTP(S) MONITOR TO CRASH
IV12935 Ping Timeout not honoured when retries are specified
IV13384 ISMBATCH CRASHES ON UNEXPECTED CHARACTERS IN PROFILE DURING XML
IV13941 Thread count not accurate when thread creation fails.
IV15338 ISM 7.3 Config GUI thinks ITM 6.2.2 Derby Database is DB2
IV15443 ISM PROFILEUPGRADE TOOL DOES NOT MIGRATE DOMAIN ATTRIBUTE FROM ISM 2.4
IV15766 HTTP(S) PARAMETERS ARE LIMITED TO 254 CHARACTER
IV15767 HAVING A \ AS THE LAST CHARACTER IN A ELEMENT FIELD CAN CAUSE PROFILE DISTRIBUTION TO FAIL.
IV16896 ISM MONITOR's REGEXP OPERATORS CARET AND DOLLAR NOT WORKING
IV18662 ISM GUI shouldn't allow trailing white space
IV20924 net-snmp is not thread safe when using SNMP v3
IV26736 ismconfig.sh didn't work in TM623 FP1 env
IV27685 SDP Information Hard Coded in SIP Invite.
IV29724 ISM Soap Requests may have incorrect namespaces
IV30821 Orphaned REGEXPS rows can cause a null pointer exception in the Config GUI
IV32399 ISM configuration does not support ITM 6.2.3 FP2
IV33232 HTTP Parameter values are limited to 1024 bytes
IV37295 ISM Timing lacks sufficient resolution to measure small time differences.
IV38085 PSIRT 398 OpenSSL 7.3
IV39976 SMTP Plain Auth includes trailing NULL in Base64 string
IV42762 Integer SLC comparisons fail when using values larger then 2,147,483,647.
IV43928 ISM SOAP monitor timeouts from lowercase content-length passed back from server.
IV44201 Unwrapped SOAP messages can generate duplicate namespace definitions in the SOAP envelope
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
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
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)
IZ77287 KIS Agent does not use the correct Candle timestamp format
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:
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
4381 All monitors except ICMP have performance issues when requests per minute exceeds 1000
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
4510 ISMBATCH runs longer than 12 min while working with profiles bigger than 3000 elements
4511 ISM ICMP - slow response of Profile statistics workspace
4880 ISM does not start for z/Linux SuSE 10 64bit
4926 GVT: Incorrect Date/Time format in ISM
4931 Change Monitor Status inactive rows to blue
4932 Old monitor profiles are not being updated in 'Monitor Status'
4933 Inconsistent Good/Marginal/Bad columns in HSTATS and SSTATS
4934 ResponderRouter always zero (0) UNLESS there is a successful connection
4994 ISM bridge failed to start when started from command line using ism_startup.sh
4998 ISM: Unable to deploy profiles via TEP
5097 zlinux tcpport monitor won't output error messages to log files for troubleshooting
5136 SNMP based monitors with large oidgroups perform terribly.
5174 ISM Soap Parse exception occurring when running SOAP 19 test case
5218 A profile for WMS monitor can be created using ismbatch command even though wms is not available
5229 KIS log doesn't indicate which monitor failed to parse it's props file
5231 zlinux monitor doesn't support DOS prop file format
5232 Error message is displayed when uninstall ISM on Windows
5234 CT4436 configuration of "echo2DStringArray" of soap monitoring can't be saved
5272 ISM:kisagent fails to start correctly.
5301 ISM Config UI security warning when using webstart.
5322 Soap Monitor inserting attributes unnecessarily
5323 Soap monitor does not insert namespace
5412 ISM: Installation readme line termination incorrect for windows notepad
5417 Bridge is unable to connect to omnibus and quits
5539 ISM doesn't provide build number
5543 ISM Soap monitor defines duplicate namespaces in soap request
5548 ZLinux soap monitor bombs out and won't start after creating valid soap profile
5564 Internal Error message is displayed when launched ISM Config GUI from the TEP
5619 History Collection Configuration dialog produces an error message when selected Internet Service Monitors
5633 7.3 monitor version info shows 7.2 build string
5651 ISM Soap Monitor Crash when using array of complex types
5667 zlinux longrun testing - File Descriptor leak in FTP monitor
5696 ISM: Installation readme line termination still incorrect for windows notepad
5702 ismbatch adds extra soapparameterelement in the profile for arrays of complex types
5712 POP3 monitor failed to start from Take Action
5714 ISM does not appear in the list of products available for installation.
5767 zlinux ISM longrun - kisagent growing in memory size
5820 ISM soap monitor does not qualify all elements with namespaces
5821 ISM soap monitor does not indicate that it doesn't support elementFormDefault="unqualified"
5870 linux SOAP monitor memory usage grew 160MB in two days.
5871 SAA monitor crashed with core files.
5963 ISM SIP monitor core files on All platforms
6022 Soap monitor does not define all namespaces referenced in request
6032 Soap monitor does not send correct namespaces for array of complex types.
6076 ICMP Monitor - MaxPacketSize is not honoured
6087 Complex Type containing array of strings adds unnecessary attributes
6130 LocalXMLProfileManager not parsing @Proxy params in XML properly
6164 zlinux TEP hangs
6241 workspaces show incorrect data using TRANSX profile on windows
6244 SOAP monitor crashes on array of integers
6274 Soap monitor does not send correct request for nested complex types with Attributes
6277 Soap Monitor does not support attributes in array of complex types
6624 Unable to create KIS.LOCK table with MSSQL
6696 Props files on Windows build are in Unix format
6703 ismbatch deletes the first nested array item whenever it rewrites the SOAP profile out
6755 ismbatch adds extra array elements to SOAPOuput in the profile
6849 ISMBATCH unable to read saa.xml probe elements correctly
6867 Cannot index elements via the checksum for the delete command
6895 Miscellaneous UI defect/ improvements
6940 Summary of good, marginal, bad ICMP requests in WH is smaller than the shown number of elements in TEPS workspace
6963 xml2cli application needs "start day of week" configuration
6967 ISMBATCH writes wrong schedules to profile if start day of week is not SUNDAY
7090 TRANSX monitor crash when run TRANSX12 case
7146 Unexpected error "mbind: Invalid argument" was catched during running "itmcmd" and installation on redhat6.0 64bit
7277 Thread ID on RHEL6.0 64bit is negative
7285 SIP monitor crashed on AIX71
7339 ProfileUpdateTimeout is not added into icmp props file for APAR IZ87532
7429 SNMP IPv6 doesn't work on Zlinux
7432 SIP monitor fails to register only on Zlinux
7451 MessageLevel in bridge.log for stoping monitor doesn't make sense
7470 Data in TEP Service Statistics is inconsistent after one hour
7486 ISM xml2cli requires default ismbatch.props file
7489 xml2cli does not show checksum for -addstep
7490 xml2cli unexpected behaviour when executed with -m and -p parameters
7517 ISM Monitors do not honour maxcca
7625 ismbatch does not write out SOAPParams with identical elements correctly.
7729 Copyright time doesn't updated to include 2011 for ISM73 in installation welcome page.
7761 ITM fail to "ResyncAgent", so fail to deploy any profile to the agent which is under "Unconfigured" status
7839 sip monitor with 39 elements can't be stoped by "itmcmd agent -f stop is"
7843 xml2cli Copyright displayed "2010"
7922 Help within config GUI displays file not found page
7929 ISM agent can't send DNS result to TEMS if the result message is "No response from server"
7931 core files from nco_m_ftp because of non existing file name in transaction - ftp step
7935 two RTSP entries from "Add monitor type to profile" on ISM configuration GUI
8003 xml2cli can't deal with oidgroup name with space
8084 ISA fails on getting ITM agent info on Windows & Linux
8104 Increase the default QSize
8265 Number of (Good+Marginal+Bad) elements in KIS_SERVICE_STATISTICS table is higher than the number of elements created
8363 zlib not included with the kisagent on zLinux
8967 ISM73 doesn't have license file too under $ITMHOME/license
9072 XML2Cli: Monitoring periods not converting correctly
9074 XML2Cli: Descriptions are not being truncated to 64 characters
9075 XML2Cli: Transx steps contain invalid configuration tokens
9076 Config Cli: HTTP Parameter validation
9077 Config Cli: Monitoring command can not be run as part of a File
9079 Config Cli: Monitoring Period syntax support
9080 Config Cli: Table upgrade breaks transx configuration
9132 DHCP - TotalTime should not include monitor activities' overhead time
9136 DNS old profiles' querytype lost after create new DNS profile
9219 Upgrade 71 to 7203, old inactive transx profile can't work after activate this profile.
9253 Empty arguments will be set to default (if available) for ismbatch -change commands
9280 ICMP monitor has high marginal results on 7.3
9595 ICMP was incorrectly setting IP family to IPv6 instead of checking
10241 core dump will happen when profile dir name with "."
10242 profileupgrade failed to upgrade large number of profiles on AIX
10396 ismconfig help message some optional fields incorrect
10459 ismconfig cli -change command requires server parameter for http
10463 Toggle for SMTP tracking information location
10468 ismconfig cli needs to check if element or checksum is supplied for step related commands as part of validation
10565 TEP sending invalid editoid ismbatch command
10596 localip in ISM Configuration GUI can't be assigned as v6 address
10663 Log files are overwritten on startup.
10700 retestinterval should be set to same as poll as poll interval is if greater
10743 ismconfig doesn't work on SOAPInputs and SOAPOutputs with double qoute
10744 SOAPInputs and SOAPOutputs not properly parsed
10745 communitystring is required by ismconfig for SNMP monitor
10759 Double quote in DVC usage is different between ismconfig and ismbatch
10813 addoidgroup failed on ismconfig using output of xml2cli
10905 Failed to synch windows ISM agent on ITM622 Derby linux env
10910 Negative data in the Bad field under Host Statics
10918 transx crash when cookie length is going over a 4k buffer
10955 Default value of retries is converted to 3 in TFTP monitor
10957 profileUpgrade fails with "-profile <DIR>" on windows
10958 Active transaction's steps were displayed as "Inactive" in liststeps
10968 resyncall can't sync Unconfigured agent in ismconfig
11061 ICMP failure retests scheduling not using end time
11062 ICMP endTime not set correctly when pings fail
11385 transx profile fails for http step timeout on Solaris and Linux
11574 ismbatch version is still 2.0
11713 Clicking Apply on an Invalid Soap Input/Ouput Parameter clears out the previous value
11783 The start all take action fails to start the radius monitor
11788 ismconfig.sh can not deal with space in monitor's description
11821 xml2cli,ismconfig,SOAPInputs & SOAPOutputs doesn't escape "\"
11948 ISM Config GUI Window is displayed whilst it is loading
12017 ismconfig cli change command does not change @Params as it only adds new ones
12026 copyright info for ismbatch & ismconfig is out of date
12301 specify the same name parameter multiple times for an element fails but displays successfully in ismconfig both gui & cli
12306 httpparameters table was not updated in upgrade env
12431 ismconfig cli is flagging unit="" as an error.
12436 The name oid value is not allowed to contain space in ismconfig but allowed in ismbatch
12446 profileUpgrade fails with "-profile C:\" & multiple \ on Windows
12519 ICMP monitor start time is not calculated correctly on windows platform.
12520 snmp crashed with 2001 elements after running 1 day
12555 Invalid retest Interval can lead to a monitor crash
12609 dns monitor crashed on Solaris 10
12610 snmp monitor sometimes failed to be stopped
12620 SNMP Monitor will crash if an element in the xml specifies a OIDGROUP that does not exist.
12631 "ismbatch -file" imports profile as InActive status by default when element number is big
12667 ism agent need to be reconfigured in the window OS after upgrade
12701 "Warning: Failure retest interval 10 ignored as failure retests is 0" on AIX
12907 core dumped when run the profileUpgrade command
13003 bridge & monitors failed to connect to kisagent on P7 AIX7.1
13031 ismconfig gui didn't support dot in oidgroup name but ismbatch worked well
13145 Example Entry for AcceptCNAME in dns.props has incorrect syntax
13163 ismconfig failed to dropDB
13168 ISM: When configuring the Profile element - DNS monitor should only accept a numeric scripted IP address in the Server field (both GUI and CLI)
13224 If ISM TEPS DB is locked, opening ISM GUI will cause the TEP client to be inaccessible after error.
13234 When editing transx steps in the cofig GUI, no error message is displayed for invalid input.
13292 Error happened when upgrade from ISM 7102 suport file to the latest version of ISM support file in the window box
13295 ismconfig cli silently fails to import profiles with invalid names
13394 Orphaned element ID rows stop creating additional elements
13537 Config CLI and Config GUI drop Array of Complex Type attributes
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
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
Document change history
|Version||Date||Description of change|
|1.0||24 June 2014||Initial Version|
More support for:
Tivoli Composite Application Manager for Transactions
Reference #: 00001843
Modified date: 25 June 2014