Is This Content Helpful?
We're glad to know this article was helpful.
Instructions provided are for the installation and configuration of IIS 6 with Tomcat 6.0.13 using J2SE Development Kit 5.0 Update 13 for ArcIMS 9.3 on Windows.
Specific information for the installation of ArcIMS is included with the product's Install Guide.
This installation requires the following:
Note: The following steps also apply for configuring IIS with Tomcat on a Windows 2003 64-bit operating system. However, there are additional steps needed for configuring IIS with Tomcat on Windows 2003 64-bit machines. See the according notes in step 5.
Warning: If a path to an older SDK version is listed, cancel the Tomcat installation. Make sure that a Java SDK is installed and the environment variables JAVA_HOME and PATH do not include any old entries regarding the Java Runtime Environment or are pointing to the J2SDK location correctly.K. Click Install to continue. Click Finish.
Note: Verify that old references to JAVA_HOME in the path variable have been removed; for example, <drive:>\jdk1.3.1 or similar.
Important: If using a 64-bit machine, create a folder 'win64' instead.E. Copy the isapi_redirect.dll from the location where it was originally extracted, to the newly created win32 folder; for example C:\Program Files\Apache Software Foundation\Tomcat 6.0\bin\win32.
Note: Important: If using a 64-bit machine, copy the file isapi_redirect_1.2.27_amd64bit.dll in the folder 'win64' and rename it to isapi_redirect.dll. Replace any paths referencing the /win32 directory with /win64 in the steps below.CONFIGURE PROPERTIES FILES:
Code: <!-- The mapping for the invoker servlet --> <!-- <servlet-mapping> <servlet-name>invoker</servlet-name> <url-pattern>/servlet/*</url-pattern> </servlet-mapping> -->
Code: <!-- The mapping for the invoker servlet --> <servlet-mapping> <servlet-name>invoker</servlet-name> <url-pattern>/servlet/*</url-pattern> </servlet-mapping>
Code: <!-- <servlet> <servlet-name>invoker</servlet-name> <servlet-class> org.apache.catalina.servlets.InvokerServlet </servlet-class> <init-param> <param-name>debug</param-name> <param-value>0</param-value> </init-param> <load-on-startup>2</load-on-startup> </servlet> --> -->
Code: <servlet> <servlet-name>invoker</servlet-name> <servlet-class> org.apache.catalina.servlets.InvokerServlet </servlet-class> <init-param> <param-name>debug</param-name> <param-value>0</param-value> </init-param> <load-on-startup>2</load-on-startup> </servlet>J. Save and close the file.
Code: <!-- The contents of this file will be loaded for each web application --> <Context privileged="true">
Warning: The instructions below include making changes to essential parts of your operating system. It is recommended that you backup your operating system and files, including the registry, before proceeding. Consult with a qualified computer systems professional, if necessary. Esri cannot guarantee results from incorrect modifications while following these instructions; therefore, use caution and proceed at your own risk.
Note: The registry file is configured for Tomcat 6.0.13 installed to the default location C:\Program Files\Apache Software Foundation\Tomcat 6.0. If the installation is in a custom location, open the according file in Notepad, and make the appropriate changes to reflect the current environment.
Warning: If ArcGIS Server is installed on the same machine as ArcIMS then IIS is being run in 32 bit mode. For this it is necessary to adjust the second line in the registry file to read: [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Apache Software Foundation\Jakarta Isapi Redirector\1.0] then save the file.
Note: If a 'Jakarta' virtual directory already exists in IIS, it is possible to delete it and re-create it as follows.
Note: If there is already a 'Jakarta' Web Service Extension listed, it is possible to delete and re-create it as follows.U. In the Internet Information Servers Manager click on 'Web Service Extensions' on the left.
Code: http://<your_machine_name>/examples/servlets/servlet/HelloWorldExampleA page that says 'Hello World' displays if the test is successful.
Warning: If this test fails, check the URL carefully for case or spelling issues. Retrace the installation steps. The URL may work if 'http://<hostname>:8080/...' is specified. This only indicates that the Tomcat Web server is working on port 8080; the required redirect to IIS is failing.C. Return to the IIS Management Console > Default Web Site > Properties. Check the ISAPI Filters tab. Verify that there is a green, upward arrow next to the Jakarta filter.
Note: This only applies to IIS 6; IIS 7 does not have a way to check if the ISAPI filter is working.
Warning: If there is not a green arrow next to the Jakarta filter, stop and re-start the IIS Admin Service, including the WWW Publishing Service, from the Services panel. If that does not work, open a browser, and type 'http://localhost' to re-initialize IIS. If the Jakarta filter still fails, do not proceed further. Go back and verify the settings created in the previous steps.D. Return to the IIS Management Console > Default Web Site > Jakarta. Verify that the Jakarta virtual directory is pointing to the correct location on the hard drive, the location of the isapi_redirect.dll.
Note: There are several options to authorize ArcIMS for use. See the Installation Guide, step 3b for more information. The following steps are for one common option:
Note: If a registration code for this product has not been received, contact Customer Service or an International Distributor.
Note: On Windows XP/2003 machines, Internet Explorer sometimes does not show the host name and port number. If this is the case, right-click near the top of the window, under the address bar, and select 'Allow Blocked Content'.C. Test both components.
Note: If these tests are successful, the ArcIMS Application Server and ArcIMS Servlet Connector are configured correctly. If an error message is received, select the error number from the drop-down list and click View. The error number and a description displays. Follow the instructions in the description to fix the problem and run the Diagnostics tool again.