InFusion™ Enterprise Control System

InFusion SCADA
Historian
Synchronization User's
Guide

B0750BX

Rev B
July 6, 2011
All rights reserved. No part of this documentation shall be
reproduced, stored in a retrieval system, or transmitted by any means,
electronic, mechanical, photocopying, recording, or otherwise,
without the prior written permission of the Invensys Systems, Inc. No
copyright or patent liability is assumed with respect to the use of the
information contained herein. Although every precaution has been
taken in the preparation of this documentation, the publisher and the
author assume no responsibility for errors or omissions. Neither is any
liability assumed for damages resulting from the use of the
information contained herein.
The information in this documentation is subject to change without
notice and does not represent a commitment on the part of Invensys
Systems, Inc. The software described in this documentation is
furnished under a license or nondisclosure agreement. This software
may be used or copied only in accordance with the terms of these
agreements.

©2009-2011 Invensys Systems, Inc. All Rights Reserved.

Trademarks
Invensys, ArchestrA, InFusion, InSQL, Wonderware and the Invensys
logo are trademarks of Invensys plc, its subsidiaries and affiliates.
All other brand names may be trademarks of their respective owners.
 iii

Contents
Before You Begin ................................................v
About This Book .................................................................................... v
Audience................................................................................................. v
Revision Information.............................................................................. v
Reference Documents ............................................................................ v
Related Wonderware Documentation ................................................ vi
InFusion-Specific Documentation ..................................................... vi
Document Conventions ......................................................................... vi
Formatting Styles............................................................................... vi

CHAPTER 1: Introduction...................................1
Overview ................................................................................................ 1
Working Principles ................................................................................. 2

CHAPTER 2: Configuration ................................5

Configuring Historian Sync ................................................................... 5
FS Gateway ............................................................................................ 8
Create FS Gateway on Application Servers ....................................... 8
Creating IDAS on Historian Server...................................................11

CHAPTER 3: Execution of Historian

Synchronization Application............................25
Overview .............................................................................................. 25
OnDemand Synchronization ................................................................ 26

CHAPTER 4: Supported Application Objects .27

$HistorianIOServerService Object....................................................... 27
$PrimaryHistPing Object ..................................................................... 29
$SecondaryHistPing Object ................................................................. 30
$SCADAWinPlatform Object .............................................................. 30
Removing References to History in Galaxy ..................................... 30
Identifying Historians in Project $SCADAWinPlatform.................. 32
$SCADAEngine Object ....................................................................... 34

APPENDIX A: Licensing ...................................35

Index ..................................................................37

InFusion SCADA Historian Synchronization User’s Guide – B0750BX Rev B

iv Contents

InFusion SCADA Historian Synchronization User’s Guide – B0750BX Rev B

 v

Before You Begin

About This Book

The purpose of this book is to provide instructions for using the InFusion™
Historian Synchronization software for InFusion SCADA Software.
The information in this document is also available from online help. This
software functions only on specific workstations with Windows® operating
system.

Audience
The information in this document is intended for process operators and
engineers.

Revision Information
For this release of the document (B0750BX, Revision B), the following
changes were made:
Chapter 2, “Configuration”
• Updated section “Configuring Historian Sync” on page 5.
• Minor updates in section “FS Gateway” on page 8.
• Updated section “Creating IDAS on Historian Server” on page 11.
Chapter 3, "Execution of Historian Synchronization Application"
• Added section “OnDemand Synchronization” on page 26.
Chapter 4, “Supported Application Objects”
• Updated section “$HistorianIOServerService Object” on page 27.

Reference Documents
Since the InFusion SCADA software is based on the ArchestrA® architecture
and incorporates several Wonderware® products, much of the documentation
written by Wonderware is relevant. In addition, there are documents that
describe InFusion-specific features. Below is a list of documents that can
provide additional information that is beyond the scope of this document.
These documents can be accessed from IPS Global Client Support web site:
http://support.ips.invensys.com

InFusion SCADA Historian Synchronization User’s Guide – B0750BX Rev B

vi Before You Begin

Related Wonderware Documentation

During Wonderware software component installation, the documents
associated with the software components being installed are also installed.
These documents can be viewed by clicking Start > Programs >
Wonderware > Books menu.

InFusion-Specific Documentation
During InFusion SCADA software component installation, the documents
associated with the software components being installed are also installed.
These documents can be viewed by clicking Start > Programs > Invensys >
InFusionSCADA Documentation menu.

Document Conventions
This section describes the conventions followed in this document.

Formatting Styles
This documentation uses the following text formatting conventions:

Convention Used for

UPPERCASE Transact-SQL keywords and SQL elements
Initial Capitals Paths and filenames
Bold Database names, table names, column names, stored
procedures, command-prompt utilities, product names,
menus, commands, dialog box options, programming
elements, and text that must be typed exactly as shown
Italic User-supplied variables, relationships, and phrasings
Monospace Code samples, examples, display text, and error messages

InFusion SCADA Historian Synchronization User’s Guide – B0750BX Rev B

 1

C H A P T E R 1

Introduction

This chapter provides a general overview of the InFusion Historian

Synchronization software for InFusion SCADA software.

Contents
• Overview
• Working Principles

Overview
InFusion SCADA includes the facility to setup InFusion Historian Servers
through the Historian Synchronization software. This facility requires extra
setup tasks over the standard InFusion Historian, and provides for up to three
Slave Historians along with a Master Historian.
The InFusion SCADA Historian Synchronization software is useful only when
the IDAS version of the Historians is used.

Note The Historian Synchronization software is for the customers who want
to use more than One Historian. The Single Node Historian customers do not
need to install it.

The advantages of the Historian Synchronization software are as follows:

• Parallel collection of history data on up to four historians
• Usage of the Historian Sync application (provided) to synchronize up to
four historians, filling the gaps in history data between the multiple
historians
• Synchronization of the InFusion SCADA Database tables between the
Historians
• Parallel collection of the alarm and event history data on multiple
historians using AlarmDB Log Manager
• The Historian solution can be implemented both as providing historians
with an ArchestrA platform (preferred) or without a platform.
The disadvantages associated with the Historian Synchronization software are
as follows:

InFusion SCADA Historian Synchronization User’s Guide – B0750BX Rev B

2 1. Introduction

• MDAS is not used; hence, there is some loss of “ease of use” while
specifying the object attributes to be stored into the history data
• There is no “Store & Forward” capability built into MDAS (although this
feature is generally not required if Historians already exist).

Working Principles
The following diagram illustrates the basic setup and flow of history data using
Historians:

Figure 1-1. Parallel Collection of History Data from Application

Servers to Parallel Historians

InFusion SCADA Historian Synchronization User’s Guide – B0750BX Rev B

 1. Introduction 3

In the previous configuration:

1. The HIST 1 server normally collects from the application server IAS1.
2. The Hist 2 server normally collects from the application server IAS2.
3. If IAS 1 fails, then both HIST 1 and HIST 2 collect from the application
server IAS2.
4. If IAS 2 fails, then both HIST 1 and HIST 2 collect from the application
server IAS 1.
5. If either of HIST 1 or HIST 2 fails, and is restored later, then a data gap
develops in it. In such cases, the Historian Synchronization software is
used to “fill in” such gaps from one server to another.
6. Store and Forward storage on the historian is not used.
The Alarm and Event Data is collected similarly, by defining a DBLogger task
for each historian. Typically, in the previous example, a DBLogger would be
created on IAS1 and another on IAS2. Both DBLogger tasks would write to the
historian. Alternatively, a platform could be used on each historian, and a local
DBLogger created on the historian (this is the preferred method).
The InFusion SCADA data is written in parallel to up to four Servers. Also, the
NetworkMonitor.HIST1 object provides for automated synchronization of
Historians.
Following are the steps for setting up the Historians:
1. Load and license each HISTORY server with standard InSQL® historian.
2. Remove the references to the historian in the Galaxy Platform and Engine
specifications.
3. Identify up to four historians in each instance of the $SCADAWinPlatform
object (along with the historian user name and password).
4. Configure the FSGateways for SuiteLink Servers in multiple application
servers.
5. Create IDAS entries in each historian.
6. Install and configure the Historian Sync task in each historian.
7. Configure the NetworkMontior.HIST1, NetworkMontior.HIST2,
NetworkMontior.HIST3, and NetworkMontior.HIST4 object parameters
to setup multiple historians.
8. Configure the aahIOSvrC objects.
9. Create Multiple DBLogger Tasks (for Alarm/Event History).
Once the historians are setup and collecting, the failover and synchronization
of the historians to backup-historians is automatic.

InFusion SCADA Historian Synchronization User’s Guide – B0750BX Rev B

4 1. Introduction

InFusion SCADA Historian Synchronization User’s Guide – B0750BX Rev B

 5

C H A P T E R 2

Configuration

This chapter explains the procedure for configuring the Historian

Synchronization software.

Contents
• Configuring Historian Sync
• FS Gateway

Configuring Historian Sync

The Historian Synchronization application is capable of synchronizing
multiple InSQL-based Historian machines. It performs the following
functions:
• Detects the data gaps across different Historians.
• Builds the blocks in the same format as managed by the Wonderware
Historian.
• Fills up the gaps on a daily basis and also supports OnDemand
Synchronization. (The gaps could occur due to physical unavailability of
the Historian, network failure, services failure, configuration issues).
In order to perform its functions effectively, the Historian Sync application
requires the following two configuration files to be modified:
1. InSQLSync_cfg.xml
While the application is running, click Config > Hist Sync file to access
this file.
2. OnDemand.xml
While the application is running, click Config > OnDemand to access
this file.
The following is a brief explanation of the InSQLSync_cfg.xml file; the
default values in this file must be modified or not modified as explained below:
1. The first three lines represent, respectively, the location name and the size
of the log file. The user can leave these settings as the default.
<log_file_folder>C:\InSQLSync\Log</log_file_folder>
<log_file_name>InSQLSync.log</log_file_name>
<log_file_size>1000000</log_file_size>

InFusion SCADA Historian Synchronization User’s Guide – B0750BX Rev B

6 2. Configuration

2. In the next line, the path of the primary file is specified.

<primary_file> C:\InSQLSync\Primary\primary</primary_file>

The primary file is maintained by the aahIOSvrSvc application objects to

provide the status of the Historians.
3. The next line represents the path to the location of the OnDemand file.
The On Demand file is used for a forced synchronization. The normal
synchronization takes place only once every day. A sample file would look
like the following:
<ondemand_file>C:\InSQLSync\Configs\ondemand.xml</ondemand_file>

4. The next line represents the folder location where the backup history
blocks get stored.
<history_block_backup_dir>C:\InSQLSync\HistBackup</history_block_backup_dir>

5. The next line represents the folder location where the gaps in the data are
detected.
<manual_gap_info_dir>C:\InSQLSync\ManualGaps</manual_gap_info_dir>

6. The next line is the relative path for the new data blocks. It is
recommended to leave the default settings.
<new_block_temp_dir>.\NewBlocks</new_block_temp_dir>

7. The next line is the name of the tag used to mark the end of a data block.
The SysPulse is an Historian default tag which gets updated every minute.
<block_completion_check_tag>SysPulse</block_completion_check_tag>

8. The next line must be configured with one or more tag names of the
Galaxy, separated by commas. One or more tags can be configured in the
file for the data quality. The quality of these tags is considered for
detecting the data in the Historians for good and bad blocks. The user must
replace the default tags with the tags in the configured Galaxy. At any
given time, the value of at least one of the chosen tags must be “good”.
<quality_check_tag>R_MOH_UNIT_1_MW,R_MDS_NPC_DEVIATION_CURR,R_XDS
_ONLINE_MW_CAPACITY</ quality_check_tag >

9. The next line represents the tag name for any manual tag. You can leave it
blank.
<manual_edit_check_tag></manual_edit_check_tag>

10. The next line represents the tag name used to monitor the status of the
Inter-Control Center Communications Protocol (ICCP). It is used to
specify the communication status tag, when the system is using data from
the RTPAgent. This field can be left blank if not used.
<iccp_comm_check_tag></iccp_comm_check_tag>

11. The next line represents the geographical time zone. The users must
update their time zone as applicable. The string representation of the time
zone must be used.
<time_zone>Pacific Daylight Time</time_zone>

InFusion SCADA Historian Synchronization User’s Guide – B0750BX Rev B

 2. Configuration 7

12. The daily_check field specifies whether the application has to check and
fill gaps on a daily basis.
<daily_check note=”true or false”>true</daily_check>

13. The daily_check_time is the actual time at which the check is to be

performed.
<daily_check_time note=”HH:MM:SS”>01:28:10</daily_check_time>

14. The ondemand_check_time is the time at which the OnDemand

Synchronization starts.
<ondemand_check_time note=”HH:MM:SS”>10:08:20</ondemand_check_time>

15. The task levels are listed in the XML file itself. The default value is 1. The
options 1 and 2 are used for troubleshooting and verifying the accuracy of
the data getting synchronized. Here:
• 1 indicates - Check Only Gaps
• 2 indicates - Build Blocks Only
• 3 indicates - Sync History
16. The next line represents the interval for the waiting time.
<wait_time>1000</wait_time>

17. The next part is the Server List configuration where the Historian machine
details must be entered. Depending on the level of redundancy, the server
must be matched.
The Historian Sync application can support synchronization of up to a
maximum of four Historians. The server list must contain the description
of the actual Historian servers only.
A typical configuration for a server is as follows:
<Server server_note=”server”>
<server_name>GOCRS1</server_name>
<user_name>wwAdmin</user_name>
<password>wwAdmin</password>
<database>Runtime</database>
<history_block_dir>\\GOCRS1\E$\InSQL\DATA\Circular\</history_block_dir>
<permanant_dir>\\GOCRS1\E$\InSQL\DATA\Permanent\</permanent_dir>
</Server>

In this text:
a. Leave the first line as it is.
b. The next line specifies the name of the Historian.
c. The next two lines represent the SQL Server login credentials of the
Historian machine.
d. The next line is the database name of the INSQL Historian, the
default value Runtime must not be altered.
e. The next line is the share path where the history blocks are stored.
f. The next line is the share path where the permanent history blocks are
stored.

InFusion SCADA Historian Synchronization User’s Guide – B0750BX Rev B

8 2. Configuration

Note The INSQL folder is created by the INSQL installation. This folder
must be shared with full access.

Similarly, provide details for the other available Historian machines as

described above.

FS Gateway

Create FS Gateway on Application Servers

Each Application Server must have an FSGateway configured so that the
historians can collect the necessary information with IDAS. To setup the
FSGateway on each application server (primary and backup), do the following:
1. Install FSGateway 2.0 from Device Integration disk.
2. Open SMC expand the DA Server Manager and browse to local.

Figure 2-1. System Management Console

3. Right-click ArchestrA.FSGateway.2 and configure service to “Auto

Service”.

Figure 2-2. System Management Console Configuring as Auto Service

InFusion SCADA Historian Synchronization User’s Guide – B0750BX Rev B

 2. Configuration 9

4. Click Yes.

Figure 2-3. Configuring as Auto Service

5. Expand ArchestrA.FSGateway.2, right-click Configuration if

ArchestrA object, and click Add ArchestrA.

Figure 2-4. System Management Console Add ArchestrA Object

InFusion SCADA Historian Synchronization User’s Guide – B0750BX Rev B

10 2. Configuration

6. Rename the ArchestrA object to ArchestrA and leave the default settings
as such.

Figure 2-5. System Management Console Rename ArchestrA Object

7. Right-click ArchestrA.FSGateway.2 and select Activate Server.

Figure 2-6. System Management Console - Activate Server

InFusion SCADA Historian Synchronization User’s Guide – B0750BX Rev B

 2. Configuration 11

8. After the Server has been activated, the Diagnostic properties of the
ArchestrA object appear.

Figure 2-7. System Management Console-Diagnostic Properties

FSGateway is now configured. Follow the same procedure for all Application
Servers.

Creating IDAS on Historian Server

Normally, the Industrial Application Server shares historical data using the
MDAS interface. For Wonderware Historians, IDAS is used. This section
discusses setting up IDAS on each History server.

InFusion SCADA Historian Synchronization User’s Guide – B0750BX Rev B

12 2. Configuration

Note Before initiating the IDAs configuration follow the Winplatform and
Engine configuration. Please refer Chapter 4, “Supported Application Objects”
for more details.

1. On each InSQL Server in the redundant configuration, select

Configuration Editor. Expand the Data Acquisition node and browse to
IDAS (Industrial SQL Server Data Acquisition Service).

Figure 2-8. System Management Console

InFusion SCADA Historian Synchronization User’s Guide – B0750BX Rev B

 2. Configuration 13

2. Right-click IDAS and select New I/O Server.

Figure 2-9. System Management Console - Adding New I/O Server

3. Enter the primary application server name in the I/O Server Location
box. Select the FSGateway option in the I/O Server Type box. Select
SuiteLink as Protocol Type. Add description and enter the redundant
Appserver name in the Alt.ServerLocation box.

Figure 2-10. New I/O Sever Window

4. Click Finish.

InFusion SCADA Historian Synchronization User’s Guide – B0750BX Rev B

14 2. Configuration

5. Expand IDAS. Right-click \\appservername\FSGateway and select

Properties to confirm the configuration.

Figure 2-11. FSGateway Properties Window

6. Click OK.

InFusion SCADA Historian Synchronization User’s Guide – B0750BX Rev B

 2. Configuration 15

7. Before proceeding, commit the modifications. Right-click either the Data

Acquisition folder or the IDAS itself, and select Commit Pending
Changes.

Figure 2-12. System Management Console - Commit Pending Changes

8. After the committing is complete, a confirmation dialog box appears.

Click Display if you want to view the changes made.

Figure 2-13. Commit Pending Changes - Confirmation Dialog Box

InFusion SCADA Historian Synchronization User’s Guide – B0750BX Rev B

16 2. Configuration

9. Following display appears:

Figure 2-14. Pending Changes Window

10. Click OK to close the display and to return to the Commit Pending
Changes - Confirmation window.
11. Click Commit to confirm the changes.

Figure 2-15. Commit Pending Changes - Confirmation Dialog Box

InFusion SCADA Historian Synchronization User’s Guide – B0750BX Rev B

 2. Configuration 17

12. Point to the server name in the navigational panel, right-click and select
New Topic.

Figure 2-16. System Management Console - Add New Topic

13. In the next window, enter the Topic Name as ArchestrA or any other
name as given in the ArchestrA object in the FS Gateway in the App
Servers. Leave the other default values as they are.

Figure 2-17. FSGateway - New Topic

InFusion SCADA Historian Synchronization User’s Guide – B0750BX Rev B

18 2. Configuration

14. Click Finish.

15. Commit changes made to the historian to complete addition of the Topic
Name by following the same process as specified in steps 7 through 11.
16. You can either manually add tags to both servers, or set the IsHistory
UDA in the SCADAAnalogDevice or SCADADiscreteDevice object. If
you set the isHistory UDA, then the tags will be added automatically to
IDAS on all defined historians by the SCADACollector. If you want to
add Tags manually to the IDAS for data collection, then right click the
Topic Name and select New Analog Tag.

Figure 2-18. System Management Console - New Analog Tag

InFusion SCADA Historian Synchronization User’s Guide – B0750BX Rev B

 2. Configuration 19

17. The following window appears:

Figure 2-19. New Analog Tag Dialog Box

18. Provide a Unique Tag Name, and click Next.

19. On the next page, select the value for Engineering Unit and specify the
Max/Min Value. Click Next

Figure 2-20. New Analog Tag IDAS_Analog - General Dialog Box

InFusion SCADA Historian Synchronization User’s Guide – B0750BX Rev B

20 2. Configuration

20. On the next page, specify the Item Name (I/O point address) and click
Next.

Figure 2-21. New Analog Tag RdTest - Acquisition Dialog Box

21. On the next page, select the Storage Method, and click Finish.

Figure 2-22. New Analog Tag IDAS_Analog - Storage Dialog Box

22. Commit all the changes made to the system in the same way as explained
in steps 7 through 11.

InFusion SCADA Historian Synchronization User’s Guide – B0750BX Rev B

 2. Configuration 21

23. Finally, re-initialize the topic to complete IDAS configuration. Open the
Management Console. Click Data Acquisition in the navigation pane. In
the right pane, right click the FSGateway object and select Re-initialize
Topic.

Figure 2-23. System Management Console - Re-initialize Topic

24. The following window appears:

Figure 2-24. Re-initialize One Topic Dialog Box

25. Click OK.

26. By default, InSQL makes some modifications to the timestamps on the
values that get historized. This may sometime result in the duplication of

InFusion SCADA Historian Synchronization User’s Guide – B0750BX Rev B

22 2. Configuration

data or other inconsistent behavior. This can be avoided by configuring

InSQL in the following way:
a. Open the System Management Console and navigate to
IndustrialSQL Server Group > [Historian_name] >
Configuration Editor > System Configuration > Parameters.

Figure 2-25. System Management Console - InSQL Configuration

b. Modify the following parameters available in the right pane:

• AllowOriginals - The default value for this parameter is zero. In
InFusion SCADA, the data received from the RTU will have a
timestamp older than the current time. To allow the data to get
stored in the Historian, this parameter value must be changed to
1.
• SuiteLinkTimeSyncInterval - This parameter represents the
number of minutes between SuiteLink time synchronizations (0 =
no time sync). The HistorianIOServerService instances get
connected to the Historians, and since the default value of this
parameter is 60, this affects the timestamp of the data stored in
the Historian. The parameter value must be changed to 0, which
implies that no time synchronization occurs between Suitelink
client and Historian node.
• TimeSyncIODrivers - When set to 1, the Historian sends time
synchronization commands to all its remote IDASs. The default
value of this parameter affects the timestamp on the data being
stored. To avoid this, change the default value to 0.

InFusion SCADA Historian Synchronization User’s Guide – B0750BX Rev B

 2. Configuration 23

27. Repeat the same procedure for other Historian Servers in the
configuration.

InFusion SCADA Historian Synchronization User’s Guide – B0750BX Rev B

24 2. Configuration

InFusion SCADA Historian Synchronization User’s Guide – B0750BX Rev B

 25

C H A P T E R 3

Execution of Historian
Synchronization Application

Overview
If the Primary Historian server fails, for some time, and comes back again as
active, then a gap develops within the data. The Historian Synchronization
application, also known as the Historian Sync application, synchronizes daily
at a pre-defined time and collects data from the second Historian machine to
fill up the Primary Historian Server data gaps. While executing, the Historian
Sync application window appears as shown in Figure 3-1.

Figure 3-1. Historian Synchronization Module Dialog Box

The application provides the following types of Synchronization:

• Regular Synchronization: This type of synchronization occurs according
to the Time specified in the file InSQLSync_cfg.xml. See “Configuring
Historian Sync” on page 5 for more information about this file.
• OnDemand Synchronization: This type of synchronization occurs
according to the Time Specified in the file OnDemand.xml.

InFusion SCADA Historian Synchronization User’s Guide – B0750BX Rev B

26 3. Execution of Historian Synchronization Application

OnDemand Synchronization
To configure the OnDemand synchronization:
1. While the application is running, click Config > On Demand to open the
OnDemand.xml file.
2. In the OnDemand file, configure the start date, end date, and the task level
for synchronization as 3. Same start date and end date would indicate one
full day.
3. Configure the ondemand_check_time in HH:MM:SS format in the main
configuration file. The time entered must be a future time.
The Historian Sync application checks/reads the configuration file every 6
seconds.
The OnDemand synchronization process is required when the user experiences
gaps in the Historians. The OnDemand synchronization process must be
carried out on the present primary Historian node.
A sample OnDemand.xml file would look like the following:
<InSQLSyncOnDemand xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
InSQLSync_key="ondemand">
<ondemand_start_date note="MM/DD/YYYY">04/30/2011</ondemand_start_date>
<ondemand_end_date note="MM/DD/YYYY">04/30/2011</ondemand_end_date>
<ondemand_task_level>1</ondemand_task_level>
</InSQLSyncOnDemand>

In this sample, the same start and end dates indicate that the synchronization
must be done for the full day on this date. The ondemand_task_level must be
changed to 3.

InFusion SCADA Historian Synchronization User’s Guide – B0750BX Rev B

 27

C H A P T E R 4

Supported Application
Objects

This chapter discusses the Application Objects that are supported by the
InFusion Historian Synchronization software and explains the procedure for
configuring them as per the requirements of the Historian Synchronization
application.

Contents
• $HistorianIOServerService Object
• $PrimaryHistPing Object
• $SecondaryHistPing Object
• $SCADAWinPlatform Object
• $SCADAEngine Object

$HistorianIOServerService Object
This object is an ArchestrA derived DDESuiteLink Object, which has been
customized to connect to the Historian.
The names of the instances of this object must be specified as aahIOSvrSvc,
aahIOSvrSvc1, and so on. The Primary Historian has to be aahIOSvrSvc and
others for backup. For each of the Historian, one Instance must be created.
The Object Server name is fixed as aahIOSvrSvc, and it should not be
changed. Only the Historian Server Node name has to be configured.
1. Enter or browse to the primary Historian machine from the Server node.

Figure 4-1. HistorianIOServerService Object General Tab

InFusion SCADA Historian Synchronization User’s Guide – B0750BX Rev B

28 4. Supported Application Objects

2. Click the UDAs tab. On this tab:

Figure 4-2. HistorianIOServerService Object UDAs Tab

a. The default myIndex value is shown as 1 for every instance. This

needs to be incremented for each new instance of the respective
Historian.
The following table describes the myIndex values for the
$HistoryIOServerService instances:

Instance Name myIndex value

aahIOsvrsvc 1
aahIOsvrsvc1 2
aahIOsvrsvc2 3
aahIOsvrsvc3 4

b. myInSQLSyncBat is not used.

c. Select the myPrimaryFile UDA and provide the path to the primary
file shared on the primary Historian machine.
3. Similarly, configure the aahIOSvrSvc objects as required. (For example,
for redundant machines, configure aahIOSvrcSvc1 object; and for the four
parallel Historians, configure aahIOSvrSvc2 and aahIOSvrSvc3 objects,
respectively).

Note Ensure that the Historian Sync application is running while performing
the above actions. To run the application, click Start > Program Files >
Historian Sync > Shortcut to HistSync.bat.

Note The network path must be shared with full Read/Write permissions to
allow the execution of the above steps.

InFusion SCADA Historian Synchronization User’s Guide – B0750BX Rev B

 4. Supported Application Objects 29

$PrimaryHistPing Object
This object plays a very important role in InFusion SCADA software. The
name of the instance of this object should be specified as Hist1Ping. The basic
function of this Object is to monitor the Network Status of the Primary
Historian and to create database tables for InFusion SCADA software. The
Object Health Status is coupled with SCADAWinPlatform.
The HistoryShares UDA in the NetworkMonitor.HIST1 object must be
mapped to a file share on each History Server, where the History File name is
to be saved. Typically this is mapped to a directory like:
\\SERVERNAME\Primary
For Example:
\\Hist1\primary
The History object maintains a “PRIMARY” file on each history server that is
used by the Historian Sync task. Hence, this path is used to specify a file share
where the file is located on each server. The file share MUST have read/write
permissions (that is, full control), but only on that single file.
Following is an example of Hist1Ping object configuration:
1. In Figure 4-3, there are two history servers (Hist1 and Hist2) along with
the file share for each. The remaining two servers (#3 and #4) do not exist.

Figure 4-3. HIST 1Ping Object

2. HistoryNames UDA shall be Hist1 and Hist2 and so forth.

3. Primary UDA shall be the Primary Historian machine name, for example,
Hist1.

InFusion SCADA Historian Synchronization User’s Guide – B0750BX Rev B

30 4. Supported Application Objects

Note In order for the PrimaryHistPing object to function properly, all the four
Historians (Hist1, Hist2, Hist3, and Hist4) should be configured.

$SecondaryHistPing Object
The Role and Purpose of this object is same as that of the $PrimaryHistPing
Object, but this object does not create Database Tables. The instance of this
object should be named as Hist2Ping.
The Server name must be entered in NodeName, and this is the only
configuration to be done.
Same procedure is to be followed to configure Hist3Ping (if required), and
Hist4Ping (if required) Objects.

$SCADAWinPlatform Object

Removing References to History in Galaxy

The Historian Synchronization application uses IDAS for data collection,
instead of MDAS. Hence, all references to the Historian must be removed in
the Platform and the Engine. It is also recommended that the Store & Forward

InFusion SCADA Historian Synchronization User’s Guide – B0750BX Rev B

 4. Supported Application Objects 31

fields be left blank. These changes are best done on the Project
$SCADAWinPlatform.
1. On the General tab of the Project $SCADAWinPlatform, clear the
History store forward directory field, and set the Lock on the directory
as shown Figure 4-4.

Figure 4-4. SCADAWinPlatform

InFusion SCADA Historian Synchronization User’s Guide – B0750BX Rev B

32 4. Supported Application Objects

2. On the Engine tab, remove any reference to the Historian. Deselect the
check box Enable Storage to Historian and Lock the History control
group as shown in Figure 4-5.

Figure 4-5. SCADAWinPlatform Engine Tab

Identifying Historians in Project

$SCADAWinPlatform
Up to four historian names can be specified in the project
$SCADAWinPlatform. These historians are identified in the following UDAs
on the $SCADAWinPlatform:

UDA Description
SQLServerName The name of the primary Historian
SQLServerName1 The name of the first Historian
SQLServerName2 The name of the second Historian
SQLServerName3 The name of the third Historian

Each entry is the Network name of the SQL Server, or empty if there is no SQL
Server.

InFusion SCADA Historian Synchronization User’s Guide – B0750BX Rev B

 4. Supported Application Objects 33

A typical configuration would be:

SQLServerName Hist1
SQLServerName1 Hist2
SQLServerName2 Hist3
SQLServerName3 Hist4

This would allow for a primary historian (Hist1) and a backup historian
(Hist2).
Also, be sure to configure the SQLUserID (the SQL Server User ID) and the
SQLUserPW (the SQL Server Password) in the Project
$SCADAWinPlatform.
Note that the historian requires that all servers have the same SQL User Name
(that is, “sa”) and password.
Figure 4-6 illustrates a typical setup of the Project $SCADAWinPlatform
Object:

Figure 4-6. Project $SCADAWinPlatform Object

Here:
1. SQLServerName should be Master Historian machine name. For example,
Hist1.

InFusion SCADA Historian Synchronization User’s Guide – B0750BX Rev B

34 4. Supported Application Objects

2. Similarly, SQLServerName1, SQLServerName2 (If configuring 3rd

Historian), SQLServerName3 (If configuring 4th Historian) should be the
backup.
3. As per the user’s requirement, SQLServer primary can be any Historian
Server (as Master Historian) and SQL Server user name and password
should be same as configured in the SQL server configuration.
4. RedundantHistory UDA value should be “1”.

$SCADAEngine Object
1. On the Project Engine template, deselect the check box Enable Storage to
Historian, and lock the History control group, as shown in Figure 4-7.

Figure 4-7. SCADA Engine Object General Tab

2. Also, remove any Historian name.

3. Save the templates and allow the changes to propagate through any
instances.

InFusion SCADA Historian Synchronization User’s Guide – B0750BX Rev B

 35

A P P E N D I X A

Licensing

This chapter discusses the license related aspects of the Historian

Synchronization application.

Contents
• InFusion Historian License
• InFusion SCADA Historian Synchronization License

InFusion Historian License

Each Historian in the redundant configuration must be licensed separately.
Note that the historians cannot share a common license, and each ArchestrA
Historian product must be licensed as a separate complete Historian license.

InFusion SCADA Historian Synchronization

License
Users must install InFusion SCADA Historian Synchronization software
license before they can use the Historian Sync application. The licenses are
updated through the License Manager Application.
Even though the users can access the Historian Sync application without a
valid license, if a valid license is not present, then the synchronization process
is not started by clicking the Start button.
To update the license key, open License Manager application (Start >
Programs > Invensys > InFusion SCADA > LicenseManager) and enter the
valid key in the Historian Synchronization License Key field. After that, you
can validate the license key by clicking the Validate button.

InFusion SCADA Historian Synchronization User’s Guide – B0750BX Rev B

36 A. Licensing

InFusion SCADA Historian Synchronization User’s Guide – B0750BX Rev B

 37

Index
A
App Servers 17
Application Server 2
Audience v

B
Before v

C
Creating IDAS 11

D
Data Acquisition 21
DBLogger 3
DDESuiteLink 27
Diagnostic 11

E
Engineering Unit 19
Execution 25

F
failover 3
FSGateway 3, 8, 11

H
Historian Sync task 29

I
IDAS 8, 11, 15, 21, 30
Industrial Application Server 11
InSQL 12
IsHistory 18

L
License 35

M
Management Console 21
MDAS 11, 30

N
network path 28
Network Status 29
New I/O Server 13

O
On Demand file 6
OnDemand Synchronization 25
on-demand Synchronization 7

InFusion SCADA Historian Synchronization User’s Guide – B0750BX Rev B

38 Index

P
Parallel Collection 2
Primary File 6
Project $SCADAWinPlatform 31, 32, 33

S
SCADAAnalogDevice 18
SCADADiscreteDevice 18
SCADAEngine 34
SCADAWinPlatform 29
SMC 8
Storage Method 20
SuiteLink 13

T
timezone 6

W
Wonderware Documentation vi

InFusion SCADA Historian Synchronization User’s Guide – B0750BX Rev B

 Index 39

InFusion SCADA Historian Synchronization User’s Guide – B0750BX Rev B

Invensys Operations Management
5601 Granite Parkway Suite 1000
Plano, TX 75024
United States of America
http://www.iom.invensys.com

Global Customer Support

Inside U.S.: 1-866-746-6477
Outside U.S.: 1-508-549-2424 or contact your
local Invensys representative.
Website: http://support.ips.invensys.com