Description:
TIBCO BusinessConnect EDI Protocol powered by Instream 6.4.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.4.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.4.0_HF-001 (This Release)

CR: EDIP-1586

When an XML is translated to TEXT format in BusinessConnect engine, the
translator is not able to handle multiple-characters like 0x0D0x0A (CR-LF)
from the Trading Partner configuration. This issue is fixed.

For this type of special multi-character delimiters, users must set the
segment delimiter to be 0x0D (CR) in the Trading Partner configuration UI
as well as set (or add if one has not been added before) the "newline"
option in the TARGETOPTION element section of the
"target guideline settings" in the map file.

A typical value would be &ltnewline value="2"/> which indicates that the New Line
should be LF (LineFeed which is 0x0A).

CR: EDIP-1590

When receiving a TEXT file from the Trading Partner, BusinessConnect
engine is not able to translate the TEXT data into the proper XML
format, since the Translator inside is not able to get the correct
segment and element delimiter of the received Inbound document if 0x0A
or 0x0D0x0A is the segment delimiter in the data file.

This issue is fixed by adding separate segment and element delimiters
by Partners for inbound in the deployed BusinessConnect Engine.tra file.
The format is specified as following:

java.property.&ltPartner Name>.TEXT.Delimited.inbound.segment.delimiter=&ltvalue>
java.property.&ltPartner Name>.TEXT.Delimited.inbound.element.delimiter=&ltvalue>
java.property.&ltPartner Name>.TEXT.Positional.inbound.record.delimiter=&ltvalue>

- A value needs to be specified for segment and element for Delimited
   and record delimiter for Positional.
- &ltPartner Name> must be replaced with the actual Trading Partner
   name specified in the configuration user interface.

CR: EDIP-1589

When invalid delimiters are entered in the Trading Partner configuration for TEXT
protocol, the BusinessConnect engine would stop processing TEXT documents due to translator
module releasing shared resources. This issue is fixed.

CR: EDIP-1588

When 0x0A is used as a segment delimiter specified in the Trading Partner configuration
for TEXT protocol, BusinessConnect engine is not able to translate the delimiters correctly
due to translator and wrap configuration set to not use 0x0A.

This issue is fixed by adding the following configuration in the deployed BusinessConnect Engine.tra
file. The format is specified as following:
java.property.&ltPartner Name>.TEXT.WrapData=true | false

- A value of true would not let the engine to wrap 0x0A data in separate lines.
- A value of false would let the BusinessConnect Engine pick up the value and allow the data
to be wrapped.
- &ltPartner Name> must be replaced with the actual Trading Partner name specified in the configuration
   user interface.