Configuring BSSV for SSL and WebSphere and Server Manager

This section describes the additional steps that are required in order for BSSV to work with SSL and WebSphere and the Server Manager for JD Edwards EnterpriseOne.

1. From the WAS Admin Console, extract the signer and personal certificates from the node default trust store and node default key store.

2. Using the ikeyman tool, open the dummy client key file (DummyClientKeyFile.jks) and import the personal signer certificate that you extracted in Step 1 of this procedure.

3. Open the dummy client trust file (DummyClientTrustFile.jks) and import the signer certificate that you extracted in Step 1 of this procedure.

4. Using the ikeyman tool, open the plugin-key.kdb of the HTTP Server that is configured with the WAS Profile hosting the BSSV Server.

5. Import the personal signer and signer certificates extracted in Step 1 of this procedure into the plugin-key.kdb file.

6. Modify the httpd.conf file and change the key store value as shown below:

   keystore=plugin-key.kdb

7. If you want to disable HTTP access and only have HTTPS (SSL) access, you must comment the include file for BSSV that was automatically added by Server Manager. The name of the Server Manage configuration file is scf_xxxx.conf.

8. After completing these steps and restarting HTTP server, the secure https url should be working properly.