English

How To: Configure Oracle Application Server 9.0.2 with Oracle HTTP Server for ArcIMS 4.0.1

Summary

After installing ArcIMS, configure the Web server for ArcIMS. If the Web server and servlet engine are not operational, contact a system administrator before proceeding. See www.oracle.com for information on problems with Oracle Application Server (OAS).

Procedure

Follow the steps below to configure the Web server for ArcIMS.

  1. Open the Oracle Enterprise Manager in a Web browser (http://mymachine.esri.com:1810).
  2. Click the OC4J_home link from the list of System Components.
  3. On the OC4J_home page click the Deploy War file link under the Applications section to open the Deploy Web Application page.
  4. For Web Application, click Browse and navigate to <ArcIMS Installation Directory>/Middleware/servlet_connector/arcimsservletconnector.war.
  5. For Application Name type 'servlet'.
  6. For Map to URL type '/servlet'.
  7. Click Deploy to deploy the arcimsservletconnector.war file. The ArcIMS servlet connector is installed in the <Oracle Application Server Installation Directory>/j2ee/home/applications directory.
  8. Click OK when the Confirmation is displayed.
  9. Navigate to the <Oracle Application Server Installation Directory>/j2ee/home/applications/servlet/servlet/WEB-INF/classes directory.
  10. Open the Esrimap_prop file in a text editor.
  11. Change the value of appServerMachine to the name of the Application Server computer. For example:

    Code:
    appServerMachine=<server name>.esri.com

  12. Save and close the file.
  13. Click the HTTP Server link from the list of System Components.
  14. Under the Administration section click the Advanced Server Properties link.
  15. In the Advanced Server Properties page, click the httpd.conf link under Configuration Files to edit the httpd.conf file.

    Note:
    If the contents of the httpd.conf file are not in the text edit window that is displayed in the browser, do not edit the httpd.conf file. Manually edit the httpd.conf file in the <Oracle Application Server Installation Directory>/Apache/Apache/conf directory in a text editor. Before manually editing the httpd.conf file, stop Oracle Application Server (OC4J_home and HTTPServer) and the Oracle Enterprise Manager. Once the edits are completed, restart Oracle Application Server and the Oracle Enterprise Manager.

  16. In the Alias section, add the following for Web site and server output:

    Code:
    Alias /output/ "<Path to output directory>/output/"
    <Directory "<Path to output directory>/output/">
    Options Indexes MultiViews
    AllowOverride None
    Order allow,deny
    Allow from all
    </Directory>
    Alias /website/ "<Path to website directory>/website/"
    <Directory "<Path to website directory>/website/">
    Options Indexes MultiViews
    AllowOverride None
    Order allow,deny
    Allow from all
    </Directory>

  17. For the Web pages designed in ArcIMS to start automatically, verify the DirectoryIndex line includes default.htm. For example:

    Code:
    DirectoryIndex index.html default.htm

  18. Click Apply to save changes.
  19. Click Yes to restart the HTTP server.
  20. To provide Web users with the ArcIMS files that are necessary to view the Java Web pages, copy the /install directory from the ArcIMS installation directory to the Web site directory. For example:

    Code:
    cp -r <ArcIMS Installation Directory>/ArcIMS/ViewerDownLoad/install <Path to website directory>

  21. Open <ArcIMS Installation Directory>/ArcIMS/Xenv/ArcIMS_Diagnostics/ArcIMS_Diagnostics.html in Netscape. The ArcIMS Diagnostics tool displays.
  22. Select the Web server protocol, type the Web server name including domain, and type your port number. The default is 80.
  23. Click 1 to test the ArcIMS Servlet Connector. If this test is successful, the ArcIMS Servlet Connector is configured correctly. If an error message occurs, select the error number in the dropdown list and click View. The error number and a description display. Follow the instructions in the description to fix the problem and try the Diagnostics tool again.

Related Information