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

●
●
●
●
●
FactoryTalk Transaction Manager User Guide
134
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.