Building the Java Web Archive (WAR)

Changes to default locations of the GAS installation affect the Java™ servlet, which can be reconfigured by building a new Java Web archive using the fglgar tool.

You will only need to perform the tasks described here if one or all of following changes have been made to the default GAS installation:
For example, the following step describes how to generate a Web archive for the Java Servlet and dispatcher with the following GAS configuration:
  1. Rename the defaultJava servlet deployment file (default FGLASDIR/war/WebContent/WEB-INF/web.xml) to, for example, web.old
  2. Create a copy of the default backup deployment file (default FGLASDIR/war/WebContent/WEB-INF/web.bak) to web.xml
    CAUTION:
    Do not delete, rename, or make any modifications to web.bak. It may only be used to make a copy.
  3. Execute the fglgar command in the FGLASDIR/war/WebContent directory replacing your options for the settings for the GAS installation (--asdir) and configuration (--asxcf) for those shown in the example:
    fglgar --war --asdir C:\usr\gas\3.00 --asxcf C:\conf\as.xcf --output java-j2eedispatch
    Note: The name of the archive must match the servlet name set in the deployment file, web.xml. For example, if the servlet is called java-j2eedispatch, generate a Web archive called java-j2eedispatch.war. The fglgar tool does this automatically for you.
    A Web archive, e.g. java-j2eedispatch.war, is created.
When you have completed building the Web archive in the above step, your next task is to deploy the new Java Servlet. This is detailed in Deploying on a Java Web Server.