Issues Fixed with ArcIMS 9.0 Service Pack 2

ArcMap Server:

• CQ00247468 Font embedding is enabled for PDF layout exports to allow correct display of labels in non-English locales.
• CQ00245350 ArcMap Service should return both projection ID and projection string in a Service Info response when a standard projection is used. Otherwise only projection string will be returned.

Incorporates ArcGIS Engine files modified for ArcGIS 9.0 sp 2.

Application Server:

• CQ00242851 Corrupt request renders all Services in a Virtual Server on an ArcIMS site unavailable.
• CQ00243582 Servlet Connector does not close file connections with a series of geocode requests.

Java Connector:

• CQ00249849 JSP Viewer is unable to show the viewer's legend on Windows XP SP2.
• CQ00245590 Connecting via HTTP always returns "HTTP Return Code" to output console.

Service Administrator:

• CQ00249542 Cannot create map services on Windows XP SP2.

Java Custom and Standard Viewers:

• CQ00249545 Identify results dialog had display problems on Windows XP SP2.

Active X Connector:

• CQ00242405 InitMap method returns False when MapService has an image layer and LoadGeocode is set to True.

.NET Link:

• CQ00237446 TCP connections and non-ASCII characters are now supported in a single .NET Link assembly

Metadata Server:

• CQ00235295 Can't view contents of an ArcIMS metadata server on some UNIX platforms after publishing documents.
• CQ00246379 MDUpgrade and MDAlterIndex fail on AIX.
• CQ00247339 MDImport fails with an extremely large number of documents.

Spatial Server:

• CQ00236164 Keyword UPPER does not work when used in the right side of a WHERE clause in a Spatial Query.
• CQ00241921 For the World Projections Winkel 1, Eckert IV, Eckert V and Eckert VI on-the-fly projection will fail when the extent of requested image is -180,-90,180,90. The projection will work fine when the requested extent is changed to -179.99, -89.99, 179.99 and 89.99.
• CQ00242148 Cannot display some special Hong Kong characters when the data is from ArcSDE.
• CQ00239222 Enable GET_PROJECT request.
• CQ00242096 Add ability to project multiple envelopes in a single GET_PROJECT request.
• CQ00246068 Return an error message to the client if any of the layers specified in the GET_IMAGE request does not exist.
• CQ00247117 Unable to project data from RD_NEW (id = 28992) to GCS_WGS_1984 (id=4326).
• CQ00243149 When using a complex TrueType Marker symbol, the inner symbol is offset and is not placed in the correct location. ArcIMS Author will display this symbol correctly.
• CQ00244341 Geocode server sometimes returns x,y coordinates of 0,0.

Samples and Tutorial Data:

• CQ00234304 International boundary and sovereignty changes made to data for China.

WMS Connector:

The WMS Connector is a Java Web Application that provides an Open GIS Consortium (OGC)-standard Web Map Service (WMS) interface to data served by ArcIMS Image and ArcMap Image Services. The connector receives OGC-standard WMS requests and converts them into ArcXML requests that are forwarded to the published ArcIMS services. The ArcXML responses are translated back into OGC standard responses and are returned to the requesting clients. The supported requests with the WMS Connector are:

• GetCapabilities
• GetMap
• GetFeatureInfo

With the version of the ArcIMS WMS Connector provided in this service pack, we have executed and passed the OGC automated conformance tests. Application for an OGC compliance certificate and license agreement are pending due to changes in OGC procedures.

Be aware that the previous version of the WMS Connector which resided with the servlet connector has not been updated, and this WMS Connector is installed into a different location under the Connectors directory (Windows) or Middleware directory (UNIX/Linux).

The document, WMS Connector for ArcIMS 9.0 SP2, lists what is new in this version of the connector and also lists known limitations.

Post installation instructions are located in the WMS Connector documentation. This documentation can be found here:

• <ArcIMS Installation Directory>/Documentation/wms_connector/wms_reference.htm for Unix/Linux.
• <ArcIMS Installation Directory>\Documentation\wms_connector\wms_connector_doc.zip for Windows.

Issues in the WMS connector that have been addressed are:

• CQ00244390 The WMS connector now has an administration UI. The connector was updated to handle admin requests.
• CQ00234923 When a service is projected, the capabilities file should still include the lat long bounding box coordinates, which are coordinates to WGS84 (SRS:4326).
• CQ00242256 Even when the WMSEsrimap_prop file has enable=false, it is still possible to request capabilities and get an image back for a service by typing in the appropriate URL request.
• CQ00245299 The bounding box for an ArcMap Server service has layout coordinate (0,0,8.5,11) instead of the data view coordinates. Also, it does not have a proper EPSG number for the SRS parameter.
• CQ00245305 Even if none of the ArcIMS layers are "Queryable" (all image layers for instance) the WMS service is still listed as "Queryable" (though the individual layer tags are correct).
• CQ00246463 If COORDSYS tags are not included in the map configuration file:
  
  1. If FEATURE/FILTERCOORDSYS are missing from the PROPERTIES section of a map config file, SERVICEINFO does not return any projection information. We cannot however assume that the service is in decimal degrees. So instead, we should assign an SRS value of EPSG:NONE in the capabilities, assume all latlong bounding boxes are -180, -90, 180, 90, and send a message to the user (via the admin) informing them of the problem and the assumptions that were made.
  2. If a custom projection string was used in the map configuration file, there really is no valid EPSG value. To accommodate this scenario, we need to create latlong bounding boxes as usual for the service and for the layers. Include only EPSG:4326 in the SRS list. After that, send an informational message to the user, via the admin, of what has occurred.
• CQ00248956 The capabilities file shows an inconsistency with the supported SRS's and the extent values/units depicted in the LatLonBoundingBox.
• CQ00248828 A GetFeatureInfo request on non-English locales and/or services with non-English data, either responds with "???" for some field values, or responds with a service exception altogether, "Error sending FeatureInfo response.Exception in FeatureInfo reply invalid byte 1 of 1-byte UTF-8 sequence (0Xa1)".

The following bugs were fixed for the purposes of certifying the WMS Connector against the OGC WMS conformance test suite:

• CQ00243436 Default value of FEATURE_LIMIT in getFeatureInfo request should be one. If no FEATURE_LIMIT parameter is specified then the connector should default to one.
• CQ00245304 When a map service is requested that has not been enabled for WMS, the HTTP content-type of the response messages is text/xml and not application/vnd.ogc.se_xml as required by the WMS specification.
• CQ00246124 A GetCapabilities request should return an error if “service=wms” is not included in the request string. The WMS spec does not require this parameter for GetMap and GetFeatureInfo requests.
• CQ00246126 According to the WMS spec, GetMap and GetFeatureInfo requests should return an error if the “version” parameter is not included in the request string. Currently a request can still be made without this parameter.
• CQ00236150 When a GetMap request contains two layers where the first is invalid and the second is valid, then the response should be an exception (code="LayerNotDefined").