Release Notes - 10.0 SP1

Spectrum™ Technology PlatformVersion 10.0 SP1

Release NotesThis document contains information about Spectrum™

Technology Platform 10.0 SP1. You have access only to themodules you have licensed. To evaluate any other modules,contact your Pitney Bowes account executive for a trial licensekey.

Complete documentation can be found atsupport.pb.com/spectrum.

Contents:

What's New 2System Requirements 29Installation Notes 43Fixed Issues 54Known Issues 60

http://support.pb.com/spectrum

What's New

This release contains the following new and changed features.

API

OpenSSL Update

The version of OpenSSL included in the Client SDK has been updated to version 1.0.2c to addressvarious security vulnerabilities.

Advanced Analytics Module

Import Data from Miner Datasets

The new Read from Miner Dataset stage extracts field information and data from a Portrait Minerdataset for import into a Spectrum™ Technology Platform dataflow.

Export Data to Miner Datasets

The new Write to Miner Dataset stage creates a Portrait Miner dataset to hold specified fields anddata from a Spectrum™ Technology Platform dataflow.

Support for Naive Bayes PMML Model type

The Model Evaluator has been enhanced to support evaluation of Naive Bayes PMML models.

Support for Association Rule PMML Model Type

The Model Evaluator has been enhanced to support evaluation of Association Rule PMML models.The Association Rule model represents rules where some set of items is associated to another setof items. For example a rule can express that a certain product or set of products is often bought incombination with a certain set of other products, also known as Market Basket Analysis.

2Spectrum™ Technology Platform 10.0 SP1 Release Notes

Release Notes

Advanced Matching Module

Candidate Finder Dataflow Options

The Candidate Finder stage now includes four dataflow options that can be exposed at runtime:

• SearchIndexName—The name of the search index used in the Candidate Finder dataflow.• StartingRecord—The record number on which search results should begin.• MaximumResults—The maximum number of responses you want the index search to return.• ReturnMatchCount—The total number of matches that were made. This field is useful if you entera lower number in the MaximumResults field but want to know the total number of matches thatwere made.

Business Steward Module

New Business Steward Portal

The new Business Steward Portal delivers an improved user experience, offering additionalcustomization options that provide optimal viewing and interaction as well as a responsive webapplication aimed at providing easy reading and navigation from desktop computers to mobiledevices. Additionally, administrators can now specify a maximum number of exceptions to reassignin support of situations where multiple users share the same queue of work. Also, you can nowretain reporting data for exception records that are purged from the repository.

Although the original Business Steward Portal has been deprecated, we will continue to support ituntil release 11.0.

To access the new Business Steward Portal, go to:

http://<servername>:8080/bsmportal

For example:

http://myserver:8080/bsmportal

You can still access the original Business Steward Portal at the following location:

http://<servername>:8080/bsm-portal

Write Exceptions

The Write Exceptions stage now makes it possible for you to limit which fields are visible in theBusiness Steward Portal. Checking the Allow viewing box for a field will result in it being visible inthe Portal; leaving it unchecked will keep the field hidden in the Portal. This feature is useful when


Release Notes

you want to hide fields that contain sensitive data or simply because you want to streamline whatappears in the Portal.

Also, while the order of fields is originally determined by how they are ordered when they come intothe Write Exceptions stage, you can now establish a global field order by rearranging the fieldswithin theWrite Exceptions stage. The order you set here will persist in the Business Steward Portal;however, each user can reorder the fields within the Portal to their own liking.

Microsoft Silverlight Support

Google Chrome is dropping support of Microsoft Silverlight in September 2015. At that time you willneed to access the deprecated Business Steward Portal using Internet Explorer or Firefox.

Data Federation Module

Caching

Data Federation now supports caching in two ways: caching the data of a Metaview, and cachingthe resultsets of queries executed on a SpectrumData Federation connection in Enterprise Designer.

Metaview CachingYou can switch on caching for all, or selective Metaview tables, or switch off caching for all tables.You can also set the cache expiry time either at the table level, or for the entire Metaview.

Resultset CachingThe resultset of a query is cached once. Each subsequent execution of the query utilizes the cachedresultset instead of making a data source trip.

You can configure the expiry time of a query cache using a Cache Hint.

Netsuite Connector

Spectrum™ Data Federation now allows you to create connections to integrate your NetSuite CRMand ERP data with the Spectrum™ Technology Platform.

Once the NetSuite connection is in place, you can read from, write to, and synchronize your NetSuitedata using the Spectrum™ Data Federation Module, and consume the data in Spectrum™ TechnologyPlatform dataflows.

SAP NetWeaver Connector

Spectrum™ Data Federation now allows you to create connections to integrate your SAP CRM andERP enterprise data with the Spectrum™ Technology Platform, using OData Services.


Release Notes

Once the SAP connection is in place, you can read from, write to, and synchronize your SAP datausing the Spectrum™ Data Federation Module, and consume the data in Spectrum™ TechnologyPlatform dataflows.

Splunk Connector

Spectrum™ Data Federation now allows you to create connections to integrate your Splunk serverwith the Spectrum™ Technology Platform.

Once the Splunk connection is in place, you can read data from your Splunk server using theSpectrum™ Data Federation Module, and consume the data in Spectrum™ Technology Platformdataflows.

Write feature is not supported for a Splunk connection in Spectrum 10 SP1.Note:

Salesforce Audit Fields Enabled

Audit fields are now enabled on all tables by default for Salesforce connections.

The Salesforce audit fields are:

• created date• last modified date• created by• last modified by

To view the audit fields in the tables of Baseviews created in Spectrum™ Technology Platformversion 10 using Salesforce connections, the Baseviews need to be opened and savedagain.

Note:

ODBC Connection Support

Spectrum™ Data Federation now supports ODBC connections to access and import data from VirtualData Sources into client applications like MS Excel, MS Access, and so on.

You can now install an ODBC driver, create a Data Source Name (DSN) for the desired Virtual DataSource, and use the DSN to access the Virtual Data Source in your client application.

Data Hub Module

Parameters

The parameters feature makes it possible for you to open the Relationship Analysis Client to aspecific model based on the information provided in the URL. By entering a parameter (in this case,the model parameter) in the URL followed by a value (in this case, the name of the model), you can


Release Notes

bypass the traditional steps of opening a model. You can also open a subset of a model by addinga saved query name to the string. This feature is useful in situations where you want to share all orspecific parts of a model but don't want the recipient to have to complete the steps it would otherwisetake to access the information.

Refresh Models

The Refresh feature in the Relationship Analysis Client will re-open the model that is currently opento its original settings.

Include Monitors and Queries In Copied Models

When copying models via Model Management in the Relationship Analysis Client, you can nowinclude all monitors and queries in the new model.

Partial Traversals

The query builder in Query Hub, Read from Hub, and the Relationship Analysis Client now containsthe Include results from partial traversals option, which enables you to specify whether to returnthe results from each individual step in the query or only the results that meet the requirements ofall steps in the query. Queries generated by the Data Hub Browser will have the option to Includeresults from partial traversals set to false.

Circular Traversals

The query builder in Query Hub, Read from Hub, the Relationship Analysis Client, and the DataHub Browser now contains the Include results from circular traversals option, which enablesyou to specify whether to return elements that occur more than once in each traversal of the resultsor to return those elements just once in each traversal.

New Query Builder Limits

The query builder in Query Hub, Read from Hub, and the Relationship Analysis Client now includesthe Limit results option to specify the total maximum number of entities and relationships returnedin the results. Queries generated by the Data Hub Browser are always limited to 1000 returnedresults.

New Query Builder Operators

The query builder in Query Hub, Read from Hub, the Relationship Analysis Client, and the DataHub Browser now contains the following operators for conditions within the query:

• Is Roughly Similar To—Searches model elements for properties with values close to what youenter in the Data Source field but allows for some differentiation (missing letters, extra letters, orsubstitutions of letters). This operator is equivalent to the Fuzzy search type with search metricof .5.


Release Notes

• Is Similar To—Searches model elements for properties with values close to what you enter in theData Source field but allows for some differentiation (missing letters, extra letters, or substitutionsof letters). This operator is equivalent to the Fuzzy search type with search metric of .6.

• Is Very Similar To—Searches model elements for properties with values close to what you enterin the Data Source field but allows for some differentiation (missing letters, extra letters, orsubstitutions of letters). This operator is equivalent to the Fuzzy search type with Search Metricof .7.

Radial Layout

The new Radial layout in the Relationship Analysis Client places entities on circles around a commoncenter (also known as the root), expanding outward, similar to rings in a tree. The center entity isthe first entity, the first ring contains the "children" entities of the first entity, the second ring containsthe "children" entities of the entities from the first ring, and so on. This layout is useful for modelsthat depict social networks, web analysis, or organizations with a central authority and multiple levelsof management.

Save Queries in the Data Hub Browser

You can now save queries you create in the Data Hub Browser and use them in the Query Hubstage, the Read from Hub stage, or the Relationship Analysis Client.

Data Hub Browser Views

The Data Hub Browser now displays data in four different views:

• Column View—Presents query results in a series of iterative columns (formerly the only viewoption)

• Tree View—Presents query results in a hierarchical manner• Table View—Presents query results in a grid format• Chart View—Presents query results in a graphic manner that can be rotated and includes a tensionrod, which enables you to specify how tight or loose the connections are between entities in thechart

Microsoft Silverlight Support

Google Chrome is dropping support of Microsoft Silverlight in September 2015. At that time you willneed to access the Relationship Analysis Client using Internet Explorer (version 11, ideally) orFirefox.


Release Notes

Enterprise Data Integration

Hadoop 2.x Updates

Spectrum now supports updated Hadoop 2.x libraries, two new Hadoop parameters, and Kerberosauthenticated file servers connections.

Updated Hadoop Libraries

• Apache Hadoop version 2.6 now supported.• Cloudera CDH 5 now supported.

New Hadoop 2.x Parameters

Two new parameters are now required to be configured for a Hadoop 2.x connection.

• fs.defaultfs• mapreduce.app-submission.cross-platform

Kerberos Authentication Security Feature

You can now enable Kerberos Authentication feature while adding a Hadoop Distributed File Server(HDFS) through Management Console.

Ensure the key tab file is placed on the Spectrum™ Technology Platform server.Note:

Spectrum™ Technology Platform does not support Kerberos authentication onWindowsplatforms.

Attention:

Cloudera Certification

Spectrum™ Technology Platform now supports Cloudera CDH 5.

Load to Hive Activity

A new activity, Load to Hive, is now supported.

The activity allows you to read from a Hadoop file, and load data into a Hive table using a JDBCconnection.

New File Server - Azure Cloud ConnectionThis release adds support for configuring Azure cloud connections as a file server.

You can now create a connection to an Azure cloud file server to use the data as required.


Release Notes

Oracle Support in Change Data Capture

Support for the Change Data Capture feature has now been extended for Oracle databases.

The data changes in the table columns are tracked and captured from an entered start date andtime up to the current date and time.

New Buttons in Read From DB

• A new Regenerate Fields button has been added to the Read From DB stage, which needs tobe clicked to fetch the schema of an edited SQL query. On clicking Regenerate Fields, the entitynames in the SQL query are retained and not replaced with their fully qualified names.

• You now need to click the Preview button explicitly to fetch the sample data of an SQL query.This improves the time needed to create or edit an SQL query using the Visual Query Builder.

Compression Support

Spectrum™ Technology Platform now provides compression support for the cloud services of AmazonS3, Google Cloud Storage, and MS Azure Blobstore.

Currently, two types of compression, Gzip (.gz) and Zip (.zip) are supported.

Enterprise Designer

Activities Search

When editing a process flow in Enterprise Designer, you can now search for activities using the newsearch bar in the Activities palette:


Release Notes

CP1047 File Encoding

The CP1047 EBCDIC file encoding is now supported.

This impacts all stages that are used to read from or write to files.

Enterprise Geocoding Module

Japan English Language Support

Japanese addresses can be returned in the character set in which the address was entered. Thismeans that addresses entered in English (Latin character set) are returned in English and Japaneseaddresses are returned in Japanese (Kanji character set). In previous releases, records were alwaysreturned in Kanji even if the input was in English.

For reverse geocoding, the user-specified locale determines the language of the best close matchcandidate.

Both the Japanese and The English language datasets should be used to achieve best possibleperformance. This requires 1GB of RAM.

This English language support feature is available with the updated 2015.05 JPN data vintage andthe Spectrum Technology Platform 10.1 release.

Japan English Language Data Support

Handling Translated Japanese Address Formats

By convention, Kanji Japanese addresses are written with the largest administrative division firstfollowed by the smaller area divisions, with the lot number last. English translated addresses canmaintain this Japanese addressing order. However, in some business practices the English translatedaddresses are written with the smaller administrative units first in keeping with Westernized addressconventions. The Enterprise Geocoding Module accepts English language addresses in eitheraddressing convention. For example, either of the following address formats are acceptable.

Tokyo Shibuya-ku Hiroo 1-1-391-1-39 Hiroo, Shibuya-ku, Tokyo

Handling Prefecture and City Names

Some municipalities have the same name as their prefecture, In single line input, when only oneprefecture/municipality name is given and a descriptor is missing from the input, this is name isalways considered a municipality. For example: .

354-1 Kuroda, Wakayama(Wakayama is considered a municipality)


Release Notes

354-1 Kuroda, Wakayama-ken(Wakayama is considered a prefecture because the descriptor "ken" isattached)

Handling Area Descriptors

Area descriptors such as ken (prefecture) or shi (city) are handled in a wide variety of formats. Thisis necessary because input and source data may have different variations of area descriptors ormay not include area descriptors. For example:

Chiba or Chiba-kenSanmu-shi, Sanmu Sanmu city, Sanmushi

Many other variations are possible because of the translated/transliterated nature of the JapaneseLatin data.

Handling Building Name and Unit Information

Input addresses may contain additional information such as building names, floor number, and unitinformation. For Kanji addresses this information is preserved and returned in the place name field.No special parsing or matching is done with this information.

Kyoto Addresses

In the city of Kyoto, the chome (an urban ward or district, AreaName 4) is a name rather than numeric.This makes it more difficult to distinguish the chome from other numeric address elements. Considerthe following address:

Nishikubo Keihokuakashicho Ukyo-ku Kyoto-shi Kyoto-fu 601-0273

In this address, the data for the matching address contains the address elements:

AN4 (chome): NishikuboAN3 (subcity): keihokuakeshichouAN2 (city): Kyoto-shi Ukyo-ku

There are other examples in which the source data for Kyoto addressees does not have a chomeor for which a chome is present but no subcity (AreaName3) exists.

Sapporo Addresses

Addresses In the city of Sapporo have a unique format than is different than the format for otherJapanese cities. Consider the following addresses:

5-26 Minami 2 Jo Nishi 6 Chome Sapporo


Release Notes

This address is interpreted as follows:

Minami 2 Jo -> means 2 blocks south of intersectionNishi 6 Chome -> means 6 blocks west of intersectionMinami 2 Jo Nishi -> these combine to form the subcity name (AN3)

The directionals used in Sapporo addresses are;

KITA – northMINAMI – southNISHI – westHIGASHI – east

There are many other variations of Sapporo addresses, including variable placement of chome,reversal of chome and jo, and presence/absence and placement of block/lot. The geocoder handlesthese variations for Sapporo addresses.

Handling Concatenated Area Names

The AreaName3 (subcity) in addresses can appear as separate words, hyphenated, or concatenated.For example:

ogi machiogi-machiogimachi

All of these variations can be recognized and the correct candidate is returned.

It is also common for addresses to be entered without spaces between the areanames. For example:

MASHIKO 2070 HAGAGUNMASHIKOMACHI TOCHIGI 3214299

This can be recognized and geocoded. The same address with a space between the AreaName3(subcity) and AreaName2 (city) is also handled correctly:

MASHIKO 2070 HAGAGUN MASHIKOMACHI TOCHIGI 3214299

Reverse Geocoding Japanese Addresses

For reverse geocoding, the user-specified locale determines the language of the best close matchcandidate. English is the default locale.

Return codes with user dictionary

If a geographic, postal, or reverse geocoded candidate comes from a user dictionary, the letter Uis appended to the result code. For example, G4U indicates a locality centroid match from a customuser dictionary. Similary, Z1U indicates a postal centroid match from a custom user dictionary. RS8Uindicates a point/parcel level reverse geocode match from a custom user dictionary.


Release Notes

Additional fields with user dictionary

If you have a user dictionary, you can map additional fields to fit your particular needs. For example,for a country-specific user dictionary you may want to map fields as:

SubUrban=TownSubDistrict=District

You can similarly map fields (such as sublocality) that are unique to specific countries.

Geocode Address AUS Deprecated

Geocode Address AUS has been deprecated. GNAF PID Location Search is the only stage that isused from Geocode Address AUS. For all other Australia geocoding functions, use the GeocodeAddress Global component.

Matching Improvements in Geocode US Address

Improved Handling of Addresses with Misplaced Directionals and Street Types

Improvements have been made in the handling of misplaced characters, directionals and streettypes in the input address. Example matching improvements are listed in the following table. Theseexamples were processed using Close mode.

Old match resultsNew match resultsInput Address

Match Code: E020 - street notfound

2260 E GRAPEVIEW LOOP RD,GRAPEVIEW, WA 98546-9410

Match Code: S8BLocation Code: AP02

E 2260 GRPVW LP R,GRAPEVIEW WA 98546

Previously, the placement of thepre-directional in addition to theabbreviated street name and street typedid not produce a match. Now able to match.


1875 SW RENFRO ST,PORT ST LUCIE, FL 34953-1375

Match Code: S89Location Code: AP02

1875 SW RENFROST,PORT ST LUCIE FL 34982

Input address with street type put as partof street name results in a match.

Returns a match with correctstreet name.


Release Notes



1374 LIBERTY LANDING RD SE,WINNABOW, NC 28479-5139

Match Code: S9FLocation Code: AP02

1374 SE LIBERTY LND,WINNABOW NC

Input address with post-directional placedas pre-directional results in a match.

Returns a match with correctstreet name, street type andpost-directional.

Improved Matching of Truncated and Abbreviated Street Names

Improvements have beenmade in cases where the input address has a street name that is shortenedor truncated. Example matching improvements are listed in the following table. These exampleswere processed using Close mode.



2487 OLD WINDER JEFFERSONHWY,JEFFERSON, GA 30549-4568


2487 OLD WINDER JEF,JEFFERSON, GA

Input address with truncated street nameresults in a match

Now able to match.

14076 SPRINGMILL PONDS CIR,CARMEL, IN 46032-8500

Match Code: T89Location Code: AS0

14076 SPRINGMILL PONDS CIR,CARMEL, IN 46032-8500


Matches a point-level address and

14076 SPRINGMILL PO,CARMEL, IN 46032

Input address with truncated street namenow returns a better match with correctstreet name and street type and ahigher quality geocode.

returns correct street name andstreet type.

16 LAWRENCE AVE,LAWRENCEVILLE,NJ 08648-3533

116 LAWRENCEVILLEPENNINGTON RD,

16 LAWRENCE-PENN RD,LAWRENCEVILLE NJ 08648

LAWRENCEVILLE,NJ 08648-1648Input address with shortened street namenow returns the correct address



Release Notes


Match Code: A88Location Code: AP02

Provides complete street name.

US Address-based ZIP Codes Returned for Input Addresses with Unique ZIP Codes

CASS rules prohibit altering an input ZIP if it matches a unique ZIP Code value. A unique ZIP Codeis a ZIP Code assigned to a company, agency, or entity with sufficient mail volume to receive itsown ZIP Code. Previously, this CASS matching rule was applied in all match modes. This resultedin the return of a standardized street address with a ZIP that was unrelated to the matched streetaddress. This matching behavior has been changed in all non-CASS modes. We now match theinput address against address ranges in the input city, update the ZIP Code and associated returnsbased on the matched address, and provide a match code that more accurately reflects the qualityof the match.

For all match modes, when the Prefer ZIP Code over city option/parameter is set,the unique ZIP Code is not modified.

Note:

New Match ResultsMode and Prefer ZIPCode over City Setting

Input Address

5810 HADRIAN DRDURHAM NC 27710Match Code: Q00

CASS Mode5810 HADRIAN DRDURHAM NC 27710

Matches to USPS range records with unique ZIP Code.Follows CASS rule by not modifying the input ZIP Code.

5810 HADRIAN DRDURHAM NC 27710-0001Match Code: Q80

Close ModePrefer ZIP Code overcity enabled

Honors matching to the input ZIP Code overmatching to the input city.

5810 HADRIAN DRDURHAM NC 27703-7138Match Code: S90

Close ModePrefer ZIP Code overcity disabled

Matches to the USPS data and returnsthe correct ZIP Code.


Release Notes

UI Changes for Geocode US Address Service

The following changes have been made to improve user experience when using the MatchingOptions and Geocoding Options pages in the Geocode US Address service in ManagementConsole:

• Determine Assessor's Parcel Number option - Moved from theMatchingOptions toGeocodingOptions page.

• On the Matching Options page, re-labeled the Candidates options.

From version 10.0 and earlier:

To:

For detailed descriptions of these Matching Options, see theGeocoding Guide for The United States.

Enterprise GeoComplete Module

Point of Interest Data Separately Packaged

GeoComplete POI data is a separate data bundle that must be purchased. Previously, the POI datawas included with the GeoComplete Street address data license.

Enterprise Routing Module

Support for New Countries

The Enterprise Routing Module now provides support for the following countries:


Release Notes

Data VintageISO 3116-1 Alpha-3ISO 3116-1 Alpha-2Country Name

2014.09CUBCUCuba

2014.12ISLILIsrael

New GetTravelBoundary SOAP Service

The GetTravelBoundary service is the first of the routing service to go through a redesign forinteroperability, standardization, and usability. The Enterprise Routing Module SOAP services anddocumentation are accessible through the Spectrum Spatial section of the Welcome Page.

Enterprise Tax Module

Support for Pitney Bowes Master Location Data

This optional data set provides access to Pitney Bowes’ expanded and enhanced data set ofpoint-level geocodes. Note that Master Location Data must be used in conjunction with theGeoTAX/Enterprise Tax Premium Master Files.

New AP Address Location Return Codes

An APnn return code indicates a point-level geocode match representing the center of a parcel orbuilding. AP22, AP23 and AP24 address location return codes are new for MLD.

DescriptionAPnn

Backfill address point

The precise parcel centroid is unknown. The address location assigned is based on two known parcelcentroids.

22

Virtual address point

The precise parcel centroid is unknown. The address location assigned is relative to a known parcelcentroid and a street segment end point.

23

Interpolated address point

The precise parcel centroid is unknown. The address location assigned is based on street segmentend points.

24


Release Notes

New Point-Level Latitude/Longitude Match Codes

New return values have been added for latitude/longitude coordinates that were determined usingMaster Location Data.

DescriptionLatLong.MatchCode

Latitude/longitude coordinates from Backfill Address Point.C

Latitude/longitude coordinates from Virtual Address Point.D

Latitude/longitude coordinates from Interpolated Address Point.E

New Address Match Data Type Return Value

A new return value has been added to indicate a match was obtained using Master Location Data.

DescriptionAddressMatch.DataTypeName

A match was made using Master Location Data.MASTER LOCATION

Updated Florida-Native File Record Format

The Florida-native files from the Florida Department of Revenue provide statewide address andtaxing jurisdiction data and can be used for address matching. The Florida Department of Revenuerecently made changes to the record format. The Enterprise Tax Module has been updated to returninformation in the new format.

The following table shows the updated format:

BytesDescriptionField Name

40USPS long city name.City Name

8Date change goes into effect, in the format YYYYMMDD.Effect Date

50Name of competent evidence file. This field is only requiredfor uploading of address for objections.

Evidence

3Fire district ID number.Fire District ID

3Police district ID number.Police District ID


Release Notes

BytesDescriptionField Name

66Reserved

1Relax match flag:Relax match flag

Match occurred as a result of relaxing secondarymatching.

Y

Match did not occur as a result of relaxingsecondary matching.

N

5Reserved

1Indicates type of database format:Format Indicator

Florida-nativeF

View the AuxiliaryData.StateFile field for the unique state-supplied output data. Any fields that arecommon data, such as county or place, will be returned in the same output fields as any other typeof database match.

Matching Improvements

Improved Handling of Addresses with Misplaced Directionals and Street Types

Improvements have been made in the handling of misplaced characters, directionals and streettypes in the input address.

Improved Matching of Truncated and Abbreviated Street Names

Improvements have beenmade in cases where the input address has a street name that is shortenedor truncated.

For examples showing these matching improvements, see Matching Improvements in GeocodeUS Address on page 13.

Information Extraction Module

Read from Documents Bookmarks Extraction Type

The Read from Documents stage now supports extractions from bookmarks in a PDF, which willproduce the following output fields:

• Bookmark


Release Notes

• PageNo• Parent

Information Extraction Text Categorization

The Information Extraction module now includes functionality to categorize unstructured content orplain text (such as email, news articles, comments, and so on) into custom categories. You cancreate your own categorizer by training a categorizer model with your data and categories. Thetrainer analyzes the data and stores the information it gains in the training process. The categorizercan then analyze the content and determine the category that content belongs to.

Partial Address Support

The Information Extraction module now supports extractions of addresses that do not contain alladdress elements, such as in the following situations:

• Address without state, ZIP code, and country• Address without city, state, ZIP code, and country• Address without house number, state, ZIP code, and country

Location Intelligence Module

MRR Support

Support has been added for MapInfo Pro's new raster data format, Multi-Resolution Raster (MRR).MRR is a unifying format that handles all types of data and provides new capabilities to improve theuser experience when visualizing and processing raster data.

This release of Spectrum Spatial provides the following support for MRR via a TAB file:

• render MRR rasters as maps and tiles using the Mapping Service and Tiling Service that havethe same visual styling as in desktop products such as MapInfo Professional

• query a cell value using the existing functions MI_GridValueAt or MI_GridValueAtPixel in theFeature Service

We recommend copying all MRR companion files (.ghx and .pprc) along with the .mrr fileto the same directory to avoid any instability. These files should be generated using MapInfo

Note:

Pro Raster 1.0. If these files are not copied then the first query or rendering request willtake a significant amount of time to process.

The query API functions support only band 0 for classified, image, and image palette rasterfiles. Also, for continuous raster files, the query of the cell value is limited to the single bandvalue persisted in the ghx file. You cannot specify the field or band to retrieve through theAPI.

Spectrum Spatial supports the reading of a cell value at base level (resolution 0).


Release Notes

See the "Rasters and Grids" topic in the Development section of the Spectrum Spatial Guide formore details such as supported environments, notes, and guidelines for using MRR files withSpectrum Spatial.

Spatial Manager Enhancements

Several enhancements have beenmade to Spatial Manager (previously known as Spectrum SpatialManager) for this release. See the online help for Spatial Manager or the Utilities section of theSpectrum Spatial Guide for more detailed information.

Managing WMS Resources and Configuration

Spatial Manager now allows you to manage Web Map Service (WMS) settings and resources inthe Spatial repository. You can add, move, rename, and delete WMS layers from the new WMSmenu at the top of the application window.

Metadata ManagementSpatial Manager now manages metadata via a metadata resource. You can now add, view, edit,and delete metadata for certain named resources (named tables, layers, tiles, and maps) via theDescription and Keywords fields on their details pages. Using metadata allows you to better organizeyour repository resources and facilitates searching.

Usability Improvements

• When creating named tables using a shapefile as a datasource, Spatial Manager uses thecoordinate system value provided in the shapefile's .prj file or populates it with a default value ifit is missing or unable to be read. It also uses the character set provided in the shapefile's .dbf or.cpg file, otherwise it populates this field with a default value.

• When creating XY tables, Spatial Manager prefills the X, Y and style fields if an appropriate optionis available.

• When searching resources, you can now filter your search results by modified date.

Optional Map Preview

To prevent performance issues, the interactive map preview is no longer automatically displayedon the named layer and named table details pages. You must now click the link to see the mappreview. Be aware that previewing the map for named layers and tables may have a detrimentaleffect on server performance; for example, if the table contains a large quantity of data, the processto render the map still runs even when switching to another resource.

Named Tile Details Page AddedA details page for named tiles is now available in Spatial Manager, similar to the details pages fornamed maps, tables, and layers. This page provides information about a named tile such as itscoordinate system and bounds.

Sample Rows Tab AddedA Sample Rows tab has been added to the details page for named tables. This tab displays up tothe first 10 rows of a table. Viewing these sample rows allows you to assess the health of the table


Release Notes

and understand the data so you can determine whether it is appropriate for your needs. It does notdisplay style, geometry, or raster columns.

SAP HANA Support Enhanced

Spectrum Spatial has enhanced its support for SAP HANA.

Upgraded Version

SAP HANA v9.3 is now supported.

Insert and Update Support

You can now insert and update records into SAP HANA database tables. Records can now beupdated in a SAP HANA table via the SOAP and REST APIs and through the Write Spatial Datadataflow stage. Named tables must be writable in order to be updated; named tables with compositeprimary keys are not writable.

In the Feature Service, updating records is supported through the Insert Features, Update by PrimaryKey, and Update by SQL methods for SOAP and REST.

In the Write Spatial Data stage, inserting and updating records are supported through the Insert,Update by Filter, and Update by Primary Key operations. TheWrite Spatial Data stage uses a namedtable from the repository. The named table must exist prior to configuring the stage. You can optionallyprovide a batch size to indicate how many inserts will be done per transaction. A successful insertreturns the primary keys of the features that were inserted.

Query Optimization for Joins

Non-spatial joins (for example, boolean joins such as AND) and spatial joins (attribute joins suchas LESS_THAN_EQUAL_TO and geometry joins such as CONTAINS) have been optimized so thatprocessing of queries containing those operations is delegated to the SAP HANA data provider.Spatial joins, however, may not work well with older versions of SAP HANA. See the "SupportedData Sources" topic in the Resources and Data section of the Spectrum Spatial Guide.

SRID 0 Support

SAP HANA tables with an SRID of 0 are now supported, as long as the Map Catalog has an entryfor this table with a valid coordinate system (SRS) or the SRS is defined in a named table definitionusing column hints. Otherwise, an exception will be thrown during metadata building of the tableindicating that the coordinate system could not be found.

WMS Changes

Several enhancements have been made to the Web Map Service (WMS).

Managing WMS Resources and Configuration

Spatial Manager now allows you to easily manage WMS resources and its configuration in therepository. You no longer need to edit the configuration file in a text editor; all WMS configuration


Release Notes

of global settings and WMS layers is now done solely by using Spatial Manager. From the newWMS menu at the top of the application window, you can modify WMS settings as well as add,move, rename, and deleteWMS layers and organization layers. Any changes youmake to theWMSservice configuration are now automatically loaded; you no longer need to reload a modified WMSconfiguration using the JMX console.

The sample configuration file that is provided demonstrates its capabilities via its folder structure;for example, that you can have can have coordinate systems on organizational layers so that childrenwill inherit them. It also shows how a WMS layer can reference multiple named layers.

Manual editing of WMS config XML files should only be done by advanced users whorequire functionality that is not supported by the current version of Spatial Manager.

Important:

Unexpected results may occur when using a manually edited configuration file withSpatial Manager.

WMS Settings Support Changes

The Opaque, NoSubsets, FixedWidth, and FixedHeight settings on a WMS layer in the WMSconfiguration have been removed. These settings were never supported, and the WMS server willalways return "false" for these values in the GetCapabilites response.

OGC Compliance

The WMS service provided by Spectrum Spatial is in compliance with OGC specifications for WMSversions 1.1.1 and 1.3.0.

Data Management Enhancements

Metadata resources are now associated with all named resources in the /Samples folder. Thesemetadata resources contain the keywords and descriptions for named layers, tiles, maps, and tables.NamedResourceMetadata is also a new resource type that is returned in a response to a NamedResource Service request to read a named resource from the repository. See the Resources andData section of the Spectrum Spatial Guide for detailed information on metadata resources.

Because you can now manage metadata in Spatial Manager (by adding and editing keywords anddescriptions for named tables, maps, layers, and tiles), the Catalog Service for the Web (CSW) hasbeen removed from Spectrum Spatial.

Spatial Import Utility Relocated and Enhanced

Previously, the Spatial Import utility was located in the%SPECTRUM_HOME%/server/modules/lim/lib directory. It is now located on the SpectrumSpatial section of the Welcome Page, under the Utilities tab. Spatial Import now also supports TABfiles that are produced by the latest versions of MapInfo Professional and can be run on 64-bitWindows platforms in addition to 32-bit.


Release Notes

Performance Improvements

You will experience significant performance improvements in many of the spatial stages. Performanceis noticeably faster better when data is passed in and out of the Read Spatial Data and Query SpatialData stages; in particular when geometries are passed between stages, the improvements aresignificant.

Coordinate Reference System Updates

The following coordinate system support has been added to the Location Intelligence Module toalign with the upcoming MapInfo Professional release. For more information on these new featuresin the 15.0 release, see the "What's New in MapInfo Professional" section in theMapInfo ProfessionalHelp System.

New Datums

• Aratu• Barbados• Beduaram• Conakry_1905• Dealul Piscului 1930 #170• Douala• Final_Datum_1958• Makassar• Manoca• NGO_1948 [1026]• Palestine_1923 [1027]

Transformations

• Updated NTv2 transformation for UK to use official Ordnance Survey GSB file.• Added NTv2 transformation for Netherlands.

RIA Proxy Installer Changes for IIS

The IIS proxy installer now requires IIS7 or above. It is no longer necessary to install the IIS6compatibility components before installing the proxy. Windows 2003 and XP, which have IIS6, areno longer supported. The user must have admin rights and run the installer in administrator mode.

PostGIS Data Provider Enhancements

Previously, the nearest filter was processed by Spectrum Spatial. It is now delegated to the PostGISdatabase if:

• the spatial column type is Geometry• the coordinate system is projected (Cartesian)


Release Notes

Spectrum Spatial still processes filters for all other conditions (for example, for Geography datatypes).

Extensible Data Provider Changes

The development CLASSPATH for a third-party data provider has changed. Before the CLASSPATHhad to contain the %SPECTRUM_HOME%/server/modules/spatial/lib directory. Some of the jarfiles from that directory have been moved to %SPECTRUM_HOME%/server/app/types so bothdirectories need to be on the data provider’s CLASSPATH while developing a third-party dataprovider.

A new method has been added to LinearUnit called valueOfIgnoreCase(String). It has the samesemantics of LinearUnit valueOf(String) except the specified String is evaluated regardless of itscase.

GeoPackage Support Expanded

Read support for GeoPackage is now available for Linux (CentOS) in addition to Windows.

UK Cabinet Office Symbols Available

Map symbols from the UK Cabinet Office are now available for use in Spectrum™ TechnologyPlatform.

The Civil Contingencies Secretariat, working in partnership with theMinistry of Defence andOrdnanceSurvey released a set of commonmap symbols. These are recommended for adoption by emergencyresponder organisations. The symbol set incorporates fixed assets and infrastructure, cordons,incidents and hazards, coordination and communication sites, command and control.

The symbols are contained in%SPECTRUM_HOME%/server/modules/spatial/lib/midev-core-mapping-2.0-onprem.jar afterinstallation. To use, create a named style and use it when you render a map.

For more information about the symbol set, see Civil Protection Common Map Symbology onthe Gov.UK website.

Tile Generator Enhancement

The Tile Generator now uses a connection pool to reuse connections, resulting in improved systemstability.

Documentation Enhancements

The "Supported Data Sources" section of the Resources and Data guide, which was added in theprevious release, has been enhanced to include information on all data providers in addition toGeoPackage and SAP HANA. Information for all data providers has been augmented with identitycolumns, query optimization, volatility, and so on.


Release Notes

https://www.gov.uk/government/uploads/system/uploads/attachment_data/file/168057/Civil_Protection_Common_Map_Symbology_V1-0_March_2012.pdf

Management Console

New Capabilities in the Web version of Management Console

The browser version of Management Console has been enhanced this release to include additionalfeatures previously available only in the Windows client only. The new features in this release are:

• Configure services• View a list of external web services• View, run, pause, and cancel jobs• Configure remote servers

Microsoft Dynamics CRM Module

Batch Address Validation

You can now validate addresses in multiple records by using the batch address validation feature.This feature is useful if you have records in your system that have never been validated.

Batch Match Key Generation

A match key is an identifier assigned to each record and used by the Spectrum™ TechnologyPlatform deduplication process to find records that may be duplicates of each other. If you haverecords in your Microsoft Dynamics CRM system that do not have match keys, you can now generatematch keys for these existing records in order for them to be found by the deduplication process.

Address Validation Report with RDI and DPV Codes

Address validation reports display charts and tables that provide details about the results of addressvalidation, such as the number of records validated and not validated, the reasons for addressvalidation failures. For addresses in the United States, the report also provides codes that indicateif the address is a residence, business, or both (U.S. Postal Service RDI codes), as well as codesthat indicate whether the address is able to have mail delivered to it (U.S. Postal Service DPVcodes).


Release Notes

Platform

Override Input and Output Files in a Job Property File

You can override the input file specified in the dataflow's source stage (such as Read from File), aswell as the output file specified in the dataflow's sink stage (such as Write to File) in a job executorproperty file. To do this, specify the following in the property file:

StageName\:file=Protocol:FileName

You can also use a property file to override the file layout (or schema) of the file specified in thedataflow's Read from File stage and Write to File stage. To do this, specify the following in theproperty file:

StageName\:schema=Protocol:SchemaFile

Process Flows Now Execute Exposed Version of Jobs

In previous releases process flows executed the latest saved version of a job instead of the exposedversion. This behavior has been fixed in this release so that process flows always execute theexposed version of a job.

Because of this change, your process flows may execute different versions of jobsafter upgrading to 10.0 SP1. This will occur if the exposed version of a job is not the

Important:

latest saved version. In this case the process flow will begin executing the exposedversion of the job after you upgrade to 10.0 SP1 instead of the latest saved version.After upgrading you should test your process flows to verify that they continue to producethe desired results.

New Clustering Configuration Property

The spectrum-container.properties file contains a new property that allows you to definea specific node name to associate with the configuration database on this node. You should set thisoption if you plan on manually copying the configuration database from one server to another, suchas copying the configuration database from a staging server to a production server. If you do notspecify this property, an internally-used node name will be automatically generated by the system.

The new property is spectrum.cluster.nodename.

Administration Utility Requires Java 8

The Administration Utility requires Java 8 or later. If you are installing the Administration Utility onthe same computer where the Spectrum™ Technology Platform server is installed, Java 8 is alreadyinstalled since it is included with the server. If you want to install the Administration Utility on anothercomputer, make sure that the computer has Java 8 or later installed.


Release Notes

In previous releases the Administration Utility required Java 7.

Deadlock Detection

Deadlock detection automatically detects when a dataflow becomes deadlocked because two ormore stages are blocking each other from processing. The deadlock detection feature cancels thedataflow and writes a thread dump to the server/app/repository/logs folder.

Universal Addressing Module

U.S. Coding Engine Upgrade

The U.S. coding engine for the 10.1 Universal Addressing Module is compatible only with the 10.0version of the Universal Addressing Module U.S. Database. If you upgrade to Spectrum TechnologyPlatform 10.1 from version 9.3 or older, youmust upgrade to the 10.0 version of the U.S. Database.

Validate Address Loqate Acceptance Level

Validate Address Loqate now includes the Acceptance Level option, which specifies the minimumnumber of address components that must be validated in order for the whole address to be consideredvalidated. One of the following:

• Level 0—No components validated (default)• Level 1—Country only validated• Level 2—City and country validated• Level 3—City, postal code and country validated• Level 4—Street, city, postal code and country validated• Level 5—Premise number, building name, sub-building, PO box, company, street, city, postalcode, and country validated

Validate Address Loqate Minimum Match Score

Validate Address Loqate now includes the Minimum Match Score option, which specifies a numericvalue between 0 and 100 that indicates the degree to which Validate Address Loqate will changean address in order to obtain a match in the Loqate reference database. The lower the number, thegreater amount of change is allowed.


Release Notes

System Requirements

Changes to Supported Operating Systems

• The Spectrum™ Technology Platform server is now supported on Red Hat Enterprise Linux 7,CentOS 7, and Oracle Linux 7. Note the following:

• The Global Geocoding Module is not supported on these operating systems.• The following stages in the Location Intelligence Module which use Centrus databases are notsupported on these operating systems:

• Closest Site• Point in Polygon

• The following Universal Addressing Module services are not supported on these operatingsystems:

• Get Candidate Addresses• Get City State Province• Get Postal Codes• Validate Address• Validate Address AUS

• We are clarifying SUSE support to state that Spectrum™ Technology Platform is supported onSUSE Enterprise Linux Server. OpenSUSE is not supported.

• SUSE Enterprise Linux Server 10 now requires service pack 2 or greater due to the fact thatSpectrum™ Technology Platform now uses Java 8.

• The Location Intelligence and Routing Module is no longer supported on SUSE 10. It is stillsupported on SUSE 11.

Server Requirements

Operating Systems

Spectrum™ Technology Platform is supported on the following operating systems.


Release Notes

NotesOperating System

The Universal Address Module service Validate Address AUS is not supported onthis operating system.

AIX 6.1


AIX 7.1

To use the Address Now Module on this operating system you must install thegcc332 libraries.

The following modules are not supported on this operating system:CentOS 5

• Enterprise Tax Module• Global Geocoding Module• Universal Address Module service Validate Address AUS

The following modules are not supported on this operating system:CentOS 6

• Enterprise Tax Module• Global Geocoding Module• The Closest Site and Point in Polygon stages in the Location Intelligence Module,which use Centrus databases, are not supported on this operating system.

• Universal Address Module service Validate Address AUS

CentOS 7• The Enterprise Tax Module is not supported on this operating system.

• The Global Geocoding Module is not supported on this operating system.• The Closest Site and Point in Polygon stages in the Location Intelligence Module,which use Centrus databases, are not supported on this operating system.

• The following Universal Addressing Module services are not supported on thisoperating system:


• MrSID raster images require libpng12.so on this operating system.


HP-UX 11.31 (Itanium)

The following modules are not supported on this operating system: Address NowModule, Enterprise Tax Module, GeoConfidenceModule, Global Geocoding Module,and the Location Intelligence Module.


Release Notes


Oracle Linux 6• The Enterprise Geocoding-US Module is not supported on this operating system.• The Enterprise Tax Module is not supported on this operating system.• The Global Geocoding Module is not supported on this operating system.• The Closest Site and Point in Polygon stages in the Location Intelligence Module,which use Centrus databases, are not supported on this operating system.

• The Universal Address Module service Validate Address AUS is not supportedon this operating system.

Oracle Linux 7• The Enterprise Geocoding-US Module is not supported on this operating system.• The Enterprise Tax Module is not supported on this operating system.

• The Global Geocoding Module is not supported on this operating system.• The Closest Site and Point in Polygon stages in the Location Intelligence Module,which use Centrus databases, are not supported on this operating system.




Red Hat Enterprise Linux 5


The Closest Site and Point in Polygon stages in the Location Intelligence Module,which use Centrus databases, are not supported on this operating system.

Red Hat Enterprise Linux 6

Red Hat Enterprise Linux 7• The Global Geocoding Module is not supported on this operating system.• The Closest Site and Point in Polygon stages in the Location Intelligence Module,which use Centrus databases, are not supported on this operating system.




Release Notes


The following modules are not supported on this operating system:Solaris 10 (SPARC only)

• Universal Addressing Module services:


• The Closest Site and Point in Polygon stages in the Location Intelligence Module,which use Centrus databases, are not supported on this operating system.

The following modules are not supported on this operating system:Solaris 11 (SPARC only)

• Universal Addressing Module services:


• The Closest Site and Point in Polygon stages in the Location Intelligence Module,which use Centrus databases, are not supported on this operating system.

Requires the following:SUSE Enterprise Linux Server 10.0SP2

• glibc-2.4-31.2, which is approximated by the standard SUSE 10.1 distribution• GCC 4.2 is needed to generate reports

The following modules are not supported on this operating system:

• Location Intelligence and Routing Module• Universal Address Module service Validate Address AUS

Requires glibc-2.9 or glibc-2.11. The Universal Address Module component ValidateAddress AUS is not supported on this operating system. Also requires these runtimelibraries installed as follows:

zypper install libstdc++33-32bit zlib-32bit

SUSE Enterprise Linux Server 11

The Closest Site and Point in Polygon stages in the Location Intelligence Module,which use Centrus databases, are not supported on this operating system.

Requires these runtime libraries installed as follows:

apt-get install libstdc++5:i386 zlib1g:i386

Ubuntu 12.04 LTS


Release Notes


The following modules are not supported on this operating system:

• Address Now Module• Enterprise Geocoding Module (U.S. is not supported; other countries are)• Enterprise Tax Module• Global Geocoding Module• Microsoft Dynamics CRM Module• SAP Module• Siebel Module• Universal Addressing Module


None.Windows Server 2008 R2

The Enterprise Tax Module is not supported on R2.Windows Server 2012 R1 & R2

64-bit Required

The Spectrum™ Technology Platform server requires a 64-bit Unix, Linux, or Windows operatingsystem. 32-bit operating systems are not supported.

Disk Space

Spectrum™ Technology Platform has the following disk space requirements.

UpgradeNew Installation

• Free disk space equal to three times the size of yourcurrent installation. To determine the size of your current

• 3 GB to install all modules, less if installing fewer modules.• 4 GB to 5 GB of temp space for the installation to extractthe files it needs, but you may need more depending on installation, look at the size of the folder where you

installed Spectrum™ Technology Platform.the options you are installing. If necessary, modify yourTEMP environment variable (Windows) or IATEMPDIR • If you are adding modules as part of your upgrade, you

will need 3 GB to install all modules, less if installing fewermodules.

environment variable (Unix and Linux) to point to alocation with enough space.

• 4 GB to 5 GB of temp space for the installation to extractthe files it needs, but you may need more depending onthe options you are installing. If necessary, modify yourTEMP environment variable (Windows) or IATEMPDIRenvironment variable (Unix and Linux) to point to alocation with enough space.


Release Notes

If you are installing a module that uses a reference database, such as a postal database,geocoding database, or data normalization tables, you will need space for this data. The

Note:

total disk space varies, depending on what modules(s) and what database(s) you areinstalling.

Memory

• Basic memory requirement: 8 GB• The Enterprise Geocoding Module requires an additional 500 MB memory for the first non-U.S.geocoder, and 250 MB for each additional non-U.S. geocoder, with these exceptions:

• Germany, Australia, and the U.K. each require 1 GB additional memory• Japan requires 2 GB additional memory

Note that you may distribute processing among multiple servers which may allow you to takeadvantage of existing hardware instead of adding memory to a single Spectrum™ TechnologyPlatform server. This is referred to as remote server processing. For information on remote servers,see the Spectrum™ Technology Platform Dataflow Designer Guide.

• The Location Intelligence Module requires an additional 2 GB RAM to support its mapping andfeature components.

• The Data Normalization Module and Universal Name Module require additional memory if youuse the following name databases:

• Arabic Plus Pack: 5.5 GB• Asian Plus Pack - Chinese: 32 MB• Asian Plus Pack - Japanese: 1.6 GB• Asian Plus Pack - Korean: 8 MB• Core Names: 1.1 GB

Additional Requirements

• For all Unix/Linux systems, a minimum of 8192 file descriptors is required. This can be set byrunning the ulimit command:

ulimit –n 8192

• For IBM AIX systems only, you must download and install Java 8, both the 32-bit version and the64-bit version, before installing Spectrum™ Technology Platform. If you do not have Java 8 installed,download and install it from:

www.ibm.com/developerworks/java/jdk/aix/service.html

• Windows administrator rights

Requirements for the Address Now Module

• Red Hat/SUSE Linux—512 MB RAM, gcc compiler, and library version 4.1.2


Release Notes

http://www.ibm.com/developerworks/java/jdk/aix/service.html

• Sun Solaris—At least an UltraSparc processor with a speed of at least 400 MHz and at least 512MB RAM, gcc compiler, and library version 3.3

Requirements for the Universal Addressing Module

• Root privileges are required to install the Universal Addressing Module.

Default Network Ports

The Spectrum™ Technology Platform server uses several network ports for communication. Networkport conflicts can result in module components failing to start up. One indication that a componenthas failed to start up is if it does not appear in the Management Console. To troubleshoot the problem,look in the Spectrum™ Technology Platform log file. This log shows which port is causing the problem.You can find the Spectrum™ Technology Platform log file in:

server\app\repository\logs\server.log

The following table lists the default network ports. You can change the ports by modifying theproperties in this file:

server\app\conf\spectrum-container.properties

If you want to change the networks ports used by a cluster, you must modify thespectrum-container.properties file on each node in the cluster.

Note:

DescriptionPropertyPort

This port is used by the Spectrum™ TechnologyPlatform configuration database.

spectrum.orientdb.binary.port2424-2430


spectrum.orientdb.hazelcast.port2434


spectrum.orientdb.http.port2480-2486

This port is used by Hazelcast for managingdistributed processing between Spectrum™

Technology Platform servers in a cluster.

spectrum.hazelcast.port5701

The port used for communication between theserver and Enterprise Designer, Management

spectrum.http.port8080

Console, and Interactive Driver. This port is alsoused by web services.

This port is used for API calls made to services.spectrum.socketgateway.port10119


Release Notes

Client Tools Requirements

Enterprise Designer, Management Console, and Interactive Driver require the following:

• Operating system requirements:

• Windows XP• Windows 7

• 86 MB of disk space to install the client without any modules. Each module you install requiresadditional disk space.

• Microsoft .NET Framework 4.0 (available from the Spectrum™ Technology Platform WelcomePage, http://<SpectrumServerName>:8080)

• The Administration Utility requires Java 8 or later. If you are installing the Administration Utility onthe same computer where the Spectrum™ Technology Platform server is installed, Java 8 isalready installed since it is included with the server. If you want to install the Administration Utilityon another computer, make sure that the computer has Java 8 or later installed.

• A monitor with at least 1024 x 768 resolution• Maximum Windows DPI setting: 150%• Adobe Reader 7 or later (for viewing and saving reports)• To use the deprecated Business Steward Portal or the Data Hub Relationship Analysis Client, abrowser with Microsoft Silverlight 5 installed. See www.microsoft.com/getsilverlight. Note thatGoogle Chrome is dropping support of Microsoft Silverlight in September 2015. At that time youwill need to access these client tools using Internet Explorer (version 11, ideally) or Firefox.

• To use the new Business Steward Portal or the Data Hub Browser, a Web browser is required.

Web Browser Requirements

• Internet Explorer 10 or later• Google Chrome 43 or later• Firefox 38 or later

Client SDK Requirements

The Client SDK provides API access to Spectrum™ Technology Platform services. To use the ClientSDK your computer must meet the following requirements:

• 1.25 GB disk space• JDK 1.5 is required to install the Client SDK. Be sure that JDK 1.5 is in the PATH environmentvariable. Once installed, the Client SDK supports JDK 1.4 and greater.


Release Notes

http://www.microsoft.com/getsilverlight

Supported Compilers

The Spectrum™ Technology Platform Client SDK is supported with the following compiler andruntime minimum versions.

Java

Client SDK Package Directory: clientSDK/platforms/java

Client SDK requires the Java JDK, version 1.4 or higher. This is not installed with the Client SDK.

Windows 32-bit

• JDK: 1.4• C Compiler: MSVC 6.0 SP3, MSVC 2003, MSVC 2005, MSVC 2008• C++ Compiler: MSVC 6.0 SP3, MSVC 2003, MSVC 2005, MSVC 2008• C# .NET: Microsoft .NET Framework 1.1• Visual Basic: MS Visual Basic 6.0

Windows 64-bit

• JDK: 1.4• C Compiler: MSVC 2005, MSVC 2008• C++ Compiler: MSVC 2005, MSVC 2008

HP-UX RISC

• JDK: 1.4• C Compiler: cc: HP92453-01 A.11.01.21 HP C (Bundled) Compiler• C++ Compiler: aCC: HP aC++ B3910B A.03.30 HP aC++ B3910B A.03.27

The clientSDK 32-bit lib is linked to the following libraries:

• libpthread.1• librt.2• libnsl.1• libxti.2


• libpthread.1• libnsl.1• librt.2• libdl.1• libc.2• libxti.2• libdl.1


Release Notes

HP-UX Itanium

• JDK: 1.4• C Compiler: cc: HP aC++/ANSI C B3910B A.06.05• C++ Compiler: aCC: HP aC++/ANSI C B3910B A.06.05


• libpthread.so.1• libnsl.so.1• librt.so.1• libxti.so.1• libdl.so.1


• libpthread.so.1• libnsl.so.1• librt.so.1• libxti.so.1• libdl.so.1

Red Hat (32-bit)

• Operating System: Red Hat Linux 2.4.9-e.65smp• C Compiler: gcc version 2.96 (gcc 4.1 required for the Address Now Module)• C++ Compiler: g++ version 2.96

The clientSDK lib is linked to the following libraries:

• libstdc++-libc6.2-2.so.3• libm.so.6• libc.so.6• ld-linux.so.2

Red Hat (64-bit)

• Operating System: Red Hat Linux version 2.6.9-34.0.2.ELsmp• C Compiler: gcc version 3.4.5• C++ Compiler: g++ version 3.4.5

The clientSDK lib is linked to the following libraries:

• libstdc++.so.6• libm.so.6• libgcc_s.so.1• libpthread.so.0• libc.so.6• ld-linux-x86-64.so.2


Release Notes

SuSE

• Operating System: SuSE SLES 8 (powered by UnitedLinux 1.0) (i586)\nKernel 2.4.21-295-smp(0).

• C Compiler: gcc version 3.2.2• C++ Compiler: g++ version 3.2.2

The clientSDK lib (32-bit) is linked to the following libraries:

• libstdc++.so.5• libm.so.6• libgcc_s.so.1• libc.so.6• ld-linux.so.2

Solaris

• Operating System: Solaris 5.8• C Compiler: cc: Forte Developer 7 C 5.4 2002/03/09• C++ Compiler: CC: Forte Developer 7 C++ 5.4 Patch 111715-16 2005/04/28


• libpthread.so.1• libsocket.so.1• libnsl.so.1• librt.so.1• libc.so.1• libdl.so.1• libmp.so.2• libaio.so.1• libc_psr.so.1


• libpthread.so.1• libsocket.so.1• libnsl.so.1• librt.so.1• libc.so.1• libmp.so.2• libmd5.so.1• libscf.so.1• libaio.so.1• libdoor.so.1• libuutil.so.1• libm.so.2


Release Notes

• libc_psr.so.1• libmd5_psr.so.1

AIX

• Operating System: AIX version 5.1.0.0• C Compiler: xlc 6.0 Visual Age C 6.0• C++ Compiler: xlC 6.0 Visual Age C++ 6.0

The clientSDK 32-bit and 64-bit lib are linked to the following libraries:

• libC.a• libc_r.a• libpthread.a• librtl.a

Location Intelligence Module Support

Database

The Location Intelligence Module supports the following spatial databases for use with the spatialservices, data, and resources:

• Oracle 11gR2• SQL Server 2008 R2, SQL Server 2012• SAP HANA 9.3• PostgreSQL 8+ (PostGIS 1.5 and 2.x)• GeoPackage (Windows and CentOS)

Data Format

The Location IntelligenceModule supports the following data formats for use with the spatial services:

• Generic JDBC (w/XY)• TAB (native, raster, grid, seamless, DBF)• ESRI ShapeFile

Raster Format

The following raster and grid formats (64-bit only) are supported in the Location Intelligence Module:

Raster formats:

File ExtensionFormat.genADRG

.genASRP


Release Notes

.bmp, .wbmpBMP

.genCADRG

variousCIB

.ecwECW (SDK v5)

.geotifGeoTiff

.gifGIF

.jpg/.jpegJPEG

.mrrMRR (Multi-Resolution Raster)

This support is provided on Windows 64-bit and thefollowing Linux environments:

Note:

• Oracle Linux 6.5 and 7.1• CentOS 6.4 and 7.1• Ubuntu 12.04

.sidMrSID (SDK v9)

Supports MG4 (MrSID Generation 4). On CentOS 7.1,libpng12.so is required for reading MrSID rasters.

Note:

.ntfNITF

.pngPNG

.tifTIFF

Solaris or AIX machines, whether installed with 32- or 64- bit JVM, do not support ECW andMrSID raster formats.

Note:

Grid Formats

File ExtensionFormat.dt0, .dt1, .dt2, .dt3Defense Digital Terrain Elevation Data (DTED)

.migMapInfo Grid

.grcVertical Mapper Classified Grid

.grdVertical Mapper Continuous Grid

In order to use rasters and grids as a map layer, there must be an associated .TAB file containinggeoreference information about the image, including the bounds, coordinate system and registrationpoints.

BrowserThe Location IntelligenceModule spatial client development, samples, and SpectrumSpatial Managersupport the following browsers:


Release Notes

• Microsoft Internet Explorer 10 and 11• Mozilla Firefox 35 and above• Google Chrome 40 and above• Safari (Mac OS X) and Safari 5.1.7 for Windows

Utilities

The Location Intelligence Module utilities (Tile Generator, Map Uploader, Geometry Validator) havethe follow requirements:

• These utilities require at a minimum Java 7. If you are installing these utilities on the same computerwhere the Spectrum™ Technology Platform server is installed, Java 8 will be installed since it isincluded with the server. If you want to install the utilities on another computer, make sure thatthe computer has Java 7 or later installed.

• The Map Uploader also requires Microsoft .NET Framework 4.0 (available from the Spectrum™

Technology Platform Welcome Page, http://<SpectrumServerName>:8080)

OGC Compliance

The Location Intelligence Module is OGC compliant for the following services:

• WFS version number 1.0.0• WMS version number 1.1.1 and 1.3.0

MapInfo Professional Compatibility

The Location Intelligence Module is compatible with MapInfo Professional up to version 15.x. SeeTools > MapInfo Pro in the Spectrum Spatial Getting Started Guide for more information about theinteroperability of the two products.

Microsoft Dynamics, SAP, and Siebel Compatibility

This release of Spectrum™ Technology Platform is compatible with the following versions of MicrosoftDynamics, SAP, and Siebel:

Compatible Versions of Microsoft Dynamics

Microsoft Dynamics CRM 2013Microsoft Dynamics CRM 2013 SP1

Compatible Versions of SAP

SAP CRM 6.0SAP CRM 7.0 EHP 1 through 3SAP ECC 6.0 EHP 1 through 7SAP Web DynPro Java 7.01


Release Notes

Compatible Versions of Siebel

Open UI for Siebel Business Applications 8.1.1.11.4Open UI for Siebel Industry Applications 8.1.1.11.4Siebel Business Applications 8.0Siebel Business Applications 8.1.1Siebel Industry Applications 8.0Siebel Industry Applications 8.1.1

Installation Notes

For complete instructions on installing Spectrum™ Technology Platform, including systemrequirements, see the Spectrum™ Technology Platform Installation Guide available atsupport.pb.com.

Upgrade Paths

You can upgrade to Spectrum™ Technology Platform 10.0 SP1 from:

• 10.0• 9.0 SP3• 8.0 SP3

If you have another version installed, you must first upgrade to one of the above versions, and thenupgrade from that version to 10.0 SP1.

Upgrading Client Tools

You need to upgrade Enterprise Designer, Management Console, and Interactive Driver if either ofthe following apply to you:

• You are currently using version 8.0 SP3 of the client tools. You must upgrade from these versionsto 10.0 or later in order to take advantage of security features in this release.

• You are planning on installing the configuration database to a separate server from the Spectrum™

Technology Platform server.• You want to see the new login window design.

To upgrade these client tools, download the client tools installer from the Spectrum™ TechnologyPlatform welcome page on your server and run the installer on any computer that has a client toolinstalled. The installer will upgrade the client tools to 10.0 SP1. For more information on installingclient tools, see the Spectrum™ Technology Platform Installation Guide.


Release Notes

http://support.pb.com

Upgrading the Advanced Matching Module

When you upgrade the Universal Name, Data Normalization, and AdvancedMatchingModules fromSpectrum™ Technology Platform 10.0 to 10.1, it is important to first back up the contents of thesearch index directory to retain changes you have made to settings in the search index propertyfiles. The upgrade will overwrite the existing files and restore default settings.

This issue does not apply if you are upgrading from Spectrum™ Technology Platform 9.0SP3 or 8.0 SP3.

Note:

1. Prior to upgrading, navigate to the following directory:

<SpectrumLocation>/server/modules/searchindex

2. Back up the contents of the searchindex folder to a different location.3. Perform the upgrade. When the upgrade is complete, stop the Spectrum™ Technology Platform

server.4. Overwrite the contents of the searchindex folder with the files that you saved in step 2.5. Start the Spectrum™ Technology Platform server.

Upgrading the Data Hub Module

Several important steps must be taken before and after you upgrade the Data Hub Module. Beforeupgrading it is important to first back up all of your models as well as any configuration files thathave been modified. The upgrade will overwrite the existing files and restore default settings.

1. Follow the instructions in "Backing up Data Hub Models" from the Master Data ManagementGuide.

2. Back up the following files to a different location:

SpectrumLocation\server\modules\hub\hub.propertiesSpectrumLocation\server\modules\hub\db\neo4j.properties

3. Be sure to shut down all models properly. The system is able to recover an improperly shut-downmodel, but only using the version of the software that created that model. Likewise, the systemis not able to upgrade an improperly shut-down model. If this occurs, you will need to reinstallthe prior version of Spectrum™ Technology Platform and reopen the models, shut down themodels properly, and begin the upgrade process again.

4. Perform the upgrade. When the upgrade is complete, stop the Spectrum™ Technology Platformserver.

5. Set the following SpectrumLocation\server\modules\hub\hub.properties propertyto true to indicate that you have properly backed up all your models:

#Uncomment to allow your graph to be upgraded to next release. A storeupgrade#is an irreversible operation. Take care to backup your installationfirst!allow_store_upgrade=true


Release Notes

The purpose of this property is to protect against unintentional and irreversible store upgrades.Setting this property to "true" indicates that you understand the ramifications of proceeding withan upgrade and have taken the necessary precautions to secure your models.

6. Start the Spectrum™ Technology Platform server. By default, theSpectrumLocation\server\modules\hub\hub.properties file contains the followingproperty:

hub.model.autostart.policy=nometadata,needsupgrade,recent

This property causes the server to open and upgrade each model.7. Examine the SpectrumLocation\server\app\repository\logs\wrapper.log file for

errors or warning messages.8. After all models have been upgraded, comment out the following property from the

SpectrumLocation\server\modules\hub\hub.properties file as an extra safeguardfor the next upgrade.

allow_store_upgrade=true

9. Start the Spectrum™ Technology Platform server.

Upgrading the Enterprise Tax Module

To upgrade the Enterprise Tax Module to Spectrum™ Technology Platform 10.0 from a version priorto 9.0 SP2:

• If you are fully licensed for the Universal Address Module in 10.0, you have the option to streamlinean existing two-step process that uses the Universal Address Module for address standardizationto a single-step process by making some minor changes, as described in the following section.

• If you received the Universal Address Module as part of your Enterprise Tax Module license, andhave an existing two-step process that uses the Universal Address Module for addressstandardization, it is required that you change the two-step process to a single-step process, asdescribed in the following section.

For batch processes:

• For a batch process that first runs the Universal Address Module, and then the Enterprise TaxModule as separate processes: Eliminate the Universal Address Module step and use the originalinput to the Universal Address Module as the new input to the Enterprise Tax Module.

• For a batch process with a custom flow that combines the Universal Address Module and EnterpriseTax Module as a single process: Replace the custom service with the current version of theEnterprise Tax Module.

For processes using service calls:

• For a process that first calls the Universal Address Module, and then the Enterprise Tax Moduleas separate calls: Eliminate the Universal Address Module call and only call the Enterprise TaxModule.


Release Notes

• For a process with a custom flow that combines the Universal Address Module and the EnterpriseTax Module as a single service: Change the name of the service being called to AssignGeoTAXInfo.

Not all of the return codes from the Universal Address Module were retained in the EnterpriseTax Module. You may need to adjust how the return codes are used in your processes.

Note:

Upgrading the LIM Module

Although part of the Spectrum upgrade installation process for the Location Intelligence Module isto automatically back up the data from a previous release before the upgrade continues, it is importantto back up custom data sources and resources prior to upgrading using WebDAV as a precaution.

Any data that was installed with the module will be deleted after upgrade. If custom data is locatedin the same directories, back it up and copy to the same location in the Spectrum™ TechnologyPlatform directories once upgraded.

It is also very important to perform a backup of the repository after the Spectrum™ TechnologyPlatform upgrade is successful, to serve as a baseline in case your repository becomes corrupt lateron. If you upgrading to 10.0 SP1 from 8.0 SP3 or 9.0 SP3, there are significant changes to therepository that will render previous backups ineffective. Make a copy of the entire repository locatedin the %install_home%\Spectrum\server\modules\spatial\jackrabbit directory, andsave it to a secure location.

Permissions to resources in the Spectrum Spatial repository are retained when upgrading from 9.0SP3 to the current version. Permissions are not retained when upgrading from version 8.0 SP3 toany 9.0 or 10.0 release due to changes in the security architecture introduced in 9.0.

Upgrading from Spectrum Spatial 1.x to the latest version is no longer supported as of the 9.0 SP3release.

Upgrading the SSL Configuration File

If you use SSL for communication with the Spectrum™ Technology Platform server and are upgradingfrom 8.0 SP3, you must update the SSL configuration file after upgrading to 10.0 SP1.

If you use SSL and do not make this update you will be unable to communicate withthe Spectrum™ Technology Platform server after upgrading to 10.0 SP1.

Important:

1. Using a text editor, open the file spectrum-override-container-ssl.xml located in<SpectrumLocation>/server/app/conf/spring.

2. Change this:

com.g1.dcg.server.jetty.JettyDelayedServerConnector

To this:

org.eclipse.jetty.server.ServerConnector

3. Save and close the file.


Release Notes

Required Operating System Updates

Before installing Spectrum™ Technology Platform, be sure to apply all the latest product updatesavailable for your operating system, especially those that resolve issues with Java.

Extracting Spectrum ZIP Files

With this release the zip file that contains the Spectrum™ Technology Platform installer has grownto over 4 GB. You must have an unzip tool that is capable of extracting a zip file that is larger than4 GB in order to install Spectrum™ Technology Platform.

Upgrading a Separated Configuration Database

Due to a known issue with the 10.0 release, youmust follow these steps before upgrading a separatedconfiguration database from 10.0 to 10.0 SP1.

1. On the server where you have installed the configuration database, open the following file in aneditor: prodrepo.xml. You can find this file in the folder where you have installed theconfiguration database.

2. Find this line:

<installerversion>99.99.00.F01.01</installerversion>

Change the value to:

<installerversion>10.00.00.F01.01</installerversion>

3. Save and close the file then proceed with the upgrade procedure as documented in the InstallationGuide.


Back Up Location Intelligence Module Named Resources and Data

Although part of the Spectrum upgrade installation process for the Location Intelligence Module isto automatically back up the data from a previous release before the upgrade continues, it is importantto back up custom data sources and resources prior to upgrading using WebDAV as a precaution.


Release Notes

Any data that was installed with the module will be deleted after upgrade. If custom data is locatedin the same directories, back it up and copy to the same location in the Spectrum™ TechnologyPlatform directories once upgraded.

It is also very important to perform a backup of the repository after the Spectrum™ TechnologyPlatform upgrade is successful, to serve as a baseline in case your repository becomes corrupt lateron. If you upgrading to 10.0 SP1 from 8.0 SP3 or 9.0 SP3, there are significant changes to therepository that will render previous backups ineffective. Make a copy of the entire repository locatedin the %install_home%\Spectrum\server\modules\spatial\jackrabbit directory, andsave it to a secure location.

Notes on Upgrading Metadata

• If you added metadata (keywords and descriptions) to named resources using Spectrum SpatialManager in version 10.0, these will be preserved in the upgrade to 10.0 SP1 unless you have aLIM cluster setup.

• The backup copy created during the upgrade process does retain keywords and descriptions andcan be copied back to your 10.1 SP1 repository via WebDAV. Keywords and descriptions are notretained, however, for manual backups created via WebDAV.

LIM Upgrade Backup Failure Procedure

Part of the Spectrum upgrade installation process for the Location Intelligence Module is toautomatically back up the data from a previous release before the upgrade continues. If the installerencounters an error during the backup, the installer will display an appropriate message and theinstaller will stop.

To re-attempt an upgrade after the error, complete the following steps:

1. Go to the <Spectrum installdir>\server\modules directory andmake a backup of the lim_backupx.xfolder at some other location (where x.x is the backup version).

2. Delete the lim_backupx.x folder from the \modules directory.3. Re-launch the Spectrum installer and follow the installation steps.

The Spectrum Spatial LIM module should upgrade successfully now.

To ensure a successful upgrade process in the first place, be sure to manually back up your databeforehand. See Back Up Location Intelligence Module Named Resources and Data on page47.

Back Up and Restore Location Intelligence Module Configuration FilesThe upgrade process from Spectrum™ Technology Platform will overwrite the configuration files forthe Location Intelligence Module. So that you do not lose custom settings, it is important that youfirst back up the files before proceeding with the upgrade.

Follow these instructions if you:

• Run Spectrum™ Technology Platform server on a port other than 8080.• Have made changes to any of the Location Intelligence Module configuration files:


Release Notes

SOAP Services (Mapping, Feature)•• Map Tiling• Named Resources• WMS• WFS• User Management

Configuration files are stored in the repository and cannot be accessed on the file syste unless youuse theWebDAV protocol and copy the files to another location. OnWindows, you can useWebDavfrom Windows Explorer. On Linux/UNIX, use WebDAV from a Windows client or from the desktopfile explorer. The easiest way to access Repository files via WebDAV is to use the direct WindowsExplorer client and create a mapped drive connection to the repository.

Before the upgrade, you should also back up the java.properties and java.vmargs files that residein %install_home%\Spectrum\server\modules\spatial to preserve any customizations you havemade.

To back up and restore user-modified configuration files and properties files:

1. Create a mapped drive connection to the repository by following these steps.a) Verify that you have the correct URL. In your web browser enter

http://<yourhost:port>/RepositoryService/repository/default/. The rootof the repository should display in your web browser.

b) Copy this URL and then via Windows Explorer right-click on the Computer icon and selectMap Network Drive.

c) Paste the URL into the Folder text box and click Finish. Windows will match the drive letter toyour repository and display the root of the repository with the same content as your webbrowser.

2. In Windows Explorer go to the mapped location for the repository and copy the Configurationfolder to a safe location.

3. Make a backup copy of \modules\spatial\java.properties and java.vmargs to save any non-defaultsettings.

4. Perform the Spectrum™ Technology Platform upgrade.5. Copy the backed up Configuration folder to the repository, overwriting the folder created during

the upgrade.6. Compare your backed up java.properties and java.vmargs files with the new ones to ensure any

properties you added or changed were preserved.7. Stop the Spectrum server and restart it after making these changes or reset each affected service

from the jmx-console.

If you forgot to back up the configuration, java.properties, or java.vmargs files, you can checkthe backup zip file that is created by the upgrade process (as long as no failures occurred).

Note:

This zip file (upgrade_backup_yyyyMMddHHmmss.zip) is located in“%install_home%\Spectrum\server\modules”.


Release Notes

Upgrading on SUSE

If you are upgrading from version 10.0 to 10.0 SP1 on SUSE Enterprise Linux Server 11, you mustremove the following files (if they exist) prior to starting the server after the upgrade:

• <SpectrumInstallationLocation>/server/app/deploy/centrus-10.0.car• <SpectrumInstallationLocation>/server/app/deploy/spatial-10.0.car

Upgrading a Clustered Environment for Location Intelligence Module

The upgrade process for a clustered environment in LIM is documented in the Installation Guidelocated on support.pb.com. See the section entitled Upgrading with Clustering for the LocationIntelligence Module.

Authentication Error When Upgrading an 8.0 SP3 Clustered Environment for LocationIntelligence Module

If you are upgrading an 8.0 SP3 clustered environment, one of the pre-upgrade steps is to switchfrom a common repository database to the local Derby database and copy the backed uprepository.xml. These pre-upgrade instructions are located in the "Upgrading Clustering in theLocation Intelligence Module" topic in the Installation Guide on support.pb.com.

After you copy the repository.xml and restart the Spectrum server, you will likely see the followingerror in the wrapper.log java.sql.SQLNonTransientConnectionException: Connectionauthentication failure occurred. Reason: Invalid authentication.

The reason for the failure is that the 8.x repository.xml does not contain the Derby databasecredentials attribute.

To resolve this, stop the server, add the following in two places under the Persistence Manager tag:;user=sa;password=group!, then restart the server before proceeding with the upgrade.

Repository.xml after adding Derby credentials

<PersistenceManagerclass="org.apache.jackrabbit.core.persistence.pool.DerbyPersistenceManager">

<param name="url"value="jdbc:derby:${wsp.home}/db;create=true;user=sa;password=group!"/>

<param name="schemaObjectPrefix" value="${wsp.name}_"/></PersistenceManager>

<PersistenceManagerclass="org.apache.jackrabbit.core.persistence.pool.DerbyPersistenceManager">

<param name="url"value="jdbc:derby:${rep.home}/version/db;create=true;user=sa;password=group!"/>


Release Notes



<param name="schemaObjectPrefix" value="version_"/></PersistenceManager>

Upgrading PostGIS Tables and Named Connections

When upgrading from 8.0 SP3, any PostGIS named table existing as a GeoTools table will betransformed to a PostGIS data provider table. This upgraded table will not have inline connectiondetails; rather, it will have a reference to a PostGIS named connection that has the same connectiondetails.

This does not apply when upgrading from 9.0 SP3 or later, as these chages are alreadyincluded in the release.

Note:

Example of an Upgraded PostGIS Table:

<?xml version="1.0" encoding="UTF-8"?><NamedDataSourceDefinition version="MXP_NamedResource_1_5"

xmlns="http://www.mapinfo.com/mxp" ><ConnectionSet><NamedConnectionRef resourceID="/PostgresConnection"><ConnectionName>PGConnection</ConnectionName></NamedConnectionRef></ConnectionSet><DataSourceDefinitionSet><DBDataSourceDefinition id="PostGISWorldTable"><DataSourceName>WORLD</DataSourceName><ConnectionMember><ConnectionName>PGConnection</ConnectionName></ConnectionMember><DBTable owner="schema" useQuotes="true">WORLD</DBTable></DBDataSourceDefinition></DataSourceDefinitionSet><DataSourceRef ref="id1"/></NamedDataSourceDefinition>

Example of an Upgraded PostGIS Named Connection:

<?xml version="1.0" encoding="UTF-8"?><NamedConnection xmlns="http://www.mapinfo.com/mxp"xmlns:gml="http://www.opengis.net/gml" version="MXP_NamedResource_1_5">

<DBConnection dbType="postgis"><ConnectionName>PostGISConnection</ConnectionName><JDBCDriverParameters><JDBCUrl>jdbc:postgresql://localhost:5432/PostGIS?

user=postgres&password=postgres&schema=public</JDBCUrl><DriverPropertySet><Property name="user" value="postgres"/>


Release Notes

<Property name="password" value="postgres"/></DriverPropertySet></JDBCDriverParameters></DBConnection></NamedConnection>

An existing named table will not be upgraded to use a named connection if the namedconnection and named table do not have identical string values for the machine name.

Note:

Permissions After Upgrading

Permissions to resources in the Spectrum Spatial repository are retained when upgrading from 9.0SP3 to the current version. Permissions are not retained when upgrading from version 8.0 SP3 toany 9.0 or 10.0 release due to changes in the security architecture introduced in 9.0.

LIM Installation Directory Names and Special Characters

For Spectrum™ Technology Platform installations that include the Location Intelligence Module, theinstallation directory names must not contain any of these escaped characters.

• & - Ampersand• > - Greater Than• < - Less Than• ' - Apostrophe• " - Quote


Database Memory Usage

For loading a large Enterprise Routing database, you might have to increase the memory of therouting remote component. To do this, set the value of the –Xmx parameter in the java.vmargs fileto a value larger than the size of the database. For example, in the case of loading entire UnitedStates database (size is approximately 1.94 GB), setting the value of –Xmx to 2048m would besufficient. The location of the java.vmargs file is %install_home%\server\modules\routing.

On Solaris 10 (SPARC) machines, you have to increase the memory of routing remotecomponent by setting the value of –Xms parameter instead of the –Xmx parameter in thejava.vmargs file.

Note:


Release Notes


EGM Database Memory Usage

When using Java 1.8, some countries can produce runtime geocoding exceptions. The solution isto increase the memory available to the Enterprise Geocoding Module. To do this, adjust the –Xmxparameter in the java.vmargs file to a larger value. For example, setting the value of –Xmx to 2048mshould be sufficient. The location of the EGM java.vmargs file is PitneyBowes\Spectrum\server\modules\igeocode-global\. In the java.vmargs file, append thefollowing: -Xmx2048m -Djava.util.Arrays.useLegacyMergeSort=true

SAP Module

Upgrading from Obsolete SAP Modules

If you are upgrading from the SAP ECC 5.0 version of the SAP Module, you must remove it beforeupgrading. This versions of the SAP Module is not supported in 10.0. When you upgrade to 10.0you can select a supported version of the SAPModule during the installation process. For instructionson removing modules, see the Spectrum™ Technology Platform Installation Guide.

Siebel Module

Upgrading from Obsolete Siebel Modules

If you are upgrading from one of the following versions of the Siebel Module, you must remove itbefore upgrading.

Siebel Enterprise 7.8Siebel Industry 7.8

These versions of Siebel are not supported in 10.0. When you upgrade to 10.0 you can select asupported version of the Siebel Module during the installation process. For instructions on removingmodules, see the Spectrum™ Technology Platform Installation Guide.


Release Notes


Validate Address Not Supported on Solaris

The Universal Addressing Module component Validate Address is not supported on Solaris 10 orSolaris 11 at the time of the release of 10.0 SP1. We will be releasing a product update to restoresupport for Validate Address on Solaris 10 and 11 after the release of 10.0 SP1. If you use ValidateAddress, wait until the product update is available before installing 10.0 SP1.

Root Access Changes

Root access for Unix/Linux is only required if you are installing the Universal Addressing Module.If you do not install the Universal Address Module, root access is no longer required.

RDI Database Update

If you are upgrading from a release prior to 8.0 and use the Universal Addressing Module to performresidential delivery indicator (RDI) processing, you must re-install the RDI database using thedatabase installer included with this release. RDI processing will not work unless you re-install theRDI database. For instructions on installing the RDI database, see the Spectrum™ TechnologyPlatform Installation Guide.

Universal Addressing Module Root Access Requirement

Root access is required to install the Universal Addressing Module.

Fixed Issues

Address Now Module

• (CDQE-20845) Various address validation errors in Hong Kong, UAE, Israel, and Indonesia.• (CDQE-20767) Various issues with Get Global Candidate Addresses.• (CDQE-19150) For an address in Ilhable, Brazil, the ACR code indicates that the state was addedbut it was not.

• (CDQE-19115) Get Global Candidate Addresses returns a different result for a Canadian addressin postal code H3G1T4 than what is returned by Canada Post.

• (CDQE-16234) Subcity "Artane" in Dublin, Ireland is not recognized.


Release Notes

• (CDQE-9751) Different results when mixed casing is enabled.

Business Steward Module

• (CDQE-37162) When running in the French locale, job fails if the Exception Monitor stage containsAND or OR logic.

• (CDQE-28245) The Business Steward Portal does not work over SSL.


• (CDQE-36527) Group statement does not display when the Add Group button is clicked to addcriteria to a second metaview table on the canvas.

Data Normalization Module

• (CDQE-37237) Unable to load CSV data into a table using Table Management.

Documentation

• (CDQE-16562) Using Java 1.7 with some countries can produce runtime exceptions whengeocoding specific addresses. The solution is to append the following -Xmx setting to the Javasystem property file (java.vmargs) located at PitneyBowes\Spectrum\server\modules\igeocode-global\. That is, specify -Xmx2048m-Djava.util.Arrays.useLegacyMergeSort=true.

This issue was noted in the Spectrum 9.0 S03 Patch Release Notes, but was omitted from the10.0 documentation and release notes. This has been corrected.

Enterprise Data Integration Module

• (CDQE-40003) Reopening a SQL statement in the SQL query editor takes a long time.• (CDQE-39887) Process flow and Execute SQL stage duplicates SQL inserts numerous times.• (CDQE-39425) Call Stored Procedure stage doesn't return columns of Decimal data type.• (CDQE-37558) Error: "Unable to create a SQL".• (CDQE-37538) Read from DB dataflow option "whereclause" is not used when job is executed.


Release Notes

• (CDQE-37283) After changing a view in a database, the error "Index was outside the bounds ofthe array" appears when opening Read from DB.

• (CDQE-34898) Read from File error when reading a text file containing a form feed character.


•• (CDQE-34464) Country Identifier returns "Suecia" as Switzerland instead of Sweden.• (CDQE-7029) A null value in a tab file causes Canadian addresses to fail geocoding.• (CDQE-9740) Corrected an issue in Enterprise Geocoding Module-US where setting the MustMatch Postal Code setting was not being honored when processing in Custom match mode.

• (CENTRUS-8253) Fixed an issue in Enterprise Geocoding Module-US where the city short namedid not match the output city name when the Find Correct Lastline and Street Centroid optionswere set.

• (CENTRUS-9529) Fixed a problem in Enterprise Geocoding Module-US where an excessivelylarge input string in single line entry caused the software to crash.

• (CENTRUS-9562) Fixed a problem in Enterprise Geocoding Module-US where entering a largenumeric character string (greater than 18 numbers) in the input address resulted in the return ofspecial characters in Address Line 1.

• (CENTRUS-9578) Corrected an issue in Enterprise Geocoding Module-US where the Find FirstLetter Expanded and Find Street Centroid options are enabled, and a street segment was found;however, the matching process continued and returned additional, less accurate results.

• (CENTRUS-9796) Corrected an issue in EnterpriseGeocodingModule-US to improve the placementof interpolated address points in cases where the points are located on curved roads.

• (CENTRUS-9800) Fixed an issue in Enterprise Geocoding Module-US to ensure an interpolatedaddress point candidate returns the correct ZIP Code for the matched Finance area.

• (CENTRUS-9802) Corrected an issue in Enterprise Geocoding Module-US to use exact addresspoint interpolation of points that are located in parcels that are aligned orthogonally to the street.

• (CENTRUS-9803) Fixed an issue in Enterprise Geocoding Module-US to improve the return ofan interpolated address point when N-N house numbers, box or lot numbers are specified in theinput address.


• (ROUT-2314) JSON response was not being returned for Invalid or Empty ambient speed valuesfor the REST GetTravelBoundary service.

• (ROUT-2602) Incorrect exception message was displayed when invalid database name wasprovided in REST URL.


Release Notes

• (ROUT-2730) When using the Shortest or Fastest search criteria in the Find Nearest stage, resultswere not returned. The Enterprise Routing Module threw an error:java.lang.IlligalArgumentException: Invalid formatString: null.

• (ROUT-2960) For the GetRoute REST service, the overall distance and time values are returnedas numbers. However, the distance and time values in the direction segments were being returnedas strings. The distance and time values in the direction segments are now returned as numbers.

Enterprise Geocomplete Module

• (GMF-1368). All coutries now display database vintage information from the dictionarydesc file.Previously, several countries (including France, Spain, Mexico, Sweden, and Singapore) did notreport this vintage information.


• (GEOTAX-1560) Corrected an issue with the casing not working on the County name on matchesto the GeoTAX Auxiliary file.

• (GEOTAX-1567) Fixed a problem with the input address not passing through if the data failed tomatch.

• (GEOTAX-1577) Added a missing geotax.h file which was creating a runtime error on the Solarisplatform.

• (GEOTAX-1584) Added a missing geotax.h file which was creating a runtime error on the UNIXplatform.

• (GEOTAX-1593) When using a GeoTAX Auxiliary file, the latitude/longitude coordinates, whenavailable, are now being used.

• (SCS-2879) The Enterprise Tax Module documentation for database compatibility omitted themajor version for service pack SP2. The major version "9.0" has been added.


• (MID-24947 / SSP-266) Parsing of MapBasic styles is now the same as it is in MapInfo Pro.• (MID-24677 / SSP-258) An error no longer occurs when creating a named table in Spatial Managerusing a shapefile for which a coordinate system is not defined in its .prj file.

• (MID-23923) Spectrum Spatial now displays legends for Individual Value and Ranged themes forpoints and lines that align with the behavior in MapInfo Professional. This involved a change forapplyStylePart="color" and applyStylePart="size" as follows:

• applyStylePart="color" now displays a colored rectangle regardless of the style or geometry typefor the theme.


Release Notes

• applyStylePart="size" now displays a black circle of varying size for points and a black line withvarying width for lines.

• There is no legend for themes on polygons.• There is no change in behavior for applyStylePart="all"

• (MID-23877)When querying an Oracle database with a long identifier (greater than 30 characters)Spectrum Spatial now generates a temporary alias and reverts back to the original user-specifiedalias once the query has been executed on the database side. Previously it threw an exception.

• (MID-23693) Generating tiles from seamless tables with labels no longer throws an exception.• (MID-23453) UTF-8 characters are now displayed properly for named resources and configurationfiles that were added to the repository via WebDAV.

• (MID-23267/MID-23646) The applyStylePart attribute for Individual Value themes and Rangethemes now correctly renders a map with the style from the feature in the table and the color orsize from the theme. This applies to point, area, line and text object styles. This behavior alignswith MapInfo Pro.

• (MID-23205) Modified MapBasicStyleConvertor to support an expression like "Brush(...) Pen(...)• (MID-23204) Map Uploader now correctly writes out the schema attribute as lowercase 'owner'for Oracle tables.

• (MID-23117) The SearchReferencedIn operation in the Named Resource Service was not returningthe full set of resources when the resource name included stop-words (e.g., and, or, ...).

• (MID-23072) The maximum HTTP message size for Map Uploader has been increased. Theprevious default value was exceeded if there were about 500 named resources or more in onefolders.

• (MID-22995) The .NET sample app failures are now fixed.• (MID-22991) Content searching using the Named Resource Service or Spatial Manager now worksproperly on the AIX operating system.

• (MID-22988) Spectrum Spatial now renders layers on a map that have the same alias.• (MID-22876) When choosing the repository path using Map Uploader, the tree view now showsempty folders in the repository.

• (MID-22644) When deleting folders in Spatial Manager, an error message no longer appears thatincorrectly indicates resources will break which are in that folder.

• (MID-22580) Previously, you were erroneously allowed to perform an ORDER BY or GROUP BYoperation on a raster, geometry, style, or binary column. Enterprise Designer and the FeatureService now alert you that these columns are invalid for these operations.

• (MID-22362) In Spatial Manager, incorrect error messages no longer appear on the table and mapdetail pages when the underlying database table is dropped.

• (MID-22225) Spatial Manager no longer allows you tomodify unknown or unsupported datasources.• (MID-21870 / SCS-2495) Spatial Manager now allows only numeric datatypes for the X and Ycolumns when creating an XY named table.

• (MID-20976) Spectrum Spatial has beenmodified to resolve an issue displaying a legend. Multipleline styles displayed in the legend even though they had not been specified in the map.

• (MID-20460) Named connections that contain a backslash (\) in the JDBCURL are now supported.This is in support of an optional \instanceName connection parameter for MS SQL Server.


Release Notes

• (MID-20325) For the Write Spatial Stage in the Enterprise Designer, an error is now reported inthe client (not just the server) if an attempt is made to load a named table fails at the server side.

• (MID-17965) The accuracy of a large distance FindNearest search and DistanceSearch has beenimproved.

Server

• (CDQE-39118) Process flows execute the latest saved version of a job instead of the exposedversion.


• (CDQE-35854) Validate Address Loqate issues with processing addresses on roads in Bangkoknamed Sukhumvit.

• (CDQE-35717) Validate Address fails when validating an address in Trinidad and Tobago.• (CDQE-34012) Get City State Province returns an invalid address for Canadian postal codeT0J2J0.

• (CDQE-31084) Get Candidate Addresses Loqate fails to return candidates for an address in ZIPCode 22033.

• (CDQE-32161) Get City State Province does not return a city for Canadian postal code T7X3B3.• (CDQE-28555) Auto Complete Loqate does not return all the expected addresses for the inputAddressLine1=140 10 and Country=CA.

• (CDQE-28303) Validate Address Loqate validates certain Canadian addresses that should not bevalidated.

• (CDQE-27698) Validate Address Loqate corrects address to an invalid address.• (CDQE-27352) Address in Pittsburgh, PA matches to the wrong street.• (CDQE-26613) An address in the city Saint Paul, AB does not validate but when used with thecity name St. Paul, AB it does.

• (CDQE-25823) In some situations Validate Address Global changes the house number inAddressLine1 to an incorrect house number.

• (CDQE-24789) Address displays multiple matches but no distinctions are observed.• (CDQE-23326) Language in Validate Address Global does not match the input language.• (CDQE-23323) Address in Bladenboro, NC is valid but fails to validate.• (CDQE-22482) When "TOWER" is abbreviated to "TWR", an address in Atlantic City, NJ returnsDPV=M.

• (CDQE-21788) Address in Empire, MI cannot be validated.• (CDQE-19128) MONT is recognized as an abbreviation for Montana.• (CDQE-19114) Improper normalization of state road keywords for address in Ferrum, VA.


Release Notes

• (CDQE-19109) Validate Address does not searching with the ZIP Code for an exact match on thestreet for an address in Mattapan, MA.

• (CDQE-18268) The Cancel button is not displayed in an error message regarding Loqate databaseinstallation and the installation process cannot be ended by clicking OK. If the user indicates thatdata from multiple discs is being installed but actually only data from one disc is installed, an errormessage appears asking the user to insert the a second disc. For example, if the user accidentallyindicates that he is installing data for Europe and Australia/Pacific but he only owns/has the discfor Europe, the user will receive an error message requesting the Australia and Pacific disc.Pressing OK will not close this error message and the user needs to end the process in theWindows Task Manager.

This issue occurs only on Windows platforms.Note:

• (CDQE-16223) Validate Address Global does not return the street prefix.• (CDQE-16221) Validate Address Global does not maintain spelled out street names in Brazil.• (CDQE-14665) Address line returned on output even if it contains garbage.• (CDQE-12666) An address in Washington DC fails when SuiteLink is enabled.• (CDQE-11628) Validate Address does not return all candidates for an address in Port Washington,NY.

• (CDQE-10809) End of File exception after approximately 6,000 records.• (CDQE-10298) Apartment number being dropped for address in Tacoma, WA.• (CDQE-9350) An address in Laval, PQ does not return the correct casing for the provinceabbreviation.

• (CDQE-8152) The Status.Description field does not reflect an EWS match if DPV is enabled.• (CDQE-8139) Multiple matches not returned for address in Bayamon, PR.• (CDQE-7455) Apartment information issue.• (CDQE-4179/00006048) Abbreviated alias option returns alias when enabled, and does not returnalias when enabled.

• (CDQE-503/CR 1-31958200) Apartment number coding incorrectly for address in Tacoma, WA.• (CDQE-477/SR 1-31926276) For an address in Davis, CA, the apartment information is droppedwhen placed in AddressLine2.

Known Issues

This release contains the following known issues.

Address Now Module

• (CDQE-20899) Missing subcity and Jeddah issue.


Release Notes

• (CDQE-15728) Normalized address line keeps growing when output address is used as input.• (CDQE-13760) Addresses in South Korea are not validated correctly.• (CDQE-12471) Validate Global Address parsing logic does not work correctly in cases whereAddressLine1 contains apartment information.

• (CDQE-2103/CR 1-32277242) The "home country" option does not allow Japan2 or Japan3.

Advanced Matching Module

• (CDQE-33494) Table loader crashes on Windows Server 2012.• (CDQE-33395) Candidate Finder does not work with a French index.• (CDQE-31843) Multiple entries getting stored in the search index for the same key field.• (CDQE-31622) Error when upgrading the Advanced Matching Module.


• (CDQE-39710) Column names containing an underscore produce an error.

Data Normalization Module

• (CDQE-32463) In the Table Management tool in Enterprise Designer, if you click New to createa new user-defined table and copy from an existing table, the table fails to standardize terms.

• (CDQE-28304) Open Name Parser does not display custom domains.• (CDQE-21062) Slow performance with Name Parser and user-defined table.• (CDQE-3939) When a culture-specific grammar is used, all of the culture's RegEx rules areappended to the end of the grammar, whether they are used or not.

Enterprise Data Integration Module

• (CDQE-30855) The following error occurs when trying to update a Postgres table: error 42703.• (CDQE-3925) Read from DB, Write to DB, and Query DB allows duplicate alternate field namesto be saved despite error message.


Release Notes

Enterprise Designer

• (CDQE-28244) Unable to edit an expression in Conditional Router if the expression was createdin a different locale.


• (CDQE-22813) Address in Chico, TX returns point level geocode even though the ZIP Code isinvalid.

• (CDQE-20550) Custom match criteria settings are lost in Geocode US Address.• (CDQE-19872) Various locations in the United States not geocoding at the street level.• (CDQE-19615) For an address in postal code 72211, the apartment number information is switchedin the output.

• (CDQE-19591) Specific addresses in MO, IL, MN, and IA do not geocode.• (CDQE-19513) 34 locations in the U.S. are not geocoding to the street level.• (CDQE-19152) Incorrect coordinates returned for an address in Cresco, PA.• (CDQE-15656) Confusing error messages when installing a database over an existing database.• (CDQE-14247) Intermittent problems with Geocode US Address in a multi-threaded environment.• (CDQE-13901) Geocode Address GBR returns latitude/longitude in scientific notation.• (CDQE-13575) GeocodeUSAddress cannot geocode some addresses verified by Validate AddressGlobal.

• (CDQE-12610) Addresses in Argentina that are validated by Validate Address Global cannot begeocoded.

• (CDQE-11721) Hyphenated street names cause multiple matches.• (CDQE-11720) S4 addresses returned as multiple matches.• (CDQE-11678) For Geocode US Address, unable to set ZIP or geographic centroid fallback inCASS mode.

• (CDQE-11137) Duplicate ranges in French data cause multiple matches.• (CDQE-11123) Close matches returned containing different postal codes.• (CDQE-9823) Spanish geocoding issue for city Laudio-Llodio.• (CDQE-8700) Segment ID field is not long enough for MultiNet values.• (CDQE-7602) Address in Sweden geocodes to postal centroid instead of a street.• (CDQE-7136) Inconsistent city/state handling for locations in Australia.• (CDQE-6913) House numbers for some French addresses unexpectedly change on output.• (CDQE-6912) Some German addresses fail to match to known house numbers.• (CDQE-6881) The Brazil geocoder becomes unresponsive on Solaris 10. If you experience thisissue, set the number of runtime instances to 1.

• (CDQE-6664) Portugal geocoder throws error during initialization.• (CDQE-4927) Multiple matches are not returned for E030 match code.


Release Notes

• (CDQE-4744) Geocode US Address returns error: "Service problem. Method setData() failed."• (CDQE-4278) Street name for a Washington D.C. street address is not recognized when theaddress elements are in the incorrect order.

• (CDQE-2865) The match code is not consistent with DPV footnotes for an address in Chico, CA.• (EGMI-875) Spain geocoder does not retain the "First two postal code digits" setting when Spectrumis stopped and restarted.

• (EGMI-874) Close match criteria label is missing in Management Console Matching tab.• (EGMI-797) Spectrum and database installation scripts do not run with Korn Shell.• (EGMI-754) In Management Console, when all items are expanded in the left panel, some optionsare cut off at the bottom of the page.

• (EGMI-740) Null Reference Object Exception when Maximum Range and Maximum Range Unitsare set to 1.

• (EGMI-732) The database loader does not accurately report an error when it fails to extract themedia correctly on the disk.

Enterprise GeoComplete Module

• (GMF-1262) No output is returned when a database is specified in lower case as part of a SOAPrequest. This should not be case sensitive.

• (GMF-1351) If search distance is specified as a decimal value, the distance is not honored. Forexample, if you restrict the search distance to 1.5 kilometers, this distance is ignored.

• (GMF-1380) For geocoders that include more than one country, the correct country code is notalways returned. For example a Vatican (VAT) address returns with the country code for Italy(ITA).

• (GMF-1475) When you re-run the database loader, you may get an error message and instructionsto "see the installation log for details." This message appears because data already exists in thetarget folder. For example, if you loaded the GeoComplete Americas bundle and then re-run thedatabase loader for the EMEA bundle, you will see this message even if the database load wassuccessful.

For each country, street, POI, and user dictionaries (if any) must have unique names andbe in the same folder. If a country supports multiple languages, the language-specificdictionaries must also be in the same parent folder. .

Note:


• Preview Tab in Management Console for Get Route Data and Persistent Updates is visible,however not functional at this time.

• Multi-Lingual support for Get Route Data is not available in this release.• (ROUT-2983) The Routing .NET sample downloaded from the landing page does not compile.


Release Notes

• (ROUT-2601) The ReturnRouteGeometry checkbox in Management Console and EnterpriseDesigner is selected by default for all locales except English.

• (ROUT-1280) While adding a routing database resource in the Management Console, the foldersize shows zero (0) bytes.

• (ROUT-421) Exception is thrown by Management Console preview if you are returning geometryobjects.


• (CDQE-71) Addresses cause "connection reset" error message.


• (CDQE-41175) There is a product update available for the Map Tiling service that fixes aperformance issue with third party cache systems such as Squid. Contact support for more details.

• (MID-25745/SCS-3126) The Feature Service does not correctly insert or update a feature'sMapBasic attribute for polygon styles into a database table.

• (MID-25619) One of the sample view tables (/Samples/NamedTables/USAViewTable) rendersbut does not validate when modifying the datasource in Spatial Manager.

• (MID-25568) The CSW and Library Services have been removed from this release of SpectrumSpatial. However, after an upgrade you will still find a /Library folder, which has been kept in caseyou had added other named resources to that folder. If it is empty, you can simply delete it inSpatial Manager or via WebDAV.

• (MID-25467) Spectrum Spatial is unable to access MRR files that contain Unicode characters inthe file names.

• (MID-24998) Anti-aliasing feature where rendering is set to quality is not supported in MRR.• (MID-24948) MI_Buffer throws exception when Computation type is incorrect for the coordinatesystem. This is a change from previous releases to align with the behavior in MapInfo Pro.

• (MID-24834) A Feature Service SearchBySQL request fails when integer input is specified for afloat column in PostgreSQL 9.3.

• (MID-24698) Mapping and Feature services are failing with large TIFF files. File size limit is 2 GB.• (MID-24686) Spectrum Spatial is unable to execute queries against an Oracle table when thetable name is in lower case.

• (MID-24668/MID-24083) Mapping Service Describe Named Layer throws an exception for GRIDlayers with override themes that use a composite GridStyle. This is encountered in both SOAPand REST.

• (MID-23901) A map with two themes created in MapInfo Pro and rendered in Spectrum Spatialdoes not match the same map rendered in MapInfo Pro.

• (MID-23679) A table from SQL Server 2012 with a null value in its geometry column throws anexception. This does not occur with same table in SQL Server 2008.


Release Notes

• (MID-23544) Upgrade installer overwrites Created/Modified dates of named resources. .• (MID-23381) In the Find Nearest stage, MaxDistance behaves inconsistently on tables fromdifferent data sources. Oracle searches all datasets and returns the nearest candidates. However,others will only return the intersected candidates (similar to searchAtPoint). In the Feature ServiceAPI the MaxDistance is optional; however, in the Find Nearest stage, MaxDistance is mandatoryand its default is 0.

• (MID-22772) Spatial Manager is sometimes unresponsive or slow when searching or navigatingto another page after creating a named connection if you have a large repository.

• (MID-22552) Spatial Manager throws an unclear error, such as "Login failed for user 'MIDEV'.ClientConnectionId:5773bc7e-849e-4e25-b886-ed83abe6afc7," on the detail pages when youhave the wrong password for a SQL Server named connection.

• (MID-22494) Named tables cannot be created from tables containing DateTimeOffset data.• (MID-22218) When you change the volatile attribute to "false" for a new named table, it referencesthe table cache of an existing named table if it also has a volatile attribute of "false" and points tothe same database table. Any changes to the database table structure are therefore not reflectedin the new named table. The cache must be refreshed by restarting the server.

• (MID-22176) In Enterprise Designer, reselecting a named table in the Write Spatial Data stageafter making changes to its underlying database table does not display the updated version of thetable. The workaround is to select a different named table and load it, then select the desirednamed table to see the most recent version.

• (MID-22175) Spectrum Spatial should throw an exception if you do not specify aFeatureGeometryAttribute when rendering a custom style column. You must specify both theFeatureGeometryAttribute and FeatureStyleAttribute under the DBDataSourceMetadata attribute.

• (MID-21250) The interactive map feature in Spatial Manager makes incorrect map tile requestswhen underlying map is a raster with an affine rotation.

• (MID-21248) A named map does not render properly when it contains a raster with an affinerotation.

• (MID-20782)When using the REST services, there are cases in which JSON is returned regardlessof the representation you specified (such as xml).

• (MID-20621) In User Management Service, Invoke method is not working properly to reload theconfiguration settings.

• (MID-20212) Multipolygon in SOAP request is getting interpreted as Polygon with hole• (MID-20059) Spectrum Spatial is not handling Boolean columns properly for MS SQL Server andPostGIS data sources. To work around this issue, change the column type to tinyint and set false= 0 and true=1.

• (MID-19747) MISQL: Exception is thrown when using an aliased attribute in a function with anOrder By clause.

• (MID-19745) MISQL: Exception should be thrown when using an aggregation function in a querywith an Order By clause.

• (MID-18776) Self Join Query does not work in case of Oracle, SQL Server and PostGIS.• (MID-18362) Some Mapping Service demo page requests are not working on AIX 7.1.• (MID-17813 / SSP-174) Issue with heat map legends. Legends should not be returned whenrendering a Grid Layer with an inline view that is returning no data.


Release Notes

• (MID-17674) In Spatial Manager, if the Spectrum license has expired a 500 error code appearsinstead of an expiration message.

• (MID-17419) Order By in Search Nearest Edge is not working for columns other than Distance. Ifyou remove the distance attribute then the sorting works.

• (MID-17041) Updates to a style are not reflected in the rendered image.• (MID-17037) FeatureGeometry.getRepresentativePoint() throws null pointer exception.• (MID-16831) The locale param on the getLegend REST request does not work as expected andhas been removed from the documentation.

• (MID-15612) Error messages and strings are not localized for JavaScript samples.• (MID-12714) In the Query Spatial Data Stage, the MISQL picker lists the same function multipletimes, once for each supported data type.

Server

• (CDQE-39914) After upgrading to 10.0 SP1, one or more modules may not be available after theserver starts up. The following errors appear in the wrapper log:

WARN [ProductScheduleManagerFactory] ProductScheduleManager alreadyexists for productName=Product NameERROR [ScanDirectoryHandler] Unable to deploy file [Car File]...Caused by: java.lang.IllegalArgumentException: Named classloader [ProductName] already registered

The cause of this issue is that the old version of the module's .car and .console files are inthe server's deploy folder. To fix this, issue:

1. Stop the server.2. Delete the old version of the module's .car and .console files in this folder:

Spectrum Location/server/app/deploy

3. Start the server.

• (CDQE-33945) Spectrum server icon in the Windows task bar shows started before the server isfinished starting up.

• (CDQE-24160) Process flow executor fails when the -r argument is the last argument specified.To work around this issue, do not specify the -r argument last.


• (CDQE-39968) Address in Toronto, ON not validated correctly.• (CDQE-39932) Suite information not placed in address line 1 for an address in Toronto, ON.


Release Notes

• (CDQE-39906) A valid address in Mt. Airy, MD and one in Cambridge, MA are not beingstandardized by Validate Address.

• (CDQE-39895) House number for an address in Dublin, Ireland is different than the one returnedby the Enterprise Geocoding Module.

• (CDQE-39808) Various issues with several Canadian addresses.• (CDQE-39764) Validate Address Loqate corrects an address with a blank address line.• (CDQE-39763) Validate Address Global validates certain addresses that are invalid and produces"EOFException" error.

• (CDQE-39712) Address 18B Yonge St, Toronto, ON is validated with incorrect postal code.• (CDQE-39279) Validate Address is not correcting misspelled street names.• (CDQE-39042) Street name in French address not returned.• (CDQE-38912) Validate Address drops apartment number from certain addresses.• (CDQE-38907) Address information for an address in Nice, France is missing.• (CDQE-38713) French address is missing the article from the street name.• (CDQE-38703) Incorrect apartment number for addressin White Plains, NY.• (CDQE-38702) Incorrect county for address in Winston Salem, NC.• (CDQE-38660) Incorrect house number for address in Fay en Bretagne.• (CDQE-38478) In a French address, the street suffix is changed and no reason is given in theresult code.

• (CDQE-38464) For French address, the street suffix changes depending on whether HouseNumberis specified.

• (CDQE-38436) French addresses with ET in the address are not validated.• (CDQE-38435) Incorrect value for house number for a French address.• (CDQE-38268) Incorrect HEVAVIA and HEXACLE number for French address.• (CDQE-37869) Addresses not validated when the dual address logic search option is set to POBox.

• (CDQE-37836) Multiple addresses should be returned for specific addresses in New York but arenot.

• (CDQE-37632) Valid address in East Hampton, NY is changed even though the address is valid.• (CDQE-37537) PO Box address in New Rochelle, NY is not being marked as a PO Box address.• (CDQE-37168) Umlauts and accents are missing from addresses in Quebec.• (CDQE-37165) DPV returns "Missing secondary address" when validating an address in Shelby,NC.

• (CDQE-36977) Fast completion is not returning AddressLine1 information for addresses in certainpostal codes in Germany and South Africa.

• (CDQE-36924) Unexpected address validation results for address in Lincoln, NE and Oakville,ON.

• (CDQE-36923) Various issues with four Canadian addresses.• (CDQE-36783) Unit number with # symbol is not recognized for an address in Missisauga, ON.• (CDQE-36608) Validate Address Loqate matching address elements to ApartmentNumber andApartmentNumber2.

• (CDQE-36558) Fast complete returns a range instead of a specific house number.


Release Notes

• (CDQE-36410) The letter "N" appended to house number.• (CDQE-36389) Unexpected changes to certain validated addresses in the UK.• (CDQE-36009) Validate Address does not handle accent characters in a French address properly.• (CDQE-35855) Unable to validate an address in Lafayette, LA.• (CDQE-35760) Incorrect CASS coding of specific addresses in Clarkston, GA, San Jose, CA, SimiValley, CA, an dBoonville, IN.

• (CDQE-35723) Validate Address produces different results on different runs.• (CDQE-35697) Miscellaneous differences in address validation compared to older version.• (CDQE-35474) Invalid address with Canadian postal code returned with 100% confidence.• (CDQE-35386) Address in Porquis Junction, ON has incorrect spacing and punctuation whenoutput is set to mixed case.

• (CDQE-34513) Get Candidate Addresses returns an error for an address in Nicaragua.• (CDQE-34456) Addresses in Colorado Springs, CO return unexpected value inLeadingDirectional.Result and TrailingDirectional.Result.

• (CDQE-33906) Certain addresses in Vermont are not being validated even though they are valid.• (CDQE-33517) The following error message appears when running certain Canadian postal codesthrough Get City State Province: "The server reported that the service ran successfully even thoughno output data was returned".

• (CDQE-32822) The street suffix is not standardized for Canadian addresses.• (CDQE-31863) Unable to validate an address on Mont Belvieu, TX and Okotoks, AB.• (CDQE-31722) Get Candidate Addresses web service request does not return multiple results.• (CDQE-31507) For an address in Vancouver, BC, the apartment number is not being returned inthe AddressLine2 field.

• (CDQE-31501) An address in Toronto, ON does not validate with unit number added.• (CDQE-31484) Validate Address does not always include the accent mark in the city nameOrléans.• (CDQE-31350) Address in New York, NY returns conflicting DPV information.• (CDQE-31025) Fast completion does not work with postal code for Dublin, Ireland.• (CDQE-30015) Validate Address Global is not returning the locality in Kanji when the databaseoption is selected for output with two Japanese records.

• (CDQE-29859) A particular SOAP request to Validate Address takes a long time to process.• (CDQE-29359) Get Candidate Addresses does not format French addresses correctly. It placesthe word "rue" at the end of the street name instead of the beginning.

• (CDQE-29291) Validate Address does not place apartment information in Address Line 2 whenconfigured to do so.

• (CDQE-29021) Get Candidate Addresses does not return all the addresses for Canadian postalcode L0E 1E0.

• (CDQE-28984) Validate Address does not recognize the city North York, ON.• (CDQE-27848) Extra carriage return added to end of record.• (CDQE-27686) Two addresses in Miami, FL are not standardized correctly.• (CDQE-27588) Validate Address does not return expected results for specific addresses in Florida,New York, and New Jersey that return multiple matches.

• (CDQE-26777) CASS detail reports 2 and 3 do not work when the output format is text.


Release Notes

• (CDQE-27361) Address returns unexpected results in the City.Result and StatProvince.Resultfields.

• (CDQE-27149) Validate Address incorrectly capitalizes "LA" in the city name La Crosse.• (CDQE-26630) Address validated with a confidence score of 100 but contains blank address fields.• (CDQE-25154) Validate Address Loqate does not return multiple matches for certain addressesthat should have multiple matches.

• (CDQE-24863) Some addresses validated by Validate Address Global cannot be geocoded whenthe records are in English/Latin.

• (CDQE-24506) Validate Address returns multiple matches found for an address in Painsville, OH.• (CDQE-24221) Addresses in British Columbia do not validate when hyphen is in the buildingnumber or "th" is included in the street name (as in 148th Street).

• (CDQE-24030) Address in Puerto Rico fails to validate.• (CDQE-22151) Valid address in Wellington, FL is not recognized as valid.• (CDQE-22060) Addresses without street numbers do not return StreetName.Result.• (CDQE-21909) Address "1 AT&T Way" is not validated.• (CDQE-21657) Error with AddressLine1 and urbanization code mismatch.• (CDQE-21608) Ampersand in Pakistan state name "Fca & Ajk" causes problem in SQL.• (CDQE-21418) Apartment and suite information missing when suite is specified as "STE 101"instead of "ste 101" or "Ste 101".

• (CDQE-20581) For an address in Lorraine, France, AddressLine1 data is returned in AddressLine3.• (CDQE-20085) For address in Mississauga, ON, when "VLLY" is used instead of "Valley" theaddress does not validate.

• (CDQE-20044) Address in Myrtle Beach, SC returns a "C" street name result code even thoughthe input address is exactly correct.

• (CDQE-19110) Address in Brookfield, WI not properly validated when the suite number is enteredin AddressLine1.

• (CDQE-18944) City alias not recognized for address in Toronto, ON.• (CDQE-15538) Get Candidate Address returns a city name with incorrect accent character.• (CDQE-14403) Firm name extraction moves apartment information.• (CDQE-12659) Non-address data not included in AdditionalInputData.• (CDQE-12653) Apartment information is missed when there is additional information inAddressLine2.

• (CDQE-12467) Validate Address returns incorrect results when multiple matches are expected.• (CDQE-12375) For an address in Washington, DC, address fragments appearing inAdditionalInputData output field.

• (CDQE-11850) Validate Address does not return a confidence score of 100 for an input addressthat is not changed during validate.

• (CDQE-11095) Validate Address returns improper directional results when matching base andreturning alias and vice versa.

• (CDQE-10973) No data returned in AddressLine1 field.• (CDQE-10775) Address in Lisbon, ME is DPV confirmed even though the secondary addressinformation is invalid.


Release Notes

• (CDQE-10718) For an address in the ZIP Code 34289 the unit number is not being returned.• (CDQE-10680) Unable to validate a numeric street name in Calgary, AB.• (CDQE-10546) Asterisk in AddressLine1 field fails to return address when specified with a postalcode that contains one unique address.

• (CDQE-10540) Specific addresses in Indio, CA, Apple Valley, CA, Gardenerville, NV, and MillValley, CA cannot be validated.

• (CDQE-9762) Address in Dallas, TX is returning a value of "V" in the StateProvince.result fieldeven though no state was provided on input.

• (CDQE-9682/00334806) Unable to validate address in Elmwood Park, NJ that contains a hyphenin the house number.

• (CDQE-9374/00280948) Congressional district not being returned for address in Montana.• (CDQE-8438) Validate Address is not returning the ISO country name for Lao People's DemocraticRepublic and Côte d'Ivoire.

• (CDQE-7676) For an address in Colorado Springs, CO, the LeadingDirectional.Result field containsa "C" for an address where neither the input nor the output contains a leading directional element.

• (CDQE-7654/00303170) For addresses that are LACS/Link converted, the output fields xxxx.Inputcontain the corrected address instead of the input address.

• (CDQE-7583/00297285) Dropped address information not being returned in AdditionalInputDatafield when using LACS/Link conversion.

• (CDQE-7311) Address in Phoenix without the state specified returns a state result code of "V"instead of "A".

• (CDQE-3150/CR 1-32540113) Address on S Doheny Dr, Los Angeles, CA, is incorrectly matchedto ZIP Code 90089-0001.

• (CDQE-2281/CR 1-30019270) A unique ZIP Code logic problem exists when no city is provided.• (CDQE-2274/CR 1-15518343) "Lamar Blvd." in Austin, TX, incorrectly codes to "LaMar".• (CDQE-2267/CR 1-17999195) With mixed casing enabled, cities such as "La Habra" are returnedas "LA Habra".

• (CDQE-2261/CR 1-28475181) A PO Box address in Sweeny, TX, does not code.

Memory Access Violation When Installing Databases

When installing the Universal Addressing Module's U.S. Postal Database on Windows or Linux youmay encounter an error similar to the following:

Memory access violation.COBOL error at 000000 in <path>\G1DBLOAD.acu

This issue is caused by a limitation in a third-party software library.

There are two workarounds for Windows and one for Linux.

Windows Workaround 1: Modify DEP Settings

1. Go to Control Panel > System.2. Click the Advanced tab.


Release Notes

3. In the Performance area, click Settings.4. Click the Data Execution Prevention tab.5. Do one of the following:

• Select Turn on DEP for essential Windows Programs and services only.• Select Turn on DEP for all programs and services except those I select then click Add andadd wrun32.exe located in C:\Program Files\Common Files\Group1\Runtime. Youshould now see ACUCOBOL-GT 32-bit Runtime listed.

6. Click OK.

Windows Workaround 2: Set USE_EXECUTABLE _MEMORY

If you do not want to modify your DEP settings, you can instead set the system-level environmentvariable USE_EXECUTABLE_MEMORY to TRUE.

Linux Workaround

To work around this issue on Linux, update the kernel configuration to turn off the NX (No eXecute)bit:

1. Log in as root.2. Edit /boot/grub/grub.conf.3. Add noexec=off to all kernel option lines. For example:

title Red Hat Enterprise Linux AS (2.4.21-15.ELsmp)root (hd0,1)kernel /boot/vmlinuz-2.4.21-15.ELsmp ro root=LABEL=/ noexec=off initrd/boot/initrd-2.4.21-15.ELsmp.img

4. Reboot the system.

Universal Name Module

• (CDQE-37883) Open Parser table missing Spanish names Apostoles and Covadol.• (CDQE-36916) Open Name Parser fails to parse a conjoined name.• (CDQE-23803) User needs View permissions for Open Parser Domains and Open Parser Culturesto accessOpen Parser andOpenNameParser views inManagement Console, Enterprise Designer,and Interactive Driver.

• (CDQE-14657) The name JOHN D does not parse correctly.


Release Notes

Web Services

• (CDQE-24081) Services with a field named "length" fail to expose as SOAP and REST services.


Release Notes

3001 Summer Street

Stamford CT 06926-0700

USA

www.pitneybowes.com

© 2016 Pitney Bowes Software Inc.

All rights reserved