TOLERANT Post Release 9.0

2018/12/03

Notices

  • The deprecated profile attribute geoCodes was removed. Please use the new attribute geocodingType to configure the usage of gecoding data.
  • A version v1 was added to the package name of the Java API classes. If you are using the Java API for your integration of Tolerant products, please adjust the package names accordingly.
  • Request ID parameter for bulk requests will now be read as string. Since the request Id is stored in the database, you are advised to deleted the bulk database (TLDATA/bulk) and restart the service, so the new database table structure could be generated.
  • The question, whether batch should be installed, is not relevant for the installation and will be skipped from the installer script.
  • Starting with version 9.0 of Tolerant Post, the product needs a valid license file to start. Please contact our support team to get a license file suitable for your use case. Please note that the functionalities in postLicense used to check the unlock-codes, were moved to the new CLI-Tool postEngineUnlockCodes.
  • Improved and more strict validation of lines in csv-files. Characters after the „enclose character“ are now interpreted as errors, which could lead to possible validation errors in configured normalizer- or synonym-files.
  • Updated English Manuals

New Product Features

Configuration and Administration GUI

  • Changed sort sequence to „alphabetical“ for the input file path
  • GUI fields for all boolean values are now shown as drop boxes.
  • The abort button for batch process in the Admin GUI will stay activated even if the stopPort is not set in the configuration. Using the abort function without setting the stopPort results in an error message.
  • Overwriting and adding new fields in the GUI input view now supports auto-mapping of the added fields.
  • License file status and content can be viewed in the Admin GUI.

Batch

  • The question, whether batch should be installed, is not relevant for the installation and will be skipped from the installer script.

Service

  • A version v1 was added to the package name of the Java API classes. After this change, the usage of different API versions of different Tolerant products is possible.
  • The database table for the request logging can now be automatically created using the number of columns configured in the runtime attribute reqLogDbNrCols.
  • Start, Stop and reconfigure of a project does not require setting the service in maintenance mode.
  • Following changes were made to simplify the usage of the java API:
    • In case of an exception, the exception will be attached as cause to the APIException
    • API retries can be configured using the java property: com.tolerantsoftware.api.maxRetries
    • The check for stale connections and the period of this check can be configured using the java property: com.tolerantsoftware.api.staleCheck
    • The error message: Response contains failure was extended to include the return code from the service response and the causing error message.
  • Request-id can now be set using a new constructor for the connection object.
  • Bulk search requests are now processed simultaneously to better utilize cpu’s available cores.
  • The JVM trust store is now created under TLCONFIG/truststore/cacerts
  • Installer creates the keystore for jetty in the pkcs#12-format.

General

  • The deprecated profile attribute geoCodes was removed. Please use the new attribute geocodingType to configure the usage of geocoding data.
  • New attribute geocodingType was added to post profile. The new attribute has one of the following values:
    • NONE: geocoding is not activated
    • STANDARD: standard geocoding reference
    • ARRIVAL_POINT: arrival point geocoding
    • PARCEL_CENTROID: parcel centroid geocoding
    • ROOFTOP: rooftop geocoding
  • Please note that the new geocoding types need an unlock code and a new reference data.
  • Post can now be configured to deliver the new 6-digits postal code for an old address in South Korea.
  • A micro version was added to all Tolerant products. The micro version is set to the patch number.
  • postEngineUnlockCodes now validates the state of the validation engine to get a more specific error message.
  • The bundled JRE was upgraded to the latest Java security patch (Java 8 Update 191)
  • Tolerant Post now uses a license file to control the used volume and the validity period of the product. The product cannot be started without a valid license file.
  • Tolerant Post now ships with the new AddressDoctor library (5.13.0)
    • Improvements:
      • Improvements to the assignment of IRIS codes to France addresses.
      • Improvements to the supplementary reference data for France
      • Verification of street names for Sweden addresses was improved
      • Support for arrival point geocoordinates in addition to interpolated geocoordinates
    • Bugfixes:
      • Australia: A slash between the house number and the subbuilding will now be retained in the output address.
      • United States: Both spellings Indianapolis and Indianápolis are now recognized as valid city names.
  • License tool returns a description text for the available modules.
  • Single line address validation is now implemented in Tolerant Post.
  • Tolerant Post now supports the V4 of AddressDoctor Cloud web interface. Following features are supported with the new version:
    • The new profile attribute: geocodingType
    • Single-Line address validation
  • Updated English Manuals

Fixed Bugs

Configuration and Administration GUI

  • TPR-4890: Environment variable substituation in the Admin GUI can now be used for all integer fields.
  • TPR-5149: Reflection problem is fixed, which has resulted in a misleading exception in the GUI trace file.
  • TPR-5167: The security right translitrules.check was missing from the default ADMIN role.
  • TPR-5169: The automatic codeset detection will no be triggered when a new synonym file is selected.
  • TPR-5244: The validation of the codesets in the Admin GUI was corrected, so that codesets with ‚_‘ can be selected.
  • TPR-5245: A new check to prevent errors from occurring when adding service input fields and setting length handling to none
  • TPR-5410: The Admin GUI now reports an error when the same character is used as separator, escape and quoting character.
  • TPR-5479: File perview now shows fields of type date (D) correctly.
  • TPR-5819: Description was missing for some Post internal fields
  • TPR-5820: Uniqueness check for the sortOrder attirubte of service output fields was not deactivated when sortMode is NONE.
  • TPR-5884: Extra check to prevent request redirect if a link points to a non-existing file.
  • TPR-6281: The Admin GUI resolve paths relative to Tolerant paths (TLCONFIG, TLDATA ..ect)

Batch

  • TPR-4808: Batch summary no longer generates invalid json protocols.
  • TPR-5157: The calucation of return codes percentage was corrected.
  • TPR-5561: The configuration checker verifies, that different outputFieldmap items are referenced in the output switch.
  • TPR-5805: For batch process a default logger will be added for missing log elements.
  • TPR-6265: Database errors occurring during a Batch process are now written in the log files and shown in the statistic output.

Service

  • TPR-4606: A change was made to the service start script so that a root user cannot start the service.
  • TPR-4699: Request ID parameter for bulk requests will now be read as string.
  • TPR-5089: A service inactive project can now be reactivated and started from the administrative GUI.
  • TPR-5403: It is now allowed to left a service input field of type ‚D‘ empty.
  • TPR-5514: Tolerant Service now stops all its cron jobs, so that it can be deployed in tomcat without thread leaking problems.
  • TPR-5592: Default values were not taken into consideration when building the json response.
  • TPR-5624: The requirement of msvcr100.dll being installed into the os for registering the product as a windows service has been dropped as we have included this into the installation.
  • TPR-5703: Extra check was implemented to cover the case, that an admin command could be called for an unknown project.
  • TPR-6251: Temporary jetty files are execluded from the installation consistency check.

General

  • TPR-4921: Upgrade process now doesn’t overwrite the hostname in tolerantEnv that was entered during the installation.
  • TPR-4979: Post installer now asks whether the service example should be installed.
  • TPR-5085: Silent installation now checks whether the backup-path can be created, otherwise the installation breaks with suitable error message.
  • TPR-5140: The uniqueness of profile name and rule name will now be validated correctly.
  • TPR-5154: The rolloverMode attribute of the log-element now overrides the value set in the logging-element.
  • TPR-5212: Useful messages logged from different CLI tools were not outputted to the console
  • TPR-5224: Frequency metric is now better dimensioned to get as few false positives as possible.
  • TPR-5596: Improved and more strict validation of lines in csv-files. Characters after the „enclose character“ are now interpreted as errors, which could lead to possible validation errors in configured normalizer- or synonym-files.
  • TPR-5656: Changes were implemented to cover the case when single line validation is missing an unlock-code.
  • TPR-5822: Searching for a street StaB code no longer ignores the entered city as a fallback.
  • TPR-5902: The following metrics are now project-specific:
    • Pipeline.Time.
    • Pipeline.RemainingQueueCapacity.
    • Pipeline.ActivityMessages.
    • Pipeline.FailureMessages.
    • Pipeline.WarningMessages.
  • TPR-5921: Update reference job updateRefDataSchedule can now be reconfigured correctly. Both ON_START and ON_STOP can now be used for Batch process.
  • TPR-6074: A change was made to the return code calculation, so that the delivered return code is now restricted to the validation level’s relevant codes.
  • TPR-6241: The installer now logs only the components that were installed.
  • TPR-6334: Address enrichment with AGS code now uses a build-in synonym replacement for cities abbreviated names.

Known Bugs

  • Currently no known bugs.

Archived release notes