TIF 2018.6.0 Release Information 2019-01-01

Database Maintenance

Support for maintaining the internal database in TIF has been added. Maintenance operations like table compacting, statistics re-calculation and consistency checking can now be performed.

The TIF start scripts (Windows and UNIX) have been updated to allow running this operation.

Database maintenance should be carried out at some points, how often and when depends on the usage of TIF. However, re-calculation of the statistics should be done after massive amount of data/jobs have been processed in order to avoid performance issues.

The maintenance operation must be done when the TIF instance is offline.

Database Network Access

In earlier versions of TIF the database were started in mixed mode, which allowed access to the database from a client over the network. As of this release, the database will only be started in embedded mode by default, which means that there is no networking capabilities turned on.

It is possible to change this via the file ${TIF_HOME}/etc/tif.custom.properties. Just add these properties:

db.port=1527
db.mode=MIXED

Instance Specific Timetable

In case you start up multiple TIF instances from the same base installation directory, you can now have instance specific timetables. This allows you to run different kind of scheduled jobs on different instances.

Within the directory ${TIF_ROOT}/modules/enovia/etc you can have timetable file with this naming convention.

  • timetable-{node-id}-{instance-id}.xml

  • timetable-{instance-id}.xml

  • timetable.xml

The names are case-insensitive.

Directory Listener and Create/Update Integration

If you trigger the create/update integration via files through a directory listener, some enhancements have been made.

If you configure the directory listener with input path, error path and done paths like shown below:

<Paths>
    <Input>c:/transfer/input</Input>
    <Output>c:/transfer/done</Output>
    <Error>c:/transfer/error</Error>
</Paths>

Then the output from the create/update configuration will be sent to the "Output" folder. In case an error occur during processing, the input file will instead be moved to the specified Error path in order to allow taking some future action on the file itself. From the Admin UI you will still be able to see the error message.

The arguments outputDestination and errorDestination, which are specific for the create/update integration type will still be supported in addition to the above.

Logging of Inbound and Outbound Payload in Configurable SOAP Web Services

In Configurable SOAP Web Services, inbound and outbound payload will now be stored, meaning it is possible to review SOAP envelope contents of request and response in Admin UI.

Change to TIF Schema in ENOVIA/3DEXPERIENCE Database

Job configuration and source ID are added as new attributes to TIF Job object. This simplifies queries regarding exclusive jobs.

Fixed Bugs

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

Issue No Description

511

Authentication failure with multiple HTTP destinations pointing to same URI

520

Truncation issue occurring if error details exceeded DB size

539

Removed unwanted dependency from TIF Client to TVC Structure Browser.

518

Transfer encoding issue with large payload transfer to HTTP destination

532

TIF Rest service, problem in decoding special characters