Description:
TIBCO BusinessConnect EDI Protocol powered by Instream 6.5.0 hotfix 2 has been released.

You can download this Hot Fix from the TIBCO Product Support FTP server using your eSupport username and password, at

            ftp://support-ftp.tibco.com

Once you have successfully logged into the server, you will find the hotfix packages under

            available_downloads/ActiveExchange/EDI/6.5.0/hotfix-02/

Listed below is a summary of updates included. Please refer to the associated readme document for any additional information.

Closed Issues in 6.5.0_HF-002 (This Release)

CR: EDIP-1979

The Group level IDs (GS02/GS03 elements) specified in private process (under
perMessage/group sender app and receiver app) are not used by BCEDI runtime when
sending the message out. Only the default values configured in BCEDI configuration
that are used.

This issue has been fixed.

CR: EDIP-2027

Foresight Translator cannot be fully leveraged to work in multi-thread mode, which
causes Translator not being able to perform well. The actual phenomenon is related
to the value set to the property "edi.Translation.ThreadPool.queueSizeThrottle";
if this property is set too small, Translator can only be ran by small number
of threads at one time, which also reduces the throughput of Instream and eventually
impacts the overall engine throughput; if this property is set larger than the value
of maximum Translator threads (controlled by property "edi.Translation.ThreadPool.maxCount"),
this throttle value will not take effect which could cause the engine run out of memory.

This issue has been fixed. After the fix the default value of
"edi.Translation.ThreadPool.queueSizeThrottle" is set to 100, meaning the Instream can
generate as many as 100 translation task to be executed by Translator; Translator will
be ran by as many as threads defined in property "edi.Translation.ThreadPool.maxCount"
(with 16 being the default value) to execute these translation tasks. Customer should
refer to their CPU powerfulness and memory size to fine tune the value of these two
properties.

CR: EDIP-2028

APF file reference is not included in the TI report published from BCEDI runtime
engine.

This issue has been fixed.

CR: EDIP-2029

If for some reason the inbound raw EDI data cannot be written successfully to
file system, BCEDI still sends out TI Report to Foresight TI server which
includes the invalid file reference; this will cause TI server mal-functioning
such as keeping too many JMS connections.

This issue has been fixed. Before sending out the TI report, BCEDI will check
if both raw EDI data file and Instream validation result file exist. If either
of these files doesn't exist, an ERROR audit log will be logged and the report
will not be sent out.