TIBCO BusinessConnect EDI Protocol 2.8.0 Hotfix 3 has been released
book
Article ID: KB0105535
calendar_today
Updated On:
Products
Versions
TIBCO BusinessConnect EDI Protocol Powered by Instream
-
Not Applicable
-
Description
Description: TIBCO BusinessConnect EDI Protocol 2.8.0 Hotfix 3 has been released You can download this HotFix 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 ActiveExchange/EDI/2.8.0/hotfix-3/
Note: the HP-UX package is not currently available. Please contact TIBCO Support for any questions.
Listed below is a summary of updates included. Please refer to the associated readme document for any additional information.
# OutOfMemoryError while processing large inbound interchange using EDI 2.8.0/ hipaa 2.8.2. (PD_Id:1-6MGLCP, SR_Id: 1-6E0DZD)
There were OutOfMemory errors occuring during processing. when running a large inbound interchange HIPAA file with several thousand transactions that contained errors.
Note: This defect was addressed on the Solaris platform only.
# Users have the ability to change the element tag value from one value to another at a Trading Partner level controlled by EDI.cfg property. (PD_Id:1-6OEUKU, SR_Id: 1-61NAR9)
The earlier property edi.outbound.xDataElementConvert.<EDI-X12|EDI-EDIFACT>.<Element-Tag>.: | is now changed to edi.outbound.xDataElementConvert.<EDI-X12|EDI-EDIFACT>.<TpName>.<Element-Tag>: | where TpName is the Trading Partner specified in the configuration GUI.
Note: To Enable TP specific configuration users must also specify another property edi.outbound.enable.tpLevel.xDataElementConvert: true to enable it. By default it is false. For e.g. In EDI.cfg add edi.outbound.enable.tpLevel.xDataElementConvert: true property in one line.
Note:Add edi.outbound.xDataElementConvert.EDI-EDIFACT.Company2.Element-7008: .|, to convert . (decimal period) to , (comma) for EDIFACT documents sent to Trading Partner 'Company2'.
# The engine produces XML files using non-optimal file mask when RESPONDER.REQUEST is being published. (PD_Id:1-6E5SZL, SR_Id: 1-62OW5H)
When running multiple engines, the XML files published by RESPONDER.REQUEST message by these engines causes files to be overwritten if they are created by each engine at the same time. This causes the back end systems to lose messages. Now each message is being prefixed with the Engine name to be unique.
# When an interchange with multiple groups are processed that are same, the Error Severity file (.esf) for consecutive transactions are not getting picked up from the repository. (PD_Id:1-6N8543, SR_Id: 1-6MQWRX)
This happens only if the groups are the same for an interchange.
Note: This defect was addressed only for HIPAA.
Issue/Introduction
TIBCO BusinessConnect EDI Protocol 2.8.0 Hotfix 3 has been released
Environment
Product: TIBCO BusinessConnect EDI Protocol
Version: 2.8.0
OS: All
--------------------