Sun Java System Access Manager 7.1 Postinstallation Guide

Deploying an Access Manager 7.1 WAR File in Sun Java System Web Server 7

Before you deploy the Access Manager WAR file, Web Server 7 must be installed and running on the host server.

ProcedureTo Deploy the Access Manager WAR File in Web Server 7

  1. Login as (or become) superuser (root).

  2. Copy the amserver.war file to the host server where you want to deploy Access Manager.

    To get the amserver.war file, see Getting an Access Manager 7.1 War File.

    For example, copy the WAR file to the /opt/SUNWam/amwar_staging directory.

  3. Backup the server.policy file and then add the Java security permissions to the file, as shown in Adding Access Manager Permissions to the Server Policy File.

  4. Restart the Web Server instance for the new entries to take effect.

  5. Deploy the Access Manager amserver.war file using the Web Server Admin Console or CLI command:

    • For example, the following Web Server 7 wadm command deploys the WAR file on Solaris systems:

      cd /opt/SUNWwbsvr7/bin
      ./wadm add-webapp --user=admin --host=${SERVER_HOST}
      --port=${WS_ADMIN_PORT} --config=${WS_CONFIG} 
      ./wadm deploy-config --user admin --host=${SERVER_HOST}
      --port=${WS_ADMIN_PORT} --restart=true ${WS_CONFIG}

      Enter the Web Server administration password when you are prompted.

      For more information about the wadm command, see Chapter 9, Deploying Web Applications, in Sun Java System Web Server 7.0 Developer’s Guide to Java Web Applications.

  6. Depending on your platform, add the following JavaHelp JAR file (jhall.jar) to the classpath so the Access Manager Console online help is accessible:

    • Solaris systems: /usr/jdk/packages/

    • Linux systems: /usr/java/packages/

  7. Continue with Configuring Access Manager 7.1 Using the Configurator.