Tech Notes

Tech Note 108: How to Use the New Summary Features of Wonderware Historian 10.0

One of the new features included with Wonderware Historian version 10.0 is tag replication. You can replicate tags locally, or to a "Tier-2 Historian" for aggregate/summary information. This feature bypasses the event system, and stores information in Historian History Blocks. You can customize tagname conventions for replicated tags, create your own schedules, and more. The purpose of this document is to demonstrate local Historian tag replication for storing analog summarized and state summary values.

...

Tech Note 104: How to automatically install Wonderware Information Server client components through Windows Domain Group Policy

As a time saving feature when faced with having to install the Wonderware Information Server 3.x or Wonderware ActiveFactory Reporting Website client components on a number of domain attached computers, it is much easier and more efficient to be able to push the Information Server Client Components install out to the client machines through Windows Domain Group Policy. This is also a very handy tool in environments where the clients are non administrative users as the installs can be attached to computer policy which does not require that an administrator level user be logged in, just a computer reboot.

By...

Tech Note 98: How to Set Up a Wonderware Historian Cluster

This tech note walks through the setup of Wonderware Historian 9.0 running on a Microsoft Windows 2003 cluster for high availability and failover purposes. By implementing a two or more node cluster, it allows avoiding extended downtime due to hardware failure by allowing the software to failover to a secondary node or other node in the case of failure of the active node.

Please note that this allows for high availability of the server and software but by itself does not provide true data redundancy.

...

Tech Note 89: How to Implement Time Considerations with Wonderware Historian and IDAS Systems

When working with Wonderware Historian and IDAS, it is important to take time into serious consideration. With IDAS historical data storage there is a term called the "Real-Time Window", which is a period of time behind and ahead of the Wonderware Historian system time, where values coming into the system are considered "valid" and will be stored properly. With Wonderware Historian the real-time window can be any value coming into the system between -30 seconds and +999 milliseconds. Time offset and discarded data can be a result of improper time synchronization. The purpose of this document is to help identify...

Tech Note 81: How to change Wonderware Historian’s server name for Wonderware QI Analyst 4.2 workspaces and data tables

Wonderware QI Analyst can be configured to retrieve historical data from Wonderware Historian Server (formerly known as IndustrialSQL Server or InSQL). If Wonderware Historian is moved to a different computer after QI Analyst has been configured, QI Analyst may not be able to retrieve data from the Historian as an incorrect computer name or server alias is used by QI Analyst to access data. In such case Wonderware QI Analyst workspace may fail to open. This tech note describes the procedure to rectify the problem.

...

Tech Note 67: Wonderware Historian Database Import/Export Utility — How to use the import feature with a manually created Industrial Data Acquisition Service (IDAS)

It may become necessary for a developer to create an IDAS in Wonderware Historian that views many data points without having an InTouch HMI application to import tags from. This document provides the procedure necessary to utilize the Import Tags feature of Wonderware Historian without an existing Wonderware InTouch application, as well as how to use the Wonderware IndustrialSQL Server database export/import utility for archiving or troubleshooting.

...

Tech Note 52: How to configure and query Wonderware Historian 9.0 as a linked server to another Microsoft SQL Server

Sometimes clients who request data from the Wonderware Historian (previously known as IndustrialSQL Server or simply InSQL) may not be directly connected to the Historian (for instance, if the Wonderware Historian is behind a firewall), or there may be a need to present data from multiple Wonderware Historians on the network within a single report.

Therefore it may be necessary or beneficial to set up a central reporting server and have that server retrieve data from one or more Wonderware Historians. In such scenario data clients would connect only to the central reporting server, which in turn would query the...

Tech Note 46: How to modify existing Microsoft SQL Server 2005 installation to comply with Wonderware Information Server 3.0

This Tech Note details the procedure to modify the existing Microsoft SQL Server 2005 installation (described in Wonderware PacWest Tech Note 8: Recommended Microsoft SQL Server 2005 installation procedure for Wonderware products) to comply with requirements of Wonderware Information Server 3.0. Microsoft Reporting Services is a major component required by Wonderware Information Server that is not included into the generic Microsoft SQL Server 2005 installation procedure described in the Wonderware PacWest Tech Note 8.

For brand new installation of Microsoft SQL Server 2005 for Wonderware Information Server 3.0 refer to Wonderware PacWest Tech Note 28: Microsoft SQL Server 2005 installation...