An ArcIMS site can consist of one or more computers, depending upon the needs of your site. It is therefore advisable to plan your ArcIMS site configuration before installing ArcIMS. This section includes an overview, and some common site configuration scenarios to help get you started on planning your ArcIMS site configuration.
The ArcIMS architecture and functionality has been engineered specifically to serve geographic data and services on the Internet. The software is designed so that it is easy to create maps, develop Web pages that communicate with the maps, and administer the ArcIMS site. The software is also designed for distribution across a network and for scalability as the demand for maps increase.
An ArcIMS site consists of one or more computers where the ArcIMS host (ArcIMS Manager (includes Manager, Manager Applications and Service Administrator), Application Server Connectors and ArcIMS Application Server), ArcIMS Spatial Servers and data reside. The Application Server Connectors, ArcIMS Application Server, and ArcIMS Spatial Server are the components needed to create and manage services that process requests and responses. The ArcIMS framework also requires a Web server, Java Runtime Environment (J2SE JRE), and servlet engine. For more information on these components see the Overview topic of the Install Guide Introduction.
The ArcIMS site management applications (Manager, Author, Designer and Administrator, and Service Administrator), provide access to ArcIMS components for authoring maps, administering ArcIMS services and Spatial Servers, and designing Web sites. If you want to use the Web based Manager, it is strongly recommended that Manager be installed on your Web server machine. The Manager Applications (Author, Designer and Administrator) can be used on any machine. A Manager installation will install Manager, Manager Applications (Author, Designer and Administrator) and Service Administrator.
There are many possible ArcIMS site configurations. Some sites run all ArcIMS components on a single computer while other sites are comprised of multiple computers. Configurations will vary depending on the available computer resources and the mapping services provided. For ArcIMS Spatial Servers, processing speed and the ability to handle the load are important. Will the ArcIMS Services perform process-intensive functions or create basic map displays? How many services will be created at one time? Will the Web server computer be dedicated to the Web site or used for other purposes as well? Answers to these types of questions will assist in planning an ArcIMS site configuration.
Configure an ArcIMS site based on the anticipated number of simultaneous users visiting the site and the number of maps generated each day. For example, a Web site with very few anticipated users, averaging 100 to 1,000 maps per day, could run from one computer. A high volume Web site, with 100,000 to 1,000,000 maps per day, should be distributed to multiple ArcIMS Spatial Servers.
When planning your ArcIMS site configuration, there are some installation recommendations to take into account. The installation configuration diagram above illustrates ArcIMS installation features and some of the installation recommendations.
The ArcIMS features in the installation configuration diagram, illustrated in the same color, should be installed on the same machine.
The Application Server Connectors must be installed on your Web server machine.
Metadata Explorer must be installed on your Web server machine.
To use Manager (the Web-based application used to author, design and administer), it is recommended that Manager be installed on your Web server machine.
The ArcIMS Servlet Connector should only be installed on the Web server machine.
The Manager Applications (Author, Designer and Administrator) can be installed on any machine. To install these applications, perform a Manager installation. A Manager installation will install Manager and Author, Designer and Administrator, and Service Administrator.
Spatial Server can be installed on one machine or many machines. Each Spatial Server installation needs to know the name of the machine where the Application Server is installed. The post installation will prompt you for the name of the Application Server and edit the monitor.properties file accordingly. One Spatial Server can not support multiple Application Servers, but one Application Server can support multiple Spatial Servers. An ArcGIS Authorization File is required to install ArcIMS Spatial Server.
Application Server can be installed on one machine or many machines. Each Application Server installation needs to know the name of the Web server. The post installation will prompt you for the name of the Web Server and edit the site preferences and diagnostics property files.
ArcMap Server is an extension of Spatial Server. You can not install ArcMap Server without installing Spatial Server. An ArcGIS Authorization File is required to install ArcMap Server. ArcMap Server is only available on Windows and Solaris platforms.
ArcSDE Services Monitor can exist on any machine where ArcSDE is installed.
There are three background processes (Windows services or UNIX/Linux daemons) associated with ArcIMS:
ArcIMS Application Server 9.0. The Application Server service is installed with the ArcIMS Application Server.
ArcIMS Monitor 9.0. The Monitor service is installed with Spatial Server and ArcSDE Services Monitor.
ArcIMS Tasker 9.0. The Tasker service is installed with the ArcIMS Application Server.
This section presents a series of common configuration scenarios that illustrate how to distribute various installation components across various computer platforms.
Multiple ArcIMS Spatial Servers
The ArcIMS site must have a Web server configured and communicating with a servlet engine before installing ArcIMS.
The entire ArcIMS site on one machine is referred to as a typical installation. This installation consists of the ArcIMS host (ArcIMS Manager, Application Server Connectors and ArcIMS Application Server) and ArcIMS Spatial Server installed on the Web server machine. A typical installation of ArcIMS will install Manager, the ArcIMS Application Server, the default ArcIMS Application Server Connector (the Servlet Connector), and the ArcIMS Spatial Server. Additionally, a typical ArcIMS installation will install Metadata Explorer, and some selected samples and documentation.
This site configuration is useful for those with limited resources or light server loads. If you are new to ArcIMS, start with this site configuration.
See Performing a typical installation for steps on installing these ArcIMS components on the same computer. To include ArcMap Server, leave all installation features checked, and in-addition check the box to install ArcMap Server.
Additional ArcIMS Spatial Servers can be added to the ArcIMS site configuration, as the number of requests increases, if redundancy needs to be built in or to optimize performance.
There is no one formula for determining how many ArcIMS Spatial Servers are needed. The Spatial Server configuration will vary among ArcIMS sites depending on the number and size of services, time required to process requests, number of requests, Web and network traffic, and other factors specific to the site.
Since it is possible to have multiple ArcIMS Spatial Servers on multiple machines, a mechanism is needed to manage these Spatial Servers and the services running on them. ArcIMS uses a Virtual Server concept to manage services on multiple ArcIMS Spatial Servers. See the ArcIMS technical paper, ArcIMS 4 Architecture and Functionality, located on http://support.esri.com and the ArcIMS Help for more information on managing Spatial Servers and Virtual Servers.
Spatial Servers can be distributed across an ArcIMS site in several ways as illustrated below.
This configuration illustrates two ArcIMS Spatial Server on the same machine.
To set up your machine with more than one ArcIMS Spatial Server on the same machine, see the topic Installing additional ArcIMS Monitors. For the additional ArcIMS Spatial Server (Monitor service/background process) running on the same machine, an additional ArcIMS Application Server is required. For more information on additional ArcIMS Spatial Servers on the same machine, see the ArcIMS Help, and the ArcIMS High-Availability Site Configuration whitepaper, available in PDF from the ESRI Support Site.
This configuration illustrates two ArcIMS Spatial Servers on multiple machines.
To install multiple ArcIMS Spatial Servers on additional machines, see the topic Installing multiple ArcIMS Spatial Servers on additional computers.
Your site may require your Web server to be on one machine while the ArcIMS components reside on a different machine. In this configuration, the Application Server Connectors must reside on the same machine as the Web server.
If your Application Server is on a different machine than your Application Server Connector, some additional configuration of the Application Server Connector is required. If you are using the Servlet Connector, the Web server-servlet engine configuration available in the post installation will automatically edit your Esrimap_prop file with the Application Server name you provide. If you are using the ColdFusion Connector see the CustomizingColdFusion.pdf for details on the servername attribute value for any action. For the Java Connector see the CustomizingJavaConnector.pdf for information on the ConnectionProxy object or the tcpConnection.tag.
If you will be using Manager, Service Administrator and/or Metadata Explorer, it is also recommended that Manager, and/or Metadata Explorer be installed on the Web server machine. If you will be using Metadata Explorer and/or Service Administrator, J2SE JDK 1.3.1 or higher is required on this machine. See the topic Verify your system requirements for system requirement information.
The ArcIMS Application Server runs as a background process (Windows service/UNIX/Linux daemon) and handles the load distribution of incoming requests. The Application Server also catalogs which services are running on which ArcIMS Spatial Servers. Using this information, the Application Server dispatches an incoming request to the appropriate Spatial Server.
Installing multiple ArcIMS Application Servers on different machines can improve load distribution of incoming requests and help create redundancy (failover). Installing the ArcIMS Application Server on a different machine to other ArcIMS components is common in a secure network environment where the Web server is located in the DMZ. The DMZ is established by an outside firewall. See the technical articles for ArcIMS located at http://support.esri.com for more information on system design strategies.
For high-volume implementations of ArcIMS, it is possible to have a single Web server communicate with several Application Servers in round-robin or failover configuration. If used for round-robin, the Application Server will rotate requests among the specified Application Servers. If used for failover, the back-up Application Server will serve maps when the primary Application Server machine is inaccessible. To support multiple Application Servers, the Application Server names and ports must be added to the Esrimap_prop file, located in your Web server's servlet directory. If more than one Application server is specified in the Esrimap_prop file, you cannot administer multiple Application Servers with Administrator. To administer multiple Application Servers, you can use the Service Administrator (installed with the Manager installation feature).
Below is an example of a multiple Application Server set up:
Steps to set up this scenario:
Set up a public Web server machine.
This machine will serve the Web sites to users.
Verify you meet system requirements, including that your Web server and servlet engine are running and communicating. For information on setting up your Web server and Servlet Engine visit http://support.esri.com/search/KbDocument.asp?dbid=25867.
IMPORTANT: You will be using Service Administrator to administer the Application Servers. Service Administrator will be installed on this machine by the Manager feature. J2SE SDK is required to use Service Administrator. The document linked above includes instructions on installing J2SE SDK for your Web server and servlet engine configuration.
To verify that your Web server and Servlet Engine are communicating see the topic Verifying your servlet engine.
Run the ArcIMS setup. Choose to install the following (Uncheck all other ArcIMS installation features so that these features will not be installed):
Expand the Application Server Connectors feature, select to install the Servlet Connector only.
Select to install Manager
Follow the installation directions on the screen.
During the post installation setup you will be required to provide the following information:
The location of your Website and Output directories. In this scenario the Website and Output directories will be created on this machine, as this machine will be used to serve the Web sites. Choose the default directory, or change the location and create these directories on a different local drive.
Select to share your Output and Website directories by checking the box on the create Website and Output dialog box. Your Application Server machine will need to be able to access these directories (discussed in detail when setting up Application Server machines).
The location of your Axl directory. In this scenario the Axl directories will be created on this machine, as this machine will be used to serve the Web sites. Choose the default directory, or change the location and create these directories on a different local drive.
The name of your Web server. Enter this machine's Web server host name. By default the host name of this machine will be provided.
The Application Server name and ports. In this scenario you will have two Application Servers, for now enter the machine name where one of these Application Servers will be installed. By default the host name of this machine will be provided, change this to the host name of one of your Application Server machines.
Your Web server and servlet engine information. If you are using a Web server and servlet engine that is automatically configured for you, configuration will be performed by the post installation setup.
At the end of the post installation setup you will be required to stop and restart your Web server to apply configuration changes.
Share the directory containing the data you will be using (if it is local data and not ArcSDE data). Each Spatial Server machine must be able to access the data for map services created. The AXL files must be accessible by the Application Server.
Create Application Server machine 1
This will be the main Application Server machine. This machine will host the ArcIMS Application Server and the ArcIMS Spatial Server. The service Administrator will be used to administer this ArcIMS Application Server. We will also create an identical set up on another machine, which will be the back-up machine for failover.
Verify you meet system requirements.
Install the following ArcIMS features (Uncheck all other ArcIMS installation features so that these features will not be installed):
Application Server
Spatial Server only
Follow the installation directions on the screen.
During the post installation setup you will be required to provide the following information:
The location of your Website and Output directories. In this scenario browse to the Website and Output directories located on your public Web server machine (for example, UNC pathname \\publicwebserver\ArcIMS). Your public Web server machine will be used to serve the Web sites.
The location of your Axl directory. Browse to your public Web server machine (for example, UNC pathname \\publicwebserver\ArcIMS). Your AXL directory will be created by default under C:\ArcIMS on your public Web server machine. All Application Servers accessing the AXL files will share the files at this location.
The name of your Web server. Enter this machine's Web server host name. By default the host name of this machine will be provided.
The Application Server name, and registry and connector ports. Enter this machine name, where this Application Server has been installed. By default the host name of this machine will be provided.
Your system domain, username and password to administer ArcIMS background processes. Enter the domain, username and password of the ArcIMS installation account. This account must have administrator privileges.
Each AXL file references the path to the data used. Verify that the path to the data is accessible by the Spatial Servers that are registered with the Application Servers, on Application Server machine 1 and Application Server machine 2. In general, the path to the data must be valid from the perspective of any Spatial Server. It is recommended that the path used be a UNC pathname.
Create Application Server machine 2
This machine will be identical to Application Server machine 1. If used for round-robin, it will rotate requests among the two Application Servers. If used for failover, it will serve maps when Application Server machine 1 is inaccessible. This machine, like Application Server machine 1, will host ArcIMS Application Server and ArcIMS Spatial Server. Service Administrator will be used to administer the Application Server.
Follow the same steps above to set up Application Server machine 2, as you did to set up Application Server machine
Configure the public Web server machine for multiple Application Servers
Find and open in a text editor the Esrimap_prop file located on your public Web server machine in the Web server servlets directory.
The following lists common default servlet directories for specific Web server and servlet engine combinations on Windows:
Apache with Tomcat: C:\<Tomcat installation directory>\Webapps\Servlet\WEB-INF\classes
Apache with ServletExec: C:\Program Files\New Atlanta\ServletExec AS\se-<instance name>\Servlets
IBM HTTP Server with WebSphere: C:\Websphere\AppServer\installedApps\sampleApp.ear\default_app.war\WEB-INF\classes
Sun Java System 6.0 (formerly Sun ONE) : C:\iplanet\servers\docs\servlet
Microsoft IIS with JRun: C:\Program Files\Allaire\Jrun\servlets
Microsoft IIS with ServletExec: C:\Program Files\New Atlanta\ServletExec ISAPI\Servlets
Microsoft IIS with Tomcat: C:\<Tomcat installation directory>\Webapps\ROOT\WEB-INF\classes
Oracle Application Server: C:\Oracle\iAS\Apache\Jserv\servlets
WebLogic: C:\bea\wlserver70\config\<mydomain>\applications\DefaultWebApp\WEB-INF\classes
Edit the AppServerMachine parameter in the Esrimap_prop file with the names of the Application Servers you installed (The names of Application Server Machine 1 and Application Server Machine 2, for example, appservermachine1,appservermachine2)
Edit the AppServerClientPort parameter in the Esrimap_prop file with the registry port numbers of the Application Servers you installed (for example, 5300,5300).
For round-robin, leave the failover parameter in the Esrimap_prop file set to false.
For failover, set the failover parameter in the Esrimap_prop file to true. This will specify that requests should be sent to the first Application Server machine listed, until it fails to return a response, then requests will be sent to the next Application Server listed.
After editing the Esrimap_prop file, save changes and stop and restart your Web server.
Create your map services for both Application Servers.
The Service Administrator will be used to administer the ArcIMS Application Servers. If you met all system requirements, and you used the post installation setup to configure your Web server, the Service Administrator will have been set up. If you manually configured your Web server you must manually configure your Web server for Service Administrator (see Configure your Web server for Service Administrator).
To access Service Administrator open your browser (on any machine), and type: http://<Web server machine name>/esriadmin
For example: http://publicwebserver/esriadmin
By default the log in page for Application Server 1 will be displayed. The Application Server specified in the esriadmin.properties file determines the default log in page displayed. Provide the user name and password to log in to administer Application Server 1.
To administer Application Server 2, adapt the URL as follows:
http://<Web server machine name>/esriadmin/logincheck.jsp?host=<Application Server Machine 2>&port=<appservermachine2port>
For example: http://publicwebserver/esriadmin/logincheck.jsp?host=appservermachine2&port=5300
For more information on using Service Administrator, see the ArcIMS Help.
Services created on each Application Server should be completely identical. The image below illustrates the parameters used in this scenario to create new services on Application Server machine 1 and Application Server machine 2. The public Web server machine serves the Web sites to the users, so the output files should be stored on this machine. The Server output locations were manually changed to point to the public Web server machine (In this example, "publicwebserver" will be the host name of your public Web server machine). In this example, the Axl file used is also stored on the public Web server machine, the UNC pathname to the Axl file is provided in the File Path field.
Once you have determined your ArcIMS site configuration, see Step 3a: Installing ArcIMS.