TIBCO BusinessConnect EDI Protocol powered by Instream 6.6.0 hotfix 3 has been released.
Article ID: KB0103098
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessConnect EDI Protocol Powered by Instream | - |
| Not Applicable | - |
Description
Description:
TIBCO BusinessConnect EDI Protocol powered by Instream 6.6.0 hotfix 3 has been released.
TIBCO BusinessConnect EDI Protocol powered by Instream 6.6.0 hotfix 3 has been released.
You can download this Hot Fix from the TIBCO Product Support server using your TIBCO Support Central (TSC) username (email address) and password, at
mft.tibco.com
mft.tibco.com supports FTP, HTTPS, and SFTP.
Once you have successfully logged into the server, you will find the hotfix packages under
/AvailableDownloads/BusinessConnect/EDI/6.6.0/hotfix-03
Listed below is a summary of updates included. Please refer to the associated readme document for any additional information.
Closed Issues in 6.6.0_HF-003 (This Release)
EDIP-2333
When asynchronous MDN receipts were received and processed, the related temporary
files created under shared temporary directory were not cleaned up after the
processes completed.
EDIP-2331
BusinessConnect Interior Server failed to start up when TIBCO BusinessConnect EDI
Protocol powered by Instream was installed with products such as TIBCO BusinessConnect
SOAP Protocol 6.1.0 under the same {TIBCO_HOME}.
EDIP-2318
In certain negative case, TIBCO BusinessConnect EDI Protocol powered by Instream
failed to insert audit log into ORACLE database with "ORA-00001: unique constraint
violated" error.
EDIP-2312
TIBCO BusinessConnect EDI Protocol powered by Instream generated duplicate HTTP
headers for NAESB request sent to trading partners.
EDIP-1105
TIBCO BusinessConnect EDI Protocol powered by Instream failed to send Insight
report for synchronous request response transactions occasionally.
================================================================================
Closed Issues in 6.6.0_HF-002
EDIP-2303
When receiving X12 request through Gateway trading partner, if the inbound Log
Raw EDI Request to File was enabled by selecting Host -> X12 protocol-> Logging
Tab, the raw EDI request was not logged into a file system.
EDIP-2298
When overriding guidelines or map files in Business Agreements for the TEXT operations,
if the overriding multiple operations was for the same message group, the guidelines
and map files under the first operation took effect.
================================================================================
Closed Issues in 6.6.0_HF-001
EDIP-2287
TIBCO BusinessConnect EDI Protocol powered by Instream did not allow sending
EDIFACT data both with UNG segment and without UNG segment to one trading partner.
This issue was fixed. Customer need to add new properties as per the following
steps in TIBCO Administrator:
a. Click BusinessConnect > System Settings > Activated Protocol Plug-ins and
Properties > tibEDI
b. Add property edi.EDIFACT.outbound.group.checking.disable for all trading
partners or add property edi.EDIFACT.outbound.group.checking.disable.<Partner Name>
for one trading partner.
EDIP-2286
When TIBCO BusinessConnect EDI Protocol powered by Instream generate X12
Acknowledgement, such as 997 and TA1, the value of ISA14 element was always 0
and the value of GS05 element was always with format HHMMSS.
This issue was fixed and customer need to install TIBCO Foresight Instream
Standard Edition 8.4.0 - Hotfix 5 first.
Issue/Introduction
TIBCO BusinessConnect EDI Protocol powered by Instream 6.6.0 hotfix 3 has been released.
Environment
BusinessConnect EDI Protocol powered by Instream 6.6.0all platforms
Feedback
Yes
No
Powered by
