ArcIMS 9.0 must be registered before it can be used. The end result of the registration process is an authorization file that is used to enable the software for use. If you are an existing ArcIMS user and using ArcMap Server, your 4.x keycode will not work with 9.0. To register in the United States, go to http://service.esri.com/. If you are not in the United States, please call your local distributor to register your software. If the Internet is not an option, you can contact ESRI Customer Service or your local distributor to register and receive your 9.0 authorization file.
Changes have been made to increase performance in the Spatial Server. The time needed to start a service using ArcSDE vector and raster data as well as ArcView image catalogs has improved. In addition, general overall performace improvements in image generation have been made resulting in faster requests.
ArcIMS now supports a multiple Monitor configuration on the same machine, which allows you to use a high-availability configuration that includes more than one ArcIMS Application Server. In addition, you can now permanently delete orphaned monitors that are no longer part of the site configuration.
On Windows, dependencies on the Microsoft Java Virtual Machine (JVM) were removed.
The way you obtain a GIF keycode has changed. The technology for GIF compression is patented by Unisys Corporation. Because of this, support for this format in ArcIMS is locked, and Unisys Corporation requires that you obtain an additional license or waiver from them to use this format for Web use until all Unisys GIF/LZW patents expire. The US patent expired on June 20, 2003, however, corresponding foreign patents remain in force and expire as follows:
Until all patents expire, you must obtain a keycode from ESRI that unlocks GIF/LZW capabilities in ArcIMS after contacting Unisys. After July 7, 2004, contact ESRI or your local ESRI Distributor directly to obtain a keycode (contacting Unisys is no longer required after that date).
The ArcIMS components of Manager, EditNotes, and MapNotes, have been deprecated in ArcIMS 9.0. They are fully supported for ArcIMS 9.0 but are subject to being removed in a future release.
The ArcIMS .NET Link is a new developer tool to facilitate the development of ArcIMS applications on the .NET platform. It consists of classes and functions used to build connections to an ArcIMS Application Server through either HTTP or TCP connections. Once you have established a connection with an ArcIMS Application Server, you can send ArcXML requests and receive ArcXML responses. While other ArcIMS connectors have an extensive API which creates ArcXML requests and parses responses for you, .NET Link requires that you build mechanisms for creating and parsing ArcXML within your application.
The ActiveX Connector has some new samples, a tutorial, and some changes to the object model. For more details, see Customizing ArcIMS--Using the ActiveX Connector.
The Java Connector has some new samples and some changes to the object model and tag library. For more details, see Customizing ArcIMS--Using the Java Connector.
The WMS Connector has been upgraded to be compliant with the OGC WMS 1.1.1 specification.
Support for ArcMap Server on UNIX (Sun Solaris) has been added.
ArcMap Server is based on ArcGIS Engine 9.0.
GIF is a supported image output format.
For ArcMap Server on Windows, ArcIMS Tasker now removes files from your local user directory.
Improved for better scalability and performance.
Support is available for SQL Server, DB2, and Oracle. Informix is not supported for ArcIMS 9.0 Metadata Services.
The OAI-PMH Connector (Open Archives Initiative Protocol for Metadata Harvesting) is a new connector that allows OAI-PMH metadata harvesting clients to access documents in an ArcIMS Metadata Service. An OAI-PMH client is also provided that can harvest from any OAI-PMH metadata provider and publish to an ArcIMS Metadata Service.
ArcSDE 9.0 is required for ArcIMS 9.0 Metadata Services. Sites using ArcIMS 4.0.1 must be upgraded to ArcSDE 9.0. Utilities are provided to help in the upgrade process.
You can dynamically start and stop full logging without having to restart the ArcIMS Monitor, Tasker, and Application Server services or daemons.
Notification, warning, and error messages generated by the Spatial Server, ArcIMS Application Server, ArcIMS Monitor, ArcIMS Tasker, and Administrator have been improved and documented in the ArcIMS Help.
A new message level has been added to the Spatial Server for logging all errors and warnings.
Application Server - AppServer.properties
The default monitor port property - defaultMonitorPort - was removed from the AppServer.properties file. This property stored the port on which Monitor registers itself. Because ArcIMS does not use this information, the property was removed.
Tasker - Tasker.properties
ArcIMS Tasker can now log to file. See the debug and logToFile attributes in Tasker.properties.
ArcIMS Tasker now removes ArcMap Server generated files from your local user directory. For more information, see the taskFile property description in the Tasker section.
Servlet Connector - Esrimap_prop
The attribute spatialServer.ForbiddenImageTypes has been added. This property determines which output formats are forbidden when the OUTPUT type attribute is used in a GET_IMAGE request. This replaces spatialServer.AllowOutputTypeChange used in ArcIMS 4.0.1.
WMS Connector - WMSEsrimap_prop
The following attributes have been added to the property file.
aimsserver.cfg
The attributes logmaxsize and savefiles have been added. These settings allow you to set a maximum limit on log file size. When this limit is reached, you can choose to start a new log file or overwrite the existing one.
The logging level values have changed for the attribute logfiles. Logging levels are 0 (no messages written to log files) through 4 (full verbose logging). The default logging level is now "2", which means all errors and warnings are logged.
Image Server - aimsms.cfg
The parameters pngcompression and interlacedgif have been added as new image output parameters.
The parameter imagefeaturelimit allows you to set the maximum number of features that can be displayed in a map on a per-layer basis.
ArcMap Server - aimsamsrv.cfg
The parameter ConnectionCheckInterval allows you to set the maximum time interval that the Spatial Server checks for valid ArcSDE connections for ArcMap Image Services.
Query and Feature Server - aimsqs.cfg and aimsfs.cfg
The parameter featurelimit allows you to set the maximum number of features that can be returned in a query for Image and Feature Services.
Extract Server - aimses.cfg
The parameter sizelimit allows you to set the maximum size of a .zip file.
aimssdeio.cfg
The parameter countmode allows you to set the method that ArcSDE counts records. In 4.0.1, the default was "server" mode. In ArcIMS 9.0, the default is "client" mode. It is recommended that you use "client" mode.
ArcIMS 9.0 is an ArcSDE 9.0 client application and works with ArcSDE 9.0 and earlier versions. However, ArcIMS 4.0.1 and earlier are not supported with ArcSDE 9.0. For compatibility issues, see the Product Compatibility Matrix.
ArcSDE's direct connect configuration now has support for the IBM DB2 and IBM Informix databases in addition to Oracle and SQL Server. The direct connect configuration provides additional options for scaling your system and lets client applications connect directly to a database without using the ArcSDE application server. In this configuration, the ArcSDE client and server functionality run on the same machine as the client applicationthere is no separate ArcSDE server process running anywhere. For more information on the direct connect configuration, see the Understanding ArcSDE and Making a Direct Connection guides.
All machines hosting a Spatial Server require an ESRI authorization file. Authorization is performed in the ArcIMS post installation setup. The ESRI license manager used with ArcMap Server in ArcIMS 4.0 and 4.0.1 is no longer required.
ArcIMS uses supported versions of a system Java Runtime Environment (JRE) 1.3.1 or higher. If a supported version of JRE 1.3.1 or higher is not detected on your machine, JRE 1.4.2 is installed (1.4.1 for AIX). However, the ArcIMS Manager applications (Author, Designer, Administrator) always use a private version of JRE 1.4.2 (AIX 1.4.1). For more information on JRE support, see the ArcIMS Installation Guide for your platform.
On UNIX and Linux, setups can now be run using a wizard-based GUI or using console mode. For more information, see the ArcIMS Installation Guide for your platform.
For a list of supported platforms, servlet engines, and Web servers, see System Requirements for ArcIMS.
Information for getting started is provided in the hardcopy book, Getting Started with ArcIMS. This book replaces Using ArcIMS from previous releases.
For information on additions and modifcations to ArcXML, see the ArcXML Programmer's Reference Guide.
ArcIMS guides on connectors, customizing viewers, and other support documents are provided on the ESRI Software Documentation Library CD. The Getting Started with ArcIMS book provides instructions for copying these files to the /ArcIMS/Documentation directory so that links from this help system to those guides are active.
The following changes have been made to ArcXML 1.1 since the release of ArcIMS 4.0.1. For more information, see the ArcXML Programmer's Reference Guide.
New elements and attributes:
Changes to element and child element relationships
The following elements have updated attributes.
Deprecated metadata elements and attributes
The following metadata elements and attributes are no longer valid with Metadata Services. They have been removed from the documentation. However, for backward compatibility, the Spatial Server will process these elements and attributes. However, you will likely receive an incorrect or empty response.
Other deprecated elements
The following elements associated with EditNotes have been deprecated. These elements are fully supported for ArcIMS 9.0 but may be removed in a future release of ArcIMS.