12.0 SP2 Updates

This product update fixes these issues:

• Conditional router duplicates a port name for two different ports.
• Inspection point does not display data after a stream combiner, although data is flowing to one of the input ports.
• When upgrading, JMX Console role mappings were not visible on the JMX Console page. A workaround for this issue is included in the software update Release Notes.
• When restarting the server, some JMX Console role mappings did not display.
• After upgrading, several routing-based services are not shown in the WSDL list, even though they show as exposed in Enterprise Designer.

• When opening a dataflow with a Record Combiner, previously defined channels are missing.
• LDAP user was disabled in Spectrum Technology Platform, but could still sign in to the system.
• Could not purge large comment in Execution History.

• Resolved a graph issue (stand-alone and clustered environments)
• Corrected an issue causing database purges to fail

• Two instances of errors that occurred when duplicate Java classes were loaded after system restart.
• A null pointer exception (NPE) error occurred when running multiple, simultaneous instances of a job.
• While a dataflow processes successfully in a standard processing environment, the same dataflow produces no output record in a distributed environment.
• Excessive amounts of Oracle database queries would cause Spectrum Technology Platform to hang/crash.Users would encounter a 404 error when running/inspecting flows with one or more remote stages.

• Updated JDBC drivers disappeared from Management Console display after being edited and saved.
• Could not connect to a DB2 database using a JDBC driver.
• After importing a dataflow, a job persisted and could not be canceled.

We urge you to apply this product update as soon as you are able to do so. If you do not apply this update, your server may become unusable or inaccessible.

This software update resolves an issue in which process flow activities would be out of sync on cluster nodes.

• Unable to log in to Management Console when a database node is unavailable in a clustered environment (Invalid User/Password message)
• DistributedObjectDestroyed exception occurs in microflow

• The View > ExecutionHistory command in Enterprise Designer was unavailable (grayed out) for a user who was created with testRolepermission.
• A security vulnerability identified by the development team.

• An enhancement to the Global Geocoding Module to support future work on the World Places geocoder.
• Bug fix to resolve a custom dictionary loading issue.

• While creating a layer, under the Define Style Override display style, the image displayed for the region fill styles was often visually clipped, particularly for more complex patterns.
• Spatial Manager was not displaying the resource (for example a NamedTable) that pointed to a NoSQL database source.
• Spatial Manager was not displaying the NamedTable that pointed to the Extensible Data Provider.
• Spatial Manager was throwing rendering map error while previewing the MRR WMS layer. When attempting to preview a raster image built in EPSG:3857 in the WMS layer setup, a GetMap request failure error was displayed as:

  WMSEx_ErrorRenderingMap: Error rendering map.

• Spatial Manager was not displaying the NamedLabelSource correctly. Any NamedLabelSource without an offset element was causing errors in Spatial Manager when accessing its detail page or the label layer that used it. Any label offset of zero is saved without this element.
• When a label layer had an offset of zero, the map was failing to upload (using the Map Uploader). Additionally, when a map already had a label layer with an offset set to zero, it was failing to load in Spatial Manager 12.2.
• With respect to the Generic JDBC, the query made on a table was not working if the schema name or the schema hierarchy contained a dot in the name.
• Extensible Data Providers were not working in Spectrum v12.1 and Spectrum v12.2 when referencing to an external NamedConnection.
• Certain dataflow options not relevant to the Spatial Calculator were resulting in an exception.
• In Search Nearest SOAP and Search Nearest REST, the values of tablePointAttributeName and geomPointAttributeName were appearing interchanged in the response.
• The classified Grid MRR files created using the MapInfo Pro Advanced from version 16.0.3 and forward tools with compression were not displaying.
• The Write Spatial stage was throwing an error for Delete By filter when the filter uses variables.
• Join with XY Table was not working.
• The Map Uploader was sending date and time thematic information in a format, which does not comply with ISO 8601. This is now the standard for Spectrum Spatial.
• The DBF TAB file was not uploading in the Map Uploader.

• Concurrent deletion of named resources was causing out-of-memory errors in some cases; users had to restart the Spectrum server to ensure stability.

• During the server startup, synchronization was failing to delete entities in those cases mentioned above; this occurred when the system was synchronizing named resources and their corresponding access control information.

The following is a description of the new properties:

Spectrum Spatial Analyst is a standalone application that installs and updates separately from the Spectrum Technology Platform.

This product update includes enhancements for the:

• Template Designer by adding Save, Save As, and Save as default options.
• See on Map feature by adding a See on Map button to highlight a record on the map.
• Zoom and Scale Visibility by adding scale visibility constraints.
• Add Layers by letting you enable or disable adding Spectrum Spatial Layers and Local Vector Layers individually from the Admin Console.

See the Release Notes for a complete list of fixes.

Spectrum Spatial Analyst is a standalone application that installs and updates separately from the Spectrum Technology Platform.

This product update improves map load times when browsing and then logging in to see the map, and when switching map configurations.

This product update fixes the Annotation tool for non-transparent annotation and improves performance for loading time.

Spectrum Spatial Analyst is a standalone application that installs and updates separately from the Spectrum Technology Platform.

This product update fixes:

• Launching Analyst via a URL that includes parameters for a query creates tabular results that cannot be sorted correctly when clicking the column headers.
• User queries convert textual comparisons to lower case to ensure the query is case insensitive, which causes significant performance issues in some Spectrum data sources (such as Oracle).
• Launching Analyst via a URL that includes parameters to specify the layers to display does now work in Internet Explorer 11 when the layer name contains non-ASCII characters. This creates a bad request (HTTP 400) error in the browser.

Spectrum Spatial Analyst is a standalone application that installs and updates separately from the Spectrum Technology Platform.

This product update fixes:

• The search zoom is not considered for an info callout when searching for an address or co-ordinates via the Locate bar, which creates results for a wider area.
• When switching map configurations, the zoom layer settings for layers is not honored.
• Querying data in an annotation and exporting the results to CSV produces correct data the first time, but shows the previously exported data on successive CSV exports.

Spectrum Spatial Analyst is a standalone application that installs and updates separately from the Spectrum Technology Platform.

This product update fixes:

• Switching the map config hangs the application when a user launches a map config using the URL launch parameters lon, lat and showInfo.
• System administrators would like to manually update the print_template.xml file to exclude callout and FMN results from PDF documents.
• This update adds two new settings, show-callout-info and show-fmn-results, that when set to false prevent callout and FMN results from displaying in PDF documents.