Configuring an application server

Configuring an application server creates user and server information in the user registry as well as creates local configuration and keystore files.

Security Access Manager uses a self-generated and self-signed certificate to authenticate its Secure Sockets Layer (SSL) communications. The Security Access Manager authorization API Java classes must be able to determine the certificate that Security Access Manager is using to establish its SSL communication.

You also must establish an identity for the Java application. The SvrSslCfg class is used to create a Security Access Manager user account for an application server and to store the server configuration and certificate information in local configuration and keystore files.

After obtaining the necessary information, use the SvrSslCfg option -action config to create the Security Access Manager application name, the configuration file, and the keystore file.

When using -action config, you must also specify whether you are creating or replacing the configuration and keystore files. The -cfg_action create option is used to initially create the configuration and keystore files. Use cfg_action replace if these files already exist. If the -cfg_action create option is used and the configuration or keystore files already exist, an exception is thrown.

Security Access Manager supports application servers in either remote mode or local mode. The following section shows a sample configuration command for each mode.