Because Access Manager SDK was installed using the Configure Later option, you need to configure Access Manager SDK by modifying Access Manager configuration files. The standard approach for making these modifications is to run the amconfig command with an input file.
Change to the directory that contains the amconfig input file template, amsamplesilent.
# cd /opt/SUNWam/bin
Copy the template to a new file.
# cp amsamplesilent amconfigps2
In a text editor, edit the amconfigps2 file to set the Access Manager SDK configuration parameters.
Locate the configuration parameters that are listed in the following table, and change their values to the values shown in the table.
Parameter |
Value |
---|---|
DEPLOY_LEVEL |
4 |
SERVER_Name |
am |
SERVER_HOST |
am.pstest.com |
SERVER_PORT |
80 |
ADMIN_PORT |
4849 |
DS_HOST |
ds.pstest.com |
DS_DIRMGRPASSWD |
directory-manager-password |
ROOT_SUFFIX |
"dc=pstest,dc=com" |
ADMINPASSWD |
access-manager-admin-password |
AMLDAPUSERPASSWD |
access-manager-LDAP-password |
COOKIE_DOMAIN |
pstest.com |
AM_ENC_PWD |
password-enc-key |
NEW_OWNER |
root |
NEW_GROUP |
other |
PAM_SERVICE_NAME |
other |
AS81_INSTANCE |
pscluster |
AS81_INSTANCE_DIR |
/var/opt/SUNWappserver/nodeagents/na-ps2/as-cluster-inst-ps2 |
AS81DOCS_DIR |
/var/opt/SUNWappserver/nodeagents/na-ps2/as-cluster-inst-ps2/docroot |
Run the amconfig command with the input file you modified in Step 3.
# /opt/SUNWam/bin/amconfig -s amconfigps2
The output should show failures after checking if Application Server is already configured with Access Manager. These errors are expected because the Access Manager configuration was already added to the Application Server cluster configuration when Access Manager SDK was installed and configured on ps1.
Verify that the Access Manager SDK is properly configured.
# /opt/SUNWam/bin/amadmin —u amadmin —m http://am.pstest.com:80
When prompted, type the access-manager-admin-password.
The output should show current session information.