IDE configuration
To begin configuration, you can drag the DTC icon on the NetConfig or select from the
menu. Specific properties are:- A list of DTC states, with options to add and delete states.
- Option to mark one state as a Start, another as a Stop state, and another as a Wait state.
- A user interface to define a state transition.
- A check box to indicate if transactions are enabled.
- Add Action, Rollback TPS to each state.
Actions are optional, in which case the message is routed directly to the thread.
- A TPS to generate transaction
IDs. If left blank, then transaction IDs are auto-generated.
This is independent of whether transactions are enabled.
- Max Steps
This table shows the options for different states:
Next | State | ||||
---|---|---|---|---|---|
State | Action | Code | State/Thread | Rollback | |
START
|
StartAction.TPS
|
DATA
|
COMPLETE
|
OUTBOUND
|
StartRollback.TPS |
EMPI
|
EMPIAction.TPS
|
DATA
|
COMPLETE
|
OUTBOUND
|
EMPIRollback.TPS |
DEMOGRAPHICS
|
DemoAction.TPS
|
DATA
|
COMPLETE
|
OUTBOUND
|
DemoRollback.TPS
|
QUESTIONAIRE
|
QAction.TPS
|
DATA
|
COMPLETE
|
OUTBOUND
|
QRollback.TPS
|
OUTBOUND
|
OutboundAction.TPS
|
DATA
|
SEND
|
outbound_thread
|
OutboundRollback.TPS
|
STOP
|
StopAction.TPS |
StopRollback.TPS |
By default, DTC has two states, a Start state and an End state. These are pre-filled in the DTC Properties Properties dialog box.
States can be added and deleted by clicking the appropriate button.
Routes can be added to other threads from the DTC thread. These thread names can be selected in response to SEND transition codes from the Properties dialog box. You can have a use case that might only do processing, and not route messages in a particular state.