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

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