Example: Two directory scopes on one computer

Different software products have different requirements for the

FactoryTalk Directory

scope. Both directory scopes are installed and configured as part of installing the

FactoryTalk Services Platform

. The directory scope needed depends upon which software products are used and whether working in a standalone or a networked environment.

For example, if using

FactoryTalk View SE

or

FactoryTalk Transaction Manager

, use the network directory scope to create and manage network applications. If using

FactoryTalk View ME

, use the local directory scope to create and manage local applications. Other products, such as

RSLogix 5

,

RSLogix 500

, and

FactoryTalk Linx

, allow using either directory scope.

Even though a local directory scope and a network directory scope reside on the same computer, all of their project information and security settings remain completely separate and cannot be shared, including:

The graphic below shows three computers. Each computer has both a local directory scope and a network directory scope configured. Each directory scope holds objects, which represent project information, such as applications, references to data servers, and security settings, including user accounts. In each local directory scope, access to these project objects is only by software products installed on that same local computer. The network directory scope, however, can share references to its objects across a network.

For example, suppose each colored icon above represents the project information and security settings that are part of a

FactoryTalk

system. The local directory scopes on each computer hold completely separate sets of information (represented by the green, blue, and yellow icons). In the network directory scope case, all client computers that point to the same network directory scope server computer share the same set of information across the network (represented by the orange icons).

Run

FactoryTalk Administration Console

on Computer 3, log on to the network directory scope, and create a user account named "Terry" with the password "OpenSesame." The change is actually made in the network directory scope server, held on Computer 1, and immediately reflected on each network directory scope client computer. "Terry" can now log on to the network directory scope from any of the three computers.

Now create a user account named "Terry" with the password "OpenSesame" in each Local Directory scope on every computer. Even though the username and password are the same, each user account is a separate object in each local directory scope.

When changing the password in the local directory scope on Computer 1, the change does not affect the user account held in the network directory scope server on the same computer, nor does it affect the user accounts held in the local directory scopes on computers 2 and 3.