To Deploy the Access Manager WAR File as Access Manager 2

Before You Begin

This procedure assumes you have just completed To Copy the Access Manager WAR File to Access Manager 2.

1. On the AccessManager-2 host machine, start the Web Server administration server.

   # cd /opt/SUNWwbsvr/admin-server/bin # ./startserv

2. Change to the non-root user am71adm.

   # cd /opt/SUNWwbsvr/bin # su am71adm

3. Start the Web Server AccessManager-2 instance.

   # cd /opt/SUNWwbsvr/https-AccessManager-2.example.com/bin # ./startserv

4. Run wadm add-webapp to add the Access Manager WAR file to the Web Server container.

   # ./wadm add-webapp --user=admin --host=AccessManager-2.example.com --port=8989 --config=AccessManager-2.example.com --vs=AccessManager-2.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.

5. Run wadm deploy-config to deploy the Access Manager WAR file.

   # ./wadm deploy-config --user=admin --host=AccessManager-2.example.com --port=8989 AccessManager-2.example.com Please enter admin-user-password> web4dmin CLI201 Command 'deploy-config' ran successfully.

6. 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-2.example.com/ web-app/AccessManager-2.example.com # ls -al total 6 drwxr-xr-x 3 am71adm staff 512 Jul 19 12:07 . drwxr-xr-x 3 am71adm staff 512 Jul 19 12:07 .. drwxr-xr-x 16 am71adm staff 512 Jul 19 12:07 amserver

   amserver exists in the directory and is owned by the non-root user am71adm.

7. Restart the Web Server instance.

   # cd /opt/SUNWwbsvr/https-AccessManager-2.example.com/bin # ./stopserv; ./startserv

8. Log out of the AccessManager–2 host machine.