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-hotfix7
1-7ZYMOA Fixed the issue in handling duplicate inbound request while the earlier request was still in progress. The duplicate request should not cause the deletion of the hibernated data from the original in-progress request. The duplicate request will be logged and terminated without affecting the original request.
1-7CGU30,1-7CGU48 TAW log was not providing debug level tracing.
1-7ZP9RD Fixed the issue with the PIP version string in the service headers for both RNIF11 and RNIF20 to be backward compatible with earlier BusinessConnect RosettaNet Protocol releases (2.6+). The PIP version string will always follow the same scheme as the incoming message. For example, if the incoming message has pip version = "V02.00.01" then this will be reused for all subsequent acks & responses. The version string for the action-identity remains the same without the patch number. Also, a new plugin property "bcrn.pipversion.include.patch" is added to allow users to set the version scheme to be used for generation of an outbound Request message.
1-7ZVTWH If the trading partner sends back a response without ack of request, the software should complete the transaction with "PIP completed - Received Response Document without Acknowldegement Receipt", instead of "PIP terminated - Outbound transport not specified".
Issue/Introduction
TIBCO BusinessConnect RosettaNet Protocol 5.1.0 hotfix 7 has been released.