Why and when to perform this task
A key locator typically locates a key store in the file system. The location of key stores can vary from machine to machine so it is often helpful to configure a default key locator for a specific machine and reference it from within the encryption or signing information. This information is found within the binding configurations of any application installed on the machine. This suggestion enables you to define a single key locator for all applications that need to use the same keys. In a Network Deployment environment, you also can specify the default binding information at the cell level.
This task provides instructions on how to configure server and cell-level key locators for a specific application using the WebSphere Application Server administrative console. You can configure binding information in the administrative console, but for extensions, you must use the Application Server Toolkit.
WebSphere Application Server has the following default key locator class implementations:
This field is optional is the key locator does not use a keystore.
This field is optional is the key locator does not use a keystore. Use ${USER_INSTALL_ROOT} as this path expands to the WebSphere Application Server path on your machine.
This field is optional is the key locator does not use a keystore. Use the JKS option if you are not using Java Cryptography Extensions (JCE) and use JCEKS if you are using JCE.
WebSphere Application Server has the following default key locator class implementations:
This field is optional is the key locator does not use a keystore.
This field is optional is the key locator does not use a keystore. Use ${USER_INSTALL_ROOT} as this path expands to the WebSphere Application Server path on your machine.
This field is optional is the key locator does not use a keystore. Use the JKS option if you are not using Java Cryptography Extensions (JCE) and use JCEKS if you are using JCE.