IBM Security Key Lifecycle Manager Version 3.0.1 -- Distributed Platforms Fix Pack 4 README

Abstract

Readme documentation for IBM Security Key Lifecycle Manager for Distributed Platforms, Version 3.0.1 Fix Pack 4 including installation-related instructions, prerequisites and corequisites, and a list of fixes. All IBM Security Key Lifecycle Manager for Distributed Platforms fix packs are cumulative.

Fix pack publish date: 31st March 2020

Last modified date: 31st March 2020

Contents

List of fixes and features
Download locations
Platform support
Prerequisites and corequisites
Known limitations

Installation information
Installing the IBM Security Key Lifecycle Manager fix pack
Prior to fix pack installation
Performing the necessary tasks after fix pack installation
Installing fix pack when IBM Security Key Lifecycle Manager Multi-Master environment is set up
Uninstalling the IBM Security Key Lifecycle Manager along with fix pack
Copyright and trademark information
Document change history

List of fixes and features

Features included in Version 3.0.1.4

New REST API to update multiple client certificates as per WWNN.
Support for checking chain of trusted certificates.
New unique return code for KMIP requests from untrusted clients.

For more information, see http://www.ibm.com/support/docview.wss?uid=ibm10873334

Features included in Version 3.0.1.2

Following security fixes have been included in 3.0.1.2:

Cross-Site Scripting
Cross-Site Request Forgery
Weak password policy

Performance improvements for KMIP QUERY in Multi-Master configuration.

New Features Provided by Version 3.0.1.1

http://www.ibm.com/support/docview.wss?uid=ibm10873334

APAR fixes included in Fix Pack 3

APAR No.	Sev.	Abstract	Remarks
IJ20422	2	UNABLE TO CONFIGURE SKLM TO USE DIFFERENT DIRECTORY TO STORE BACKUPS	-

APAR fixes included in Fix Pack 2

APAR No.	Sev.	Abstract	Remarks
IJ19775	1	INSTALLATION OF 3.0.1 FP FAILS ON STANDBY SERVERS IN MM SETUP	-
IJ17579	3	UNABLE TO INSTALL FIXPACKS WITH LDAP USERNAMES WITH SPECIAL CHARACTERS IN THEM	-
IJ13131	3	NO "CONFIGURED CLONE" TABLE IN REPLICATION TAB OF WELCOME PAGE ON IBM SECURITY KEY LIFECYCLE MANAGER 3.0.1	This APAR was fixed in 3.0.1 fix pack 1 but reproduced again on Japanese OS, fix for that has gone in this fix pack.

APAR fixes included in Fix Pack 1

APAR No.	Sev.	Abstract
IJ13131	3	NO "CONFIGURED CLONE" TABLE IN REPLICATION TAB OF WELCOME PAGE ON IBM SECURITY KEY LIFECYCLE MANAGER 3.0.1
IJ15006	3	ERROR: COULD NOT FIND OR LOAD MAIN CLASS KLM.SERVER.MIGRATE.EKM21.BACKUP.BACKUPHANDLEREKM21
IJ13132	3	IT IS UNEXPECTED 'START REPLICATION SERVER' BUTTON APPEARS AND "REPLICATE NOW" BUTTON IS GRAY OUT IN REPLICATION PAGE

IBM Security Key Lifecycle Manager, Version 3.0.1 - Supported Platforms

For more information about supported operating systems, see IBM Security Key Lifecycle Manager Support Matrix.

Download location

Download IBM Security Key Lifecycle Manager, Version 3.0.1 fix pack from IBM Fix Central

1. Go to IBM Fix Central home page: http://www.ibm.com/support/fixcentral/

2. For the Product Group, select "Security Systems"

3. For the Product, select "IBM Security Key Lifecycle Manager".

4. For Installed Version, select your system's appropriate version level, ie. 3.0.1.

5. For Platform, select the appropriate platform. Choose "Continue".

6. At the Identify Fixes page, select the "Browse for Fixes" radio button (default) and choose "Continue".

7. At the Select Fixes page, choose Fix Pack "3.0.1-ISS-SKLM-FP0004". Choose "Continue".

8. You might be prompted to "Sign In". If you do not have an ID, click on the "register now" link and follow the registration steps as appropriate.

9. At the Download Options page, choose a download method (default is "Download using Download Director").

10. Select the associated files and README for Fix Pack 3.0.1-ISS-SKLM-FP0004 and select "Download now".

Platforms updated by this Fix Pack

Product/Component Name	Platform	File Name
IBM Security Key Lifecycle Manager version 3.0.1 Fix Pack - 3.0.1-ISS-SKLM-FP0004	AIX	3.0.1-ISS-SKLM-FP0004-AIX.tar.gz
IBM Security Key Lifecycle Manager version 3.0.1 Fix Pack - 3.0.1-ISS-SKLM-FP0004	Linux	3.0.1-ISS-SKLM-FP0004-Linux.tar.gz
IBM Security Key Lifecycle Manager version 3.0.1 Fix Pack - 3.0.1-ISS-SKLM-FP0004	zLinux (System z)	3.0.1-ISS-SKLM-FP0004-zLinux.tar.gz
IBM Security Key Lifecycle Manager version 3.0.1 Fix Pack - 3.0.1-ISS-SKLM-FP0004	Linux PPC	3.0.1-ISS-SKLM-FP0004-LinuxPPC.tar.gz
IBM Security Key Lifecycle Manager version 3.0.1 Fix Pack - 3.0.1-ISS-SKLM-FP0004	Windows	3.0.1-ISS-SKLM-FP0004-Windows.zip

For current version 3.0.1 installations: This fix pack can be installed on systems with IBM Security Key Lifecycle Manager, Version 3.0.1 GA or 3.0.1 fix pack 1 or 3.0.1 fix pack 2.

Prerequisites and corequisites

IBM Security Key Lifecycle Manager, Version 3.0.1 GA, 3.0.1 fix pack 1, 3.0.1 fix pack 2, or 3.0.1 fix pack 3.

Known limitations

Rollback of installed fix pack is not supported.

Installing the IBM Security Key Lifecycle Manager fix pack

Prior to fix pack installation

1. Ensure that IBM Security Key Lifecycle Manager is not in use before installing the fix pack. If your facility has a "service maintenance outage" process, consider installing this fix pack during an arranged service outage.

2. A backup of your IBM Security Key Lifecycle Manager server should be performed prior to installing this fix pack. Follow the steps Backing up critical files in the Administering section of the IBM Security Key Lifecycle Manager Product Manuals.

Backup WebSphere Application Server files

S.No.	Instruction	Windows Commands	Linux / AIX Commands
1.	Windows - Open a command prompt. Linux / AIX - Open a ksh or bash shell.	Click the Start button, click Run, type cmd, and click the OK button.	If your default shell is not ksh or bash, run "exec ksh" or "exec bash".
2.	Stop WebSphere Application Server.	<WAS_HOME>\bin\stopServer.bat server1 -username <WAS_ADMIN> -password <WAS_PASSWORD>	<WAS_HOME>/bin/stopServer.sh server1 -username <WAS_ADMIN> -password <WAS_PASSWORD>
3.	Make a temporary directory.	mkdir <WAS_BACKUP_DIRECTORY> Example: mkdir c:\wasbackup	mkdir <WAS_BACKUP_DIRECTORY> Example: mkdir /tmp/wasbackup
4.	Change to the temporary directory.	cd c:\wasbackup	cd /tmp/wasbackup
5.	Copy or archive the files from the directory where WebSphere Application Server is installed.	xcopy /y /e /d <WAS_HOME> c:\wasbackup	tar -cvf wasbackup.tar <WAS_HOME>/*
6.	Start WebSphere Application Server.	<WAS_HOME>\bin\startServer.bat server1 Where: <WAS_HOME> is the directory where WebSphere Application Server is installed (default:C:\Program Files\IBM\WebSphere\AppServer).	<WAS_HOME>/bin/startServer.sh server1 Where: <WAS_HOME> is the directory where WebSphere Application Server is installed (default: /opt/IBM/WebSphere/AppServer).

Before fix pack installation

Instruction	Steps
Make a repository directory.	Open a command prompt. Make a repository, i.e. a directory where you extract the update installer. Windows Default repository directory is C:\sklminstall_windowsfp mkdir C:\sklminstall_windowsfp Unix Default repository directory is /sklminstall_linuxfp mkdir /sklminstall_linuxfp
Change directory to the directory created.	Windows cd C:\sklminstall_windowsfp Unix cd /sklminstall_linuxfp
Download the fix pack into the repository directory.	Link to fix pack download table
Extract the downloaded file.	Windows Extract the downloaded file: 3.0.1-ISS-SKLM-FP0004-Windows.zip Unix Extract the downloaded file: 3.0.1-ISS-SKLM-FP0004-Linux.tar.gz

Steps for installing fix pack for IBM Security Key Lifecycle Manager, Version 3.0.1 on Windows and Unix operating systems in GUI mode

Instruction	Steps
Stop WebSphere Application Server, update Java SDK, and then start Installation Manager in GUI mode.	Windows Open a command window, and change to the repository directory. Example: C:\sklminstall_windowsfp Run the following command. updateSKLM.bat <IM_INSTALL_LOCATION> <WAS_HOME> <WAS_ADMIN> <WAS_PASSWORD> Example: updateSKLM.bat "c:\Program Files\IBM\Installation Manager" "c:\Program Files\IBM\WebSphere\AppServer" wasadmin wasadminpwd Unix Open a command window, and change to the repository directory. Example: /sklminstall_linuxfp Run the following commands. chmod +x ./updateSKLM.sh ./updateSKLM.sh <IM_INSTALL_LOCATION> <WAS_HOME> <WAS_ADMIN> <WAS_PASSWORD> Example: updateSKLM.sh /opt/IBM/InstallationManager /opt/IBM/WebSphere/AppServer wasadmin wasadminpwd Where: <IM_INSTALL_LOCATION> refers to the installation root directory for IBM Installation Manager. Default value on Windows system is “c:\Program Files\IBM\Installation Manager”. For Linux system: “/opt/IBM/InstallationManager” <WAS_HOME> refers to installation root directory for WebSphere Application Server (WAS). Default value on Windows system is "c:\Program Files\IBM\WebSphere\AppServer". For Linux system: /opt/IBM/WebSphere/AppServer <WAS_ADMIN> refers to the ID for the WebSphere Application Server Administrator. <WAS_PASSWORD> refers to the password for the WebSphere Application Server Administrator.
Select the IBM Security Key Lifecycle Manager, Version 3.0.1 software package group.	1. Select the base offering software package group (IBM Security Key Lifecycle Manager, Version 3.0.1). 2. Click Next. 3. In the Update Packages updates panel, select Version 3.0.1.4, and click Next.
Provide credentials for WebSphere Application Server admin user (default: wasadmin) SKLM admin user (default: SKLMAdmin) and DB2 user (default: sklmdb31).	In the Update Packages Configuration for IBM Security Key Lifecycle Manager v3.0.1.4 panel: Enter Username and Password for Application Server Administrator. Enter Username and Password for IBM Security Key Lifecycle Manager Application Administrator. Enter Username and Password for IBM DB2 user. Click the Validate Credentials button. Validation might take few minutes, wait till the Next button is enabled. Click Next.
Click the Update button.	In the Update Packages > Summary panel, review the software packages that you want to install and click Update. After Installation Manager successfully updates the fix pack for the services that you select, a message is displayed.

Steps for installing a fix pack for IBM Security Key Lifecycle Manager, Version 3.0.1 on Windows and Unix operating systems in silent mode

Instruction	Steps
Installation Manager utility to encrypt the passwords for users as required.	Open a command window. Change to the <IM_INSTALL_LOCATION>/eclipse/tools directory. Windows Run the following command to generate an encrypted password: imcl.exe encryptString <password_to_encrypt> Unix Run the following command to generate an encrypted password: ./imcl encryptString <password_to_encrypt>
Make a backup of the response file.	Create a backup of original response file SKLM_Silent_Update_<platform>_Resp.xml by renaming it. For example: SKLM_Silent_Update_<platform>_Resp_original.xml This file will be located in the sklm sub-folder under the repository directory where fix pack is extracted.
Edit the response file.	Windows Edit the silent response file "SKLM_Silent_Update_<platform>_Resp.xml". Edit the repository location to point to current location of installables. (Sample: <repository location='C:\sklminstall_windowsfp\sklm'/>) Edit WASAdmin username and password (Password need to be encrypted). (Sample: <data key='user.WAS_ADMIN_ID,com.ibm.sklm301.win>value='wasadmin'/> <data key='user.WAS_ADMIN_PASSWORD,com.ibm.sklm301.win>value='e9PjN93MeQxwnSs9VXJFMw=='/>) Edit SKLMAdmin username and password (Password need to be encrypted). (Sample: <data key='user.SKLM_ADMIN_ID,com.ibm.sklm301.win>value='SKLMAdmin'/> <data key='user.SKLM_ADMIN_PASSWORD,com.ibm.sklm301.win>value='9YTRJMRIydDSdfhaHPs1ag=='/>) Edit DB user username and password (Password need to be encrypted). (Sample: <data key='user.DB2_ADMIN_PWD,com.ibm.sklm301.db2.win.ofng' value='sklmdb31'/> <datadata key='user.CONFIRM_PASSWORD,com.ibm.sklm301.db2.win.ofng' value='QTh/0AiFvrljhs9gnOYkGA=='/>) Unix Edit the silent response file "SKLM_Silent_Update_<platform>_Resp.xml". Edit the repository location to point to current location of installables. (Sample for Linux:<repository location='/sklminstall_linuxfp/sklm'/>) Edit WASAdmin username and password (Password need to be encrypted). (Sample: <data key='user.WAS_ADMIN_ID,com.ibm.sklm301.linux>value='wasadmin'/> <data key='user.WAS_ADMIN_PASSWORD,com.ibm.sklm.Linux>value='e9PjN93MeQxwnSs9VXJFMw=='/>) Edit SKLMAdmin username and password (Password need to be encrypted). (Sample: <data key='user.SKLM_ADMIN_ID,com.ibm.sklm301.linux>value='SKLMAdmin'/> <data key='user.SKLM_ADMIN_PASSWORD,com.ibm.sklm301.linux>value='9YTRJMRIydDSdfhaHPs1ag=='/>) Edit DB user username and password (Password need to be encrypted). (Sample: <data key='user.DB2_ADMIN_ID,com.ibm.sklm301.db2.lin.ofng' value='sklmdb31'/> <data key='user.DB2_ADMIN_PWD,com.ibm.sklm301.db2.lin.ofng' value='QTh/0AiFvrljhs9gnOYkGA=='/>)
Install the fix pack.	Windows Open a command window, and change to the repository directory. Example: C:\sklminstall_windowsfp Run the following command: silent_updateSKLM.bat <IM_INSTALL_LOCATION> <WAS_HOME> <WAS_ADMIN> <WAS_PASSWORD> Example: silent_updateSKLM.bat "c:\Program Files\IBM\Installation Manager" "c:\Program Files \IBM\WebSphere\AppServer" wasadmin wasadminpwd Unix Open a command window, and change to the repository directory. Example: /sklminstall_linuxfp Run the following commands: chmod +x ./silent_updateSKLM.sh ./silent_updateSKLM.sh <IM_INSTALL_LOCATION > <WAS_HOME> <WAS_ADMIN> <WAS_PASSWORD> Example: ./silent_updateSKLM.sh /opt/IBM/InstallationManager /opt/IBM/WebSphere/AppServer wasadmin wasadminpwd. Where: IM_INSTALL_LOCATION refers to the installation root directory for IBM Installation Manager. Default value on Windows system is “c:\Program Files\IBM\Installation Manager”. For Linux system: “/opt/IBM/InstallationManager” <WAS_HOME> refers to installation root directory for WebSphere Application Server. Default value on Windows system is "c:\Program Files\IBM\WebSphere\AppServer". For Linux system: /opt/IBM/WebSphere/AppServer WAS_ADMIN refers to the ID for the WebSphere Application Server Administrator. WAS_PASSWORD refers to the password for the WebSphere Application Server Administrator.
Check logs for fix pack installation success.	View the log file output produced for successful fix pack installation. Log files are located at: <Installation_Manager_Home>/logs/native

Performing the necessary tasks after fix pack installation

1. Verify Installation - Run the wsadmin AdminTask.tklmVersionInfo() command.

Unix users:

Open a shell (ksh or bash).

Type: cd <WAS_HOME>/bin/

Type: ./wsadmin.sh -lang jython -username <sklmadminUserID> -password <sklmadminPassword>
Example: ./wsadmin.sh -lang jython -username sklmadmin -password sklmpassword

At the wsadmin> prompt, type: print AdminTask.tklmVersionInfo()

Windows users:

Open a command prompt.

Type: cd <WAS_HOME>\bin

wsadmin -lang jython -username <sklmadminUserID> -password <sklmadminPassword>

Example: wsadmin.bat -lang jython -username sklmadmin -password sklmpassword
At the wsadmin> prompt, type: print AdminTask.tklmVersionInfo()

Check the output of the tklmVersionInfo command:

IBM Security Key Lifecycle Manager Version = 3.0.1.4

IBM Security Key Lifecycle Manager Build Level = 202003301015

WebSphere Application Server Version = 9.0.0.5

DB2 Version = 11.1.2.2

Java Version = JRE 1.8.0_144 IBM J9 VM 2.9

Operating System Version = Linux:4.4.73-5-default:s390x

Agent Version : 1.0

You can also view the detailed server information such as version number of IBM Security Key Lifecycle Manager, DB2, Java, and WebSphere Application Server through GUI.

Log on to the graphical user interface.

On the welcome page header bar, click the Help icon.

Click About.

2. A backup of your IBM Security Key Lifecycle Manager server must be performed after installing this fix pack. Follow the steps Backing up critical files in the Administering section of the IBM Security Key Lifecycle Manager Product Manuals.

Installing fix pack when IBM Security Key Lifecycle Manager Multi-Master environment is set up

Prerequisite for fix pack installation:

If the original primary master server is currently acting as a standby master server, promote it to primary and then, install the fix pack. Otherwise the database updates are not applied to the cluster. To promote a master server to primary, follow the instructions given in this topic: https://www.ibm.com/support/knowledgecenter/en/SSWPVP_3.0.1/com.ibm.sklm.doc/admin/tsk/tsk_ic_admin_multimaster_promote_node_to_primary.html

Steps:

Stop WebSphere Application Server on all masters in the multi-master cluster. You can stop WebSphere Application Server on the masters (Primary, Standby, or non-HADR masters) in any sequence.

Open a command prompt.

Go to the <WAS_HOME>\bin directory.
Windows
C:\Program Files\IBM\WebSphere\AppServer\bin

Linux
/opt/IBM/WebSphere/AppServer/bin

Stop the server.
Windows
stopServer.bat server1 -username <wasadmin> -password <mypwd>

Linux
./stopServer.sh server1 -username <wasadmin> -password <mypwd>
Stop Agent on all masters in the multi-master cluster. You can stop Agent on the masters (Primary, Standby, or non-HADR masters) in any sequence.

Open a command prompt.

Go to the <SKLM_INSTALL_HOME>\agent directory.

Windows
C:\Program Files\IBM\SKLMV301\agent

Linux
/opt/IBM/SKLMV301/agent
Stop the Agent.

Windows
stopAgent.bat <WAS_HOME>
stopAgent.bat "C:\Program Files\IBM\WebSphere\AppServer"

Linux
./stopAgent.sh <WAS_HOME>
./stopAgent.sh /opt/IBM/WebSphere/AppServer

Apply fix pack on the HADR primary master. After the fix pack installation, run the following verification tasks:

Login to IBM Security Key Lifecycle Manager and check the version number.
Ensure that the HADR primary master is running and available for use.

Apply fix pack on the HADR standby master. After the fix pack installation, run the following verification tasks:

Login to IBM Security Key Lifecycle Manager and check the version number.
Ensure that the HADR standby master is running and available for use.

Apply fix pack on all the non-HADR masters. After the fix pack installation, run the following verification tasks:

Login to IBM Security Key Lifecycle Manager and check the version number.
Ensure that all the non-HADR masters are running and available for use.

Uninstalling the IBM Security Key Lifecycle Manager along with fix pack

Note: This will uninstall the entire product package i.e. IBM Security Key Lifecycle Manager, IBM DB2 and WebSphere Application Server, and all your data will be lost. Please take backup before uninstalling.

Steps for uninstalling IBM Security Key Lifecycle Manager version 3.0.1 along with fix pack on Windows and Unix operating systems in GUI mode

Instruction

Steps

Before you begin.

Stop WebSphere Application Server before you uninstall IBM Security Key Lifecycle Manager.

Start uninstalling the IBM Security Key Lifecycle Manager in GUI mode.

Windows

Browse to <IM_INSTALL_LOCATION>\eclipse and double-click IBMIM to start IBM Installation Manager in GUI mode.
In IBM Installation Manager, click Uninstall. The Uninstall Packages window opens.
Select the check boxes to uninstall IBM Security Key Lifecycle Manager, DB2, and the WebSphere Application Server.
Click Next. Type the WebSphere Application Server Administrator user ID and the password.
Click Next. The Summary panel window opens.
Review the software packages to be uninstalled and their installation directories; click Uninstall.

Unix

Browse to <IM_INSTALL_LOCATION>/eclipse and run IBMIM.
In IBM Installation Manager, click Uninstall. The Uninstall Packages window opens.
Select the check boxes to uninstall IBM Security Key Lifecycle Manager, DB2, and the WebSphere Application Server.
Click Next. Type the WebSphere Application Server Administrator user ID and the password.
Click Next. The summary panel opens.
Review the software packages to be uninstalled and their installation directories.
Click Uninstall.

Steps for uninstalling IBM Security Key Lifecycle Manager version 3.0.1 along with fix pack on Windows and Unix operating systems in silent mode

Instruction

Steps

Go to the repository directory.

1. Go to the repository directory
Example:
Windows: c:\sklminstall_windowsfp
Linux: /sklminstall_linuxfp

2. Backup the original response file SKLM_Uninstall_<platform>_Resp.xml by renaming it to SKLM_Uninstall_<platform>_Resp_original.xml

3. Edit the silent response file "SKLM_Uninstall_<platform>_Resp.xml".
Edit WASAdmin username and password (password need to be encrypted).
Windows:
(Sample:
<data key='user.WAS_ADMIN_ID,com.ibm.sklm301.win' value='wasadmin'/>
<data key='user.WAS_ADMIN_PASSWORD,com.ibm.sklm301.win' value='e9PjN93MeQxwnSs9VXJFMw==>)
Unix:
(Sample:
<data key='user.WAS_ADMIN_ID,com.ibm.sklm301.linux' value='wasadmin'/>
<data key='user.WAS_ADMIN_PASSWORD,com.ibm.sklm301.linux' value='e9PjN93MeQxwnSs9VXJFMw=='/>

Start uninstalling IBM Security Key Lifecycle Manager in silent mode.

Windows

Open a command prompt.
Change to <IM_INSTALL_LOCATION>\eclipse\tools directory.
Execute the following command:
imcl.exe -input <PATH_TO_UNINSTALL_RESPONSE_FILE> -silent

Example:
imcl.exe -input "c:\sklminstall_windowsfp\SKLM_Uninstall_Win32_Resp.xml" -silent

Unix

Open terminal.
Change to <IM_INSTALL_LOCATION>/eclipse/tools directory.
Execute the following command:
./imcl -input <PATH_TO_UNINSTALL_RESPONSE_FILE> -silent

Example:
./imcl -input /sklminstall_linuxfp/SKLM_Uninstall_Linux_Resp.xml -silent

Where:

<IM_INSTALL_LOCATION> refers to the installation root directory for IBM Installation Manager. Default value on Windows system is “c:\Program Files\IBM\Installation Manager”. For Linux system: “/opt/IBM/InstallationManager”

<PATH_TO_UNINSTALL_RESPONSE_FILE> refers to the uninstallation response file provided or bundled with the update installer.

<platform> refers to the operating system where the fix pack is being installed / uninstalled. For example: SKLM_Uninstall_<platform>_Resp.xml on Linux would be SKLM_Uninstall_Linux_Resp.xml

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:

the Excluded Components are provided on an "AS IS" basis
IBM DISCLAIMS ANY AND ALL EXPRESS AND IMPLIED WARRANTIES AND CONDITIONS WITH RESPECT TO THE EXCLUDED COMPONENTS, INCLUDING, BUT NOT LIMITED TO, THE WARRANTY OF NON-INFRINGEMENT OR INTERFERENCE AND THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
IBM will not be liable to you or indemnify you for any claims related to the Excluded Components
IBM will not be liable for any direct, indirect, incidental, special, exemplary, punitive or consequential damages with respect to the Excluded Components.

Document change history

Change Date	Reason	Modified by
2nd March 2020	Created initial draft for 3.0.1-ISS-SKLM-FP0004	AP
31st March 2020	Created final draft for 3.0.1-ISS-SKLM-FP0004	AP

End of Document