software/spectrum/lim/8_0/pdf/Spectrum_8.0.0_ReleaseNotes

UNITED STATES 

www.pb.com/software 

Technical Support: 

www.pbinsight.com/support 

CANADA 

www.pb.com/software 


www.pbinsight.com/support 

EUROPE/UNITED KINGDOM 

www.pitneybowes.co.uk/software 


www.pbsoftware.eu/uk/support 

ASIA PACIFIC/AUSTRALIA 

www.pitneybowes.com.au/software 


www.pbinsight.com.au/support 

© 2012 Pitney Bowes Software Inc. 

June 26, 2012 

Spectrum Technology Platform 

Version 8.0 

Release Notes 

This document contains information about Spectrum Technology Platform 8.0. You have 

access only to the modules you have licensed. To evaluate any other modules, contact 

your Pitney Bowes Software account executive for a trial license key. 

Complete documentation can be found on the Spectrum Technology Platform DVD, in 

the "documentation" folder. 

Contents: 

• What's New . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2 

• Fixed Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13 

• Known Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17 

• Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22 

• Installation Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24

What's New 

What's New 

This release contains the following new and changed features. 

Address Now Module 

Support for First Quarter 2012 Address Now Data 

This release adds support for the First Quarter 2012 Address Now data. This support was previously 

released as 7.0 S24. You must install the 7.0 S24 product update or upgrade to Spectrum Technology 

Platform 8.0 in order to use the Q1 2012 data. 

Advanced Matching Module 

Jaro-Winkler Algorithm in Matching Stages 

The Advanced Matching Module now includes the Jaro-Winkler algorithm as a Child Option in the Interflow 

Match, Intraflow Match, and Transactional Match stages. This algorithm refers to the Jaro–Winkler distance, 

which is a measure of similarity between two strings. It estimates the number of character replacements 

it takes to transform one string into another. The higher the Jaro–Winkler distance for two strings 

is, the more similar the strings are. The Jaro–Winkler distance metric was developed and is best suited 

for short strings such as personal names. The score is normalized such that 0 equates to no similarity 

and 1 is an exact match. 

Business Steward Module 

Field Filtering in Write Exceptions 

The Write Exceptions stage now enables you to select which fields' data should be returned to the exceptions 

repository. 

Drill Down from Charts to Editor 

The Business Steward Portal now allows you to drill down from chart categories to the editor view so 

that you can see the specific records that comprise a particular category in a chart. 

Data Hub Module 

2 

New Module: The Data Hub Module 

The new Data Hub Module offers a complete suite of Master Data Management (MDM) capabilities. The 

Data Hub Module provides a persistent hub to manage not only single views of your most critical data 

assets, but also takes a unique approach in the marketplace, providing you with a relationship-centric 

view across domains and across connected networks of obvious and non-obvious relationships. 

By using the new Write to Hub stage with input data, you can define models that represent the entities 

and the relationships between those entities. You can interact with models in three ways: 

• Visually, by using the Relationship Analysis Client 

Spectrum Technology Platform 8.0

• By querying the model in real time to deliver the results directly to your business processes 

• Through event triggers based on your custom business rules 

Modeling is based on an underlying graph database that provides for a very intuitive and flexible process 

in defining the models, unlike a rigid, schema-based, normalized relational model that does not deliver 

the performance needed to understand connected data across large networks. 

Some of the ways you can use the Data Hub Module include: 

• Providing more personalized customer service by anticipating customer needs and optimizing offerings 

• Predicting customer influence and impact 

• Categorizing customers as leaders, followers, influencers, or late adopters 

• Identifying hidden, latent, non-obvious connections among people, groups, and organizations 

• Identifying shifting patterns of connectedness, distance, centrality, influence status, and importance 

Besides Master Data Management (MDM), there are many other applications for the Data Hub Module. 

These include: 

• Social network analysis 

• Fraud, crime, and terrorist network detection and prevention 

• Churn prediction 

• Business intelligence 

• Call detail record analysis 

• Recommendation engine 

For details on the Data Hub Module, please contact your Pitney Bowes Software account executive. 

Data Normalization Module 

Transliterator 

The new Transliterator stage converts a string between Latin and other scripts. For example: 

Source 

Open Parser Import/Export 

Transliteration 

kyanpasu 

biologichyeskom 

You can now import and export domains and cultures in the Open Parser tool of the Data Normalization 

Module. This allows you to import domains and cultures you've created elsewhere and export domains 

and cultures you've created in Spectrum Technology Platform. For more information on importing and 

exporting domains and cultures, see the Open Parser section of the Data Normalization Module in the 

Spectrum Technology Platform User's Guide. 

Release Notes 

Release Notes 

3

Enterprise Designer 

New Open Parser Tables 

The following tables are now available as part of the Asian Plus Pack. The Asian Plus Pack requires an 

additional license. Contact your account executive for more information. 

• Korean Family Names (Native) 

• Korean Family Names (Romanized) 

• Korean Given Names (Native) 

• Korean Given Names (Romanized) 

New Table Lookup Tables 

The following tables are now available. 

Core Names 

• Enhanced Family Names Ethnicity 

• Enhanced Given Names Ethnicity 

Arabic Plus Pack 

• Arabic Family Names Ethnicity (Arabic) 

• Arabic Family Names Ethnicity (Romanized) 

• Arabic Given Names Ethnicity (Arabic) 

• Arabic Given Names Ethnicity (Romanized) 

Asian Plus Pack 

• CJKI Family Names Ethnicity (Native) 

• CJKI Family Names Ethnicity (Romanized) 

• CJKI Given Names Ethnicity (Native) 

• CJKI Given Names Ethnicity (Romanized) 


4 

XML Input and Output 

You can now read XML files as input to a dataflow and write to XML files as dataflow output. Two new 

stages, Read from XML and Write to XML support this new capability. 

Variable Format File Input and Output 

This release adds a new source for reading from a variable format file (Read From Variable Format File) 

and a new sink for writing to a variable format file (Write to Variable Format File). Variable format files 

have these characteristics: 

• Records in the file may have different fields, and different numbers of fields. 

• The first field in every record must contain a tag (usually a number) identifying the type of record. 

• Fields within a record must be separated by a delimiter such as a comma. 


• Hierarchical relationships are supported. 

• All records have a record delimiter (usually CRLF). 

The following example shows a variable format file containing information about checking account 

activity for two customers, Joe Smith and Anne Johnson. 

001 Joe,Smith,M,100 Main St,555-234-1290 

100 CHK12904567,12/2/2007,6/1/2012,CHK 

200 1000567,1/5/2012,Fashion Shoes,323.12 

001 Anne,Johnson,F,1202 Lake St,555-222-4932 

100 CHK238193875,1/21/2001,4/12/2012,CHK 

200 1000232,3/5/2012,Blue Goose Grocery,132.11 

200 1000232,3/8/2012,Trailway Bikes,540.00 

Pivot Tables 

The Group Statistics stage has been updated to perform pivot table calculations. A pivot table aggregates 

and transposes column values in the dataflow to make it easier analyze data visually. With pivot, you 

can arrange input columns into a cross tabulation (also known as crosstab) that produces rows, columns 

and summarized values. 

Oracle Data Type NVARCHAR2 

Spectrum Technology Platform now supports the Oracle data type NVARCHAR2. 

Performance Improvement for Write to DB 

You can now specify the number of records to commit in a batch when using the Batch commit option 

in Write to DB. In previous releases, the batch size was fixed at 100 records. By using the new Batch 

size option you can specify a batch size that optimizes the commit performance for your particular situation. 

For information about this new option, including the factors to consider when choosing a batch 

size, see the Spectrum Technology Platform User's Guide. 

Note: The Batch size option can improve the performance of writing data to a database. However, 

many factors can affect the overall performance of your dataflow. For information on obtaining 

the best performance from your dataflows, see the Spectrum Technology Platform Performance 

Tuning Guide. 

Create Table in Write to DB 

You can now create a table in the target databases from within Write to DB. 

Visual Query Builder in Read from DB 

Read from DB now provides a visual query builder, which allows you to create complex queries without 

having to write SQL. You can build queries with different join types, build queries with sorting, grouping 

and complex criteria, and build queries with different server-specific options. 

Read From DB Limit Increase 

The Read From DB stage now supports viewing more than 2,000 tables. 

Note: 

Release Notes 

To implement this new functionality, please contact technical support. 

Release Notes 

5

Enterprise Geocoding Module 

Full Screen Script Editing in Transformer 

The Transformer stage now provides a full-screen script editor which makes it easier to work with larger, 

more complex Groovy scripts. 

Import/Export Source & Sink Settings 

The Read from File and Write to File stages now include the option to import and export settings from 

the File Properties tab, the Fields tab, and the Sort Fields tab. Use the Export function to save the configuration 

for your current dataflow, and use the Import function to bring in that configuration to another 

dataflow. 

When you export settings from a Read from File or Write to File stage, the data is saved into an XML 

file. The schema for that file is provided in the Read from File and Write to File sections of the Spectrum 

Technology Platform User's Guide. 


6 

Geocoding Support for New Countries 

The following countries are now supported for geocoding: Chile, China, Estonia, Greece, Hong Kong, 

India, Indonesia, Latvia, Lithuania, Macau, The Philippines, Russia, Slovakia, and Slovenia. To geocode 

locations in these countries, you must license the geocoding database for the respective country. For 

more information, contact your account executive. 

Legacy Geocoders No Longer Supported 

The legacy country-specific geocoding stages are no longer supported. The country-specific geocoding 

stages are those with names that end in a country code, like Geocode Address BRA, Geocode Address 

CAN, Geocode Address FRA, and so on. If you have dataflows that use these stages, you must update 

your dataflows to use Geocode Address Global before upgrading to Spectrum Technology Platform 

8.0. If you need assistance updating your dataflows please contact technical support. 

Note: 

There are two exceptions to the end of life for legacy geocoding stages: Geocode Address GBR 

and Geocode Address AUS will continue to be supported. 

Support for New Centrus Data Format 

As you may have read in the Centrus data release notes and in previous communications, the April 2012 

Centrus data release introduced a new data format which provides better performance, improved geocoding 

accuracy, and improved match rates. 

Note: 

As previously communicated, the old data format will be available until November 2012. At that 

time you must either apply this product update to your 7.0 installation or upgrade to 8.0 in order 

to continue using the latest Centrus data. 

New G-NAF Geocoding Options 

If you use G-NAF data for Australian geocoding, two new options are available: 

Point Type (API: 

GNAFPointType) 

For street address matching, specifies whether to return the parcel latitude/longitude 

or the street frontage latitude/longitude. This option is available only if 


Return 8 decimal 

places of parcel latit- 

ude/longitude (API: 

Return8DecimalPlaceParcelLatLong) 

you have the G-NAF database installed, and the database selected in the 

Database list on the Data tab includes the G-NAF database. This option only 

affects addresses matched to the G-NAF database. 

One of the following: 

Parcel (API Value: 

P) 

Street frontage 

(API Value: S) 

In a street address match, return the exact location of 

the parcel. This is the standard G-NAF point which is 

the exact authoritative point returned by the G-NAF 

database. Default. 

In a street address match, return the street frontage 

point for the parcel. The street frontage point is 12.5 

meters from the front boundary of the parcel. Street 

frontage points are more suitable for routing applications. 

Specifies whether to return the original latitude and longitude, precise up to 

eight digits after the decimal. This is the latitude/longitude that the candidate 

matched to in the G-NAF database. These are the original coordinates directly 

from the G-NAF data prior to truncation or rounding. This option is available 

only if you have the G-NAF database installed, and the database selected in 

the Database list on the Data tab includes the G-NAF database. This option 

only affects addresses matched to the G-NAF database. 

New Australia Option to Prefer Postal Code Over City 

For Australia, a new option Prefer postal code over city (API: PreferPostalCodeOverCity) specifies 

whether to return a close match when the postal code and street match exactly but the city does not. If 

you enable this option, the City input field is ignored if the postal code and street address are an exact 

match. If you do not enable this option, there may be situations where street address and postal code 

input are an exact match but the city name is not, and close matches are not returned. 

For example, without this option enabled, the following input address would return no close matches: 

5 East St 

GLENROY VIC 3046 

With this option enabled, this same input address would return the following close match: 

5 EAST ST 

HADFIELD VIC 3046 

The API option takes one of the following values: 

Y 

N 

Yes, return close matches if the postal code and street address are an exact match and ignore 

the city input. 

No, do not return close matches if the postal code and street address are an exact match 

and the city is not. Default. 

HouseNumber Input Field 

A new input field, HouseNumber, provides a dedicated input field for the building number of an address. 

In most cases you can specify the house number as part of the address in the AddressLine1 input field. 

Release Notes 

Release Notes 

7


8 

However, you will get better parsing results for some countries if you put the house number in this field. 

For the best results, use the HouseNumber input field for these countries: India, Singapore, Malaysia, 

Thailand, and Turkey. 

Note: 

The house number specified in the HouseNumber field takes precedence over any house number 

specified in the AddressLine1 field. 

Reverse Geocoding for Great Britain 

This release adds support for reverse geocoding locations in Great Britain. You must license the Enterprise 

Geocoding Module - Great Britain Geocoding Database in order to use this new functionality. For more 

information, contact your account executive. 

Range Output 

Geocode Address Global now provides options for obtaining information about the ranges located on a 

candidate's street segment. The new options are located on the Matching tab in the Geocode Address 

Global stage. For API users, a new option, ReturnRanges, enables range output, while options 

MaxRanges and MaxRangeUnits specify the maximum number of ranges and unit ranges (for example, 

apartment ranges) to return. 

A new output field, Ranges, contains a list of the ranges on the candidate's segment. If any of the ranges 

are comprised of a building with multiple units (for example, apartments or suites) information about the 

unit ranges is also included. 

Geocode Address World - Support for First Quarter 2012 Data 

This release adds support for the First Quarter 2012 Geocode Address World data. This support was 

previously released as 7.0 S17. In order to use Spectrum Technology Platform 8.0 you must install 

the Q1 2012 data. Conversely, you must install the 7.0 S17 product update or upgrade to Spectrum 

Technology Platform 8.0 in order to use the Q1 2012 data. 

Geocode Address World - Country Input 

Geocode Address World now supports the three-character ISO code and country name in the Country 

input field. Previously only the two-character ISO country code was supported. 

Geocode Address World - State Abbreviations 

Geocode Address World now supports two-letter state abbreviations for Australia, Canada, Italy, Mexico, 

the Netherlands, and the United States. 

Geocode Address World - Single Line Input 

Geocode Address World now supports single line input. Single line input means you can enter the entire 

address in the AddressLine1 input field. For example: 

Am Fleischmarkt 20 Vienna 1010 Austria 


Enterprise Routing Module 

New Module: Enterprise Routing Module 

The Enterprise Routing Module includes all of the existing routing capabilities from the Location Intelligence 

Module. All stages and functionality have been moved to the new module. The Enterprise Routing 

Module provides the ability to obtain driving or walking directions, calculate drive time and drive distance, 

and identify locations within a certain time or distance from a starting point. 

Valid Routes Always Returned from Get Travel Cost Matrix 

Get Travel Cost Matrix now returns valid routes within the route matrix even if it cannot find a route 

between one or more start and end points in the matrix. For example, if you have start point A and end 

points 1 and 2, and Get Travel Cost Matrix can find a route from A to 1 but not from A to 2, Get Travel 

Cost Matrix will now return the route from A to 1. In previous releases no routes would be returned if any 

one route could not be determined. 

Location Intelligence Module 

MapInfo Spatial Server Integration into the Location Intelligence Module 

MapInfo Spatial Server has been fully integrated into the Location Intelligence Module. This provides a 

new suite of broadly applicable spatial capabilites through a set of remote services and access via REST 

and SOAP APIs. These location capabilites include mapping, map tiling, feature seraching, geometry 

calculations, WMS (web map), WFS (web feature), and CSW (catalog service). 

Location Intelligence Module Documentation Site 

To support the integration of MapInfo Spatial Server into the Location Intelligence Module, there is a 

new Spectrum Technology Platform Location Intelligence Module documentation site. This site provides 

documentation, samples, and utilities to help understand and utilize the new spatial capabilities added 

to Spectrum Technology Platform. 

The documentation site is located at: http://reference.mapinfo.com/software/spectrum/lim/8_0/index.html 

Routing Capabilites Removed from the Location Intelligence Module 

All routing stages and functionality have been removed from the Location Intelligence Module and have 

been added to the new Enterprise Routing Module. All existing routing capabilities from the Location 

Intelligence Module are still supported. 

Spatial Support for EPSG 3068 

Spatial services in the Location Intelligence Module now support coordinate system EPSG 3068 (DHDN 

/ Soldner Berlin). This coordiante system is a large scale topographic and statistical mapping, cadastral 

and engineering survey projection for Berlin, Germany. 

Release Notes 

Release Notes 

9

Management Console 


File Monitor 

A file monitor triggers a job or process flow when a control file that you create is detected in a monitored 

directory. The presence of this control file indicates that all files required by a particular job or process 

flow are in place and ready for processing. When the control file appears, the file monitor runs the job 

or process flow you specify. File monitors are useful in cases where there are other processes that create 

the files you want to use as inputs to a job or process flow. 

Custom Logs Removed 

In previous releases you could create user-defined logs to capture information about the dataflow and 

write it to a database table. As of this release, custom logs are no longer available. If you need to log 

information about job execution to a database, use the Write to DB stage. 

SAP Module 

Server 

10 

Web DynPro Support 

The SAP module now supports Business Partner (BP) functionality in Web DynPro (NetWeaver 7.01). 

You can create and update Business Partner Person records, Business Partner Organization records, 

and Business Partner Group records. 

In addition, you can perform the following actions: 

• Postal validation 

• Duplicate check 

• Address searching for addresses in the U.S. and Canada 

Support for ECC Enhancement Package 4 

This release adds support for SAP ECC Enhancement Package 4 (EHP4). 

French Address Validation 

The SAP module now supports address validation for addresses in France. 

Distributed Processing 

If you have a very complex job, or you are processing a very large data set such as one containing millions 

of records, you may need to distribute processing in order to achieve optimal performance. Spectrum 

Technology Platform can now be configured to distribute processing to multiple instances of the Spectrum 

Technology Platform server on one or more physical servers. To set up and configure a distributed 

environment, contact Pitney Bowes Software for information on a professional services engagement. 

Because of the complexity of such a setup, you should not attempt to set up distributed processing 

without consulting professional services. 

For more information about distributed processing, see the Performance Tuning Guide. 


Support for Windows Mapped Drives 

You can now use Windows mapped drives for dataflow input and output files, and for reference databases 

used by modules such as the Enterprise Geocoding Module and Universal Addressing Module. 

Siebel Module 

French Address Validation 

The Siebel module now supports address validation for addresses in France. 

Universal Addressing Module 

SNA Certification for French Addresses 

Validate Address has been certified by La Poste's Service National de l'Adresse (SNA). La Poste is 

France's postal authority. La Poste SNA is responsible for ensuring that all address data is correct and 

up to date. The organization also sets standards for how French and European addresses should be 

written (information, order, punctuation, alignment, and so on). 

There is no established postal discount for complying with SNA. However, there are several benefits to 

SNA certification: 

• Assurance that your mail will arrive at the recipient's address 

• Improved address quality in your data 

• Improved file exchanges between systems and organizations 

• Reduced or eliminated costs associated with returned mail 

To take advantage of SNA certified processing you must license three additional postal databases: 

HEXAPOSTE, HEXAIA and HEXACLE. For more information, contact your sales executive. 

CASS Cycle N Certification for U.S. Addresses 

Validate Address has been CASS certified for Cycle N by the U.S. Postal Service. 

Discontinued Support for 4-State Barcode 

The 4-State Barcode (also known as Intelligent Mail Barcode) functionality has been removed from 

Validate Address and is no longer supported in Spectrum Technology Platform. 

Support for 2012 First Quarter International Postal Database 

This release adds support for the 2012 First Quarter International Postal Database for the Universal 

Addressing Module. This support was previously released as the 7.0 S21 product update. 

Validate Address Global - AMAS Certification 

Validate Address Global is now certified by Australia's Address Matching Approval System (AMAS). It 

can now standardize and validate your mail against the Postal Address File, providing postal discounts 

and allowing for the least amount of undeliverable pieces. 

In order to take advantage of AMAS certification, you must install a Certified database. For more information 

on installing a Certified database, see the "Installing Validate Address Global Databases" section 

Release Notes 

Release Notes 

11


12 

of the Spectrum Technology Platform Installation Guide for your platform. For complete information 

on using a certified database, see the "Validate Address Global" section of the Spectrum Technology 

Platform User's Guide. 

AMAS certification affects the following: 

• Process options: You will now see "Certified" in the list of processing modes in the Validate Address 

Global stage in Enterprise Designer. 

• Output fields: You will now see the following output fields in a Validate Address Global dataflow in 

Enterprise Designer: AMAS.HouseNbr1, AMAS.HouseNbr2, AMAS.PostalDeliveryN, AMAS.RecordType, 

AMAS.ResultCode, AMAS.Status, and DPID. 

• Type options for database resources: You will now see "Certified" in the list of database types when 

adding a Universal Addressing database resource in Management Console. 

Validate Address Global - AddressType Output Field 

For United States and Canada addresses only, the new AddressType field indicates the type of address. 

One of the following: 

F 

B 

G 

H 

L 

M 

P 

R 

S 

U 

The address was validated/corrected to the firm name. 

The address was validated/corrected to the building name. 

The address is a general delivery address. 

The address was validated/corrected to the high-rise default. 

The address is a large volume receiver. 

The address is a military address. 

The address was validated/corrected to PO box. 

The address was validated/corrected to a rural route. 

The address was validated/corrected to a street address. 

The address could not be validated/corrected so the type is unknown. 

Validate Address Global - Parsing and Validation Enhancements for India 

With the new release the parser checks the Indian address elements against the reference data to verify 

their validity. The position of the elements within an address has little influence on the quality of the 

output result. For example, if the localities within a given address are exchanged, the results will be returned 

as validated correctly. 

Validate Address Global - Improved Japanese Address Processing 

This release contains significant improvements to the way Japanese addresses are processed and validated. 

Due to these changes, a new format for the Japanese database has been introduced. It should 

be noted that to benefit from the new improved functionality, customers need to download the new 

database for Japan. 

In addition, this release contains transliteration improvements, enhanced parsing, and improved 

formatting for Japanese addresses. 


Validate Address Global - Secondary Address Information in Fast Complete 

Validate Address Global now returns secondary address information when run in Fast Complete mode. 

Validate Address AUS - AMAS Certification 

Validate Address AUS is now certified by Australia's Address Matching Approval System (AMAS). It can 

now standardize and validate your mail against the Postal Address File, providing postal discounts and 

allowing for the least amount of undeliverable pieces. 

Universal Name Module 

New Name Variant Finder Options for Output Script 

The Name Variant Finder stage has new options that control the writing system used for the names returned. 

The new options are: 

• Romanized: Returns the Romanized version of the name. A Romanized name is one that has been 

converted from a non-Latin script to the Latin script. For example, Achin is the Romanized version of 

the Korean name . 

• Native: Returns the name in the native script of the name's culture. For example, a Korean name 

would be returned in Hangul. 

• Kana and Kanji: For Japanese names, these options control whether to return the Kana version of 

the name, the Kanji version of the name, or both. 

GenderDeterminationSource Field Renamed 

The Name Variant Finder input and output field GenderDeterminationSource has been renamed to 

Ethnicity. The field still contains the same data but the name of the field is different. The new field name 

more accurately reflects the meaning of the field, which is not limited to gender determination but is a 

reflection of the name's ethnicity. 

You must update any dataflows that contain the Name Variant Finder stage to use the new field name 

Ethnicity. 

Important: 

Fixed Issues 

If you do not update your dataflows to use the Ethnicity field instead of GenderDeterminationSource, 

your dataflows may fail to run. 

This release contains fixes for the following issues. 


• (CDQE-11629) ClassCast error with Best Of Breed. 

• (CDQE-15264) Interflow Match does not delete temp file. 

Release Notes 

Release Notes 

13



• (CDQE-10586) During a batch commit in the Write to Database stage, if the number of records is not 

evenly divisible by 100, the remainder does not get written to the database. 

• (CDQE-10657) Output files are locked when running a job a second time after opening the Write to 

File stage. 

• (CDQE-10964) When a column named "Date" is used in an Oracle database for the Write to Database 

stage, an exception is thrown when a string of date and time information is entered in that column. 

The server is not properly converting the type of data from string to an Oracle date. 

• (CDQE-13045): In Read from DB, the OK, Cancel, and Help buttons are not displayed correctly when 

using a high DPI display setting. These DPI settings now work: 

• Windows XP: Large size (120 DPI) 

• Windows 7: Medium - 125% 

Note: 

The fix in this release only supports screen resolutions of 1280x1024 and larger. Support for 

lower screen resolutions will be added in a later release. 

• (CDQE-13745): Complex typed values do not work correctly in Record Combiner. 

• (CDQE-3862) The custom transform Add Output field should have a Modify button. 


14 

• (CDQE-3464) Database loader for non-U.S. databases and for routing data can install the wrong 

country database into the wrong folder. 

• (CDQE-8538) Incorrect Status calculation when address information is missing. 

• (CDQE-10758) Geocode Address Global fails to geocode locations in Liechtenstein and Luxembourg. 

• (CDQE-10951) When defining a database resource, an error in any one resource path causes all paths 

in the database resource to be lost. 

• (CDQE-11131) When modifying a database resource, an error in a path causes the existing Geocode 

Address Global and Reverse Geocode Address Global stages to disappear. 

• (CDQE-11133) Certain addresses in Athens, AL cause Geocode US Address to crash. 

• (CDQE-11272) Exception when using Geocode US Address in Enterprise Designer or Management 

Console after setting the MatchMode to CASS. 

• (CDQE-11304) Geocode US Address error "Illegal argument exception" when geocoding an address 

in Center City, MN. 

• (CDQE-11381) Unable to access GeocodeUSAddress service after setting the match mode to CASS. 

• (CDQE-11887) Japanese geocoder always returns latitude/longitude in EPSG:4301. 

• (CDQE-13056) Geocode US Address returns incorrect city centroids. 

• (CDQE-13385) Geocode US Address JVM crashes with certain addresses when the match mode is 

set to "close". 

• (CDQE-13654) Reverse Geocode US Location returns blank and/or meaningless characters in the 

Latitude and Longitude output fields and the incorrect address. 

• (CDQE-13727) Adding a country to an existing group of countries changes the options set by the user. 

• (CDQE-16028) Certain addresses put Enterprise Geocoding Module into a non-responsive state. 


Enterprise Tax Module 

• (CDQE-10010) On 6.4 servers with the C01 product update installed, and on all 7.0 servers, Calculate 

Distance returns the following error when run multiple times: "The server reported that the service ran 

successfully even though no output data was returned." 


• (CDQE-15140) "Too many open files" error when using Query Spatial Data. 

• (CDQE-13880) Strange travel directions between two points on the same street segment. 

GeoConfidence Module 

• (CDQE-6887) When using NAVTEQ data, the street segment points returned for geoconfidence types 

ADDRESS and POSTAL3 are incorrect. 


• (CDQE-6215, CDQE-10389, CDQE-13198) The number of days remaining in a license is incorrectly 

displayed in the Licensing window in Management Console when the computer's locale is set to a 

date format other than MM/DD/YYYY. 

• (CDQE-14053) No warning is given before a module license expires. 

SAP Module 

Server 

• (CDQE-11073) The HouseNumber field contains part of the street address. 

• (CDQE-12689) Some region codes are not defined for France in SAP ECC 6.0. 

• (CDQE-11248, CDQE-11249) Unable to get AccountID using Spectrum Technology Platform 7.0 

SOAP and REST web services. 

• (CDQE-11422) POX over HTTP requests in Spectrum 7.0 cause accountID/users to be mixed and 

interchanged incorrectly. 

• (CDQE-12500) Lists with a data type of "double" cause dataflows to fail. 

• (CDQE-13041) Authentication is attempted on every request to a Universal Addressing Module service, 

resulting in slow performance. 

• (CDQE-13828) ExpirationManager requires authentication on restart. 

• (CDQE-14397) Expiration notice email is empty. 

• (CDQE-14678) "Resource not found" error when trying to access the DCG Monitor. 

Siebel Module 

• (CDQE-3782) Default casing option for Siebel Standardize Name does not have an effect. 

• (CDQE-7618/00298078) Last name "Ma" being returned as "M.A." 

Release Notes 

Release Notes 

15


• (CDQE-10531) Solaris library missing in Siebel 8.1.1 Industry and Siebel 8.1.1 Business. 


16 

• (CDQE-140/CR 1-31857433) Apartment label is incorrectly parsed as street suffix. 

• (CDQE-141/CR 1-31857436) Validate Address returns multiple matches when the city and state are 

present. 

• (CDQE-1616/CR 1-32173003) Address in Turtle Lake, WI, is not matched and corrected. 

• (CDQE-2258/CR 1-28989760) An address in Inglewood, CA, returns an "S" in the StreetSuffix.Result 

field. 

• (CDQE-2264/CR 1-19525709) Universal Addressing Module is unable to match an address in Williamsburg, 

VA, even though the address exists in the USPS database. 

• (CDQE-2280/CR 1-29452802) The PostalCode.Type output field contains a "P" for all addresses in 

the ZIP Code 55085. 

• (CDQE-3496/1-32640983) Address in Riopiedras, PR, causes segmentation violation. 

• (CDQE-5634/00274641) Military abbreviations are returned in mixed case. 

• (CDQE-6302) Address in Stillwater, OK, returns incorrect ZIP + 4 code. 

• (CDQE-7657/00303171) For some addresses that are LACS/Link converted, the PostCode.Result 

field contains "C" for "corrected" even though the original postal code is retained. 

• (CDQE-8573/00316190) A valid address in the ZIP Code 54005 fails to match. 

• (CDQE-10439) Providing a firm name causes DPV to fail. 

• (CDQE-10461) FirmName.Result = C when no firm name was input. 

• (CDQE-10514) Validate Address changes the house number even though the house number is correct. 

• (CDQE-10585) Different results from multiple occurrences of the same address. 

• (CDQE-11143) City name Pago Pago is returned in mixed case. 

• (CDQE-11155) When using Validate Address Global with the option Return input data with results 

enabled, only .input fields are being returned. 

• (CDQE-11156) When using Validate Address Global, .input fields are being returned even though the 

option Return input data with results is disabled. 

• (CDQE-11525) Address in Astoria, NY returns a different DPV code if the "#" symbol is included. 

• (CDQE-11692) The CASS 3553 report double-counts records with a LACS Link code of 14. 

• (CDQE-12646) For some US address, the Validate Address output field "Additional Input Data" contains 

duplicate information with address lines. 

• (CDQE-12759) Validate Address changes house number. 

• (CDQE-13102) Validate Address Global does not return complete PO Box information when using 

Fast Completion mode. 

• (CDQE-13748) Addresses produce inconsistent results. 

• (CDQE-14029) UAM is not returning data for certain addresses. 

• (CDQE-14378) For an address in Pittsburgh, PA the result varies depending on whether the suite information 

is in AddressLine1 or AddressLine2. 

• (CDQE-14402) Firm name extraction not being cleared between requests. 

• (CDQE-14612) Address in Schaumburg, IL, returns different confidence codes. 

• (CDQE-14726) DPV license cannot be disabled when seed record is encountered. 


Known Issues 

This release contains the following known issues. 

Memory Access Violation When Installing Databases 

When installing the Enterprise Tax Module's GeoTAX Subscription File or the Universal Addressing 

Module's U.S. Postal Database on Windows or Linux you may encounter an error similar to the following: 

Memory access violation. 

COBOL error at 000000 in \G1DBLOAD.acu 

On Windows, there are two ways to fix this issue. The first option is to do the following: 

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 and 

add wrun32.exe located in C:\Program Files\Common Files\Group1\Runtime. You 

should now see ACUCOBOL-GT 32-bit Runtime listed. 

6. Click OK. 

The second option for fixing this issue on Windows is to set the system-level environment variable 

USE_EXECUTABLE_MEMORY to TRUE. 

To correct this error 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. 

Address Now Module 

• (CDQE-12471) Validate Global Address parsing logic does not work correctly in cases where Address- 

Line1 contains apartment information. 

• (CDQE-3368) The apartment number is placed in the ApartmentLabel output field. 

• (CDQE-3367) The PostalCode and PostalCode.AddOn output fields are missing this ZIP + 4 digits. 

• (CDQE-3366) The Confidence field contains a value of 100 even if the address was not validated. 

Release Notes 

Release Notes 

17


• (CDQE-2533/CR 1-32277245) Documentation does not describe the differences between the Japan, 

Japan2, and Japan3 datasets. 

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


• (CDQE-438) Express Match Identified field not being populated for a particular match collection when 

using the Sliding Window matching option. 

Data Normalization Module 

• (CDQE-3939) When a culture-specific grammar is used, all of the culture's RegEx rules are appended 

to the end of the grammar, whether they are used or not. 

• (CDQE-3936) In the Open Parser Domain Editor, the OK button in the Grammar Editor is disabled 

after modifying culture properties. 


• (CDQE-15012) When using Visual Query Builder with an Oracle database, JOIN with a USING clause 

does not work. 

• (CDQE-14974) When using Visual Query Builder, the aggregate function result does not display in 

the correct data type. 

• (CDQE-10386) Unmarshalling error occurs when adding a dataflow option to a job that's used in a 

process flow. To work around this problem, go to the process flow and open the Run Program stage. 

Delete the variables on the Variables tab of the Run Program Options window. Save the PF, add the 

variables back, and then save again. 

• (CDQE-6372) Defining a schema type that is the same as an existing complex type causes problems. 

• (CDQE-5696) In a process flow, using a slash in an activity name causes the following error: "cannot 

find the path specified." 

• (CDQE-3925) Read from DB, Write to DB, and Query DB allows duplicate alternate field names to be 

saved despite error message. 

• (CDQE-3864) In a transformer, if a custom output field is deleted, an error occurs when trying to readd 

the field. 

• (CDQE-420) Read from File preview fails when server and file are on computers with different operating 

systems. 


18 

• (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-13575) Geocode US Address cannot geocode some addresses verified by Validate Address 

Global. 

• (CDQE-12121) Incorrect address match when the input street number is missing and a secondary 

address is supplied. 

• (CDQE-11678) For Geocode US Address, unable to set ZIP or geographic centroid fallback in CASS 

mode. 

• (CDQE-11552) Various addresses causing Geocode US Address to fail. 

• (CDQE-11407) Certain addresses in Thailand not getting geocoded. 


• (CDQE-9919/00319252) Spectrum 6.4 cannot geocode addresses that CDQ Platform 5.7 could. 

• (CDQE-9916) Some postal codes in the U.K. that start with a digit cause StringIndexOutOfBoundsException 

error. 

• (CDQE-9699/00334935) Two German addresses cause JVM errors in the server log. 

• (CDQE-9573/00334040) Incorrect longitudes for Guam. 

• (CDQE-8700) Segment ID field is not long enough for MultiNet values. 

• (CDQE-7602/00288936) Address in Sweden geocodes to postal centroid instead of a street. 

• (CDQE-7121) The New Zealand geocoder returns an undocumented field named NZL.KEY_UFI, which 

can be seen with the dataflow inspection tool in Enterprise Designer. 

• (CDQE-7029) A null value in a tab file causes Canadian addresses to fail geocoding. 

• (CDQE-6913/00280120) House numbers for some French addresses unexpectedly change on output. 

• (CDQE-6912/00263629) Some German addresses fail to match to known house numbers. 

• (CDQE-4927/00265134) Multiple matches are not returned for E030 match code. 

• (CDQE-4744/ 00262333 ) Geocode US Address returns error: "Service problem. Method setData() 

failed." 

• (CDQE-4448/0026425) Geocode Address AUS fails with the error "MapMarkerException: 

java.lang.NullPointerException." 

• (CDQE-4278/00256985) Street name for a Washington D.C. street address is not recognized when 

the address elements are in the incorrect order. 

• (CDQE-4222/00257507) Geocode Address SGP times out. 

• (CDQE-2865/CR 1-14724429) The match code is not consistent with DPV footnotes for an address 

in Chico, CA. 

• (CDQE-405) Database resources with paths longer than approximately 60 characters cause the 

server to hang. 

Enterprise Tax Module 

• (CDQE-71/CR 1-21142578) A "connection reset" error message occurs in Assign GeoTAX Info. 


• (CDQE-12040) Querying SHP files does not work if the SHP file is in British National Grid. 

• (CDQE-3887) The Location Intelligence Module database resource tool allows invalid database paths. 


• (CDQE-9596/00316647) Problems connecting to Oracle databases. 

• (CDQE-3056) Clicking the help button causes abnormal behavior. 

• (CDQE-3033) File servers with special characters in their names cannot be modified. To work around 

this issue, delete the file server then create a new one without using special characters in the name. 

SAP Module 

• (CDQE-3858) SAP Batch Validate Address and SAP Validate Address With Candidates does not indicate 

a save flag when the default database is automatically selected. 

Release Notes 

Release Notes 

19

Server 

Server 

• CDQE-15003) Temp files are not deleted if java.io.tmpdir fills up. 

• (CDQE-7204) Long jobs cause the following error: "SocketException: Software caused connection 

abort: socket write error." 

• (CDQE-6894) Changes to an external web service in Management Console cause dataflows that use 

the service to unexpose without warning. To work around this issue, re-expose the dataflow. 

• (CDQE-5672/00275370) Unable to write to an Oracle date/time field. 

• (CDQE-3844) External REST service fails when an encoded URL is used. 

• (CDQE-412/CR 1-30647509) Remote components do not follow logging level setting. 

Spectrum API 

• (CDQE-4851/00263144) Cannot import data into Oracle using the Java API. 


20 

• (CDQE-15973) Address in Heeney, CO, does not DPV confirm. 

• (CDQE-15363)Validate Address Global cannot validate an address if "Minton Place" is included. 

• (CDQE-14095) Receive NullPolinterException upon first call to ValidateAddress after increasing the 

instance count. 

• (CDQE-13573) For a Canadian address, Get Candidate Addresses returns the address range in two 

separate records with different variations of the street name. 

• (CDQE-12375) Address fragments appearing in AdditionalInputData output field. 

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

NY. 

• (CDQE-10714) Database installer references CODE-1 Plus. 

• (CDQE-10298) Apartment number being dropped for address in Tacoma, WA. 

• (CDQE-10138/00270942) For Canadian addresses, when unit information and street address are 

separated by a hyphen, "Unit" is returned in both AdditionalInputData and AddressLIne1. 

• (CDQE-9682/00334806) Unable to validate address in Elmwood Park, NJ that contains a hyphen in 

the house number. 

• (CDQE-9374/00280948) Congressional district not being returned for address in Montana. 

• (CDQE-8527/00315190) Invalid address in Canada causes the job to fail. 

• (CDQE-8489/00315177) Address in Toronto, ON, results in FirmName.Result=V even though no firm 

name was used on input so there was none to be validated. 

• (CDQE-8454/00314943) Get Candidate Addresses casing option does not work when just a postal 

code is input. 

• (CDQE-8449/00313107) For U.S. rural route addresses that are LACS/Link converted, the output field 

USLACS contains "N" for not converted. 

• (CDQE-8438) Validate Address is not returning the ISO country name for Lao People's Democratic 

Republic and Côte d'Ivoire. 

• (CDQE-7654/00303170) For addresses that are LACS/Link converted, the output fields xxxx.Input 

contain the corrected address instead of the input address. 

• (CDQE-7583/00297285) Dropped address information not being returned in AdditionalInputData field 

when using LACS/Link conversion. 


• (CDQE-7229) The following error occurs when using Validate Address: G1PARSER Lookup Table 

Name Not Found: FRLINE. 

• (CDQE-6665/00286900) For an address in Laurel, MD, a valid postal code is returned in the Could- 

NotValidate field. 

• CDQE-6356) Receive a null pointer exception when performing multiple match. 

• (CDQE-5088/00268474) Non-ASCII characters not handled correctly for non-U.S. addresses. 

• (CDQE-4875/00259152) When dual address logic is set to prefer the street address, an address in 

Kenosha, WI, does not match to the street. 

• (CDQE-4186/00256804) Address in Laval, QC, causes "Invalid or missing database" error. 

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

when enabled. 

• (CDQE-3150/CR 1-32540113) Address on S Doheny Dr, Los Angeles, CA, is incorrectly matched to 

ZIP Code 90089-0001. 

• (CDQE-2531/CR 1-32391188) An address in Richmond, ON, causes a segmentation violation. 

• (CDQE-2281/CR 1-30019270) A unique ZIP Code logic problem exists when no city is provided. 

• (CDQE-2276/CR 1-14859431) ST. ANNE street in Sudbury, ON, is incorrectly coded. 

• (CDQE-2274/CR 1-15518343) "Lamar Blvd." in Austin, TX, incorrectly codes to "LaMar". 

• (CDQE-2271/CR 1-17369063) An address in Lang, BC, does not properly correct to 199 ST. 

• (CDQE-2270/CR 1-17369069) The city and street of an address in Peterborough, ON, does not get 

corrected. 

• (CDQE-2269/CR 1-17369087) An address in Bramton, ON, which is missing a space between the 

street name and street type, does not get corrected to include the space. 

• (CDQE-2268/CR 1-17842931) Corrected house number "120R" is not recognized as a replacement 

for "120", and the corrected street name "6th" is not recognized as a replacement for "6" for an address 

in Cranbrook, BC. 

• (CDQE-2267/CR 1-17999195) With mixed casing enabled, cities such as "La Habra" are returned as 

"LA Habra". 

• (CDQE-2263/CR 1-27305941) ApartmentLabel.Result and ApartmentNumber.Result incorrectly have 

"V" when DPV is used. 

• (CDQE-2262/CR 1-28373918) Street suffix "ST" is improperly included in an address in Rock Hill, SC. 

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

• (CDQE-2260/CR 1-28886291) An invalid address in New York, NY, is successfully coded even though 

it should not code. 

• (CDQE-2259/CR 1-28900721) PostalCode.Result reflects only the five-digit ZIP Code, ignoring the 

ZIP+4. 

• (CDQE-2255/CR 1-29112009) The Empire State Building address returns StreetSuffix.Result=A. 

• (CDQE-2253/CR 1-29770488) 303 Baron St does not match to 303 Barron St. 

• (CDQE-2221/CR 1-32320665) For non-matched addresses, Validate Address returns the English 

translation of the post-directional. 

• (CDQE-1479/CR 1-32117119) Fractional addresses not being parsed correctly in parsed output. 

• (CDQE-503/CDQE-5506/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 dropped when 

placed in AddressLine2. 

• (CDQE-457/CR 1-31481513) For an address in Oklahoma City, OK, Validate Address returns a C 

(corrected) result code even though the address is unchanged on output. 

• (CDQE-358/CR 1-31900754) With the option "keep multiple matches" enabled no data is returned for 

an address in Toronto, ON. 

Release Notes 

Release Notes 

21



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

• (CDQE-5386/00272154) Incorrect name parsing and gender assignment. 

• (CDQE-1468/CR 1-32095140) When the input contains two personal names, the first with a middle 

name and the second without, the Name Parser is duplicating the first person's middle name to the 

second person's middle name. 

Compatibility 

• You can upgrade to Spectrum Technology Platform 8.0 from Spectrum Technology Platform 7.0 

and 6.4. If you have a version previous to 6.4 installed, uninstall Spectrum Technology Platform 

before installing this release. 

• .NET 4.0 is required to run Enterprise Designer, Management Console, and Interactive Driver. 

• Spectrum Technology Platform API compatibility: 

• JDK 1.6 is required to install the Client API. Be sure that JDK 1.6 is in the PATH environment variable. 

Once installed, the Client API supports JDK 1.4 and greater. 

• The Spectrum Technology Platform .NET API is compatible with .NET 1.1 and later. 

• iSeries platforms support the Client API in Java only. 

Operating Systems 

22 

Server 

The Spectrum Technology Platform server is supported on these operating systems: 

• AIX 6.1 1 

• AIX 7.1 

1, 2 

1, 3 

• HP-UX 11.31 (Itanium) 

• Solaris 2.9 (SPARC only) 1 

• Solaris 2.10 (SPARC only) 1 

• Red Hat 5 4 

• Red Hat 6.1 with the following required packages: 4 

• Linux Standard Base 

1 

The Universal Address Module components Validate Address AUS and Validate Address Global are not 

supported on this operating system. 

2 

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

3 

The following modules are not supported on HP-UX Itanium: Address Now Module, GeoConfidence 

Module, Location Intelligence Module. 

4 

The Universal Addressing Module component Validate Address AUS is not supported on this operating 

system. 


• glibc.i686 glibc-devel.i686 

• zlib.i686 zlib.x86_64 zlib-devel.i686 zlib-devel.x86_64 

• libstdc++.i686 libstdc++-devel.i686 libstdc++-devel.x86_64 

• compat-libstdc++-33.i686 compat-libstdc++-33.x86_64 

• SUSE 10.0 4 (requires glibc-2.4-31.2 which is approximated by the standard SUSE 10.1 distribution) 

• SUSE 11.1 4 (requires glibc-2.9) 

• Windows 2003 Server 

• Windows 2008 Server 

Client 

Spectrum Technology Platform clients (Enterprise Designer, Management Console, and Interactive 

Driver) are supported on these Windows platforms: 

• Windows XP 

• Windows 7 

API 

The Spectrum Technology Platform API is supported on the same platforms as the server. 

Geocode Address World Database Compatibility 

Geocode Address World is compatible with the March 2012 data and later. 

Universal Addressing Module Canada Data Compatibility 

If you are upgrading to Spectrum Technology Platform 8.0 from version 6.4, note that the Universal 

Addressing Module Canadian postal database used in version 6.4 is not compatible with version 8.0. 

You must install the latest Canadian postal data and update your database resources in Management 

Console to point to the updated data. 

Supported Versions of SAP and Siebel 

This release of Spectrum Technology Platform adds support for: 

Web DynPro Java 7.01 

The complete list of supported versions of SAP and Siebel follows. 

Release Notes 

SAP CRM 6.0 Module 

SAP CRM 7.0 Module 

SAP ECC 5.0 Module 

SAP ECC 6.0 Module 

Siebel Enterprise 7.8 Module 

Siebel Business 8.0 Module 

Siebel Business 8.1.1Module 

Siebel Industry 7.8 Module 

Release Notes 

23

Location Intelligence Module Support 

Siebel Industry 8.0 Module 

Siebel Industry 8.1.1 Module 

As of this release SAP CRM 5.0 Module is no longer supported. 

Location Intelligence Module Support 

Database 

The Location Intelligence Module supports the following spatial databases for use with the spatial services, 

data, and resources: 

• Oracle 10 and 11 

• SQL Server Spatial 2008 

• PostGIS 1.5.2 

Browser 

The Location Intelligence Module spatial client development and samples support the following browsers: 

• Microsoft Internet Explorer 8 and 9 

• Mozilla Firefox 10 and 11 

• Safari (Mac OS X) 

• Chrome 17 and 18 

Installation Notes 

For complete instructions on installing Spectrum Technology Platform, including system requirements, 

see the Spectrum Technology Platform Installation Guide available on the Spectrum Technology 

Platform DVD and the technical support website. 

Upgrading Clients 

When you upgrade to Spectrum Technology Platform 8.0 you must re-install the Enterprise Designer, 

Management Console, and Interactive Driver. 

Upgrading Location Intelligence Module 

24 

When you upgrade the Location Intelligence Module or a previous version of MapInfo Spatial Server to 

Spectrum Technology Platform 8.0 it is important to backup data sources and resources prior to upgrading. 


Upgrading from Previous Location Intelligence Module Version 

Prior to upgrading, you should backup your data definition directory which stores all of the property files 

that have the data source information. This folder is located in the %install_home%/server/modules/spatial/data 

directory. 

Any data located inside of the existing Spectrum Technology Platform installation directory will be deleted 

after upgrade. If data is located in these directories, backup any data and copy to the same location in 

the Spectrum Technology Platform 8.0 directories once upgraded. 

Upgrading from Previous MapInfo Spatial Server Version 

When upgrading, the installer will create a backup of the previously installed MapInfo Spatial Server repository. 

This backup is located in the %install_home%\server\app\repository\backup\spatial 

directory. 

Permissions set on named resources in the repository will not get migrated to the new version. All named 

resource will have default permissions after upgrade. The admin user will have full permissions, and all 

other users will have read only permissions. 

Client Installer Consolidation 

In previous releases there were three separate installers for Enterprise Designer, Management Console, 

and Interactive Driver. With this release, there is now one installer that installs all three. You can choose 

which clients to install during the installation process. 

Note: 

You must uninstall your current clients before installing the 8.0 clients. 

Operating System Patches 

Before installing Spectrum Technology Platform, be sure to apply all the latest patches and updates 

available for your operating system, especially those that fix issues with Java. 

If you use the Data Normalization Module database load utility on HP-UX, be sure that you have applied 

the HP-UX 11.31: PHSS_37202 update in order to avoid an issue. 

Reverse Geocoding Database Upgrade 

If you use Reverse Geocode US Location, you must rebuild the reverse geocoding database after upgrading. 

To do this, delete your existing .gsx files then run the batchind utility. For more information, see 

"Installing Enterprise Geocoding Module Databases" in the Spectrum Technology Platform Installation 

Guide. 

RDI Database Update 

If you are upgrading from a previous release and use the Universal Addressing Module to perform residential 

delivery indicator (RDI) processing, you must re-install the RDI database using the database installer 

included with this release. RDI processing will not work unless you re-install the RDI database. 

For instructions on installing the RDI database, see the Spectrum Technology Platform Installation 

Guide. 

Release Notes 

Release Notes 

25

Arabic Plus Pack and Asian Plus Pack 

Arabic Plus Pack and Asian Plus Pack 

64-bit Required for Arabic Plus Pack and Asian Plus Pack 

Arabic Plus Pack and Asian Plus Pack databases are no longer supported on 32-bit computers. You 

must use a 64-bit computer when using these databases. 

Installing Arabic Plus Pack Data 

Arabic Plus Pack data is used by the Advanced Matching module for handling data in Arabic. The Advanced 

Matching Module database load utility currently does not support the Arabic Plus Pack. To install 

the Arabic Plus Pack, copy the file g1-cdq-cjki-arabic-7.0.jar to /modules/server/modules/tables/ext. 

You do not need to restart the server. 

Installing Enterprise Tax Module Databases on Unix or Linux 

The procedure for installing Enterprise Tax Module databases on Unix and Linux has been updated to 

avoid an error that can occur if the database is larger than 2 GB. If you are installing a database larger 

than 2 GB, type the following commands at the command prompt before installing the database: 

export LARGE_FILE_LIMIT_2TB=1 

export USE_LARGE_FILE_API=1 

For complete instructions on installing Enterprise Tax Module databases, see the Spectrum Technology 

Platform Installation Guide. 

JVM Performance Tuning 

26 

There are JVM options that will yield performance gains with certain hardware. These are advanced 

options and can cause unexpected behavior when used incorrectly (possibly even JVM crashes). We 

recommend that you contact technical support if you want to explore increasing performance by tuning 

the JVM. 

• On multiple CPU computers the -XX:+UseParallelGC option can be added to improve GC processing. 

• We have also seen performance increases by adding these options, although on some hardware they 

have been known to cause JVM crashes. 

• -Xmn512m 

• -XX:+AggressiveOpts

software/spectrum/lim/8_0/pdf/Spectrum_8.0.0_ReleaseNotes

Create successful ePaper yourself

Delete template?

Save as template?