Technical data

Setting Up Node Manager
Administration Guide 3-7
Step 2: Converting a WebLogic-Style Private Key
If you want to use WebLogic-style certificates with Node Manager, you will first need
to convert the private key to the newer PKCS #5/#8 format. A tool to do this is
provided with the WebLogic software.
The tool for converting WebLogic-style certificates for use with Node Manager is
called
wlkeytool and is located in:
n The /bin directory under the root WebLogic installation directory on Windows
systems
n The /lib directory of the root WebLogic installation directory on UNIX
systems
The syntax for using
wlkeytool is:
wlkeytool old_key new_key
You will be prompted for the private key password to unlock the old key. Press return
if it has no password. You will then be prompted to enter a password to use in
encrypting the new key. A password is required for use with Node Manager.
For example:
wlkeytool demokey.pem demokey_new
Step 3: Merging the Certificates into a Single Certificate File
WebLogic Server uses separate certificate files (with .pem file extension) for the
private key, the public key, and the certificate authority (or a series of certifying
authorities). In addition to the requirement that the private key be password-protected
PKSC #5/#8 format, Node Manager combines these components of the certificate into
a single certificate file (with a
.crt file extension).
Note: Although the components of the user SSL identity are combined in a single
file, the private key information is not transmitted between servers.
The three components are simply concatenated into a single file with a
.crt extension.
For example:
cat demokey_new democert.pem ca.pem > demo.crt