News about our products 1.6

Current versions of the products

Our products are currently available in the following versions:

At the end of November we will release all products together. The products will then be based on the same base libraries and support the same base features.

We will set the version numbers of the products uniformly to 2.0 with this release to make it easier for you to distinguish them from previous releases. The next major release is scheduled for May 2015.

Highlights of the upcoming release

Common to all products are the following new or enhanced features:

A maximum length can be set for input fields. If the content exceeds this length, it will be trimmed to the specified length or the records will be marked as incorrect.
A maximum length can be defined for output fields. If the contents exceed this length, they are trimmed to the specified length.
Batch products allow reading and writing from/into databases.
Sensitive data written to log files can be anonymised.
The administration of service instances via the interface has been simplified.
Obsolete configuration elements are no longer supported. This includes in particular the former setting options for logging.
Current Java Virtual Machine.
The entire file system of a server could previously be accessed via the file selection of the configuration interface. This can now be restricted via extended security attributes.
If it is discovered during an upgrade installation that you have modified files, it is possible to save these files before the installation.
Most products come with several sample configurations. In the case of service installations, the examples can be installed together with the product.
For database accesses, a table prefix can be defined, which precedes all table names. In this way, the number of database schemas can be reduced if this is of benefit from an operational point of view.
An experimental tool allows conversion between batch and service configurations.
Updated versions of the manuals are enclosed.

In TOLERANT Bank, the logic for IBAN conversion was optimised in coordination with the Bundesbank.

TOLERANT Match was revised and significantly improved with regard to robustness against database access errors. Also, runtimes of database accesses and error counters are now regularly written to log files. Fields in the Match API can be marked as optional in future, so that new fields can be added to a service configuration without having to adapt all applications that use this service. The initial loading of data into a match service can now be done from a database as well as from files.

Enhancements to TOLERANT Post:

The latest version of the AddressDoctor library (5.6.0) has been integrated.
This means that the following older operating system versions can no longer be supported for TOLERANT Bank:
– Redhat Linux smaller version 6
– Solaris Sparc lower version 10
– Suse Linux lower version 11
Fields in the Post API can be marked as optional. This allows new fields to be added to the interface without having to customise all applications that use the interface.
The configuration interface shows extended information about installed licence keys.
Information on installed licence keys can be queried via the service interface.
The postal service can cyclically search a directory (local or remote) for new reference data and install them automatically if necessary.
Extended delivery codes of the postal organisations of Great Britain, France and Japan can be determined.
In case of a validation error of an address, the original input values can be output again instead of the corrected data.
If it is uneconomical to obtain reference data for a particular country, a cloud service for individual countries can be used via the Internet.