Now (opens new window)

Now (opens new window)
USER GUIDE
PUBLICATION RSSQL-UM001H-EN-P-April 2011
Supersedes Publication RSSQL-UM001G-EN-P
●
●
●
Copyright
●
●
Contact Rockwell Customer Support Telephone — 1.440.646.3434
Online Support — http://www.rockwellautomation.com/support
Copyright Notice © 2011 Rockwell Automation Technologies, Inc. All rights reserved.
This document and any accompanying Rockwell Software products are copyrighted by
Rockwell Automation Technologies, Inc. Any reproduction and/or distribution without prior
written consent from Rockwell Automation Technologies, Inc. is strictly prohibited. Please
refer to the license agreement for details.
Trademark Notices FactoryTalk, Rockwell Automation, Rockwell Software, the Rockwell Software logo are
registered trademarks of Rockwell Automation, Inc.
The following logos and products are trademarks of Rockwell Automation, Inc.:
RSBizWare, FactoryTalk Metrics, and FactoryTalk Transaction Manager.
Other Trademarks Microsoft, SQL Server, Event Viewer, Windows, Windows Server 2003, and Windows
Server 2008 are either registered trademarks or trademarks of Microsoft Corporation in the
United States and/or other countries.
Adobe, Acrobat, and Reader are either registered trademarks or trademarks of Adobe
Systems Incorporated in the United States and/or other countries.
All other trademarks are the property of their respective holders and are hereby
acknowledged.
Warranty This product is warranted in accordance with the product license. The product’s performance
may be affected by system configuration, the application being performed, operator control,
maintenance and other related factors. Rockwell Automation is not responsible for these
intervening factors. The instructions in this document do not cover all the details or variations
in the equipment, procedure, or process described, nor do they provide directions for meeting
every possible contingency during installation, operation, or maintenance. This product’s
implementation may vary among users.
This document is current as of the time of release of the product. However, the accompanying
software may have changed since the release. Rockwell Automation, Inc. reserves the right to
change any information contained in this document or the software at anytime without prior
notice. It is your responsibility to obtain the most current information available from
Rockwell when installing or using this product.
2
Contents
Chapter 1
Welcome To FactoryTalk Transaction Manager
13
What Is FactoryTalk Transaction Manager? ................................. 13
What Can FactoryTalk Transaction Manager Do For Me? ................. 13
Automate Data Logging .................................................... 13
Control the Plant Floor Using Business Rules and Quality
Enforcement ................................................................. 14
Manage Recipes .............................................................. 14
Understanding FactoryTalk Transaction Manager Concepts ............. 14
Transaction Control Manager Service .................................... 15
FactoryTalk Transaction Manager Service and Control Connectors 17
Control Connectors ......................................................... 18
Enterprise Connectors ...................................................... 18
Configuration Server ........................................................ 18
Transactions .................................................................. 19
FactoryTalk ....................................................................... 19
FactoryTalk Services Platform Components ............................ 20
Intended Audience .............................................................. 21
Where Can I Go For Help?...................................................... 22
3
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
Online Help ................................................................... 22
Product Manual .............................................................. 22
Training ....................................................................... 23
Technical Support ........................................................... 23
Get Web Support ............................................................ 24
Get Phone Support .......................................................... 24
Get Consulting Services .................................................... 24
Contact Us .................................................................... 24
Chapter 2
Installing FactoryTalk Transaction Manager
27
Before You Begin ................................................................ 27
Hardware Requirements ................................................... 27
Software Requirements .................................................... 28
Software Compatibility ..................................................... 30
Activation ..................................................................... 30
Activation Options .......................................................... 33
Installing FactoryTalk Transaction Manager Software .................... 36
Distributed FactoryTalk Transaction Manager Installations ......... 38
Chapter 3
Exploring the FactoryTalk Transaction Manager User Interface
41
Starting FactoryTalk Transaction Manager ................................. 41
Exploring the FactoryTalk Transaction Manager User Interface ........ 42
Title Bar....................................................................... 43
Menu Bar ...................................................................... 44
Toolbar ........................................................................ 45
Configuration Tree .......................................................... 46
Workspace .................................................................... 49
Status Bar ..................................................................... 50
Configuration Checklist ........................................................ 50
4
●
●Contents
●
●
●
●
Step 1: Defining and Naming a New Configuration .................... 53
Step 2: Defining Connectors ............................................... 54
Step 3: Defining Data Points .............................................. 54
Step 4: Defining Data Objects ............................................ 55
Step 5: Defining Transactions ............................................. 55
Step 6: Verifying Transactions ............................................ 56
Miscellaneous .................................................................... 56
Viewing Configuration Properties ........................................ 56
Starting Configurations ..................................................... 57
Stopping Configurations .................................................... 58
Starting and Stopping Connectors ........................................ 58
Monitoring Configurations ................................................. 58
Understanding FactoryTalk Transaction Manager External Files ........ 60
Using the Service Console ..................................................... 61
Chapter 4
Understanding FactoryTalk Transaction Manager Services
63
Introducing FactoryTalk Transaction Manager Services .................. 63
Control Connectors ............................................................. 63
FactoryTalk Live Data ...................................................... 64
DDE ............................................................................ 64
RSLinx Classic OPC .......................................................... 65
RSView32 ..................................................................... 65
Generic OPC .................................................................. 66
Enterprise Database Connectors .............................................. 66
ODBC........................................................................... 67
Oracle OCI .................................................................... 67
Microsoft OLE DB ............................................................ 67
Enterprise Application Connectors ........................................... 67
Microsoft COM+ .............................................................. 68
Time-series Data Compression ............................................ 68
FactoryTalk Metrics ......................................................... 68
Enterprise Connector Options ................................................. 68
FactoryTalk Transaction Manager Service .................................. 69
Transaction Control Manager Service ........................................ 70
5
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
Configuration Server ............................................................ 70
Chapter 5
Defining Data Points
73
Introducing Data Points ........................................................ 73
FactoryTalk Live Data Data Points ........................................... 75
Selecting a Collection Mode ............................................... 76
Consecutive Data Point and Data Block Support ....................... 77
Selecting Timeout Properties ............................................. 78
Selecting a Substitution Option ........................................... 80
Preventing Stale and Mismatched Data ................................. 80
Specifying Quality ........................................................... 81
OPC Data Points ................................................................. 82
RSLinx Classic OPC Data Points ........................................... 82
Generic OPC Data Points ................................................... 83
RSView32 Data Points ...................................................... 83
DDE Data Points ............................................................. 84
Chapter 6
Defining Data Objects
87
Introducing Data Objects ...................................................... 87
Enterprise Database Objects .................................................. 89
Oracle Call Interface (OCI) Data Objects ............................... 89
Microsoft SQL Server Data Objects ........................................... 89
ODBC Data Objects .......................................................... 89
Enterprise Application Objects ............................................... 90
Microsoft COM+ Data Objects ............................................. 90
FactoryTalk Metrics Data Objects ........................................ 91
Enterprise Connector Error Handling ........................................ 91
Inserting and Updating Data Table Records ................................ 93
Stored Procedures ............................................................... 93
Chapter 7
Creating Transactions
95
Introducing Transactions ....................................................... 95
Transaction Types ............................................................... 96
6
●
●Contents
●
●
●
●
Unidirectional Transactions ............................................... 97
Bidirectional Transactions ................................................. 97
Bidirectional or Unidirectional Transactions With Transaction
Bindings ....................................................................... 99
Transaction Timeout .......................................................... 101
Transaction Completion ...................................................... 102
Cached Transactions ...................................................... 102
Real-time Transactions ................................................... 102
Bidirectional Transactions ............................................... 104
Transactions With Bound Transaction Results........................ 104
Database Triggers ......................................................... 104
Expression Editor .............................................................. 104
Logical and Mathematical Operations ................................. 105
Time Functions ............................................................ 106
Data Point Range and Advanced Functions ........................... 106
Parse Function ............................................................. 107
Chapter 8
Understanding Online Edits
111
Introducing Online Edits ..................................................... 111
Understanding Online Edit Concepts....................................... 111
Online Edits Workflow .................................................... 112
Configurations That Use Online Edits .................................. 114
Learn More About Current and Pending Edits ........................ 115
Assembling Pending Edits ................................................ 116
Canceling Pending Edits .................................................. 117
Pending Edit Alerts ........................................................ 118
Creating a Configuration That Uses Online Edits ........................ 121
Editing Data Points In a Running Configuration That Uses Online Edits
............................................................................... 121
Editing Transactions In a Running Configuration That Uses Online
Edits ......................................................................... 124
Chapter 9
Exploring Advanced Topics
131
Introducing Advanced Topics ................................................ 131
Remote User Interface ....................................................... 131
7
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
Configuring the Remote User Interface ...............................
Distributed Configurations ...................................................
Licensing Required For a Distributed Configuration ................
Establishing Microsoft Windows Privileges ............................
Creating a Distributed Configuration ..................................
Using UNC Paths ...........................................................
Data Point Buffering ......................................................
Increasing Performance ......................................................
Control System .............................................................
Database ....................................................................
FactoryTalk Transaction Manager ......................................
Hardware and Operating Environment ................................
Appendix A FactoryTalk Transaction Manager Sample Applications
132
133
133
134
134
134
135
138
138
138
139
140
143
External Trigger Sample Application ...................................... 143
Contents .................................................................... 143
Running the Application .................................................. 144
Appendix B FactoryTalk Transaction Manager and Microsoft COM+ Objects147
Introducing FactoryTalk Transaction Manager and Microsoft COM+
Objects .......................................................................... 147
Creating the Remote Component .......................................... 147
Creating the Client Application ............................................. 148
Installing the Remote Component .......................................... 149
Setting Up the Remote Client ............................................... 150
Creating the Microsoft COM+ Setup Program ............................. 150
Moving the Client Sample Application ..................................... 151
Including the COM+ Enterprise Application Connector In a FactoryTalk
Transaction Manager Configuration ........................................ 152
Defining the COM+ Enterprise Application Connector .................. 152
Defining the COM+ Data Object ............................................ 153
Code Sample A (ComSampleVB) ............................................ 154
Code Sample B (ClientSampleVB) .......................................... 155
8
●
●Contents
●
●
●
●
Appendix C Securing FactoryTalk Transaction Manager Using FactoryTalk
Security
159
About FactoryTalk Security .................................................. 159
Considerations When Using FactoryTalk Transaction Manager With
FactoryTalk Security .......................................................... 159
Specify FactoryTalk Security Permissions That Allow You To Perform
FactoryTalk Transaction Manager Tasks .................................. 162
FactoryTalk Transaction Manager Behaviors When the FactoryTalk
Security Single Sign-on User Is In Effect .................................. 165
Overview .................................................................... 166
At FactoryTalk Transaction Manager Start Up ....................... 166
When Using FactoryTalk Transaction Manager ....................... 168
Writing Product-Specific Security Privileges From a Previous Release
To a File .................................................................... 169
Map Old Product-Specific Security Privileges To the New FactoryTalk
Security Permissions ...................................................... 170
Appendix D Glossary
173
Index .................................................................. 181
9
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
10
Figures
Figures
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
1: FactoryTalk Transaction Manager Functions (1) ................... 16
2: FactoryTalk Transaction Manager Functions (2) ................... 17
3: FactoryTalk Transaction Manager Functions (3) ................... 42
4: FactoryTalk Transaction Manager Title Bar ........................ 43
5: FactoryTalk Transaction Manager Menu Bar ........................ 44
6: FactoryTalk Transaction Manager Configuration Tree ............ 47
7: Error Log File View ...................................................... 49
8: Transaction Definition View ........................................... 50
9: FactoryTalk Transaction Manager Configuration Checklist ...... 52
10: FactoryTalk Data Point dialog box .................................. 74
11: Data Object Definition dialog box .................................. 88
12: Transaction Monitor ................................................... 92
13: Transaction Definition dialog box ................................... 96
14: Expression Editor dialog box ....................................... 105
15: Online Edits Workflow diagram ................................... 113
16: Pending Edit Alerts dialog box..................................... 120
17: FactoryTalk Transaction Manager Configuration ............... 121
18: Transaction Definition dialog box ................................. 124
19: Transaction Differences dialog box ............................... 127
20: Communication scheme ............................................ 132
11
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
12
Chapter 1
Welcome To FactoryTalk Transaction
Manager
What Is FactoryTalk Transaction Manager?
FactoryTalk Transaction Manager (previously known as RSSql) is an
industrial transaction software engine that shares data between your shop
floor systems and your enterprise applications (for example, corporate
databases) or COM+. FactoryTalk Transaction Manager can interact with
the following shop floor systems:

Human Machine Interfaces (HMI)

Programmable Logic Controllers (PLC)

ControlLogix Controllers

Distributed Control Systems (DCS)
What Can FactoryTalk Transaction Manager Do For Me?
FactoryTalk Transaction Manager helps you to manage your manufacturing
processes by integrating the data in your control systems with enterprise
applications. The following three sections describe examples of FactoryTalk
Transaction Manager applications.
Automate Data Logging
FactoryTalk Transaction Manager can move large amounts of data in a fast
and robust manner. In addition, the software has built-in fault tolerance and
13
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
the ability to optimize reading and writing of both control and enterprise
data. You can use the software to automate the following types of processes:

Monitoring performance of control systems such as machine usage.

Tracking product information such as Work in Progress status and raw
material availability.

Updating real-time process information such as temperature, pressure,
and alarm states.
Control the Plant Floor Using Business Rules and
Quality Enforcement
FactoryTalk Transaction Manager provides the interface for a repository of
business rules. A business rule can be any logic required to run your plant
such as product specifications or quality parameters. By placing business
rules in a database or COM+ server in a central location, the rules are easier
to manage within an enterprise system. Additionally, the software can assure
quality data to meet the requirements of today’s advanced manufacturing
companies.
Manage Recipes
FactoryTalk Transaction Manager moves data (for example, recipe
information) from a database to an HMI or control system.
Understanding FactoryTalk Transaction Manager
Concepts
FactoryTalk Transaction Manager consists of several design-time and
run-time components. This guide describes the following components in
detail: Transaction Control Manager service, FactoryTalk Transaction
Manager service, control connectors, enterprise connectors, Configuration
Server, and transactions.
14
●
1 ●Welcome To FactoryTalk Transaction Manager
●
●
●
●
Transaction Control Manager Service
The Transaction Control Manager is a service that controls and executes
FactoryTalk Transaction Manager transactions contained in a configuration,
but with the additional functionality of the FactoryTalk Live Data control
connector embedded in it. In an edit enabled configuration, the Transaction
Control Manager replaces the separate FactoryTalk Transaction Manager
and control connector services.
15
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
The Transaction Control Manager service can connect to Rockwell Software
products and all OPC servers; therefore, the use of this service is the
preferred method for all new FactoryTalk Transaction Manager
configurations. For more information on how the Transaction Control
Manager service functions, see the following figure.
Figure 1: FactoryTalk Transaction Manager Functions (1)
In a configuration that uses online edits, the Transaction Control Manager
service performs the duties of the FactoryTalk Transaction Manager service.
For more information on online edits, see Chapter 8, Understanding Online
Edits (page 111).
16
●
●
1 ●Welcome To FactoryTalk Transaction Manager
●
●
●
FactoryTalk Transaction Manager Service and Control
Connectors
The FactoryTalk Transaction Manager service is used to control and execute
FactoryTalk Transaction Manager transactions contained in configurations
created prior to CPR 7 or when you have a business reason to not run the
Transaction Control Manager service. For more information on how the
FactoryTalk Transaction Manager functions, see the following figure.
Figure 2: FactoryTalk Transaction Manager Functions (2)
17
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
Control Connectors
The FactoryTalk Transaction Manager service interfaces with the industrial
control system device via a control connector. A control connector is a
Microsoft Windows 2003/XP/Vista/2008 R2 service that collects data from
a controller and sends it to the FactoryTalk Transaction Manager service in
the FactoryTalk Transaction Manager. You can use the following types of
control connectors: FactoryTalk Live Data, DDE, RSLinx Classic OPC,
RSView32, and Generic OPC. Control connectors can be used to reference
data points, or memory locations within your control or shop floor system,
such as ―tags‖ from an RSView32 application.
Enterprise Connectors
The Transaction Control Manager service and the FactoryTalk Transaction
Manager service interface with enterprise systems such as databases via an
enterprise connector service. An enterprise connector is a Microsoft
Windows 2003/XP/Vista/2008 R2 service that transfers data between the
Transaction Control Manager service or the FactoryTalk Transaction
Manager service and a database. You can use the following types of
enterprise connectors: Open Database Connectivity (ODBC), Oracle Call
Interface (OCI), Microsoft OLE DB, Microsoft COM+, Time-series Data
Compression, and FactoryTalk Metrics. Enterprise connectors can be used
to create data objects that reference elements in your enterprise system, such
as tables or stored procedures.
Configuration Server
The Configuration Server is a Microsoft Windows 2003/XP/Vista/2008 R2
service that runs continuously to provide a single interface to the
configuration (.dat) files that make up the FactoryTalk Transaction Manager
configuration. The Configuration Server simplifies access to configuration
files by filtering all changes to the files and interfacing with other
FactoryTalk Transaction Manager services. A collection of all changes that
affect a configuration are recorded in an audit trail (via either FactoryTalk
Diagnostics or the Configuration Server *.log file). For more information,
see the FactoryTalk Transaction Manager online help.
18
●
1 ●Welcome To FactoryTalk Transaction Manager
●
●
●
●
Transactions
FactoryTalk Transaction Manager creates transactions, or discrete
operations that transfer data from your control system to/from the enterprise
system. For example, a single transaction can download data from an Oracle
database, via a stored procedure, to tags in a ControlLogix processor.
Alternately, a transaction can send multiple data points from a distributed
control system to a Microsoft SQL Server database to be logged for
reporting. Transactions can be modified at runtime; for more information,
see Chapter 8, Understanding Online Edits (page 111).
The transaction model organizes the task of data management. FactoryTalk
Transaction Manager’s flexibility provides many options for customizing all
aspects of a transaction. The software can manage many transactions at
once, allowing for sophisticated manufacturing data collection and control
applications. Using the software, you can also monitor, modify, and enable
or disable individual transactions, making the development and
implementation of an application easier.
FactoryTalk
FactoryTalk is a manufacturing information platform that integrates
plant-wide control systems and connects the enterprise with the production
facility.

Integrate - FactoryTalk eliminates both functionality gaps and overlaps
by providing common services (such as diagnostics and access to
real-time data) and by sharing plant resources (such as tags and graphic
displays) throughout a production facility.

Communicate - FactoryTalk transforms plant-floor data into useful
information and delivers it to the people who need it, from maintenance
engineers to enterprise planners.

Collaborate - FactoryTalk allows defining plant-floor resources once,
and then allows simultaneous access to those resources across system
boundaries.
19
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
FactoryTalk Services Platform Components
With each coordinated release, additional Rockwell Software products build
on the FactoryTalk platform and integrate more of the FactoryTalk
components. All of the FactoryTalk components install together as a
platform, integrated into each FactoryTalk-enabled product's install process.
The following sections discuss the FactoryTalk Services Platform
components.
FACTORYTALK DIRECTORY
FactoryTalk-enabled products use the FactoryTalk Directory to share a
common address book, which automatically finds and provides access to
plant-floor resources, such as data tags and graphic displays. Unlike a single
database, FactoryTalk Directory provides searchable references to resources
stored anywhere across an automation system, offering the benefits of
central data storage without the risk of a single point of failure. Changes
made to the automation system automatically update across all participants
in a FactoryTalk-enabled application.
FACTORYTALK LIVE DATA
FactoryTalk Live Data manages connections between FactoryTalk-enabled
products and data servers. It notifies clients when a connection is lost,
automatically reconnects, and combines data from multiple controllers and
servers into a single group with a single data server connection. This results
in faster real-time data transfer and more reliable, efficient connections to
data servers. It also assists in redundancy support for data servers by
automatically handling detection and failovers for all FactoryTalk-enabled
products.
FACTORYTALK ADMINISTRATION CONSOLE
The FactoryTalk Administration Console is a stand-alone tool that allows
you to configure and manage FactoryTalk-enabled applications.
20
●
1 ●Welcome To FactoryTalk Transaction Manager
●
●
●
●
FACTORYTALK AUDIT AND FACTORYTALK DIAGNOSTICS
FactoryTalk Audit and FactoryTalk Diagnostics provides the ability to log
errors, warnings, and other status messages generated throughout a
FactoryTalk-enabled system to either local logs or a central location.
FACTORYTALK SECURITY
FactoryTalk Security is intended to improve the security of your automation
system by limiting access to those with a legitimate need. FactoryTalk
Security authenticates user identities and authorizes user requests to access a
FactoryTalk-enabled system. These security services are fully integrated
into the FactoryTalk Directory and are included as part of the FactoryTalk
Services Platform that installs with many Rockwell Software products.
FactoryTalk Security replaces all of the product-specific privilege
configuration that was available in previous releases of FactoryTalk
Transaction Manager. For more information about using FactoryTalk
Transaction Manager with FactoryTalk Security, refer to Appendix C,
Securing FactoryTalk Transaction Manager using FactoryTalk Security
(page 159).
Intended Audience
We assume that you are a control engineer or database administrator and that
you are familiar most of the following:

Intel personal computers

Microsoft Windows 2003/XP/Vista/2008 R2 operating systems

DDE or OPC servers (for example, RSLinx Classic or RSView32)

Configuration of database connections such as ODBC, OCI, or
Microsoft OLE DB

Microsoft COM+

RSLinx Enterprise
21
●
●
●
FactoryTalk Transaction Manager User Guide
●
●

FactoryTalk View SE
Where Can I Go For Help?
Our commitment to your success starts with the suite of learning aids and
assistance we provide with FactoryTalk Transaction Manager. Consult the
following resources for additional information:

Online help

Product manual

Training

Technical support
Online Help
The online help provides general overview information, comprehensive
step-by-step procedures, quick start topics, and context-sensitive control
definitions (for example, text boxes, drop-down lists, and option buttons) for
working with all of the features in FactoryTalk Transaction Manager. You
can view online help in FactoryTalk Transaction Manager by using any of
the following methods:

select Help > FactoryTalk Transaction Manager Help on the main
FactoryTalk Transaction Manager user interface.

click Help on any FactoryTalk Transaction Manager dialog box.

click the What's This? icon in the upper-right corner of a FactoryTalk
Transaction Manager dialog box, then click any control to open a
definition of that control.
Product Manual
You can gain immediate access to product documentation by selecting Help
> Product Manuals > FactoryTalk Transaction Manager User Guide
from within FactoryTalk Transaction Manager. Throughout this document,
a number of style conventions are used to help identify material. File menu
22
●
1 ●Welcome To FactoryTalk Transaction Manager
●
●
●
●
paths are in bold with a (>) separating the entries (e.g., go to File > New);
text you are asked to type is shown in Courier Bold (e.g., in this field, type
Work Week), and button names are shown in bold (e.g., click OK).
Training
One of the best ways to increase your proficiency at using Rockwell
Software products is to attend Rockwell Software training programs. Our
training programs can help you master the basics and show you how to
unleash the full potential of our software.
We offer a wide range of training programs, from regularly scheduled
classes conducted at Rockwell Automation facilities to custom-tailored
classes conducted at your enterprise. The size of each class is kept small
intentionally to maximize student engagement.
If you would like more information about our training programs, visit the
Rockwell Software site on the World Wide Web or contact the Rockwell
Software Training Coordinator. Our World Wide Web address and
telephone numbers appear on the inside front cover of this document.
Technical Support
Rockwell Automation’s support team of outstanding professionals provides
top-notch technical support-monitoring and tracking your experience with
our products to pave the road to your success in understanding and
improving your factory performance.
Rockwell Automation provides full support for FactoryTalk Transaction
Manager. Questions concerning installation and the use of the software are
handled by the Rockwell Automation Customer Support Center, staffed
every day - except U.S. holidays - from 8 AM to 5 PM in your time zone for
calls originating within the U.S. and Canada.
To reach the Customer Support Center, call 1 (440) 646-3434 and follow the
prompts. For calls originating outside the U.S./Canada, locate the number in
your country by visiting http://www.rockwellautomation.com/locations.
23
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
Get Web Support
For web-based product support, and for detailed information on technical support
resources, please visit http://www.rockwellautomation.com/support/.
Access the Rockwell Automation Knowledge base for 24/7 technical
information and assistance. You can also download software patches and
new software versions, ask questions via email, participate in user forums,
and access other useful problem-solving tools.
The support resources available vary depending upon the product
purchased. The latest information can be obtained from the Rockwell
Automation Technical Support website.
A current TechConnect Support contract may be required to use some online
features.
Get Phone Support
To speak with a Technical Support representative in North America, call
1-440-646-3434.
For information on how to contact Technical Support in other locations
worldwide, please visit http://www.rockwellautomation.com/support/.
A current TechConnect Support contract may be required to obtain phone
support.
Get Consulting Services
Rockwell Automation provides expert consulting and turnkey
implementation of this product. Please contact your local representative for
more information.
Contact Us
We strive to help all of our customers become successful in their
manufacturing improvement efforts. Toward this objective, we invite you to
contact your local representative or Rockwell Automation at any time that
we may be of service to you.
24
●
1 ●Welcome To FactoryTalk Transaction Manager
●
●
●
●
25
Chapter 2
Installing FactoryTalk Transaction Manager
Before You Begin
You should know about the following prerequisites before you install
FactoryTalk Transaction Manager:

hardware requirements

software requirements

software dependencies

activation

activation options
See the following sections for more information.
Hardware Requirements
To use FactoryTalk Transaction Manager v10.10 effectively, your personal
computer must meet the following hardware requirements:

Intel Pentium processor (1 GHz or faster recommended) - single, dual,
or quad processors.

512 MB of RAM recommended (or more based on application
requirements).

34 MB of free hard disk space (or more based on application
requirements).

CD-ROM compatible drive.

256-color VGA graphics adapter (1024 x 768 or greater resolution).
27
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
Software Requirements
To use FactoryTalk Transaction Manager v10.10 effectively, the software
installed on your server computer must meet the following minimum
requirements.


One of the supported operating systems:

Microsoft Windows XP (Service Pack 3)

Microsoft Windows Server 2003 R2 Standard Edition (Service
Pack 2)

Microsoft Windows Vista Business (Service Pack 2)

Microsoft Windows Server 2008 R2
In order to use control connectors, you need one or more of the
following:

DDE server and/or OPC server software.

If you use the RSView32 control connector, you must have
RSView32 v7.40.00 or later.
RSView32 is not supported on Windows Server 2008 R2.

If you use the RSLinx Classic OPC control connector, you must
have RSLinx Classic v2.52.00 or later.
RSLinx Classic must be configured to start as a Microsoft Windows service.

28
In order to use enterprise connectors, you need one or more of the
following:

If you use an ODBC enterprise connector, you must have ODBC
Manager and ODBC drivers version 2.x or later.

If you use an Oracle OCI enterprise connector, you must use one of
the following types of Oracle databases:
●
2 ●Installing FactoryTalk Transaction Manager
●
●
●
●

Oracle 9i, with ODBC driver version 9.2.1.0, and Net client
driver version 9.2.0.1.0.

Oracle 10g, with ODBC driver version 10.2.0.1.0, and Net
client driver version 10.2.0.1.0.

Oracle 11g, with ODBC driver version 11.1.0.6.0, and Net
client driver version 11.1.0.6.0.
Oracle 10g and later supports all three types of client installations (Instant client,
Runtime and Administrator install).
Oracle databases created in version 10.2.0.1.0 and later are recommended. The use
of the Oracle ODBC drivers is not recommended.

If you use a Microsoft OLE DB enterprise connector, you must
have one of the following types of Microsoft SQL Server
databases:

SQL Server 2000 (Service Pack 4), with ODBC driver
SQLSRV32.DLL version 2000.85.1117.0

SQL Server 2005 (Service Pack 3), with ODBC driver
SQLSRV32.DLL version 2000.86.3959.0 and Net client
driver SQLNCLI.dll version 2005.90.4035.0.

SQL Server 2008 R2 with ODBC driver SQLSRV32.DLL
version 6.1.7600.16385 and Net client driver SQLNCLI.dll
version 2005.90.1399.0.

If you use Microsoft COM+, your Microsoft COM+ connector and
the FactoryTalk Transaction Manager configuration using it must
reside on a computer running one of the supported systems:

Microsoft Windows XP (Service Pack 3)

Microsoft Windows Server 2003 R2 Standard Edition (Service
Pack 2)

Microsoft Windows Vista Business (Service Pack 2)
29
●
●
●
FactoryTalk Transaction Manager User Guide
●
●

Microsoft Windows Server 2008 R2
Microsoft COM+ objects must be built using Microsoft Developer Studio 6.0.

Microsoft Windows 2003/XP/Vista/2008 R2 simple TCP/IP services
must be configured.

Microsoft Data Access Components (MDAC) is updated to version 2.8
during the FactoryTalk Transaction Manager installation.

Minimum video resolution of 1024 x 768.
Software Compatibility
FactoryTalk Transaction Manager v10.10 has been tested, and is
compatible, with the latest Rockwell Software release of the following
products:

FactoryTalk Services Platform (v2.30.01)

FactoryTalk Activation (v3.30.00)

RSView32 (v7.50.00)

FactoryTalk View SE (v5.20.00)

RSLinx Enterprise (v5.30.00)

RSLinx Classic (v2.56.00)
Activation
Rockwell Software's Windows-based software products are copy protected
and require an activation key, located in an activation file, to run the
software.
FactoryTalk Transaction Manager v10.10 supports the following activation
tools:

30
FactoryTalk Activation: If you are a new user, you will need to
activate your software using FactoryTalk Activation.
●
2 ●Installing FactoryTalk Transaction Manager
●
●
●
●

EvRSI activation: If you are a current user upgrading to FactoryTalk
Transaction Manager v10.10, your activation is already installed and
will be used automatically.
EvRSI activation will be replaced by FactoryTalk Activation in a future release. If you
are using EvRSI activation, please contact your local Rockwell Automation Sales
office or Technical Support for information on migrating your activations to
FactoryTalk Activation.
For Rockwell Automation Technical Support in the U.S. call 1 (440) 646-3434.
Outside the U.S. see http://www.rockwellautomation.com/locations.
When you launch FactoryTalk Transaction Manager, the software checks
for the activation file. If the system fails to detect the activation file, an error
is logged to FactoryTalk Diagnostics. Refer to the FactoryTalk Activation
online help for more information about diagnostic messages (go to
x:\Program Files\Common Files\Rockwell\Help\FTActivationEN.chm,
where x: is the drive where your Rockwell Software products are located).
FactoryTalk Transaction Manager software consists of several components.
The Transaction Control Manager service and the FactoryTalk Transaction
Manager service are copy protected, which means that you can run either of
these services on only one computer, per license, at a time. The Microsoft
COM+ enterprise application connector is also copy protected. If you have
FactoryTalk Transaction Manager Professional, you may install copies of
any of the other connectors on as many computers as necessary.
ACTIVATE USING FACTORYTALK ACTIVATION
FactoryTalk Activation provides a secure, software-based system for
activating Rockwell Software products and managing software activation
files. Activation files are generated and distributed via the Internet. If an
Internet connection is not available, activation file information can be
delivered via email, fax, or phone.
FactoryTalk Transaction Manager v10.10 supports floating, concurrent
activations.
31
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
To activate your software using FactoryTalk Activation, first determine
your activation server/client configuration:

One or more activation servers, one or more clients. You will need
to run the FactoryTalk Activation Server software on the network
computer(s) that will act as the activation server(s). You will need to
run the FactoryTalk Activation Client software on each of the client
computers. Then you will direct the client computers to the activation
server computer.

Activation server/client on each computer. You will need to run the
FactoryTalk Activation Server software on this computer. This
computer will then act as both the activation server and client.
For more information, see the FactoryTalk Activation online help.
ACTIVATE USING EVRSI ACTIVATION
EvRSI activation relied on a physical master disk that used to be supplied
with the FactoryTalk Transaction Manager product. If you are a current user
upgrading to the latest release, your activation is already installed and will
be used automatically.
For more information about EvRSI activation, refer to the Activation Help
(COPYPROT.HLP) by selecting Help > Copy Protection or by clicking
Help on any of the EvMove or Reset dialog boxes.
GRACE PERIOD
In FactoryTalk Transaction Manager v10.10, the software supports a seven
day activation grace period when a valid activation is not found. During
grace period:
32

When a configuration is started following an operating system reboot, a
message is logged to the FactoryTalk Diagnostic log every four hours
until a valid activation is found.

When a configuration is started from the software itself, you are
prompted to confirm entry into grace period mode. Upon confirmation,
a message is logged to the FactoryTalk Diagnostic log every four hours
●
2 ●Installing FactoryTalk Transaction Manager
●
●
●
●
on the computer running the Transaction Control Manager service or
FactoryTalk Transaction Manager service until a valid activation is
found.

FactoryTalk Transaction Manager can be started an unlimited number
of times. If the grace period ends and a valid activation has not been
found, you will no longer be able to start the software.
If FactoryTalk Transaction Manager is unable to successfully obtain valid activations
(for example, a network failure occurs), the software will attempt run in grace period
for up to seven days.
Activation Options
Activating FactoryTalk Transaction Manager software is determined by two
factors: whether the control and enterprise connectors can be distributed
among several computers and the maximum number of tags (data points)
that the Transaction Control Manager service or FactoryTalk Transaction
Manager service will support.
Please keep the following in mind about FactoryTalk Transaction Manager
activation:

FactoryTalk Transaction Manager previously was sold without a restriction on
the number of tags. Although this option is no longer available, customers who
own this version can continue without a tag restriction.

Each Microsoft COM+ connector must be installed on the same computer as
the Transaction Control Manager service or FactoryTalk Transaction Manager
service and requires a separate activation.

Any FactoryTalk Transaction Manager activation must be installed on the same
computer (when using EvRSI activation) or on either a centralized or local
activation server (when using FactoryTalk Activation) that will be running the
Transaction Control Manager service or the FactoryTalk Transaction Manager
service.
33
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
FACTORYTALK TRANSACTION MANAGER LITE
This embedded version of FactoryTalk Transaction Manager supports data
collection for RSBizWare components and allows you to create transactions
in FactoryTalk Historian Classic and FactoryTalk Metrics, which can then
be executed by the FactoryTalk Transaction Manager services. While
FactoryTalk Transaction Manager Lite is similar to FactoryTalk Transaction
Manager Professional and FactoryTalk Transaction Manager Standard, it
only supports creating and modifying data points, data objects, and
transactions defined by other RSBizWare components. FactoryTalk
Transaction Manager Lite does not support custom transactions created
outside of the RSBizWare suite. To use custom transactions in addition to
RSBizWare transactions, a FactoryTalk Transaction Manager activation is
required.
FactoryTalk Transaction Manager Lite cannot be purchased separately and does not
require a separate activation. FactoryTalk Transaction Manager Lite does not run in
Demo mode.
FACTORYTALK TRANSACTION MANAGER DEMO
FactoryTalk Transaction Manager Demo cannot be purchased separately.
This embedded version of FactoryTalk Transaction Manager runs when no
activation is installed or the software is not already running under grace
period. FactoryTalk Transaction Manager Demo is limited to two hours and
10 tags.
FACTORYTALK TRANSACTION MANAGER TRIAL
This version of FactoryTalk Transaction Manager allows you to run a
configuration that includes 50 tags for a period of seven days. After seven
days, FactoryTalk Transaction Manager servers will be shut down; these
servers can be restarted. FactoryTalk Transaction Manager Trial is not
compatible with configurations containing transactions that were created by
FactoryTalk Historian Classic or FactoryTalk Metrics.
34
●
2 ●Installing FactoryTalk Transaction Manager
●
●
●
●
An activation is required to run this version of FactoryTalk Transaction Manager. This
activation is available with RSView32 7.30.00 or later, and FactoryTalk ViewSE
5.00.00 or later.
SUMMARY
The table below shows the level of distribution and the maximum number of
tags supported for each FactoryTalk Transaction Manager activation.
The Availability column denotes sales availability (if the product is still for
sale). "No" denotes products that are no longer available for sale.
Catalog Number:
Class:
Availability:
Tag Limit:
9356-PRO2400
Unlimited Professional (1)
No
Unlimited
9356-PRO2500
Large Professional
Yes
70000
9356-PRO2450
Large Professional
Yes
32000
9356-PRO2350
Medium Professional
Yes
5000
9356-PRO2300
Medium Professional
Yes
1500
9356-PRO2200
Small Professional
Yes
300
9356-PRO2100
Small Professional
Yes
150
9356-STD2400
Unlimited Standard
No
Unlimited
9356-STD2350
FactoryTalk Transaction
Manager Standard
Yes
5000
9356-STD2300
Large Standard
Yes
1500
9356-STD2200
Medium Standard
Yes
300
9356-STD2100
Small Standard
Yes
150
9356-SQLCOMPLS
Microsoft COM+ Connector Yes
(1), (2)
N/A
35
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
Catalog Number:
Class:
Availability:
Tag Limit:
N/A
Trial
Free (3)
50
N/A
Demo
Free
10
N/A
FactoryTalk Transaction
Manager Lite
Free (3)
N/A
(1) Used when the software enters grace period.
(2) Sold for use with FactoryTalk Transaction Manager Professional only.
(3) With the purchase of other Rockwell Software products.
Installing FactoryTalk Transaction Manager Software
FactoryTalk Transaction Manager is installed from the FactoryTalk
Transaction Manager CD-ROM or the RSBizWare CD-ROM.
To perform the installation tasks, you must have the Windows System
Administrator privilege, and your user account must be a member of the
local administrator user group.
If you install FactoryTalk Transaction Manager on a system running Microsoft
Windows 2003/XP/Vista/2008 R2 that has not previously run Microsoft Windows
Installer (MSI), you will have to reboot the computer once the FactoryTalk Services
Platform is installed. You may also have to reboot the computer at the end of the
installation.
To install FactoryTalk Transaction Manager software, complete the
following steps:
36
1.
Log on to your system using an account with administrator privileges.
2.
Shut down any other Rockwell Software applications and services.
3.
If you are installing FactoryTalk Transaction Manager from the
FactoryTalk Transaction Manager CD-ROM, use autorun.exe or
●
2 ●Installing FactoryTalk Transaction Manager
●
●
●
●
setup.exe. If you are installing FactoryTalk Transaction Manager from
the RSBizWare CD-ROM, FactoryTalk Transaction Manager installs
automatically with any other RSBizWare service.
4.
After you have launched the FactoryTalk Transaction Manager
Welcome Page, click Required Steps. Click each of the following
options in the order specified below, to successfully install FactoryTalk
Transaction Manager.
1.
Check Operating System - Verifies your operating system and its
compatibility with the current version of FactoryTalk Transaction
Manager.
2.
Install Microsoft Internet Explorer - Installs Microsoft Internet
Explorer so that you can properly view the FactoryTalk
Transaction Manager online help files. Follow the instructions that
appear on the screen. If Microsoft Internet Explorer is already
installed, skip to step 4.3.
3.
View Release Notes - Displays the Release Notes, allowing you to
learn more about the current version of FactoryTalk Transaction
Manager prior to installing the software.
4.
Install FactoryTalk Services Platform - Installs the FactoryTalk
Services Platform on your computer. Follow the instructions that
appear on the screen.
At the end of the FactoryTalk Services Platform installation, the FactoryTalk Services
Platform Wizard appears. Follow the instructions that appear on the screen.
5.
Install FactoryTalk Activation Client - Installs the FactoryTalk
Activation Client on your computer. Follow the instructions that
appear on the screen.
6.
Install FactoryTalk Transaction Manager - Installs FactoryTalk
Transaction Manager on your computer. Follow the instructions
that appear on the screen.
37
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
7.
View “How to Activate Rockwell Software Products” Displays information on activating Rockwell Software products.
8.
Check for Product Updates - Displays the FactoryTalk
Transaction Manager Product Updates page, outlining any
software updates that may be available after this version of the
software was released.
5.
After you have completed all of the required steps of the FactoryTalk
Transaction Manager installation, either click Documentation and
Extras to display an optional page (which allows you to install Adobe
Acrobat Viewer, view the FactoryTalk Transaction Manager User
Guide, Release Notes, and other related documentation, display the
Application Trigger example, and launch the FactoryTalk Transaction
Manager Live Data Migration Tool), or proceed to step 6.
6.
When you have finished installing the software, remove the
FactoryTalk Transaction Manager CD-ROM from the CD-ROM drive.
Store it in a safe place.
Distributed FactoryTalk Transaction Manager
Installations
You may want to run FactoryTalk Transaction Manager or its services on
more than one computer. To run the software in a distributed mode, it must
be installed on all computers that are referenced in a configuration. For more
information, see Distributed Configurations (page 133) in Chapter
9,Exploring Advanced Topics.
38
●
2 ●Installing FactoryTalk Transaction Manager
●
●
●
●
39
Chapter 3
Exploring the FactoryTalk Transaction
Manager User Interface
Starting FactoryTalk Transaction Manager
To start FactoryTalk Transaction Manager, click Start on the Task bar, then
select Programs > Rockwell Software > FactoryTalk Transaction
Manager > FactoryTalk Transaction Manager.
41
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
Exploring the FactoryTalk Transaction Manager User
Interface
When you start FactoryTalk Transaction Manager for the first time (and if it
is the first Rockwell Software product run on your computer), you are
automatically logged on to FactoryTalk Security using your
Windows-linked user account information. The system graphic appears in
the right pane (or workspace) of the FactoryTalk Transaction Manager user
interface.
Figure 3: FactoryTalk Transaction Manager Functions (3)
For more information on FactoryTalk Security, see Appendix C, Securing
FactoryTalk Transaction Manager with FactoryTalk Security (page 159).
To view the procedures for configuring and using FactoryTalk Transaction
Manager, select Help > Quick Start.
42
●
3 ●Exploring the FactoryTalk Transaction Manager User Interface
●
●
●
●
The design elements on the main FactoryTalk Transaction Manager user
interface include:

Title bar

Menu bar

Toolbar

Configuration tree

Workspace

Status bar
Title Bar
The title bar shows the FactoryTalk Transaction Manager icon, the name of
the configuration or configuration server (depending on what is selected in
the configuration tree), the product name, and the Minimize, Maximize, and
Close buttons.
Figure 4: FactoryTalk Transaction Manager Title Bar
To view the Control Menu, click the FactoryTalk Transaction Manager icon
on the title bar. The following items appear on the control menu.
Item:
Description:
Restore
Restores the window to its former size after minimizing or maximizing it.
Move
Repositions the window on the desktop using the arrow keys on the keyboard.
Size
Resizes the window on the desktop using the arrow keys on the keyboard.
Minimize
Shrinks the window to an icon that is located on the task bar.
Maximize
Enlarges the window to occupy the entire screen.
Close
Exits the software.
43
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
Menu Bar
You can access many features from the FactoryTalk Transaction Manager
menu bar. For a description of the available shortcuts, refer to Section
Toolbar (page 45) in this chapter.
Figure 5: FactoryTalk Transaction Manager Menu Bar
The Security menu allows you to log on or log off of FactoryTalk Security,
or view your FactoryTalk Security permissions on the current configuration
server. For more information on FactoryTalk Security, see Appendix C,
Securing FactoryTalk Transaction Manager with FactoryTalk Security
(page 159).
The Configuration menu allows you to create a new configuration, set or
change properties in a configuration, access the Configuration Checklist,
delete, backup, or restore a configuration, or stop or start a configuration.
The Define menu allows you to define a connector, data object, data points,
or a transaction. In addition, you can define options for error logging and
scheduled events.
The View menu allows you to view information about the currently defined
transaction. You can view diagnostic information about the configuration
that is currently running. You can also view error log files or the system
graphic. This option allows you to switch between large and small icons,
obtain a status update, or enable or disable the toolbar or status bar.
The Tools menu allows you to create a configuration report, verify the
selected configuration, or use wizards to create data logging, duplicate data
points, or duplicate transactions. You can also use this menu to set message
and log viewer options.
The Help menu provides assistance with using FactoryTalk Transaction
Manager. From the Index of the online help system, simply enter the name
of the topic for which you want to search for information. Click the Help
44
●
3 ●Exploring the FactoryTalk Transaction Manager User Interface
●
●
●
●
graphic on the toolbar, and then place the cursor on any design element on
the system graphic for more information. The Help menu also provides
specific links for viewing the release notes, a quick start, the online books,
an error code resource, support and training,. In addition, you can use this
option to obtain FactoryTalk Transaction Manager license and version
information.
Toolbar
The toolbar contains shortcuts to several commonly used FactoryTalk
Transaction Manager functions. Each button on the toolbar is a graphical
representation of a command that is also available from the FactoryTalk
Transaction Manager menu bar.
Icon:
Description:
Creates a new FactoryTalk Transaction Manager configuration.
Displays the About FactoryTalk Transaction Manager dialog box.
Displays the online help for any design element (click this button and place
the cursor on any design element).
Starts the configuration or connector currently selected in the Configuration
tree. If the edit enabled configuration has pending edits, a message displays
prompting the user to ignore the pending edits and start the configuration
anyway.
Stops the configuration or connector currently selected in the Configuration
tree.
Assembles all data point and transaction pending edits in the edit enabled
configuration. For a detailed description of assembling pending edits, refer to
the chapter Understanding Online Edits (page 111).
Opens the Pending Edit Alerts dialog box. For a detailed description of
pending edit alerts, refer to the chapter Understanding Online Edits (page
111).
45
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
Icon:
Description:
Verifies the selected configuration. You can verify multiple transactions and
choose to save the results to a text file.
Displays information about the current transactions in the right pane of the
application workspace.
Displays diagnostic information about the configuration that is currently
running in the right pane of the application workspace.
Displays error log information in the right pane of the application workspace.
Displays the system graphic in the right pane.
Configuration Tree
The FactoryTalk Transaction Manager user interface is divided into two
panes. The left pane is known as the Configuration tree; it is a tree view of
the current configurations.
46
●
3 ●Exploring the FactoryTalk Transaction Manager User Interface
●
●
●
●
The top level is the Configuration Server, named for the computer on which
it is running. The second level is the configuration name. The third level
displays the Transaction Control Manager service (if the configuration uses
online edits) or the FactoryTalk Transaction Manager service. The
Transaction Control Manager service or the FactoryTalk Transaction
Manager service are followed by the control connectors and enterprise
connectors defined for the configuration. For a detailed description of the
Transaction Control Manager service’s role in a configuration that uses
online edits, see Chapter 8, Understanding Online Edits (page 111).
Figure 6: FactoryTalk Transaction Manager Configuration Tree
CONFIGURATION AND CONNECTOR STATUS
The traffic lights in the Configuration tree represent the status of
FactoryTalk Transaction Manager connectors and configurations, turning
from red to green when services are started. See the following table to
determine how each icon applies to connectors and configurations.
If you see
this icon:
A configuration is...
A connector is...
running properly; all connectors in running properly.
that configuration are running
properly. All transactions start based
on the triggering rules that you
defined.
47
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
If you see
this icon:
A configuration is...
A connector is...
experiencing one or more connectors n/a (this state does not apply to a
that are not functioning properly
connector).
stopped; all of the connectors are not not running properly.
running. Additionally, the
Transaction Control Manager
service or the FactoryTalk
Transaction Manager service is not
running.
CONFIGURATION SERVER STATUS
The icons that are displayed in the Configuration tree represent the status of
the configuration servers. The following table shows the status icons, state,
and a description of that state:
Icon:
Status:
Description:
Running
The configuration server host computer:
Unknown
48

Resides in the FactoryTalk Administration Console.

Is working properly (the service is running and FactoryTalk
Transaction Manager can connect to it).

Has been configured in the FactoryTalk Administration
Console so that the current user has permissions (page 162)
to communicate with it.
The configuration server host computer:

May or may not reside in the FactoryTalk Administration
Console.

Cannot be connected to or queried in FactoryTalk
Transaction Manager.

Cannot provide any information to FactoryTalk Transaction
●
3 ●Exploring the FactoryTalk Transaction Manager User Interface
●
●
●
●
Icon:
Status:
Description:
Manager so that the software can determine why it is not
working properly.
No privilege The configuration server host computer:

Resides in the FactoryTalk Administration Console.

Is working properly.

User does not have permissions (page 162) to
communicate with the Configuration Server.
Workspace
The right pane of the FactoryTalk Transaction Manager user interface is the
workspace; it displays the Transaction Definition View, the Transaction
Monitor View, the Error Log Files View, or the FactoryTalk Transaction
Manager system graphic, depending on the view option that you have
selected. The Error Log File View is displayed below.
Figure 7: Error Log File View
TRANSACTION STATES
Transactions display in the Transaction Definition view. The states are
described below:

Current - The current definition of a transaction (with or without
pending edits).

Edit Pending - Changes that are made to the current transaction
definition, but not assembled.

Add Pending - A new transaction (created online), but not assembled.
49
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
The following is an example Transaction Definition View.
Figure 8: Transaction Definition View
Status Bar
The status bar at the bottom of the main FactoryTalk Transaction Manager
user interface displays the following information:

Rows Selected (includes pending edits). The number of rows selected
before you saved, assembled or canceled pending edits.

Transactions Selected. The number of transactions selected.

Passed. The number of successful operations.

Disregarded. FactoryTalk Transaction Manager does not allow the
action to be performed.

Failed. Operations that did not take place because of an internal error.
Configuration Checklist
A FactoryTalk Transaction Manager configuration consists of a set of
transactions that use control and enterprise connector elements required to
perform the transactions. You may create many configurations, but the
Transaction Control Manager service or the FactoryTalk Transaction
Manager service can run only one configuration at a time. Therefore, all the
50
●
3 ●Exploring the FactoryTalk Transaction Manager User Interface
●
●
●
●
transactions required to implement an application must be contained in a
single configuration.
Create a configuration using the Configuration Checklist, which lists the
required steps and displays the progress of your configuration. A green
check mark indicates a completed step, while a yellow check mark indicates
a partially completed step.
51
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
Select Configuration > Checklist or Configuration > New to begin using
the Configuration Checklist. The following figure shows the Configuration
Checklist:
Figure 9: FactoryTalk Transaction Manager Configuration Checklist
This chapter is not intended to provide step-by-step directions for creating a
configuration, but to provide an overview to help you understand
configurations. The following sequence mimics the Configuration
52
●
3 ●Exploring the FactoryTalk Transaction Manager User Interface
●
●
●
●
Checklist. It is recommended, at least initially, that you follow this sequence
when creating configurations:

Define and name a new configuration.

Define control and enterprise connectors.

Define the data points that will be used in transactions.

Define the data objects that will be used in transactions.

Define transactions, which transfer data between data points, in the
control system and data objects.

Verify transactions.
The following sections provide additional details for each task in the
sequence. For more information, see the Quick Start in the FactoryTalk
Transaction Manager online help (select Help > Quick Start).
Step 1: Defining and Naming a New Configuration
To create a new configuration, enter a configuration name, and then click
Step 1 to open the FactoryTalk Transaction Manager Configuration dialog
box. Enter a name for the configuration and the directory path in which the
configuration (*.dat) files will reside. This directory becomes the default
location of the other files used in the configuration. Select the control and
enterprise connector service types to use in the configuration. To create a
distributed configuration, see Chapter 9, Exploring Advanced Topics (page
131).
Each configuration must have an unique name and directory path.
To create a configuration that uses online edits, you can select only the
FactoryTalk Live Data control connector. You may select any enterprise
connector. Make sure to select the Enable Online Edits check box. For more
information, see Chapter 8, Understanding Online Edits (page 111).
53
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
Step 2: Defining Connectors
To begin defining a connector, select the service to define from the
drop-down list of connector services. Click Step 2 to open the Connector
Definition dialog box. This dialog box allows you to configure
communication and security settings for the Microsoft Windows
2003/XP/Vista/2008 R2 services.
You can create multiple control or enterprise connectors in a configuration,
but you can create only one connector of each type on each host computer. A
FactoryTalk Transaction Manager Professional activation is required to
distribute connectors.
Only one instance of the Transaction Control Manager service or the FactoryTalk
Transaction Manager service can be used by a configuration.
The connector service uses the Microsoft Windows user name and password
assigned to the connector when it runs on the host computer.
In general, control connectors must run on the computer that contains the
data server to which they will communicate. This is not the case with some
OPC servers that support DCOM or OPC used in a FactoryTalk architecture.
After this step is complete (and you exit the Configuration Checklist), the
configuration displays in the Configuration tree. Click the plus sign next to a
configuration to expand it. Each connector service that is used by the
configuration displays. Individual control and enterprise connectors display
under the connector services. The Configuration tree displays all
configurations recognized by each registered configuration server.
Step 3: Defining Data Points
From the Configuration Checklist, define the data points in the control
system that you wish to use in a configuration. For more information about
data points, see Chapter 5, Defining Data Points (page 73). If you have
multiple control connectors, you must configure them individually. Select
the connector for which you wish to add or edit points, then click Step 3. In
a configuration that uses online edits, you can perform Step 3 on the
54
●
3 ●Exploring the FactoryTalk Transaction Manager User Interface
●
●
●
●
Configuration Checklist while the configuration is running. For information
about distributing control connectors and remote browsing capabilities, see
Chapter 9, Exploring Advanced Topics (page 131).
Step 4: Defining Data Objects
To begin defining a data object, select the enterprise connector to define
from the dropdown list. Click Step 4 to configure connections to the
database and create a data object. For more information about enterprise
connectors, see Chapter 6, Defining Data Objects (page 87).
From the Data Object Definition dialog box, select the table, view, or
connection (or appropriate enterprise object for your type of connector) to
configure the data object to use. Depending on the connector type, different
properties display, such as whether to insert or update the rows in the table
you select. For information about distributing enterprise connectors, see
Chapter 9, Exploring Advanced Topics (page 131).
Step 5: Defining Transactions
You can create transactions that move data between a control system and an
enterprise application or database. Click Step 5 to open the Transaction
Definition dialog box. Provide a name for the transaction, and then select the
data object to which you want to bind (the process of mapping a column in a
database table to a data point) the data points. The data object’s columns or
parameters appear in the list of available bindings near the bottom of the
dialog box.
Each transaction name must be unique.
You can bind individual data points or an expression to a
column/field/parameter in a data object. Double-click a non-bound entry in
the Data Object Column to open the Filter and Select Data Points dialog box
or right-click and select Filter and Select Data Points from the menu. You
can limit the list of data points by a connector and/or device. Bind the data
point to the data object by dragging it from the Filter and Select Data Points
55
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
dialog box and dropping it onto the appropriate Data Object Column in the
Transaction Definition dialog box.
From the Transaction Definition dialog box, open the Trigger and Storage
Parameters dialog box to specify the events that will initiate your
transactions and timeout values. For more detailed information about
transactions, see Chapter 7, Creating Transactions (page 95).
In a configuration that uses online edits, you can edit existing or create new
transactions while the configuration is running. When you have pending
edits, you can view the differences between the current and pending
definitions on the Transaction Differences dialog box. If the pending edits
that you created have caused pending edit alerts, you can view them on the
Pending Edit Alerts dialog box. For a detailed description of the information
displayed on these dialog boxes, see Chapter 8, Understanding Online Edits
(page 111).
Step 6: Verifying Transactions
To verify multiple completed transactions, click Verify on the
Configuration Checklist. You can also verify transactions individually from
the Transaction Definition dialog box, which provides informational
messages or warnings about the configuration.
Miscellaneous
Viewing Configuration Properties
To open the Configuration Properties dialog box, select Configuration >
Properties or right-click a configuration name in the Configuration tree and
select Configuration Properties from the menu. You can access all
configuration level settings, such as enterprise connector options and error
logging levels, from individual tabs on this dialog box.
56
●
3 ●Exploring the FactoryTalk Transaction Manager User Interface
●
●
●
●
Starting Configurations
If you are starting a FactoryTalk Transaction Manager configuration, you must be
logged into a Microsoft Windows 2003/XP/Vista/2008 R2 account that has
administrative privileges for all computers that are part of the FactoryTalk
Transaction Manager system. This is required by the Microsoft Windows
2003/XP/Vista/2008 R2 Service Control Manager to be able to start and stop
FactoryTalk Transaction Manager services.
Only the Transaction Control Manager service or the FactoryTalk
Transaction Manager service can run at one time. Further, the Transaction
Control Manager service or the FactoryTalk Transaction Manager service
can run only one FactoryTalk Transaction Manager configuration at a time;
the configuration runs until it is stopped. You can start a FactoryTalk
Transaction Manager configuration by using one of the following methods:

Select the configuration name in the Configuration tree, right-click, and
select Start Configuration from the menu.

Select the configuration name in the Configuration tree, then click Start
on the toolbar.
If you are using a distributed configuration, make sure all remote computers that are
used in the configuration are running and available before you start the configuration.
If the software encounters a remote computer that is not running or available, it will
proceed to the next running and available computer.
If your configuration includes RSView32 or FactoryTalk View SE, ensure that these
products are running on the appropriate host computer and the project that is used
by the configuration is loaded and running before you start the configuration.
Once you have started a configuration manually, you can set the
configuration to autostart by performing the following steps:
7.
Select Start > Settings > Control Panel > Administrative Tools >
Services. The Services dialog box appears.
8.
Navigate through the Services list, select either the FactoryTalk
Transaction Manager Transaction and Control Manager service or the
FactoryTalk Transaction Manager service (depending on your
57
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
configuration), and double-click the mouse. The Properties dialog box
appears.
9.
In the Start-up field, select Automatic.
10. Click OK.
11. Repeat steps 2 through 4 for each connector service in your
configuration.
The Transaction Control Manager service and the FactoryTalk Transaction Manager
service cannot be set to Auto-start at the same time.
Stopping Configurations
You can stop a configuration by using one of the following methods:

Select the configuration name in the Configuration tree, right-click and
select Stop Configuration from the menu.

Select the configuration name in the Configuration tree, then click Stop
on the toolbar.
You cannot stop the configuration by exiting FactoryTalk Transaction
Manager or logging off of the computer. For more information, see Chapter
9, Exploring Advanced Topics (page 131).
Starting and Stopping Connectors
To start an individual connector when a configuration is running, select the
connector in the Configuration tree, right-click and select Start Connector
Service from the menu. To stop an individual connector when a
configuration is running, select the connector in the Configuration tree,
right-click and select Stop Connector Service from the menu.
Monitoring Configurations
You can monitor transactions as they are executed while a configuration
runs. Click Transaction Monitor on the toolbar to view a summary of
cumulative activity organized by transaction.
58
●
●
3 ●Exploring the FactoryTalk Transaction Manager User Interface
●
●
●
Click any column header, except Total, to sort the list. The list refreshes every 30
seconds, or when you click the column headers.
The columns in the Transaction Monitor have the following meaning:

Total - The total number of transactions that have been triggered.

Passed - The number of transactions that have completed without
errors.

Failed - The number of transactions that have failed.

% Passed - Passed/Total * 100.

Cached - The number of transactions currently in Transaction Cache
files.

Database Passed - The number of transactions that have been
successfully executed by the database.

Database Failed - The number of transactions that have experienced a
database error.

Pending - The number of transactions that have been started, but are not
completed or currently running.
59
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
Understanding FactoryTalk Transaction Manager
External Files
FactoryTalk Transaction Manager generates several types of external files
while creating and running a configuration; you can set the location of these
files from the FactoryTalk Transaction Manager user interface. The easiest
way to determine where the configuration files are stored is to view the
Configuration Properties dialog box. Select Configuration > Properties or
select a configuration name in the Configuration tree, right-click and select
Configuration Properties from the menu.
60

Configuration files (*.dat) - FactoryTalk Transaction Manager stores
all information associated with a single configuration in a set of *.dat
files. The configuration files have fixed file names, so each
configuration generates a set of identically named files. For this reason,
configuration files must be stored in a unique directory.

Cached Transaction files (*.rsl) - FactoryTalk Transaction Manager
transactions can update their target database directly from cached
transaction files. These files contain completed transactions that are
applied to the database as a group. The use of cached transaction files is
set individually for each transaction, but the files are associated with an
enterprise connector. To edit cached transaction file properties, open
the Configuration Properties dialog box, select the Cache tab and
double-click a connector to open the Enterprise Connector Options
dialog box.

Log files (*.log) - Each of the FactoryTalk Transaction Manager
services generates log files when the configuration is running. The level
of error messages contained in these files is set at the configuration
level. You can specify error log file parameters from the FactoryTalk
Transaction Manager user interface by selecting Define > Error
Logging. All log files can be viewed by selecting View > Error Log
Files.
●
●
3 ●Exploring the FactoryTalk Transaction Manager User Interface
●
●
●

SQL files (*.sql) - FactoryTalk Transaction Manager generates these
SQL files as a result of a failed connection or database error. To include
this data in the database, use a database maintenance utility.

RSQ files (*.rsq) - FactoryTalk Transaction Manager uses these
compressed files to backup configurations. An .rsq file is a result of a
backup. You can restore an .rsq file by using the restore command.

RPB files (*.rpb) - These files are generated when you use the
Time-series Data Compression enterprise connector. FactoryTalk
Historian Classic uses these files to save uncompressed, partial block
information.

RFB files (*.rfb) - These files are generated when you use the
Time-series Data Compression enterprise connector. FactoryTalk
Historian Classic uses these files to save compressed, full block
information prior to storage in the database.
Using the Service Console
The Service Console is a Microsoft Management Console (MMC) snap-in
that provides administrative functions for the Information Services Manager
and other RSBizWare servers. The Service Console is capable of accessing
and controlling RSBizWare servers that are running on machines across the
network or on the local machine. It supports system user administration,
server administration, and any custom functionality specific to the
RSBizWare component that is being managed.
FactoryTalk Transaction Manager can be managed via the Service Console
when used as a part of a FactoryTalk Historian Classic or FactoryTalk
Metrics applications. For more information, refer to the Administration
Guide.
The Service Console is not installed with FactoryTalk Transaction Manager, but it is
installed with the RSBizWare products.
61
Chapter 4
Understanding FactoryTalk Transaction
Manager Services
Introducing FactoryTalk Transaction Manager Services
FactoryTalk Transaction Manager is designed to run as several services.
During design time, the FactoryTalk Transaction Manager user interface
sends information to the Configuration Server which writes to the
configuration files. At run time, the other FactoryTalk Security services run
in the background of the computer(s) involved in the configuration, similar
to other Microsoft Windows 2003/XP/Vista/2008 R2 services. For more
information about configuring services, refer to Chapter 3,Exploring the
FactoryTalk Transaction Manager User Interface (page 41).
This chapter describes the types of control and enterprise connectors you
must define during design time.
Control Connectors
The control connector services manage the interaction between the
industrial control system and the FactoryTalk Transaction Manager service
in the FactoryTalk Transaction Manager. These control connector services
(FactoryTalk Live Data, DDE, RSLinx Classic OPC, RSView32, or Generic
OPC) communicate with the data server using the appropriate protocol.
Rockwell Software recommends using the FactoryTalk Live Data control
connector for most user applications. If your application requires the use of
any other control connector, please review and consider the following
sections before selecting an alternate control connector.
63
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
FactoryTalk Live Data
The FactoryTalk Live Data control connector service is used to interface
with data items provided by the FactoryTalk Live Data servers. The
FactoryTalk Directory provides a common name space for factory
automation products from Rockwell Software, allowing all applications to
use the same naming convention and giving you the capability to browse
available data points. FactoryTalk Live Data provides services that allow the
efficient transfer of high-speed manufacturing data between processes in the
system.
In a configuration that uses online edits, the Transaction Control Manager
service performs the duties of the FactoryTalk Transaction Manager service
and inherits the functionality of the FactoryTalk Live Data control
connector. For more information about performing online edits, see Chapter
8, Understanding Online Edits (page 111).
DDE
The DDE control connector service can be used for legacy connections to
DDE servers or to provide functionality that is not supported by the OPC or
FactoryTalk Live Data specification.
The DDE server must be running on the same computer as the associated control
connector. FactoryTalk Transaction Manager does not support NetDDE.
The FactoryTalk Transaction Manager user interface cannot query remote
DDE servers to retrieve configured DDE topic information. When the DDE
control connector is located on a remote FactoryTalk Transaction Manager
computer, manually enter DDE topic names on the FactoryTalk Transaction
Manager DDE Data Point Configuration dialog box. Perform the following
steps.
1.
64
Define a configuration on the local computer that contains the
FactoryTalk Transaction Manager service.
●
●
4 ●Understanding FactoryTalk Transaction Manager Services
●
●
●
2.
Run the FactoryTalk Transaction Manager user interface on the remote
computer and select a configuration that is using existing configuration
files on the local computer.
3.
Use the FactoryTalk Transaction Manager user interface on the remote
computer to configure the DDE topics and items.
When you have finished, exit the FactoryTalk Transaction Manager user
interface on the remote computer and continue creating configurations on
the local computer.
RSLinx Classic OPC
The RSLinx Classic OPC control connector service can be used for data
items that reside in Allen-Bradley Programmable Logic Controllers (PLC),
with the exception of the Logix family of controllers. The RSLinx Classic
OPC control connector must be on the same computer on which RSLinx
Classic is running.
OPC recognizes when a controller sends a message to a client with the same value,
but does not forward that message to the client. If you are using MSG instructions to
trigger transactions, then you must ensure that the value is different in each MSG
instruction. Additionally, you can use the DDE control connector to forward all values
to your application.
RSView32
The RSView32 control connector service can be used to interface with tags
provided by RSView32 applications. The FactoryTalk Transaction Manager
RSView32 control connector must be on the same computer on which the
RSView32 project is running. The FactoryTalk Transaction Manager user
interface can browse for RSView32 project tags on remote computers, but
when the transactions are running, the RSView32 control connector must be
on the same computer as the RSView project.
The RSView32 control connector can be used to collect data from either
memory tags or device tags. Device tags are updated every 300
milliseconds.
65
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
If you need updated tags at a faster rate, use the FactoryTalk Live Data, RSLinx
Classic OPC, or Generic OPC control connectors to retrieve data from the devices
directly.
To interface with tags provided by FactoryTalk View SE, use the FactoryTalk Live
Data control connector.
Generic OPC
The Generic OPC control connector service can be used to interface with
items provided by any OPC server that conforms to the OPC custom
interface specifications. The Generic OPC connector is an OPC client that
supports OnDataChange subscription callback using either:

IAdviseSink– for OPC 1.0A-compliant servers.

IConnectionPoints– for OPC 2.0-compliant servers.
The Generic OPC connector service tries to establish the IAdviseSink
method, and then tries the IConnectionPoints method. Data writes to OPC
items are performed using Asynchronous Writes. FactoryTalk Transaction
Manager also supports Asynchronous Reads from Device as an option for
OPC servers that support this method.
Enterprise Database Connectors
The enterprise database connector services (Microsoft OLE DB, ODBC, or
Oracle OCI) manage FactoryTalk Transaction Manager's interaction
between a database and the Transaction Control Manager service or
FactoryTalk Transaction Manager service. Each enterprise database
connector service can manage connections with multiple databases on
multiple computers.
For transactions that update existing records, the data values that are used to
look up a record in the database may update zero or more records in the
database. If one or more records is selected, the transaction updates all of the
selected records. If no records area selected, the transaction converts from
Update to Insert mode, and the transaction is inserted into the database. This
is not an error condition.
66
●
4 ●Understanding FactoryTalk Transaction Manager Services
●
●
●
●
ODBC
The ODBC enterprise database connector allows you to interface with
virtually any ODBC-compliant database including Microsoft Access,
Microsoft SQL Server 2000 or later, IBM DB2, and Sybase.
The ODBC enterprise connector requires a system data source name (DSN)
to connect to an ODBC data source. When you create an ODBC database
connection, you must enter a valid system DSN for the ODBC server. A
system DSN is available to all users and Microsoft Windows
2003/XP/Vista/2008 R2 services.
Oracle OCI
The Oracle Call Interface (OCI) enterprise database connector allows you to
connect to database objects from an Oracle server. If you are using Oracle
OCI in FactoryTalk Transaction Manager, you need to install SQL*NET
2.3x or later, Net8, or Oracle Net services (all from Oracle) locally. You can
then connect to an Oracle database versions 9i through 11g.
Microsoft OLE DB
The Microsoft OLE DB enterprise database connector should be used only
for interfacing with Microsoft SQL Server 2008 R2, Microsoft SQL Server
2005 Standard (Service Pack 3) or Microsoft SQL Server 2000 (Service
Pack 4). The Microsoft OLE DB connector allows you to browse a
Microsoft SQL Server 2008 R2, 2005 or 2000 database without a DSN.
Enterprise Application Connectors
The enterprise application connector services (Microsoft COM+,
Time-series Data Compression, or FactoryTalk Metrics) manage
FactoryTalk Transaction Manager's interaction with the enterprise
application connectors (Microsoft COM+, Time-series Data Compression,
or FactoryTalk Metrics), and the Transaction Control Manager service or
FactoryTalk Transaction Manager service.
67
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
Microsoft COM+
The Microsoft COM+ enterprise application connector allows you to
interface with Microsoft COM+ application components; these components
must be integrated into a Microsoft Windows 2003/XP/Vista/2008 R2
COM+ environment.
Time-series Data Compression
FactoryTalk Metrics
The FactoryTalk Metrics enterprise application connector is only used with
FactoryTalk Metrics and stores data into the Service Console. The
FactoryTalk Metrics enterprise application connector can only be
configured through the Service Console. For more information, see the
Administration Guide.
Enterprise Connector Options
FactoryTalk Transaction Manager allows you to set additional options for
enterprise connectors on the Enterprise Connector Options dialog. From the
Configuration Checklist, click Step 2. On the Connector Definition dialog
box, click Options to display the Enterprise Connector Options dialog box.
Another way to access this dialog box is to select a configuration from the
Configuration tree, right-click and select Configuration Properties from the
menu. On the Configuration Properties dialog box, select the Connectors
tab. Double-click the appropriate enterprise connector; on the Connector
Definition dialog box, click Options to display the Enterprise Connector
Options dialog box.
You can set the following options:

68
Number of real-time threads: Specifies the number of real-time
threads used by this connector. Increasing this value permits multiple
real-time transactions to execute simultaneously in the enterprise
connection with each thread having its own database connection. Do
not increase this value unless the real-time transactions are not
●
4 ●Understanding FactoryTalk Transaction Manager Services
●
●
●
●
executing to the database fast enough. To make a transaction use
real-time threads, select Use Real Time Thread on the Transaction
Definition dialog box.

SQL buffer size: Specifies the size of the SQL buffer in kilobytes. The
SQL buffer specifies the number of bytes necessary to build the
command that will be executed. The default value only needs to be
modified if database errors occur and the SQL file shows only a partial
command.

Maximum transactions per file: Indicates that a file is sent to the
enterprise connector for processing when Maximum Transactions Per
File or Maximum Time Between Files value is reached, whichever
comes first. Setting this value to a field greater than 1 allows the
enterprise connector to use array inserts on databases that support them.
Array inserts increase database performance by allowing multiple
inserts/updates in a single database command.

Maximum time between files: Indicates that a file is sent to the
enterprise connector for processing when the Maximum Time Between
Files or Maximum Transactions Per File is reached, whichever comes
first.
FactoryTalk Transaction Manager Service
The FactoryTalk Transaction Manager service performs the following tasks:

Controls the execution of all FactoryTalk Transaction Manager
transactions.

Collects and sends data to and from all of the connector services.

Controls the scheduling and execution of the transactions.

Controls data manipulation, if required.
69
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
Transaction Control Manager Service
The Transaction Control Manager is a service that controls and executes
FactoryTalk Transaction Manager transactions contained in a configuration,
but with the additional functionality of the FactoryTalk Live Data control
connector embedded in it. In an edit enabled configuration, the Transaction
Control Manager replaces the separate FactoryTalk Transaction Manager
and control connector services.
Configuration Server
The Configuration Server is a Microsoft Windows 2003/XP/Vista/2008 R2
service that runs continuously to provide a single interface to the
configuration (.dat) files that make up the FactoryTalk Transaction Manager
configuration. The Configuration Server simplifies access to configuration
files by filtering all changes to the files and interfacing with other
FactoryTalk Transaction Manager services. A collection of all changes that
affect a configuration are recorded in an audit trail (via either FactoryTalk
Diagnostics or the Configuration Server *.log file).
Since the service is always running, functions such as configuration
diagnostics and remote file browsing are easier. One benefit of the
Configuration Server is consolidated file access. The Configuration Server
is the focal point for all interaction with, and manipulation of, the
configuration files.
70
●
4 ●Understanding FactoryTalk Transaction Manager Services
●
●
●
●
71
Chapter 5
Defining Data Points
Introducing Data Points
Data points are specific data locations or registers in the control system that
are made available to FactoryTalk Transaction Manager transactions. The
software can read from, and write to, data points through the embedded
FactoryTalk Live Data control connector (Transaction Control Manager
service) or a control connector (FactoryTalk Transaction Manager service).
The control connector then communicates with a data server (based on OPC,
DDE, or FactoryTalk) that communicates with the control system devices.
Once defined, a data point can be used by multiple transactions.
Using FactoryTalk Transaction Manager, you can assign the following
attributes to a data point:

Item string or address.

Data point name.

Data type.

Number of elements.

Mode and Scan rate.

Retrieval timeout.

Substitution options.
These attributes are assigned by defining data points on the Data Point
Definition dialog boxes (click Step 3 on the Configuration Checklist). These
dialog boxes allow you to browse for data locations serviced by a data
73
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
server, add data points to your configuration, edit existing data points, and
delete unwanted data points. The following figure shows an example
FactoryTalk Data Point dialog box.
Figure 10: FactoryTalk Data Point dialog box
Notice the following fields on the status bar at the bottom of the FactoryTalk
Data Point dialog box:
74

Configuration status- The status of the current configuration.

Rows- The number of rows selected before you saved, assembled, or
canceled pending edits.
●
●
5 ●Defining Data Points
●
●
●

Points- The number of data points that specific row represents. For
example, two rows may be two different data points or they may be the
current definition and the pending definition of the same data point.

Passed- The number of successful operations.

Disregarded- The number of rows that FactoryTalk Transaction
Manager does not allow the action to be performed. For example,
selecting a row that does not have a pending edit and clicking Cancel
Edits.

Failed- Operations that did not take place because of an internal error.
For more information on online edits, see Chapter 8, Understanding Online
Edits (page 111).
FactoryTalk Live Data Data Points
FactoryTalk Transaction Manager uses FactoryTalk Live Data to
communicate with the FactoryTalk Live Data servers. With access to the
FactoryTalk Directory, the FactoryTalk Transaction Manager service can
browse available data items directly. This is the only method that can be
used to transfer data to and from FactoryTalk View SE or RSLinx
Enterprise, and is the recommended method to transfer data to and from
RSLinx Classic or RSView32.
In a configuration that uses online edits, you can use only FactoryTalk data
points. For further details about using FactoryTalk data points in a
configuration that uses online edits, see Chapter 8, Understanding Online
Edits (page 111).
Rockwell Software recommends using the FactoryTalk Live Data control
connector for most user applications. The majority of this chapter will focus
on information related to FactoryTalk Live Data data points. For
information on all of the other data point types, see OPC Data Points (page
82) in this chapter.
75
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
Selecting a Collection Mode
For FactoryTalk data points, you can select the collection mode type. This
section provides more detail about the following types of data point
collection for FactoryTalk control connectors:

Scheduled

Device Scheduled

Unscheduled
SCHEDULED: MAINTAIN THE CURRENT SUBSCRIBED VALUE
During scheduled collection mode, each data point is continuously on scan
at a configurable rate. The data server sends any change in value or quality
to the control connector. The control connector retains the current value in a
buffer and provides it to the FactoryTalk Transaction Manager service when
it is requested. The Transaction Control Manager service also buffers this
data internally and uses it as needed.
The data server reads the value of the data point at the Subscription Scan
Rate that is set on the FactoryTalk Data Point dialog box; if a new value is
found, it is sent to the data client. If the value has not changed in the data
server, no data is transferred. Thus network bandwidth is not used to
transmit the same value between the data server and the control connector.
Typically, this type of collection mode is used to support a transaction that
logs data constantly and rapidly (for example, logging a data point every
second while an assembly line is running).
DEVICE SCHEDULED: REQUEST THE CURRENT VALUE FROM THE
DEVICE
During device scheduled collection mode, each data point is not on scan and
data is not buffered in the control connector or data server. The data server
reads directly from the device. Each value is read from the controller only
when the Transaction Control Manager service or FactoryTalk Transaction
Manager service requests it from the control connector. The value is then
retrieved from the controller and passed to the control connector.
76
●
5 ●Defining Data Points
●
●
●
●
Typically, this mode of collection is used to support a transaction that logs
data infrequently.
UNSCHEDULED: SEND SUBSCRIBED VALUE WHENEVER IT CHANGES
This collection mode is driven by the data server and each data point is
continuously on scan at the prescribed rate. When the server detects a
change to a data point value or quality, it sends the value to the control
connector, which passes it to the Transaction Control Manager service or the
FactoryTalk Transaction Manager service. This collection mode is
event-based, not time-based.
Keep in mind that any unsolicited message sent by the controller that does not
include a change in value or quality will never be sent to FactoryTalk Transaction
Manager.
The Subscription Scan Rate sets the limit on how fast new data can arrive.
For example, if the Subscription Scan Rate is 150 milliseconds, the data
server cannot send changes faster. If the underlying data value is changing
faster, the control connector only sees the current value every 150
milliseconds.
Typically, this mode of collection is used for a transaction trigger that
executes at a high or low transition, or exceeds a valid range.
Consecutive Data Point and Data Block Support
You can quickly add multiple consecutive data points in your application.
For example, if you want to add multiple consecutive data points N7:0
through N7:6, select them from the Contents of window on the FactoryTalk
Transaction Manager FactoryTalk Data Point dialog box, and then click Add
Selected Tags to add them to the FactoryTalk data point grid.
You can create a single data point with blocked data, such as a data point that
has multiple consecutive elements. For example, if you want to create a data
point with 10 elements, type N7:0,L10. This feature applies to pure data
table files and not to structures (for example, T3:0.ACC,L8 is not
supported). The maximum size of a data block passed to the connector from
77
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
a data point is 512 bytes for transactions without online edits, and 4096 bytes
for transactions with online edits. If you defined a contiguous set of ASCII
registers from a PLC processor, this data point contains a complete string
(when used in a transaction). On the other hand, if you defined multiple
consecutive elements with numeric data types in the contiguous registers of
the PLC processor, you have an array. You can use the Parse() expression to
extract each element from the block data.
This feature also applies to the RSLinx Classic OPC, Generic OPC, and DDE control
connectors.
Selecting Timeout Properties
Keep the following sections in mind when selecting timeout properties.
DATA VALID
Regardless of the trigger mechanism, once a transaction is started, the
Transaction Control Manager service or FactoryTalk Transaction Manager
service checks each required data point to determine if the value in its local
cache is still valid.
A data point value is not valid when either the data valid time has passed or
the data valid time is set to zero. The following calculation demonstrates the
requirements for validity.
Data is valid = Time Received + Data Valid value < Current
Time
Once the data point value is no longer valid, the Transaction Control
Manager service or FactoryTalk Transaction Manager service requests the
data point from a data server and starts a timer for the retrieval of that data
point. If the data point is not returned by the time specified in the data
retrieval parameter, the rules of substitution are applied.
When a data point is unscheduled, it is never requested and the transaction
fails if the data valid time has expired. Unscheduled data points do not have
substitution values. If a data point will be used as a transaction trigger and in
other transactions, set the data valid parameter to a value that is large enough
78
●
●
5 ●Defining Data Points
●
●
●
so that the value will remain fresh. Or create another data point using the
same address and make it a scheduled data point so that the Transaction
Control Manager service or FactoryTalk Transaction Manager service can
then request it as needed.
The unscheduled trigger is considered to be fresh when it starts a transaction.
If the Transaction Control Manager service or FactoryTalk Transaction
Manager service starts a transaction and determines it has already requested
a data point but not yet received a reply, it will not request the data point
again. Rather, it uses the same value for both transactions when the value is
received.
DATA RETRIEVAL TIMEOUT
The data retrieval timeout is measured from the start of the transaction until
the data point arrives. If there is any latency in the communications between
any of the following, the data point timeout may be affected:

Transaction Control Manager service and the data server.

FactoryTalk Transaction Manager service and the control connector,
and the control connector and the data server.
An example of this type of latency is using a device-scheduled data point in
FactoryTalk. In this case, the Transaction Control Manager service or
FactoryTalk Transaction Manager service requests the data point from the
control connector. The control connector then sends notification to the
FactoryTalk Live Data server. The FactoryTalk Live Data server sends a
read request to the controller, which in turn returns the data value. The
FactoryTalk Live Data server sends the value to the control connector,
which sends it to the Transaction Control Manager service or FactoryTalk
Transaction Manager service. If the data point is not returned by the time
specified in the data retrieval parameter, the rules of substitution are applied.
79
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
Selecting a Substitution Option
All data points must have valid values for a transaction to complete
successfully. If a data point is not retrieved and ―times out,‖ the Transaction
Control Manager service or FactoryTalk Transaction Manager service uses a
substitution value. Unscheduled data points do not have substitution
policies. If unscheduled data points are invalid, the transaction will fail.
From the Data Point Definition dialog box, select one of the listed data
points, right-click the mouse, and select Edit Selected Collection
Parameters. Choose one of the following substitution options for scheduled
data points:

No Substitution- Specifies that the transaction fails if valid data is not
available for this data point. This occurs when the Transaction Control
Manager service or FactoryTalk Transaction Manager service times out
waiting for data or when you have bad quality data.

Substitute Previous Value- Instructs the FactoryTalk Transaction
Manager service to use the last good value for this data point.

Substitute Value- Allows you to specify the substitution value to use.
A substitution value of Null (default) causes the enterprise database
connector to leave the value for that column empty. A data point that has a
Null substitution policy causes a transaction to fail if the data point is used in
an expression. A Null value is not a null string or a zero; it is a value that
does not exist and, therefore, the expression evaluator cannot use it to
calculate a result.
Preventing Stale and Mismatched Data
Stale data is data that no longer matches the value in the control system.
Mismatched data refers to a set of data in which individual data values from
different times were collected and are not synchronized. Several strategies
exist to eliminate stale and mismatched data depending on the type of
transaction. For scheduled transactions, data may be read while values are
changing. For most applications, this should not be a concern (except in the
80
●
5 ●Defining Data Points
●
●
●
●
case of high-speed data changes). If the data is changing at a high rate, then
switch the transactions to unscheduled.
Unscheduled transactions offer better protection against stale and
mismatched data via the use of ladder logic. The controller dictates when the
data is read and it can lock values into its registers prior to triggering the
transaction. This helps prevent stale data from being read as long as the data
valid time is set to zero for a non-trigger data point.
The best way to prevent stale or mismatched data is to use unscheduled data
point blocks. All data is handled as a single unit, managed by the controller,
and parsed into separate units using the Parse function from the Transaction
Definition dialog box (double-click a transaction in the right pane of the
FactoryTalk Transaction Manager workspace). This method may also
reduce traffic on the controller network because the data is not scanned at a
constant rate.
Specifying Quality
For the FactoryTalk Live Data connectors, choose one of the bad quality
options if you want the Transaction Control Manager service or FactoryTalk
Transaction Manager service to use bad quality values. Otherwise, select
Use Substitution Option for Bad Quality on the Edit Collection Parameters
dialog box. If you do not select a bad quality value, the Transaction Control
Manager service or FactoryTalk Transaction Manager service uses one of
the substitution policies listed earlier in this chapter when it receives a bad
quality value for this data point.
If you choose to allow bad quality values, then use the QualityOf()
expression from the Expression Editor dialog box to bind the quality value
to a column in your database. In addition, the bad quality status is saved to
the Transaction Control Manager service log file or the control connector’s
log file (when using the FactoryTalk Transaction Manager service) at an
error level. The QualityOf() expression provides the following quality
values:
81
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
Server Returns:
QualityOf() Returns:
Bad (0)
1
Uncertain (1)
2
N/A (2)
3
Good (3)
0
This function only applies to FactoryTalk Live Data and OPC data servers. If you are
using a DDE data server, a Good value is always returned.
OPC Data Points
OPC data points are used by the RSLinx Classic OPC, Generic OPC, and
RSView32 connectors, but can also be used by FactoryTalk Live Data
connectors.
―The OPC Specification is a non-proprietary technical specification that
defines a set of standard interfaces based upon Microsoft’s OLE/COM
technology. The application of the OPC standard interface makes possible
interoperability between automation/control applications, field
systems/devices and business/office applications.‖ For further information,
visit the OPC Foundation’s web site at www.opcfoundation.org.
RSLinx Classic OPC Data Points
RSLinx Classic must run as a service (not as an application) on the computer
that is running the RSLinx Classic OPC control connector. When
FactoryTalk Transaction Manager uses OPC to communicate with RSLinx
Classic, RSLinx Classic 2.52.00 is recommended.
On the RSLinx Classic OPC Data Point dialog box, data points are sorted by
the associated connector, server, and host server. If you select a different
OPC server, only the data points with that server display; this also applies
when you select a new server or connector. You should not create a new
RSLinx Classic OPC control connector to collect data from data points in
82
●
●
5 ●Defining Data Points
●
●
●
different OPC servers. Instead, select the new server and add the data points
you want to include.
Generic OPC Data Points
The Generic OPC control connector service is an OPC client and
communicates with an OPC server according to the OPC standards. The
OPC Data Points dialog box allows you to browse a list of the servers
supported by the Generic OPC control connector. If the OPC server supports
tag browsing, then you can browse for the desired OPC items to create data
points. The Generic OPC control connector has full DCOM support, which
allows an OPC server to reside on a remote PC if the DCOM security is set
correctly.
RSView32 Data Points
RSView32 6.10.16 or higher supports transmitting data via OPC. In
RSView32 6.10.16 through 6.3x.xx, an OPC browse was not enabled.
Therefore, if you are using those versions of RSView32, you must use the
FactoryTalk Transaction Manager RSView32 connector to provide the
browsing capability. If you are using RSView32 6.40.00 or later, you can
use the FactoryTalk Live Data connector (recommended), RSView32
connector, or the Generic OPC connector.
To connect to data points from a RSView32 connector when the project is
not on the FactoryTalk Transaction Manager user interface computer,
RSView32 needs to be installed locally to provide the correct registry keys
to allow remote browsing. (The same is true if using RSView32 6.40.00 or
later and using the OPC connector). In the RSView32 project, use the
RTDataServerOn command to turn on the data server and allow FactoryTalk
Transaction Manager to read RSView32 tags. To provide write access to
RSView32 tags, you must issue the RTDataWriteEnable command.
83
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
FactoryTalk View SE users must use the FactoryTalk Live Data connector in
FactoryTalk Transaction Manager.
When using RSView32 data points and the FactoryTalk Live Data connector, use the
FTDataServerOn and FTDataWriteEnable commands in the RSView32 project.
DDE Data Points
To create a DDE data point, enter an Item String or import a tag or symbolic
name from a tag file. RSLogix 5/500, AI5 project files, or CSV and TSV
files are supported.
On the DDE Data Point dialog box, data points are sorted by the associated
connector, server, and topic. If you select a different topic, only the data
points with that topic are displayed. Likewise, for selecting a new server or
connector. If you select a new tag file after data points have been created for
a connector/server/topic combination, the tag file is cascaded to all data
points for that connector/server/topic. You do not have to create a new DDE
control connector to collect data from data points in different topics. Instead,
select the new topic and add the data points you want to include.
84
●
5 ●Defining Data Points
●
●
●
●
85
Chapter 6
Defining Data Objects
Introducing Data Objects
A FactoryTalk Transaction Manager data object references a specific object
in an enterprise system. For enterprise database connectors, this object can
be a database table, view, or stored procedure. For enterprise application
connectors, objects can be a FactoryTalk Metrics function or a Microsoft
COM+ method. These objects can be used in transactions. A data object may
contain many columns or parameters that are used as a unit. Enterprise
database objects can also include an action (for example, inserting or
updating a record).
Using FactoryTalk Transaction Manager, you can assign the following
attributes to a data object:

Data object name.

Enterprise system connection.

Mode (Insert or Update), if required for tables or views only.

Database tables, views, or stored procedures.

Database columns or parameters.
87
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
The following figure shows an example Data Object Definition dialog box
(click Step 4 on the Configuration Checklist).
Figure 11: Data Object Definition dialog box
The target database tables, views, and stored procedures must already exist
in the database to be used in data objects. You can also create new stored
procedures using the Stored Procedure Wizard (for Microsoft SQL Server
7.0 or later and Oracle only).
If you modify target database tables, views, or stored procedures in the database
after you create a data object within FactoryTalk Transaction Manager, you must
click Apply on the Data Object Definition dialog box so that data object recognizes
the database modifications.
Enterprise database connectors (ODBC, Oracle OCI, or Microsoft OLE DB)
can communicate with databases located on other computers. Multiple data
88
●
6 ●Defining Data Objects
●
●
●
●
objects can reference the same database using a connection to the database
system.
Enterprise Database Objects
The following sections describe how to connect to database objects for the
enterprise database connectors.
Oracle Call Interface (OCI) Data Objects
The Oracle Call Interface (OCI) allows you to connect to database objects
from an Oracle server. The OCI Data Object Definition dialog box allows
you to create, modify, or delete FactoryTalk Transaction Manager data
objects. When you create a data object, you must enter a valid connection for
the Oracle OCI server.
FactoryTalk Transaction Manager can communicate with a local or remote
Oracle database via the Oracle network of client tools such as SQL*NET,
Net8, or Oracle Net Services.
You can install SQL*NET/Net8 on the same computer that contains the enterprise
connector and communicate with remote Oracle databases running on any operating
system supported by Oracle.
Microsoft SQL Server Data Objects
The Microsoft OLE DB connector service allows you to connect to database
objects from Microsoft SQL Server 2000, Microsoft SQL Server 2005, and
Microsoft SQL Server 2008 R2. You can browse a Microsoft SQL Server
2000, SQL Server 2005, or SQL Server 2008 R2 database without entering a
DSN.
ODBC Data Objects
The ODBC connector service allows you to connect to database objects
using any ODBC 2.0 or later-compliant server. You must use a valid system
89
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
DSN, which is available to all Microsoft Windows 2003/XP/Vista/2008 R2
services.
If the FactoryTalk Transaction Manager user interface resides on a computer
that is remote from the computer(s) containing the enterprise connector, the
system DSN list comes from the computer where the enterprise connector
resides.
Rockwell Software does not recommend using ODBC data objects if you have an
Oracle database. Instead, use Oracle OCI data objects.
Enterprise Application Objects
The following sections describe how to connect to database objects for the
enterprise application connectors.
Microsoft COM+ Data Objects
FactoryTalk Transaction Manager communicates to COM+ components
through the COM+ enterprise connector service. You can code COM+
components using standard program development tools such as Microsoft
Visual Basic or Microsoft Visual C++ (6.00). These COM+ components
provide reusable functionality for large enterprise systems. COM+
components reside on local or remote servers running Microsoft Windows
2003/XP/Vista/2008 R2.
Data is passed between the client applications and the remote server
components in arguments that can accept many different types of data.
FactoryTalk Transaction Manager restricts the arguments that it can utilize
to scalar variables (variables that contain a single value). The data types that
can be used are String, Integer, Long Integer, Single Float, Double Float,
Byte, Date, and Boolean (True/False) data.
You can create a data object by selecting a COM+ method from the COM+
Connection Definition dialog box.
90
●
6 ●Defining Data Objects
●
●
●
●
FactoryTalk Metrics Data Objects
You can only connect to FactoryTalk Metrics data objects from the
FactoryTalk Metrics Server. This connector is different from the other
connectors because it preprocesses the data before sending it to the database.
For more information, see the FactoryTalk Metrics User Guide.
Enterprise Connector Error Handling
This section describes the most likely FactoryTalk Transaction Manager
error conditions that can affect the enterprise connector.

Lost connection with enterprise connector- The Transaction Control
Manager service or FactoryTalk Transaction Manager service cannot
communicate with the enterprise connector. This may occur because the
enterprise connector service has stopped running, or the enterprise
connector is located on another computer and communication has been
interrupted. The Transaction Control Manager service or FactoryTalk
Transaction Manager service will create cache transaction files for
transactions that use historical logging (when the Use Cached
Transaction Files checkbox is selected on the Transaction Definition
dialog box). Therefore, you should store configuration cache files on
the same computer as the Transaction Control Manager service or
FactoryTalk Transaction Manager service.

Lost connection with enterprise database- The enterprise connector
cannot communicate with the database. This may occur because the
database service has stopped running, or the database is located on
another computer and communication between the computers has been
interrupted. The enterprise database connector stores the data to be
reapplied when the database connection returns.
91
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
If you select the Use Cached Transaction Files checkbox on the Transaction
Definition dialog box, a *.sql file is generated that you must manually apply to the
database and the software generates *.rsl files until the connection is returned.
FactoryTalk Transaction Manager does not process any further *.rsl files until the
connection is returned.

Lost connection with Microsoft COM+- The enterprise application
connector cannot communicate with Microsoft COM+. This may occur
because the FactoryTalk Transaction Manager COM+ service has
stopped running, or the Microsoft COM+ component stopped working.
Microsoft COM+ may respond by creating a *.txt file, which displays
the insert method.
The Transaction Monitor (select View > Transaction Monitor when a
configuration is running) displays diagnostic information about the
currently running configuration.
Figure 12: Transaction Monitor
Two columns in the Transaction Monitor dialog box display failed
transactions:

The Failed column contains transactions that were not successfully
processed.

The Database Failed column contains transactions that were processed
correctly, but could not be applied to the database due to a database
error.
For more information on error conditions that can affect enterprise
connectors, as well as how FactoryTalk Transaction Manager handles
transaction types and storage methods, see chapter Creating Transactions
(page 95).
92
●
6 ●Defining Data Objects
●
●
●
●
Inserting and Updating Data Table Records
When logging data to a table, you can use FactoryTalk Transaction Manager
to directly insert data, which creates new records in the table, or update
existing data in the table. The default setting is Insert, but you can change it
by selecting the option for the given data object. When the Update option is
selected, some of the data points may be used as criteria for selecting rows to
be updated, while other data points are used to update the values in the
selected columns. If no rows match the given criteria, the data will be
inserted into a new row.
Stored Procedures
A stored procedure is a user-defined function or program that is executed
inside of the database; it can consist of any of the components of a structured
language that enable you to define data behavior. A stored procedure can be
simple like a single select command or complicated like validating all data
before it is inserted into a table.
A stored procedure works like a function that is stored in a database. Most
databases provide a comprehensive stored procedure language that
combines the data query capabilities of SQL and some kind of procedural
control (for example, an If…Then statement). As with most kinds of
function calls, a stored procedure can have both inputs and outputs. In a
transaction that is connected to a stored procedure, the values bound to
inputs are collected from the control system and the outputs are returned to
the control system.
When you create a data object and select the Stored Procedure radio button
on the Data Object Definition dialog box, FactoryTalk Transaction Manager
queries the database for all stored procedures accessible by the chosen
database user account and lists them in the stored procedure list box. When
you select a stored procedure, the input and output parameters display in the
lower pane. Since all parameters for a stored procedure are required, the
93
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
software automatically adds them to the data object pane on the right when
they are selected.
To simplify the creation of simple stored procedures, FactoryTalk
Transaction Manager provides a Stored Procedure Wizard for SQL Server
and Oracle databases (on the Data Object Definition dialog box, click the
Stored Procedure radio button and then click Wizard). For complicated
stored procedures and/or debugging of stored procedures, use
database-specific tools.
94
Chapter 7
Creating Transactions
Introducing Transactions
FactoryTalk Transaction Manager transactions move data between the
control system and the enterprise system. Binding is the process of mapping:

A column in a database table to a data point in a control system,
expression, or a literal string.

A parameter in a stored procedure to a data point, expression, a literal
string, or a null value.
A configuration can contain any number of transactions, each running
independently based on a trigger event. Although the number of transactions
in a configuration is unlimited, you cannot exceed the tag count for which
you are licensed (see Activation Options (page 33)). In a configuration that
uses online edits, you can edit existing or create new transactions while the
configuration is running. For more information, see chapter Understanding
Online Edits (page 111).
You can assign the following attributes to a transaction on the Transaction
Definition dialog box (click Step 5 on the Configuration Checklist):

Transaction name.

Transaction time out.

Data object name.

Bindings of data object elements to data points/expressions.

Trigger event.
95
●
●
●
FactoryTalk Transaction Manager User Guide
●
●

Transaction (cached or real-time) and storage options.
The following figure shows an example Transaction Definition dialog box.
Figure 13: Transaction Definition dialog box
Transaction Types
FactoryTalk Transaction Manager supports the following types of
transactions regardless of the trigger mechanism:

Unidirectional transactions.

Bidirectional transactions.
Additionally, for either transaction type, you can optionally specify that a
transaction result is bound back to a control system.
96
●
7 ●Creating Transactions
●
●
●
●
Unidirectional Transactions
Unidirectional transactions in FactoryTalk Transaction Manager use
information from the control system to add records to a database table,
update the contents of existing records, or call stored procedures that do not
contain output parameters.
Unidirectional transactions are commonly used to log production data to a
database, including:

Performance monitoring.

Quality analysis sampling.

Real-time production information collecting.

Material consumption tracking.

Product tracking.

End of job/batch/shift reporting.
Unidirectional transactions are the simplest transaction type. They can be
used to perform database Insert or Update commands. They can also be used
to perform simple stored procedures, provided no output parameters or
return codes exist. In most applications, unidirectional transactions account
for the majority of transaction volume. Data may be collected frequently
from a large number of data points.
Bidirectional Transactions
Bidirectional transactions in FactoryTalk Transaction Manager take data
from the control system and call a stored procedure that exercises some
logic, and then provides the software with output values that can be written
back to the control system. You can also set up bidirectional transactions so
that data is not sent to a database, but only downloaded from a database to a
control system.
This transaction type is the most powerful because it allows transactions to
interact with a database stored procedure or Microsoft COM+ method. This
capability makes it possible for FactoryTalk Transaction Manager to
97
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
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:

98
Input parameters. In a stored procedure, these parameters must have a
binding (a data point, expression, or a null). Select a data object
●
7 ●Creating Transactions
●
●
●
●
parameter, right-click and select either Bind Data Point or Bind Null
Value from the menu. A transaction must have all input parameters
bound to it before it can be enabled. Binding a null value to an input
eliminates the need to gather a value from the database.

Output parameters. These parameters do not require a binding. The
results of the bound value display under the Bound Value column. If an
output parameter is not bound or is bound to a null, the value is ignored
and this column is empty. A procedure must succeed before output
parameters can be returned to the control system. Normally, you bind
outputs to a data point in the control system; upon the successful
completion of a transaction, a value is written from the stored procedure
to the data point.

Input/output parameters. These parameters are handled as a single
binding unless they are separated using the Separate Input/output
option. This option permits separate data points to be bound to the same
procedure parameter. This implies that the address from which the input
parameter is derived is different from the address to which the output
parameter is written. This also implies that if an input/output parameter
is used only for output, then the input portion can be bound to a null
value. Leaving an input/output parameter bound to a single data point
causes the value to be read prior to executing the procedure and the
output value to be written upon completion of the transaction.
The Microsoft SQL Server RETURN_CODE contains data that can be
bound as an output to a stored procedure. This value is only available if the
procedure executes successfully. A successful return code does not
guarantee a successful transaction as the transaction is not yet complete.
Bidirectional or Unidirectional Transactions With
Transaction Bindings
A bidirectional or unidirectional transaction with a transaction result binding
implements a data value that is written back to the control system; that data
value allows you to determine if the transaction completed successfully. The
control system can then take appropriate action based on the success or
99
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
failure of the transaction. For example, consider a high liability
manufacturing environment where a verifiable quality record is a
requirement for each product produced. At various steps in the
manufacturing process, a transaction may send a test result to be stored in a
central database. If that test result is not recorded successfully, the part on
the production line may become worthless.
The Transaction Result, which notifies the control system that the
transaction was successful, is sent variably based on the type of transaction.
In a real-time transaction (where data flows straight to the database), the
Transaction Result is sent upon data being successfully logged into the
database. However in a cached transaction, where a cache is used to ensure
data integrity, the Transaction Result is sent once data has been logged into
the cache, and not necessarily into the database. The Transaction Result is
used to confirm that the test result was recorded. If the Transaction Result
indicates the test result was not recorded, the control system can respond
appropriately by alerting an operator, changing the part's routing, or retrying
the transaction. Some examples may include:

Validated data logging.

Closed-loop quality tracking.
The Transaction Result Binding option allows a transaction to return a
Transaction Result code to the control system. To enable the Transaction
Result Binding option, select the Bind Transaction Result check box on the
Transaction Definition dialog box, then select a data point to accept the
Transaction Result code. The control system should take appropriate action
depending upon the result of the transaction.
The Transaction Result code is a 16-bit integer. Bit 0 is the least significant,
Bit 15 is the most significant. The Transaction Result code consists of:

100
Bit 0: the Done Bit- A 1 indicates the transaction has completed, a 0
indicates that it has not completed. No information is given as to
whether the transaction was successful or unsuccessful.
●
7 ●Creating Transactions
●
●
●
●

Bit 1- The Error Bit. A 1 indicates there was an error, a 0 indicates no
error.

Bits 2 through 15- The Error Code. If Bit 1 contains a 1, these bits
contain the error code. Otherwise, these bits are zeros. If you chose to
use the Transaction Result code, you can run the FactoryTalk
Transaction Manager error utility from the Startup menu. This
eliminates the need to decode the integer to determine the FactoryTalk
Transaction Manager error code.
To convert the error code to a proper error number:
1.
Select Start > Programs > Rockwell Software > FactoryTalk
Transaction Manager > Error Messages. The FactoryTalk
Transaction Manager Error Messages dialog box appears.
2.
Enter the Transaction Result code number (binary or decimal).
3.
Click the Bind Transaction Result Error radio button.
4.
Click Apply.
For example, a transaction result code of 0000000000000001 (binary) or 1
(decimal) indicates that the transaction has completed without errors.
If the Transaction Result code is: 0000010111101111 (1519 decimal) then
the FactoryTalk Transaction Manager error code is: 33147.
Transaction Timeout
The transaction timeout parameter specifies how long the Transaction
Control Manager service or FactoryTalk Transaction Manager service
should wait for a transaction to complete. The transaction timeout for an
unscheduled transaction does not affect other copies of the same
unscheduled transactions as multiple copies of the unscheduled transaction
can execute at the same time.
101
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
Setting the transaction scan rate for a scheduled transaction lower than the
transaction timeout may cause the second transaction to fail because only one
scheduled transaction can run at a time.
Transaction Completion
It is important to determine when the Transaction Control Manager service
or FactoryTalk Transaction Manager service considers a transaction to be
complete because the Transaction Control Manager service or FactoryTalk
Transaction Manager service only runs one occurrence of a scheduled
transaction at a time. The next occurrence cannot start until the current
transaction is complete. Also, if a transaction has a Transaction Result
Binding, the Transaction Result is written when the transaction completes.
Cached Transactions
If you select Use Cache Transaction Files from the Transaction Definition
dialog box, unidirectional transactions complete as soon as the data is
written to the cache file. The data is not yet stored to the database, but is on
the disk.
Real-time Transactions
If you select Real Time Storage from the Transaction Definition dialog box,
unidirectional transactions complete when the Transaction Control Manager
service or FactoryTalk Transaction Manager service receives a reply from
the enterprise connector that the data has been stored. This means that the
time necessary for the enterprise system to store the values is included in the
transaction completion time. This may cause the transaction to timeout if the
Transaction Control Manager service or FactoryTalk Transaction Manager
service has not received the reply from the enterprise connector in the
allotted time. The transaction timeout does not determine if the data was
logged to the database; the transaction can time out prior to sending the data
to the database or after the data was successfully stored.
The table below shows how FactoryTalk Transaction Manager handles each
transaction type and storage method.
102
●
●
7 ●Creating Transactions
●
●
●
Transaction Type:
Transaction
Storage Method:
Lost Connection with
Enterprise Connector:
Lost Connection with
Enterprise System:
Unidirectional
Cached transaction
files
Cache files are applied
when the connection is
restored.
One cache file can be converted
to an .sql file and returns
Database Failed. Remaining
cache files are processed when
connection is restored.(1)
Unidirectional
Real time thread
Transaction fails and
transaction data is lost.
Transaction returns Database
Failed, transaction data is
written to an .sql file.(2)
Bidirectional
Real time thread
Transaction fails and
transaction data is lost.
Transaction returns Database
Failed, transaction data is
written to an .sql file.(2)
Transaction Result
Binding
Cached transaction
files
Transaction data is written
to a cache file. The
transaction returns a
successful result to the
controller. The cache files
are processed when the
connection is restored.
Transaction returns a successful
result. One cache file can be
converted to an .sql file and
returns Database Failed.
Remaining cache files are
processed when the connection
is restored.(1)
Transaction Result
Binding
Real time thread
Transaction fails and
Transaction returns Database
transaction data is lost. The Failed, transaction data is
failure is sent to the
written to an .sql file.(2)
controller.
(1) If multiple database connections are defined in the configuration, then the cache files continue
processing. All data for the failed connection is written to an .sql file.
(2) Data is stored in separate .sql files depending on whether the Real Time option or the Transaction Cache
Files option was used on the Transaction Definition dialog box. This allows you to recover this data.
For more information on enterprise connector error handling, see chapter
Defining Data Objects (page 87).
103
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
Bidirectional Transactions
Bidirectional transactions with input/output parameters are not complete
until the control connector acknowledges that the control system has
received the transaction output data. The transaction timeout includes the
time it takes for the data server to connect to the control system, write the
data values, and return a response to the control connector. Transactions
with outputs may have latency in both the enterprise connector and the
control connector.
Transactions With Bound Transaction Results
Bidirectional transactions that use the Transaction Result Binding are not
complete until the Transaction Control Manager service or FactoryTalk
Transaction Manager service receives a reply from the control connector
that the bound result was written. If a transaction times out after the bind
transaction result is sent to the control connector, all data is moved
successfully to the controller and a message indicates that the transaction
failed.
Database Triggers
Database triggers are functions that are executed by the database whenever
the triggering operation occurs. For example, a trigger can be set so that
whenever a value is inserted into a table, the data is verified and then another
value is updated with the verified data. The amount of time necessary to
process the trigger and the associated function is charged against the
transaction timeout. In this case, the database insert does not return control
to the enterprise connector until the insert and it’s triggered function is
complete. In other words, a real-time transaction is considered complete
when the FactoryTalk Transaction Manager transaction, and any database
triggers that are caused by the transaction, are complete.
Expression Editor
An expression is a calculation or formula defined in the Expression Editor
using mathematical operators and functions that can be bound to a data
104
●
●
7 ●Creating Transactions
●
●
●
object. To display the Expression Editor, select a data object on the
Transaction Definition dialog box, right-click the mouse, and select Bind
Expression. The following is an example Expression Editor dialog box.
Figure 14: Expression Editor dialog box
Logical and Mathematical Operations
Mathematical operators define simple expressions that perform calculations
that are evaluated after all data has been collected (or substituted). There is
105
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
also a set of operators for both bit-wise and logical operations. Once an
expression has been defined, the syntax and semantics are checked to
determine if it can be evaluated at run time. Once the data points have been
collected, their current values are used to evaluate the expression. The
results are then passed to the database for processing.
Time Functions
The Expression Editor provides several functions for storing the current
time. Select time functions can be expressed in either Coordinated Universal
Time (UTC) or system local time.
The TimestampOf( ) function logs the time a data point is read. This may
differ from the time the transaction executed because the data point may
have a data valid time of greater than zero.
The TransTimestamp( )function returns the transaction execution time. This
may differ from the time the data was inserted into the database because
completed transactions may be buffered in cached transaction (*.rsl) files.
The MTimestampOf( ) and MTransTimestamp( )functions log the
millisecond portions of the two previous times. These can be stored in
separate columns, which permits accurate trend analysis for databases that
do not store time values to the millisecond.
The OPCTimeStampOf( ) and MOPCTimeStampOf( )functions return an
OPC timestamp value that indicates when the OPC data server (or
FactoryTalk data server) received (or read) the data from the controller. If
the data server is RSLinx Classic, this is when RSLinx Classic provided data
to FactoryTalk Transaction Manager. If the data server is RSLinx
Enterprise, this is the time when RSLinx Enterprise acquired the data from
the controller. This value is accurate to the nearest second.
Data Point Range and Advanced Functions
The Expression Editor supports a data point range syntax that compares a
data point value over a series of transactions. Each time the transaction runs,
a new value is added to the data range for a given transaction. The
expression is then evaluated using the range of values. This permits an
106
●
7 ●Creating Transactions
●
●
●
●
expression to calculate an average of the previous 10 transaction values
(avg(datapoint[0,9]). This functionality also works to calculate the
minimum (min) or maximum (max) value of a data point over several
transactions.
You must run the transaction to reflect changes in the historical values. The results,
however, do not need to be stored.
Using the Store on Every N Transactions option, you can collect the data
needed for an average, but not store the data to the database. If a transaction
executes every second but only stores its data every 60 times and there is an
avg(datapoint[0,59]), the value that is stored once a minute is the average of
the values taken every second.
If you make changes to transactions (or their bound data points) in a running
configuration using the Data Point Range function in conjunction with the
Avg function in an expression, the transaction resets or behaves as though it
is starting for the first time when you assemble the pending edits. For more
information about this behavior in a transaction, see Chapter 8,
Understanding Online Edits (page 111).
Parse Function
The Parse function in the Expression Editor provides a powerful feature to
guarantee that all data for a transaction is synchronized. The input for the
parse function is a block of data and the output is a parsed subset. This
permits the control system to manage all data into a single data point, which
can then be sent using an unsolicited message to the control connector. The
control connector then sends the data as a single unit to the Transaction
Control Manager service or FactoryTalk Transaction Manager service. The
Transaction Control Manager service or FactoryTalk Transaction Manager
service uses the arrival of the data point as a trigger and then parses out the
individual values as needed. Since the control system gathered all of the data
into a single block and the block was sent to the Transaction Control
Manager service or FactoryTalk Transaction Manager service as a single
unit, it is synchronized. The Parse function can also be used on scheduled
107
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
data points and in scheduled transactions to separate data values from a
single data point.
108
●
7 ●Creating Transactions
●
●
●
●
109
Chapter 8
Understanding Online Edits
Introducing Online Edits
The ability to change data points and transactions in a FactoryTalk
Transaction Manager configuration while it is running is known as online
edits. The use of online edits allows data collection to continue in your
automation system while you add new or modify existing data points and
transactions. The following terms and concepts are fundamental to
understanding how to perform online edits.
Understanding Online Edit Concepts

Configuration that uses online edits– A configuration you can change
while it is running.

Current definition– The definition of a transaction or data point that is
currently running.

Pending definition– The changes made to data points or transactions in
a running configuration that uses online edits. Pending edits must be
saved before they can be assembled. Pending edits do not affect the
running configuration until they have been assembled.

Assemble pending edits– The process of changing the running, current
definition of a transaction or data point in a configuration that uses
online edits to the pending definition. You cannot assemble pending
edits until you save them first.

Cancel pending edits– The process of removing pending edits made to
data points or transactions. Since pending edits do not affect the running
111
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
configuration until they have been assembled, the definition of a data
point or a transaction reverts to the current definition and there is no
effect on the running configuration.

Pending edit alerts– Informational messages describing the side
effects of the pending data points or transaction edits made on running
transactions.

Transaction Control Manager– Similar to the FactoryTalk
Transaction Manager service, but with the additional functionality of
the FactoryTalk Live Data control connector embedded in it. In a
configuration that uses online edits, the Transaction Control Manager
service replaces the separate FactoryTalk Transaction Manager service
and FactoryTalk Live Data control connector services.
Online Edits Workflow
The diagram below illustrates the multi-step process of changing a
configuration that uses online edits.
112
1.
Create data point and/or transaction pending edits.
2.
Save pending edits.
3.
Review pending edit alerts (immediately or later) (optional).
4.
Cancel all or cancel selected pending edits (if desired).
●
8 ●Understanding Online Edits
●
●
●
●
5.
Assemble all or assemble selected pending edits.
Figure 15: Online Edits Workflow diagram
113
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
The running configuration is not affected until the end of the process when
the pending edits are assembled. Saving, reviewing or canceling pending
edits prior to assembling only affects the configuration files, not the running
configuration itself.
Configurations That Use Online Edits
A configuration that uses online edits allows you to add new data points and
transactions as well as change existing data points and transactions while it
is running. These changes are referred to as pending edits. In defining
configurations that use online edits, you automatically use the Transaction
Control Manager which communicates exclusively with FactoryTalk Live
Data data servers.
If you wish to convert existing configurations to configurations that use
online edits, you will need to migrate the existing configurations using
RSLinx Classic, RSView32, and OPC connectors to configurations that use
the FactoryTalk Live Data connector. For more information about available
migration methods and tools, refer to the product CD or Rockwell
Automation Knowledgebase Web site. Go to
http://www.rockwellautomation.com/support/, click the Knowledgebase
link and search by entering keywords such as ―FactoryTalk Transaction
Manager‖, ―RSSql‖, or ―migration‖.
If you visit the support site for the first time, you need to select your region and
country in order to access the Knowledgebase page.
The following guidelines apply to working with configurations that use
online edits.
In a running configuration that uses online edits, you can:
114

Create new and modify existing data points.

Create new and modify existing transactions.

Enable and disable transactions.

Save and assemble pending edits.
●
●
8 ●Understanding Online Edits
●
●
●

View differences between current transaction definitions and
transactions with pending edits.
In a running configuration that uses online edits, you cannot:

Modify configuration properties.

Modify error logging properties.

Add new, modify, or delete existing enterprise connectors.

Modify enterprise or control connector properties.

Use any control connector except FactoryTalk Live Data.

Modify database connection properties.

Add new, modify, or delete existing data objects.

Modify a starting or stopping event definition.

Change data point names or modes (scheduled, unscheduled or
device-scheduled).

Delete data points.

Delete transactions (although you can disable them).
If you have a running configuration with pending edits and then stop it, you cannot
make any further changes to those items with pending edits until you cancel or
assemble the pending edits.
Learn More About Current and Pending Edits
When discussing online edits, you need to understand the difference
between ―how data points and transactions are defined in the running
configuration‖ (current) and ―what the changes will be if you assemble‖
(pending).
A current edit reflects how a data point or a transaction is currently defined
in the running configuration.
115
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
A pending edit reflects the new definition of a data point or transaction after
you have changed and saved it, before it has been assembled. Pending edits
do not affect the currently running configuration until they have been
assembled. After pending edits have been assembled, they replace the
current definition and become the new current definition. In the Transaction
Definition view on the main FactoryTalk Transaction Manager user
interface, notice the Current label for those transactions that do not have
pending edits. For transactions with pending edits, there is a pending row
and a current row.
Assembling Pending Edits
The process of making the running configuration aware of the changes made
to data points or transactions is referred to as assembling pending edits. You
must save pending edits before you assemble. If you attempt to assemble
pending edits before you save them, a warning message displays.
You can assemble pending edits from the following:

Main FactoryTalk Transaction Manager user interface.

FactoryTalk Data Point dialog box.

Pending Transaction Definition dialog box.

Pending Edit Alerts dialog box.
This process may affect different types of pending edits based in the dialog
box from which you assemble. If you have questions about what will or will
not be assembled, refer to the online help.
FROM THE MAIN FACTORYTALK TRANSACTION MANAGER USER
INTERFACE
When you assemble pending edits from the toolbar on the main FactoryTalk
Transaction Manager user interface, all pending edits for transactions and
data points are assembled.
116
●
●
8 ●Understanding Online Edits
●
●
●
FROM THE FACTORYTALK DATA POINT DIALOG BOX
Assembling from this dialog box affects only the selected data point rows
and only data point pending definitions. Transaction pending definitions are
not assembled from this dialog box.
FROM THE PENDING TRANSACTION DEFINITION DIALOG BOX
The pending definitions for the transaction you are currently viewing are
assembled. Data point pending definitions are not assembled from this
dialog box.
FROM THE PENDING EDIT ALERTS DIALOG BOX
When you assemble transaction or data point pending edits that have caused
side effects that you may not be aware of, FactoryTalk Transaction Manager
prompts you to review the pending edits on the Pending Edit Alerts dialog
box. If you select Assemble All from the Pending Edit Alerts dialog box, all
of the data point and transaction pending edits are assembled (including the
pending edits that did not cause alerts) and therefore do not display in the
dialog box.
Canceling Pending Edits
The process of removing pending edits made to data points and transactions
in a running configuration that uses online edits is referred to as canceling.
You can cancel pending edits after you have saved. You cannot cancel
pending edits after you have assembled. Canceling pending edits does not
affect the running configuration, and data point or transaction definitions
return to their original definition before changes were made. You can cancel
pending edits from the following dialog boxes:

FactoryTalk Data Point.

Pending Transaction Definition.

Pending Edit Alerts.
117
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
Pending Edit Alerts
Pending edit alerts are informational messages explaining that a transaction
that has ―state‖ information (that is, internal buffers that contain information
about the current and previous states of the transaction) will lose that state
information. The conditions necessary for a transaction to be reset are
described in detail below.
HOW DOES A PENDING EDIT ALERT OCCUR?
Some transactions require state information to execute correctly. If you
make certain changes to these transactions or the bindings they use, the
transaction resets or behaves as though it is starting for the first time when
you assemble the pending edits. FactoryTalk Transaction Manager warns
you that the transaction will be reset by displaying a pending edit alert
message. If the transaction includes any of the following characteristics, it
requires state information.

Ignore First Unscheduled Event.

Transactions Stores Data On Number of Completed Transactions.

Transactions Stores Data On Data Change and/or Rate.

Expression using DIFF function.

Expression using Data Point Range function used in conjunction with
the Min, Max, or Avg functions.
A pending edit alert occurs if your enabled transaction includes any of the
characteristics listed above and you perform any of the following tasks or
change any of the transaction parameters:
118

Trigger type.

Unscheduled event data point trigger.

Add a binding.

Delete a binding.

Data point to expression.
●
8 ●Understanding Online Edits
●
●
●
●

Expression to data point.

Data type of binding.

Data point in a binding.

Expression in a binding.

Order of bindings.

Merge input/output parameters in a binding.

Separate input/output parameters in a binding.
Or change these data point parameters:

Number of elements in an array.

Size of string.

Address of a data point.

Data type of a data point.
You can review transactions that have pending edit alerts on the Pending
Edit Alerts dialog box. From this dialog box, only the transactions and data
points with pending edit alerts are displayed; pending edits without alerts are
not displayed. You can either assemble or cancel:

The selected transactions.
119
●
●
●
FactoryTalk Transaction Manager User Guide
●
●

All the transactions in the configuration (even the ones not displayed on
this dialog box).
Figure 16: Pending Edit Alerts dialog box
120
●
●
8 ●Understanding Online Edits
●
●
●
Creating a Configuration That Uses Online Edits
Two fundamental components constitute a configuration that uses online
edits: exclusively using the FactoryTalk Live Data control connector, and
selecting the Enable Online Edits check box.
Figure 17: FactoryTalk Transaction Manager Configuration
Editing Data Points In a Running Configuration That
Uses Online Edits
There are two ways to edit data points (or create pending edits) in a running
configuration: add new data points or edit existing data points.
You can access the FactoryTalk Data Point dialog box from the
Configuration Checklist or the Configuration tree on the main FactoryTalk
Transaction Manager user interface. On the FactoryTalk Data Point dialog
box, notice that the FactoryTalk Connector and the Application fields cannot
be edited.
121
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
ADDING NEW DATA POINTS
To begin adding new data points, navigate to the correct area in your
FactoryTalk Directory in the Select Tags group and double-click to open the
folder/area. Select a tag in the Contents of window, and then click Add
Selected Tag(s). The new data points appear in red text in the data point
grid. This new data point is considered a pending edit.
In creating new data points and saving them, saving pending edits does not
affect the running configuration because they have not been used in a
transaction. Assembling new data points that are not used in a configuration
that uses online edits does not affect the running configuration because
FactoryTalk Transaction Manager does not collect data for data points that
are not used. Data points must be assembled before they can be used in a
new transaction.
EDITING EXISTING DATA POINTS
While editing existing data points, you may change any of the data point
parameters except the data point name and mode (scheduled, unscheduled or
device-scheduled). To open the Edit Collection Parameters of Selected
Row(s) dialog box and change the properties of data points, use one of the
methods described below:

Select the data point row in the data point grid, right-click and select
Edit Selected Collection Parameters from the menu.

Double-click in the data point row to which you want to make the
change.

Select the data point row in the data point grid and select Create Edits.

Select the data point row in the data point grid, and copy or paste data
points from Excel.
After you have finished modifying the data point parameters, you must save
the changes before you close the FactoryTalk Data Point dialog box.
122
●
●
8 ●Understanding Online Edits
●
●
●
SAVING DATA POINT PENDING EDITS
When you are finished adding new data points or changing existing data
points, you must save the pending edits. Select the data point rows in the
data point grid and click Save Edits or select the data point rows in the grid,
right-click and select Save Selected Edit(s) from the menu. You must always
save pending edits before you assemble.
ASSEMBLING DATA POINT PENDING EDITS
To make the pending edits effective in the running configuration, you must
assemble them. On the FactoryTalk Data Point dialog box, select the data
point rows in the grid and click Assemble Edits or select the data point rows
in the grid, right-click and select Assemble Edits from the menu.
It is not critical to assemble pending edits at a specific time in the online
edits process. If you have already created data point pending edits, you can
close the FactoryTalk Data Point dialog box without assembling and
proceed to make changes to transactions on the Pending Transaction
Definition dialog box. However, data point pending edits do not display on
the Pending Transaction Definition dialog box until they have been
assembled. It is a good idea to save and assemble data point pending edits
before creating transaction pending edits. Assembling new data points does
not affect a running configuration because the new data points are not used
in a running transaction yet.
You can also click Assemble Edits on the main FactoryTalk Transaction
Manager user interface to assemble data point pending edits.
CANCELING DATA POINT PENDING EDITS
To cancel pending edits, select the data point rows in the grid and click
Cancel Edits or select the data point rows in the grid, right-click and select
Cancel Edits from the menu. You can cancel pending edits after you have
saved. You cannot cancel pending edits after you have assembled.
123
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
Editing Transactions In a Running Configuration That
Uses Online Edits
When you open the Transaction Definition dialog box to edit an existing
transaction, notice that the fields are all disabled. You must first click
Create Edits to begin making changes to the transaction. Notice that the
title changes to Pending Transaction Definition dialog box. Then you can
change transaction bindings and parameters such as scan rate or timeout, and
even enable or disable the transaction. If you want to change the transaction
name or the data object that the transaction uses, you must create a new
transaction. When you are finished modifying the transaction, click Save
Edits to save your changes. You must always save pending edits before you
assemble. The following figure is an example of the Transaction Definition
dialog box.
Figure 18: Transaction Definition dialog box
124
●
●
8 ●Understanding Online Edits
●
●
●
You can edit multiple transactions in a running configuration that uses
online edits from the main FactoryTalk Transaction Manager user interface.
Select one or more transactions in the Transaction Definition View in the
right pane, right-click, and select one of the following menu options.

Enable Transaction or Disable Transaction- A new pending edit row
displays with the new state. The pending edit is automatically saved, but
must be assembled manually.

Edit Transaction Parameters- The parameters that display on the
Trigger and Storage Parameters dialog box are FactoryTalk Transaction
Manager default values, not the values of the selected transactions.
Once again, the pending edit is automatically saved, but must be
assembled manually.
SAVING TRANSACTION PENDING EDITS
When you are finished changing the transaction, save the pending edits. You
must save pending edits before you assemble. Saving pending edits does not
affect the running configuration, it only saves the pending definition.
ASSEMBLING TRANSACTION PENDING EDITS
To make the pending edits effective in the configuration, you must assemble
them. On the Pending Transaction Definition dialog box, click Assemble
Edits. You can also click Assemble Edits on the main FactoryTalk
Transaction Manager user interface to assemble transaction pending edits.
There may be a delay between the time you assemble the pending definition and the
time the pending definition actually becomes effective, regardless of when the
FactoryTalk Transaction Manager user interface indicates the changes have been
made.
The rules governing when the actual transaction is changed are complex
because they take into consideration the management of currently running
transactions. Keep the following in mind:

If a transaction is not currently executing, the software will apply
pending edits immediately.
125
●
●
●
FactoryTalk Transaction Manager User Guide
●
●

If a transaction is currently executing, the software will wait until that
transaction has completely executed or it’s timeout has been reached
before applying pending edits. No additional instances of this
transaction will be executed until the pending edits have been applied.
The Transaction Control Manager log file contains the entry displaying the
time the transaction in question has been assembled. To view this log file on
the main FactoryTalk Transaction Manager user interface, select the
Transaction Control Manager in the Configuration tree, and click Log Files
on the toolbar.
VIEWING TRANSACTION DIFFERENCES
On the Transaction Differences dialog box, you can see the differences
between the current definition and the pending definition for a specific
transaction. You must save pending edits before you view transaction
differences. Click Show Differences on the Pending Transaction Definition
dialog box to view transaction differences.
126
●
8 ●Understanding Online Edits
●
●
●
●
Transaction properties are displayed at the top of the dialog box and
bindings (including the address location of the data points, not just the data
point names) are displayed at the bottom of the dialog box. The default
option is All, but you may select Differences to display only the properties
or bindings that are different between the current and pending definitions.
You can view the differences between the current and pending transaction
definitions any time after you save, but before you cancel or assemble
pending edits.
Figure 19: Transaction Differences dialog box
You can also view transaction differences in the Transaction Definition
View on the main FactoryTalk Transaction Manager user interface. Select a
transaction, right-click, and select Show Transaction Differences from the
menu.
127
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
CANCELING TRANSACTION PENDING EDITS
To cancel pending edits after you saved them on the Pending Transaction
Definition dialog box, click Cancel Edits. You cannot cancel pending edits
after you have assembled. Canceling pending edits does not affect the
running configuration, it only removes the pending definition. If you have a
running configuration with pending edits and then stop it, you cannot make
any further changes to the configuration until you cancel or assemble the
pending edits.
128
●
8 ●Understanding Online Edits
●
●
●
●
129
Chapter 9
Exploring Advanced Topics
Introducing Advanced Topics
This chapter will provide the following additional information for using
FactoryTalk Transaction Manager:

Remote user interface.

Distributed configurations.

Data point buffering.

Increasing performance.
Remote User Interface
A remote FactoryTalk Transaction Manager user interface is used to
configure FactoryTalk Transaction Manager services and configuration
(.dat) files to run on another computer. For example, the FactoryTalk
Transaction Manager user interface runs on Computer A, but the
FactoryTalk Transaction Manager services and FactoryTalk Transaction
Manager configuration files are located on Computer B. No additional
licensing is required to perform this function remotely.
Although you can use the Demo or Trial versions of FactoryTalk Transaction
Manager to configure a remote user interface, you cannot run a configuration using
either of those versions.
131
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
The remote FactoryTalk Transaction Manager user interface communicates
directly with the Configuration Server, which then reads from and writes to
the configuration files.
Figure 20: Communication scheme
Remote browsing allows you to browse DSNs and Oracle connection strings
that are not found on the local computer. All browsing for FactoryTalk data
points and all databases is in the context of Computer B.
Configuring the Remote User Interface
While running the FactoryTalk Transaction Manager user interface on the
remote computer (the computer not running the Configuration Server),
select the computer name in the Configuration tree, right-click and select
Register Configuration Server from the menu. Enter the host computer name
on the Register Configuration Server dialog box, then click Register.
132
●
9 ●Exploring Advanced Topics
●
●
●
●
If you are not using the FactoryTalk Live Data connector, we recommend that you do
not attempt to use a remote FactoryTalk Transaction Manager user interface for
configuring your data points.
When using the remote FactoryTalk Transaction Manager user interface, you must
ensure that all of the computers that are involved in your configuration belong to the
same FactoryTalk Directory.
For FactoryTalk Security to work properly, the local FactoryTalk Transaction
Manager user interface and remote FactoryTalk Transaction Manager user interface
must share the same Configuration Server in the FactoryTalk Directory.
Distributed Configurations
A distributed configuration exists when FactoryTalk Transaction Manager
services are used on different computers. One advantage of using a
distributed configuration is that the processing of large amounts of data that
can be distributed across multiple computers. A single computer processor
may not be able to handle the increased amount of data that multiple
computers can process, or you may want to use multiple control connectors
or enterprise connectors of the same type.
In Step 2 of the Configuration Checklist, you create a distributed
configuration by choosing different computers to run the different
FactoryTalk Transaction Manager services.
Licensing Required For a Distributed Configuration
A FactoryTalk Transaction Manager Professional license is required to
distribute control and enterprise connector services among multiple
computers. You will need to run the FactoryTalk Server Activation software
on the network computer(s) that will act as the activation server(s). You will
need to run the FactoryTalk Client Activation software on each of the client
computers. Then you will direct the client computers to the activation server
computer.
133
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
The license must not be installed on a mapped drive, since the Transaction Control
Manager service or FactoryTalk Transaction Manager service will not be able to use
it.
Establishing Microsoft Windows Privileges
The FactoryTalk Transaction Manager user interface must be logged into a
Microsoft Windows 2003/XP/Vista/2008 R2 account that has administrative
privileges for all computers that are part of the FactoryTalk Transaction
Manager system. This requirement allows the FactoryTalk Transaction
Manager user interface access to the Microsoft Windows
2003/XP/Vista/2008 R2 Service Control Manager to start and stop the
FactoryTalk Transaction Manager services.
Creating a Distributed Configuration
In Step 1 of the Configuration Checklist, define the FactoryTalk Transaction
Manager configuration files using a path that must be local to the location of
the Configuration Server. Then, select the control and enterprise connector
services. In Step 2, define the host computer on which each service will run.
You should have FactoryTalk Transaction Manager installed on each of the
host computers before you begin.
Using UNC Paths
For distributed configurations, you should use the Universal Naming
Convention (UNC) for the error log (.log) and transaction cache (.rsl) file
paths when defining the configuration. Follow the format below:
\\servername\sharename\path
For example:
\\Computer 1\c$\rssql_config
It is important that the account you are currently logged into (and the one that
FactoryTalk Transaction Manager services will run as) has read and write privileges
to that UNC share.
134
●
●
9 ●Exploring Advanced Topics
●
●
●
CHANGING THE TRANSACTION CACHE FILE PATH
To change the transaction cache file, select the configuration name, and then
select Configuration > Properties. From the Cache tab on the
Configuration Properties dialog box, double-click the connector to change
the file path.
The transaction cache file must reside on the same computer as the FactoryTalk
Transaction Manager service.
CHANGING THE ERROR LOG FILE PATH
To change the error log file, select the Error Log tab from the Configuration
Properties dialog box and change the file path in the field.
You can store the error log files on the remote FactoryTalk Transaction Manager
computer; this may help to reduce network traffic. Unfortunately, you may not be able
to view those log files from the local FactoryTalk Transaction Manager computer; in
this case, view the files directly on the remote FactoryTalk Transaction Manager
computer.
Data Point Buffering
Simple logging applications include many locations for buffering data. This
means that the potential exists for discrepancies between the values in your
controller and the values in your database. The following sections describe
different areas where data point buffering can be used.
BUFFERING IN THE CONTROLLER
Values may change between scans, or more likely, the data server may read
a series of related values while the controller is updating them. In this case,
the values will not be synchronized. This problem can be solved by either
blocking the data into a single message sent by the controller or by making
sure that the controller does not trigger the transaction until all the values are
set. You should also use a transaction result to alert the controller that the
values have been read and can now be changed.
135
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
BUFFERING IN THE FACTORYTALK TRANSACTION MANAGER CONTROL
CONNECTOR
The FactoryTalk Transaction Manager control connector maintains a copy
of the data. Data servers, which may have separate copies of the data, send
changed values to the control connector. Once in the control connector, the
data is either sent to the FactoryTalk Transaction Manager service
(unscheduled data points) or is buffered until it is requested (scheduled data
points). Unscheduled data points that are sent to the FactoryTalk
Transaction Manager service are used in currently running transactions or as
transaction triggers, or they are used to update the current value table of the
FactoryTalk Transaction Manager service. If the data points are not
immediately needed, they can be overwritten before the data is used. This
will appear to cause data loss.
Scheduled data points are only used when a transaction is executed.
Scheduled data points are stored in the control connector until the
FactoryTalk Transaction Manager service requests them. If the transaction
executes slower than the data is changing in the controller, then data may be
overwritten in the control connector’s buffer. In some circumstances, lost
data is acceptable (for example, where a temperature is recorded every five
minutes but fluctuates every few seconds). The control connector is aware of
every change while the FactoryTalk Transaction Manager service is only
aware of the value that is current every five minutes.
BUFFERING IN THE TRANSACTION CONTROL MANAGER SERVICE
The Transaction Control Manager service has a local data point cache that
contains the current values for every data point and the time the value was
collected. If the Data Valid option that you set on the FactoryTalk Data Point
Definition dialog box is set to zero, data is not requested from the
FactoryTalk Live Data server because this server automatically provides
updated data values when they change (hence, the values for the Transaction
Control Manager services are always correct). Transactions buffer their own
values and only request those values from the Transaction Control Manager
service master value table when the Data Valid timeout has occurred. An
exception to this rule is Device- Scheduled points, which are read from the
136
●
●
9 ●Exploring Advanced Topics
●
●
●
controller by the FactoryTalk Live Data server once it receives the read
request from the Transaction Control Manager service. Another exception is
that the FactoryTalk Transaction Manager service never requests the current
value of an unscheduled data point from the FactoryTalk Live Data server.
BUFFERING IN THE FACTORYTALK TRANSACTION MANAGER SERVICE
The FactoryTalk Transaction Manager service has a local data point cache
that contains the current values for every data point and the time the value
was collected. If the Data Valid option that you set on the appropriate
connector’s Data Point Definition dialog box is set to zero, data is requested
from the control connector every time it is needed. Using this data, the
FactoryTalk Transaction Manager service knows which data points are still
fresh (still in the data valid timeout range), and which data points need to be
requested from the control connector. Note that the data is not read from the
controller at this time but from the control connector’s buffers. The
exception to this rule is device scheduled data points, which are read from
the controller by the data server once it receives the read request from the
control connector. The other exception is that the FactoryTalk Transaction
Manager service never requests the current value of an unscheduled data
point from the control connector.
Individual transaction buffers are maintained for each transaction that is
running; if two copies of the same transaction are running at the same time,
the data values from the second transaction do not overwrite the data values
from the first. Only unscheduled transactions can execute more than one
copy of the same transaction at the same time.
BUFFERING IN CACHED TRANSACTION FILES
Completed transactions that are not configured for real-time storage are
buffered in cached transaction (*.rsl) files prior to storage in the database.
Therefore, data will not be available from a query until it has been removed
from the cache file and written to the database.
The rate that the cache transaction files are applied is also controllable. In
the Transaction Definition dialog box, set the number of completed
137
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
transactions to a smaller value or decrease the time between cache
transaction files. This will improve the timeliness of the data in your
database, but increase the load on your database.
Increasing Performance
The following sections discuss recommendations for increasing
performance when running FactoryTalk Transaction Manager
configurations.
Control System

Store data in the control system in consecutive locations. This allows
the control data server to read and write the entire block of data one time
instead of performing several reads and writes for each transaction.

If you must use DDE, then select AdvanceDDE instead of DDE because
AdvanceDDE is faster than CF_Text.

Enable control system data server optimization for reads and writes.

Use event driven communication (unsolicited messages) instead of fast
polling. For example, if the control data does not change often, set the
control system to send data only when it changes instead of
continuously polling.

If you must poll control data, use an appropriate poll rate. For example,
do not poll every 10 milliseconds for data that is saved every 10
seconds.
Database
138

Use a commercial database (e.g. Microsoft SQL Server) rather than a
personal database (such as Microsoft Access). If you choose a
Microsoft SQL Server, upgrade it to the version 2000 or later.

Distribute the database to a different computer than the one running
FactoryTalk Transaction Manager.

Use an appropriate data model for your application.
●
●
9 ●Exploring Advanced Topics
●
●
●

Tune the database. Understand when to use indices and how to archive
data. Consult your database administrator for assistance.

Optimize queries, triggers, and stored procedures executed by
FactoryTalk Transaction Manager.
FactoryTalk Transaction Manager

Trigger transactions on unscheduled data change instead of scheduled
transaction execution.

If you must use DDE, select hot links instead of cold links to the control
data server.

Use FactoryTalk Device Scheduled collection mode, which improves
data accuracy and reduces network traffic.
This collection mode will cause transactions to run slower.

Distribute both control connectors and enterprise connectors on
multiple computers.

When using real-time transactions, use multiple real-time threads. The
disadvantage is that this consumes extra connections to the database.
Some databases are licensed based on the number of simultaneous
connections.

Use an Oracle OCI connection instead of an ODBC connection to an
Oracle database.

Use cached transaction files instead of real-time threads, which
enhances database performance on commercial databases that allow
―array inserts.‖

Modify the cached transaction file parameters (number of transactions
per log file and time between cache files) to optimize the scheduling and
volume of transactions to your database.

Disable debug error logging in FactoryTalk Transaction Manager.
139
●
●
●
FactoryTalk Transaction Manager User Guide
●
●

When collecting data from RSLinx Enterprise and FactoryTalk View,
some controller values may exist in RSLinx Enterprise and in the
FactoryTalk View tag database. Collect these points from RSLinx
Enterprise, not from FactoryTalk View. This allows RSLinx Enterprise
to optimize the data collection from the controller by reading the data
once and passing it to FactoryTalk View and FactoryTalk Transaction
Manager.

When collecting data from RSLinx Classic and RSView32, some
controller values may exist in RSLinx Classic and in the RSView32 tag
database. Collect these points from RSLinx Classic, not from
RSView32. This allows RSLinx Classic to optimize the data collection
from the controller by reading the data once and passing it to RSView32
and FactoryTalk Transaction Manager.

Delete unused data objects and database connections. The enterprise
connector automatically tries to connect to these databases even if they
are not used in the configuration.

If a controller register is assigned to more than one data point in a
transaction, use the same data point name so that the Transaction
Control Manager service or FactoryTalk Transaction Manager service
does not have to request the data more than once.
Hardware and Operating Environment
140

Use the fastest CPU, most RAM, and fastest disk controller as possible,
as well as multiple fast disks.

Run FactoryTalk Transaction Manager services, especially the
Transaction Control Manager service or FactoryTalk Transaction
Manager service, on a multi-processor computer. The FactoryTalk
Transaction Manager services are multi-threaded and can take
advantage of multiple-processors.

Optimize Ethernet traffic by using a local subnet that uses switched
Ethernet instead of shared.

Increase the Ethernet data rate from either 10Mbit or 100Mbit.
●
9 ●Exploring Advanced Topics
●
●
●
●

Turn off ODBC trace and SQL trace facilities.

Place the Microsoft Windows 2003/XP/Vista/2008 R2 operating
system and paging files, the cached transaction files, and the database
and its associated files on separate physical disks.
141
Appendix A
FactoryTalk Transaction Manager Sample
Applications
External Trigger Sample Application
The External Trigger sample application illustrates how an external
application can trigger a FactoryTalk Transaction Manager transaction. Use
external triggering to create a custom user interface to the FactoryTalk
Transaction Manager application or to integrate FactoryTalk Transaction
Manager functionality into an existing software system.
The Extras directory on the FactoryTalk Transaction Manager product CD
contains the External Trigger sample application discussed in this appendix.
Contents
The example application contains the following elements:

A Microsoft Excel spreadsheet named ExternalTriggerSample.xls. The
integer number in cell A1 is the data point that is sent to the database.

A Microsoft SQL database with a table named ExternalTriggerSample
that contains three columns: ExternalTriggerDatabaseID (an
Autonumber field), ExcelValue, and a timestamp.

A FactoryTalk Transaction Manager configuration that contains a
single unidirectional transaction named ExternalTriggerTransaction.
This transaction obtains a data value from cell A1 in an Excel
spreadsheet and appends a record named ExternalTriggerSample in the
Microsoft SQL database. The transaction is defined so that it can be
triggered by an external application.
143
●
●
●
FactoryTalk Transaction Manager User Guide
●
●

Three sample programs: one each in Microsoft Visual Basic, C
Language, and Microsoft Visual C++ allow you to trigger a transaction
by entering a transaction name.
Running the Application
1.
Open the ExternalTriggerSample.xls Excel spreadsheet and enter an
integer value in cell A1. This is the data value used by the transaction.
2.
Create the ExternalTriggerSample table using the provided
ExternalApplication.sql script.
3.
Create a System DSN (use ODBC Data Sources on the Microsoft
Windows 2003/XP/Vista/2008 R2 Control Panel) named ExtTrigger
that points to the Microsoft SQL table (ExternalTriggerSample).
4.
Restore the FactoryTalk Transaction Manager configuration contained
in the ExternalTrigger.rsq file using correct host name paths. Start the
configuration, and wait for all traffic light indicators to turn green.
5.
Select the programming environment that you will use, and open the
corresponding sample program from its appropriate subdirectory
(VB_Example.vbp, C_Example.dsw, Visual_CPP_Example.dsw).
6.
Run the program and enter the ExternalTriggerTransaction transaction
name.
If you are using the Visual_CPP_Example.dsw, click Trigger to trigger the
transaction.
7.
View the records that have been created in the database. A new row will
be created each time a transaction is triggered.
8.
You can change the data value in the Excel spreadsheet or select another
option on the sample application screen.
If you are using the Visual_CPP_Example.dsw, you can continue to click Trigger.
144
●
A ● FactoryTalk Transaction Manager Sample Applications
●
●
●
●
The sample illustrates the following two methods in the FactoryTalk
Transaction Manager Application Program Interface (API) for triggering
transactions:

RSSqlUnconnectedTrigger() function: The only parameter is the name
of the transaction to be triggered (case sensitive). This function
establishes a connection to the FactoryTalk Transaction Manager
service, sends the trigger request, and stops the connection. This
function works well when the number of trigger requests is small. The
Visual Basic version of this call is RSSqlUnconnectedTriggerVB().

RSSqlConnectedTrigger() function: The only parameter is the name of
the transaction to be triggered (case sensitive). In addition, this function
requires that the calling function use the RSSqlConnect() and
RSSqlDisconnect() functions to manage the connection. This function
is better suited for applications in which a large number of transactions
must be triggered. The Visual Basic version of this call is
RSSqlConnectedTriggerVB(), and the related calls are
RSSqlConnectVB() and RSSqlDisconnectVB().
For more information, see the topic ―API Calls‖ in the FactoryTalk
Transaction Manager online help.
145
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
146
Appendix B
FactoryTalk Transaction Manager and
Microsoft COM+ Objects
Introducing FactoryTalk Transaction Manager and
Microsoft COM+ Objects
FactoryTalk Transaction Manager logs data to many different databases.
Additionally, FactoryTalk Transaction Manager can call stored procedures
in a database, as well as call Microsoft COM+ objects that are used in
building multi-tiered, distributed applications. The following examples
provide the steps required to create and use a simple COM+ object in a
FactoryTalk Transaction Manager configuration using Microsoft Visual
Basic. Some sections are optional, but they are included to demonstrate the
ability to reuse and distribute COM+ objects.
Creating the Remote Component
Complete the following prerequisites before you create a remote
component:

Install Microsoft Windows 2003/XP/Vista/2008 R2.

Verify administrator logon privileges.

Install Microsoft Visual Basic.

Verify COM+ activation in FactoryTalk Transaction Manager.
To create the remote component, complete the following steps:
1.
Open Visual Basic and create a new ActiveX DLL project.
147
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
2.
Select Project > References to add a reference to the Microsoft
ActiveX Data Objects 2.5 and COM+ Services Type libraries.
3.
Select Project > Project Properties. Click the General tab and change
the project name to ―ComSampleVB.‖ Make sure that the Threading
Model is Apartment Threaded.
4.
Recreate Code Sample A at the end of this section in the General
Declarations section of the default class module. Notice the use of the
required ObjectContext object.
5.
1.
Declare an object (in this case, ctxObject).
2.
Set the object using GetObjectContext().
3.
Follow GetObjectContext with your code.
4.
End the code with either a SetComplete or SetAbort method on
ctxObject.
Save the project and compile into a .DLL file.
Creating the Client Application
The client application is used to test the remote component outside of FactoryTalk
Transaction Manager. A remote component can be used by more than one client.
This process is optional.
To create the client application, complete the following steps:
148
1.
Create a new Visual Basic Standard EXE project.
2.
Select Project > Project Properties. Click the General tab and change
the project name to ClientSampleVB.
3.
Add a command button to the standard form.
4.
Copy Code Sample B at the end of this section and paste it into the
General Declarations section of the form.
5.
Save the project.
●
B ● FactoryTalk Transaction Manager and Microsoft COM+ Objects
●
●
●
●
Installing the Remote Component
To install the remote component, ―ComSampleVB,‖ complete the following
steps:
1.
Select Start > Programs > Administrative Tools > Component
Services to start the Component Services Console. If you do not see the
Administrative Tools Group on the Start menu, right-click the Taskbar
and select Properties from the menu. Select the Advanced tab, then
select Display Administrative Tools.
2.
In the left pane of the Component Services, click the plus sign next to
Component Services to expand it. Continue expanding Computers, My
Computer, and COM+ Applications.
3.
Right-click COM+ Applications and select New > Application.
4.
From the COM Application Wizard dialog box, click Next.
5.
Select Create an Empty Application and name the application
ComSampleVB.
6.
Select Server Application as the Activation Type, then click Next.
7.
Select Interactive User as the Application Identity, then click Next.
8.
Click Finish to complete the process.
9.
In the new application, select Components, right-click and select New >
Component from the menu.
10. From the COM Component Install Wizard dialog box, click Next.
11. Select Install new component(s) and browse to the directory where the
.dll file was saved in the ―Creating the Remote Component‖ procedure.
12. Select ComSampleVB.dll from the Select Files to Install dialog box and
click Open.
13. ComSampleVB.dll displays under Files to Install. Click Next, then
click Finish.
149
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
You should be able to run the client code “ClientSampleVB” from the Visual Basic
environment on the server computer successfully.
Setting Up the Remote Client
This process is optional.
A Microsoft COM+ application is usually part of a larger application
(N-tier) or system that affects many areas of a business. You will have to
decide how to distribute components across the servers and what clients will
have access to them. We assume a thorough understanding of the target
environment (user accounts/groups, server names, etc.). For general
concepts and detailed information about administering COM and COM+
applications, refer to the online help of the Component Services application.
You can install a Microsoft COM+ application by using the setup program
provided by the application vendor or the in-house developer, or by
manually installing and configuring the COM+ application using the
Component Services application.
For more information about installing a COM+ application, refer to
Installation Tasks in the online help of the Component Services application.
The following procedures explain how to export the remote COM+
component, move the client project ―ClientSampleVB.vbp‖ into Visual
Basic, then run the client application in the Visual Basic environment.
Creating the Microsoft COM+ Setup Program
This process is optional.
To create a COM+ setup program, complete the following steps:
1.
150
Select Start > Programs > Administrative Tools > Component
Services to start the Component Services Console.
●
B ● FactoryTalk Transaction Manager and Microsoft COM+ Objects
●
●
●
●
2.
In the left pane of the Component Services, click the plus sign next to
Component Services to expand it. Continue expanding Computers, My
Computer, COM+ Applications, and finally, the ComSampleVB
application folder.
3.
Right-click the ComSampleVB application and select Export from the
menu.
4.
From the COM Application Export Wizard dialog box, click Next.
5.
Enter, or browse for, the full path and filename where you will save the
Microsoft Install (MSI) file. Make sure to select Application proxy –
Install on other machines to enable access to this machine.
6.
Click Finish.
7.
Navigate to the directory to which you exported the application. An
MSI file and an MSI.CAB file that were built as a result of the export
appears in the directory.
8.
Move these files to the remote (client) computer and run the MSI file.
Do not run this program on the server. This program correctly registers
the remote components on the client computer.
Moving the Client Sample Application
This process is optional.
To move the Client Sample Program, complete the following steps:
1.
From Microsoft Windows Explorer, navigate to the directory in which
the client application is stored. A Form1.frm file and a
ClientSampleVB.vbp file appears in this directory.
2.
Move these files to the remote (client) computer.
3.
Open the .VBP file up in the Visual Basic environment.
151
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
You should now be able to run the ClientSampleVB application on the remote client
computer and execute the COM+ Server component “ComSampleVB” on the server.
Including the COM+ Enterprise Application Connector In
a FactoryTalk Transaction Manager Configuration
To include a Microsoft COM+ enterprise application connector in a
FactoryTalk Transaction Manager configuration, complete the following
steps:
1.
Open FactoryTalk Transaction Manager.
2.
Select the desired configuration in the Configuration tree, right-click
and select Define Configuration from the menu.
3.
From the dialog box, select the Microsoft COM+ check box under the
Enterprise Connector Services group.
4.
Click Apply to save the parameters, and then click Close.
Defining the COM+ Enterprise Application Connector
152
1.
Select the desired configuration in the Configuration tree, right-click
and select Define Connector from the menu.
2.
From the Connector Definition dialog box, select COM+ Connectors
from the Connector Service drop-down list.
3.
Enter a connector name, host computer name, user name, and password
in the appropriate fields.
4.
Click Apply to save the parameters, and then click Close.
●
B ● FactoryTalk Transaction Manager and Microsoft COM+ Objects
●
●
●
●
Defining the COM+ Data Object
The remote component must already be installed on the COM+ server before you
can define a FactoryTalk Transaction Manager COM+ data object. For more
information, refer to the “Installing the remote component” section in this appendix. If
you are on a client computer, the application proxy must already be installed. For
more information, refer to the “Setting up the remote client” section in this appendix.
1.
Select Configuration > Checklist.
2.
From the Configuration Checklist, make sure that all previous steps
have been completed (a yellow or green checkmark next to a step
designates that the step has been completed), then click Step 4.
3.
From the COM+ Data Object Definition dialog box, enter a name for
the connector in the Connector Name field.
4.
Enter a name for the data object in the Name field.
5.
If the desired COM+ connection does not display, click (…) to define
one.
6.
From the COM+ Connection Definition dialog box, select a connection
name from the drop-down list or enter it in the Connection Name field.
The User Name and Password fields are disabled because they are not supported in
the initial release of Microsoft COM+.
7.
Select a COM+ server from the drop-down list. The COM+ applications
(or proxies) installed on the computer display in the COM+
Applications area.
8.
Select a COM+ interface from the list, click Apply, then click Close to
return to the COM+ Data Object Definition dialog box.
9.
Select a COM+ Method from the drop-down list. The method
parameters that can be included in the specified FactoryTalk
Transaction Manager data object display in the Parameters column.
153
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
10. Click Apply to save the parameters, then click Close to return to the
Configuration Checklist.
You are now ready to use Microsoft COM+ components in a FactoryTalk
Transaction Manager transaction.
Code Sample A (ComSampleVB)
The following code is referenced in the ―Creating the remote component‖
procedure.
Option Explicit
Public Function Get_VB_Sample_Data( _
ByVal strKeyID As String, _
Optional ByRef strData As String, _
Optional ByRef intData As Integer, _
Optional ByRef lngData As Long, _
Optional ByRef sngData As Single, _
Optional ByRef dblData As Double, _
Optional ByRef bytData As Byte, _
Optional ByRef dtData As Date, _
Optional ByRef bolData As Boolean) _
As Long
‘ Declare an object variable as ObjectContext
Dim ctxObject As ObjectContext ‘Required
On Error GoTo errorhandler
‘ Set the object variable using GetObjectContext()
Set ctxObject = GetObjectContext() ‘Required
‘ Put all business code below
strData = "VB Sample Data"
intData = 32767
lngData = 32768
sngData = 34.02823
dblData = 1797.69313
bytData = 255
dtData = Now()
bolData = True
Get_VB_Sample_Data = 0
‘ Keep all business code above
154
●
B ● FactoryTalk Transaction Manager and Microsoft COM+ Objects
●
●
●
●
ctxObject.SetComplete ‘Required
Exit Function
errorhandler:
Get_VB_Sample_Data = 33999
ctxObject.SetAbort ‘Required
Err.Raise vbObjectError, "Error in Get_VB_Sample_Data ",
_
Err.Description
Exit Function
‘ Program Notes:
‘
‘ Note the use of SetComplete and SetAbort methods
‘ of the ctxObject to end the code. SetComplete and
‘ SetAbort indicate to the transaction server to
‘ deactivate the object and whether to commit changes
‘ made by the business code (SetComplete) or throw
‘ away all changes (SetAbort)
‘
‘ The purpose of the arguments (strKeyID – bolData) of
‘ the Get_VB_Sample_Data function is to demonstrate
‘ how to pass data to and from the function. The
‘ strKeyID variable will show a required input, notice
‘ the ByVal keyword. The remaining variables will show
‘ optional variables returned by the function, notice
‘ the Optional and ByRef keywords.
End Function
Code Sample B (ClientSampleVB)
The following code is referenced in the ―Moving the client sample
application‖ procedure.
Option Explicit
Private Sub Command1_Click()
Dim obj As Object
Dim szKey As String
Dim szString As String
‘ Create an instance of the remote component
155
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
Set obj = CreateObject("ComSampleVB.Class1")
‘ Put a value into the required argument and
‘ pass it to the remote component
szKey = "ignored"
‘ Call the remote component
‘ and display the return value
MsgBox obj.Get_VB_Sample_Data(szKey, szString)
‘ Display the returned data
MsgBox "String Data: " & szString
‘ Destroy the instance of the remote component
Set obj = Nothing
End Sub
Private Sub Form_Load()
Command1.Caption = "Call COM+ VB Sample"
End Sub
156
●
B ● FactoryTalk Transaction Manager and Microsoft COM+ Objects
●
●
●
●
157
Appendix C
Securing FactoryTalk Transaction Manager
Using FactoryTalk Security
About FactoryTalk Security
FactoryTalk Security is intended to improve the security of your automation
system by limiting access to those with a legitimate need. FactoryTalk
Security authenticates user identities and authorizes user requests to access a
FactoryTalk-enabled system. These security services are fully integrated
into the FactoryTalk Directory and are included as part of the FactoryTalk
Services Platform that installs with many Rockwell Software products.
For more information on configuring or overriding security services using
FactoryTalk Security, see the FactoryTalk Security online help (select Start
> Programs > Rockwell Software > FactoryTalk Tools > FactoryTalk
Help).
Considerations When Using FactoryTalk Transaction
Manager With FactoryTalk Security
Please keep the following in mind when configuring FactoryTalk
Transaction Manager for use with FactoryTalk Security:

FactoryTalk Transaction Manager inherits its security settings from
Network (also called Distributed) applications and/or the FactoryTalk
Network Directory. Any changes that you make via FactoryTalk
Security affect FactoryTalk Transaction Manager and all other products
that are connected to the same FactoryTalk Directory computer.
159
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
If you must change the FactoryTalk Directory computer location, reboot your
computer to synchronize the Configuration Server with the FactoryTalk Directory
computer.

The Configuration Server is the only FactoryTalk Transaction
Manager-specific component that you can apply security permissions to
via the FactoryTalk Administration Console. One Configuration Server
(in FactoryTalk Transaction Manager) is equivalent to one computer (in
FactoryTalk). All configurations that are displayed under a single
Configuration Server will have the same security settings.
For information on product-specific, FactoryTalk Security-related permissions that
are necessary for external components used by FactoryTalk Transaction Manager
(for example, FactoryTalk Live Data), please see the online help for that respective
component.

FactoryTalk Transaction Manager inherits its FactoryTalk Security
settings from the computer that hosts the Configuration Server. These
attributes must be configured using the FactoryTalk Administration
Console.
The computer that hosts the Configuration Server may be configured to inherit from a
higher level in the FactoryTalk Directory (for example, the Application or the Area).
For more information, see the FactoryTalk online help.
160

In addition to the standard Read and Write permissions, FactoryTalk
Transaction Manager also supports one custom action: Start, Stop, and
Assemble Configurations. For more information, see Specifying
FactoryTalk Security Permissions That Allow You to Perform
FactoryTalk Transaction Manager Tasks (page 162) and Writing
Product-specific Security Privileges From a Previous Release To a File
(page 169).

All productFactoryTalk Transaction Manager-specific privilege
information from previous releases will be ignored in existing
configurations and it will not be converted directly to FactoryTalk
Security attributes. All productFactoryTalk Transaction
●
C ● Securing FactoryTalk Transaction Manager Using FactoryTalk Security
●
●
●
●
Manager-specific privilege information can be viewed using the Write
FactoryTalk Transaction Manager-specific security privileges to file
tool (page 169), and then you can use that data to establish similar
permissions in the FactoryTalk Administration Console.

FactoryTalk Security is set in the FactoryTalk Directory. Therefore, if
you move a configuration from one FactoryTalk Directory to another
FactoryTalk Directory, your FactoryTalk Security permissions will not
be maintained.

If an administrator changes your individual security permissions in the
FactoryTalk Administration Console or if your user permissions to a
computer are altered, FactoryTalk Transaction Manager will reflect
those changes (in FactoryTalk Transaction Manager, select Security >
Permissions to launch the FactoryTalk Security Permissions dialog
box) without requiring you to log off and log on to FactoryTalk
Security. However, if an administrator makes changes in the
FactoryTalk Administration Console to a group membership (in which
you are a member), you must log off and log on again to FactoryTalk
Security for those permission changes to be enforced.

FactoryTalk Transaction Manager also includes a Security menu that
allows you to log on and log off from FactoryTalk Security from within
FactoryTalk Transaction Manager, as well as check the current user's
permissions.

If you select Security > Permissions in FactoryTalk Transaction
Manager, you can view current user permission information. The
permission types that can appear are "Read" "Write" or "Start, Stop,
and Assemble Configurations" (page 169).

If you want to share configuration tasks across multiple computers, the
FactoryTalk Directory servers on all of the computers must match. For
example, if the FactoryTalk Directory server and the FactoryTalk
Transaction Manager Configuration Server are on your computer
(computer A) and you want to communicate to another computer
161
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
(computer B) that is configured to use another FactoryTalk Directory
server, data cannot be shared between computer A and computer B until
the FactoryTalk Directory servers are the same.

All security permissions must be assigned in the FactoryTalk
Administration Console.

Keep in mind that the user name and password associated with
FactoryTalk Security permissions to the FactoryTalk Transaction
Manager user interface may be completely independent from the user
name and password associated with each connector.
For more information on configuring FactoryTalk Security, refer to the
FactoryTalk Security online help, section "About Security" (go to
x:\Program Files\Common Files\Rockwell\Help\FTSecurityEN.chm, where
x: is the drive where your Rockwell Software products are located).
Specify FactoryTalk Security Permissions That Allow
You To Perform FactoryTalk Transaction Manager Tasks
To perform specific tasks in FactoryTalk Transaction Manager, you must
first have specific FactoryTalk Security permissions. Use the following
table to determine the initial action (indicated by an ―x‖) that you or your
administrator must take in the FactoryTalk Administration Console to
ensure that you will be able to perform the specified FactoryTalk
Transaction Manager tasks.
To perform this
FactoryTalk
Transaction
Manager task:
162
Select the
following item on
the Explorer pane
in the FactoryTalk
Administration
Console:
Right-click the selected item on the Explorer pane in
the FactoryTalk Administration Console, select
Security, and then set the following actions on the
Security Settings dialog box that is displayed:
FactoryTalk
Transaction
Manager >
Start, Stop,
and Assemble
Transactions
Common > Common > Common >
List Children Read
Write
●
C ● Securing FactoryTalk Transaction Manager Using FactoryTalk Security
●
●
●
●
To perform this
FactoryTalk
Transaction
Manager task:
View a
configuration.
Select the
following item on
the Explorer pane
in the FactoryTalk
Administration
Console:
Right-click the selected item on the Explorer pane in
the FactoryTalk Administration Console, select
Security, and then set the following actions on the
Security Settings dialog box that is displayed:
FactoryTalk
Transaction
Manager >
Start, Stop,
and Assemble
Transactions
Computer in the
Computers group that
hosts the FactoryTalk
Transaction Manager
Configuration Server.
X
FactoryTalk Area
(located beneath
Network >
Application) that you
wish to browse for
tags.(1)
Change a
non-running
configuration.
X
Computer in the
Computers group that
hosts the FactoryTalk
Transaction Manager
Configuration Server.
Computer in the
X
X
FactoryTalk Area
(located beneath
Network >
Application) that you
wish to browse for
tags.(1)
Change a running
Common > Common > Common >
List Children Read
Write
X
X
X
X
X
X
163
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
To perform this
FactoryTalk
Transaction
Manager task:
Select the
following item on
the Explorer pane
in the FactoryTalk
Administration
Console:
Right-click the selected item on the Explorer pane in
the FactoryTalk Administration Console, select
Security, and then set the following actions on the
Security Settings dialog box that is displayed:
FactoryTalk
Transaction
Manager >
Start, Stop,
and Assemble
Transactions
Common > Common > Common >
List Children Read
Write
configuration (i.e., Computers group that
perform online
hosts the FactoryTalk
edits).
Transaction Manager
Configuration Server.
Start or stop a
configuration.
Computer in the
X
Computers group that
hosts the FactoryTalk
Transaction Manager
Configuration Server.
X
Run a service that
is not FactoryTalk
Live Data
enabled.
Run a service that
is FactoryTalk
Live Data enabled
(Transaction
Control Manager
or FactoryTalk
Live Data
connector) for
read only access to
the controller.(2)
164
FactoryTalk Area
(located beneath
Network >
Application) that you
wish to browse for
tags.
X
X
X
●
C ● Securing FactoryTalk Transaction Manager Using FactoryTalk Security
●
●
●
●
To perform this
FactoryTalk
Transaction
Manager task:
Select the
following item on
the Explorer pane
in the FactoryTalk
Administration
Console:
Right-click the selected item on the Explorer pane in
the FactoryTalk Administration Console, select
Security, and then set the following actions on the
Security Settings dialog box that is displayed:
FactoryTalk
Transaction
Manager >
Start, Stop,
and Assemble
Transactions
Common > Common > Common >
List Children Read
Write
(1) If you specify permissions at the application level in the FactoryTalk Administration Console, those
permissions will be inherited by all of the areas that are included in that application. You can also set the
permissions for each area separately. For more information, see the FactoryTalk Security online help.
(2) The user specified in the control connector must be a Microsoft Windows-linked user. This Microsoft
Windows-linked user does not have to be defined via FactoryTalk Security.
FactoryTalk Transaction Manager Behaviors When the
FactoryTalk Security Single Sign-on User Is In Effect
Single sign-on (SSO) is a FactoryTalk Security policy setting that allows
you to log on to the first product that you are running in the FactoryTalk
system, and then automatically allows you to be logged on (without being
prompted) to each subsequent Rockwell Software product that you run,
using the same user account and password information.
For more information on user account types and how they interact with
FactoryTalk Security, refer to the FactoryTalk Security online help, section
"About User, Computer, and Group Accounts" (go to x:\Program
Files\Common Files\Rockwell\Help\FTSecurityEN.chm, where x: is the
drive where your Rockwell Software products are located).
165
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
To use FactoryTalk Transaction Manager and FactoryTalk Security effectively, you
must have a FactoryTalk user account in the FactoryTalk Directory. Additionally, to
use FactoryTalk Transaction Manager to perform any design-time or run-time task,
you must log into FactoryTalk Security. For more information, see the following
sections. If you have additional questions, please contact your system administrator.
Overview
Single sign-on (SSO) is a FactoryTalk Security policy setting that allows
you to log on to the first product that you are running in the FactoryTalk
system, and then automatically allows you to be logged on (without being
prompted) to each subsequent Rockwell Software product that you run,
using the same user account and password information.
For more information on user account types and how they interact with
FactoryTalk Security, refer to the FactoryTalk Security online help, section
"About User, Computer, and Group Accounts" (go to x:\Program
Files\Common Files\Rockwell\Help\FTSecurityEN.chm, where x: is the
drive where your Rockwell Software products are located).
To use FactoryTalk Transaction Manager and FactoryTalk Security effectively, you
must have a FactoryTalk user account in the FactoryTalk Directory. Additionally, to
use FactoryTalk Transaction Manager to perform any design-time or run-time task,
you must log into FactoryTalk Security. For more information, see the following
sections. If you have additional questions, please contact your system administrator.
At FactoryTalk Transaction Manager Start Up
Use the following sections to learn how the SSO information is used at
FactoryTalk Transaction Manager start up.
166
●
C ● Securing FactoryTalk Transaction Manager Using FactoryTalk Security
●
●
●
●
After FactoryTalk Transaction Manager starts, all ties with the machine-wide SSO
are severed; any changes to the machine-wide SSO user do not affect the user
logged into FactoryTalk Transaction Manager. Likewise, if you log out of FactoryTalk
Transaction Manager (select Security > Logoff), the machine-wide SSO user is not
affected.
You are not required to perform any additional operations unless an alternate
FactoryTalk user wants to use FactoryTalk Transaction Manager. If an alternate
FactoryTalk user is desired, you must select Security > Logoff in FactoryTalk
Transaction Manager; then, the alternate user must select Security > Logon and
enter the required user information. Note that if you log off of FactoryTalk
Transaction Manager and another user logs onto FactoryTalk Transaction Manager
via the FactoryTalk Transaction Manager Security menu (Security > Logon), there
is no impact to the SSO user. This also applies when you have a Windows-linked
user account.
SCENARIO 1: YOU HAVE A WINDOWS-LINKED USER ACCOUNT
Prior to starting FactoryTalk Transaction Manager, if you:

are not recognized as the SSO user,

have a Windows-linked user account in the FactoryTalk Directory.
Then FactoryTalk Transaction Manager recognizes that an SSO is not set at
startup. However, since you have a Windows-linked user account in the
FactoryTalk Directory (and the user information on that account matches
your user information as the currently logged in Microsoft Windows user),
FactoryTalk Security logs you in as the SSO user. FactoryTalk Transaction
Manager uses your user information to represent the logged in FactoryTalk
Transaction Manager user.
SCENARIO 2: YOU HAVE A FACTORYTALK USER ACCOUNT AND ARE
LOGGED INTO THE FACTORYTALK DIRECTORY
Prior to starting FactoryTalk Transaction Manager, if you are:

a FactoryTalk user (with a FactoryTalk user account in the FactoryTalk
Directory),
167
●
●
●
FactoryTalk Transaction Manager User Guide
●
●

already logged on to the FactoryTalk Directory via Start > Programs >
Rockwell Software > FactoryTalk Tools > Log on to FactoryTalk or
some other FactoryTalk-enabled product.
Then FactoryTalk Transaction Manager immediately retrieves your SSO
information at startup. That user information represents both the
FactoryTalk Transaction Manager and FactoryTalk logged-in user.
SCENARIO 3: YOU DO NOT HAVE A WINDOWS-LINKED USER
ACCOUNT
Prior to starting FactoryTalk Transaction Manager, if you:

are not recognized as the SSO user,

do not have a Windows-linked user account in the FactoryTalk
Directory.
Then FactoryTalk Transaction Manager recognizes that an SSO is not
present at startup. You are prompted with the Log on to FactoryTalk dialog
box. Either:

Enter a valid FactoryTalk user name and password - In this case,
you are immediately logged into FactoryTalk Transaction Manager and
your user information represents the computer-wide SSO user.

Cancel the log on prompt - In this case, FactoryTalk Transaction
Manager starts up with the default system graphic displayed. To use
FactoryTalk Transaction Manager effectively, you must select Security
> Logon; you are immediately logged into FactoryTalk Transaction
Manager and your user information represents the computer-wide SSO
user.
When Using FactoryTalk Transaction Manager
Use the following sections to learn how the SSO information is used when
you are using FactoryTalk Transaction Manager:
168
●
C ● Securing FactoryTalk Transaction Manager Using FactoryTalk Security
●
●
●
●
The Security > Logon menu selection is available only when you are not currently
logged into FactoryTalk Transaction Manager. After logging on, you can log out at
any time by selecting Security > Logoff or by canceling the Log on to FactoryTalk
dialog box at FactoryTalk Transaction Manager startup.
Since FactoryTalk Transaction Manager severs all ties with the machine-wide SSO
at startup, selecting Security > Logon does to recognize the current SSO user (if
logged on). Additionally, selecting Security > Logoff does not log off the
machine-wide SSO user.
SCENARIO 1: YOU HAVE A WINDOWS-LINKED USER ACCOUNT
While using FactoryTalk Transaction Manager, if you select Security >
Logon and you:

have a Windows-linked user account in the FactoryTalk Directory,

are currently logged into Microsoft Windows.
Then you will be automatically logged into FactoryTalk Transaction
Manager.
SCENARIO 2: YOU DO NOT HAVE A WINDOWS-LINKED USER
ACCOUNT
While using FactoryTalk Transaction Manager, if you select Security >
Logon and you do not have a Windows-linked user account in the
FactoryTalk Directory, then the Logon to FactoryTalk dialog box appears.
Writing Product-Specific Security Privileges From a
Previous Release To a File
Prior to FactoryTalk Transaction Manager v9.00.00, the software used its
own security mechanism to secure configurations. If you used this
product-specific security implementation to secure your configurations in a
previous release, you can now use a utility to write your previous
FactoryTalk Transaction Manager security settings to a file.
169
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
When using this tool, you can specify the file name and location where this
file will reside. This file will be formatted as follows:

Line 1 - file title.

Line 2 - Configuration Server name.

Line 3 - configuration name.

Line 4 and subsequent lines - security level, the user or group name, and
any file notification options.
After generating this file, you can review the old product-specific security
privileges and use that content to establish new FactoryTalk Security
permissions in the FactoryTalk Administration Console.
For more information on writing product-specific security privileges to a
file, see the FactoryTalk Transaction Manager online help.
Map Old Product-Specific Security Privileges To the
New FactoryTalk Security Permissions
For more information on how old product-specific security privileges map
to the new FactoryTalk Security permissions, see the following table:
If you used this
old
product-specific
security privilege:
It has been replaced by this
FactoryTalk Security
permission or FactoryTalk
Transaction Manager custom
action:
RSSQL_ADMIN
Start, stop or assemble
FactoryTalk Transaction
(on-line editing) a running
Manager > Start, Stop, and
Assemble Configurations (page configuration.
162)
Note: This attribute also requires
that you have Common > Read
and Common > Write
permission.
170
This security permission
allows you to:
●
C ● Securing FactoryTalk Transaction Manager Using FactoryTalk Security
●
●
●
●
If you used this
old
product-specific
security privilege:
It has been replaced by this
FactoryTalk Security
permission or FactoryTalk
Transaction Manager custom
action:
This security permission
allows you to:
RSSQL_MODIFY
Common > Write (page 162)
Make offline changes to a
configuration.
Note: This attribute also requires
that you have Common > Read
permission.
RSSQL_VIEW
Common > Read (page 162)
View a configuration.
No privilege
No permissions needed.
View the following
FactoryTalk Transaction
Manager options (since
security permissions have
not been configured):

Security > Logon

Configuration > Exit

Help Menu (all enabled)

Configuration Tree
(empty)

System View Graphic
171
Appendix D
Glossary
The process of changing the running, current definition of a transaction or
data point in a configuration that uses online edits to the pending definition.
You cannot assemble pending edits until you save them first.
Assemble Pending Edits
The process of changing the running, current definition of a transaction or
data point in a configuration that uses online edits to the pending definition.
You cannot assemble pending edits until you save them first.
Audit Trail
A record of changes made to a FactoryTalk Transaction Manager service in
the FactoryTalk Transaction Manager configuration, by whom, and when
they were made, as compiled by the Configuration Server log file. The
changes are displayed in FactoryTalk Diagnostics.
Binding
The relationship between a single data object element (table column or
stored procedure parameter) and its corresponding data point or expression
in a transaction.
Bound Value
The data to be written to, or read from, a table column or stored procedure
parameter.
Configuration
A FactoryTalk Transaction Manager configuration consists of a set of
transactions and the connectors, data points, and data objects required to
implement the transactions. All configuration information is stored in the
173
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
configuration files. You can create an unlimited number of configurations,
but the FactoryTalk Transaction Manager can run only one configuration at
a time.
Configuration Server
The Configuration Server is a Microsoft Windows 2003/XP/Vista/2008 R2
service that runs continuously to provide a single interface to the
configuration (.dat) files that make up the FactoryTalk Transaction Manager
configuration. The Configuration Server simplifies access to configuration
files by filtering all changes to the files and interfacing with other
FactoryTalk Transaction Manager services. A collection of all changes that
affect a configuration are recorded in an audit trail (via either FactoryTalk
Diagnostics or the Configuration Server *.log file).
Configuration That Uses Online Edits
A configuration that can be changed while it is running and uses the
Transaction Control Manager service to communicate exclusively with
FactoryTalk Live Data servers.
Control Connector
A service that moves data between a data server in the control system and
the FactoryTalk Transaction Manager service.
Control System
Typically includes a network of controllers and/or HMI servers that collect
data from, and control the operation of, machines in a manufacturing plant.
Data Object
A subset of columns in a database table or database view or a set of stored
procedure parameters, along with the database connection information to
access the database. A FactoryTalk Transaction Manager transaction acts on
a single data object, so all of the necessary database information for a
transaction must be contained in a single data object. Data objects are
defined in enterprise connectors.
174
●
D ● Glossary
●
●
●
●
Data Point
Data locations in the control system. Data points are associated with control
connectors and also contain collection parameters and other attributes. Data
points can serve as transaction triggers, supply input data for transactions,
and receive data as an output from a transaction.
Database View
A filter on selected fields in database table(s) outside of the FactoryTalk
Transaction Manager software.
DDE Control Connector
A service that moves data between the FactoryTalk Transaction Manager
service and a DDE or AdvanceDDE server.
DSN
An acronym for Data Source Name; that is, the name of the database being
used. A system DSN is available to all users and Microsoft Windows
2003/XP/Vista/2008 R2 services, while a user DSN is available only to the
user who configured it. The ODBC enterprise database connector requires a
system DSN to connect to an ODBC data source.
Enterprise Connector
A service that moves data between the FactoryTalk Transaction Manager
service and database(s) or an enterprise system.
Expression Editor
A FactoryTalk Transaction Manager utility used to create expressions prior
to binding them in a transaction.
FactoryTalk Metrics Enterprise Application Connector
FactoryTalk Security
Rockwell Software’s current security software that is intended to improve
the security of your automation system by limiting access to those with a
legitimate need. FactoryTalk Security authenticates user identities and
authorizes user requests to access a FactoryTalk-enabled system. These
175
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
security services are fully integrated into the FactoryTalk Directory and are
included as part of the FactoryTalk Services Platform that installs with many
Rockwell Software products.
FactoryTalk Transaction Manager User Interface
The user interface that you use to create, run, control, and monitor
FactoryTalk Transaction Manager configurations.
Generic OPC Control Connector
A service that moves data between the FactoryTalk Transaction Manager
service and an OPC-compliant server.
Local FactoryTalk Transaction Manager Computer
A computer that is running the FactoryTalk Transaction Manager user
interface.
Microsoft COM+ Enterprise Application Connector
A standard for designing distributed n-tier application systems. Microsoft
COM+ builds on standard COM, and incorporates new versions of tools
such as Microsoft Transaction Server (MTS) and Microsoft Message
Queues (MSMQ).
Microsoft OLE DB Enterprise Database Connector
A service that moves data between the FactoryTalk Transaction Manager
service and Microsoft SQL Server.
OCI
An acronym for Oracle Call Interface. OCI is an Application Programming
Interface (API) used for developing software that can interface natively to
Oracle databases.
ODBC
An acronym for Open Database Connectivity. ODBC is a widely accepted
API for database access that is based on the Call-Level Interface (CLI)
specifications from X/Open and ISO/IEC APIs and uses Structured Query
Language (SQL) as its database access language.
176
●
D ● Glossary
●
●
●
●
ODBC Enterprise Database Connector
A service that moves data between the FactoryTalk Transaction Manager
service and an ODBC-compliant database. The ODBC enterprise database
connector is currently written to the ODBC version 2.0 specification and
should support any ODBC driver that is version 2.0 compliant or greater.
OLE DB
A Component Object Model (COM)–based database architecture that
provides universal data integration over an enterprise network (from
mainframe to desktop) regardless of the data type.
Oracle OCI Enterprise Database Connector
A service that uses OCI to move data between the FactoryTalk Transaction
Manager service and an Oracle SQL*NET–compliant database.
Pending Edits
Changes made to data points or transactions in a configuration that uses
online edits. Pending edits must be saved before they can be assembled.
Pending edits do not affect the running configuration until they have been
assembled.
Pending Edit Alerts
Informational messages describing that transactions that have state
information will lose that state information when the associated data point or
transaction is assembled.
Remote FactoryTalk Transaction Manager Computer
A computer that is used to configure FactoryTalk Transaction Manager
services and configuration (.dat) files to run on another computer (local
FactoryTalk Transaction Manager computer). This computer communicates
directly with the Configuration Server, which then writes to the
configuration files. The FactoryTalk Transaction Manager user interface
does not run on this computer.
177
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
RSLinx Classic OPC Control Connector
A service that moves data between the FactoryTalk Transaction Manager
service and an RSLinx Classic server.
RSView32 Control Connector
A service that moves data from an RSView32 project to the FactoryTalk
Transaction Manager server in RSView32.
SQL
An acronym for Structured Query Language. SQL is an ANSI/ISO standard
language for querying, updating, inserting, deleting, controlling access to,
and defining storage containers for, data.
Table
In relational database terms, a unit of storage that contains columns of
specific names and data types and rows of those columns.
Tag
A collection of information for a single data point.
Time-series Data Compression Enterprise Database Connector
A service that compresses data from the control system using a lossless
algorithm to conserve space. This connector can be configured and used by
only FactoryTalk Historian Classic.
Transaction
An exchange of data between data points and a data object. Transactions
also include triggering information and other attributes that govern its
behavior. Transactions can be unidirectional or bidirectional.
Transaction Control Manager Service
The Transaction Control Manager is a service that controls and executes
FactoryTalk Transaction Manager transactions contained in a configuration,
but with the additional functionality of the FactoryTalk Live Data control
connector embedded in it. In an edit enabled configuration, the Transaction
Control Manager replaces the separate FactoryTalk Transaction Manager
and control connector services.
178
●
D ● Glossary
●
●
●
●
FactoryTalk Transaction Manager Service
A service that controls and executes FactoryTalk Transaction Manager
transactions contained in a configuration.
Transaction Result Binding
Implements a data transfer from the control system to the enterprise system
(and possibly back to the control system, logging a return code to the control
system that is bound to a data point and reports the success or failure of the
transaction). The control system can then take appropriate action based on
the success or failure of the transaction.
Transaction Result Code
A data value assigned to a transaction by FactoryTalk Transaction Manager
to communicate successful transaction completion.
UNC
An acronym for Universal Naming Convention. Unidirectional transactions
- Transactions that use information from the control system to add records to
a database table or to update the contents of existing records.
Unidirectional Transactions
Unidirectional transactions are commonly used to log production data to a
database and do not return data to the control system.
179
Index
Index
A
About FactoryTalk Security • 153
Activate Using EvRSI Activation • 32
Activate Using FactoryTalk Activation • 31
Activation • 30
Activation Options • 33
Adding New Data Points • 118
Assemble Pending Edits • 167
Assembling Data Point Pending Edits • 119
Assembling Pending Edits • 112
Assembling Transaction Pending Edits • 122
At FactoryTalk Transaction Manager Start Up •
160
Audit Trail • 167
Automate Data Logging • 13
B
Before You Begin • 27
Bidirectional or Unidirectional Transactions
With Transaction Bindings • 96
Bidirectional Transactions • 93, 100
Binding • 167
Bound Value • 167
Buffering In Cached Transaction Files • 133
Buffering In the Controller • 131
Buffering In the FactoryTalk Transaction
Manager Control Connector • 132
Buffering In the FactoryTalk Transaction
Manager Service • 133
Buffering In the Transaction Control Manager
Service • 132
C
Cached Transactions • 98
Canceling Data Point Pending Edits • 119
Canceling Pending Edits • 113
Canceling Transaction Pending Edits • 125
Changing the Error Log File Path • 131
Changing the Transaction Cache File Path • 131
Code Sample A (ComSampleVB) • 150
Code Sample B (ClientSampleVB) • 152
Configuration • 168
Configuration and Connector Status • 45
Configuration Checklist • 49
Configuration Server • 18, 68, 168
Configuration Server Status • 46
Configuration That Uses Online Edits • 168
Configuration Tree • 44
Configurations That Use Online Edits • 110
Configuring the Remote User Interface • 128
Consecutive Data Point and Data Block Support
• 75
Considerations When Using FactoryTalk
Transaction Manager With FactoryTalk
Security • 153
Contact Us • 25
Contents • 139
Control Connector • 168
Control Connectors • 18, 61
Control System • 134, 168
Control the Plant Floor Using Business Rules
and Quality Enforcement • 14
Creating a Configuration That Uses Online
Edits • 117
Creating a Distributed Configuration • 130
181
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
Creating the Client Application • 144
Creating the Microsoft COM+ Setup Program •
147
Creating the Remote Component • 143
Creating Transactions • 91
D
Data Object • 169
Data Point • 169
Data Point Buffering • 131
Data Point Range and Advanced Functions •
104
Data Retrieval Timeout • 77
Data Valid • 76
Database • 135
Database Triggers • 100
Database View • 169
DDE • 62
DDE Control Connector • 169
DDE Data Points • 82
Defining Data Objects • 83
Defining Data Points • 71
Defining the COM+ Data Object • 149
Defining the COM+ Enterprise Application
Connector • 148
Device Scheduled
Request the Current Value From the Device
• 74
Distributed Configurations • 129
Distributed FactoryTalk Transaction Manager
Installations • 38
DSN • 169
E
Editing Data Points In a Running Configuration
That Uses Online Edits • 117
Editing Existing Data Points • 118
182
Editing Transactions In a Running
Configuration That Uses Online Edits • 121
Enterprise Application Connectors • 66
Enterprise Application Objects • 86
Enterprise Connector • 169
Enterprise Connector Error Handling • 87
Enterprise Connector Options • 67
Enterprise Connectors • 18
Enterprise Database Connectors • 65
Enterprise Database Objects • 85
Establishing Microsoft Windows Privileges •
130
Exploring Advanced Topics • 127
Exploring the FactoryTalk Transaction
Manager User Interface • 39, 40
Expression Editor • 102, 170
External Trigger Sample Application • 139
F
FactoryTalk • 19
FactoryTalk Administration Console • 21
FactoryTalk Audit and FactoryTalk Diagnostics
• 21
FactoryTalk Directory • 20
FactoryTalk Live Data • 20, 62
FactoryTalk Live Data Data Points • 73
FactoryTalk Metrics • 66
FactoryTalk Metrics Data Objects • 87
FactoryTalk Metrics Enterprise Application
Connector • 170
FactoryTalk Security • 21, 170
FactoryTalk Services Platform Components •
20
FactoryTalk Transaction Manager • 135
FactoryTalk Transaction Manager and
Microsoft COM+ Objects • 143
●
●Index
●
●
●
●
FactoryTalk Transaction Manager Behaviors
When the FactoryTalk Security Single Sign-on
User Is In Effect • 159
FactoryTalk Transaction Manager Demo • 34
FactoryTalk Transaction Manager Lite • 34
FactoryTalk Transaction Manager Sample
Applications • 139
FactoryTalk Transaction Manager Service • 68,
173
FactoryTalk Transaction Manager Service and
Control Connectors • 17
FactoryTalk Transaction Manager Trial • 34
FactoryTalk Transaction Manager User
Interface • 170
From the FactoryTalk Data Point Dialog Box •
113
From the Main FactoryTalk Transaction
Manager User Interface • 112
From the Pending Edit Alerts Dialog Box • 113
From the Pending Transaction Definition
Dialog Box • 113
G
Generic OPC • 64
Generic OPC Control Connector • 170
Generic OPC Data Points • 81
Get Consulting Services • 25
Get Phone Support • 24
Get Web Support • 24
Glossary • 167
Grace Period • 32
H
Hardware and Operating Environment • 136
Hardware Requirements • 27
How Does a Pending Edit Alert Occur? • 114
I
Including the COM+ Enterprise Application
Connector In a FactoryTalk Transaction
Manager Configuration • 148
Increasing Performance • 134
Inserting and Updating Data Table Records • 89
Installing FactoryTalk Transaction Manager •
27
Installing FactoryTalk Transaction Manager
Software • 36
Installing the Remote Component • 145
Intended Audience • 21
Introducing Advanced Topics • 127
Introducing Data Objects • 83
Introducing Data Points • 71
Introducing FactoryTalk Transaction Manager
and Microsoft COM+ Objects • 143
Introducing FactoryTalk Transaction Manager
Services • 61
Introducing Online Edits • 107
Introducing Transactions • 91
L
Learn More About Current and Pending Edits •
111
Licensing Required For a Distributed
Configuration • 129
Local FactoryTalk Transaction Manager
Computer • 170
Logical and Mathematical Operations • 103
M
Manage Recipes • 14
Map Old Product-Specific Security Privileges
To the New FactoryTalk Security Permissions •
164
183
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
Menu Bar • 42
Microsoft COM+ • 66
Microsoft COM+ Data Objects • 86
Microsoft COM+ Enterprise Application
Connector • 170
Microsoft OLE DB • 66
Microsoft OLE DB Enterprise Database
Connector • 171
Microsoft SQL Server Data Objects • 85
Miscellaneous • 54
Monitoring Configurations • 57
Moving the Client Sample Application • 147
O
OCI • 171
ODBC • 65, 171
ODBC Data Objects • 86
ODBC Enterprise Database Connector • 171
OLE DB • 171
Online Edits Workflow • 108
Online Help • 22
OPC Data Points • 80
Oracle Call Interface (OCI) Data Objects • 85
Oracle OCI • 65
Oracle OCI Enterprise Database Connector •
171
Overview • 159
P
Parse Function • 104
Pending Edit Alerts • 114, 172
Pending Edits • 172
Preventing Stale and Mismatched Data • 79
Product Manual • 23
184
R
Real-time Transactions • 98
Remote FactoryTalk Transaction Manager
Computer • 172
Remote User Interface • 127
RSLinx Classic OPC • 63
RSLinx Classic OPC Control Connector • 172
RSLinx Classic OPC Data Points • 81
RSView32 • 64
RSView32 Control Connector • 172
RSView32 Data Points • 81
Running the Application • 140
S
Saving Data Point Pending Edits • 119
Saving Transaction Pending Edits • 122
Scenario 1
You Have a Windows-linked User Account
• 160, 162
Scenario 2
You Do Not Have a Windows-linked User
Account • 163
You Have a FactoryTalk User Account and
Are Logged Into the FactoryTalk Directory •
161
Scenario 3
You Do Not Have a Windows-linked User
Account • 161
Scheduled
Maintain the Current Subscribed Value • 74
Securing FactoryTalk Transaction Manager
Using FactoryTalk Security • 153
Selecting a Collection Mode • 74
Selecting a Substitution Option • 78
Selecting Timeout Properties • 76
Setting Up the Remote Client • 146
Software Compatibility • 30
●
●Index
●
●
●
●
Software Requirements • 28
Specify FactoryTalk Security Permissions That
Allow You To Perform FactoryTalk
Transaction Manager Tasks • 156
Specifying Quality • 79
SQL • 172
Starting and Stopping Connectors • 56
Starting Configurations • 55
Starting FactoryTalk Transaction Manager • 39
Status Bar • 48
Step 1
Defining and Naming a New Configuration
• 51
Step 2
Defining Connectors • 52
Step 3
Defining Data Points • 52
Step 4
Defining Data Objects • 53
Step 5
Defining Transactions • 53
Step 6
Verifying Transactions • 54
Stopping Configurations • 56
Stored Procedures • 89
Summary • 35
T
Table • 173
Tag • 173
Technical Support • 23
Time Functions • 103
Time-series Data Compression • 66
Time-series Data Compression Enterprise
Database Connector • 173
Title Bar • 41
Toolbar • 43
Training • 23
Transaction • 173
Transaction Completion • 98
Transaction Control Manager Service • 15, 68,
173
Transaction Result Binding • 173
Transaction Result Code • 174
Transaction States • 47
Transaction Timeout • 98
Transaction Types • 92
Transactions • 19
Transactions With Bound Transaction Results •
100
U
UNC • 174
Understanding FactoryTalk Transaction
Manager Concepts • 14
Understanding FactoryTalk Transaction
Manager External Files • 57
Understanding FactoryTalk Transaction
Manager Services • 61
Understanding Online Edit Concepts • 107
Understanding Online Edits • 107
Unidirectional Transactions • 93, 174
Unscheduled
Send Subscribed Value Whenever It
Changes • 75
Using the Service Console • 59
Using UNC Paths • 130
V
Viewing Configuration Properties • 54
Viewing Transaction Differences • 123
185
●
●
●
FactoryTalk Transaction Manager User Guide
●
●
W
Welcome To FactoryTalk Transaction Manager
• 13
What Can FactoryTalk Transaction Manager
Do For Me? • 13
What Is FactoryTalk Transaction Manager? • 13
When Using FactoryTalk Transaction Manager
• 162
Where Can I Go For Help? • 22
Workspace • 47
Writing Product-Specific Security Privileges
From a Previous Release To a File • 163
186
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement