To Generate an Access Manager WAR File on the Access Manager 1 Host Machine

1. As a root user, log in to the AccessManager–1 host machine.

2. Create a directory into which the Access Manager WAR file can be downloaded and change into it.

   # mkdir /export/AM71 # cd /export/AM71

3. Download the Access Manager 7.1 WAR file from http://www.sun.com/download/products.xml?id=460d5c8e.

4. Unzip the Access Manager download.

   # unzip AccessManager7_1RTM.zip # ls -al total 228716 drwxr-xr-x 6 root root 512 Jul 11 20:00 . drwxr-xr-x 5 root sys 512 Jul 19 10:30 .. -rw-r--r-- 1 root root 117008919 Jul 10 15:00 AccessManager7_1RTM.zip drwxr-xr-x 4 root root 512 Jun 25 20:16 applications drwxr-xr-x 2 root root 1536 Jun 25 20:16 legal -rw-r--r-- 1 root root 3018 Jun 25 20:16 README drwxr-xr-x 2 root root 512 Jun 25 20:16 samples -r--r--r-- 1 root root 11934 Jun 25 20:16 Software_License_Agt_SLA.txt drwxr-xr-x 2 root root 512 Jun 25 20:16 tools

5. Switch to the non-root user.

   # su am71adm

6. Create a staging area in which the WAR will be exploded.

   # cd /export/am71adm # mkdir am-staging

   ---

   Tip –

   In the staging area, after exploding the WAR, you can modify the WAR contents to suit your needs, generate a new WAR, and deploy it on any number of remote host computers. Whenever you need to make changes to the WAR, you maintain the changes in this one staging area, and redeploy the modified WAR as many times as you want, on as many host machines as you need.

   ---

7. Explode the WAR file.

   # cd am-staging # jar xvf /export/AM71/applications/jdk15/amserver.war

8. Add the following context parameter to the web.xml file.

   By default, during the WAR deployment, Access Manager creates a bootstrap file in the user's home directory. The bootstrap file points to the directory where all the Access Manager configurations will be created. By specifying this new context parameter, Access Manager will create the bootstrap file in the directory you specify; in this case, /export/am71adm/bootstrap. web.xml is located in /export/am71adm/am-staging/WEB-INF/.

   <context-param> <param-name>com.sun.identity.bootClassPath</param-name> <param-value>/export/am71adm/bootstrap</param-value> </context-param>

9. Regenerate the Access Manager WAR file.

   # cd /export/am71adm/am-staging # jar cvf ../amserver.war *

   A new WAR file is created, including the modified web.xml.

10. Verify that the new WAR file was created in the proper location and with the appropriate permissions.

    # cd /export/am71adm # ls -al total 62262 drwxr-xr-x 6 am71adm staff 512 Jul 19 11:46 . drwxr-xr-x 5 root sys 512 Jul 19 10:30 .. -rw-r--r-- 1 am71adm staff 144 Jul 19 10:30 .profile drwx------ 3 am71adm staff 512 Jul 19 10:40 .sunw -rw-r--r-- 1 am71adm staff 566 Jul 19 11:06 .wadmtruststore drwxr-xr-x 16 am71adm staff 512 Jul 19 10:47 am-staging -rw-r--r-- 1 am71adm staff 31834862 Jul 19 10:56 amserver.war -rw-r--r-- 1 am71adm staff 136 Jul 19 10:30 local.cshrc -rw-r--r-- 1 am71adm staff 157 Jul 19 10:30 local.login -rw-r--r-- 1 am71adm staff 174 Jul 19 10:30 local.profile

    ---

    Note –

    The amserver.war file is owned by am71adm.

    ---