Description:
TIBCO BusinessConnect EDI Protocol powered by Instream 6.5.0 hotfix 1 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-01/

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-001 (This Release)

CR: EDIP-1964

BusinessConnect runtime table size grows too fast because the EDI resent raw
messages are saved more than one times.

This issue is fixed.

CR: EDIP-1965

When EDIFACT documents containing no Functional Group (EmptyGroup) is processed
and if the messages in the Interchange have more than 100 errors (or
information or warning) reported, only the first 100 errors are being captured
and reported.

This issue is fixed. The correction is to send all the errors that are received.

CR: EDIP-1966

Service Protocol DB connection pool for the handler was always 16, the default
value of Audit and Runtime connection pool size even it is changed in TIBCO
Administrator.

This issue is fixed. The real value will be picked up from Audit and Runtime
connection pool size set in TIBCO Administrator.

CR: EDIP-1967

When Outbound XML to EDI translation and validation is completed, the document
parser instance to check for Interchange ID/Qualifier was not released which
leads to a growth in memory. This would also affect Inbound synchronous
transactions as well when the synchronous response is sent back to the trading
partner.

This issue is fixed.

CR: EDIP-1969

If BusinessConnect EDI engine crashes when the outbound scheduled batching
process is in RUNNING status,  the documents do not always go out to trading
partner after restart of the engine. This normally requires manual intervention
to reset the statuses to PENDING or resending the batch documents that were
in the process.

This is because the RUNNING status of BC_SCHEDULED_TASK could be in several
internal states including batch transactions being collated, ready for message
packaging, message packaged, sent to partner and waiting for response, etc.
The engine could be in any of the above states when crash occurs, and in some
of the states the documents cannot be automatically sent out after the engine
restarts.

To better tackle this issue, in this hotfix release the RUNNING status are
separated into several "sub-statuses", and if the engine crashes while in
certain sub-status the engine could still re-process batched documents when
it restarts. The newly introduced sub-statuses are RUNNING_SENT_FOR_PKG,
RUNNING_PKG_MARKED and RUNNING_SENT_TO_TP, in addition to the original RUNNING
status.

The engine status is set to RUNNING before the transaction collation starts.
If the engine crashes during the transaction collation, users must still do
manual intervention as before (reset the status to RUNNING) in order for the
batch to be sent out after the engine restarts;

The engine status is updated to RUNNING_SENT_FOR_PKG once the batch is collated
and sent to internal BC component for enveloping and packaging. If the engine
crashes at this status, the users must still do manual intervention as before
in order for the batch to be sent out after the engine restarts;

The engine status is updated to RUNNING_PKG_MARKED once the enveloping and
packaging is done; the engine then do the transport level packaging before it
is sent to trading partner. If the engine crashed during this status, the batch
can be processed and sent out automatically after the engine restarts;

The engine status is updated to RUNNING_SENT_TO_TP once the transport level
packaging is done and the engine starts to send the whole batch to the trading
partner, and then wait for response from the TP. If the engine crashes during
this status and then restarted, the engine will update the status as COMPLETE
or ERROR depending on whether the response from the partner has been received.

CR : EDIP-1958

Previously only one set of inbound delimiters for TEXT protocol can be configured
for each trading partner, so BusinessConnect EDI only can handle inbound TEXT
data with the same delimiters.

This issue is fixed. BusinessConnect EDI can now handle TEXT data from a
particular TP with different delimiters. You must install Instream 8.3.0 and
above to make this fix take effect.

CR : EDIP-1971

When BusinessConnect EDI send RESPONDER.REQUEST message to Private Process,
the value of IEA's/UNZ's first element in "interchangeTrailer" property is
always 1, no matter how many transactions or function groups in the interchange.

This issue is fixed. The value of "interchangeTrailer" in RESPONDER.REQUEST
will reflect the real number as inbound EDI data.

CR : EDIP-1984

EDI cannot support one TP using different GS04 formats for different group
version.

This issue is fixed by adding separate GS04 format for 3071 and lower function
group in Admin GUI -> BusinessConnect -> System Settings -> Activated Protocol
Plug-ins and Properties -> tibEDI.

Adding separate GS04 format for one TP:
Add string property with name "&ltTPName>.X12.3071AndLower.GS04.date.format" and
the property value should be "YYMMDD"

Adding separate GS04 format for all TPs:
Add string property with name "X12.3071AndLower.GS04.date.format" and the
property value should be "YYMMDD"