Products | Versions |
---|---|
TIBCO BusinessConnect EDI Protocol Powered by Instream | - |
Not Applicable | - |
Description:
TIBCO BusinessConnect EDI Protocol 2.8.0 Hotfix 2 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-2/
Listed below is a summury of updates included. Please refer to the associated readme document for any additional information.
. AK403 Segment incorrect in 837-997 Interchange.
(PD_Id:1-4MJ49M, SR_Id:1-4KNEYL)
cf readme for further details
. Incorrect Error Code in 997 segment AK304
(PD_Id:1-4MJ4AZ, SR_Id:1-4KNEZ8)
cf readme for further details
. Fixed a deadlock situation that happens on SQLServer 2000 for edi_control_number table.
(PD_Id:1-5AI62H, SR_Id: 1-53OHB1)
When running multiple engines on a Load-balancing mode with DMZ enabled, BusinessConnect engines gets deadlocked on Microsoft SQLServer database. This is fixed with granular level ROWLOCK hint recommended by Microsoft.
. When a EDI-TEXT message received from Trading Partner contains X12 or EDIFACT detection strings like ISA, UNA or UNB the initial detect pre-processor identifies the document as EDI-X12 or EDI-EDIFACT and not as EDI-TEXT protocol. This had resulted in parsing and processing failures since the actual document does not contain any X12 or EDIFACT envelope segments.
(PD_Id:1-5AL8CH, SR_Id: 1-56UUO1)
Note: This defect was addressed on the Solaris and Windows platforms only.