This procedure assumes you have just completed To Generate an Access Manager WAR File on the Access Manager 1 Host Machine.
On the AccessManager-1 host machine, start the Web Server administration server.
# cd /opt/SUNWwbsvr/admin-server/bin # ./startserv |
Change to the non-root user am71adm.
# cd /opt/SUNWwbsvr/bin # su am71adm |
Start the Web Server AccessManager-1 instance.
# cd /opt/SUNWwbsvr/https-AccessManager-1.example.com/bin # ./startserv |
Run wadm add-webapp to add the Access Manager WAR file to the Web Server.
# ./wadm add-webapp --user=admin --host=AccessManager-1.example.com --port=8989 --config=AccessManager-1.example.com --vs=AccessManager-1.example.com --uri=/amserver /export/am71adm/amserver.war Please enter admin-user-password> web4dmin ... Do you trust the above certificate? [yes/no] yes CLI201 Command 'add-webapp' ran successfully. |
Run wadm deploy-config to deploy the Access Manager WAR file.
# ./wadm deploy-config --user=admin --host=AccessManager-1.example.com --port=8989 AccessManager-1.example.com Please enter admin-user-password> web4dmin CLI201 Command 'deploy-config' ran successfully. |
To verify that the Access Manager WAR file was successfully deployed, list the contents of the Web Server instance directory.
# cd /opt/SUNWwbsvr/https-AccessManager-1.example.com/ web-app/AccessManager-1.example.com # ls -al total 6 drwxr-xr-x 3 am71adm staff 512 Jul 19 11:08 . drwxr-xr-x 3 am71adm staff 512 Jul 19 11:08 .. drwxr-xr-x 16 am71adm staff 512 Jul 19 11:09 amserver |
amserver exists in the directory and is owned by the non-root user am71adm.
Restart the Web Server instance.
# cd /opt/SUNWwbsvr/https-AccessManager-1.example.com/bin # ./stopserv; ./startserv |
Log out of the AccessManager–1 host machine.