releasenotes - pitney bowes · spectrum™ technologyplatform version10.0 releasenotes...

61
Spectrum Technology Platform Version 10.0 Release Notes This document contains information about Spectrum Technology Platform 10.0. You have access only to the modules you have licensed. To evaluate any other modules, contact your Pitney Bowes account executive for a trial license key. Complete documentation can be found at support.pb.com/spectrum. Contents: What's New 2 System Requirements 24 Installation Notes 36 Fixed Issues 45 Known Issues 48

Upload: others

Post on 15-Mar-2020

26 views

Category:

Documents


0 download

TRANSCRIPT

Spectrum™ Technology PlatformVersion 10.0

Release NotesThis document contains information about Spectrum™

Technology Platform 10.0. You have access only to the modulesyou have licensed. To evaluate any other modules, contact yourPitney Bowes account executive for a trial license key.

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

Contents:

What's New 2System Requirements 24Installation Notes 36Fixed Issues 45Known Issues 48

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.2 to addressvarious security vulnerabilities.

Advanced Matching Module

New Stage—Private Match

The new Private Match stage enables two entities to compare datasets and identify common records,or customers, without compromising sensitive information. By using an encrypt function security isretained while a match function is performed, and then a decrypt function shows the output of thematched data.

Candidate Finder Search Query Count

Candidate Finder contains a new field called Return total match count that includes in the outputthe number of matches made.

Search Index Distributed Processing

Search indexes created with the Spectrum™ Technology Platform 10.0 API now support distributedprocessing, including sharding, replication, and searching.

Existing search indexes do not support distributed processing; to enable this feature, youmust recreate the search index using the Spectrum™ Technology Platform 10.0 API.

Note:

Search Index Error Port

Write to Search Index now includes an error port to capture records that were not added to thesearch index.

Search Index Templates

There are now four Write to Search Index templates:

2Spectrum™ Technology Platform 10.0 Release Notes

Release Notes

• AppendIndex—Shows a job where new data overwrites existing data, and any new data that didnot previously exist will be added to the index.

• CreateIndex—Shows a job where a new search index is created.• DeleteIndex—Shows a job where a field is deleted from a search index.• SearchIndex—Shows a job where Candidate Finder conducts an index search.

Business Steward Module

Security Overrides

In addition to creating secured entity types for the Business Steward Module, you can now alsocreate security entity overrides that specify restrictions for specific dataflows or even specific stages.These overrides supersede user- and role-based secured entity type settings in that they make thepermissions more restrictive.

Returning Grouped Exception Records

The Return all records in exception's group option in the Exception Monitor stage will no longerbe enabled if the input data does not contain a field called "CollectionNumber" or "CandidateGroup".

Data Federation Module

Introduction - Spectrum™ Data FederationA new module, Data Federation, has been added to the Spectrum™ Technology Platform. Themodule allows you to create an abstracted virtual data source providing unified access toheterogeneous data sources through a uniform user interface. Using the module, you can collatethe data from multiple data sources and organize it as a specific representation of your businessmodel.

The Spectrum™ Technology Platform is placed between one or more data sources and your ownapplication. It connects to the data sources and collates the data from them for access by yourapplication. Data Federation creates a federated view of this collated data, providing a unifiedbusiness-relevant view of the entire federated data.

Data Hub Module

Data Hub Browser

The new Data Hub Browser component of the Data Hub Module offers a discovery tool where youcan search the contents of a model by browsing the results of a natural-language inspired querybased on the model’s metadata.

3Spectrum™ Technology Platform 10.0 Release Notes

Release Notes

Write to Hub Error Port

Write to Hub now includes an error port to capture records that were not added to the model.

Literal Types

You can now select a literal type for source and target entities in the Merge Entities and DeleteEntities stages.

Audit Feature

The Audit feature enables you to view the activity that has taken place for a model. This featurereturns create, read, update, and delete event information for the model and its metadata. Thisinformation is located on the Model Audit Events tab found on the Manage button of the Modelribbon in the Relationship Analysis Client.

History Feature

The History feature in the Relationship Analysis Client provides detailed information about changesthat have been made to entities or relationships within a model. The history feature groups data byversion number, in reverse chronological order, and provides a date and time stamp for each version.It also provides the user name of the person who made the changes. Additionally, the History tabdisplays the following details about any given change:

• Operation—The action that took place: added, modified, or deleted. Note that if you delete anentity, it will be shown only if it is re-added to the model. However, if you delete relationships orproperties, those deletions will appear in the history.

• Type—The component that changed: property or relationship• Name—The name of what changed. For properties, this is the ID of the property that changed.For entities whose relationship changed, this is the source and target IDs plus the relationshipname.

• Value—The new value that was entered (if any)• Previous Value—The value prior to the change (if any)

Prior to using this feature, you must first enable auditing by editing the hub.properties filefound in <Spectrum Location>\server\modules\hub.

Note:

Metadata Index Type

You can now set property index types while adding entity types when creating amodel usingmetadatain the Relationship Analysis Client.

4Spectrum™ Technology Platform 10.0 Release Notes

Release Notes

Current Item

Current item functionality has been moved from the Selection Pane to the new Current Item pane,and a toggle button for the Current Item pane has been added to the Tools ribbon on the View tabof the Relationship Analysis Client.

Moving Relationships

Themoving relationships feature enables you to manually move relationships between entities. Thiscan be useful if you need to change the source or target entity for a given relationship.

Model Modifications Tab

The new Model Modifications Tab, found under Model Management in the Relationship AnalysisClient, contains the functionality for what was previously called "Model Algorithms" (now just"Algorithms"). It also contains the new Schema Changes tool.

Schema Changes

The new Schema Changes tool in the Relationship Analysis Client allows you to make certainchanges to elements of your entire model, such as deleting an entity type or modifying a propertyindex type.

Clear Models

You can use the new Clear function, found under Model Management in the Relationship AnalysisClient, to clear the contents of a model.

Copy Models

You can use the new Copy function, found under Model Management in the Relationship AnalysisClient, to copy a model under a new name.

Save As

You can now save a model under a new name using the Save As button on the Model ribbon of theHome tab of the Relationship Analysis Client.

Data Normalization Module

Configuring Stages at Runtime

You are now able to pass configuration for the following stages at runtime:

• Advanced Transformer

5Spectrum™ Technology Platform 10.0 Release Notes

Release Notes

• Open Parser• Table Lookup

Open Parser InputFields Command

Open Parser now accepts multiple input fields for domain-independent grammar via the InputFieldsHeader Section Command.

Enterprise Data Integration

Expression Builder of Conditional RouterThe Expression Builder of the Conditional Router stage now allows defining an expression containingnested expressions. These nested expressions can be grouped using the Any or All conditions, asrequired.

In previous versions, a multi-level expression was achieved by using multiple Conditional Routerstages, and configuring and linking them to achieve the desired combination.

Record Joiner Converts Incoming Datatypes to Left Port DatatypeThe Record Joiner stage now allows joins on records from multiple incoming channels of differentdatatypes to the datatype of the left port.

The stage allows you to mark one of the incoming channels as the left port. All other incomingchannels comprise the right join. The datatypes of the right port in the defined join are converted tothe datatype of the left port.

Any datatype conversion done on the data of any incoming channel is indicated by a blue indicatoron the converted incoming channel. If a field on which the join is defined is missing, a yellow indicatoron the particular incoming channel indicates the same.

New File Server - Google CloudThis release supports configuring Google Cloud as a file server.

You can now use a Google Cloud file server to create a connection to use the data as required.

New File Server - Sharepoint 2010This release supports configuring Sharepoint 2010 as a file server.

You can now use a Sharepoint 2010 file server to create a connection to use the data as required.

6Spectrum™ Technology Platform 10.0 Release Notes

Release Notes

Encryption feature in Amazon S3 Cloud file serverThe Amazon S3 cloud server provides the encryption feature in this release. The encryption featureallows you to opt to encrypt and decrypt the data either at the server side, or at the client side, orboth.

Certain JAR files are required in order to enable the encryption feature of an Amazon S3 Cloud fileserver. For more information, refer the Enterprise Data Integration Guide.

New Stage - Change Data CaptureThe new Change Data Capture stage allows you to include such columns of a table in a jobflow forwhich all column value changes are to be captured and saved.

Currently, this stage has been implemented for MS SQL servers.

New Stage - DB LoaderThe new DB Loader stage allows you to load data to databases configured in the Enterprise DataIntegration Module.

As of now, the below mentioned DB loaders are configured:

1. DB2 Loader2. Oracle Loader

Oracle Loader was supported in previous versions as well. It is can now be configured aspart of the DB Loader stage.

Note:

Fetch Size configuration in Read from DBThe fetch size is now available as an option that can be configured at runtime.

Field Rename support in Unique ID GeneratorIn the Unique ID Generator stage, the RecordID field can now be renamed appropriately

Enterprise Designer

Changes to Version Permissions

Dataflow and process flow version behavior has changed in this release as follows:

• If a user's role does not have the Modify permission for the Dataflows or Process Flows securedentity type, the user will only see the exposed version and the last saved version in the Versionspane in Enterprise Designer.

• In order to expose the latest saved version of a dataflow or process flow (the version that's alwaysat the top of the Versions pane in Enterprise Designer) the user's role must have the Modifypermission for the Dataflows or Process Flows secured entity type in addition to the Modifypermission for the Dataflows - Expose or Process Flows - Expose secured entity type. This is

7Spectrum™ Technology Platform 10.0 Release Notes

Release Notes

because the latest saved version must first be saved as a version before it can be exposed, whichrequires the Modify permission for the dataflow/process flow.

Enterprise Geocoding Module

Parsed Address Input

You can select an option to return the formatted input street address and each input address elementin a separate field. This feature can help you understand how the input address was parsed andidentify specific input elements that could not be geocoded. For example, a returnedHouseNumber.Input field could contain an invalid house number in your input address. By default,parsed address elements are not returned.

Data vintage must be 2014 Q4 or newer to get Parsed Address Input returns.Note:

In the Management Console Options Geocoding tab, check the Return Parsed Address check boxif you want the address input elements to be returned. You can enable or disable Parsed Addressreturns as the default behavior for all countries in the database bundle. You can also override thedefault behavior for individual countries in the database bundle.

Parsed Address Input elements are returned in separately labeled fields names with a .Inputextension. For example:

• FormattedInputStreet.Input• FormattedInputStreet.Input• City.Input• Country.Input• HouseNumber.Input• Locality.Input• PostalCode.Base.Input• StreetName.Input• StreetSuffix.Input

Other labeled fields are possible depending on the input address, country, and data source.

Parsed Address Input elements are not returned for every country. Also, because GeocodeAddress World geocodes to the geographic or postal level only (not street address), thisdoes not return Parsed Address Input.

Note:

For many countries, if part of the input address could not be recognized as a specific addresselement, this content is returned in UnparsedWords.Input.

For intersection addresses, the first entered street is returned in StreetName.Input and the secondentered street name is returned in IntersectionStreet2.Input.

8Spectrum™ Technology Platform 10.0 Release Notes

Release Notes

Parsed Address Input API

The Enterprise Geocoding Module Parsed Address Input feature is supported by REST and SOAPmethods. The REST method is:

Option.IncludeInputs

The values are Y to implement Parsed Address Input returns or N to disable returns.

Improved Address Point Geocoding for India

India Address Points (TomTom data source) are now geocoded.

This enhancement is available with all updated Enterprise Geocoding Module 2015 Q1 databases.

Improved Geocoding of Turkish Addresses Using Nearby Streets

Major (primary) streets in Turkey can be very long and can span multiple geographic or postal codeboundaries. Because of this, identical address numbers can be found more than once on the samestreet. These can all be valid addresses, but do not represent the same location. For example, thefollowing can be valid addresses with identical house number and street names, so the geocodercould return either location without making a distinction.:

1 ABC Street Istanbul

1 ABC Street Izmir

It is also possible for the same house number to be repeated within the same geography, but againthese do not represent the same location.

2 XYZ Street Istanbul

2 XYZ Street Istanbul

To resolve this problem the geocoder now can use a nearby (secondary) street to provide a referencepoint for the address. Using the nearby secondary street in combination with the primary streetenables the geocoder to locate and return the intended address. The format is:

<House Number> <Primary Street> <Secondary Street> <Town|Postal Code>

By using both the primary and nearby secondary street in the input, the intended address andlatitude/longitude are returned. The candidate also returns the secondary street in an additionalfield.

This enhancement is available with all updated Enterprise Geocoding Module 2015 Q1 databases.

9Spectrum™ Technology Platform 10.0 Release Notes

Release Notes

Enterprise GeoComplete Module

GeoComplete Coverage

Australia is newly available for the GeoComplete Module (GCM). The countries of Bahrain, Oman,Qatar, Saudi Arabia, and Thailand were introduced in 2014 Q4. Other data vintages have beenupdated as described below.

Updated data vintages are indicated by a + in the Street Vintage column. The data provider isTomTom, unless otherwise indicated. All POI data vintages (with the exception of Japan and Mexico)are 2014.06.

Future updates will be covered in subsequent updates of the Enterprise GeoComplete ModuleDatabase Update Release Notes.

Table 1: GeoComplete Supported Countries and Data Sources for Spectrum 10.0

NotesPOI VintageStreet VintageCountry

2014.062014.09 +Andorra (AND)

Street data from PSMA. POI datavendors include MicroPlan, POIPlaza, and SmartLife Technologies.

2014.Q2 +2014.10 +Australia (AUS)

2014.062014.09 +Austria (AUT)

English and Arabic supported2014.062014.06Bahrain (BHR)

2014.062014.12 +Belgium (BEL)

2014.062014.09 +Brazil (BRA)

2014.062014.12 +Canada (CAN)

2014.062014.09 +Czech Republic (CZE)

2014.062014.09 +Denmark (DNK)

2014.062014.12 +Finland (FIN)

2014.062014.09 +France (FRA)

2014.062014.09 +Germany (DEU)

10Spectrum™ Technology Platform 10.0 Release Notes

Release Notes

NotesPOI VintageStreet VintageCountry

2014.062014.12 +Great Britain (GBR)

2014.062014.12 +Hungary (HUN)

2014.062014.06 +Ireland (IRL)

2014.062014.09 +Italy (ITA)

Data from IPC. English andJapanese supported

2014.032014.04Japan (JPN)

English and Arabic supported2014.062014.06Kuwait (KWT)

2014.062014.12 +Liechtenstein (LIE)

2014.062014.12 +Luxembourg (LUX)

2013.122014.09 +Mexico (MEX)

2014.062014.09 +Netherlands (NLD)

2014.062014.09 +Norway (NOR)

English and Arabic supported2014.062014.06Oman (OMN)

2014.062014.09 +Poland (POL)

2014.062014.09 +Portugal (PRT)

English and Arabic supported2014.062014.06Qatar (QAT)

English and Russian (Cyrillic)supported

2014.062014.03Russia (RUS)

English and Arabic supported2014.062014.06Saudi Arabia (SAU)

(Street data from Map InformationSolutions Sdn Bhd. POI data fromTomTom)

2014.062014.02 +Singapore (SGP)

2014.062014.03 +Slovakia (SVK)

11Spectrum™ Technology Platform 10.0 Release Notes

Release Notes

NotesPOI VintageStreet VintageCountry

2014.062014.03 +Slovenia (SVN)

2014.062014.06 +South Africa (ZAF)

2014.062014.09 +Spain (ESP)

2014.062014.09 +Sweden (SWE)

2014.062014.12 +Switzerland (CHE)

2014.062014.03Thailand (THA)

2014.062014.06 +Turkey (TUR)

English and Arabic supported2014.062014.06United Arab Emirates (ARE)

2014.062014.12 +United States (USA)

Must Match Address Number Search Restriction

For GeoComplete, the Management Console has a new Search Restriction named Match OnAddress Number. This option allows the user to determine if an address number match is required.If this match restriction is checked, then returned candidates must match the input address number.By default, Match On Address Number is unchecked, which means that returned candidates do nothave to match the input address number.

If the input does not contain a house number, the Must Match Address Number restriction has noeffect.

The supporting REST and SOAP API call is:

MatchOnAddressNumber

Values can be Y to implement the Must Match restriction or N to ignore it.

Enterprise Routing Module

Support for New Countries

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

12Spectrum™ Technology Platform 10.0 Release Notes

Release Notes

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

2014.03ARGARArgentina

2014.03ALBALAlbania

2014.06BHSBSBahamas

2014.03BLRBYBelarus

2014.06BMUBMBermuda

2014.03BIHBABosnia and Herzegovina

2014.03CHLCLChile

2014.06CODCDDemocratic Republic of theCongo

2014.06GHAGHGhana

2014.06JORJOJordan

2014.06KENKEKenya

2014.06LSOLSLesotho

2014.03MLDMDMoldova

2014.06MOZMZMozambique

2014.06TZATZTanzania

Included with these countries is the ability to provide localized route directions for the following:China(zh_CN), Albania(sq).

Enterprise System Connector

New Module: Enterprise System Connector

This new module provides the ability to read data from an SAP database into a dataflow. It consistsof a single stage: Read from SAP.

13Spectrum™ Technology Platform 10.0 Release Notes

Release Notes

Information Extraction Module

New Module

The new Information Extraction Module provides advanced text-processing capabilities by extractinginformation from unstructured data. This data can come from multiple files and multiple formats.The Information Extraction Module includes the following stages.

• Read From Documents—A source stage that reads unstructured input data from various fileformats and extracts the contents. Once the data has been extracted it can be used for varioustypes of processing, including entity extraction and string manipulation among others. The datacan also be used to build search indexes for unstructured text searches.

• Information Extractor—Extracts entities such as names and addresses from strings of unstructureddata. As with many stages in Spectrum™ Technology Platform, default settings for InformationExtractor can bemade in Management Console, and stage-level settings can bemade in EnterpriseDesigner.

Location Intelligence Module

Spectrum Spatial Manager Enhancements

Several enhancements have been made to Spectrum Spatial Manager for this release. See theonline help for Spectrum Spatial Manager or the "Resources and Data" section of the SpectrumSpatial Guide for more detailed information.

Workflow Changes

Changes have been made throughout the interface to improve usability. The Create drop-down listhas been added to the toolbar that allows you to select the specific type of resource you want tocreate (a connection, a table, an XY table, or a view table). Also, you no longer need to specify thetype of datasource (File System or Database) when creating a table. You simply select a connectionand the application displays all the datasources that can use it.

Detail Pages Enhanced

• The table details page now uses tabs to display different types of information (datasource info,columns, and repository info). An interactive preview of a map is now displayed that is renderedusing data from the table. You can also add a description and keywords that allow you to betterorganize your repository resources and facilitate searching.

• On the map details page, the interactive map is now displayed in its own coordinate system orreprojected using the popular visualization coordinate system Spherical Mercator (epsg:3857) ifit cannot be displayed in its own coordinate system. If it cannot be reprojected, you will see anerror.

• On the layer details page, you can now see a default view of the layer.

14Spectrum™ Technology Platform 10.0 Release Notes

Release Notes

Search Added

A search field has been added above the repository tree. You can now search for named resourcesin the repository by name, description, or keyword. Sorting and filtering options are available to helpyou refine your initial search results.

Updating Inline Named Tables

You can now update named tables that use inline references to use connections instead. Click thelink at the top of either the connection details or table details page to be guided through the updateprocess. Once a table is updated to use a connection, it can then be edited using Spectrum SpatialManager and is easier to update if you use it in other applications or dataflows.

GeoPackage Support

SpectrumSpatial has added support for GeoPackage forWindows. GeoPackage is a spatial extensionto the SQLite database technology. The GeoPackage standard, adopted last year by OGC, allowsfor multiple tables, their relationships, and relevant metadata to be self-contained within a singlefile. It is useful for large datasets and for working around character set and data size limitations inMapInfo Professional.

See the "Resources and Data" section of the Spectrum Spatial Guide for more detailed informationabout GeoPackage as a supported data source.

Write Spatial Data Stage Improvements

Included Columns for Insert and Update

TheWrite Spatial Data stage in Enterprise Designer has been enhanced to ensure that only writablecolumns and primary keys are included for inserts and updates. The following rules are supportedfor all data providers:

Insert

• Read-only columns or primary keys do not appear in the list of columns that you can include foran insert.

• Writable primary keys appear in the list and are required to be included for an insert.

Update by Filter

• Read-only columns or primary keys do not appear in the list of columns that you can include foran update; however, they are allowed in the WHERE clause.

• Writable primary keys do appear in the list and can be optionally included for an update.

Update by Primary Key

• Read-only columns do not appear in the list of columns that you can include for an update.• Read-only primary keys do appear in the list for informational purposes, but are unselected anddisabled (that is, you can cannot select a read-only primary key for an update).

15Spectrum™ Technology Platform 10.0 Release Notes

Release Notes

• Writable primary keys do appear in the list, and are selected and enabled (that is, they areautomatically selected but you can deselect them).

Named Table Selector

Named tables in the Write Spatial Data Options dialog can now be selected from a tree view ofavailable tables in the repository. From the tabs for Insert, Update by Filter or Update by Primary,Key, click the Browse button and choose a writable named table from the list. You can eitherdouble-click on the named table or highlight it and click the Select button. The named table willdisplay in the Named Table field. This text field is not editable.

Map Uploader Enhancements

Several enhancements have been made to the Map Uploader that now make it easier to generatemaps and upload named resource into Spectrum Spatial from MapInfo Professional.

For ease of installation, the old Map Uploader installer has been replaced by a simple zip filecontaining the MapInfo Professional plugin. The plugin can simply be placed in the MapInfoProfessional plugin directory and run within the application.

You can now easily browse the repository using a new repository path chooser that also allows thecreation of folders in the repository. You no longer need to remember the structure of the repositorywhen uploading resource, as you can visually choose where to upload.

Inline named connections are no longer added to resources (e.g., GeoTools connections weregenerated using inline connection definitions). All resources are generated using named connectionreferences.

When uploading both file based and JDBC table resources, you are able to select named connections.New options in the Setting tab have been added to configure the named connections for file basedtables. You can choose a file based named connection and also define the relative path within thenamed connection where the data is located.

Line Direction Enhancements

A new optional boolean attribute showLineDirection has been added to the FeatureLayer. Thisattribute can be used to display the direction of a feature (line, multiline, curve, etc.) By default, theline direction is not rendered, with a default value false. The direction depicts the flow direction ofa based on start and end points of the feature.

Request Timeout

Spectrum Spatial now allows you to set a timeout for SOAP and REST operations as part of arequest to the Mapping and Feature services. The timeout is enabled by default with a value of 300seconds (5 minutes).

To apply the timeout, entry and intermediate pointcuts need to be configured. This is done in theaop.xml located under server/modules/spatial/. The file includes several implementations that you

16Spectrum™ Technology Platform 10.0 Release Notes

Release Notes

can use. The entry point is the point where the timeout starts measuring time. The intermediarypoints are where the timeout checks if the operation timed out.

Use this, for example, when you want to apply a timeout to SOAP and REST renderMap methodsand some intermediary steps (calls to the database, searching tables, retrieving candidates).

To adjust the default timeout value of 300 seconds, edit the timeout property for the Mapping and/orFeature services in the java.properties located under /server/modules/spatial. The values may bedifferent for each service.

timeout.mapping.value=300

timeout.feature.value=300

If the specified timeout value is <= 0, then the timeout will be disabled.

After changing the timeout value changes, restart Spectrum™ Technology Platform.

MI SQL Functions Added

The following MI SQL geometry constructor functions were added in this release:

• fromWKB - converts a WKB (Well-known Binary) BLOB value to a feature geometry• toWKB - converts a feature geometry to its WKB (Well-known Binary) equivalent

These functions can be used in the Query Spatial Data, Write Spatial Data, and Read Spatial Datastages. These stages also now support the bytearray data type.

Support for Classified Grids

TheMI SQL functions MI_GridValueAt andMI_GridValueAtPixel have been enhanced to add supportfor getting values from a classified grid (.GRC). Previously this was supported for continuous gridfiles (.GRD) only.

Classified grids are those that group grid cells by a class description rather than by a numeric value.

The return type of the functions will change based on the grid file type. If the grid is numeric, as inthe case of .GRD, then the return type will be a double.

If the grid file type is character-based, as in the case of .GRC, the return type will be a string.

Improvements to Selecting a Coordinate System

Previously, you had to scroll through a drop-down list of all coordinate systems to select one fromthe coordinate system field in Enterprise Designer or Management Console. You can now typeahead in the coordinate system field to see a shorter, more relevant list of coordinate systems tochoose from. After you clear the default value then enter three alphanumeric characters, a listappears below the field and displays coordinate systems that being with or contain those characters.A descriptive name for the coordinate system also now appears as the default value (for example,

17Spectrum™ Technology Platform 10.0 Release Notes

Release Notes

Longitude/LatitudeWGS 84 instead of epsg:4326). You still have the option to browse for a coordinatesystem.

Coordinate Reference System Additions

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

New Projection

35 – Added support for Rectified Skewed Orthomorphic projection used in Malaysia.

New Datums

• Timbalai 1948, Everest 1968• MAGNA-SIRGAS• GDM2000

New Coordinate Systems

These coordinate systems will be supported in a future release of MapInfo Professional.Note:

• Peninsular RSO Kertau Datum• Peninsular RSO GDM2000 Datum• East Malaysia (BRSO) GDM2000 Datum• East Malaysia (BRSO) Timbalai Datum• Longitude / Latitude (GDM2000 Datum)• Longitude / Latitude (Timbalai 1948, Modified Everest Ellipsoid)• Longitude / Latitude (MAGNA-SIRGAS)• Colombia East• Colombia East Central zone• Colombia Bogota zone• Bogota 1975 / UTM Zone 18• Colombia West zone• MAGNA-SIRGAS / Colombia East zone• MAGNA-SIRGAS / Colombia East Central zone• MAGNA-SIRGAS / Colombia Bogota zone• MAGNA-SIRGAS / Colombia West zone• MAGNA-SIRGAS / Colombia Far West zone

18Spectrum™ Technology Platform 10.0 Release Notes

Release Notes

Updated Datum Transform

JGD2011, the updated version of the Japanese Standard Datum, is now being supported for datumtransforms to remain compatible with MapInfo Professional. This datum was updated to reflectchanges from the Tohoku Earthquake on March 11, 2011.

Enabling the JGD2000 datum transform in the java.properties file also enables the JGD2011 datum(see the Administration section of the Spectrum Spatial Guide for more information on configuringdatum transforms).

Changes to Extensible Data Provider

The Extensible Data Provider bundle can now be downloaded from the Spectrum Spatial WelcomePage, under the Sample Applications tab. It is no longer available for download from thesupport.pb.com site.

Changes to Sample Named Resources

For named maps and named layers in the /Samples folder, all inline layer, table, and style referenceshave been replaced with references to named layers, named tables, and named styles.

Specifying GeoJSON as the Output Format of a Flow Exposed As a Service

When you create a Spectrum flow exposed as a service, you are now able to have that serviceproduce GeoJSON. "GeoJSON" is now one of the Web Service Options along with "XML" and"JSON". This enhancement supports only native platform types along with geometry.

Buffer Enhancements

Spectrum Spatial now uses MapInfo Professional's new algorithm instead of JTS (the Java TopologySuite) for creating buffers, resulting in better performance, reduced memory usage, more consistentresults, and better interoperability with MapInfo Professional.

.

Volatile Attribute for Named Tables

All named tables, including TAB named tables, are now volatile by default unless overridden. Thismeans that with each query the table is checked for modifications. It is important to ensure that anychanges to the table structure are identified, such as before performing an insert or update.

Overriding this default (that is, setting the volatility flag to false) should only be used on tables thatdo not change. You must manually modify the named table definition for the table and add thefollowing attribute:

<DBDataSourceDefinition volatile="false">

19Spectrum™ Technology Platform 10.0 Release Notes

Release Notes

You can use either WebDAV or the updateNamedResource operation in the Named ResourceService to change the value.

You must restart the server when you change the volatile flag from false to true on any existingnamed table or when creating a new named table based on a database table that was previouslyset to false. Regardless of how the volatile flag is set, you will see the actual representation of thedatabase table structure whenever you restart the server.

Spectrum Spatial Manager adds a volatile attribute that is set to true when you create newnamed tables; however, even for named tables without the attribute (as in the case of oldtables) the behavior is the same as if being set to true.

Note:

Management Console

Access Management Console with a Web Browser

You can now access some Management Console functionality using a web browser. This releaseprovides access to the following features:

• View dataflow execution schedules and execution history• Configure dataflow execution defaults for data type conversion, sort performance, malformedrecord handling, and reporting options

• Create database connections and JDBC drivers• View licenses• View expiration information• Configure expiration notifications• View version information• Create users and roles• Create server directory access restrictions• Set service logging levels• View the audit log (the audit log is a new feature in this release)• Configure an SMTP server for email notifications

We will be adding additional features in future releases.

To access Management Console with a web browser, go to:

http://SpectrumServer:HTTPPort/managementconsole

For example:

http://MySpectrumServer:8080/managementconsole

Audit Log

A new log is available with this release: the audit log. This log records events that occur when userscreate and modify objects on your system, as well as events that occur when users execute jobs

20Spectrum™ Technology Platform 10.0 Release Notes

Release Notes

or access services through the API or web services. Some examples of events recorded in the auditlog include creating a dataflow, modifying a database connection, or running a job.

The audit log is only available through the web version of the Management Console.Note:

Microsoft Dynamics CRM Module

Enhanced Duplicate Merging

When you save a record in Microsoft Dynamics CRM and Spectrum™ Technology Platform finds aduplicate in the system, you now have these new options for merging duplicate records:

• You can now merge more than two records together.• You can choose which fields from each duplicate record to merge into the master record.• Duplicate detection is now invoked when you click the Save and Close button on a record. Inprevious releases duplicate detection only worked if you clicked Save.

• You can now generate match keys for existing records. Generating a match key for existing recordsmakes it possible for the records to be identified as duplicates.

Platform

Configuration Database Separated from the Server

You can now install the configuration database to a separate server from the Spectrum™ TechnologyPlatform server. This approach has the following advantages:

• More CPU is available to the server for running jobs, process flows, and service requests becausereading and writing to the configuration database is handled by a separate server.

• Reduced network traffic due to reduced configuration data replicated between nodes. For example,you could have five Spectrum™ Technology Platform servers for handling execution while havingonly three repositories. With just three repositories instead of five, data only needs to replicatebetween three servers rather than five.

• Most scalable installation scenario.

The following diagram illustrates how the configuration database can be placed in its own clusterseparately from the server cluster. For more information, see the Installation Guide.

21Spectrum™ Technology Platform 10.0 Release Notes

Release Notes

Minimum Password Length

You can now set a minimum password length for user accounts. To set a minimum password length,go to the com.pb.spectrum.platform.config:manager=AccountConfigurationManager settingin the JMX console.

New Look for Login Windows

The login window for Enterprise Designer, Management Console, and Interactive Driver has beenupdated with the new Pitney Bowes logo and colors. In order to see the redesigned login windowyou must uninstall existing versions of these tools then install the new version. Reinstalling the clienttools is optional in this release since the only change is to the look and feel of the login window.

SAP Module

Postal Information for Customers and Vendors

The following United States Postal Service information is now added to addresses on customer andvendor records. In previous releases this information was only available for addresses of businesspartners.

• Delivery Point Validation (DPV)

22Spectrum™ Technology Platform 10.0 Release Notes

Release Notes

• Residential Delivery Indicator (RDI)• Commercial Mail Receiving Agency (CMRA)• Early Warning System (EWS)

This additional information helps you gain a more precise understanding of the addresses ofcustomers and vendors.

Universal Addressing Module

U.S. Coding Engine Upgrade

The U.S. coding engine for the Universal Addressing Module has been upgraded in this releaseand is compatible only with the 4.0 version of the U.S. Postal Database. If you upgrade from aprevious version to Spectrum Technology Platform 10.0 and already have a U.S. Postal Databaseconfigured, you may incur errors.

Canadian Coding Engine Upgrade

The Canadian coding engine for the Universal Addressing Module has been upgraded in this release.There are no compatibility issues with this release and the Canadian Postal Monthly Database.

International Coding Engine Upgrade

The international coding engine for the Universal Addressing Module has been upgraded in thisrelease. There are no compatibility issues with this release and the International Postal Database.

New Validate Address Output Fields

Validate Address now supports the following fields that are included in the output when you checkInclude a standard address or Include matched address elements on the Output Data Optionstab of Validate Address:

• AdditionalInputData.Unmatched—Contains data that was passed into Validate Address but notused in the final validation.

• AdditionalInputData.Base—Contains all the data that was not output to the standardized address.

New Loqate Output Fields

Loqate stages now support the following output fields:

• Building• Principality• StreetAlias• Subcity• Substreet• USCounty

23Spectrum™ Technology Platform 10.0 Release Notes

Release Notes

Validate Address Loqate Acceptance Level

Validate Address Loqate has a new field called Acceptance level that specifies the minimumverification level a record must attain in order to be considered valid.

Get Candidate Address Loqate Address Lookup Process Option

Get Candidate Address Loqate has a new field called Address Lookup Process that specifieswhether to verify or search candidate records. The Search option takes a full or partial address asinput and returns as output a list of closely matching results. The Verify option takes addressinformation in address lines, address components, or a combination of both as input and returns asoutput results that more closely match the input.

Universal Name Module

Configuring Open Name Parser at Runtime

You are now able to pass configuration for Open Name Parser at runtime.

System Requirements

Changes to Supported Operating SystemsWindows Server 2003 is no longer supported.

Server Requirements

Operating Systems

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

NotesOperating System

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

AIX 6.1

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

AIX 7.1

24Spectrum™ Technology Platform 10.0 Release Notes

Release Notes

NotesOperating System

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• Universal Address Module component Validate Address AUS

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

• Enterprise Tax Module• Universal Address Module component Validate Address AUS

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

HP-UX 11.31 (Itanium)

The following modules are not supported on this operating system: Address NowModule, Enterprise Tax Module, GeoConfidence Module, and Location IntelligenceModule.

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

Oracle Linux 6

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

Red Hat Enterprise Linux 5

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

Red Hat Enterprise Linux 6

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

Solaris 10 (SPARC only)

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

• Enterprise Tax Module• Universal Addressing Module

Requires the following:SUSE 10.0

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

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

25Spectrum™ Technology Platform 10.0 Release Notes

Release Notes

NotesOperating System

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 11

Requires these runtime libraries installed as follows:

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

Ubuntu 12

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• Microsoft Dynamics CRM Module• SAP Module• Siebel Module• Universal Addressing Module

NotesOperating System

None.Windows Server 2008 R2

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

64-bit Required

The server requires a 64-bit system. 32-bit 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.• 2 GB to 3 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

26Spectrum™ Technology Platform 10.0 Release Notes

Release Notes

UpgradeNew Installation

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

• If you are adding modules as part of your upgrade, youwill need 3 GB to install all modules, less if installing fewermodules.

• 2 GB to 3 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.

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

27Spectrum™ Technology Platform 10.0 Release Notes

Release Notes

• For IBM AIX systems only, you must download and install Java 7, both the 32-bit version and the64-bit version, before installing Spectrum™ Technology Platform. If you do not have Java 7 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• 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

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

spectrum.orientdb.hazelcast.port2434

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

spectrum.orientdb.http.port2480-2486

28Spectrum™ Technology Platform 10.0 Release Notes

Release Notes

DescriptionPropertyPort

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

Client Tools RequirementsEnterprise 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 7. If you are installing the Administration Utility on thesame computer where the Spectrum™ Technology Platform server is installed, Java 7 is alreadyinstalled since it is included with the server. If you want to install the Administration Utility onanother computer, make sure that the computer has Java 7 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 Business Steward Portal or the Data Hub Relationship Analysis Client, a browser withMicrosoft Silverlight 5 installed. See www.microsoft.com/getsilverlight.

Web Browser Requirements• Internet Explorer 10 or later• Google Chrome 40 or later• Firefox 35 or later

29Spectrum™ Technology Platform 10.0 Release Notes

Release Notes

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

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

• iSeries platforms support the Client SDK in Java only

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

30Spectrum™ Technology Platform 10.0 Release Notes

Release Notes

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

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

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

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

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

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

• 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

31Spectrum™ Technology Platform 10.0 Release Notes

Release Notes

• 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

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

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

• 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

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

• libpthread.so.1

32Spectrum™ Technology Platform 10.0 Release Notes

Release Notes

• 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• 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, Oracle Linux• SQL Server 2008, SQL Server 2012 R2• SAP HANA 7.4• PostGres 8+ (PostGIS 1.5 and 2.x)• GeoPackage (Windows only)

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)

33Spectrum™ Technology Platform 10.0 Release Notes

Release Notes

• ESRI ShapeFile

Raster Format

The Location Intelligence Module supports the following raster formats (64-bit only) for use with thespatial services:

• GIF• TIFF• GEOTIFF• JPG• PNG• ECW• MrSID• MI Grid (*.MIG)• Northwood Grid (GRD, GRC (view only))• ADRG• CADRG• CIB• DTED• NITF• RPF

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

Note:

Browser

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

• 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 requires Java 7. If you are installing these utilities on the same computer where theSpectrum™ Technology Platform server is installed, Java 7 is already installed since it is includedwith the server. If you want to install the utilities on another computer, make sure that the computerhas Java 7 installed.

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

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

34Spectrum™ Technology Platform 10.0 Release Notes

Release Notes

OGC Compliance

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

• CSW version number 2.0.2• 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 12.5.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 CompatibilityThis 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

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

35Spectrum™ Technology Platform 10.0 Release Notes

Release Notes

Installation Notes

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

Upgrade PathsYou can upgrade to Spectrum™ Technology Platform 10.0 from:

• 9.0 SP3• 9.0 SP2• 9.0 SP1• 9.0• 8.0 SP3• 7.0

If you have 8.0 SP2, 8.0 SP1, or a version prior to 7.0 installed, you must first upgrade to one of theabove versions, and then upgrade from that version to 10.0.

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 versions 7.0 or 8.0 SP3 of the client tools. You must upgrade from theseversions to 10.0 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. For more information on installing clienttools, see the Spectrum™ Technology Platform Installation Guide.

Upgrading the Business Steward Module

To upgrade to this version of the Business Steward Module, your current installation must be atleast on version 8.0 of Spectrum™ Technology Platform. For any other version of Spectrum™

Technology Platform, you must first uninstall the existing Business Steward Module before installingthe new version. For instructions on removing modules, see the Spectrum™ Technology PlatformInstallation Guide.

36Spectrum™ Technology Platform 10.0 Release Notes

Release Notes

Upgrading the Data Hub Module

To upgrade to this version of the Data Hub Module, your current installation must be at least onversion 8.0 of Spectrum™ Technology Platform. For any other version of Spectrum™ TechnologyPlatform, you must first uninstall the existing module before installing the new version. For instructionson removing modules, see the Spectrum™ Technology Platform Installation Guide.

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.

• 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

When you upgrade the Location IntelligenceModule to Spectrum™ Technology Platform it is importantto back up custom data sources and resources prior to upgrading using WebDAV.

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.

37Spectrum™ Technology Platform 10.0 Release Notes

Release Notes

It is very important to perform a backup of the repository once the Spectrum™ Technology Platformupgrade is successful. For this release, there are significant changes to the repository that will renderprevious backups ineffective. Make a copy of the entire repository located in the%install_home%\Spectrum\server\modules\spatial\jackrabbit directory, and saveit to a secure location.

Permissions to resources in the Spectrum Spatial repository are retained when upgrading from any9.0 verison to the current version. Permissions are not retained when upgrading from version 7.0or 8.x to any 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 9.0, 8.0 SP3, or 7.0, you must update the SSL configuration file after upgrading to 10.0.

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.

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.

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

Location Intelligence Module

Back Up Location Intelligence Module Named Resources and Data

When you upgrade the Location IntelligenceModule to Spectrum™ Technology Platform it is importantto back up custom data sources and resources prior to upgrading using WebDAV.

38Spectrum™ Technology Platform 10.0 Release Notes

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 very important to perform a backup of the repository once the Spectrum™ Technology Platformupgrade is successful. For this release, there are significant changes to the repository that will renderprevious backups ineffective. Make a copy of the entire repository located in the%install_home%\Spectrum\server\modules\spatial\jackrabbit directory, and saveit to a secure location.

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 page38.

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:

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

39Spectrum™ Technology Platform 10.0 Release Notes

Release Notes

Configuration files are stored in the repository and cannot be simply accessed on the file system.You must use the WebDAV protocol to access and copy the files to another location. On Windows,you can use WebDav from Windows Explorer or the open-source DAV Explorer client application.On Linux/UNIX, use WebDAV from a Windows client or from the desktop file explorer. The easiestway to access Repository files via WebDAV is to use the direct Windows Explorer client and createa 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. If you are using DAV Explorer, use File > Get File on each of the files in the Configuration folder.4. Make a backup copy of \modules\spatial\java.properties and java.vmargs to save any non-default

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

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

properties you added or changed were preserved.

If you are upgrading from version 7.0 to 9.x or later, do not simply copy the oldjava.properties and java.vmargs files over the new ones. Theremay be required arguments

Note:

that were added with a newer version. Carefully merge the contents of the two filestogether as needed.

8. Stop the Spectrum server and restart it after making these changes or reset each affected servicefrom 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”.

40Spectrum™ Technology Platform 10.0 Release Notes

Release Notes

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 ErrorWhen Upgrading an 8.x Clustered Environment for Location IntelligenceModule

If you are upgrading an 8.x clustered environment, one of the pre-upgrade steps is to switch froma common repository database to the local Derby database and copy the backed up repository.xml.These pre-upgrade instructions are located in the "Upgrading Clustering in the Location IntelligenceModule" 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!"/>

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

Upgrading PostGIS Tables and Named Connections

When upgrading from a 9.0 SP2 or earlier version, any PostGIS named table existing as a GeoToolstable will be transformed to a PostGIS data provider table. This upgraded table will not have inline

41Spectrum™ Technology Platform 10.0 Release Notes

Release Notes

connection details; rather, it will have a reference to a PostGIS named connection that has the sameconnection details.

This does not apply when upgrading from 9.0 SP3, as these chages are already includedin 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"/><Property name="password" value="postgres"/></DriverPropertySet></JDBCDriverParameters></DBConnection></NamedConnection>

42Spectrum™ Technology Platform 10.0 Release Notes

Release Notes

Notes on Upgrading

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

• When you are upgrading from 9.2 or earlier to 10.0, PostGIS XY tables will not be upgraded touse new named connections. The connections will continue to be stored inline in the named table.

Permissions After Upgrading

Permissions to resources in the Spectrum Spatial repository are retained when upgrading from any9.0 verison to the current version. Permissions are not retained when upgrading from version 7.0or 8.x to any 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

Enterprise Routing Module

Database Memory Usage

For loading a large Enterprise Routing database, you have to increase the memory of the routingremote component. To do this, set the value of the –Xmx parameter in the java.vmargs file to avalue larger than the size of the database. For example, in the case of loading entire United Statesdatabase (size is approximately 1.94 GB), setting the value of –Xmx to 2048m would be sufficient.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:

SAP Module

New BC Set

There is a new BC set in this release. If you are upgrading from a previous version, you must activatethis new BC set after upgrading:

43Spectrum™ Technology Platform 10.0 Release Notes

Release Notes

/HSGRP1/BCSET_VENDOR

For instructions, see the SAP Module Guide.

New Dataflow for Enterprise Tax Module

If you use the Enterprise Tax Module with the SAP Module, and have licensed only the EnterpriseTax Module and no others, there is a new dataflow you must deploy on your Spectrum™ TechnologyPlatform server. The new dataflow is ValidateAddressWithCandidates_ETM.df. For instructions ondeploying dataflows, see the SAP Module Guide.

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.

Universal Addressing Module

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 the

44Spectrum™ Technology Platform 10.0 Release Notes

Release Notes

RDI 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

Documentation• For GeoComplete, the Management Console has a new Search Restriction named Must MatchAddress Number. This option allows the user to determine if a house number match is requiredto get a match. By default, the Must Match Address Number box is unchecked, which means thatreturned candidates do not have to match the input house number. If the Match Restriction ischecked, then returned candidates must match the input house number. If the input does notcontain a house number, the Must Match Address Number restriction has no effect.

This feature was introduced previously, but was not documented at that time.

Enterprise Data Integration Module• (CDQE-36176) Write to DB does not work when writing to an Oracle database in the Japaneselocale.

• (CDQE-36158) Query Cache malfunctions when runtime instances is greater than 1.• (CDQE-33918) Read from XML appears to lock the file.

Enterprise Geocoding Module• (CDQE-24467) Addresses for Brooklyn NY are now returned more accurately. Previously, the topranked candidate was sometimes from a small populated place in a different New York Statecounty, rather than from the intended address in Brooklyn, New York City.

Enterprise Routing Module• (ROUT-2464) The REST services were accepting the wrong time and distance units. They wereusing full names (meters or seconds), similar to the SOAP services, instead of using the shortversions (m or s).

45Spectrum™ Technology Platform 10.0 Release Notes

Release Notes

• (ROUT-1973) Invalid values for query parameters in the REST services were not being handledconsistently across all services. Some parameters would cause error messages, some were beingignored, and some (boolean) were using a default value.

• (ROUT-1972) Value of the q parameter for all REST services were throwing invalid query exceptionsas it was considered case sensitive. Now all q parameters are case insensitive (e.g., routecostmatrixor routeCostMatrix).

• (ROUT-1949) For a given set of points (and all similar scenarios where the path route goes beyondthe destination, and then takes a turn back, before reaching the destination.), GetTravelCostMatrixoperation was not able to calculate the route, however the PointToPoint operation could. This isnow fixed, and for those points (and all similar scenarios) GetTravelCostMatrix is able to calculatethe route.

• (ROUT-2570) The ReturnRouteGeometry option in the GetTravelDirection service in ManagementConsole was not working for any locales except English.

Location Intelligence Module• (MID-23062) Previously, parsing failed for a MapBasic style expression if it contained a Brushclause followed by a Pen clause; regardless of the order of the clauses, the expression is nowcorrectly interpreted.

• (MID-22500 and MID-22509) Previously, there was an issue with Tomcat connection pooling if apooled connection became invalid on the database server side. When an application tried to usethis invalid connection it threw an exception, such as Caused by:com.microsoft.sqlserver.jdbc.SQLServerException: The connection is closed.To fix this issue, the ability to enable and configure validation of pooled connections was addedto the pooling-datasource-factory.properties file (located underSpectrumLocation\server\modules\spatial). You can now allow objects to be validatedbefore being borrowed from the pool. If the object fails validation, it will be dropped from the pooland an attempt will be made to borrow another. You can also set a validation interval to alleviateperformance impacts or use a SQL query to validate pool connections.

Using this feature will have a slight negative performance impact as a query is alwaysexecuted before the real query executed by Spectrum Spatial; however, the test query

Note:

maintains the integrity of all the connections in the connection pool in cases wherecommunication between Spectrum Spatial and an external database is not reliable. Setthe validation interval to avoid excessive validation. If a connection is due for validation,but has been validated previously within this interval, it will not be validated again.

• (MID-21275) The Save button is now enabled if you make certain changes (such as deselectinga column or changing the text in the filter) to a Write Spatial Data stage that you have reopenedafter saving.

• (MID-21231) The crs property is no longer included in the GeoJSON response if the geometry isin the WGS 84 coordinate system.

• (MID-21017 / SSP-219) The rendering attribute for MapView set to Quality is now working correctly.The Quality setting means that anti-aliasing is used for higher quality rendering over the defaultrendering setting for speed. The issue was that while rendering regions with solid or pattern filled

46Spectrum™ Technology Platform 10.0 Release Notes

Release Notes

interiors and no borders using the quality setting, visible translucent edges were appearing betweenregions. Now translucent edges do not appear. In the case of regions with pattern filled interiorsand no border, anti-aliasing is turned off.

• (MID-20985) Queries involving an envelope filter executed against a view table have beenoptimized. Previously, the query that defined the view was executed against the data source, andthe envelope query was then applied to the results. Now the envelope query is added to the viewtable's query so that it has the opportunity to be delegated to the data source. This change appliesto all data sources.

• (MID-20654) Mapping service REST operations that generate images in the response are nowfunctioning properly on AIX 6.1 and 7.1 operating systems.

• (MID-20567) The MI_AggregateEnvelope (MBR aggregate) was returning a polygon with ringsfor the SAP HANA, SQL Server 2012, and PostGres data providers. It now correctly returns arectangle for all data providers.

• (MID-20465) When performing an update on a Geometry column of a table to a MultiFeatureGeometry (two or more of the same multi-type geometries), the Feature service no longer throwsa runtime exception error: You can now query, update, and insert a MultiFeatureGeometry thathas multiple MultiCurves or MultiPolygons for all supported data providers.

• (MID-20480) A dot (.) is now allowed for names of folders and resources in Spectrum SpatialManager.

• (MID-20406) For relational database data sources in MapInfo Professional, Map Uploader nowcreates named tables that use named connections.

• (MID-19803) If the Spectrum Spatial upgrade installer encounters a problem during the backupphase of the process, it will now notify the user of the failure and the installer will stop. To re-trythe upgrade, you must manually backup the lim_backup8.0 folder upgrade underSpectrumLocation\server\modules to another location, and delete it from this location. Re-launchthe installer. See LIM Upgrade Backup Failure Procedure on page 39.

• (MID-19786 / SCS-2235) Previously, if a database file was either deleted or renamed for a Pointin Polygon stage, you were prevented from configuring the stage and the following error messagewas displayed: "Object reference not set to an instance of an object." You can now open the Pointin Polygon Options dialog in this situation and see the appropriate error displayed next to theDatabase field. You can then either change the selected database from the drop-down list or fixthe underlying file and reopen this dialog box where the corresponding details are displayed asexpected.

• (MID-18608) The returned data type from the Min and Max MI SQL functions now matches thedata type of the column. For example, if the column has short data type then Min and Max willhave return type of short.

• (MID-17920 / SCS-2012) We are now able to achieve more accurate results for the Contain andWithin operators in the case of boundary conditions. Spectrum Spatial no longer return points thatare on or near a polygon boundary based on tolerance value, as it gave incorrect results. Forexample, when you previously performed a Within operation for Query Spatial Data, a point wasshown in two non-overlapping polygons; a point is now shown in just one polygon.

• (MID-17420) The REST Search Nearest request no longer throws an error when a GeoJSONgeometry is specified without a coordinate system (CRS property). If no CRS is specified, thenEPSG:4326 is considered the default CRS.

47Spectrum™ Technology Platform 10.0 Release Notes

Release Notes

• (MID-20730) Inserting a feature into a PostGIS table containing a SERIAL datatype primary keyis now working correctly.

• (MID-21043) SERIAL and IDENTITY datatype columns for PostGIS and SQL Server, respectively,are now marked as read-only.

• (MID-21821) ForWMS 1.3 GetCapabilities requests, the axes of the returned bounds for coordinatereference systems other than CRS84 are now correct as specified in the coordinate referencesystem definition. In previous versions, the bounds returned for many non-Lat/Long coordinatesystems were incorrect.

• (MID-22152) Rendering enhancements have resulted in improved performance for raster images.• (MID-22153) Classified grid file (.GRC) no longer throws an error when using the MI_GridValueAtfunction. This function and MI_GridValueAtPixel have been enhanced to support .GRC files.Queries using the functions now return the string value of the file. See Support for ClassifiedGrids on page 17.

Universal Addressing Module• (CDQE-32143) EAST is not abbreviated to E for an address in North Vancouver, BC.• (CDQE-31850)When using the Fast Completion service, address in Spain and Belgium the housenumber does not contain the expected result.

• (CDQE-31791) Validate Address Loqate does not parse suffix and trailing directionals intoappropriate output fields.

• (CDQE-29574) Validate Address Loqate returns duplicates in AddressLine fields.• (CDQE-28014) Validate Address stops responding after validating a certain address in PuertoRico.

• (CDQE-27450) Address fails validation but Validate Address Loqate changes the street name.• (CDQE-27024) Validate Address is not abbreviating the street type or directional on valid outputfor certain addresses.

• (CDQE-24674) AdditionalInputData missing from Canadian addresses.• (CDQE-23385) Address in Great Bend, KS is not validated even though it is a valid address.• (CDQE-12654) For an address in Greenville, NC, non-address data is dropped from the output.

Known Issues

This release contains the following known issues.

Address Now Module• (CDQE-20899) Missing subcity and Jeddah issue.• (CDQE-20845) Various address validation errors in Hong Kong, UAE, Israel, and Indonesia.

48Spectrum™ Technology Platform 10.0 Release Notes

Release Notes

• (CDQE-20813) Return codes for addresses with complex first lines are not as expected.• (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.• (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-9751) Different results when mixed casing is enabled.• (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.

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.

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

• (CDQE-29695) Unable to deploy a virtual data source that has the same name but different casing.• (CDQE-29683) The count of items slected changes when using themove up or move down buttons.• (CDQE-28899) In the Virtual Data Store view, the Select all check box is not cleared when anitem is unchecked.

49Spectrum™ Technology Platform 10.0 Release Notes

Release Notes

Enterprise Data Integration Module• (CDQE-34898) Read from File error when reading a text file containing a form feed character.• (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.

Enterprise Geocoding Module• (CDQE-34464) Country Identifier returns "Suecia" as Switzerland instead of Sweden.• (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-7029) A null value in a tab file causes Canadian addresses to fail geocoding.• (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.

50Spectrum™ Technology Platform 10.0 Release Notes

Release Notes

• (CDQE-6664) Portugal geocoder throws error during initialization.• (CDQE-4927) Multiple matches are not returned for E030 match code.• (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:

Enterprise Routing Module• 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-421) Exception is thrown by Management Console preview if you are returning geometryobjects.

51Spectrum™ Technology Platform 10.0 Release Notes

Release Notes

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

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

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

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

Location Intelligence Module• (MID-22995) In the .NET samples, an error appears when doing a Feature Service request in twoof the Feature samples, SearchIntersects and SearchIntersectsWithCount. Also, the Mappingsample RenderMapWithLineLinkageLayer uses a named style resource that does not exist.

• (MID-22991) Content searching using the Named Resource Service or Spectrum Spatial Managerdoes not work properly on the AIX operating system.

• (MID-22876)When choosing the repository path using Map Uploader, the tree view does not showempty folders in the repository.

• (MID-22772) Spectrum Spatial Manager is sometimes unresponsive or slow when searching ornavigating to another page after creating a named connection.

• (MID-22733) When using Map Uploader, an error message is shown if you are trying to upload amap to a repository location which contains the same resources in nested folders.

• (MID-22644) When deleting a folder that contains a GeoPackage table in Spectrum SpatialManager, an error message appears that incorrectly indicates resources will break.

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

• (MID-22494) Named tables cannot be created with DateTimeOffset data.• (MID-22362) In Spectrum Spatial Manager, incorrect error messages appear on the table andmap detail pages when the underlying database table is dropped, such as "Error Occurred: Nomessage available" or "Error Occurred: java.lang.NullPointerException."

• (MID-22225) Spectrum Spatial Manager does not properly handle unknown data sources, eitherby ignoring them or displaying a message that they are not supported.

• (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-21870 / SCS-2495) Spectrum Spatial Manager incorrectly allows non-numeric datatypes forthe X and Y columns when creating an XY named table.

• (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 the

52Spectrum™ Technology Platform 10.0 Release Notes

Release Notes

table. 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 does not 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-20977) The Mapping Service renders raster jpeg files with a pink tone.• (MID-20976) A legend generated in Spatial Analyst displays multiple line styles that were neverspecified, whereas the legend in MapInfo Professional displays a single line style. This occursafter uploading a map to Spectrum Spatial using Map Uploader, then adding that map to a MapConfig in Spatial Analyst. Use a style override in Spectrum Spatial as a workaround.

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

• (MID-23137) In a clustered LIM environment, creating named resources on a node where thecontaining folder is created on another node will throw a permissions exception. An issue existsin Spectrum Spatial 9.0 SP3 and 10.0 where the folder on the other node did not register properly.To work around this issue, create the folder and add any named resources under the folder onthe same node. Restart the rest of the nodes to synchronize.

• (MID-20325) For the Write Spatial Stage in the Enterprise Designer, if an attempt is made to loada named table and the opening of the table fails at the server side, there is no error reported tothe client. Rather, the error is reported to the wrapper log file. For example, if a named table withan invalid JDBC connection string is chosen, you will get an I/O exception in wrapper.log, but nowarning in Enterprise Designer.

• (MID-20308) The GetNamedMap request used by Management Console fails for some of thesample map data.

• (MID-18362) Some Mapping Service demo page requests are not working on AIX 7.1.• (MID-17965) The SearchNearest request for the Feature Service does not return all candidates.• (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.

• (MID-17674) In Spectrum Spatial Manager, if the Spectrum license is expired a 500 error codeappears instead of an expiration message.

• (MID-17629) When moving, renaming, or deleting resources, Spectrum Spatial Manager does notindicate that other resources which are not visible (that is, ones you do not have permission tosee) are going to be affected by the operation.

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

• (MID-17276) Oracle not returning correct data with MI_Contains.• (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.

53Spectrum™ Technology Platform 10.0 Release Notes

Release Notes

• (MID-10723) Shapefiles added to the repository may contain the incorrect projection. The namedtable will receive the SRSName=mapinfo 1, 104, known as WGS84. If a shapefile with a differentprojection (for example, British National Grid) is added through Management Console, use oneof the methods below to change the coordinate system:

• Use the Named Resource Service to update the named resource(UpdateNamedResourceRequest operation), OR

• Use a WebDAV client (DAVExplorer or Windows Explorer) to upload (and overwrite) the namedtable with the correct coordinate system. The element to be replaced is<mxp:SRSName>mapinfo:coordsys 1, 104</mxp:SRSName>.

SAP Module• (CDQE-22601) Various addresses that are valid are not able to be validated during customercreation process in SAP.

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-21961) Job executor error when folder does not exist on client machine.

Universal Addressing Module• (CDQE-36608) Validate Address Loqate matching address elements to ApartmentNumber andApartmentNumber2.

• (CDQE-36410) The letter "N" appended to house number.• (CDQE-36389) Unexpected changes to certain validated addresses in the UK.• (CDQE-36244) Duplicate record for Canadian postal code H2R2T6.• (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-35854) Validate Address Loqate issues with processing addresses on roads in Bangkoknamed Sukhumvit.

• (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-35717) Validate Address fails when validating an address in Trinidad and Tobago.• (CDQE-35697) Miscellaneous differences in address validation compared to older version.• (CDQE-35474) Invalid address with Canadian postal code returned with 100% confidence.

54Spectrum™ Technology Platform 10.0 Release Notes

Release Notes

• (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-34350) Validate Address does not provide apartment level information and multiple matchrecords.

• (CDQE-34012) Get City State Province returns an invalid address for Canadian postal codeT0J2J0.

• (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-32161) Get City State Province does not return a city for Canadian postal code T7X3B3.• (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-31084) Get Candidate Addresses Loqate fails to return candidates for an address in ZIPCode 22033.

• (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-29280/CDQE-28359) Unable to validate rural Ontario addresses without a postal code.• (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-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-27848) Extra carriage return added to end of record.• (CDQE-27698) Validate Address Loqate corrects address to an invalid address.

55Spectrum™ Technology Platform 10.0 Release Notes

Release Notes

• (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.• (CDQE-27447) Invalid address in Calgary, AB does not return Status=F.• (CDQE-27361) Address returns unexpected results in the City.Result and StatProvince.Resultfields.

• (CDQE-27352) Address in Pittsburgh, PA matches to the wrong street.• (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-26613) An address in the city Saint Paul, AB does not validate but when used with thecity name St. Paul, AB it does.

• (CDQE-26499) AutoComplete Loqate returns an address in St. John, BC but this address geocodesonly to a postal centroid.

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

• (CDQE-25154) Validate Address Loqate does not return multiple matches for certain addressesthat should have multiple matches.

• (CDQE-24949) Japanese addresses entered in Kanji and transliterated to Latin are not recognizedby the geocoder.

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

• (CDQE-24789) Address displays multiple matches but no distinctions are observed.• (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-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-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-21788) Address in Empire, MI cannot be 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.

56Spectrum™ Technology Platform 10.0 Release Notes

Release Notes

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

• (CDQE-19128) MONT is recognized as an abbreviation for Montana.• (CDQE-19114) Improper normalization of state road keywords for address in Ferrum, VA.• (CDQE-19110) Address in Brookfield, WI not properly validated when the suite number is enteredin AddressLine1.

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

• (CDQE-18944) City alias not recognized for address in Toronto, ON.• (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-15538) Get Candidate Address returns a city name with incorrect accent character.• (CDQE-14665) Address line returned on output even if it contains garbage.• (CDQE-14403) Firm name extraction moves apartment information.• (CDQE-13403) ZIP Code is being updated instead of the city or street suffix.• (CDQE-12666) An address in Washington DC fails when SuiteLink is enabled.• (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-12270) Fast complete does not return the correct data for an address in ZIP Code 34677.• (CDQE-11850) Validate Address does not return a confidence score of 100 for an input addressthat is not changed during validate.

• (CDQE-11628) Validate Address does not return all candidates for an address in Port Washington,NY.

• (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-10809) End of File exception after approximately 6,000 records.

57Spectrum™ Technology Platform 10.0 Release Notes

Release Notes

• (CDQE-10775) Address in Lisbon, ME is DPV confirmed even though the secondary addressinformation is invalid.

• (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-10298) Apartment number being dropped for address in Tacoma, WA.• (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-9350) An address in Laval, PQ does not return the correct casing for the provinceabbreviation.

• (CDQE-8449/00313107) For U.S. rural route addresses that are LACS/Link converted, the outputfield USLACS contains "N" for not converted.

• (CDQE-8438) Validate Address is not returning the ISO country name for Lao People's DemocraticRepublic and Côte d'Ivoire.

• (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-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-7455) Apartment information issue.• (CDQE-7311) Address in Phoenix without the state specified returns a state result code of "V"instead of "A".

• (CDQE-4179/00006048) Abbreviated alias option returns alias when enabled, and does not returnalias when enabled.

• (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.• (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.

58Spectrum™ Technology Platform 10.0 Release Notes

Release Notes

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.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.

59Spectrum™ Technology Platform 10.0 Release Notes

Release Notes

Universal Name Module• (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.

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

60Spectrum™ Technology Platform 10.0 Release Notes

Release Notes

3001 Summer Street

Stamford CT 06926-0700

www.pitneybowes.com