MapMarker USA v25.1 Release Notes

Transcription

1 MapMarker USA v25.1 Release Notes United States: Phone: Fax: Sales: Government Sales: Technical Support: Technical Support Fax: pbinsight.com These Release Notes accompany the MapMarker USA v25.1 release. This provides information on new features, behavioral changes in the software, fixes for customer-reported issues, and known issues that may require your attention. These Release Notes are also available on the Pitney Bowes Software web site. Related MapMarker documentation appears on the MapMarker Product Documentation page on the Pitney Bowes Software web site. The USA v25.x documentation appears under the USA heading. Release Notes may be updated as new information becomes available. Any updated Release Notes will be posted to the web site with an indication of the revision date. Canada: Phone: Fax: Sales: Technical Support: Technical Support Fax: pbinsight.ca Europe/United Kingdom: Phone: Fax: Technical Support: pbinsight.co.uk In these release notes: MapMarker USA v25.1 Features and Enhancements MapMarker USA v25 Features and Enhancements Operating Requirements Fixes to Known Issues Installation-Related Configuration and Tomcat Integration Known Issues and Clarifications Asia Pacific/Australia: Phone: Fax: Technical Support: pbinsight.com.au 2012 Pitney Bowes Software Inc. All rights reserved. MapInfo, Group 1 Software, and MapMarker are trademarks of Pitney Bowes Software Inc. All other marks and trademarks are property of their respective holders. November 2012

2 MapMarker USA v25.1 Features and Enhancements Following is a summary of the updates that are you will see with the MapMarker USA v25.1 release. Updated Dictionaries Improved License Management Tool Updated Dictionaries By default, the TomTom Streets address dictionary is included with MapMarker USA v25.1.you can also purchase and license supplemental address dictionaries. The following Address Dictionaries are available for use with MapMarker USA v25.1 and can be used within the same core engine. TomTom Street data (2012_10) TomTom Points data (2012_10) Centrus Points data (2012_10) NAVTEQ data (2012_10), available as a secondary address dictionary only. Updates are referred to by the month name, such as: MapMarker USA v October (2012_10) data update. You can receive quarterly or monthly updates for any licensed address dictionary. The Centrus Points, TomTom Points, and NAVTEQ Address Dictionaries can be installed in their own data paths. See the Pitney Bowes Software web site for more detailed information on the U.S Geocoding Data Sets. Contact your Sales Representative for more information on purchasing additional data sets and for establishing an update schedule. Improved License Management Tool The key-based license management system was introduced with MapMarker USA v25. (See License Management System on page 3.) The License Assistant utility has been improved to enhance usability and facilitate the transfer of license files between you and the Pitney Bowes Software Customer Service group. The utility now generates a simple.txt file that you can to Pitney Bowes Software without the need to zip the file (as was previously required). The improved Licence Assistant utility is located on your software media under the licassist/<platform> folder, where <platform> represents either a Windows or UNIX platform. The licassist. txt file, located in the same folder, provides more detailed instructions on using the License Assistant utility. Note that temporary licenses are now good for 30 days. Previously they expired after 15 days. When you do get a permanent license, replace your temporary license and restart the application in order to activate the new license. If you fail to do so, the software will stop working when the temporary license expires. For more specific instructions on replacing your temporary or expiring license, see Activating a New Permanent License on page 14. MapMarker USA 25.1 Release Notes 2

3 MapMarker USA v25 Features and Enhancements Following is a summary of the updates that were introduced with MapMarker USA v25 in May These features are summarized here for convenience and are fully covered in the appropriate sections of the MapMarker 25 User Guide and in the MapMarker 25 Developer Guide. MapMarker USA v25 features are described in the following topics: License Management System REST Architecture API Updated Desktop Application Advance Notification for Software and Data License Expiration Improved Help About Dialog Performance Improvements License Management System Beginning with MapMarker USA v25,pitney Bowes Software is introduced license management based on software keys. This will allow you and Pitney Bowes Software to accurately track the licensed software that is installed and running. Each license file will be associated with a System ID. Your Sales Representative should provide you with valid license files before you receive your software media. Under some circumstances, you may have received a 30 day temporary license. When you do get a permanent license, replace the temporary license and restart the Server or Desktop application in order to activate the new license. Otherwise, the software will stop working when the temporary license expires. MapMarker USA software will also stop working if your data expires. If your Sales Representative did not send you a license file or if you need a new one, your media includes the command line License Assistant utility. You can use that utility to generate a license file request. Your media also includes a LicAssist.txt file that explains how to run the License Assistant utility. These files are located on your media in the following locations: License Assistant Utility Location Platform File Name and Description Location Windows UNIX LicAssist.exe license assistant utility licassist.txt instructions for running License Assistant utility licassist license assistant utility. licassist.txt instructions for running License Assistant utility <root>\licassist\windows\ directory on the software installation media. <root>/licassist/platform/ directory on the software installation media, where platform identifies your UNIX platform. For Solaris platform, the locations are: <root>/licassist/solaris/2.9/ and <root>/licassist/2.10/. If you have any difficulty in using the license file, the Pitney Bowes Software Customer Service group will be prepared to answer your questions and assist you. The software key implementation does not replace other licensing schemes. Product feature licensing, data licensing and expiration terms, CASS, DPV, and LACSLink licensing are not affected by this license management system. MapMarker USA 25.1 Release Notes 3

4 MapMarker USA V25 also introduced a new data format. See New Data Format with MapMarker USA on page 4. Running the License Assistant Utility If you installed MapMarker USA v25, your existing license is valid for the v25.1 upgrade. If you changed hardware or are licensing different data, you will have to create and point to a new license as described in this section. If you need to run the License Assistant, copy the LicAssist.exe (or licassist for UNIX platforms) from the media to a writable area on your local machine, for example to your Desktop folder or the root of your C:\ directory for a Windows platform. For Windows, navigate to where you copied LicAssist.exe on your local machine. Double-click to launch it. For UNIX systems, open a prompt and navigate to the directory where you copied licassist. Grant execute permissions to the licassist.exe file, then run the utility. $./licassist When you run the License Assistant utility, it generates the license request file (system.machinename.txt file). this file to Pitney Bowes Software Customer Service. In return , you will the receive the license file (.lic file) specific to your machine. For MapMarker USA v25.1, the License Assistant utility generates a simple.txt file. Previously the utility generated an.inf that had to be zipped before sending to Customer Service. This is no longer necessary, and you can the system.machinename.txt file without zipping it. Your MapMarker USA v25 license file will be named as follows: mmusa_<machinename>.lic Copy the license file into a local folder on your machine. During the MapMarker USA v25.1 graphical installation procedure, the Licensing dialog will prompt you to enter this license file. For silent installation, copy the silentinstall.properties file (located on your media) and edit the LICENSE_FILE= entry to include the new license file. Run the silent installation as described in the MapMarker USA v25 User Guide. You cannot use an existing MapMarker USA v24 license file. Only a v25 license file can be used to run MapMarker USA v25.1. If you are doing a shared Desktop application installation (Windows platform only), each client machine server must have its own MapMarker license file. See Shared installation Accessing and Running Client Desktop Installer on page 16 for more information. If you do not have a valid v25 license file, the MapMarker Desktop application displays an appropriate error message when you attempt to install or start the application. See the topic "Troubleshooting License File Errors" in the Installing MapMarker chapter of the MapMarker USA User Guide for detailed information on the possible error messages. New Data Format with MapMarker USA MapMarker USA v25 uses a new data format. The older format is available (on request only) for the October 2012 data. After October 2012, the older data format will not be available. Customers must upgrade to MapMarker USA v25 software to support the new data format, and this requires the software key-based license management system. MapMarker USA 25.1 Release Notes 4

5 Reverse Geocoding The MapMarker USA v25 Server supports reverse geocoding. If you provide X/Y (Longitude/Latitude) coordinates, the geocoder returns the closest address for the given X/Y location. Reverse geocoding is available with the Developer (Server) edition only. Reverse geocoding is not implemented in the Desktop application and is not available with User Dictionaries. Reverse geocoding is also separately licensed and must be covered in your license agreement. The ReverseGeocodeAPI interface includes classes and methods that support reverse geocoding. See the Developer Guide for relevant information on reverse geocoding. The Javadocs includes complete coverage of the reverse geocoding classes and methods. Basic support and configuration for reverse geocoding You can configure MapMarker USA v25 to perform reverse geocoding using a different street segment or point dictionary. Follow these guidelines: The spatial index (gsx files) must be built with all the dictionaries that you want to potentially use for reverse geocoding. That is, if you want the TomTom Streets and Centrus Points dictionaries to be available for reverse geocoding, both of these address dictionaries must be specified with the batchind command line program that generates the gsx files. See Building spatial index files with the batchind program. The gsx folder that includes spatial index gsx files must reside under the Data folder. If you add or remove a dictionary from your data path, you must rebuild the gsx files to support reverse geocoding. Similarly, if you update to a newer data vintage of an address dictionary, you must regenerate the gsx files. If multiple dictionaries are available, the closest possible match is returned regardless of which point or street segment dictionary produced the candidate. See Dictionary sources for reverse geocoded candidates. Building spatial index files with the batchind program Decide what dictionaries you want to use for reverse geocoding. You must then use the batchind command line program to generate the spatial index files (gsx files). The batchind program is installed with your software in the <install>\sdk\additional_tools\batchind folder. The specific name of the batchind program varies slightly for Windows or non-windows platforms. UNIX users must grant execute permissions to the batchind file before running the program. The batchind program creates a gsx folder and files based on the address dictionaries specified in the searchpath. If you attempt to reverse geocode using different data dictionaries than were specified with batchind, reverse geocoding will fail. If you intend to use reverse geocoding, create and use a unique gsx folder and files for each combination of address dictionaries that you use. Building all the index files takes anywhere from several minutes to several hours, depending on the machine you use to make the files. If you machine is slow, you may wish to run batchind.exe overnight. The generated GSX files takes up several hundred megabytes of hard drive space. MapMarker USA 25.1 Release Notes 5

6 Using command line arguments with batchind: You can open a command prompt and run the batchind program from where it was installed. On UNIX platforms, grant execute permissions to the batchind file before running. Specify your searchpath and outputdir and run batchind as follows: batchind <searchpath> <outputdir> Batchind Syntax Input searchpath outputdir Description The full datapath. That is, the path where the us.gsd and ust.gsd files reside. The Finmbr.dat file associated with the address dictionary must also be present in this folder. Delimit multiple search paths with a semi-colon (;). For non-windows platforms, use a colon (:) as a path delimiter. The full output path (including the gsx folder) where the gsx files will be created. By default, this is the searchpath/gsx folder. A space delimits searchpath from outputdir. When running batchind from the command line, you can enclose searchpath and outputdir in quotes so that a space is not misinterpreted as a delimiter between the paths. For example, assume that your TomTom Data folder includes the Finmbr file and you have a separate folder for Centrus Points (CPoints) data. From the <<install>\sdk\additional_tools\batchind folder, run batchind from the command line as follows: c:\program Files\MapInfo\MapMarker_USA_v25\sdk\additional_tools\batchind> batchind "c:\program Files\MapInfo\MapMarker_USA_v25\MapMarker_USA_v25_Data\TomTom ";"c:\program Files\ MapInfo\MapMarker_USA_v25\MapMarker_USA_v25_Data\CPoints" c:\program Files\ MapInfo\MapMarker_USA_v25\MapMarker_USA_v25_Data\gsx This creates the gsx files based on the TomTom and Centrus Points address dictionaries. the gsx folder is created if it did not already exist. If you copy and run batchind from the data folder (for example from: C:\Program Files\MapInfo\ MapMarker_USA_v25\MapMarker_USA_v25_Data, you can simplify the syntax as: batchind././gsx Using an INI file with batchind: You can create a batchind.ini file in the directory from which you run batchind. The batchind.ini file should have two entries to specify the searchpath and outputdir. The searchpath and outputdir are described in Batchind Syntax. searchpath=<datapath> outputdir=<output path> Do not use quotes for INI file search paths. When you run the batchind executable, it will look for and use the batchind.ini file in the same directory as the executable. On UNIX platforms, remember to grant execute permissions to the batchind file before running. A sample file named batchind.txt is installed in the batchind folder. During installation, this sample file is populated with your searchpath (based on the location of your data) and the outputdir (searchpath/gsx). You can use this sample batchind.txt file as a model for a batchind.ini file. Dictionary sources for reverse geocoded candidates MapMarker USA reverse geocoding returns the closest possible candidate that it finds from all of the available dictionaries, regardless of whether it was from a point or street segment dictionary. The candidate must be available within the search distance. By default this is 150 meters. If you change the search distance constraint (setdistance method of the RevereseGeocodeLocation class) this can affect the reverse geocoded candidate that is returned. The street and corner offsets (setstreetoffset and setcorneroffset methods) can affect the exact house number that you get if the candidate comes from a street segment dictionary. MapMarker USA 25.1 Release Notes 6

7 MapMarker Server can also return identifying information on the datasource for each candidate. This information is returned by the getdbtype method of the USA_UserCandidateAddress class. For example: cand.getdbtype() The returned DBType identifies the data source for the reverse geocoded candidate. For more information, see the Using the Java MapMarker API chapter of the MapMarker USA v25 Developer Guide for the topic on Returning Database Source Information. Reverse Geocoding Result Codes Reverse geocoded candidates return R result codes. The first three characters of the R result code indicate the type of match found. R geocode results include an additional letter to indicate the dictionary from which the match was made. This is always an A, indicating Address Dictionary. Reverse Geocoding Result Codes Sample Georesult Code RS8A RS5A RS4A Description Point level precision. Candidate returned from a point dictionary (such as Centrus Points or TomTom Points). Street address match. Candidate returned from Address Dictionary. Street centroid match. Candidate returned from the Address Dictionary. For the following input coordinates, a close match candidate is returned from a street segment with a result code of RS5A. X: Y: See the MapMarker USA v25 Developer Guide for relevant information on reverse geocoding. REST Architecture API MapMarker USA introduced a new REST (Representational State Transfer) API. REST is a lightweight client/server architecture that allows you to easily send and receive geocoding requests and responses via HTTP. The MapMarker USA. REST API also supports USA-specific constraints (related to CASS, DPV, LACS Link, Search Level, Wide Search, etc.) The REST API is also documented as an HTML page. After you start the MapMarker USA Server, follow these steps to view the HTML. 1. Access the MapMarker USA program group and select the MapMarker USA Server page. 2. A page appears with the URL for your server page. Select that URL. 3. From the next page, select the REST API link in the MapMarker Documentation category to launch the REST API HTML page. There is also a link for MapMarker USA API that opens the Javadocs for the API specification. Updated Desktop Application The Desktop application has been updated to improve visual appeal and usability. This includes improvements to the main application window and common dialogs. MapMarker USA 25.1 Release Notes 7

8 Advance Notification for Software and Data License Expiration The MapMarker USA Desktop application issues improved and more timely early warning messages to inform you that your software or data licenses are nearing the expiration date. Beginning 30 days before expiration of software or any data, you will receive a message notifying you about the upcoming expiration. This notification appears in the startup splash screen, status bar, and Help About dialog. Note that your data expires five months from the USPS data vintage month. For example, October, 2012 vintage data is valid through March 31, 2012 and expires on April 1, This does not affect CASS data, which is valid for 105 days from the 15th of the vintage month. When your software license expires, the software will stop functioning. If you receive new licenses for any reason (for example, if you receive your permanent license to replace a temporary one), make sure you replace the old license on your system. See Activating a New Permanent License on page 14 for details on that procedure. You must then restart the application in order to activate the new license. Otherwise, your MapMarker USA application will stop working when the old license or data expires. MapMarker USA software will also stop working if your data expires. Improved Help About Dialog The Help > About MapMarker dialog has been redesigned and now shows data source and vintage information. This also shows notification messages for software and data license expiration. If you are not using the Desktop application, you can verify the data vintage by opening the dictionarydesc.properties file in any text editor. By default, this is located in <install>\mapmarker_usa_v25_data. Performance Improvements MapMarker USA v25 ships with JVM v1.6, which offers performance improvements over the older JVMs. See JVM Requirements on page 9. MapMarker USA v25 ships with Tomcat 6.0. Previous versions shipped with Tomcat 5.5. See Supported Web Application Servers on page 10. Operating Requirements This section describes the hardware, memory and other requirements for MapMarker USA v25.1. Hardware and Memory Requirements The minimum system requirements for MapMarker on a full installation of the Desktop Application and MapMarker SDK are: Dual Core processor or better 4 GB RAM 10 GB available disk space MapMarker USA 25.1 Release Notes 8

9 For optimal performance we recommend more processing power. Many factors can affect performance, including network speed, hardware, number of concurrent users, number of address/user dictionaries, geocoding preferences, and quality of input addresses. Supported Operating Systems MapMarker USA runs on both 32-bit and 64-bit operating systems. The 32-bit versions will run on any supported 64-bit machine. To run as a true 64-bit application, you must use the appropriate Geostan 64-binary file. These binaries are installed with your software. For information on how to configure MapMarker USA for 64-bit systems, see Running on 64-bit Operating Systems on page 12. MapMarker runs on the following operating systems: Microsoft Windows XP Professional Microsoft Windows 2003 Enterprise Edition Microsoft Windows 2008 Server Microsoft Windows 7 Solaris 2.9 and 2.10 HP-UX 11x Red Hat Linux 4.0 and 5.0 SUSE Linux 9, 10 and 11 Desktop Application The Desktop Application runs on Microsoft Windows only. The Desktop is a 32-bit application, but runs on 64-bit Windows providing that 32-bit binaries are used. This works by default, because the installer always configures 32-bit binaries. Microsoft Windows XP Professional (32 and 64-bit) Microsoft Windows 2003 Enterprise Edition (32 bit) Microsoft Windows 2008 Server (32 bit) Microsoft Windows 7 (64-bit) JVM Requirements MapMarker v25.1 requires a Java Virtual Machine (JVM). MapMarker USA v25.1 ships with: JVM 1.6 JVM 1.5 is still supported. During the installation, you will have the option of installing the JVM that ships with MapMarker or using one that you already have installed on your computer. Note that if you install a 64-bit version of MapMarker USA v25.1 you must also use a 64-bit JVM. Database Support MapMarker USA v25.1 supports the following ODBC databases and drivers. SQL Server 2008 SQL Server 2005 SQL Server 2000 Microsoft Access 2007 (Link to download: driver for Microsoft Access 2007) Microsoft Access 2003 Microsoft Access 2000 MapMarker USA 25.1 Release Notes 9

10 MapMarker also supports the following Oracle drivers. Oracle 11 Oracle 10G Release 2 You must install the Oracle driver separately. To use the driver, you must have the Oracle client installed. Supported Web Application Servers The MapMarker server allows you to develop geocoding applications on any Java Platform, Enterprise Edition (Java EE) application server that supports JVM 1.5 or JVM 1.6. MapMarker USA v25.1 ships with: Apache Tomcat 6.0 Tomcat 5.5 is still supported. System Library Dependencies for UNIX Installations On UNIX/Linux systems, MapMarker USA requires standard system libraries that are used by the geocoding engine. While these standard libraries are available with every UNIX platform, they may not be found unless you install with the appropriate system option. To determine which system libraries are needed on your UNIX system, run the ldd (list dynamic dependencies) command, which will print shared library dependencies. For example, to identify the library dependencies for MapMarker USA 25.0 (which uses the engine), run: ldd <install_dir>/sdk/engine/bin/geostanmt.so This will return the MapMarker library dependencies for your UNIX system (Linux, Solaris, or HPUX). If you install the v25.1 update, the underlying geocoding engine is also updated (for example to ) Supported Pitney Bowes Software Products MapMarker USA v25.1 can integrate with the following products: Other MapMarker country products (Canada, Australia, etc.) MapInfo Professional MapInfo AnySite Envinsa MapMarker Geocoding Extender for Oracle MapMarker Geocoding Extender for SQL Server MapXtreme.NET version Fixes to Known Issues The following incidents were addressed in MapMarker USA v25.1 and previously in the July 2012 patch and in MapMarker USA v25. Fixes for MapMarker USA v25.1 Fixes Included from July 2012 Patch Update Fixes for MapMarker USA v25 MapMarker USA 25.1 Release Notes 10

11 Fixes for MapMarker USA v25.1 MapMarker USA v25.1 includes several fixes related to user dictionary behavior. There is also an important fix for locating the valid license file after a data vintage update. Upgrading data vintage invalidates license file. After upgrading the v25 data vintage (for example from April to July data). MapMarker USA generates a license file error. This problem has been corrected. The upgrade installation now preserves the USA_DataManagerSettings.properties file and points to the correct license file and custom user settings. Point user dictionaries are not returning complete Census information Point-based user dictionaries are not returning complete Census information with candidates. The Census Block field returns the first 5 numbers only, with the last 10 digits returned as zeroes. This has been fixed. There is still a problem with segment user dictionaries. See Segment user dictionaries are not returning complete Census information. on page 15 For user dictionaries, if a ZIP Code or city does not exist in USPS data, records on that street segment may not be returned. This problem has been fixed and invalid ZIP Codes or invalid city names no longer interfere with searching or returning candidates. An address with an invalid ZIP Code can still return a close match candidate, even if no city was mapped when building the user dictionary. This has been fixed. Fixes Included from July 2012 Patch Update The July, 2012 (vintage ) MapMarker USA v25 data refresh update included fixes for several issues. These fixes are packaged in MapMarker USA v25.1and are summarized here for convenience. When a point dictionary is loaded, the Desktop can crash after geocoding a table. When geocoding a table using a point dictionary, the Desktop application can crash after you click Done. This problem has been resolved. Desktop application can crash during interactive geocoding. During interactive geocoding it was possible to experience a Desktop crash. This problem occurred rarely, but has been fixed. When using the Find Address tool, the MapMarker engine fails to start. when you start MapMarker, the Find Address tool (findadd32.mbx) initializes as expected but when you try to use the tool an engine failure message appears. A new mbx has been provided and this problem no longer occurs. Opening an ODBC project file causes a crash. When you open a MapMarker project file that was created from an ODBC table, MapMarker USA crashes. Particular address causes system error and closes application. Certain addresses cause the Desktop application to crash. For example, the address 1100MLK APT 7 when entered with no space between the house number and the street name caused the Desktop to crash. This problem was fixed. During interactive geocoding, some intersection addresses produce an error message. When interactive geocoding, some intersection candidates produce an "corrupted memory" error message. The application does not terminate, but stops the remainder of the table from geocoding and displays the Results Summary dialog. This problem could occur if one or both of the streets in the intersection candidate is from an alias record. This problem has been fixed. Developer Guide updated on media. The Developer Guide PDF provided on your media has been updated. The original PDF provided on your media with the v25 release was missing the REST API content. The updated PDF has this complete content. Fixes for MapMarker USA v25 The following incidents were addressed in MapMarker USA v25 and are included here for completeness and convenience. User Dictionary in Relaxed Mode can cause a crash.when geocoding with a user dictionary in Relaxed Mode, some specific addresses could cause MapMarker to crash. This has been fixed. MapMarker USA 25.1 Release Notes 11

12 Exception when building user dictionary. When attempting to build a user dictionary with bad postcode data, the user dictionary build failed with an ArrayIndexOutOfBoundsException. This occurred in both the Desktop application and the user dictionary build utility. This problem has been fixed. Exact match not returned for 960 HC Mathis Drive and similar addresses. The letters HC in the address were sometimes mistakenly interpreted as Highway Contract. MapMarker now better distinguishes Highway Contracts from streets with the letters "HC" in them, and returns the exact match as expected. ZIP+4 entered in postcode1 input field returns a Z1 result instead of Z3. The correct 9-digit ZIP Code should return a Z3 match. This works properly when the entire Zip Code is entered as lastline or when the 5-digit ZIP is entered as postcode1 and ZIP+4 is entered as postcode2. But when the 9-digit ZIP Code was entered in the postcode1 input field, then a Z1 result was returned. This has been corrected and a Z3 result is returned. Installation-Related Configuration and Tomcat Integration This section provides some additional information regarding installation of MapMarker USA v25.1, including how to configure MapMarker USA v25.1 for a supported 64-bit operating system. Running on 64-bit Operating Systems Integrating Multiple MapMarker Countries Into One Tomcat Instance Running on 64-bit Operating Systems MapMarker USA includes the GeoStan 64-bit binaries but these binaries are not configured by default. Locate the 64-bit binaries in the appropriate Additional Tools > geostan_libs folder or your installation. For example, the linux 64-bit binary is (libgeostanmt.so) is located in: C:\Program Files (x86)\mapinfo\mapmarker_usa_v25\sdk\additional_tools\geostan_libs\linux64 A comparable 64-bit binary file is located in the aix64 folder. The solaris64 folder has 2.9 and 2.10 subfolders that contain the corresponding 64-bit binaries. The win64 folder contains libgeostanmt.so. You must use a 64-bit JVM to support your 64-bit MapMarker USA 25.1 application. To use MapMarker USA v25.1 as a 64-bit application, follow these steps. 1. Stop the MapMarker USA server, if it is running. 2. Install a 64-bit Java JRE if you have not already done so. 3. Make a backup of the file libgeostanmt.so by renaming it libgeostanmt.so.bak. (On Windows 64-bit systems, make a backup of Geostn64MT.dll.) This file is located in: <install_dir>/sdk/engine/bin/. 4. Locate the file libgeostanmt.so under <Install_dir>/additional_tools/geostan_libs/<platform> (file is named Geostn64MT.dll. on Windows 64-bit systems). Copy this file to <install_dir>/sdk/engine/bin/. 5. Make a backup copy of the Tomcat startup file in <install_dir>/sdk/tomcat/bin/startup.sh (UNIX systems). For Windows systems, the file is named startup.bat. 6. Open startup.sh (or startup.bat) in a text editor. 7. Update the path for JRE_HOME to the new 64-bit JRE that will be used. 8. If needed, edit the CATALINA_OPTS entry to increase the maximum memory usage. The default is 512m. MapMarker USA v25.1 will consume more memory in a 64-bit installation. 9. Save and close the startup file. 10. Restart the MapMarker USA server. MapMarker USA 25.1 Release Notes 12

13 Integrating Multiple MapMarker Countries Into One Tomcat Instance You can integrate multiple geocoders into one Tomcat instance. This allows you to use more that one geocoder with a single URL. The Developer Guide provided on your media also describes this integration strategy. For demonstration purposes, this section describes the integration of MapMarker USA v25.1 and MapMarker Canada v11.4 and assume that both products have been successfully installed. At a minimum, install the MapMarker server component and data for each country. The best strategy is to identify which country web application has the newest MapMarker Java core and integrate into that web application. This strategy will minimize the number of files that you have to copy. Determining the Java Core Engine To determine the core version, you need to examine the MapMarker Java Server Status for each country. After starting the MapMarker server, select MapMarker CTY v## Server from the MapMarker program group (for example, MapMarker USA Server). Then click the link that displays your machine name. Select the MapMarker Server Status link in the Administration category. The MapMarker Java Core version appears near the top of the status report. The country-specific MapMarker Java Plugin Version Information appears in the Product Specific Information category. After you examine both the MapMarker USA and MapMarker Canada server reports, you will know the core version number and build numbers for both products. For example: MapMarker Country MapMarker Java Core Version MapMarker Java Plugin Version (Build Number) MapMarker USA v MapMarker Canada v Since MapMarker USA v25.1 uses the newer core ( ), it is easier to integrate files from the CAN installation into the USA Tomcat. Now follow these steps: 1. Identify the USA and CAN jar files and properties files. By default, the locations are: <MM_USA_install>\sdk\tomcat\webapps\mapmarker40\WEB-INF\lib <MM_CAN_install>\sdk\tomcat\webapps\mapmarker40\WEB-INF\lib Copy the following files from the MapMarker CAN installation into the corresponding USA WEB-INF\lib\ folder: miscp.jar mmj_can.jar 2. You must also copy several properties and license files. By default, these are in: <MM_USA_install>\sdk\tomcat\webapps\mapmarker40\WEB-INF\classes\ <MM_CAN_install>\sdk\tomcat\webapps\mapmarker40\WEB-INF\classes\ Copy the following files from the MapMarker CAN installation into the corresponding USA WEB-INF\classes\ folder: CAN_DataManagersettings.properties MMCANLicenseFactory.config MMCANLicenseProvider.config MapMarker USA 25.1 Release Notes 13

14 3. Verify that the Tomcat server allocates at least 512 MB of RAM. Open catalina.bat (or catalina.sh for Solaris) in: <Install>\sdk\tomcat\bin and look for the entry: set CATALINA_OPTS= -mx512m -server The maximum heap size should be at least 512 MB. This should be adequate for most country integrations, but a heap size of 1 GB is recommended for optimum performance for a USA and CAN integration. 4. Restart the USA server and re-examine the Java Server Status report for USA as described in Determining the Java Core Engine on page 13. The Product Version Information shows the MapMarker Java Core version. The MapMarker Java Plugin Version Information near the bottom of the status report shows something similar to the following, confirming that both the USA and Canada products are installed in the same Tomcat. Plugin Version United States (USA) Canada (CAN) You can now geocode both American and Canadian addresses within the same Tomcat instance. Both geocoders will now use the same (USA) port number. Integrating other MapMarker Server products into a single Tomcat instance: You can use this same strategy to integrate any number of MapMarker servers into one Tomcat instance. First determine which installed MapMarker has the most recent core version. Then determine which country-specific files need to be copied into the target web server. (It may help to diff the contents of the...\web-inf\lib and...\web-inf\classes folders.) For each country you wish to integrate into an existing Tomcat, copy the country-specific jar, properties, and license files into the Tomcat with the newest MapMarker Java core. Performance of Tomcat integration strategy: Heap size of 512 MB is usually adequate, but 1 GB is recommended for optimum performance for a USA and CAN integration. On 32 bit systems, 1.5 MB is the maximum heap size. Larger heap sizes can be allocated on 64 bit systems. If you move country data: By default, country-specific data is located in directories named MapMarker_CTY_v##_Data (where CTY is the country identifies and v## is the version number). Each CTY_DataManagersettings.properties file (copied in step 2) includes a DICTIONARY_PATH# entry that points to the respective data file location. If you move country data to a different location, you must update the property file to point to the data location. Known Issues and Clarifications This section covers known issues and behaviors that require further explanation. Activating a New Permanent License You may receive a permanent license for several reasons. Most commonly, you will receive a permanent license to replace a temporary one. You also will receive a new permanent license if you renewed your contract of it there is a change to your contract agreement (for example, if you licensed additional states or supplemental data that was not covered by your previous contract). Remember, your MapMarker USA application will stop working when the old license or data expires. MapMarker USA 25.1 Release Notes 14

15 To activate the new license, follow these steps. 1. After receiving your new permanent license file, delete the temporary or old license file from the MapMarker Data folder and replace with the new one. C:\Program Files\MapInfo\MapMarker_USA_v25\MapMarker_USA_v25_Data Or for 64-bit machines: C:\Program Files (x86)\mapinfo\mapmarker_usa_v25\mapmarker_usa_v25_data If you are extending or changing your contract, the new license file may have the same name as your existing license file. However, because the license has a new contract expiration date (or other changes) you must still replace the old license file. 2. If you are using the Server product, open the server USA_DataManagerSettings.properties file in a text editor. This properties file is located in: C: \Program Files\MapInfo\MapMarker_USA_v25\sdk\tomcat\webapps\mapmarker40\WEB- INF\classes Or for 64-bit machines: C:\Program Files (x86)\mapinfo\mapmarker_usa_v25\sdk\tomcat\webapps\mapmarker40\web- INF\classes Edit the USA_DataManagerSettings.properties file to point to the full pathname of the new the license file. LICENSE_FILE=...NameOfLicense.lic 3. If you had a previous license for the Desktop product, make the comparable edit to the USA_DataManagerSettings.properties file located in the Desktop folder. (typically C:\Program Files\MapInfo\MapMarker_USA_v25\desktop). User Dictionary Issues Some issues related to user dictionary behavior have been resolved (see Fixes for MapMarker USA v25.1 on page 11). However, there are several outstanding user dictionary-related issues. User dictionary problem with geocoding to the correct side of the street. In a user dictionary, if a street segment has odd and even house numbers on the same side of the street (Parit y= Both) and all house numbers on the right side, then returned candidates will mistakenly be geocoded to the left side of the street. This issue has not yet been resolved. User dictionary may return unexpected city name. A candidate from a user dictionary may return an unexpected city name. This is because different city names may be associated with the postal data and the street segment data. In the past, the city name associated with the street segment data was preferred but this behavior has changed. This issue has not yet been resolved. Segment user dictionaries are not returning complete Census information. Segment user dictionaries are returning incomplete Census information with candidates. The Census Block field returns the first 5 numbers only, with the last 10 digits returned as zeroes. A similar problem has been fixed for point user dictionaries (see Point user dictionaries are not returning complete Census information on page 11) but the problem with segment user dictionaries has not yet been resolved. Creating a Point User Dictionary with the User Dictionary Utility The MapMarker USA User Dictionary Utility can be installed with the MapMarker USA Developer product. This utility simplifies the steps for creating user dictionaries. The utility displays a dialog indicating that point-based user dictionaries are not supported. This dialog is misleading. When you click Next and proceed past that dialog, you will still have the opportunity to create a user dictionary in which each street range contains a single point. MapMarker USA 25.1 Release Notes 15

16 To create a point-based user dictionary using the utility, the From Left and To Left columns for each record must have the same house number. You must then map the table input columns appropriately in the Required Columns dialog of the User Dictionary Utility. Required Column Mapping for Point User Dictionary UD Utility Entry Left Starting Address Number Left Ending Address Number Right Starting Address Number Right Ending Address Number Map To Table Column From Left input table column To Left input table column empty column empty column Follow these requirements and column mapping guidelines when creating a point-based user dictionary with the User Dictionary Utility. The source TAB file for your user dictionary must have an empty column. You will need this empty column for mapping purposes. To add an empty column to the TAB file, use MapInfo Professional and select Table > Maintenance > Table Structure > Add Field). Add this column before starting the User Dictionary Utility. The User Dictionary Type dialog indicates that point-based user dictionaries are not supported. However when you click Next and proceed past that dialog, you will still have the opportunity to create a user dictionary in which each street range contains one point. Map the Left Starting Address and Left Ending Address fields. The same house number must be in both the left and right fields for each record. Map the Right Starting Address and Right Ending Address to an empty column. Shared installation Accessing and Running Client Desktop Installer After the administrator installs the MapMarker USA Desktop application as a shared application (for Windows platform only), each MapMarker client user can install the Desktop application on their local machine. To perform this client installation, access the <install>mapmarker_usa_v25_data\desktopinstaller\ folder on the server machine and locate the following files: ClientSetup.exe client Desktop application installer Setup.INI INI file that specifies the data path The administrator must share the Data and DesktopInstaller folders so that client users can access these files. You can run the ClientSetup.exe to install the Desktop application on your local machine. See the MapMarker USA V25 User Guide for the Client Workstation Install topic. Each client must have a license file (received from your Sales Representative) in order to complete the installation. Microsoft Windows Administrator-Related Issues This section covers some administrator -related issues that are common to Microsoft Windows 2008 Server, and Windows 7. You must always have administrator rights on the target machine to install MapMarker. This is true on all operating platforms. Starting and Stopping the MapMarker Server: To start or stop the server using administrator credentials, right-click the shortcut for the operation that you wish to perform and from the menu that appears, select Run as administrator. If you did not install shortcuts, run the commands from an Administrator Command Prompt. MapMarker USA 25.1 Release Notes 16

17 To open an Administrator Command Prompt, access the Start Menu and select All Programs > Accessories. Right-click the shortcut titled "Command Prompt" and from the menu that appears, select Run as administrator. The command prompt that opens allows commands to be executed with administrator credentials applied. Installing and Removing the MapMarker Server as a Windows Service: To install or remove the server as a Windows Service, first open an Administrator Command Prompt. From the Command Prompt, run the commands to install or remove the service, as described in the topic Running the Web Application as a Windows Service in Chapter 2 of the MapMarker Developer Guide. Using ODBC Data source: You must have administrator privilege to create a new ODBC data source. The user also must set up their ODBC connections in advance. Reinstall Failure after Improper Uninstall: To properly uninstall MapMarker, you must run the Uninstaller. If you did not run the Uninstaller, but instead deleted the MapMarker directories, you will not be able to routinely re-install the product. Administrator Rights for UNIX/Linux Platforms On UNIX and Linux platforms, administrator rights are required in the following cases. Administrator Rights Required for Installation: For UNIX and Linux installations, you must have administrator rights on the target machine to install MapMarker. If you attempt to install on a machine where you do not have administrator rights, you receive an error message. Administrator Rights Required to Start Tomcat Server: On UNIX/Linux platforms, the Tomcat server must be started and stopped by a user with administrator rights. HP-UX Installation Issue During installation on HP-UX machines, the geoappl application (installed to $USER_INSTALL_DIR/sdk/additional_tools/geoeng/test/geoappl) may fail to start with error code If this happens, examine the file $USER_INSTALL_DIR/sdk/additional_tools/mme.profile and look for double occurrences of the path separator character ( : ) in the variable assignments. For example, if the path looks like: SHLIB_PATH=$SHLIB_PATH::/data/MapMarker_USA_v25/jre/lib/PA_RISC2.0:/... Edit this to remove the extra colon separator following PATH SHLIB_PATH=$SHLIB_PATH:/data/MapMarker_USA_v25/jre/lib/PA_RISC2.0:/... Log File for Cancelled or Failed Install When the installation fails or is cancelled, a log file is created that provides some insight into what happened. This is useful in the silent install scenarios (install, modify, update, or uninstall), because it directs the user to what must be changed. On Microsoft Windows, the log is created in the user s desktop folder by default. On UNIX/Linux systems, this file is created in the user's home directory or at the root directory ( / ). MapMarker USA 25.1 Release Notes 17