TIBCO BusinessConnect EDI Protocol 5.3.0 hotfix 2 has been released.

TIBCO BusinessConnect EDI Protocol 5.3.0 hotfix 2 has been released.

book

Article ID: KB0106069

calendar_today

Updated On:

Products

TIBCO BusinessConnect EDI Protocol Powered by Instream Not Applicable

Description

Description:
TIBCO BusinessConnect EDI Protocol 5.3.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/5.3.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 5.3.0-hotfix2 (This Release)

CR: 1-9J1OJC

When sending a file using EDI-Gateway Trading Partner through AS2
Transport, any EDI-X12 or EDI-EDIFACT files are sent with a content-type of
application/edi-consent and not with appropriate content-type as
application/edi-x12 and application/edifact in the HTTP headers. This issue
is fixed.

CR: 1-9C9UPN

BusinessConnect EDI protocol internally was caching the errors per interchange
to publish the *.ERROR message at the end of each interchange even though per
transaction level *.ERROR.VALIDATION error messages are published. This causes
a huge memory buildup, if there are lots of transactions with each transaction
containing several number errors. BusinessConnect server eventually runs out
of memory due to this cache buildup. The fix involves limiting the error cache
to a threshold of only 256K size for the *.ERROR that is published, but still
publishing the *.ERROR.VALIDATION message in full.

CR 1-9LC65N

BusinessConnect EDI protocol when configured to send via Gateway Trading Partner
was wrongly checking the receiver ID/Qualifier sent from the Private Process If
the Private Process sends 'tpName' of that Protocol (like EDI-X12, EDI-EDIFACT).
This prevented the message to be sent out through the Gateway Trading Partner.
This issue is corrected by checking the receiver ID/Qualifier with the correct
Protocol 'tpName' specified in the Private Process, rather than the Gateway
Trading Partner.

CR 1-9LUR4R

When a Protocol (like EDI-X12, EDI-EDIFACT etc) message is sent from the Private
Process to BusinessConnect routed to a Gateway Trading Partner, the EDI message
is not sent to that Gateway Trading Partner if only the receiver ID/Qualifier
is set with no 'tpName' specified in the Send Request Activity from
BusinessConnect Palette. The EDI message instead is sent through the Protocol
Trading Partner's transport. This issue is fixed with the EDI message properly
being routed to Gateway Trading Partner.

Issue/Introduction

TIBCO BusinessConnect EDI Protocol 5.3.0 hotfix 2 has been released.

Environment

Product: TIBCO BusinessConnect EDI Protocol Version: 5.3.0 OS: --------------------