Professional Documents
Culture Documents
CONTENTS
1 Overview ........................................................................................................... 1
Other Information Sources.............................................................................................................
Training Programs .....................................................................................................................
Knowledgebase ..........................................................................................................................
Consulting Services ...................................................................................................................
1
2
2
2
3
3
3
3
4
4
4
4
20
20
20
20
21
21
22
22
23
23
23
23
25
25
25
26
26
26
26
26
27
27
27
27
28
28
28
28
33
33
34
34
ii
41
41
41
43
44
46
48
49
51
53
56
57
57
58
59
59
59
59
60
iii
Contents
iv
CHAPTER 1
Overview
FactoryTalk Historian Site Edition (SE) provides the capability to collect, store, analyze,
and visualize data using a powerful engine and a set of reporting tools such as time-series
trends, bar charts, piecharts, pareto and tabular trends, and a method of generating reports
using Microsoft Excel. It also uses compressed-storage data algorithms to contain a vast
amount of data in a small format.
FactoryTalk Historian SE is closely integrated with FactoryTalk Services Platform and the
following Rockwell Automation applications:
FactoryTalk Live Data (FTLD): A direct data interface to FTLD delivers native
FTLD data directly to FactoryTalk Historian SE without requiring intermediate
interfaces and standards such as OPC.
FactoryTalk View SE Trending: FactoryTalk View Site Edition natively trends data
from FactoryTalk Historian SE.
Training Programs
Rockwell Automation offers a wide range of training programs, from regularly scheduled
classes to custom-tailored classes conducted at your site.
If you would like more information about these training programs, visit the Rockwell
Automation site on the Web at http://www.rockwellautomation.com/support/, or call
1.440.646.3434.
Knowledgebase
The Rockwell Automation Customer Support Center offers an extensive online database
that includes frequently asked questions and the latest patches.
Please visit http://www.rockwellautomation.com/support/, and select Knowledgebase
under Self-Service Support.
Consulting Services
Rockwell Automation provides expert consulting and turnkey implementations for
making optimal use of Rockwell Software products. Please contact your local distributor
for more information.
CHAPTER 2
RSLinx Enterprise
The following diagram shows an example of a network layout for a distributed system
using all of these software products.
Use this diagram only as an example; your own distributed system may vary.
(Optional) FactoryTalk View Site Edition Client and FactoryTalk View Site Edition
Updates on the same computer.
Note: Install FactoryTalk View Site Edition Updates on the same computer on which
you install FactoryTalk View Site Edition.
RSLinx Enterprise and FactoryTalk Historian Live Data Interface on a computer other
than the FactoryTalk Historian SE server computer.
Note: Configure the buffer subsystem on the same machines on which you install
FactoryTalk Historian Live Data Interface.
CHAPTER 3
FactoryTalk Live Data: Manages connections between FactoryTalk products and data
servers. It reads values from and writes values to OPC-DA servers (OLE for Process
Control - Data Access) and FactoryTalk Live Data Servers on behalf of client software
products, such as FactoryTalk View.
FactoryTalk Diagnostics: Collects and provides access to activity, status warnings, and
error messages generated throughout a FactoryTalk system.
FactoryTalk Administration Console: Provides a method of configuring, managing, and
securing applications.
For more information on FactoryTalk, refer to FactoryTalk Help. You can access it from
Start > Programs > Rockwell Software > FactoryTalk Tools > FactoryTalk Help after
you have installed FactoryTalk Services Platform on your machine.
FactoryTalk Historian Site Edition Management Tools: This option installs AF, APS,
DAS, and SMT.
FactoryTalk Historian Site Edition Interface Configuration Utility: This option
installs the ICU.
FactoryTalk Historian Site Edition Live Data Interface: This option installs the
FactoryTalk Historian Live Data Interface, AutoDiscovery, and Rule Editor. The
FactoryTalk Historian Live Data Interface is a FactoryTalk Live Data client that enables
process data to be passed between a FactoryTalk Live Data Server and a FactoryTalk
Historian SE Server.
10
2. On all the other computers, run the FactoryTalk Historian SE Install DVD. From the
installation screen, click Specify FactoryTalk Directory Server Location. On the
FactoryTalk Directory Server Location Utility screen, click the browse button (...) to
select the name of the computer that you specified as FactoryTalk Directory computer
(the previous step). Once selected, click OK, and then restart the computer.
Note: On the computers that have FactoryTalk Services Platform installed, the Specify
FactoryTalk Directory Server Location Utility screen can also be launched from Start >
Programs > Rockwell Software > FactoryTalk Tools > Specify FactoryTalk Directory
Location.
11
12
3. On the Company Information screen, enter the user name, organization, and serial
number. Click Next to continue.
4. On the Setup Type screen, select FactoryTalk Historian Server Installation, and
then click Next. This option installs all of the components. For more information, see
FactoryTalk Historian Site Edition Server Install.
5. On the InstallShield Wizard Completed screen, clear the Specify FactoryTalk
Directory Location and FactoryTalk Activation Server check boxes (you already
set the FactoryTalk Directory and installed the FactoryTalk Activation Server).
6. Leave the FactoryTalk Activation Client option selected, and then click Finish. This
will launch the FactoryTalk Activation Client install. You need to install the
Activation Client software so you can use the Factory Activation Tool to activate the
FactoryTalk Historian SE Server software.
Steps to Install FactoryTalk Activation Client
1. On the installation screen, click Install FactoryTalk Activation Client.
2. On the Welcome to the InstallShield Wizard screen, click Next.
3. On the Customer Information screen, enter the user name and organization, and then
click Next.
4. On the Setup screen, keep the default settings, and then click Next.
5. On the Ready to Install Program screen, click Install.
6. On the InstallShield Wizard Completed screen, click Finish.
Steps to Get Activation from FactoryTalk Activation Server
Note: You must perform this section on all the client computers that have FactoryTalk
Activation Client installed.
1. From Start > Programs > Rockwell Software > FactoryTalk Activation >
FactoryTalk Activation Tool launch the FactoryTalk Activation Tool dialog box.
2. On the Activation Tool dialog box, click the Current Activations tab, and verify that
you have no current activations.
3. Click the Settings tab.
4. On the Settings tab, click the + icon as shown in the following figure. Clicking the
+ icon introduces a browse button.
5. Click the browse button to launch the Browse for Folder dialog box.
6. Browse to the computer on which you installed FactoryTalk Activation Server, and
select it to add it to the list.
7. Click the Current Activation tab to verify the activations were added from the server.
13
IMPORTANT! Once you have installed FactoryTalk Historian SE Server and moved
activations to it from the FactoryTalk Activation Server, follow the steps described in
Verify the FactoryTalk Historian SE Server is Running to make sure the FactoryTalk
Historian SE Server is functioning properly.
14
15
10. From the Tools menu, select the Tag Search option. The Tag Search dialog box
displays.
11. Use the default settings in the Tag Search dialog box and click Search.
12. From the list of tags that appears in the search results, select one of the tags, and click
OK. This displays the current value of the tag.
16
6. Verify that the system returned archived values, and close the System Management
Tools.
Steps to Enable Buffering
The buffering subsystem stores time-series values to memory when the remote interface
computer cannot communicate with the FactoryTalk Historian SE Server. To enable
buffering on the interface computer, use the following procedure:
Note: FactoryTalk Historian SE only supports the PI Buffer Subsystem and not the API
(BufServ) buffering.
1. Start the System Management Tools from Start > Programs > Rockwell Software >
FactoryTalk Historian SE > System Management Tools.
17
2. In the System Management Plug-Ins pane, click the Security folder, and then select
the Trusts sub-folder, as shown in the following figure
3. Verify that PIBuffSybSystemService is listed in the Trusts column of the Trusts table,
as shown in the following figure.
4. Exit the System Management Tools by selecting File > Exit from the main menu.
5. Launch the Interface Configuration Utility from Start > Programs > Rockwell
Software > FactoryTalk Historian SE > Interface Configuration Utility.
6. From the Interface list on the Interface Configuration Utility dialog box, select the
Remote Interface name.
7. From the Interface Configuration Utility main menu, select Tools > Buffering.
8. On the Buffering dialog box, select the Choose Buffer Type option, and then select
the Enable buffering with PI Buffer Subsystem option (right pane), and click Yes
on the confirmation message that displays. Wait until the status box displays Current
Configuration: Good.
Note: If you delete an interface and recreate the interface (with the same id) on
another computer, you will get errors unless you restart the computer on which the
deleted interface was located. Restarting ensures restart of the buffering subsystem.
As a general rule, you must always disable buffering on the interface before you delete
it. If you forget to disable buffering, you will have to restart the computer to make sure
the buffering subsystem is restarted.
18
9. Select the Buffered Servers section option from the left pane. This will open up on
the right pane the options for the Buffered Servers section. From the Buffering to
collective/server drop-down menu, select the name of the computer on which the
Remote Interface is installed, and then click Yes to the confirmation message.
10. Click OK to close the Buffering dialog box.
11. From the list on the Interface Configuration Utility dialog box, select Service, as
shown in the following figure.
In the Dependencies list, add the PIBufss service from the list of Installed Services. It is
important to add PIBufss as a dependent service to make sure your interface always starts
after the buffering service starts.
IMPORTANT! If the interface starts before the buffering subsystem, data will be lost.
12. After adding PIBufss as a dependent service, restart the interface from the Restart
Interface Service option on the toolbar.
13. Verify that the Status Bar (at the bottom of the dialog box) shows status as Ready and
Running.
14. Click Close to exit the Interface Configuration Utility dialog box. The buffering
service is now configured.
19
Follow these steps in the order they are listed to upgrade from FactoryTalk Historian SE
2.0 to FactoryTalk Historian SE 2.1. Each step is described in the sections that follow.
1. Steps to Stop Services and Processes
2. Steps to Upgrade FactoryTalk Services Platform (optional)
3. Steps to Upgrade FactoryTalk Activation Server and Client (optional)
4. Steps to Upgrade RSLinx Enterprise (optional)
5. Steps to Back Up Your 2.0 Database
6. Steps to Upgrade FactoryTalk Historian ActiveView
20
21
For more information on the upgrade process of FactoryTalk Services Platform, refer to
FactoryTalk Help, available from Start > Programs > Rockwell Software > FactoryTalk
Tools > FactoryTalk Help.
1. On the installation screen, click Install RSLinx Enterprise. The install will check for
the current version of the RSLinx Enterprise installed on the computer and display a
message. Click OK to continue the upgrade process, or click Cancel to cancel the
upgrade.
Note: You will be prompted to cancel out of the installation if you already have the
correct version installed.
On the License Agreement screen, read the end-user license agreement select I
accept the terms of the license agreement, and then click Next.
4. On the Customer Information screen, enter the user name and organization, and
click Next.
22
5. On the Setup screen, keep the default settings, and then click Next.
6. On the Ready to Install Program screen, click Install.
7. On the InstallShield Wizard Completed screen, click Finish.
23
24
CHAPTER 4
Note: If you are installing FactoryTalk Historian DataLink on a computer that has
FactoryTalk Historian Interface or FactoryTalk Historian SE Server installed, in the SMT
and MDBBuilder folders you will see the following two files: PITagCnf.xla and
MDBBuilder.xla. These files are required to create the PI-SMT menu in MS Excel.
25
26
Install ActiveView
1. On the installation screen, click Install FactoryTalk Historian ActiveView.
2. On the Welcome screen, click Next.
3. On the End User License Agreement screen, select I accept the terms of the
agreement, and then click Next.
4. From the Setup Type screen, select Typical.
5. When the installation is complete, restart your computer.
6. Launch the Internet Information Services Manager application from Start >
Programs > Administrative Tools > Internet Information Services (IIS) Manager.
7. In the IIS main window, in the left pane, you will see the name of your local computer,
right-click the name, and from the list, select Properties.
8. On the Properties dialog box, click MIME Types.
9. On the MIME Types dialog box, click New.
10. In the MIME Type New dialog box, in the Extension field, enter the following
information:
Extension: .pdi
28
CHAPTER 5
Important: By default, FactoryTalk Security allows any user to change their privilege
level to any level, including administrative levels. For information on tightening
29
security, see FactoryTalk Security Quick Start, available from Start > Programs >
Rockwell Software > FactoryTalk Tools > FactoryTalk Security Quick Start.
30
CHAPTER 6
Message Parameters
Each message logged to the FactoryTalk Diagnostics service contains the following
information:
Date/Time - This is the date and time the message was recorded. The time is the local
time for the server. This is important to note if you are in a different time zone than the
server.
User Name - This is the name of the user that performed or requested an operation
that generated the error message.
Note: If you plan to track user IDs in FactoryTalk Diagnostics for auditing purposes, you
must create identical user IDs in the FactoryTalk Historian SE Server. See the FactoryTalk
Historian System Management User Guide for information on creating user IDs in the
Historian Server.
Location - The name of the computer where the diagnostic message was generated.
Provider - The name of the FactoryTalk product or subsystem that generated the
message.
View Messages
To view the messages in FactoryTalk Diagnostics, run the FactoryTalk Diagnostics Viewer
tool. See the FactoryTalk Diagnostics Viewer Help for more information on how to use the
Viewer to search and filter messages.
31
To view messages stored in the Windows Event log, click Start > Settings > Control
Panel > Administrative tools > Event Viewer.
32
CHAPTER 7
3. After the wizard completes the point discovery, it prompts you to start the Data
Collection Interface Service to start collecting the data points in the FactoryTalk
Historian SE server.
33
For more information on the Rule Editor, refer to the FactoryTalk Historian SE
Discovery Rule Editor topic in the FactoryTalk Historian SE Help. It can be accessed by
clicking the Help icon on the Edit Discover Rules dialog box.
This local interface is configured to start collecting data points from any data servers that
are available to the FactoryTalk Historian SE server.
IMPORTANT! You can use the local interface for data collection; however, we strongly
recommend that you create a remote interface on the computer that has the data
server installed. Buffering, which ensures that loss of data does not occur, can only be
enabled on a remote interface. To learn more about buffering, see Steps to Enable
Buffering.
34
CHAPTER 8
The FactoryTalk View SE Patch Roll Up is installed on all FactoryTalk View Client
computers. This is required if you are using FactoryTalk View SE TrendX to visualize
FactoryTalk Historian SE data. The FactoryTalk View SE Patch Roll Up is available
through the Rockwell Automation Knowledgebase located at http://
www.rockwellautomation.com/knowledgebase/.
Note: Select the FactoryTalk Historian Site Edition Management Installation option and
install on all FactoryTalk View Client and Studio Computers to support using TrendX with
FactoryTalk Historian SE 2.1.
35
Real-time data server: Retrieves data from the snapshot subsystem. This option
is preferred for points that change infrequently like setpoints.
Poll historical data: Retrieves data from the archive files. This option is
preferred for points that change faster than a second.
8. On the Pens tab of the Trend Properties dialog box, select Historian Server from
the Pen Source field.
Note: The fields on the TrendX object tab are explained in detail in the FactoryTalk
View SE Help. Click Help on the TrendX object dialog box for information on those fields.
6. Click Remove All to remove all the tags in the list. A confirmation dialog box
displays. Click OK to remove all tags.
36
CHAPTER 9
Configure a Collective
A collective consists of two FactoryTalk Historian SE servers that have the same
configuration database. This provides the same association between the key values in the
FactoryTalk Historian SE tables on all of the servers. This also ensures that the archive
data files have the same structure on all of the servers. You can also create a collective
with only one server.
Collectives Information
When working with collectives, keep the following in mind:
When creating collectives, you must always use fully qualified hostnames, not IP
addresses.
The FactoryTalk Historian SE servers must be members of the same network domain
in a collective.
Activate the FactoryTalk Historian SE servers individually before you make them part
of a collective. You cannot activate a collective individually. To activate a FactoryTalk
Historian SE server, see Steps to Get Activation from FactoryTalk Activation Server
To create a collective on computers that have Windows Firewall turned on, you must
manually open Port 445 between the two computers. To open the port, follow these
steps:
a. Go to Start > Settings > Control Panel.
b. In the Control Panel window, click Windows Firewall.
c. In the Windows Firewall dialog box, click the Exceptions tab.
d. On the Exceptions tab, select the File and Printer Sharing checkbox (Programs
and Services list), and then click Edit.
e. In the Edit a Service dialog box, select the checkbox next to TCP 445, and then
click OK.
f.
Prerequisite: Install and activate all FactoryTalk Historian SE servers before you make
them part of a collective. If you are installing FactoryTalk Historian SE 2.1 for the first
time, see Steps to Install FactoryTalk Historian SE 2.1 for more information. If you are
an existing customer, see Steps to Upgrade to FactoryTalk Historian SE v2.1.
37
Create a Collective
1. Click Start > Programs > Rockwell Software > FactoryTalk Historian SE >
FactoryTalk Historian SE System to open the Collective Manager.
2. From the main menu, select File > Create New Collective. This launches the Create
New Collective wizard.
3. On the Create New Collective dialog box, select both I have verified my backups
are valid and I have verified my interface servers configuration options and then
click Next.
4. On the Existing or New Primary dialog box, select one of the following:
An existing server that contains historic data if you are adding an existing FactoryTalk
Historian SE server to a collective
Click Next
5. On the Select Primary and Collective name dialog box, in the Collective Primary
field, enter the name of the server you want to make the primary server. If you do not
know the name of the server, click the browse button (...) to select a server from the
list. In the Collective name field, enter the name of the collective.
6. On the Select Secondary Servers dialog box, click the browse button to select the
secondary servers you want to add, and then click Add. Click Next.
7. On the Select Archives dialog box, you will see the list of archives on your primary
server. From the list, select the archives you want copied to your secondary server. We
recommend you back up all your primary server archives onto your secondary server.
Click Next.
8. On the Select Backup Location dialog box, click the browse button to browse to the
location where you want your primary servers content to be backed up. Verify that the
Space Available field is showing more space than the Required Space field.
9. On the Verify Selections dialog box, verify the name of the collectives, primary
server, and secondary server(s). Click Next. The Conversion progress dialog box
appears. It displays the steps running in the background to create the collective.
38
10. On the Server ID Mismatch dialog, select Accept the new ID, and then click OK as
shown in the following image.
11. On the last screen, click Finish. The Collective Manager window displays the name
of the collective.
For more information on collectives, refer to the Collective Manager Help. On the
Collective Manager window, select Help > Contents. FactoryTalk Historian SE High
Availability and Replication also contains information about collectives.
39
9 Configure a Collective
40
CHAPTER 10
Prerequisites
A FactoryTalk Historian SE system with interface redundancy requires the following:
Note: When you configure a FactoryTalk Historian SE Server, a FactoryTalk Historian Live
Data Interface with the name FTLD1 is created. Before you create a new interface, you
must delete the FTLD1 interface. To read about the FTLD1 interface, see FactoryTalk
Historian Live Data Local Interface.
A location to store the shared file that will be used for failover communication
between the primary and backup interfaces. That is, data will be written to and
retrieved from this shared file. We strongly recommend that you put this file on a
dedicated file server (for example, the FactoryTalk Directory server) that has no
other role in data collection.
41
4. Click Save to save the newly added collective server. Click Close.
5. From the Interface Configuration Utility menu bar, select Tools > Options.
6. In the Options dialog window, click the radio button next to Load interfaces from a
selected list of PI servers.
7. Check the box next to the newly loaded interface (below the Load interfaces from a
selected list of PI servers), and then click OK.
8. From the Interface Configuration Utility menu bar, select Tools > Buffering.
42
9. In the Buffering dialog window, click the radio button next to Enable buffering with
PI Buffer Subsystem. Click Yes on the confirmation message that displays. Wait until
the status box displays Current Configuration: Good.
10. From the left pane, click Buffered Servers, and then select the name of the
FactoryTalk Historian SE from the Buffering to collective/servers drop-down list
(right pane).
43
displayed. In the Enter the object names to select textbox, enter the name of the
windows domain user, and then click OK to return to the Permissions dialog box.
6. On the Permissions dialog box, select the windows domain user you added, and then
click the Full Control, Change, Read checkboxes in the Allow column to give
permissions to the domain user.
7. Click Apply to save the changes, and then click OK to close the dialog box.
3. Select Failover from the left panel of the Interface Configuration Utility window to
expose the UniInt Failover options, as shown in the following image. Click the radio
button next to Phase 2. This will enable UniInt failover. In the same window, click the
browse button next to the Synchronization File Path and type the following path:
\\apcndaebiz03\ShareFile\FTLDInt_FTLD_1.dat. Note that apcndaebiz03 is the
share file node.
44
4. In the same UniInt Failover section of the window, select Hot from the drop-down
box next to UFO Type. In the Failover ID# for this interface field, enter 1, and in
the Failover ID# of the other interface field, enter 2. Click Apply.
5. Select Service from the left panel of the Interface Configuration Utility window to
expose the Service Configuration options, as shown in the following image. In the
Service ID field, enter 1 to create service for your primary interface, FTLDInt1.
45
3. Select Failover from the left panel of the Interface Configuration Utility window to
expose the UniInt Failover options, as shown in the following image. Click the radio
button next to Phase 2. This will enable UniInt failover. In the same window, click the
browse button next to the Synchronization File Path and type the following path:
\\apcndaebiz03\ShareFile\FTLDInt_FTLD_1.dat. Note that apcndaebiz03 is the
share file node.
46
4. In the same UniInt Failover section of the window, select Hot from the drop-down
box next to UFO Type. In the Failover ID# for this interface field, enter 2, and in
the Failover ID# of the other interface field, enter 1. Click Apply.
5. Select Service from the left panel of the Interface Configuration Utility window to
expose the Service Configuration options, as shown in the following image. In the
Service ID field, enter 2 to create service for your Secondary Interface,
FTLDInt2.
47
Note: Ensure that the assigned user name for This account is a user who has both read
and write access to the shared folder.
48
4. The UFO_State Digital Set on Server... is now created, as shown in the following
Successfully Created message window.
49
5. In the Tag column shown in the following image, select a tag and then right-click on
it. From the drop-down menu, select Create Points (UFO Phase 2).
6. In the Status column shown in the following image, the tag status has changed from
Not Created to Created.
7. Start the failover interfaces and then launch the System Management Tools (SMT)
application to check failover point value, as shown in the following image.
50
For additional information on testing and validating, refer to Test, Validate and Configure
Tags.
2. Click Tag Search (marked in red in the above figure) to search for tags matching the
tag mask *UFO*.
51
3. Once the search retrieves all the tags, click Select All, and then click OK to add the
tags to the Current Values view.
4. Click Play on the tool bar to start monitoring the tag values. Tag values should report
Pt Created until the primary interface is started for the first time.
52
5. Start the FactoryTalk Live Data Interface service on the primary interface computer by
clicking Play on the Interface Configuration Utilitys main window. Verify that the
failover control tags report values, as shown in the following image.
6. Start the FactoryTalk Live Data Interface service on the secondary interface computer
by clicking Play on the Interface Configuration Utilitys main window. Verify that the
failover control tags report values, as shown in the following image.
7. Create the desired FactoryTalk Historian tags using either FactoryTalk Administration
console or Excel. Verify that data is collected for these points and that data collection
continues after restarting the current primary interface several times.
53
Heartbeat ID: This value indicates that the interface is functioning. This point is
updated once every failover update interval. If the interface is connected to the
FactoryTalk Historian server, the value of the heartbeat point will be incremented by
UniInt from 1 15 and then wraps around to a value of 1 again. If the connection to
the FactoryTalk Historian server is lost, the value of the heartbeat point will be
incremented from 17 31 and then wrap around to a value of 17 again. Once the
connection to the FactoryTalk Historian server is restored, the heartbeat values revert
back to the 1 15 range. During a normal shutdown process, the heartbeat value will
be set to zero.
54
Device Status: This value identifies the data collection ability of an interface. A good
value is represented by zero. Any value other than zero indicates the interface is not
fully communicating and collecting data from the data source. If the primary interface
writes a bad value for its device status to the shared file and the backup has a good
device status, the backup interface will attempt to assume the role as primary as soon
as it reads the bad device status value of the primary interface from the shared file.
UFO_State:1 and UFO_State:2: These tags are digital tags assigned to a digital state
set with the following values. The value of a state tag is updated by the primary
interface.
2 =Backup No PI: The interface is running and connected to the data source
but has lost its communication to the FactoryTalk Historian server.
3 =Backup: The interface is running and collecting data normally and is ready
to take over as primary if the primary interface shuts down or experiences
problems.
4 =Transition: The interface stays in this state for only a short period of time.
The transition period prevents thrashing when more than one interface
attempts to assume the role of primary interface.
5 =Primary: The interface is running, collecting data, and sending the data to
Historian.
4. On the Import Digital Set(s) dialog box, click the button to browse to the
UniInt_Failover_DigitalSet_UFO_State.csv file. The file is usually located in the
C:\Program Files\Rockwell Software\FactoryTalk
Historian\Server\PIPC\Interfaces\OPCInt folder. In a collective, this file is imported
to the primary FactoryTalk Historian server and then synchronized with the secondary
server.
5. Once the file is imported, click Create Sets to create the sets, and then click Close to
close the Import Digital Set(s) dialog box. If the Digital Sets were imported correctly,
you will see the following in the right pane of the System Management Tools.
55
6. Open the excel file that contains the failover control tags. Using the Export Tags
option in the PI-SMT menu (PI-SMT > Export Tags) in Microsoft Excel, export the
tags to the collective.
7. When finished, verify that all seven tags were exported successfully.
Related Documentation
The following documents provide additional information on interface redundancy:
These documents are available from Start > Programs > Rockwell Software > FactoryTalk
Historian SE > Help.
56
CHAPTER 11
57
If you do not see the four user groups, do the following on the FactoryTalk Directory
server computer:
1. Log on to Windows as the local Administrator
2. Log on to FactoryTalk as a member of the FactoryTalk Administrators User Group.
3. Launch the FactoryTalk Administration Console, and create a computer account for
each FactoryTalk Historian SE host.
4. On the FactoryTalk Historian SE Install disk, look for the FTD Updates for FTH
Schemas folder. It is typically located in the Redist\FTHistorian\FTD Updates folder.
5. Open a command prompt window from Start > Programs > Accessories >
Command Prompt. Change the directory to Z:\FTHistorian SE
2.0x\Redist\FTHistorian\FTD Updates for FTH Schemas (where Z is the letter of
the CD or DVD drive that is running the FactoryTalk Historian SE Installation disc).
6. Execute the file FTDUpdates.Bat. This batch file is dependent on the other four files
(FTHistorianFolders.xml, FTHistorianInstallSetup.exe, FTHistorianSchema.xml, and
FTHistorianStrings.xml) located in the FTD Updates for FTH Schemas folder.
7. Return to the FactoryTalk Administration Console and verify that the user groups have
been created.
58
59
60
INDEX
A
ActiveView
installing 27
uninstalling 28
Auto Discovery Wizard 33
uninstalling 20
upgrade instructions 23
FactoryTalk View TrendX display object 35
FTHAdministrators 29
FTHEngineers 29
FTHOperators 29
FTHSupervisors 29
buffering, enabling 17
I
C
Collective 37
Collectives Information 37
Create a Collective 38
Customer Support Center 2
M
D
error messages 59
R
F
FactoryTalk Activation Client 10, 22
FactoryTalk Activation Server 9, 22
FactoryTalk Activation tool 12
FactoryTalk Diagnostics 31
FactoryTalk Diagnostics Viewer tool 31
FactoryTalk Historian ActiveView
installing 27
uninstalling 28
FactoryTalk Historian DataLink
installing 25
uninstalling 28
FactoryTalk Historian DataLink Client 20
FactoryTalk Historian ProcessBook
installing 26
uninstalling 28
upgrading 23
FactoryTalk Historian SE
installing 7
overview 1
troubleshooting 57
RSLinx Enterprise 9, 22
S
shared file 41
software components, where to install 4
Steps to Configure the FactoryTalk Historian SE Server
14
Steps to Install and Configure FactoryTalk Historian
Live Data Remote Interface 15
Steps to Install RSLinx Enterprise (Data Server) 14
Steps to Upgrade FactoryTalk Historian ActiveView,
upgrading 23
Steps to Upgrade to FactoryTalk Historian SE v2.1
upgrade instructions 20
T
To 23
troubleshooting 57
U
upgrading FactoryTalk Historian SE 20
61
62