ArcIMS 9.3.1
The following summarizes changes to ArcIMS 9.3.1.
See also What's new in previous versions of ArcIMS, including ArcIMS 9.3, for a history of what's new in ArcIMS in earlier versions.
- Added support for 64-bit Linux Platforms.
- Added support for Red Hat 5.
- For a list of supported platforms, servlet engines, and Web servers, see the ArcIMS System Requirements.
- In ArcXML, the attribute scalebarunitlabel has been added to SCALEBAR
ArcIMS 9.3
The following summarizes changes to ArcIMS 9.3.
- ArcIMS ships with JRE 1.5.0 Update 13.
- For a list of supported platforms, servlet engines, and Web servers, see the ArcIMS System Requirements.
- PostgreSQL is a supported database for ArcSDE data.
- Support has been added for Internet Protocol Version 6 (IPv6).
- Unicode support for ArcSDE and shapefiles was added.
- For updates to ArcXML for this release, see What's New in ArcXML
- Support has been added for Informix and PostgreSQL enterprise databases. Support has also been added for SQL Server Express Edition with Advanced Services workgroup database.
- Support was added for the WMS 1.3.0 specification.
- ArcSDE databases in unicode can be accessed by ArcIMS.
ArcIMS 9.2
ArcIMS 9.2 is a major release with new functionality. The following is a summary of these changes.
ArcIMS introduces a Web Manager for creating Web applications. The Web Manager provides step-by-step instructions that guide you through the application building process.
- First, you are prompted for which services you want to access. You can select not only Image and ArcMap Image Services, but also ArcGIS Server services, ArcWeb services, and WMS services. You can add more than one service, and the Web application will automatically merge the services for you.
- Second, you can select what functionality you want to add to the application such as finding addresses or searching for features. You can also add map elements such as a table of contents or overview map.
The output is a Web Mapping Application that can be deployed immediately. The Web Mapping Application uses current technology such as AJAX, and includes seamless panning, scroll-wheel zoom, keyboard navigation, and a fully functional table of contents with swatches, among other new features.
The Web Manager comes in two versions:
- ArcIMS 9.2 Web Manager for the Microsoft .NET Framework
- ArcIMS 9.2 Web Manager for the Java Platform
ArcIMS includes a Web Application Developer Framework (Web ADF). Like Web Manager, the Web ADF is available for the Microsoft .NET Framework and for the Java Platform.
When using the Web ADF, you can work with Image and ArcMap Image Services, ArcGIS Server services, ArcWeb services, and WMS services. The same Web ADF can be used with both ArcIMS and ArcGIS Server.
As a developer, you have access to a full set of mapping-related Web controls and an API that wraps ArcXML functionality. Since the Web Mapping Application is built using these components, you can take the output from Web Manager into an Integrated Development Environment (IDE) and modify the output. You can also use the Web controls and build your own application from scratch.
The Web ADF includes comprehensive online support via the ESRI Developer Network (EDN), including Getting Started guides, detailed API discussions, Scenarios and Samples, and Library References.
Web ADF for the Microsoft .NET Framework
The .NET 2.0 framework is required. Visual Studio 2005 or Visual Studio Web Express Edition must be installed to work with the Web controls and templates.
The Web ADF also includes a .NET ArcIMS API, which replaces the .NET Link. The API has an object model that comprehensively wraps all ArcXML functionality. The exception at ArcIMS 9.2 is that Metadata elements are not part of the API.
Web ADF for the Java Platform
The Web ADF for the Java Platform uses Java Server Faces (JSF), which provides the framework for the Web controls and tasks. The Web ADF uses the Java Connector for communication with ArcIMS services. While developers can use any IDE that supports JSF, the recommended IDE's are Eclipse or Sun Studio Creator.
For those who use Metadata Services, a new, ready-to-use Metadata Explorer application based on the Web ADF for the Java Platform is provided for accessing Metadata Services.
| Documentation and online help |
|---|
- ArcIMS documentation is accessible from one location and has been enhanced with new content and better organization. On Windows, the documentation is accessible from the Start menu. The list includes the ArcIMS Help, Errors and Warnings, ArcXML Programmer's Reference Guide, Metadata Services, WMS Connector, WFS Connector, and customizing guides.
- An overview section has been added that provides steps for creating a successful ArcIMS site.
- Checklists have been added that focus on best practices for optimizing ArcIMS services and administering your site.
- The Web ADF's have documentation installed when the respective ADF is installed. This documentation is separate from the main ArcIMS documentation.
The Spatial Server has been updated to improve performance and stability. The following enhancements have been made.
- Image and ArcMap Image Services will not include geometry by default in the response to a GET_FEATURES request if the output mode is binary. With this change, ArcMap cannot be used to download vector data served in ArcIMS without the knowledge of the service provider. ArcIMS administrators have the option to allow geometry when the output mode is xml or newxml, to allow geometry for all cases, or to disallow geometry for all cases. For more information, see Restricting geometry in responses.
- The Spatial Server will stop processing a request if the Application Server times out. This should make Spatial Server instances available more quickly for new requests. For more information on timeouts, see Setting timeouts.
- Support for projections has been upgraded.
- Many projections that did not work at all or worked incorrectly are supported.
- More datum transformations are supported.
- If a service uses a datum transformation, the datum transformation will be honored, even if the request does not include any datum transformation information.
- The following improvements have been made for data support.
- To support faster service creation time of very large ArcSDE Raster catalogs, a server parameter has been added to disallow preloading the entire catalog into a cache. The initial service creation time is less and raster rows are loaded by demand when that portion of image is first requested. For more details, see Setting connection parameters for ArcSDE.
- Support was added for using attribute indices with shapefiles. This improves performance of queries using IN and OR.
- Querying shapefiles with mixed case field names is supported.
- Query responses return geometry of polygon features containing a hole correctly.
- On Solaris platforms, the 256 file handle restriction has been removed.
- Additional font directory locations for the Spatial Server can be specified. This allows the Spatial Server to automatically locate ESRI fonts, system fonts, and other fonts in a specified directory. For more information, see Locating and pointing to font directories.
- Spatial Server log files have been updated.
- ArcMap Image Services support the following ArcMap functionality:
- Reading File Geodatabases
- Maplex labeling
- Representations
- ArcMap Image Services have the following improvements:
- Domain descriptions, Subtype descriptions, and field aliases set in the ArcMap document or geodatabase are returned in query responses. The GET_FEATURES request must included outputmode="newxml".
- Definition queries are supported in requests. Layers containing the results of a definition query can be dynamically rendered using SIMPLERENDERER.
- Annotation, multipatch, and group layers are identified when requesting service information.
When using Extract Server, if there are no layers to extract in a request, an error message is returned instead of returning an empty zip file.
Support has been added for new geocoding styles: World Cities with Country, US Cities with State and US Streets with City, State and Zip. For more information, see Adding geocode parameters to the geocode extension
- Direct connect is supported in Author for accessing ArcSDE layers. For more information, see Adding ArcSDE data.
- Metadata Explorer has been updated to use the Web ADF for the Java Platform. Existing JSP-based Metadata Explorer applications will continue to work with ArcIMS 9.2, but the Metadata Explorer and Advanced Metadata Explorer sample included in ArcIMS 9.1 are no longer available in the product.
- In the Metadata Service configuration file, you can set the following attributes:
- A DBTUNE keyword to use when the Metadata Service tables are created in the database.
- A toggle to store metadata documents uncompressed in the database.
- A custom XPath index definition file.
- Search results can be ordered by the date when the metadata documents were published or updated, either from newest to oldest or oldest to newest.
- New metadata services have a unique constraint placed on the DocUUID column in the Metadata Service business table and its associated deleted table. This eliminates the possibility of duplicate records.
- Contents of the feature class associated with a Metadata Service can be previewed, but not copied or pasted, in ArcCatalog.
- The CSW Connector has the following new features:
- It is easier to extend the connector to support alternative CSW profiles.
- The connector has a new Web administration page, similar to the WMS and WFS Connectors.
- Support has been added for two CSW profiles: OpenGIS® Catalogue Services Specification 2.0 - ISO1915/ISO19119 Application Profile for CSW 2.0 and OGC Catalogue Services - ebRIM (ISO/TS 15000-3) profile of CSW
.
- New RDBMS support for Metadata Services includes SQL Server 2005 and SQL Express with Advanced Services with either Enterprise ArcSDE or Workgroup ArcSDE.
- The following changes have been made to the gazetteer:
- Data to support a Gazetteer Metadata Services is provided on a separate disk with the ArcIMS product. The data can be accessed directly from the disk or copied locally.
- A world gazetteer is provided as well as U.S.-only subest of the gazetteer places.
- ArcSDE export files containing pre-loaded Gazetteer Metadata Services continue to be provided along with shapefiles containing the source gazetteer data.
- Scripts for loading the ArcSDE export files have been improved; they continue to be provided with the ArcIMS install.
- The WMS Connector has OGC Styled Layer Descriptor (SLD) support. SLD uses a Styled Layer Descriptor XML file to define symbolization of a map. The XML file must follow the SLD schema as defined in the OGC Styled Layer Description Implementation Specification. You can use your own XML file or reference an XML file at a different location. The file reference must be included in the WMS GetMap request URL or as an embedded XML fragment. For more information, see Styled Layer Descriptor support.
- Requests to WMS-enabled services will honor the datum transformation parameters set in the service.
- A problem with messages about invalid SRS values in GetMap requests has been resolved.
- The WFS Connector has OGC Filter encoding support. With Filter support, you can describe a set of features on which to operate. The OGC Filter is defined in the "OGC Filter Encoding Implementation Specification".
- The following are some highlights for ArcXML.
- Support has been added for requesting acetate objects such as a scale bar in a separate image.
- The scale dependency set for a layer or label can be requested as a relative scale rather than units per pixel.
- For Image Services, the relative scale of the map can be requested along with the image.
- For a complete list of updates to ArcXML, see What's New in ArcXML 1.1 for ArcIMS 9.2
| Internationalization/localization |
|---|
- For the Metadata Explorer, locales that use a comma for a decimal delimiter will function correctly for searches.
- ArcXML builder for metadata requests can be localized like the other map ArcXML builders.
- The layer name can be internationalized in the Active X Connector.
- Able to render TIFF images using a comma as the decimal in the world file on non-English locales.
- Additional font directory locations for the Spatial Server can be specified. This allows the Spatial Server to automatically locate ESRI fonts, system fonts, and other fonts in a specified directory.
- The WFS Connector has been internationalized.
| Platform, Web server, and servlet engine support |
|---|
- ArcIMS 9.2 ships with J2SE Runtime Environment 5.0 Update 6 on Windows, Solaris, and Linux, J2SE Runtime Environment 5.0 Update 3 on HP-UX, and J2SE Runtime Environment 5.0 on AIX.
- For a complete list of supported platforms, Web servers, and servlet engines for ArcIMS 9.2, see the System Requirements.
As ArcIMS adds new features and functionality, older components are marked for deprecation. Deprecation means that a particular feature is completely supported but may be removed in a future release. Features are not normally removed from ArcIMS unless there is a new feature to replace it.
Features deprecated in ArcIMS 9.2
The following features are marked as deprecated in ArcIMS 9.2. They continue to be fully supported; however, they may be removed in a future release:
- ArcSDE connection administration in the Service Administrator (Not the entire Service Administrator)
- Java Viewer API for use with the Java Custom Viewer. Note: The Java Custom Viewer itself is not being deprecated.
- ActiveX Connector
Features removed from ArcIMS 9.2
- Browser-based ArcIMS Manager available in ArcIMS 3.x, 9.0, and 9.1. You will need to use Author, Designer, and Administrator. For remote management, the Service Administrator is available. This Manager should not be confused with the ArcIMS Web Manager, which is a new feature.
- Metadata Explorer and the Advanced Metadata Explorer sample are no longer available from the setup. They have been replaced with a new Metadata Explorer that takes advantage of features in the Web ADF for the Java Platform.
- The ArcXML elements AVIMSWORKSPACE, MOIMSWORKSPACE, GET_USER, and PUT_USER.
- World and cities shapefiles from the sample data.
ArcIMS 9.1
- ArcIMS 9.1 ships with J2SE Run Time Environment (JRE) 1.4.2_06.
- Duplicate sample data has been removed from the sample directory.
- For a list of supported platforms, servlet engines, and Web servers, see the ArcIMS System Requirements.
- A connectionCheckInterval parameter was added in aimssdeio.cfg. For Image and Feature services that use ArcSDE data, this parameter defines the time interval between attempts to reconnect to ArcSDE when the SDE server becomes unavailable.
- Querying dynamic layers is supported.
- ArcIMS Image Server supports the JPEG 2000 image format on Windows and Solaris, and MrSid Generation 3 on Windows, Solaris and Linux.
- Decimal degree calculations for scale dependencies are fixed.
- The identify envelope calculation is fixed.
- WMS Administrator provides a warning message for custom projections.
- Oracle 10g application server is supported.
- Deployment is similar to WMS Connector.
- Supports WFS 1.0 specification.
- Supports GML 2.1.2 and GML 3 Level 0.
- The CSW Connector provided with this release supports searching a Metadata Service using the OpenGIS® Catalogue Services Specification v2.0. This connector translates CSW queries into searches the Metadata Service can understand, then translates the Metadata Service's response into the appropriate CSW format.
- The OAI-PMH client and the OAI-PMH Connector can now be installed when installing ArcIMS and are partially configured by the post installation setup.
- Changes in database schema and text indexing were made in both ArcIMS Metadata Services and ArcSDE XML columns for improved search performance.
- Metadata search has more constrained rules.
- To search a 9.1 Metadata Service, you must use the 9.1 version of clients. These include: ArcGIS Desktop, Metadata Explorer, and the Portal Toolkit.
| Internationalization and Localization |
|---|
- The correct Japanese characters are now returned in UNICODE.
- The WMS Connector Administrator supports localization and an option to set the Charset property.
ArcIMS 9.0
- 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 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 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 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. The .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.
- The Java Connector has some new samples and some changes to the object model and tag library.
- 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.
- 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) 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.
| Error and warning messages |
|---|
- You can dynamically start and stop full logging without having to restart the ArcIMS Monitor, Tasker, and Application Server.
- 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.
- The default monitor port property - defaultMonitorPort - was removed from AppServer.properties. This property stored the port on which Monitor registers itself. Because ArcIMS does not use this information, the property was removed.
- ArcIMS Tasker can log to file using debug and logToFile attributes in Tasker.properties.
- ArcIMS Tasker removes ArcMap Server generated files from your local user directory.
- The attribute spatialServer.ForbiddenImageTypes has been added to Esrimap_prop. 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.
- The following attributes have been added to the WMSEsrimap_prop property file: errorLog, wms_capabilities_100, wms_capabilities_110, wms_capabilities_111, wms_featureinfo, and availableServices.
| Spatial Server configuration file changes |
|---|
- In 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.
- In aimsserver.cfg, 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.
- In aimsms.cfg, the parameters pngcompression and interlacedgif have been added as new image output parameters. In addition, the parameter imagefeaturelimit allows you to set the maximum number of features that can be displayed in a map on a per-layer basis.
- In 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.
- In 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.
- In aimses.cfg, the parameter sizelimit allows you to set the maximum size of a .zip file.
- In aimssdeio.cfg, the parameter countmode allows you to set the method that ArcSDE counts records. In 4.0.1 and earlier versions, the default was "server" mode. In ArcIMS 9.0, the default is "client" mode. It is recommended that you use "client" mode.
| ArcSDE and direct connect support |
|---|
- 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.
| Supported platforms, Web servers, and servlet engines |
|---|
- 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.
- For a list of supported platforms, servlet engines, and Web servers, see System Requirements for ArcIMS.
