Log in as or become superuser (root) on the server where you want to deploy the Access Manager Client SDK.
Get the Java ES installer. For information, see Getting the Java ES Installer.
If not already installed, install the web container that you plan to use for the Client SDK:
Web Server or Application Server: Install the web container using the Java ES installer.
BEA WebLogic Server or IBM WebSphere Application Server: Follow the BEA or IBM documentation. See also Chapter 7, Installing and Configuring Third-Party Web Containers.
If you are not using a web container, skip this step.
Install the Access Manager Client SDK by running the Java ES installer with either the Configure Now or Configure Later option. On the installer Component Selection page, check Client SDK.
If you are using the Configure Now option, see Access Manager Client SDK Configuration Variables for the values that you must specify during installation.
If you are using BEA WebLogic Server or IBM WebSphere Application Server as the web container, you must use the Configure Later option.
If you specified the Configure Later option during the previous step, or if you need to reconfigure the Client SDK, run the amconfig script as follows:
Copy the amsamplesilent file and set the configuration variables in the new file. For example, you might name the new file as ClientSDK_config.
On Windows systems, copy the AMConfigurator.properties file to AMConfigurator-clientsdk.properties.
For the variables that you need to set, see Access Manager Client SDK Configuration Variables.
Run the amconfig script using the new configuration file.
For example, on a Solaris system with Access Manager installed in the default directory:
# cd /opt/SUNWam/bin # ./amconfig -s ./ClientSDK_config
On Windows systems, in the amconfig.bat file, change AMConfigurator.properties to AMConfigurator-clientsdk.properties, and then run the edited amconfig.bat file.
Restart the web container for the Access Manager Client SDK.