How To: Install IBM HTTP Server 6 and WebSphere 6 using Java 1.4.2_06 for ArcIMS 9.1 Windows 2003


Instructions provided are for the installation and configuration of IBM HTTP Server 6.0 with WebSphere 6.0 using J2SDK 1.4.2_06 for ArcIMS 9.1 on Windows.

Specific information for the installation of ArcIMS is included with the product's Install Guide.

WebSphere possesses its own native servlet engine and does not require other third-party servlet engines.
This installation will require the following software:
· Java 2 SDK, v.1.4.2_06
· IBM HTTP Server 6.0
· WebSphere 6.0 Application Server
· ArcIMS 9.1 Installation CD

A user account that has administrator rights on the ArcIMS machine is required.

· Familiarity with certain Windows tasks is required to install and configure ArcIMS. For details, see Common Windows tasks when installing ArcIMS.

· For more information on the acronyms and terms used in this document, see the Glossary of terms used in ArcIMS Installation articles.

· Review and follow steps 1 and 2 from the ArcIMS Installation Guide on the DVD. These two steps ensure that the system meets the minimum requirements and assist in planning the ArcIMS site configuration. To open the ArcIMS Installation Guide, launch the DVD menu and click 'ArcIMS Installation Guide'.


ArcIMS 3.1, 4.0, 4.0.1 or 9.0 must be uninstalled to install ArcIMS 9.1. The setup program for ArcIMS 9.1 on Windows will prompt for the removal of previously installed versions.

If ArcIMS components were distributed among several computers, it is recommended the uninstall program be manually run on each computer.

A supported Web server and Servlet Engine must be properly installed and configured before running the setup program for ArcIMS 9.1.
  1. Uninstall any unsupported versions of JDK/JRE, Webserver, and Servlet Engine. See: How To: Uninstall ArcIMS-related third-party software on Windows
    1. Install Java 2 SDK, v. 1.4.2_06.
      A. Click J2SDK 1.4.2_06 to download Sun Java 2 SDK, Standard Edition, version 1.4.2_06.
      B. Click 'Download J2SDK'.
      C. Accept the license agreement.
      D. Click on the download link for the Windows Offline Installation Multi-Language. The file j2sdk-1_4_2_06-windows-i586-p.exe is downloaded.
      E. Run the program after it has finished downloading.
      F. Accept all of the default installation options, unless changes are required.
    • Install WebSphere 6.0.
      A. Insert the installation CD or double click on launchpad.bat.
      B. Click on “Launch the installation wizard for WebSphere Application Server”.
      C. At the “Welcome” screen, click Next.
      D. At the “License” screen, choose “I Accept” and click Next.
      E. At the “System Prerequisites Check” screen, click Next.
      F. At the “Installation Directory” screen, keep the default and click Next.
      G. At the “Choose Install Type” screen, choose “Custom Installation” and click Next.
      H. At the "Product installation" screen, click Next.
      I. At the ports screen, click Next.
      J. At the "Node and host names" screen, click Next.
      K. At the "Windows service definition" screen, keep the defaults and click Next.
      L. At the “Installation Summary” screen, click Next.
      M. At the "Installation complete" screen, make sure Launch the First steps console is checked and click Finish.
      N. First Steps should come up. Click on Installation verification.
      O. When you see "Installation Verification is complete" close the First steps output window.
      P. Click on “Stop the server “, close the First Steps output window, then click Exit to exit First steps.
      Q. Close the Launchpad window if it's still open.
    • Install IBM HTTP Server 6.0.
      A. At Launchpad select Launch the installation wizard for IBM HTTP Server.
      B. At the “Welcome” screen, click Next.
      C. At the “License” screen, choose “I accept” and click Next.
      D. At the “Installation Directory” screen, keep the default location and click Next.
      E. At the “Setup Type” screen, choose “Custom” and click Next.
      F. At the "Product installation" screen, click Next.
      G. At the ports screen, click Next.
      H. At the "Windows service definition" screen, make sure the "Run ... as a Windows Service" check boxes are checked, select "Log On as local system account", and click Next. (Note: the Startup Type should remain “Automatic”).
      I. At the “Summary” screen, click Next.
      J. When the installer is finished, click Next.
      K. Ensure the box is checked to launch the Plugin-Install and click Finish.
    • Install the Web server plug-ins.
      A. At the "Welcome" screen, uncheck the boxes and click Next.
      B. At the “License” screen, choose “I Accept” and click Next.
      C. At the “System Prerequisite” screen, click Next.
      D. At the “Select Web Server” screen, choose “IBM HTTP Server V6” and click Next.
      E. At the “Select Installation Scenario” screen, choose “WebSphere Application Server machine (local)” and click Next.
      F. At the “Web server plugins installation location” screen, keep the default location and click Next.
      G. At the "Installation location of WebSphere Application Server V6" screen, keep the default location and click Next.
      H. At the “Web Server configuration” screen, browse to IBM HTTP Server’s httpd.conf file and click Next. This file is located at: <IBM HTTP Server Install Location>/conf.
      I. At the “Specify Web Server Definition name” screen, leave as “webserver1” and click Next.
      J. At the “Web Server plugin-cfg.xml file” screen, click Next. (Write down the location of the plugin-cfg.xml file! You will need this information later.)
      K. At the “Detection” screen, click Next.
      L. At the “Summary” screen, click Next.
      M. At the “Details” screen, click Next.
      N. If the “Web server plug in installation roadmap” appears, close it.
      O. At the “Summary Info” screen, click Finish.
    • Test the WebSphere 6.0 Installation.
      A. Start IBM WebSphere Application Server V6 - <machine>Node01
      B. Start IBM HTTP Server 6.0
      C. http://localhost:9080/snoop - This should return all your info.
      D. http://<machine name>/snoop - This should also return all your info.
    • Install ArcIMS 9.1 from the installation CD.
    • Configure WebSphere 6.0 with ArcIMS 9.1.
      Deploy ArcIMS servlet connector through the WebSphere Admin console

      A. http://localhost:9060/ibm/console/
      B. Login as admin
      C. In the left panel, expand Applications.
      D. In the left panel, click on “Install New Application”
      E. In the right panel, browse to <ArcIMS install location>\Connectors\Servlet\arcimsservletconnector.war
      F. For “Context Root” type: /servlet and click Next.
      G. At the “Generate Bindings” screen, click Next.
      H. At the “Application Security Warnings” screen, click Continue.
      I. At the “Install New Application” screen, click Next.
      J. At the “Map modules to servers” screen, check the box and click Next.
      K. At the “Map virtual hosts for Web modules” screen, check the box and click Next.
      L. At the “Summary” screen, click Finish.
      M. In the right panel, click on the “Save to Master Configuration” link.
      N. In the right panel, click Save.
      O. In the left panel, click on Enterprise Applications. You should see aimsservletconnector.war in the list of Enterprise Applications and there should be a red X in the status column.

      Edit the Esrimap_prop file.

      A. Navigate to <WebSphere Install Location>\AppServer\profiles\default\installedApps\<servername>Node01Cell\arcimsservletconnector_war.ear\arcimsservletconnector.war\WEB-INF\classes and edit the Esrimap_prop file.
      B. Change appserverMachine to your machine name.
      C. Save the file and close your editor.
      D. Start the servlet connector.
      E. Return to the WebSphere Admin console and log in if necessary.
      F. In the left panel, expand Applications then click on “Enterprise Applications”.
      G. In the right panel, check the box next to arcimsservletconnector_war and click start. You should see a green arrow in the status column.
      H. Close WebSphere’s Admin console.
      I. By default, when a web application is deployed through WebSphere’s administrative console, plugin-cfg.xml gets modified automatically. If a web application appears to be deployed but still isn’t working, if may be because that file didn’t get updated correctly. To update plugin-cfg.xml manually:
      J. Refer to step 10 under the Installing Plugin section of these instructions for the location of plugin-cfg.xml (hopefully you wrote it down!)
      K. Navigate to plugin-cfg.xml & open it in a text editor.
      L. Make sure the following line(s) is/are in the plugin-cfg.xml file:
      <Uri Name="/<webappname>/*"/>
      M. Repeat steps 2, 4, and 5 for each web application that you want to deploy. (Note: the Uri Name(s) should be the name(s) of the web application(s) that is/are being deployed.)
      N. Edit IBM HTTP Server’s httpd.conf file.
      O. Add the following in the appropriate section of httpd.conf file located at: <IBM HTTP Server Install Location>/conf
      Alias /output "<path to output dir>"
      Alias /website "<path to website dir>"
      <Directory "path to website dir">
      Options Indexes MultiViews
      AllowOverride None
      Order allow,deny
      Allow from all

      P. Scroll to the DirectoryIndex section and add default.htm to this line.
      DirectoryIndex index.html default.htm
      Q. Restart IBM HTTP Server.

    • To configure ArcIMS 9.1, run the ArcIMS Post Installation. Refer to the ArcIMS 9.1 Installation Guide, Step 3B. When you get to the Web Server-Servlet Engine section of the Post Install, select “I will manually configure my Web server / Servlet engine”.
    • Verify that the ArcIMS installation was successful.
      A. Navigate to Start > Programs > ArcGIS > ArcIMS > ArcIMS Diagnostics.
      B. Verify the Web server protocol and Web server name are correct, including the domain and port number. The default is port 80.
      On Windows XP/2003 machines, Internet Explorer sometimes does not show the hostname and port number. If this is the case, right-click near the top of the window and select 'Allow Blocked Content'.
      C. Test both components. The result for Test 1 should be:

      IMS v9.1.0
      Test successful

      The result for Test 2 should be:

      Test successful
      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 dropdown list and click View. The error number and a description displays. Follow the instructions in the description to fix the problem and then try the Diagnostics tool again.