7 ) ,.

8# # . # 7
) ,9

Background

! The FactoryTalk Services Platform (FTSP) is installed on one

! " or more Microsoft Windows-based computers to create a
! # FactoryTalk system. Click here for a list of Rockwell
$ % !&% ' Software products that currently leverage the FactoryTalk
(
Services Platform. Note: The FactoryTalk Services Platform
& was formerly known as the FactoryTalk Application Platform
)* & + , (FTAP).
* $
( * $ ) &- $% , In every FactoryTalk system, one computer must be
designated as the FactoryTalk Directory (FTD), and there are
( . #
currently two types of FactoryTalk Directories:

1: A Local FactoryTalk Directory (Local FTD) is typically

used in a single (standalone) computer system. The
/0120/ 3 24
Local FTD may or may not be connected to a Local
Area Network (LAN).
01 0/ 3 456
/: A Network FactoryTalk Directory (Network FTD) is
$
designed primarily for use with a multiple (distributed)
computer system and it is normally connected to a
LAN. Any other computers in the FactoryTalk system
are clients to the designated Network FTD. Note: It is
also possible to have a single computer system act as a
Network FTD, but this configuration is atypical.

For more information on the differences between a Local

FactoryTalk Directory and a Network FactoryTalk Directory,
open the FactoryTalk Help (All Programs > Rockwell
Software > FactoryTalk Tools > FactoryTalk Help) and select
the topic 'What is a FactoryTalk System?' from the Contents
tab.

The FactoryTalk Directory is the centerpiece of the

FactoryTalk Services Platform. FactoryTalk Directory
provides a central lookup service for all products participating
in an application. The role of the FTD in the Rockwell
environment is analogous to the role of a Domain Controller
in the Microsoft Windows environment.

Network FactoryTalk Directory Best Practices

The remainder of this document will focus solely on the role

of the Network FTD and address Best Practices for design and
management/maintenance.

Design
When designing FactoryTalk systems, it is highly
recommended that:

1: the role of the Network FTD be hosted on a dedicated

computer. This recommendation applies mainly to
FactoryTalk systems that utilize redundancy.
Redundancy is available with Data Servers, View SE
HMI Servers, Historian SE interfaces and - coming
soon - FactoryTalk Alarm & Events Servers. Ideally,
both the primary and secondary servers will always
have access to the Network FTD to insure consistent
switchover.

Additionally, a dedicated Network FTD is also an ideal

location for the following roles that are typically
present in a FactoryTalk system:

• FactoryTalk Activation Server

• CentralizedFactoryTalk Diagnostics Repository
(using SQL Server database)
• FactoryTalkAlarms and Events Historical Log
(using SQL Server database)

/: a server operating system (2000, 2003 Server) is used.

A server OS is optimized to service network requests,
which is a common function of a Network FTD.
However, this server should not be a Windows domain
controller.

Note: There are exceptions to both of these recommendations,

such as small, non-redundant FactoryTalk Historian SE and
View SE systems, and dedicated FactoryTalk AssetCentre
systems.

While these recommendations typically result in additional

initial cost (i.e., hardware, OS licensing, etc), these costs are
typically offset by the long term savings associated with
increased system performance and manageability. Also keep
in mind that the Network FTD does not typically require a
high-end server or even a large amount of memory, although
the use of redundant disks (RAID) is generally a best practice
to prevent the loss of the Network FTD due to disk failure.

Management/Maintenance

When managing and maintaining FactoryTalk systems, it is

highly recommended that:

1: the computer hosting the Network FTD be highly

available. All of the computers in a FactoryTalk system
contact the Network FTD when they boot, and maintain
periodic communications afterwards. Therefore, if the
FactoryTalk system is shutdown for maintenance or
 upgrade, the Network FTD should be the last computer
shutdown and the first to be restarted.
/: the computer hosting the Network FTD never be
renamed. All of the computers in a FactoryTalk system
only know the Network FTD by name (vs. IP address),
so if the name changes, the clients will be unable to
communicate with the Network FTD.
: the Network FTD be periodically backed up to a .BAK
file. This is currently a manual task performed using the
FactoryTalk Administration Console. Refer to
'Choosing the correct backup and restore options' in the
FactoryTalk on-line Help for additional information.
Note: A periodic complete system backup is a preferred
alternative to creating only the .BAK file, especially if
the Network FTD is also a FactoryTalk Activation
Server.

Refer to the FactoryTalk on-line Help for additional

information on the FactoryTalk Services Platform and the
FactoryTalk Directory.

# % ; ; % % - % #
- & &;< &;< % =# &
& # &;< :! % > # # ;
% % & -- >% > #
- % :. %
> # # # & ?& - > & # &% &
?& %- % :

(@ " A8 $'' !B @ ! @ 7 @ $ 7 @ 8 !((!7 $ "@ '$ $7 $ >

$' 7 $ @ ( !" " B (!" C @ !7 C @ $ ! ! "@ 7 ! 7 $ 7 8 $.
$ !7 !C !A$ " !7 $ $($ @ ! !7 C $ 7 @ '$
" ($ @ 7 8 @B 7@ "$: B ( $(> !'' 7 @ ( ! @ 7 " @ 7 *$C$
$($.C (@ * $ @ B $( D! :D 7 7 @ $*$7 !'' (@ " A8 $'' .$
' !.'$ @ ( !7 C ! ! $ @ !7 C A 7 7 " 'B 7 ($" > 7 ($" >
7 " $7 !'> "@ 7 $E B $7 !'> '@ (@ @ ( ! ! $> $*$7
(@ " A8 $'' !B @ ! @ 7 !*$ .$$7 ! * $ @ 7 $ @ .' C@
B" ! ! $ :

(@ " A8 $'' !B @ ! @ 7 "'! !'' 8 !((!7 $ 8 $ $(

$F ($ $ @ ( ' $ 7 ($ $" @ $ 7 @ ( ! @ 7 ) 7 " 'B 7
@ 8 !($, (@ * $ $($.C> 7 " 'B 7 $ ' $ 8 !((!7 $ @
7$ @ ( ! !( " B '!( B ( @ $> $(" !7 !. ' C> !7 7 @ 7 G
7 ( 7 $ $7 : 7 # <& % % & #
= & - % H #& > # % --
&:

" - # I/ 2G/ ( !& :! # %: