To Deploy an Access Manager 7.1 WAR File in WebSphere Application Server

1. On the host server where you want to deploy Access Manager, create a staging directory for the WAR file.

   For example, on a Solaris system: /opt/SUNWam/amwar_staging

2. Copy the amserver.war file to the staging area.

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

3. Modify the server.xml file as follows:

   1. Add the following JVM entries to allow Access Manager to function:

      genericJvmArguments="-Djava.awt.headless=true 
      -DamCryptoDescriptor.provider=IBMJCE -DamKeyGenDescriptor.provider=IBMJCE"/>

   2. If you are using SSL, add the following properties and JVM entry:

      </cacheGroups>
      </services>
      <properties xmi:id="Property_1120370477732" name="amCryptoDescriptor.provider" 
      value="IBMJCE" required="false"/>
      <properties xmi:id="Property_1120370511939" name="amKeyGenDescriptor.provider" 
      value="IBMJCE" required="false"/>

      genericJvmArguments="-Djava.awt.headless=true 
      -Djava.protocol.handler.pkgs=com.ibm.net.ssl.internal.www.protocol 
      -DamCryptoDescriptor.provider=IBMJCE -DamKeyGenDescriptor.provider=IBMJCE"/>

4. 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.

5. Restart the WebSphere instance for the new entries to take effect.

6. Deploy the amserver.war file using either the WebSphere Application Server Admin Console or the CLI.

7. 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/javax.help-2.0/lib/jhall.jar

   • Linux systems: /usr/java/packages/javax.help-2.0/javahelp/lib/jhall.jar

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