Thursday, March 26, 2009

IKEYCMD ( IKEYMAN ) Command Line Interface (gsk7cmd)

Environment Set Up for IKEYCMD Command Line Interface
To run IKEYMAN , set up environment variables to use the IKEYCMD command line interface
as follows:
1. Set your PATH to where your Java or JRE executable resides:
EXPORT PATH=/opt/IBMJava/bin:$PATH

2. Set the following CLASSPATH environment variable:
EXPORT CLASSPATH=/usr/local/ibm/gsk/classes/cfwk.zip:/usr/local/ibm/gsk/classes/gsk4cls.jar:$CLASSPATH

Once completed, IKEYCMD should run from any directory. To run an IKEYCMD command,
use the following syntax:
java com.ibm.gsk.ikeyman.ikeycmd (command)

You can substitute JRE for Java, depending on whether you are using a JRE or JDK.
Example:
jre com.ibm.gsk.ikeyman.ikeycmd (command)

IKEYCMD Command Line Syntax
The syntax of the Java CLI is: java [-Dikeycmd.properties= com.ibm.gsk.ikeyman.ikeycmd (object) (action)[options]

where:
-Dikeycmd.properties Specifies the name of an optional properties file to use for this Java
invocation. A default properties file, ikeycmd.properties, is provided as a sample file that can be modified and used by any Java application.

Object is one of the following:

-keydb Actions taken on the key database (either a CMS key database file, a WebDB keyring file, or SSLight class)
-cert Actions taken on a certificate
-certreq Actions taken on a certificate request
-help Display help for the IKEYCMD invocations
-version Display version information for IKEYCMD

Action is the specific action to be taken on the object, and options are the options, both required
and optional, specified for the object and action pair.

Note: The object and action keywords are positional and must be specified in the selected
order. However, options are not positional and can be specified in any order, provided
that they are specified as an option and operand pair.

User Interface Task Reference
IKEYCMD command line interface tasks are summarized in the following table.

IKEYMAN and IKEYCMD task

Create a new key database and specify the
database password

Create a new key pair and certificate request
Create a self-signed certificate
Export a key to another database or PKCS12 file
Import a key from another database or PKCS12
file
List certificate authorities (CAs) and certificate
requests
Open a key database

Receive a CA-signed certificate into a key
database
Show the default key in a key database

Store the root certificate of a CA
Store the encrypted database password in a stash
file

No comments:

Post a Comment

Bookmark and Share
Join the TrafficZap Exchange