IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Administrator's Guide > Securing communications > Use the GSKit iKeyman utility to work with key databases and certificates
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Set the JRE for GSKit and starting Key Manager
You must set the path to the Java Runtime Environment before starting GSKit. Otherwise, you might get an error similar to Failed to parse JAVA_HOME setting.
Procedure
- From the command prompt, run this script to get the IBM Java location:
install_dir\InstallITM\GetJavaHome.bat
Set the JAVA_HOME variable to point to the IBM Java location.
Get the GSKit location by running this script: install_dir\InstallITM\GetGSKitHome.bat
Execute the following command: $JAVA_HOME\jre\bin\ikeyman.exe [properties]where, [properties] can be zero or more system properties.
- From the console, run this script to get the IBM Java location:
install_dir/bin/CandleGetJavaHome.sh
- Export variable JAVA_HOME to point to the IBM Java path.
- Execute the following command:
$JAVA_HOME\jre\bin\ikeyman.exe [properties]where [properties] can be zero or more system properties.
- From the console, run this script to get the IBM Java location:
install_dir/bin/CandleGetJavaHome.sh
- Export variable JAVA_HOME to point to the IBM Java path. For 64-bit, the gsk7ikm has to be 64-bit Java.
- Check the path for a local GSKit by looking in this file:
install_dir/config/gsKit.config
GskitInstallDir points to a 32–bit GSKit and GskitInstallDir_64 points to a 64–bit GSKit.
- Start IBM Key Management (through the graphical utility that requires X Windows System) by running the following command:
GskitInstallDir/bin/gsk7ikm_32
Parent topic:
Use the GSKit iKeyman utility to work with key databases and certificates