60114 FAQ: FactoryTalk Historian Site Edition

1 of 5

https://rockwellautomation.custhelp.com/app/answers/detail/a_id/60114

Rockwell Automation Support Center

60114 - FAQ: FactoryTalk Historian Site Edition
Access Level: Everyone
Date Created: 03/31/2009 11:54 AM
Last Updated: 02/19/2015 02:57 PM

*** Begin Conditional Section: Distributor ***

This Answer is intended as a supplement to the sales channel FactoryTalk Historian SE v4.00 FAQ located on Noggin. It is also intended to be more technical in nature and will
be updated relatively frequently for the foreseeable future. Click the 'Add to My Favorites' link at the bottom of this page to be notified of the updates.
Other resources found on Noggin: Launch Overview | Product Profile | Sales Tools | Presentations | Videos
Additional videos are available in the Knowledge Network On-Demand Archives and YouTube.
*** End Conditional Section: Distributor ***

Related FactoryTalk Historian Product Family Supplemental FAQs:

63082 - FAQ: FactoryTalk Historian Machine Edition

FactoryTalk Historian Site Edition (FTHSE) FAQs

Table of Contents (TOC):
Documentation
Versions
Historian v4.xx
Historian v3.xx
Historian v2.xx
FTHSE Integration with FTHME (Data Transfer)
FTHSE Integration with FT View SE
FTHSE Integration with OSIsoft PI
FTHSE Integration with FT VantagePoint
FTHSE Integration with Third Party Reporting
FTHSE Clients
FTHSE Interfaces
Miscellaneous

Documentation Questions
What documentation is provided with the software?
The FactoryTalk FTHSE documentation consists of:
Release Notes (installed with the product and located on the installation media in the '\Redist\Docs' folder)
User's Guides (installed with the product)
KnowledgeBase Answers

Version Questions
What is the shipping history for FactoryTalk SE and the equivalent versions of OSIsoft PI?
You can find the RA version using Control Panel > Programs and Features. You can find the OSIsoft Version by launching the System Management Tools and selecting
Operations > PI Version. For more information, refer to 451943 - FactoryTalk Historian SE: Version number/build of OSIsoft subsystems.

FTHSE Version

OSIsoft PI Version

FTSP

MS Excel version
for SMT Add-in

3.4.375.55 (x86) - also known as "375.55"

CPR 9

2003 & 2007

3.4.375.80 (x86) - also known as "375.80"

CPR 9 SR 1

2003 & 2007

3.4.385.77 (x64) - also known as "385.77" and/or PI 2010 R3

CPR 9 SR 5

2007 & 2010

3.4.385.77 (x64) - also known as "385.77" and/or PI 2010 R3

CPR 9 SR 5.1

2007 & 2010

3.4.390.16 (x64) - also known as "390.16" and/or PI 2012

CPR 9 SR 6

2007, 2010 & 2013

2.00 (x86)
UniInt/FTLDInt.exe 4.4.0.15
2.10 & 2.20 (x86)
UniInt/FTLDInt.exe 4.4.0.15
3.00.00 & 3.00.01 (x64)
UniInt/FTLDInt.exe 4.5.4.0
3.01 (x64)
UniInt/FTLDInt.exe 4.5.4.0
4.00 (x64)
UniInt/FTLDInt.exe 4.5.5.23

Historian v4.xx Questions

What's New in FactoryTalk Historian SE v4.00?
Refer to 562414 - FactoryTalk Historian Site Edition: What's New in v4.00?.

19/3/2015 12:40 PM

60114 FAQ: FactoryTalk Historian Site Edition

2 of 5

https://rockwellautomation.custhelp.com/app/answers/detail/a_id/60114

What version of OSIsoft's PI is FactoryTalk Historian SE v4.00.xx based upon?

FactoryTalk Historian SE v4.00.xx is based upon PI 2012, also known as 3.4.390.16. The Server components are true 64-bit, so a 64-bit Server operating system (Server 2008
R2 SP1) will be required for the FactoryTalk Historian SE Server Suite. For more information, refer to 117888 - FAQ: Software Installation and Operation on a 64-bit Operating
System.
Is FactoryTalk Historian SE v4.00.xx supported on Server 2012 or Server 2012 R2?
The initial release did not support Server 2012/2012 R2 (the Installation Manager would prevent the installation of the Historian Server components). However, a patch now
exists that allows installation.
Is FactoryTalk Historian SE v4.00.xx supported with FactoryTalk Services Platform v2.70 (CPR 9 SR 7)?
The initial release did not fully support FTSP v2.70 (CPR 9 SR 7). However, a patch now exists.
Can a FactoryTalk Historian SE v2.xx system be upgraded to v4.00?
No. The v4.00 release does not support upgrades from v2.xx. To get from v2.xx to v4.00, the system must first be migrated to v3.01 (and then upgraded to 4.00). For more
information, refer to 491889 - FAQ: Migrating to FactoryTalk Historian SE v3.01.

Historian v3.xx Questions

What's New in FactoryTalk Historian SE v3.01?
Refer to 519797 - FactoryTalk Historian Site Edition: What's New in v3.01?.
What's New in FactoryTalk Historian SE v3.00?
Refer to 491469 - FactoryTalk Historian Site Edition: What's New in v3.00.xx?.
What version of OSIsoft's PI is FactoryTalk Historian SE v3.00.xx based upon?
FactoryTalk Historian SE v3.00.xx is based upon PI 2010 Release 3 (R3), also known as 3.4.385.77, which OSI released in December of 2011. The Server components are
true 64-bit, so a 64-bit Server operating system (Server 2008 R2) will be required for the FactoryTalk Historian SE Server. For more information, refer to 117888 - FAQ:
Software Installation and Operation on a 64-bit Operating System.
What is the difference between v3.00.00 and v3.00.01?
SE v3.00.00 was the initial release of v3 prior to the discovery of two security vulnerability in the OSIsoft OPC Interface. For more information, refer to 509721- FactoryTalk
Historian SE: Bundled PI OPC Interface has Two Security Vulnerabilities. SE v3.00.01 was a subsequent release where the OSIsoft OPC Interface vulnerabilities were
corrected and the RA Installation Manager was used.
Can a FactoryTalk Historian SE v2.xx system be upgraded to v3.00?
No. FactoryTalk Historian SE v3.00 release is for new installations only - it should not be used for upgrades or migrations from previous releases. Support for upgrades and
migrations will be in v3.01. For more information, refer to 491889 - FAQ: Migrating to FactoryTalk Historian SE v3.01.
Is there an Installation Assistant for FactoryTalk Historian SE v3.xx?
Yes. The FactoryTalk Historian SE v3.xx Installation Assistant is located on the installation media ('\Redist\Docs' folder) and installed with the product (Start > All Programs >
Rockwell Software > FactoryTalk Historian > Help).
What is the most common problem likely to be experienced with v3.xx?
Establishing remote PI Connections to the Historian Server. In a distributed systems (as opposed to a single host system), a mapping is now required in the SMT prior to
establishing remote PI Connections to the server. For more information, refer to the Configuring FactoryTalk Historian SE Security User's Guide located on the installation
media ('\Redist\Docs' folder) and installed with the product (Start > All Programs > Rockwell Software > FactoryTalk Historian SE > Help).
Has FactoryTalk activation changed with FactoryTalk Historian SE v3.xx?
Yes, for more information, refer to 60530 - FAQ: FactoryTalk Historian SE Activation.
What are the new applications/utilities installed with FactoryTalk Historian SE v3.xx?
There are two:
1. Module Database (MDB to Asset Framework (AF) Preparation Wizard: This utility is only used for a 2.x to 3.x migration and only if the installation media's 'Migrating to
FactoryTalk Historian Site Edition' option was not selected.
2. System Explorer: Used to configure Asset Framework's SQL Server database. It will be seldom used in the typical FactoryTalk Historian system because AF is seldom
used in the typical FactoryTalk Historian system. For more information, refer to 471159 - FAQ: FactoryTalk Historian Asset Framework Server.
What is FactoryTalk Historian SE v3.xx"Advanced Server Option"?
Refer to 490050 - FAQ: FactoryTalk Historian SE Advanced Server Option.
Are there any new clients available for use with FactoryTalk Historian SE v3.xx?
No. However, OSIsoft's AlarmView and ProfileView are being considered for a future release.
What are the four "FactoryTalk Historian...installation blockers" entries in Programs and Features?
Refer to 492538 - FactoryTalk Historian Site Edition v3.00 Installation Blockers.
Do the FactoryTalk Historian SE v3.xx System Management Tools work with FactoryTalk Historian ME v2.x modules?
Yes, but the PI-SDK v1.4.0 does not. For more information, refer to 498086 - FactoryTalk Historian SE v3.xx: Using the System Management Tools (SMT) with FactoryTalk
Historian ME v2.xx modules.

Historian v2.xx Questions

Is FactoryTalk Historian SE v2.20 an atypical product release?
Yes, the FactoryTalk Historian SE v2.20 release is atypical in that it is primarily a commercial release (as opposed to a typical technical release that includes new functionality
and/or enhanced performance). The commercial change in v2.20 is that it now includes FactoryTalk VantagePoint.
However, there are some technical changes in v2.20:
it includes new connections for VantagePoint 3.x, Batch 9.x and Exele Information Systems. For more information, refer to the Release Notes.
it includes all of the v2.10 patches listed in 63530 - FactoryTalk Historian SE 2.10.00 Patch TOC
The Installation Menu now includes FactoryTalk VantagePoint. Note: As a rule, installing FactoryTalk Historian and FactoryTalk VantagePoint on the same host is not
recommended. For more information, refer to 62869 - Using FactoryTalk Historian and FactoryTalk VantagePoint on a single host computer.
The Installation Menu now includes PIBaGen (installs v2.0.5.1). For more information, refer to 115328 - FAQ: The Rockwell Automation FactoryTalk Batch Interface and
the OSIsoft PIBatch Generator Interface.
The Installation Menu no longer includes DataLink. To install DataLink, browse to the \Redist\OtherComponents folder and launch FactoryTalk HistorianDataLink.exe.
What's NOT New in v2.20 (relative to v2.10)?

19/3/2015 12:40 PM

60114 FAQ: FactoryTalk Historian Site Edition

3 of 5

https://rockwellautomation.custhelp.com/app/answers/detail/a_id/60114

Version 2.20 still installs FTAP CPR 9 SR 1 and therefore does not support the recent Windows operating systems such as Server 2008 or Vista. A patch (released in
Nov. 2010) for the Historian Server to provide support for post-FTAP CPR 9 SR 1 system and Server 2008 (32-bit only) is available in 519083.
Version 2.20 installs the same software components as v2.10:

Server 3.4.375.91
Management Tools 3.2.4.0
Interface Configuration Utility 1.4.5.0
Live Data Interface 4.4.0.15
Software Development Kit (SDK) 1.3.5 (includes API 1.6.1.10). For more information, refer to 466175 - FAQ: FactoryTalk Historian Site Edition Software
Development Kit (SDK).

Should I upgrade my Historian v2.10 system to v2.20?

fully patched v2.10 users have little reason to upgrade unless they are in need of the new connectors or they wish use Windows Server 2008 SP2 on the Historian
host (which requires the patch in 519083).
unpatched v2.10 users can apply the v2.10 patches or upgrade to v2.20
Note: Users who upgrade and wish to take advantage of the VantagePoint license should refer to 68720 - Updated FactoryTalk Activation is required for using
FactoryTalk VantagePoint with FactoryTalk Historian SE v2.20.
Should I upgrade my Historian v2.00 system to v2.20?
v2.00 users can upgrade directly to v2.20 if they wish to take advantage of the new features of v2.20 (and v2.10) or they wish use Windows Server 2008 SP2 on the
Historian host (which requires the patch in 519083).
When upgrading from v2.00 to v2.10, do I navigate to add/remove programs to remove the old version?
Do not uninstall the previous version of FactoryTalk Historian SE. The 2.1 Installation automatically updates the software to the latest version.
When upgrading from v2.00 to v2.10, do I need to upgrade my clients (ActiveView, ProcessBook, DataLink) as well?
Yes, The FactoryTalk Historian SE server and all its client components (ActiveView, ProcessBook, DataLink) must be on the same version.
To upgrade clients, you must go to (i.e. Start > Programs > Rockwell Software > FactoryTalk Historian SE > Uninstall FactoryTalk Historian ActiveView)
Can I install the FactoryTalk Historian Server SE v2.x on a drive other than C:\?
Yes, When Installing FactoryTalk Historian Site Edition you will see the following:
A.
B.
C.
D.
E.

Welcome to the InstallShield Wizard for FactoryTalk Historian Site Edition 2.10 Protected, select 'Next'
Next Screen is to accept 'End-User License Agreement'
Next Screen is to Enter Customer Information
Next Screen is to choose 'Setup Type', to install on a driver other than C:\ Choose 'Selected Components and Tools'
Under the 'Custom Setup', for 'Destination Drive' this is where you can type a different drive letter

Where should I install the Activation Server?

Install the Activation Server on a dedicated server computer (i.e.. FactoryTalk Historian Server SE) or it could be on a separate computer. Install the Activation Client on all
client computers.
Which computer should RSLinx Enterprise be installed on?
Install 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. Do not install FactoryTalk Historian
ProcessBook (or any of the other clients, such as ActiveView or DataLink) on the FactoryTalk Historian server computer. This is documented in the FactoryTalk Historian
SE v2.1 Installation and Configuration Guide.
Can I browse and add a tag to the FactoryTalk Historian Server using a remote interface node?
Yes, you can in v2.10. This is a new feature. In version 2.0, you could browse and add tags only from the FactoryTalk Historian Server.

FTHSE Integration with FTHME (Data Transfer) Questions

Does the addition of the ME Module to the Historian Product Family result in new Points Sources?
Yes. The existing FTD point source is for points in the FactoryTalk Historian SE Server whose source is thru the FTD Interface. The new Point Sources are FTME and FTMS:
The FTME point source is for points in the FTME Module
The FTMS point source is for points in the FactoryTalk SE Server whose source is the FactoryTalk ME Module
For example, when connected to the FactoryTalk Historian SE Server and using the SMT Point Search dialog, you can filter the results to only display ME Module points by
entering 'FTMS' in the Point Source field.
Does a v2.10 Historian Server require any updating to facilitate Data Transfer from ME Modules?
Yes. For more information, refer to 66211- FactoryTalk Historian v2.1 Patch to support Historian ME point source licensing. A v2.1 Historian Server without this patch applied
will produce the following error when attempting to assign FTMS points in the Historian Server's Point Sources dialog: "No usable 3rd Party license. The Interface Type
Allocation will be removed."
Does a v2.20 (or higher) Historian Server require any updating to facilitate Data Transfer from ME Modules?
No.
Is there a checklist for setting up Data Transfer from ME Modules?
Yes. Refer to the ME Quick Start Guide, or 68711 - Transfer Data from FactoryTalk Historian ME module to FactoryTalk Historian SE Server - Connection Failed.
If an ME module is deployed prior to a SE Server, are there any special Data Transfer considerations?
If the data in the older ME module data is desired in the SE Server, then archive reprocessing at the SE Server will be required in order to get the older ME module data
transferred. For more information, refer to 117362 - FactoryTalk Historian SE: Configuring the archives to accept older data from another data source (PIOLEDB/CSV Import
etc.).
When are the ME's FTME points that have been selected for Data Transfer actually created as SE FTMS points?
After they have been selected (Configure Historian > Data Transfer Points) and Data Transfer is started/restarted (Configure Historian > Data Transfer).
If an ME's FTME point that has been selected for Data Transfer is renamed, will it get recreated as an additional SE FTMS point?
Yes, the next time Data Transfer is started/restarted, the ME's FTME point will get created again on the Historian Server as an FTMS point with the new point name (prefixed by

19/3/2015 12:40 PM

60114 FAQ: FactoryTalk Historian Site Edition

4 of 5

https://rockwellautomation.custhelp.com/app/answers/detail/a_id/60114

the ME Module name).

Can the ME Data Transfer rate be modified?
Yes. For more information, refer to 111217 - FactoryTalk Historian Machine Edition Data Transfer.
Are there any ME Module conditions that would cause Data Transfer to stop?
Yes, if the ME CPU utilization exceeds 95%. However, when the ME CPU utilization falls, Data Transfer will restart. Examples of activities that will significantly increase ME
Module's CPU utilization are configuration and monitoring via the Web Interface or the System Management Tools.
How can the status and performance of Data Transfer be monitored?
Refer to 501448 - FactoryTalk Historian ME: Methods for Monitoring Performance and Status.
Is the ME Data Transfer functionality identical to the PI to PI Interface available from OSIsoft?
No. While ME Data Transfer performs essentially the same function as PI to PI, Data Transfer was developed by Rockwell Software specifically for the ME Module and does
not use PI to PI technology. However, Data Transfer does use the same TCP/IP port (5450) as PI to PI.
Is there an additional activation required on the FactoryTalk Activation Server for Data Transfer from ME Modules?
Refer to 467296 - FT Historian ME: Assigning the FTMS Point Source.
When configuring Historian ME Modules for Data Transfer to a Historian SE Server, do the Historian ME Modules need to be in FactoryTalk security mode (as
opposed to Native mode)?
While there are several benefits to using FactoryTalk security mode, selecting it is not a prerequisite for Data Transfer to a Historian SE Server. Note: To get the FactoryTalk
Security Web Services prerequisite working on a x64 FactoryTalk Directory computer, you must modify the IIS default application pool to support x86 bit applications. For more
information, refer to the FactoryTalk Help.
Why do Data Transfer (FTMS) points in the FTHSE (or PI) Server have the Exception Deviation (excdev) parameter set to 0?
When the FTLD interface is used with FTHSE, exception filtering takes place at the FTLD interface. When FTHME is used with FTHSE (or PI), exception filtering takes place at
the FTHME module (which has an "integrated" interface). Therefore, FTMS tags created in FTHSE (or PI) via the FTHME Web Interface have exception filtering disabled (set
to 0) by default. This is because typically an exact copy of the original FTHME data is desired in FTHSE (or PI). However, you can use SMT > Points > Point Builder on
the FTHSE (or PI) Server if you desire additional filtering.
Can Data Transfer be used with a FactoryTalk Historian SE Collective?
No. However, the FactoryTalk Historian to Historian Interface will allow the ME module to be used with a FactoryTalk Historian SE collective. For more information, refer
to 58662 - FAQ: The Rockwell Automation FactoryTalk Historian to Historian interface and the OSIsoft PI to PI Interface.
Can Data Transfer be used with Audit Viewer configured at the FactoryTalk Historian SE?
Yes. However, the pisnapssaudit.dat file created by Audit Viewer on the FTHSE Server will grow very rapidly due to "EditAttempt" records being logged. To avoid this problem,
the FactoryTalk Historian to Historian Interface should be substituted for Data Transfer when using Audit Viewer. For more information, refer to 58662 - FAQ: The Rockwell
Automation FactoryTalk Historian to Historian interface and the OSIsoft PI to PI Interface.
Can the Historian SE Server be located at a remote location (e.g., via a WAN link)?
Refer to 66118 - Using FactoryTalk Historian over Wide Area Networks.
What TCP port does the ME Module's Data Transfer use?
TCP port 5450 (the same port as the FTLD Interface).
How many ME Modules are supported with a single FactoryTalk Historian Server?
Refer to 559780 - FactoryTalk Historian SE: Interface and ME Module Limits.
How many ME Module Connections are supported with a Network FactoryTalk (i.e., a single FactoryTalk System)?
Again, only 20 have been tested successfully. However, we have no reason to believe that additional modules will be an issue.
When using multiple ME modules with one Historian Server, are there any "good to know" behavior issues?
Yes. If the SE Server goes down, Data Transfer will cease and the MEs will store the data. When the SE Server is back online, all of the MEs will simultaneously resume Data
Transfer and this will likely result in high CPU utilization at the SE Server until all the data is transferred.
Can the Historian SE Server be used as a Network Time Protocol (NTP) Server for one or more ME Modules?
Yes, however Data Transfer must be configured first and the Web Interface will indicate this. Note: The best practice is to used a controller as the time source for the ME
Module.
I'm adding a ME Module(s) to localize some of the collection currently performed by Historian SE, but maintaining my SE Server for long term storage. Is there a
procedure to explain and expedite this process?
Yes. Refer to 68407 - Converting Historian SE points to Historian ME points.
Does the scan class (location 4) of a FTMS point in the SE Server serve any purpose?
No. The rate at which an FTMS point updates in the SE Server is determined by the ME Module's Data Transfer rate which is between 15-60 seconds (proportional to the
number of points being transferred). For more information on interface location definitions, refer to 51765 - FactoryTalk Historian SE LiveData Interface Location Definitions.
Are there any FactoryTalk Historian Machine Edition (FTHME) known issues that can disrupt Data Collection and/or Data Transfer?
Yes. For more information, refer to 113075 - FactoryTalk Historian ME: Issues that can Disrupt Data Collection and Data Transfer.

Historian SE Integration with FT View SE Questions

Can historical data from Historian SE be displayed in a View SE trend?
Yes. For more information, refer to 61476 - How to Trend Data in FactoryTalk View from a FactoryTalk Historian Database.
FactoryTalk View v7.00 began shipping in January 2013 and includes FactoryTalk Services Platform v2.60 (CPR 9 SR 6) and RSLinx Enterprise v2.60 (CPR 9 SR
6). Are these new components compatible with FactoryTalk Historian SE components?
As of February 2013, these new components have not yet been tested on the same host with any version of FactoryTalk Historian SE. However, there are no known issues
and the likelihood of an issue is low. As with any software component upgrade, a complete backup (or virtual machine snapshot) is strongly recommended prior to the
upgrade. For more information, refer to 534697 - FAQ: FactoryTalk Historian and FactoryTalk View Site Edition v7.00 (CPR 9 SR 6).
FactoryTalk View v8.00 began shipping in August 2014 and includes FactoryTalk Services Platform v2.70 (CPR 9 SR 7), RSLinx Enterprise v2.70 (CPR 9 SR 7) and
support for Windows Server 2012 R2. Are these new components compatible with FactoryTalk Historian SE components?
Yes. For more information, refer to 618193 - FactoryTalk View SE v8.00 (CPR 9 SR 7): The "FactoryTalk Historian Connectivity" option and 640724 - FactoryTalk Historian SE,
View SE and VantagePoint EMI on a single Windows Server 2012/2012 R2 host.

Historian SE Integration with OSIsoft PI Questions

Can Historian SE integrate with OSIsoft PI systems?

19/3/2015 12:40 PM

60114 FAQ: FactoryTalk Historian Site Edition

5 of 5

https://rockwellautomation.custhelp.com/app/answers/detail/a_id/60114

Yes. For more information, refer to 58662 - FAQ: The Rockwell Automation FactoryTalk Historian to FactoryTalk Historian Interface and the OSIsoft PI to PI Interface.

Historian SE Integration with FT VantagePoint

Refer to 70820 - FactoryTalk VantagePoint: Methods for Monitoring the Status of a FactoryTalk Historian and 640724 - FactoryTalk Historian SE, View SE and VantagePoint
EMI on a single Windows Server 2012/2012 R2 host.

Historian SE Integration with Third Party Reporting Questions

Are Third Party Reporting packages able to connect to FactoryTalk Historian SE?
Yes, via the OLE-DB connector. For more information, refer to 65354 - FactoryTalk Historian SE and the OSIsoft PI OLEDB Provider (PIOLEDB).
Are Third Party Reporting packages able to connect to FactoryTalk Historian SE using the PI-SDK (i.e., custom connections)?Yes. Using the SDK is not recommended
due to cost and complexity. For more information, refer to 117808 - FactoryTalk Historian SE: Anonymous Connections.

Historian SE Client Questions

What are the available Historian SE Clients?
Refer to 451934 - FactoryTalk Historian Clients.

Historian SE Interface Questions

What are the available Historian SE Interfaces?
Refer to 55105 - FAQ: FactoryTalk Historian Site Edition and the OSIsoft Interfaces.

Miscellaneous Questions
How many FactoryTalk Historian SE Servers are supported in a Network FactoryTalk Directory?
With the release of v4.00, this limit was increased from one to two (however, this limit is not enforced by the FT Administration Console). For more information, refer to 562414
- FactoryTalk Historian Site Edition: What's New in v4.00?.
How many FactoryTalk Live Data Interfaces and/or FT Historian ME Modules are supported with each FactoryTalk Historian SE Server?
Refer to 559780 - FactoryTalk Historian SE: Interface and Machine Edition Module Limits.
Can a FactoryTalk Historian SE Server collect data from multiple FactoryTalk Applications?
In production environments the answer is currently "no" because multiple FactoryTalk Applications are not supported. For more information, refer to 58382 - Multiple
FactoryTalk Applications within a Single FactoryTalk Directory. However, in non-production environments the answer is "yes" because multiple FactoryTalk Applications
are permitted.
Does FactoryTalk Historian SE support OSIsoft's AutoPointSync (APS) with the FTLD and FTHtoH Interfaces?
No. APC Connectors are not available for these Rockwell specific interfaces.
Is FactoryTalk Historian SE supported on Virtualized Systems?
Yes - provided the minimum hardware requirements (in the virtualized environment) are met. For more information, refer to 451936 - FactoryTalk Historian Site Edition and
Virtualization. We have FTHSE systems running in the following environments: VMware Workstation, VMware ESXi, and Windows Hyper-V. We also have systems, running as
instances, in Windows Azure. For more information please see:
490072 - VMware Ready Products
568026 - Using Rockwell Automation Software with VMware
115299 - How to maximize VMWare images performance

Comments (0)
This answer has no comments

Post a Comment

Product Tree for This Answer (expand/collapse)

DISCLAIMER
This knowledge base web site is intended to provide general technical information on a particular subject or subjects and is not an exhaustive treatment of such subjects.
Accordingly, the information in this web site is not intended to constitute application, design, software or other professional engineering advice or services. Before making any
decision or taking any action, which might affect your equipment, you should consult a qualified professional advisor.
ROCKWELL AUTOMATION DOES NOT WARRANT THE COMPLETENESS, TIMELINESS OR ACCURACY OF ANY OF THE DATA CONTAINED IN THIS WEB SITE AND
MAY MAKE CHANGES THERETO AT ANY TIME IN ITS SOLE DISCRETION WITHOUT NOTICE. FURTHER, ALL INFORMATION CONVEYED HEREBY IS PROVIDED TO
USERS "AS IS." IN NO EVENT SHALL ROCKWELL BE LIABLE FOR ANY DAMAGES OF ANY KIND INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL,
LOSS PROFIT OR DAMAGE, EVEN IF ROCKWELL AUTOMATION HAVE BEEN ADVISED ON THE POSSIBILITY OF SUCH DAMAGES.
ROCKWELL AUTOMATION DISCLAIMS ALL WARRANTIES WHETHER EXPRESSED OR IMPLIED IN RESPECT OF THE INFORMATION (INCLUDING SOFTWARE)
PROVIDED HEREBY, INCLUDING THE IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, AND NON-INFRINGEMENT. Note that
certain jurisdictions do not countenance the exclusion of implied warranties; thus, this disclaimer may not apply to you.

This page is best viewed in Internet Explorer 10, Firefox 31, Chrome 37, Safari 6 or newer.

19/3/2015 12:40 PM