On the computer system where the load balancing IBM HTTP
Server is installed, export the public signer certificate from the
key database using the iKeyman graphical interface.
About this task
Alternatively, you can use the gskcmd command-line
interface to complete this task. For detailed information on using
the gskcmd command-line interface, see
"Managing keys with the gskcmd command line interface
(Distributed systems)" in
the
WebSphere Application Server Information Center.
Procedure
- On the computer system where the load balancing IBM HTTP
Server is installed, export the public signer certificate from the
key database using the iKeyman graphical interface.
- Click Key Database File from
the main UI, then click Open.
- Specify the location of the CMS key database
file plugin-key.kdb that is specified in the
HTTP server plugin-cfg.xml file.
By
default the file is plugin-key.kdb.
When using
HTTP server V8.5, the following default locations apply:
C:\Program
Files\IBM\WebSphere\Plugins_1\config\webserver1

/opt/IBM/Websphere/Plugins/config/webserver1
- Provide the password for the key database
and click OK. The default password is WebAS.
- From the Key database content drop
down list, select Signer Certificates.
- Select the trusted root certificate used to sign the IBM
HTTP server SSL certificate.
Tip: If you are
not sure which signer certificate is the trusted root certificate,
select a certificate and click View / Edit.
In the Key information dialog window, check
if the Set the certificate as trusted root option is
selected.
- Click Extract.
- In the Extract Certificate to a File dialog
box, set the following fields:
- Data type: Base64-encoded ASCII data.
- Certificate file name: Accept the default
of cert.arm or specify a different name.
- Location: Type the drive and directory
where you want to store the file or use Browse to
select a drive and directory.
- Click OK to export the public signer
certificate to the file name and directory specified above.