Readme documentation for IBM® Tivoli® Key Lifecycle Manager for Distributed Platforms, Version 2.0 Fix Pack 7 including installation-related instructions, prerequisites and corequisites, and a list of fixes. All IBM Tivoli Key Lifecycle Manager for Distributed Platforms fix packs are cumulative. This fix pack contains the content of all prior fix packs published to date.
Readme file for: IBM® Tivoli® Key Lifecycle Manager for Distributed
Platforms
Product/Component Release: 2.0
Update Name: Fix Pack 7
Fix ID: 2.0.0-ISS-TKLM-FP0007
Publication date:17 November 2014
Last modified date:12 November 2014
Contents
Platform support
Download locations
Tivoli Integrated Portal Fix Pack
Installation
Prerequisites and corequisites
Known issues
Known limitations
Updates to CLI commands
Installation information:
Installing the Tivoli Key Lifecycle Manager fix
pack
Prior to fix pack installation
Performing the necessary tasks after fix pack
installation
Fix pack installation error conditions
List of fixes
Copyright and trademark information
Document change history
| Tivoli Key Lifecycle Manager Version 2 platforms supported |
|---|
AIX Version 5.3 64-bit |
| AIX Version 6.1 64-bit |
| AIX Version 7.1 64-bit (See "Known Issues" section for installation tip) |
| Red Hat Enterprise Linux AS Version 4 32-bit on x86 |
| Red Hat Enterprise Linux Version 5 update 2 32-bit on x86 |
| Red Hat Enterprise Linux Version 5 update 2 64-bit on x86 (32-bit mode application) |
| Red Hat Enterprise Linux Version 5 on System z (Requires TKLM v2 Manufacturing Refresh 3 installed) |
| SuSE Linux Enterprise Server Version 9 32-bit on x86 |
| SuSE Linux Enterprise Server Version 10 32-bit Service Pack 2 on x86 |
| SuSE Linux Enterprise Server Version 10 64-bit Service Pack 2 on x86 (32-bit mode application) |
| SuSE Linux Enterprise Server Version 11 32-bit on x86 |
| SuSE Linux Enterprise Server Version 11 64-bit on x86 (32-bit mode application) |
| SuSE Linux Enterprise Server Version 11 on System z (Requires TKLM v2 Manufacturing Refresh 3 installed) |
| Solaris 9 SPARC 64-bit |
| Solaris 10 SPARC 64-bit |
| Windows Server 2003 R2 32-bit |
| Windows Server 2003 R2 64-bit (32-bit mode application) |
| Windows Server 2008 32-bit |
| Windows Server 2008 64-bit (32-bit mode application) |
| Windows Server 2008 R2 32-bit |
| Windows Server 2008 R2 64-bit (32-bit mode application) |
Tivoli Key Lifecycle Manager Version 2.0 has been certified to run on the following virtual environments when fix pack 2 or higher has been installed. The platform running within the virtual machine must be supported by the virtual platform server and Tivoli Key Lifecycle Manager Version 2.0 (see platforms supported table).
| Tivoli Key Lifecycle Manager Version 2 virtual platforms supported |
|---|
VMWare ESX/ESXi Server Versions 4.0 and 5.0 |
| Red Hat Enterprise Virtualization/Kernel-Based Virtual Machine (RHEV/KVM) Version 5.4 |
Download IBM Tivoli Key Lifecycle Manager Version 2.0 Fix Pack 7 from IBM Fix Central:
Platforms updated by this fix pack.
| Product/Component Name | Platform | File Name |
|---|---|---|
| IBM Tivoli Key Lifecycle Manager version 2.0 Fix Pack 7 - 2.0.0-ISS-TKLM-FP0007 | AIX | 2.0.0-ISS-TKLM-FP0007-AIX.tar.gz |
| IBM Tivoli Key Lifecycle Manager version 2.0 Fix Pack 7 - 2.0.0-ISS-TKLM-FP0007 | Linux-s390 | 2.0.0-ISS-TKLM-FP0007-Linux-s390.tar.gz |
| IBM Tivoli Key Lifecycle Manager version 2.0 Fix Pack 7 - 2.0.0-ISS-TKLM-FP0007 | Linux-x86 | 2.0.0-ISS-TKLM-FP0007-Linux-x86.tar.gz |
| IBM Tivoli Key Lifecycle Manager version 2.0 Fix Pack 7 - 2.0.0-ISS-TKLM-FP0007 | Solaris | 2.0.0-ISS-TKLM-FP0007-Solaris.tar.gz |
| IBM Tivoli Key Lifecycle Manager version 2.0 Fix Pack 7 - 2.0.0-ISS-TKLM-FP0007 | Windows | 2.0.0-ISS-TKLM-FP0007-Windows.zip |
Tivoli Integrated Portal Fix Pack
Installation
Prerequisites and
corequisites
All Linux platforms require the 32-bit i386 rpm installation of compat-libstdc++-33-3.2.3-61 or higher.
To determine if you have the package, run this command:
rpm -qa | grep -i "libstdc"
If the package is not installed, locate the rpm file on your original installation media and install it:
find installation_media -name
compat-libstdc++-33-3.2.3-61.*
rpm -ivh full_path_to_compat-libstdc++_rpm_file
Tivoli Key Lifecycle Manager version 2.0 must be successfully installed prior to the installation of the Tivoli Key Lifecycle Manager fix pack.
When installing this Tivoli Key Lifecycle Manager fix pack on Windows, the location of Tivoli Integrated Portal should be checked. If Tivoli Integrated Portal was installed in the default location (C:\IBM\tivoli\tiptklmV2), it is not required to set the TIP_HOME variable. If the location of Tivoli Integrated Portal is not the default, the directory path must be typed exactly as defined by Tivoli Integrated Portal.
To check the installation location of Tivoli Integrated Portal:
Search the output of the de_lsrootiu.cmd command for <discriminant>directory</discriminant>. The TIP_HOME variable should be set as the directory encapsulated by the <discriminant> tags.
Example de_lsrootiu.cmd output:
<iuInstance undoable="false" softwareLifeCycleStatus="Usable">
<instanceID>InstanceID[IU,TKLM,mrid:http://w3.ibm.com/namespaces/2003/OS_componentTypes:Operating_System,2.0.0.0,C:\ibm\tivoli\tiptklmV2,30E5C7271DA44099FEAF64037F3358A4]</instanceID>
<UUID>30E5C7271DA44099FEAF64037F3358A4</UUID>
<identityName>TKLM</identityName>
<version>2.0.0.0</version>
<hostingEnv>mrid:http://w3.ibm.com/namespaces/2003/OS_componentTypes:Operating_System</hostingEnv>
<discriminant>C:\IBM\tiptklmV2</discriminant>
</iuInstance>
When installing this Tivoli Key Lifecycle Manager fix pack on UNIX or Linux platforms, the location of Tivoli Integrated Portal should be checked. If Tivoli Integrated Portal was installed in the default location (/opt/IBM/tivoli/tiptklmV2), it is not required to set the TIP_HOME variable. If the location of Tivoli Integrated Portal is not the default, the directory path must be typed exactly as defined by Tivoli Integrated Portal.
To check the installation location of Tivoli Integrated Portal:
Search the output of the de_lsrootiu.sh command for <discriminant>directory</discriminant>. The TIP_HOME variable should be set as the directory encapsulated by the <discriminant> tags.
Example de_lsrootiu.cmd output:
<iuInstance undoable="false" softwareLifeCycleStatus="Usable">
<instanceID>InstanceID[IU,TKLM,mrid:http://w3.ibm.com/namespaces/2003/OS_componentTypes:Operating_System,2.0.0.0,/opt/IBM/tivoli/tiptklmV2,30E5C7271DA44099FEAF64037F3358A4]</instanceID>
<UUID>30E5C7271DA44099FEAF64037F3358A4</UUID>
<identityName>TKLM</identityName>
<version>2.0.0.0</version>
<hostingEnv>mrid:http://w3.ibm.com/namespaces/2003/OS_componentTypes:Operating_System</hostingEnv>
<discriminant>/dmount/IBM/tivoli/tiptklmV2</discriminant>
</iuInstance>
The TKLM.ear (com.ibm.tklm.ear) file fails to deploy when running the UNIX updateTKLM.sh or Windows updateTKLM.bat commands.
The following error message is displayed:
KMSDebug.init, noop, already inited (inited=true, logger=com.ibm.ws.logging.WsLogger@19521952) WASX7015E: Exception running command: "$AdminApp update tklm_kms app {-operation update -contents installableApps/com.ibm.tklm.ear -usedefaultbindings }"; exception information: com.ibm.ws.scripting.ScriptingException: WASX7115E: Cannot read input file "C:\windows64\tklminstall_windowsfp\TKLM\META-INF\installableApps\com.ibm.tklm.ear"
ERROR: Failed to deploy TKLM.ear Tivoli Key Lifecycle Manager Install Exit Code = 9, Problem deploying TKLM.ear.
On Windows platforms, the contents of the fix pack's zip file must be unzipped and installed on the same drive as the installation of Tivoli Key Lifecycle Manager version 2.0.
If %TIP_HOME% is not set by the user, Tivoli Integrated Portal is located by default on the drive defined by the %SystemDrive% environment variable. The zip file must be unzipped in a directory on the same drive.
Tivoli Key Lifecycle Manager version 2.0 must be successfully installed prior to the installation of the Tivoli Key Lifecycle Manager fix pack.
Problems can occur if you migrate keys that are members of multiple key groups in Encryption Key Manager to Tivoli Key Lifecycle Manager. The key is successfully migrated and made a member of the first key group. However, for subsequent key memberships, the migration code will log an error indicating the key and key group were not able to be migrated. You can use the migrated keys to read data, but cannot use the migrated keys to write from any group other than the first group membership that was successfully migrated. The error message is similar to this example:
com.ibm.tklm.common.exception.KLMException: CTGKM0851E The group cannot be created because an entity (key) cannot be in multiple key groups.
Contact support in order to complete migration. Do not install the fix pack until the migration is successful.
Installing the Tivoli Key Lifecycle
Manager fix pack.
Prior to fix pack
installation
Backup Tivoli Integrated Portal files on Windows platforms
| Instruction | Command |
|---|---|
| Open a command prompt. | Click the Start button, Click Run, type cmd and Click the OK button. |
| Stop the Tivoli Integrated Portal server | %TIP_HOME%\bin\stopServer.bat server1 -username [TIP_ADMIN] -password [TIP_PASSWORD] |
| Make a temporary directory | mkdir [TIP_BACKUP_DIRECTORY] example: mkdir c:\tipbackup |
| Change to the temporary directory | cd c:\tipbackup |
| Copy the files from the directory where Tivoli Integrated Portal is installed | xcopy /y /e /d %TIP_HOME% c:\tipbackup |
| Start the Tivoli Integrated Portal server | %TIP_HOME%\bin\startServer.bat server1 -username [TIP_ADMIN]
-password [TIP_PASSWORD] where: TIP_HOME is the directory where Tivoli Integrated Portal is installed (default: C:\IBM\tivoli\tiptklmV2). TIP_ADMIN defines the Tivoli Integrated Portal user name defined during installation (default: tipadmin). TIP_PASSWORD is the Tivoli Integrated Portal password for the TIP_ADMIN. |
Backup Tivoli Integrated Portal files on AIX, Solaris, and Linux
platforms
| Instruction | Command |
|---|---|
| Open a ksh or bash shell. | if your default shell is not ksh or bash, run "exec ksh" or "exec bash". |
| Stop the Tivoli Integrated Console server | $TIP_HOME/bin/stopServer.sh server1 -username [TIP_ADMIN] -password [TIP_PASSWORD] |
| Make a temporary directory | mkdir [TIP_BACKUP_DIRECTORY] example: mkdir /tmp/tipbackup |
| Change to the temporary directory | cd /tmp/tipbackup |
| Archive the files from the directory where Tivoli Integrated Portal is installed | tar -cvf tipbackup.tar $TIP_HOME/* |
| Start the Tivoli Integrated Portal server | $TIP_HOME/bin/startServer.sh server1 -username [TIP_ADMIN] -password
[TIP_PASSWORD] where: TIP_HOME is the directory where Tivoli Integrated Portal is installed (default: /opt/IBM/tivoli/tiptklmV2). TIP_ADMIN defines the Tivoli Integrated Portal user name defined during installation (default: tipadmin). TIP_PASSWORD is the Tivoli Integrated Portal password for the TIP_ADMIN. |
Steps for installing a fix pack on Tivoli Key
Lifecycle Manager version 2.0 on Windows platforms.
| Instruction | Command |
|---|---|
| Open a command prompt. | Click the Start button, Click Run, type cmd and Click the OK button. |
| Make a temporary directory. For this example, the directory is called "c:\tklmv1fp". | md c:\tklmv2fp |
| Change directory to the temporary directory. | cd c:\tklmv2fp |
| Download the Windows fix pack into the temporary directory. | Link to fix pack download table |
| Unzip the downloaded file. | unzip 2.0.0-ISS-TKLM-FP0007-WINDOWS.zip |
| Install the fix pack. | Enter the command: updateTKLM.bat [TIP_USERNAME TIP_PASSWORD] >> [ LOG_FILE ] where: -? Returns this command usage TIP_USERNAME defines the Tivoli Integrated Portal user name defined during installation (default: tipadmin). TIP_PASSWORD is the Tivoli Integrated Portal password for the TIP_USERNAME. LOG_FILE is a text log file used for collecting installation information. Defaults:
Note: See Known Issues for instructions
about verifying the Tivoli Integrated Portal default location and
defining the TIP_HOME variable using a case-sensitive directory path.
Note: The directory c:\IBM\tivoli\tiptklmV2 in the example above can be changed to any valid directory. The directory MUST exist prior to running the updateTKLM.bat command. |
| Check error codes for fix pack installation success | View the log file output produced by the updateTKLM.bat script. Check the error conditions produced by the fix pack installer. An error code of "0" is a success. |
| Instruction | Command |
|---|---|
| Open a ksh or bash shell. | if your default shell is not ksh or bash, run "exec ksh" or "exec bash". |
| Make a temporary directory. For this example, the directory is called "/tmp/tklmv1fp". | mkdir /tmp/tklmv2fp |
| Change directory to the temporary directory. | cd /tmp/tklmv2fp |
| Download the AIX, Solaris and Linux fix pack into the temporary directory. | Link to fix pack download table. |
| Untar and gunzip the downloaded file. | gunzip 2.0.0-ISS-TKLM-FP0007-lt;platform>.tar.gz tar -xvf 2.0.0-ISS-TKLM-FP0007-<platform>.tar where <platform> is: AIX, Linux-s390, Linux-x86 or Solaris |
| Install the fix pack. | Interactive mode command: or Batch mode command: ./updateTKLM.sh [TIP_USERNAME TIP_PASSWORD ] | tee -a [ LOG_FILE] 2>&1 where: Defaults: |
Performing the necessary tasks after
fix pack installation.
Verify Installation -
After the fix pack is installed, verify the Tivoli Key Lifecycle Manager and Tivoli Integrated Portal fix pack versions installed on your system.
Run the following commands to verify the Tivoli Key Lifecycle Manager
version:
AIX, Solaris and Linux:
/usr/ibm/common/acsi/bin/listIU.sh | grep TKLM-TIP-2
Windows: "C:\Program Files\IBM\Common\acsi\bin\listIU.cmd" | find
"TKLM-TIP-2"
or
"C:\Program Files (x86)\IBM\Common\acsi\bin\listIU.cmd" | find
"TKLM-TIP-2"
One of the contents for "Fix Name" listed should be TKLM-TIP-2007-TKLM-0007.
Fix pack installation error conditions
| Exit Code | Description | Possible Causes, Recovery Actions and Log Locations |
|---|---|---|
| -1 | User is not "root" user | AIX, Solaris and Linux: execute the fix pack installer as the "root" user. |
| -2 | /tmp directory does not exist | Problem creating temporary files because the expected temporary directory does not exist. Create the /tmp directory |
| 3 | TIP_HOME environment variable not found or contents of TIP_HOME environment variable incorrect | AIX, Solaris and Linux: Check if the $TIP_HOME environment variable
is valid. Ensure that the $TIP_HOME variable points to the directory
where Tivoli Integrated Portal is installed when Tivoli Key Lifecycle
Manager is deployed.
Windows: Check if the %TIP_HOME% environment variable is valid. Ensure that the %TIP_HOME% variable points to the directory where Tivoli Integrated Portal is installed when Tivoli Key Lifecycle Manager is deployed. |
| 7 | Failure to install Tivoli Integrated Portal fixes. | Check for generated error messages and error messages in the
following log files:
AIX, Solaris and Linux: /usr/ibm/common/acsi/logs and $TIP_HOME/logs Windows: %ProgramFiles%\IBM\Common\acsi\logs and %TIP_HOME%\logs If the error message is "Exception: Could not locate the specific root instance", verify the values of the TIP components by running the command: AIX, Solaris and Linux: run the /usr/ibm/common/acsi/bin/de_lsrootiu.sh command and set $TIP_HOME exactly as the directory path is displayed on the discriminant field, as output from the de_lsrootiu.sh command. Windows: C:\Program Files\IBM\Common\acsi\bin\de_lsrootiu.cmd or C:\Program Files (x86)\IBM\Common\acsi\bin\de_lsrootiu.cmd If the value of the de_lsrootiu command is C:\IBM\tivoli\tip with using exact case, you must set the environment variable, %TIP_HOME% with the correct directory name and in the exact case. For example: if %TIP_HOME% is set to C:\IBM\tivoli\tip, then you must set %TIP_HOME% to “C:\IBM\tivoli\tip” (not C:\ibm\tivoli\tip). Note: See Known Issues for instructions about verifying the Tivoli Integrated Portal default location and defining the TIP_HOME variable using a case-sensitive directory path.
Information about the specific failure is contained in the IA-TIPInstallFP17-00.log, which is located in the following directories:
|
| 8 | TIPadmin or TIPPassword incorrect. | An incorrect username or password was entered for TIPadmin or TIPPassword. |
| 9 | Failed to deploy the TKLM.ear file. | Check for error messages in the following log files:
AIX, Solaris, Linux: Refer to the $TIP_HOME/logs/updateTKLMEar.log and the $TIP_HOME/logs/TKLMInstall_2.0.0.7.log files. Windows: Refer to the %TIP_HOME%\logs\update\TKLMEar.log and the %TIP_HOME%\logs\TKLMInstall_2.0.0.7.log files |
| 10 | Failed to install Tivoli Key Lifecycle Manager fixes. | Check for error messages in the following log files:
AIX, Solaris and Linux: /usr/ibm/common/acsi/logs and $TIP_HOME/logs and the $TIP_HOME/logs/TKLMInstall_2.0.0.7.log file. Windows: %ProgramFiles%\IBM\Common\acsi\logs and %TIP_HOME%\logs and the %TIP_HOME%\logs\TKLMInstall_2.0.0.7.log file |
| 12 | Fix pack already installed | The TKLM fix pack trying to be installed, is equal to or lower than
the TKLM fix pack already on the system. - Error message has fix pack installer version and the TKLM fix pack that is already on the system. - Verify have expected fix pack installation package |
| 13 | Failed to stop WAS server1. | -Verify Tivoli Integrated Portal user ID and password specified are
valid. The error code from stopServer is <code from stopServer>. Note: Check TIP_HOME/profiles/TIPProfile/logs/server1/stopServer.log for the failure. |
| 14 | Failed to start WAS server1 | The error code from startServer is <code from startServer>. Note: Check $TIP_HOME/profiles/TIPProfile/logs/server1/startServer.log for the failure. |
| 15 | Passwords do not match | When prompted to reenter the password for verification, a different password was entered. Please try again. |
| 16 | Password cannot be empty | Please correct the password and try again. |
| 17 | Password contained a space. | Password contained a space. Please correct the password and try again. |
| 23 | The base TKLM version needs to be at least 2.0.0.0 |
The base TKLM version needs to be at least 2.0.0.0
See Known Issues for instructions on how to troubleshoot this problem. |
| 24 | Problem creating response files for TIP fix pack installation | Problem creating or accessing the TIP response file on Windows systems in %USERPROFILE% directory. See Known Issues for possible causes. |
| 30 | Vendor check does not match. | Vendor
check does not match. The fix pack you attempted to install was
provided by a different vendor than the currently installed fix pack
version.
Contact the vendor that supplied your copy of Tivoli Key Lifecycle Manager. The vendor will provide you with the correct fix pack for your Tivoli Key Lifecycle Manager installation. |
| APAR No. | Sev. | Abstract |
|---|---|---|
| IV66969 | 3 | ALLOWS CUSTOMERS USING DELL EKM 3.0 KEY MANAGERS TO MIGRATE TO TKLM 2.0.0.7 AND THEN SKLM 2.5 |
| APAR No. | Sev. | Abstract |
|---|---|---|
| IV17092 | 4 | Audit log writing is causing performance problems for several CLI commands in TKLMv2 when there are several threads processing |
| IV19719 | 3 | SETTING TRANSPORTLISTENER.SSL.CIPHERSUITES TO A TLS CIPHER SUITE DOES NOT WORK UNLESS "TLS" IS REPLACED BY "SSL" |
| IV20664 | 4 | DELETING EKM DIRECTORY AFTER MIGRATING TO TKLM |
| IV19125 | 2 | CTGKS0060E WHEN TRYING TO READ LTO ENCRYPTED TAPE |
| IV24361 | 3 | TKLMV2 FIX PACK INSTALL FAILS WITH ERROR "EXIT CODE = 24" |
| IV30863 | 3 | Backups generated by a previous fixpacks are restricted from restoring on later fixpacks. |
| IV30429 | 3 | TKLMV2 documentation should indicate the supported OS fix packs |
| APAR No. | Sev. | Abstract |
|---|---|---|
| IV13768 | 2 | FP002 AND FP004 INSTALLATION ON A TKLMV2000 MIGRATED FROM TKLM V1004 IS FAILING WITH ERROR CODE 23. |
| IV13758 | 3 | TKLMV2 INSTALLATION HANGS ON DEFINING TKLMDB2 USER |
| IV13818 | 2 | ERROR WHEN SETTING MULTIPLE CIPHER SUITES (NOT JSSE_ALL) (CTGKM3081E NOT A SUPPORTED CIPHER SUITE: ) |
| IV18082 | 3 | Tape can be read where the key is from a different key group(112634) |
| IV16267 | 2 | TKLMV2 EXPORT PERFORMANCE SIGNIFICANTLY SLOWER THAN TKLMV1 |
| IV16269 | 3 | TKLMSERVEDDATALIST COMMAND HAS A 2000 ENTRIES DISPLAY LIMIT |
| IV16585 | 1 | TKLMKEYLIST OPERATION IN V2 IS SIGNIFICANTLY SLOWER THAN IN V1 |
| APAR No. | Sev. | Abstract |
|---|---|---|
| IZ91421 | 3 | TKLM V2 FP (2.0.0-TIV-TKLM-FP0002) updateTKLM.sh script may fail (111753) |
| IZ92273 | 3 | Documentation: MIGRATING WHEN USING A LINK |
| IV06625 | 3 | TKLMV2 FIX PACK INSTALL FAILS ON SYSTEM THAT WAS PREVIOUSLY MIGRATED FROM TKLMV1 (112259) |
| IV06750 | 4 | UNEXPECTED ERROR EE0F WHEN NO DEFAULT KEY ALIAS SET UP (112323) |
| IV06837 | 3 | DATABASEBACKUPDIRECTORY PARAMETER ON THE TKLM BACKUP COMMAND (112261) |
| IV07604 | 3 | Backup encrypted with PBEWithMD5AndDES with TripleDES set (112307) |
| IV08114 | 2 | RESTORE OF ROLLOVER INFORMATION DOES NOT WORK / CTGKM0249E (112372, 112389) |
| IV08545 | 2 | TKLM V2 on AIX 7.1 install fails with 0514-519 AIO error (112373) |
| IV08668 | 3 | THE SSL LISTENER STOPS WORKING AFTER THE ALIAS IS NOT FOUND (112495) |
| IV11892 | 3 | Backup/restore events only logged if Audit=High (107826) |
| IV11893 | 3 | "CTGKM3020E NOT A RECOGNIZED DEVICE GROUP" ERROR OCCURED WHILE DELETING A USER DEFINED DEVICE GROUP (111580) |
| IV11896 | 3 | USING CLI TO ADD A ROLLOVER TASK, TKLM CAN NOT RECOGNIZE PAST DATES. (111702) |
| IV11915 | 3 | SHADOW KEYSTORE FLUSH PRODUCES ERROR "CTGKM0002E COMMAND FAILED: JAVA.SECURITY.KEYSTOREEXCEPTION: PASSWORD IS NOT ASCII" (112214) |
| IV11931 | 3 | TKLM DB2 INSTANCE IS CREATED ON C DRIVE |
| APAR No. | Sev. | Abstract |
|---|---|---|
| IZ84418 | 3 | After deleting a user-defined device group, the server status panel on the TKLM welcome page is blank. |
| IZ87599 | 3 | CTGKM0239E Cannot restore from backup error when trying to restore a backup file |
| IZ89216 | 1 | After the keystore password is modified by the tklmKeystoreUpdate() CLI, Tivoli Integtrated Portal should be restarted. |
| IZ90077 | 3 | WWN written to drivetable on every new connection |
| IZ90098 | 3 | Cert usage changed even if Cancel button clicked in TKLM GUI |
| IZ90107 | 3 | Performance degrades when storing a large amount of key material. |
| IZ90180 | 3 | Machine affinity attribute set as NULL on DS5000 devices. |
| IZ90182 | 3 | TKLM UI backup confirm prompt does not disappear using Internet Explorer. Second backup is taken when you click "OK" |
| IZ90192 | 3 | Configurable KMIP SSL timeout value. |
| IZ90197 | 3 | keygroup mentioned instead of key in the audit |
| IZ90198 | 3 | Debug log logging java object data instead of useful data |
| IZ90203 | 3 | Documentation: The error CTGKM1129E "Target and source device groups family type does not match" is displayed when creating a key group |
| IZ90207 | 4 | Documentation: Attributes that cannot be deleted show up as examples in delete command |
| IZ90208 | 3 | Documentation: Password length limit on creation of new db2 admin on Windows |
| IZ90213 | 3 | Temporary directory remains after restore on Windows platforms |
Copyright and trademark
information
http://www.ibm.com/legal/copytrade.shtml
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.
Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel
Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are
trademarks or registered trademarks of Intel Corporation or its subsidiaries in
the United States and other countries.
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:
| Change Date | Reason | Modified by |
|---|---|---|
| 5 November 2014 | Create initial 2.0.0-ISS-TKLM-FP0007 | lla |
| 10 November 2014 | 2.0.0-ISS-TKLM-FP007.README.html update to clarify the valid values for OutputCount parameter | lla |
| 17 November 2014 | 2.0.0-ISS-TKLM-FP007.README.html finalized | lla |