Transaction and Operations |
Any transaction is a set of operations that DataPorter™ can perform on the configured items. Based on a built-in transaction engine, DataPorter™ can copy, calculate, store and read from database or publish the configured items on the Web. Execution of transactions or operations can be controlled by the configured conditions.
This topic contains the following sections:
Operations sequenceDataPorter™ uses an advanced transaction engine, which executes operations in a defined sequence. Operations can have parameters, inputs and outputs. Outputs of the current operation can be used as an input (argument) for the next operation in the sequence.
Transactions can be in one of the following states:
Inactive state – the transaction is waiting till the transaction manager tests execution conditions for this transaction.
Test state – the transaction is tested whether conditions allow the execution of the content (MinUpdateRate and Deadband events are checked).
Execution state – operations from this transaction are executed.
More information