TIBCO BusinessConnect EDI Protocol 2.8.0 Hotfix 1 has been released
Article ID: KB0105390
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessConnect EDI Protocol Powered by Instream | - |
| Not Applicable | - |
Description
Description:
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-1/
Listed below is a summury of updates included. Please refer to the associated readme document for any additional information.
Level 5 errors in .esf are not picked up in synchronous response during XML to EDI conversion process.
(PD_Id:1-4HXTBB, SR_Id:1-4GERA5)
NullPointerException thrown when BusinessConnect tries to report invalid Trading Partner when validating a positional flat file.
(PD_Id:1-4GG894, SR_Id:1-4BXYE5)
Positional flatfile parser schema requires a static Property that defines the Standard as TEXT. All Positional flatfile parser schema and examples have been changed for this defect.
Multiple transactions in a single document do not get processed on HPUX Platform and several validation errors are published even though the same document validates in ediconvert.
(PD_Id:1-4IUJSD, SR_Id:1-4BZ6RD)
XEngine is querying the network interface for its MAC address in order to generate a GUID used in validation reporting. The buffer was set too small, causing the invalid argument mentioned above.
Note:This defect was addressed for HPUX Platform only.
8-digit Error ID from Audit Report that is defined in Error Severity file is not getting published in ErrorValidation/Warning message.
(PD_Id:1-4ISTX4, SR_Id:1-4IKRU5)
A new attribute is added to ErrorValidation/Warning message in ConversionEngineInfo AE class under the name errorID. This attribute is also audit logged during Audit Reporting. BW Plugin users should refresh their connections to get this new attribute visible in their ReceiveValidationError Activity if they want to make use of this attribute.
When the underlying transport encounters failures, the FTP transport error handler leads to recursive IM Error and eventually job termination. This occurs only in the case of FTP-Get when CustomScripts is used for a Trading Partner.
(PD_Id:1-4IJKJS, SR_Id:1-3YG1AO)
Error Handler implementation is fixed so that recursive IM Error does not occur.
BW Plugin for BC: EDI.aeSchema.xsd/ResponderResponse is missing the following elements in AESchema:
encoding
perMessage
(PD_Id:1-4C908X, SR_Id:1-4BJFH5)
EDI Documentation mentions that Users can send encoding and perMessage attribute for ResponderResponse message, but these attributes were not available for BW Plugin for BC Users. The above attributes are now part of the AESchema. Users should manually copy the <BC_installation_directory> \java\client\ediclient.jar to the <BW_installation_directory> \plugins\lib folder and refresh the BC Server Connection in BW to see these new attributes.
Error directory scenario is not handled in the case where transaction is successfully processed.
(PD_Id:1-49PQE2, SR_Id:1-44RJGL)
When using EDI-Gateway outbound file poller with both error directory and delete file options enabled, the original files are not deleted when transactions are successfully processed.
EDI engine did not error out with a GS-GE in the middle with an interchange envelope.
(PD_Id:1-3OCA67, SR_Id:1-3O600H)
The following property was introduced to enable or disable the audit logging and error advisory publication of invalid printable characters when preprocessing is enabled:
edi.report.preprocess.errors=<true|false>
Note: To maintain backward compatibility, the error advisory is not published by default. Users should add the above property and enable it if they require the advisory as well as audit logging needs to be shown.
When Rendezvous daemon could not process due to out of memory in the daemon, a No transition task caused WorkFlow Exception to be thrown thereby terminating the Job during Inbound EDI processing.
(PD_Id:1-4W9V5R, SR_Id:1-4T1X5T)
The No transition is corrected in this case to process the Inbound EDI processing to avoid any Job loss.
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-1/
Listed below is a summury of updates included. Please refer to the associated readme document for any additional information.
Level 5 errors in .esf are not picked up in synchronous response during XML to EDI conversion process.
(PD_Id:1-4HXTBB, SR_Id:1-4GERA5)
NullPointerException thrown when BusinessConnect tries to report invalid Trading Partner when validating a positional flat file.
(PD_Id:1-4GG894, SR_Id:1-4BXYE5)
Positional flatfile parser schema requires a static Property that defines the Standard as TEXT. All Positional flatfile parser schema and examples have been changed for this defect.
Multiple transactions in a single document do not get processed on HPUX Platform and several validation errors are published even though the same document validates in ediconvert.
(PD_Id:1-4IUJSD, SR_Id:1-4BZ6RD)
XEngine is querying the network interface for its MAC address in order to generate a GUID used in validation reporting. The buffer was set too small, causing the invalid argument mentioned above.
Note:This defect was addressed for HPUX Platform only.
8-digit Error ID from Audit Report that is defined in Error Severity file is not getting published in ErrorValidation/Warning message.
(PD_Id:1-4ISTX4, SR_Id:1-4IKRU5)
A new attribute is added to ErrorValidation/Warning message in ConversionEngineInfo AE class under the name errorID. This attribute is also audit logged during Audit Reporting. BW Plugin users should refresh their connections to get this new attribute visible in their ReceiveValidationError Activity if they want to make use of this attribute.
When the underlying transport encounters failures, the FTP transport error handler leads to recursive IM Error and eventually job termination. This occurs only in the case of FTP-Get when CustomScripts is used for a Trading Partner.
(PD_Id:1-4IJKJS, SR_Id:1-3YG1AO)
Error Handler implementation is fixed so that recursive IM Error does not occur.
BW Plugin for BC: EDI.aeSchema.xsd/ResponderResponse is missing the following elements in AESchema:
encoding
perMessage
(PD_Id:1-4C908X, SR_Id:1-4BJFH5)
EDI Documentation mentions that Users can send encoding and perMessage attribute for ResponderResponse message, but these attributes were not available for BW Plugin for BC Users. The above attributes are now part of the AESchema. Users should manually copy the <BC_installation_directory> \java\client\ediclient.jar to the <BW_installation_directory> \plugins\lib folder and refresh the BC Server Connection in BW to see these new attributes.
Error directory scenario is not handled in the case where transaction is successfully processed.
(PD_Id:1-49PQE2, SR_Id:1-44RJGL)
When using EDI-Gateway outbound file poller with both error directory and delete file options enabled, the original files are not deleted when transactions are successfully processed.
EDI engine did not error out with a GS-GE in the middle with an interchange envelope.
(PD_Id:1-3OCA67, SR_Id:1-3O600H)
The following property was introduced to enable or disable the audit logging and error advisory publication of invalid printable characters when preprocessing is enabled:
edi.report.preprocess.errors=<true|false>
Note: To maintain backward compatibility, the error advisory is not published by default. Users should add the above property and enable it if they require the advisory as well as audit logging needs to be shown.
When Rendezvous daemon could not process due to out of memory in the daemon, a No transition task caused WorkFlow Exception to be thrown thereby terminating the Job during Inbound EDI processing.
(PD_Id:1-4W9V5R, SR_Id:1-4T1X5T)
The No transition is corrected in this case to process the Inbound EDI processing to avoid any Job loss.
Issue/Introduction
TIBCO BusinessConnect EDI Protocol 2.8.0 Hotfix 1 has been released
Environment
Product: TIBCO BusinessConnect EDI Protocol
Version: 2.8.0
OS:
--------------------
Feedback
Yes
No
Powered by
