TIBCO BusinessConnect EDI Protocol powered by Instream 6.4.0 hotfix 2 has been released.
Article ID: KB0104764
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessConnect EDI Protocol Powered by Instream | - |
| Not Applicable | - |
Description
Description:
TIBCO BusinessConnect EDI Protocol powered by Instream 6.4.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/6.4.0/hotfix-02/
Listed below is a summary of updates included. Please refer to the associated readme document for any additional information.
Closed Issues in 6.4.0_HF-002 (This Release)
CR: EDIP-1922
When EDIFACT documents containing no Functional Group (EmptyGroup) is processed
and if the messages in the Interchange have more than 100 errors (or
information or warning) reported, only the first 100 errors are being captured
and reported. The correction is to send all the errors that are received. This
issue is fixed.
CR: EDIP-1565
BusinessConnect runtime table size grows too fast because the EDI resend raw
messages are saved more than one times.
This issue is fixed.
CR: EDIP-1952
Service Protocol DB connection pool for the handler was always set to
default pool connection size of 16 even when it is changed for Audit
and Runtime. This issue is fixed and will pick up the values from Audit
and Runtime connection pool size values.
CR: EDIP-1959
When Outbound XML to EDI translation and validation is completed, the
document parser to check for Interchange ID/Qualifier was not released
which leads to a growth in memory. This would affect Inbound synchronous
transactions as well when the synchronous response is sent back to the
trading partner. This issue is fixed.
CR: EDIP-1960
Inbound processing of large transactions take longer time on Linux 64-bit
operating system. This was due to compile option not providing maximum
performance for Foresight Instream library. This issue is fixed.
CR: EDIP-1963
When BusinessConnect EDI engines crash during the batching of documents
which are in the RUNNING status due to certain abnormal conditions, the
documents do not go out to trading partner after restart of the engine.
This requires manual intervention to reset the statuses to PENDING or
resending the batch documents that were in the process.
RUNNING status indicates several internal states that includes batch transactions
being collated, ready for message packaging or packaged, sent to partner
and waiting for response and an internal RV communication waiting to
confirm. The engine could be in any of the above states. There are fixes
to address and separate reprocess of the batch documents automatically
when engines restart and for this to happen there are additional statuses
introduced (namely RUNNING_PKG_MARKED, RUNNING_SENT_FOR_PKG and
RUNNING_SENT_TO_TP) to tackle in terms of recovering and sending the
batches.
If the batched transactions are in collation state and the engine
crashes, users must still do manual intervention like before.
once in the RUNNING status after the batch is collated and ready to
sent to internal BC component for Enveloping and packaging the internal
status is changed to RUNNING_SENT_FOR_PKG and if the engine crashes during this
status and engine is restarted, the batched transaction would be reprocessed
automatically.
If the batch status in BC_SCHEDULED_TASK table is in RUNNING_SENT_FOR_PKG,
then the engine changes it to RUNNING_PKG_MARKED to process the collated
batch for transport level packaging before it is sent to trading partner.
If the engine has crashed during this status, then when the engine restarts,
this batch would be automatically processed.
If the batch status in BC_SCHEDULED_TASK table is in RUNNING_PKG_MARKED,
then the engine changes it to RUNNING_SENT_TO_TP status and sends it to the
trading partner and waits for response. If the engine crashes during the status
and restarted, then the engine looks at the partner response if available and
appropriately mark it as either COMPLETED or ERROR status.
TIBCO BusinessConnect EDI Protocol powered by Instream 6.4.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/6.4.0/hotfix-02/
Listed below is a summary of updates included. Please refer to the associated readme document for any additional information.
Closed Issues in 6.4.0_HF-002 (This Release)
CR: EDIP-1922
When EDIFACT documents containing no Functional Group (EmptyGroup) is processed
and if the messages in the Interchange have more than 100 errors (or
information or warning) reported, only the first 100 errors are being captured
and reported. The correction is to send all the errors that are received. This
issue is fixed.
CR: EDIP-1565
BusinessConnect runtime table size grows too fast because the EDI resend raw
messages are saved more than one times.
This issue is fixed.
CR: EDIP-1952
Service Protocol DB connection pool for the handler was always set to
default pool connection size of 16 even when it is changed for Audit
and Runtime. This issue is fixed and will pick up the values from Audit
and Runtime connection pool size values.
CR: EDIP-1959
When Outbound XML to EDI translation and validation is completed, the
document parser to check for Interchange ID/Qualifier was not released
which leads to a growth in memory. This would affect Inbound synchronous
transactions as well when the synchronous response is sent back to the
trading partner. This issue is fixed.
CR: EDIP-1960
Inbound processing of large transactions take longer time on Linux 64-bit
operating system. This was due to compile option not providing maximum
performance for Foresight Instream library. This issue is fixed.
CR: EDIP-1963
When BusinessConnect EDI engines crash during the batching of documents
which are in the RUNNING status due to certain abnormal conditions, the
documents do not go out to trading partner after restart of the engine.
This requires manual intervention to reset the statuses to PENDING or
resending the batch documents that were in the process.
RUNNING status indicates several internal states that includes batch transactions
being collated, ready for message packaging or packaged, sent to partner
and waiting for response and an internal RV communication waiting to
confirm. The engine could be in any of the above states. There are fixes
to address and separate reprocess of the batch documents automatically
when engines restart and for this to happen there are additional statuses
introduced (namely RUNNING_PKG_MARKED, RUNNING_SENT_FOR_PKG and
RUNNING_SENT_TO_TP) to tackle in terms of recovering and sending the
batches.
If the batched transactions are in collation state and the engine
crashes, users must still do manual intervention like before.
once in the RUNNING status after the batch is collated and ready to
sent to internal BC component for Enveloping and packaging the internal
status is changed to RUNNING_SENT_FOR_PKG and if the engine crashes during this
status and engine is restarted, the batched transaction would be reprocessed
automatically.
If the batch status in BC_SCHEDULED_TASK table is in RUNNING_SENT_FOR_PKG,
then the engine changes it to RUNNING_PKG_MARKED to process the collated
batch for transport level packaging before it is sent to trading partner.
If the engine has crashed during this status, then when the engine restarts,
this batch would be automatically processed.
If the batch status in BC_SCHEDULED_TASK table is in RUNNING_PKG_MARKED,
then the engine changes it to RUNNING_SENT_TO_TP status and sends it to the
trading partner and waits for response. If the engine crashes during the status
and restarted, then the engine looks at the partner response if available and
appropriately mark it as either COMPLETED or ERROR status.
Issue/Introduction
TIBCO BusinessConnect EDI Protocol powered by Instream 6.4.0 hotfix 2 has been released.
Environment
Product: TIBCO BusinessConnect EDI Protocol
Version: 6.4.0
OS:
--------------------
Feedback
Yes
No
Powered by
