TIF 2019.5.0 Release Information

08 November 2019

1. Tutorial - How to connect with IBM MQ over JMS

There is a new tutorial in TIF Admin Guide that describes how to configure JMS destination connecting to IBM MQ. The tutorial covers both MQ queues and topics.

2. File modifier - Debug log

When using the TIF File Modifier (used for creating PDF files among others), and the debug log level is enabled, the file modifier log file is appended to the TIF log.

Also, the File Modifier log is available from the Admin UI if the execution fails.

3. Limiting logged inbound/outbound payload

For hosted RESTful, Apache CXF and SOAP web services, new configurable web-application init-parameters have been added in order to allow set the maximum length for logged inbound (request) and outbound (response) payloads.

These parameters can be used to prevent larger payloads to consume all heap memory and also prevent persisting too large payloads into the TIF Database.

See parameters "inboundPayloadMaxLength" and "outboundPayloadMaxLength" in ${TIF_ROOT}/modules/enovia/webapps/<webapp>/WEB-INF/web.xml.

The default value for these parameters are 1 000 000 bytes, if not defined.

4. Improvements to job and payload cleanser

New optional arguments "deleteLimit" and "maxIterations" can be defined for the job and payload cleanser scheduled jobs. The argument "deleteLimit" defines the maximum number of rows to be deleted within a single TIF database call, and the argument "maxIterations" defines the maximum number of database calls that are done during one cleanser job execution.

The purpose of these arguments is to help preventing too heavy database calls, and to split cleanser job to smaller calls, which might happen if these cleansers have been enabled on a TIF instance that have a large amount of historical data already in the database.

By default, "deleteLimit" is 0 (unlimited) and "maxIterations" is 1.

For example:

<job-cleanser>
    <schedule>
        ...
    </schedule>
    <args>
        <arg name="deleteLimit" value="100" type="integer" />
        <arg name="maxIterations" value="5" type="integer" />
    </args>
</job-cleanser>

In the example above, maximum of 5 TIF database calls are executed that each can clean up to 100 jobs. E.g the cleanser job could clean maximum of 500 jobs per execution.

See ${ROOT_DIR}/modules/enovia/etc/timetable.xml.sample.

5. Fixed Bugs

Below is the list of fixed bugs as of this release.

Issue No Description

669

Hosted rest services not working due to a missing dependency: "jersey-hk2"

5962

TIF rest services consumes too much heap memory

6053

Handle the MX_DECIMAL_SYMBOL correctly in the create/update integration when processing decimal values