Rockwell Automation FactoryTalk Transaction Manager User Guide - Manual (Page 98)

●
●
●
●
●
FactoryTalk Transaction Manager User Guide
98
perform functions that were previously possible only through custom
application development. Applications that are possible with this type of
transaction include:
 Product parameter downloading.
 Dynamic routing.
 Dynamic production scheduling.
 Controller centralizing.
 Production floor interacting.
 Automated storage and retrieval warehousing.
A bidirectional transaction with input/output bindings implements a data
transfer from the enterprise system and sends it to the control system,
binding database stored procedure input and output parameters. The control
system data serves as input to a stored procedure. The results of a stored
procedure can be written back to data points in the control system (enabling
the creation of sophisticated transactions that allow a high degree of
interaction between a database system and the factory floor).
Transactions with output bindings must use the Real Time Thread Storage
option on the Transaction Definition dialog box because the procedure or
method must complete before data can be returned to the Transaction
Control Manager service or FactoryTalk Transaction Manager service.
FactoryTalk Transaction Manager allows you to specify the number of
database threads used by a connector to improve performance.
When creating a transaction using input/output bindings, parameters are
bound in the same manner as columns in a table. The input data points are
collected, any expressions are evaluated, and the procedure is called. If the
procedure succeeds, any output parameters are written to the control system.
Transactions with input/output bindings use the following types of
parameters:
 Input parameters. In a stored procedure, these parameters must have a
binding (a data point, expression, or a null). Select a data object