Rockwell Automation RSBizWare Administration Guide - Manual (Page 293)

Application notes for FactoryTalk Transaction Manager Appendix D
net start rssql_cfg_server
Additionally, if you want to stop the FactoryTalk Transaction
Manager service in the FactoryTalk Transaction Manager from a
DOS command prompt, type the following:
net stop rssql_tb
You can distribute FactoryTalk Transaction Manager control and
enterprise connectors among several computers. Keep the following
points in mind when distributing FactoryTalk Transaction Manager
connectors on multiple computers:
• UNC paths for configuration files cannot be used. The
configuration files must be local to the Configuration Server.
The configuration file path is defined in Step 1 of the
Configuration Checklist in FactoryTalk Transaction
Manager.
• FactoryTalk Transaction Manager must be logged into a
Windows Server 2012/2008/2003 account that has
administrative privileges in all computers that are part of the
FactoryTalk Transaction Manager system. This is required for
the Windows Server 2012/2008/2003 service control manager
to be able to start and stop the FactoryTalk Transaction
Manager services.
• The FactoryTalk Transaction Manager configurations that
you create must use cache file paths and error logging paths
that comply with the Universal Naming Convention (UNC).
Each time you define a FactoryTalk Transaction Manager
control connector or enterprise connector, you must indicate
the host name of the remote computer on which that service
will run. Additionally, you must assign that service to a user
account with sufficient privileges to access UNC files on the
applicable computers.
• If you have defined a connector to run on a remote computer,
FactoryTalk Transaction Manager v9.00.00 or later will
Considerations for
distributed configurations
Rockwell Automation Publication BZWARE-IN001M-EN-P-June 2014 293