Use Checkpoint activity after the DataEventPoller activity to recover the data while exceptions happen.
Article ID: KB0076220
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveMatrix BusinessWorks Plug-in for Database | 8.x |
Description
In TIBCO ActiveMatrix BusinessWorks process, DataEventPoller activity of with TIBCO ActiveMatrix BusinessWorks Plug-in for Database, If a failure happens after the DataEventPoller activity and before the end of the handling next logic, there would cause a data loss, But with database adapter published data is never lost because after publishing the data it will be available in the messaging layer.
Issue/Introduction
Confirm DataEventPoller event in TIBCO ActiveMatrix BusinessWorks Plug-in for Database
Environment
===================================================
Product:TIBCO ActiveMatrix BusinessWorks Plug-in for Database
Version: 8.x
OS: All Supported Operating Systems
====================================================
Resolution
The DataEventPoller activity of TIBCO ActiveMatrix BusinessWorks Plug-in for Database is the ActiveMatrix BusinessWorks activity, it uses the different approach to against data lose from TIBCO ActiveMatrix BusinessWorks Database Adapter. ActiveMatrix BusinessWorks has a "Checkpoint" activity.
Checkpoint is an asynchronous activity that executes a checkpoint in a running process instance. A checkpoint saves the current process data that can be recovered, if the event fails. If a process engine fails, all the process instances can be recovered and resume the execution of their last checkpoint in the process. Configuring the process engine to checkpoint data for the failed process helps optionally, to recover the process instance at a later stage. This happens if the process fails due to an exception that cannot be handled or terminated manually.
Database adapter sends the data to messaging layer while the database plugin does not sends the data to messaging layer because messaging layer is not available for database plugin. Because of the messaging layer in database adapter, It can control when to confirm the data, while in TIBCO ActiveMatrix BusinessWorks has checkpoint activity to avoid the data loss which can be used after DataEventPoller activity of database plugin.
Checkpoint is an asynchronous activity that executes a checkpoint in a running process instance. A checkpoint saves the current process data that can be recovered, if the event fails. If a process engine fails, all the process instances can be recovered and resume the execution of their last checkpoint in the process. Configuring the process engine to checkpoint data for the failed process helps optionally, to recover the process instance at a later stage. This happens if the process fails due to an exception that cannot be handled or terminated manually.
Database adapter sends the data to messaging layer while the database plugin does not sends the data to messaging layer because messaging layer is not available for database plugin. Because of the messaging layer in database adapter, It can control when to confirm the data, while in TIBCO ActiveMatrix BusinessWorks has checkpoint activity to avoid the data loss which can be used after DataEventPoller activity of database plugin.
Additional Information
https://docs.tibco.com/pub/activematrix_businessworks/6.4.2/doc/html/GUID-F0B8CCCA-6CDC-4CC5-8C8B-FE054A724053.html
Feedback
Yes
No
Powered by
