Netscape MANAGEMENT SYSTEM 4.5 Installation And Setup Manual page 453

Enter information as appropriate. If you choose JAR as your file type, you
d.
are required to provide the path to the JAR file that contains the DLLs. If
you choose DLL as your file type, in addition to the path to the DLL you
are also required to provide a name for the module you're attempting to
install (so as to help you identify it easily later). The sample in the figure
shows how you would install an nCipher
Pick DLL to add a UNIX shared/dynamic library, which on a Solaris
machine is identified with the
Click OK.
e.
• To install the PKCS #11 module using the
Locate the CMS instance for which you want to install the PKCS #11
a.
module.
Open a terminal window.
b.
Go to the configuration directory of Administration Server; it is located
c.
here:
<server_root>/admin-serv/config
At the prompt, enter this command:
d.
<server_root>/shared/bin/modutil -dbdir . -nocertdb
-create
This creates the required security module database file (
configuration directory.
At the prompt, enter this command:
e.
<server_root>/shared/bin/modutil -dbdir . -nocertdb
-add <module_name> -libfile <library_file>
<library_file>
containing the implementation of the PKCS #11 interface module.
<module_name>
you specified in Step 1 when you installed the drivers).
For example, if you are installing a Litronic
look like this:
<server_root>/shared/bin/modutil -dbdir . -nocertdb
-add CryptOS -libfile core32
Copy the new
f.
location:
<server-root>/cert-<instance_id>/config/
This overwrites the old
extension.
.so
specifies the path to the DLL or other library file
specifies the name of the PKCS #11 module (which
(
secmod.db secmodule.db
secmod.db
Chapter 14
Tokens for Storing CMS Keys and Certificates
TM
token.
tool:
modutil
secmod.db
TM
token, the command would
on Unix) to the following
in this directory.
Managing CMS Keys and Certificates
) in the
453