TOLERANT Name Release 6.0

2016/11/10

Notices

  • The installer will now summarize all configured URLs for service and configured GUIs (if available) at the end of the installation.
  • In case of an (unlikely) OutOfMemoryError the product will now crash and create dump files.
  • The new administration command state database project-Id can be used to check the state of the project’s databases. If the project-Id was not entered, all databases will be checked.
  • Usage of a normalizer section name starting with a minus (-) is no longer allowed. Please replace the minus with another character.
  • The product ships with a newer embedded web server jetty 9.3.11.

New Product Features

Service

  • New admin command can be used to list all available metrics list metric. The value of the single metrics can be aquired using the admin command get metric.
  • The installer will now summarize all configured URLs for service and configured GUIs (if available) at the end of the installation.
  • All steps within the internal processing now report the size of the incoming queue as performance value in JMX.
  • In a service it is now possible to define an output field as of type JSON (‚J‘). This is currently only useful for Tolerant NAME in conjunction with using the PERL script interface. A PERL script could thus return a JSON response, that is delivered as a field within the response of the service.

General

  • In case of an (unlikely) OutOfMemoryError the product will now crash and create dump files.
  • Unified behaviour (help, usage, result codes, …) of Commandline Tools
  • The new administration command state database project-Id can be used to check the state of the project’s databases. If the project-Id was not entered, all databases will be checked.
  • The usage of the character minus (-) at the beginning of a normalizer section name is no longer allowed.
  • The product ships with a newer embedded web server (jetty 9.3.11). The cyphersuite can be configured using TLCONFIG/jetty-config/tweak-ssl.xml.

Fixed Bugs

Batch

  • TPR-3586: Batch process does not exist if the output file couldn’t be written.

Service

  • TPR-3648: The name mode „PROBABILISTIC“ did not work for a NAME service.
  • TPR-3724: The output of AdminCLI tools using json format is not JSON-conform.

General

  • TPR-7: Even if the logging for audit events was turned off, some initial logging messages appeared in the audit log.
  • TPR-384: When upgrading an installation with https, the installer overwrites the keystore (only relevant for products with servicecomponent).
  • TPR-484: The attribute „instances“ in the tag „configuration“ of the security.xml is no longer supported. All productinstance specific rights are now enabled, when „administration“ is enabled. The value of „instances“ will now be silently ignored.
  • TPR-3531: The check for errors in synonym file does not validate entries, that have no list-name.
  • TPR-3555: The name of a Match field should not contain a special character.
  • TPR-3569: All batch configuration templates coming with the product have now the same logginglevels:
    • Tracefiles: INFO
    • Logfiles: INFO
    • Console: INFO
  • TPR-3591: When configuring https during the installation (for products with servicecomponent), the selfsignedcert.txt file was overwritten and therefore empty. Now the file will contain the details about the selfsigned certificate as intended.
  • TPR-3691: The counter metrics for the synonym substitution should be project-specific.
  • TPR-3796: If a script for a generatedField did not return a value (or a null value), the trace file will contain errors about NullPointerExceptions.
  • TPR-3821: It is not possible to read and/or write in database tables if their schemas do not match the database username.
  • TPR-3837: Upgrade does not delete the Jetty-tmp directories if the hostname was used for JETTY_HOST (only relevant for products with servicecomponent)

Security

  • TPR-3472: The security.xml reader now checks the version of the file.

Known Bugs

  • TPR-3892: The new trimtypes M, RM, LM and A do not work for the following configuration-elements and tools:
    • serviceOutputField
    • csvOutputField
    • databaseOutputField
    • matchFiletest.sh/bat
    • postFiletest.sh/bat

Archived release notes