Once the keys and keystores have been created, you must configure the server to use these keystores.
1. Start the ALSB/WLS server from the domain directory (for example, run .startWebLogic.sh).
2. From a browser, run the WebLogic Admin Console (for example, http://localhost:7001/console) and configure WebLogic Server to use the new certificate trust keystore rather than the default demo trust keystore, by selecting the Keystores tab for the server and entering the keystore settings. Note: WebLogic Server doesn't allow the demo identity store to still be used by the server, therefore, the new identity store is also specified in this example even though it will not be used directly by the service bus or application server for Web service message-level security. The screenshots in Figure 2 show example settings (passphrase is "weblogic"):
3. Using the WebLogic Admin Console, for the default security realm (myrealm), choose to add a new Provider and then choose to add a new Credential Provider by selecting the New button shown in Figure 3:
Set the name to be WSPKICredentialMapper, for example, and ensure the type is set to PKICredentialMapper, as Figure 4 shows:
Once saved, choose to edit the provider-specific settings to specify the custom identity keystore as the keystore for this credential mapper, as Figure 5 shows. Note: In this example, the passphrase is "weblogic."
4. Once the changes are saved and activated, restart the WebLogic Server to enable the new keystore settings to be used.
Note: Strictly speaking, a PKI credential mapper does not need to be specified if ALSB/WebLogic Server does not have to sign or encrypt Web service responses (as in this example). However, these additional steps are included to enable Web service response signing/encryption capabilities to be easily accommodated at a later date.