Change to IS-INSTALL-DIR/ bin
Copy the Access Manager IS-INSTALL-DIR /bin/amsamplesilent file.
cp amsamplesilent amsamplesilent.uwc
Edit the copy of amsamplesilent created in the previous step.
Set the parameters to correspond to the deployment details.
If you are deploying Access Manager SDK in a web container, such as Sun Java System Web Server or Sun Java System Application Server, set the DEPLOY_LEVEL to value 4, that is, select the option “SDK only with container config.”
Set AM_ENC_PWD to the value of the password encryption key used during the installation of Access Manager.
The encryption key is stored in the parameter am.encryption.pwd under:
Set NEW_INSTANCE to true.
If you are deploying Access Manager SDK in Sun Java System Web Server, set WEB_CONTAINER to WS6.
If you are deploying Access Manager SDK in Sun Java System Application Server, set the WEB_CONTAINER to AS7 or AS8.
For a more detailed description on the other parameters in the amsamplesilent file and to help you configure the Access Manager Remote SDK parameters refer to Chapter 1, Identity Server 2004Q2 Configuration Scripts, in the Sun Java System Identity Server Administration Guide
Configure Access Manager SDK in the web container.
Make sure directory server that is used by Access Manager is running.
Start the web container instance in which the Access Manager SDK will be deployed.
Change directory to IS-INSTALL-DIR/ bin.
Run the following command:
./amconfig -s amsamplesilent.uwc
Restart the web container instance for configurations to take effect.
Access Manager and Communications Express deployed in the different web container instances in SSL and non-SSL mode will now use the Access Manager’s Single Sign-On mechanism for obtaining valid user sessions.
Refer to Tuning Communications Express, for instructions on enabling or disabling Access Manager after deploying Communications Express.