Creating a Keystore Connection Profile

Create a keystore connection profile to supply the runtime connection information for a keystore.

1. In Enterprise Explorer, right-click the server type or enterprise resource for which you want to create a connection profile and select New.
2. Enter a name and description for the connection profile, and click Next.

   Table 1. Create Connection Profile page

   Field	Description
   Name	Enter a unique and descriptive name for the connection profile.
   Description	(Optional) Enter a profile description that helps you distinguish it from others.
   Auto-Connect at Startup	(Optional) Connect automatically to the server and display its contents in Enterprise Explorer when Sybase WorkSpace starts.

3. Configure keystore properties, and then click Next. You can select the Sybase implementation of a Merlin keystore. Alternatively, if you have a custom implementation, you can configure these properties accordingly.

   Field	Description
   Keystore Drivers	Select the driver for your Business Activity Monitor Server, or click [...] to define a new driver. The Driver Definitions dialog opens. For example, if you want to use the default Sybase implementation of a driver that is built with the Apache-Merlin open source crypto engine, select WS-Security Merlin Implementation Default.
   Keystore File	Browse for the keystore file that contains valid certificates. For example, you can use an outbound keystore file that works with the default Sybase keystore implementation. You can find this file in the following location: <installation directory>\DevRuntimes\EAServer\bin\sc_security\outbound\uosecurity.keystore
   Keystore Password	Enter the password required to unlock and give access the contents of the keystore file. For example, if you are using the Sybase implementation with the installed keystore files, then type changeit as the password. Note: You can might discover the password required, by opening the property file (for example, an inbound keystore) in a text browser and looking for the password propety value.
   Keystore Type	Choose the format of your flat keystore file. For an unencrypted Java keystore file, choose JKS. For an encrypted JCE keystore file, choose JCEKS. JCEKS is the format used by the Sybase default keystore.

4. Click Test Connection to ping the server and to verify that the connection profile is working.
5. Click Finish to create the connection profile.

   The connection profile displays under the appropriate category in the Enterprise Explorer.

Send your feedback on this help topic to Sybase Technical Publications: pubs@sybase.com

Your comments will be sent to the technical publications staff at Sybase, Inc. For product-related issues or technical support, contact Sybase Technical Support at 1-800-8SYBASE.