DE  EN 
Tel.: +49 711 490 448 50

Tel: +49 711 490 448 50

Kontakt

Release Notes 4.0

TOLERANT Match
Release 4.0, 2015/12/04

Notices

  • 32-Bit operating systems are no longer supported.
  • When upgrading an installation where https is used, a MANUAL(!) step is required to reimport the certificate into the java virtual machine. This step is documented in the „HTTPS“ appendix of the manual (section „USING JAVA API WITH HTTPS“). This step is necessary, as the upgrade does not know the keystore password used in previous installs.
  • The product ships with a newer embedded web server (jetty 9.3.3). The configuration of the server has changed, so that the server configuration now resides in $TLCONFIG/jetty-config. When upgrading, all web server configurations from the previous installation should be incorporated automatically into the new config.
  • A newer java virtual machine (1.8.0_66) is now bundled with the product.
  • The script to install a windows service using Apache Tomcat has been removed. If you still need this script, please write an email to support@tolerant-software.de
  • The temporary directories for the extracted web applications are now reused on startup.
  • Java API requires java1.6 or a newer version.
  • The feature to run the Match Client GUI with a local configuration file, configured through the installation path at menu „File–>Settings“ or the URL parameter „dir“, was removed.
  • The English manuals have been updated.
  • A bug fix (bug #2906, see fixed service bugs below) may require a new initial load of Match service data, because it influences partition number calculation. New initial load is required, if an initial load was carried out with Match release 3.0 using configuration tag ‚innerPartitioning‘ with ‚maxNumberPartitions‘ set to one of 3, 9, 10, 11, 22, 24, 26, 29, 30, 34, 41, 42, 48, 52, 53, 54, 55, 56, 57, 59, 61, 62, 68, 69, 70, 74, 77, 81, 82, 83, 85, 88, 92, 93, 98, 100, 101, 103, 108, 110, , 113, 114, 115, 117, 118, 119, 121, 122, 124, 125, 135, 136, 137, 138, 141, 142, 154, 155, 158, 161, 164, 166, 167, 170, 171, 173, 175, 181, 183, 184, 186, 187, 189, 194, 202, 205, 206, 211, 213, 216, 217, 219, 220, 223, 226, 227, 228, 229, 230, 234, 236, 237, 238, 239, 242, 244, 245, 247, 248, 252, 253. These numbers are valid for one dimension on Linux and Windows.
    If you are using multi dimensional partitioning and/or Solaris, other values of ‚maxNumberPartitions‘ are affected. Please contact support in this case. (since Match 3.1)
  • As for the bug fix mentioned above, calculation of partition numbers is now more precise in some situations than before. As a consequence new initial load of Match service data is required, if an initial load with Match release before 3.0 was performed using configuration tag ‚innerPartitioning‘ with three partitioning dimensions and ‚maxNumberPartitions‘ is one of 64, 125, 216.(since Match 3.1)

New Product Features

Configuration and Administration GUI

  • When a synonym list name at synonym editor is removed or renamed and these synonym list is referenced on an input or output field, a new popUp window is opened. There contains a list of all currently used removed or renamed synonym lists and ask if remove or rename the currents.
  • Match administration GUI shows an error popUp window to prevent deleting an input field, that is used for the partitioning.
  • All menu items for a service instance which requires that the running service must be on maintenance state gets a security query in a popUp window.
  • Adds the attributes „url“, „maxBulkSize“ and „tablePrefix“ as fields to database settings.
  • The logging settings was restructured to configure general logging settings. Under the tree item „Logging“, the general logging settings are shown with an additional field for the „anonymizeMethod“ attribute. Its child item „File logging“ shows the file logging settings. For the service runtime settings a second child item shows the request logging settings.
  • Adds logging settings for an initial load.
  • Adds the matchProfileField attributes „useAbbreviations“, „abbreviationScore“, „phoneticUsage“, „phoneticType“ and „maxScoreWeight“.
  • Default integer field width changed to the width of selection boxes.
  • Adds match project attributes „nrFullSavepoints“ and „protectedFullSavepoints“ to match service project settings under „Index backup settings“ tab. Furthermore the attributes „active“, „ekPartitionPrefixLength“, „ekPartitionCount“ and „language“ to the „Advanced settings“ tab.
  • A new tab „Cluster settings“ is added to match service project settings. He contains the attributes for „clusterMode“ and „maxHistoryDuration“.
  • The file selector dialog now shows directories followed by the files.
  • The project menu items „Start“ and „Stop“ at project view in a service instance are no longer deactivated.

Client GUI

  • The service configuration check before starting the Client GUI is no longer carried out by the client, but by sending an administration request to the Match service, if possible. If security activated then the configfile.check right is needed.
  • Projects which are not running at service, are removed from the project selection box, when the Client GUI is started.

Batch

  • No new features

Service

  • Bug #3017: When stopping the service using the service.sh script with the „stop“ option, additional parameters „–url <serviceurl>“ can now be used to use the save on shutdown with a given hostname/port.
  • The security settings can now be configured to use LDAP for authentification. More details can be found in the manual.
  • The service administration command reconfigure service was improved upon and expanded to include a force option. Please note that using the command with the extra force option could result in the indices becoming inconsistent. Therefore this option should be used with extra caution.(since Match 3.1)

General

  • A new command „check configfile“ is added to the matchAdmin tool, to get information about configuration warning and errors.
  • Individual set of normalization rules can be defined for each matchField in normalizer file. Set of rules are grouped in sections with names inside [] square brackets. These names are then referenced by individual matchFields. Any rules defined before all the named sections are grouped automatically under [DEFAULT].

Security

  • The rights „configfile.get“ and „project.state“ were added to the predefined „GUEST“ role at default security.xml. They were added to allow the use of Client GUI. But keep in mind that these rights are administrative rights, which can be a security issue.
  • Following rights were added:
    • configfile.check: Get configuration warnings and errors information form the administration service interface.
    • environment.get: Get defined environment variables.
  • When using https the following CipherSuites have been disabled by default, due to security problems:
    • SSL_RSA_WITH_DES_CBC_SHA
    • SSL_DHE_RSA_WITH_DES_CBC_SHA
    • SSL_DHE_DSS_WITH_DES_CBC_SHA
    • SSL_RSA_EXPORT_WITH_RC4_40_MD5
    • SSL_RSA_EXPORT_WITH_DES40_CBC_SHA
    • SSL_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA
    • SSL_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA
    • SSL_RSA_WITH_RC4_128_SHA
    • SSL_RSA_WITH_RC4_128_MD5
    • TLS_ECDHE_RSA_WITH_RC4_128_SHA

Performance

  • Batch execution performance has been improved.
  • Initial loader of Match Service has been improved: before fields were loaded successively. Now multiple fields are loaded in parallel. The number of fields corresponds to configuration attribute ‚threadCount‘. (since Match 3.1)
  • Batch execution has been improved: partitions were processed sequentially before. Now, as many partitions are processed parallelly as the number in attribute ‚threadCount‘. (since Match 3.1)

Miscellaneous

  • Nothing to report

Fixed Bugs

Configuration and Administration GUI

  • Bug #3177: Relative paths in a batch instance’s configuration was not resolved using the execution path.
  • Bug #3156: Auto correction for a invalid clean file output field map item, that has only indexRef and indexFieldRef but no inputRef and inputFieldRef attributes set, does not work well, so that saving such project configuration produces a configuration error.
  • Bug #3120: Sometimes no service or project state icon is shown for a product instance.
  • Bug #3035: Wrong validation message, if password field was not set for the runtime’s databases configuration.
  • Bug #3010: Creation of a service instance creates a 0 byte backup file if service has no configuration before.
  • Bug #2940: The attribute saveInterval was not loaded for the project settings and after a save it was removed from configuration file.
  • Bug #2909: Deletion of all input fields via context menu does not delete unmapped input fields.
  • Bug #2907: When edit or remove a synonym list name at synonym file editor, which is linked at an output field, the synonym list selection was not updated immediately.
  • Bug #2902: Saving a project with a new saveSchedule value removes all saveSchedule attributes from other projects.
  • Bug #2860: Warning icon at input or output mapping tree, is not shown when opening the mapping tab for the first time.
  • Bug #2850: Online help for the fields pattern attribute is insufficient.
  • Bug #2846: Synonym file validation at synonym file configuration tab does not check if the synonym file can be read.
  • Bug #2842: Saving index, runtime or project at a service instance sends the service unnecessarily into maintenance.
  • Bug #2840: The error handling tab for a Match service configuration is moved to the initial load settings from.
  • Bug #2834: Creating a service instance with no configuration sends the service unnecessarily into maintenance.
  • Bug #2811: Bread crumb caption at runtime settings contains runtime id instead of product instance name.
  • Bug #2805: Configuration of mongo database has marked user name as mandatory field.
  • Bug #2794: The result part of the execution dialog was shown with wrong language.
  • Bug #2792: „Input clean“ can be selected after add as first match method.
  • Bug #2723: In rare cases there is an internal error when list projects from a product instance.
  • Bug #2710: Wrong browser tab caption name.
  • Bug #2529: The max. length at input field definition was not set to 0 in case of the length handling „<None>“ switch.
  • Bug #2427: After project id changes at project settings a validation error occurred if project id is set back to the original value.
  • Bug #2228: Error message if service configuration contained errors was unreadable.
  • Bug #1517: Error messages on the wrong configuration file error popup window are not completely readable when the word exceeds the window width.
  • Bug #1008: Missing safety check for an existing service outputFieldmap, when opens the service project configuration.

Client GUI

  • Bug #3081: Exception at console, if user has security activated and no project.state right.
  • Bug #3003: After start the client, the spinner do not stop to spin.
  • Bug #2923: In rare cases there is an internal error after send a request to service.
  • Bug #2786: Wrong value(„null“) at log file output after reading the configuration from service.

Service

  • Bug #3133: Calling reconfigure runtime on a cluster member results in failure if serviceTimeout was changed.
  • Bug #2906: Wrong calculation of partition number for some values of ‚maxNumberPartitions‘ (inner partitioning only) (since Match 3.1)
  • Bug #2905: Results order for the getByKey search was not deterministic if wildcards were used. (since Match 3.1)
  • Bug #2903: Putting together the identifier for profiles in match kernel adds profile counter (0 based) in the end unnecessarily. (since Match 3.1)

Batch

  • Bug #3054: Match Batch ends with error if input file is empty.
  • Bug #2920: Internal error because of insufficient synchronization for parallel partition handling in Match Batch.
  • Bug #2797: Attribute outputRecordType in element <matchMethod> does not work correctly for the values „HEAD“ and „FOLLOW“. (since Match 3.1)

Installer

  • Bug #2925: Installation to paths with umlauts or other special characters failed.

General

  • Bug #3053: The attribute „allowEmptyResults“ for a synonymFile if set to „Y“ will now also revert a synonym replacement if the result is a string containing only of blanks.
  • Bug #2945: Missing matches for compare modes other than DICECOEFF and only one matching feature.

Known Bugs

  • No known bugs

Requirements

  • Please refer to the manual

Installation/De-Installation

  • Please refer to the manual

Release 3.1, 2015/07/29

Notices

  • A bug fix (bug #2906, see fixed service bugs below) may require a new initial load of Match service data, because it influences partition number calculation. New initial load is required, if an initial load was carried out with Match release 3.0 using configuration tag ‚innerPartitioning‘ with ‚maxNumberPartitions‘ set to one of 3, 9, 10, 11, 22, 24, 26, 29, 30, 34, 41, 42, 48, 52, 53, 54, 55, 56, 57, 59, 61, 62, 68, 69, 70, 74, 77, 81, 82, 83, 85, 88, 92, 93, 98, 100, 101, 103, 108, 110, , 113, 114, 115, 117, 118, 119, 121, 122, 124, 125, 135, 136, 137, 138, 141, 142, 154, 155, 158, 161, 164, 166, 167, 170, 171, 173, 175, 181, 183, 184, 186, 187, 189, 194, 202, 205, 206, 211, 213, 216, 217, 219, 220, 223, 226, 227, 228, 229, 230, 234, 236, 237, 238, 239, 242, 244, 245, 247, 248, 252, 253. These numbers are valid for one dimension on Linux and Windows.
    If you are using multi dimensional partitioning and/or Solaris, other values of ‚maxNumberPartitions‘ are affected. Please contact support in this case.
  • As for the bug fix mentioned above, calculation of partition numbers is now more precise in some situations than before. As a consequence new initial load of Match service data is required, if an initial load with Match release before 3.0 was performed using configuration tag ‚innerPartitioning‘ with three partitioning dimensions and ‚maxNumberPartitions‘ is one of 64, 125, 216.

New Product Features

Configuration and Administration GUI

  • No new features

Client GUI

  • No new features

Batch

  • No new features

Service

  • The service administration command reconfigure service was improved upon and expanded to include a force option. Please note that using the command with the extra force option could result in the indices becoming inconsistent. Therefore this option should be used with extra caution.

General

  • No new features

Security

  • The latest java virtual machine 1.8.0_45 is now bundled with the software.

Performance

  • Initial loader of Match Service has been improved: before fields were loaded successively. Now multiple fields are loaded in parallel. The number of fields corresponds to configuration attribute ‚threadCount‘.
  • Batch execution has been improved: partitions were processed sequentially before. Now, as many partitions are processed parallelly as the number in attribute ‚threadCount‘.

Miscellaneous

  • Nothing to report

Fixed Bugs

Configuration and Administration GUI

  • No bugs were fixed

Client GUI

  • No bugs were fixed

Service

  • Bug #2906: Wrong calculation of partition number for some values of ‚maxNumberPartitions‘ (inner partitioning only)
  • Bug #2905: Results order for the getByKey search was not deterministic if wildcards were used
  • Bug #2903: Putting together the identifier for profiles in match kernel adds profile counter (0 based) in the end unnecessarily

Batch

  • Bug #2797: Attribute outputRecordType in element <matchMethod> does not work correctly for the values „HEAD“ and „FOLLOW“.

Installer

  • No bugs were fixed

General

  • No bugs were fixed

Known Bugs

  • No known bugs

Requirements

  • Please refer to the manual

Installation/De-Installation

  • Please refer to the manual