Description:
TIBCO BusinessConnect EDI Protocol 5.1.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.1.0/hotfix-2/

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


Closed Issues in 5.1.0-hotfix2 (This Release)

1-7H9J7N
When the file Transmission Sender/Receiver Code/Name was overidden
from the private process perMessage, the overrides at the final
converted TRADACOMS document were not correct.
This has been fixed.

There was also a problem with namespaces during pre-population of XML
that caused the XML to become invalid.
This has been fixed too.

1-7UUETB
When doing batching for EDIFACT with no testIndicator or processing
code in the Interchange Header of the Trading Partner, an exception
was thrown and the batched document did not go out.
This has been fixed.

In addition, the sender and receiver ID/Qualifier specified in the
process perMessage was not correctly reflected in the outbound
EDI document.
This has been fixed too.

1-7E1X5G
When EDI batching was enabled for sending EDI documents through
the outbound AS2 HTTP transport, the software was generating a
required EDI document to be sent to the Trading Partner.
However, the AS2 HTTP content-type header included text/xml instead
of application/edi-x12, which caused the document to be rejected
by the Trading Partner.
This has been fixed.

1-7CDC8T
When sending an EDIFACT document with an Interchange sender or a
recipient Qualifier configured as NULL, the document would fail on
the Trading Partner side with validation errors due to the invalid
EDI format.
This has been fixed.

======================================================================
Closed Issues in 5.1.0-hotfix1

1-7AO4OI
The "Enable Text to XML Validation and Conversion" feature was not
working properly in that the EDI-TEXT protocol was attempting to
validate transactions even when the "Enable Text to XML Validation
and Conversion" checkbox was deselected. This feature now behaves as
expected.

1-76B4OQ
The software was not processing with the tpName field left blank even
though the field is optional. This is fixed. Either the tpName should
be specified or the receiver ID/Qualifier value should be specified
in the perMessage attribute.

1-76RQZ8
The software was rejecting transactions sent from non-default hosts
even when there was a valid business agreement between the non-default
host and the trading partner. The message was sent using the
perMessage sender ID/qualifier field in the InitiatorRequest message.

This is fixed.

1-79Q8WP
The override transport feature was not working for batched
transactions.

This is fixed.

1-7A39SY
The software was throwing a null pointer exception during XML to EDI
conversion when there were XML characters (for example ?&?) in the
default domain identity qualifier of the trading partner/host
configuration.

This is fixed.

1-7A6AF4
The software was failing to process inbound EDI messages sent using
FTPS and was throwing an exception.

This is fixed.

TIBCO BusinessConnect EDI Protocol 5.1.0 hotfix 2 has been released.

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