IBM Tivoli Monitoring, Version 6.3

Global Security Toolkit

IBM® Tivoli® Monitoring includes the Global Security Toolkit (GSKit) for SSL processing as used in SPIPE and HTTPS. GSKit is installed by default on all distributed components, and its utilities are used to create and manage the encryption of data between components through the use of digital certificates.

Note: Do not uninstall or manipulate the GSKit during installation. This may cause functional regression in other products or make them inoperable. The GSKit will automatically install the most recent build if another version GSKit already exists.

On z/OS®, GSKit is known as the Integrated Cryptographic Service Facility, or ICSF. If ICSF is not installed on the z/OS system, the monitoring server uses an alternative, less secure encryption scheme. Since both components must be using the same scheme, if the hub system does not use ICSF, you must configure the Tivoli Enterprise Portal to use the less secure scheme (EGG1) as well. For more information, see Configuring the Tivoli Enterprise Monitoring Server on z/OS.

A default certificate and key are provided with GSKit at installation. A stash file provides the database password for unattended operation. You can also use the key management facilities in GSKit to generate your own certificates. For information about the GSKit command line interface, see the GSKCapiCmd Users Guid at ftp://ftp.software.ibm.com/software/webserver/appserv/library/v80/GSK_CapiCmd_UserGuide.pdf.

Note:
  1. The IBM Tivoli Monitoring installer no longer modifies the system GSKit. If necessary, it installs a local copy of GSKit that is private to Tivoli Monitoring.
  2. In 64-bit environments, both the 64-bit and the 32-bit GSKit are installed, to support both 64-bit and 32-bit Tivoli Monitoring components.


Feedback