Proficy* Historian - GE Customer Center

Proficy* Historian - GE Customer Center

Proficy* Historian

O P C H D A S

E R V E R

G

U I D E

V e r s i o n 6 . 0

J u n e 2 0 1 5

Disclaimer of Warranties and Liability

The information contained in this manual is believed to be accurate and reliable. However, GE Intelligent Platforms,

Inc. assumes no responsibilities for any errors, omissions or inaccuracies whatsoever. Without limiting the foregoing,

GE Intelligent Platforms, Inc. disclaims any and all warranties, expressed or implied, including the warranty of merchantability and fitness for a particular purpose, with respect to the information contained in this manual and the equipment or software described herein. The entire risk as to the quality and performance of such information, equipment and software, is upon the buyer or user. GE Intelligent Platforms, Inc. shall not be liable for any damages, including special or consequential damages, arising out of the use of such information, equipment and software, even if

GE Intelligent Platforms, Inc. has been advised in advance of the possibility of such damages. The use of the information contained in the manual and the software described herein is subject to GE Intelligent Platforms, Inc. standard license agreement, which must be accepted by the buyer or user before the use of such information, equipment or software.

Trademark Notices

© 2015, General Electric Company. All rights reserved.

Proficy is a trademark of GE Intelligent Platforms, Inc., a wholly-owned subsidiary of General Electric Company.

* Indicates a trademark of General Electric Company and/or its subsidiaries.

All other trademarks are the property of their respective owners.

All other product names and marks identified throughout this book are trademarks or registered trademarks of their respective companies. They are used throughout this book in editorial fashion only. No such use, or the use of any trade name, is intended to convey endorsement or affiliation.

No part of this publication may be reproduced in any form, or stored in a database or retrieval system, or transmitted or distributed in any form by any means, electronic, mechanical photocopying, recording or otherwise, without the prior written permission of GE Intelligent Platforms. Information contained herein is subject to change without notice.

We want to hear from you. If you have any comments, questions, or suggestions about our documentation, send them to the following email address: [email protected]

Table of Contents

Historian OPC HDA Server .............................................................................................................. 1

Reference Documents .................................................................................................................. 1

Getting Started: Historian HDA Server ............................................................................................. 1

Overview ....................................................................................................................................... 2

Features of the Historian OPC HDA Server ................................................................................. 3

Setting up the Historian OPC HDA Server ................................................................................... 3

HDA Server Configuration ................................................................................................................ 3

Historian OPC HDA Server Configuration .................................................................................... 3

Historian OPC HDA Server License ............................................................................................. 4

Historian OPC HDA Server supported attributes ......................................................................... 4

Historian OPC HDA Server supported data types ........................................................................ 5

Historian OPC HDA Server supported quality values .................................................................. 7

Setting up the Windows XP or Vista firewall for use with remote OPC servers ........................... 8

Connecting and Disconnecting from the OPC HDA Server ....................................................... 12

Running Multiple Clients ............................................................................................................. 13

Tested OPC HDA Clients ....................................................................................................... 13

Filtering OPC HDA Server Browser............................................................................................ 13

How Do I ......................................................................................................................................... 14

Configure OPC HDA Server - Specific DCOM Settings ............................................................. 14

DCOM Settings ....................................................................................................................... 15

System-wide COM/DCOM Limits Settings ............................................................................. 15

For Windows XP and Windows Vista: .................................................................................... 16

OPC Server-specific DCOM Settings ..................................................................................... 16

In Windows 2003 .................................................................................................................... 17

In Windows XP, Windows Vista, Windows 7, and Windows Server 2008 ............................. 18

Trace Logging OPC HDA Server Communications .................................................................... 19

iii

HDA Server

Example Trace Log File .............................................................................................................. 20

Browse large number of tags ...................................................................................................... 21

Troubleshooting Historian OPC HDA Server ................................................................................. 21

iv

Historian OPC HDA Server

The Historian OPC HDA Server Manual provides you with information on the following:

• Getting Started: Historian HDA Server

• Setting up the Historian HDA Server

• Historian HDA Server Configuration

• Configure OPC HDA Server - Specific DCOM Settings

Reference Documents

For related information about Historian, refer to the following documents:

• Getting Started with Historian

• Using the Historian Administrator

• Using the Historian Excel Add-In

• Migrating Advanced and Classic Historian Data

• Using the Historian OLE DB Provider

• Historian Alarm and Event Collector

• Historian Software Development Kit (SDK) Online Help System

Getting Started: Historian HDA Server

The Proficy Historian OPC HDA Server reads the raw data stored in Proficy Historian and sends it to the interested OPC HDA clients. OPC HDA compliant clients can connect to the Proficy Historian

HDA Server to acquire and analyze data.

The Proficy Historian OPC HDA Server complies with OPC Server HDA 1.20 standards. The Proficy

Historian OPC HDA server dynamically updates when the tags are added and/or deleted in Proficy

Historian Server.

IMPORTANT: OPC HDA clients can browse data from only one Historian server at a time. If you want to connect to another Historian server, you must disconnect all OPC HDA clients, re-configure the Historian OPC HDA Server, and then reconnect OPC HDA clients.

NOTE: Proficy Historian OPC HDA Server supports only synchronous read raw interface in this release.

1

HDA Server

Overview

OPC Historical Data Access (HDA) is used to retrieve and analyze historical process data which is typically stored in a Process Data Archive, database, or RTU. OPC HDA is a widespread standard used to access historical process data. Historical Data is used to analyze the following: analysis: trending, fault prediction, performance assessment, and so on.

With OPC HDA, the exchange of historical data between an application and any data archive is consistent. In other words, OPC HDA client applications that implement trends, reports, or spreadsheets can retrieve archived process data from Historian.

OPC HDA specifications are built upon Microsoft's OLE (Object Linking and Embedding) and DCOM

(Distributed Component Object Model) technologies. OPC is fully endorsed by Microsoft.

OPC HDA is created to allow different automation applications to communicate with each other based on the historical data, regardless of the manufacturer. This allows greater flexibility and reliability when setting up automation systems.

For manufacturers of OPC-compliant applications, it simplifies the development process since they have to create only one I/O interface. For consumers of OPC-compliant applications, it increases the flexibility of their automation process—they are no longer limited to communicating with devices specified by the applications' developers.

• Multiple OPC HDA compliant client applications can communicate with an OPC HDA server simultaneously.

• DCOM client and server software programs can be configured to run on the same computer node or can be distributed across a network of computers.

• OPC HDA servers provide a common view of automation information managed by the system for which the server was written.

For more information on the OPC HDA in general, visit the OPC Foundation's web site at http://www.opcfoundation.org/

2

Historian OPC HDA Server

Features of the Historian OPC HDA Server

The main features provided by the Proficy Historian OPC HDA Server include:

1. Support for the OPC HDA Server specification (1.2.0) for Historian HDA Server.

2. Browsing all the tags available on the Historian Server.

3. Converting Historian timestamps, data types, and qualities to OPC HDA timestamps, data types, and qualities.

4. Automatically reconnecting to the Historian Server (Archiver) when connection is lost.

Setting up the Historian OPC HDA Server

Setting up and using Historian OPC HDA Server involves the following steps:

1. Install the Historian OPC HDA Server. For more details, refer to the Installing the Historian

HDA Server section.

2. Start the Historian Non-Web Administrator.

NOTE: You must install Historian Non-Web Administrator in order to set up the OPC HDA

Server.

3. Open the Historian Administrator Login dialog box. If Historian is already open, double-click on the Main button to open the Historian Administrator Login dialog box.

4. Click the Browse for Server button.

5. From the Servers list, select the Historian server you want to configure .

6. Click Set Selected Server as Target of HDA Server, and then click OK.

The selected server is set as the target Historian server.

NOTE: You must disconnect and reconnect all HDA clients before connecting to Historian

OPC HDA Server.

7. Configure any external OPC HDA Clients to connect to the Proficy Historian HDA Server.

The Proficy OPC HDA Server uses Proficy.Historian.HDA as the ProgID (Program ID).

HDA Server Configuration

Historian OPC HDA Server Configuration

After installation, the Proficy Historian OPC HDA Server runs as an independent executable file. For more information about configuring Proficy Historian HDA Server, refer to the Setting up the

Historian HDA Server.

3

HDA Server

Historian OPC HDA Server License

A valid license is required for Historian OPC HDA Server. If you do not have a valid license, Historian

OPC HDA Server cannot connect to the Proficy Historian.

Whenever Historian OPC HDA Server attempts to connect to the Proficy Historian, Historian Server verifies the Historian OPC HDA Server license.

NOTE: Historian OPC HDA Server does not consume a "Client Access License (CAL)" when

Historian OPC HDA Server connects to the Proficy Historian.

If the Historian OPC HDA Server license is available, then the Historian OPC HDA Server can connect and read the raw data from the Proficy Historian. A message is logged into the Historian OPC

HDA Server trace log file. By default, you can view the log file (that is, .html file) in C:\Proficy

Historian Data\LogFiles. For example:

4/6/2009 4:32:05 PM HDA Client is connecting

4/6/2009 4:32:06 PM Connected to Historian server : [3.212.219.88]

4/6/2009 4:32:06 PM HDA Client Connected

4/6/2009 4:32:11 PM HDA Address Space Created

If the Historian OPC HDA Server license is not available, then the Historian OPC HDA Server cannot connect to Proficy Historian. A message is logged into the Historian OPC HDA Server trace log file.

By default, you can view the log file (that is, .html file) in C:\Proficy Historian Data\LogFiles. For example:

4/6/2009 4:29:22 PM HDA Client is connecting

4/6/2009 4:29:31 PM ===========================================

Proficy.Historian.HDAServer.ApiConnectionInterface

OPC HDA Server not Licensed : Please make sure you have license for HDA server. Try re-starting Archiver and then connect HDA clients again.at HistorianApiConnection.ApiConnection.ApiConnectClient(String nodeName, String userName, String passWord) at HDAPlugin.AppPlugin..ctor(PluginUse mode)

==========================================================

4/6/2009 4:30:02 PM HDA Client Disconnected

NOTE: After installing a valid license, you must restart the Archiver and then reconnect the OPC

HDA clients to Proficy Historian OPC HDA Server.

To purchase a valid license or If you have any questions about Proficy licensing call the GE Intelligent

Platforms support line at 1-800-433-2682. GE Intelligent Platforms representative will direct your call to the correct resource.

Historian OPC HDA Server supported attributes

The following table lists the Historian OPC HDA Server supported attributes:

4

Historian OPC HDA Server

Historian

Property

Type

Data Type

Historian OPC HDA

Attribute

Data

Type

Description

OPCHDA_DATA_TYPE Int16 Specifies the data type for the item. For more information, refer to the

Historian OPC HDA

Server supported data types section.

Tag

Description

OPCHDA_DESCRIPTION String Describes the item.

Engineering

Units

OPCHDA_ENG_UNITS String Specifies the label to use in displays to define the units for the item

(For example, kg/sec).

Archiving

Item ID

OPCHDA_ARCHIVING Boolean Indicates whether

Historian is recording data for this item. (Zero means it is not recording data)

OPCHDA_ITEMID String Specifies the Item id.

This is used to allow filtering in the

CreateBrowse method.

Historian OPC HDA Server supported data types

The following table lists the mapping of data types between Historian and the OPC HDA Server.

Proficy Historian Data Type OPC HDA Data Type

5

HDA Server

Proficy Historian Data Type

Single Integer

Double Integer

Quad Integer

Unsigned Single Integer

Unsigned Double Integer

Unsigned Quad Integer

Byte

Boolean

Single Float

Double Float

Variable String

Fixed String

OPC HDA Data Type

VT_I2 &endash; 16 bit signed integer

VT_I4 - 32 bit signed integer

VT_I8 - 64 bit quad integer

VT_UI2 - 16 bit unsigned single integer

VT_UI4 - 32 bit unsigned single integer

VT_UI8 - 62 bit quad integer

VT_I1

VT_BOOL

VT_R4 - 32 bit float

VT_R8 - 64 bit double float

VT_BSTR

VT_BSTR

6

Historian OPC HDA Server

Proficy Historian Data Type

Date

Blob

OPC HDA Data Type

VT_DATE

VT_BSTR

Historian OPC HDA Server supported quality values

The following table lists the mapping of quality values between Historian and the OPC HDA Server.

Proficy Historian

Quality

OPC HDA Quality Description

ihOPCGood OPC_QUALITY_GOOD ihOPCBad ihOPCUncertain

OPC_QUALITY_BAD

OPC_QUALITY_UNCERTAIN

Indicates there is no need for inspection.

This quality is returned for the tags that have all the values archived properly.

Indicates a need for attention. This quality is returned for the tags that had problems during the collection.

Indicates a need for inspection. This quality is returned when the data collection time is low and when there is no specific quality value.

7

HDA Server

Proficy Historian

Quality

OPC HDA Quality

ihOPCNA OPC_QUALITY_BAD

Description

Indicates a need for attention.

Setting up the Windows XP or Vista firewall for use with remote OPC servers

If Firewall security is enabled on Windows XP or Windows Vista, you may need to modify or add items to the Exceptions list.

GE Intelligent Platforms recommends that you enter these settings on the local machine running

Historian, as well as on the remote machine that has the OPC server you want to use.

To modify Windows Firewall settings:

1. Log into the Windows operating system with an Administrator account.

2. Open the Control Panel and double-click Windows Firewall. The Windows Firewall dialog box appears. For the Windows Vista operating system, you also need to click the "Allow a program through Windows firewall" option.

3. Click the Exceptions tab and make sure that the File and Printer Sharing check box is selected. The following figure shows an example of this dialog box in Microsoft Windows

XP.

8

Historian OPC HDA Server

4. Click the Add Port button. The Add a Port dialog box appears. The following figure shows an example of this dialog box in Microsoft Windows XP.

9

HDA Server

5. In the Name field, enter a name for the port.

6. In the Port Number field enter 135.

7. Select the TCP option.

8. Click OK to save your changes.

9. The port name you entered is now listed with its check box selected.

10. Select the Add Program button. The Add a Program dialog box appears.

11. Click the Browse button. A Browse dialog box appears.

10

12. Navigate to the System32 folder. This folder is found under the operating system folder

(usually Windows or WINNT).

13. In the System32 folder, select the OPCENUM.exe file, and then click the Open button.

In the Add a Program dialog box, the path field displays the full path of the OPCENUM.exe file.

Historian OPC HDA Server

14. Click OK.

OPCENUM.exe should now be listed in the Exceptions list with its check box selected.

11

HDA Server

15. Complete steps 9-13 for each OPC server that you want to access.

NOTES:

If any OPC server that you want to use is a dll surrogate (an in-process dll and not an .exe),

you must add \system32\dllhost.exe into the Exceptions list.

You must also add the GE Intelligent Platforms OPC Client driver by adding the file

OPCDrv.exe into the Exceptions list.

OPCENUM must reside on the remote machine with the OPC server. While most OPC Server

applications install and register this file, some do not. You can download this file from www.opcfoundation.org. Currently it is contained within the OPC Core Components 2.00

Redistributable 2.30.msi file. After you download OPCENUM, run the .msi file.

Connecting and Disconnecting from the OPC HDA Server

When an OPC HDA Client tries to connect to the Historian OPC HDA Server, and if an instance of

HDA is not available, then an instance of a Historian OPC HDA server is started and the client connects to the running instance of the server.

12

Historian OPC HDA Server

The Historian OPC HDA Server continues to run as long as there are clients connected to it. If there are no clients connected, then the OPC HDA Server shuts down immediately.

NOTE: After installation, the Historian OPC HDA Server is typically referenced by an OPC client by its ProgID (program ID) Proficy.Historian.HDA.

Running Multiple Clients

The Proficy Historian OPC HDA Server supports multiple instances of OPC HDA clients without any additional configuration. Refer to the OPC HDA Client documentation for more information on performing communication and control operations.

Tested OPC HDA Clients

OPC HDA Server has been tested with:

• OPC Foundation HDA Sample client. You can download this client from www.opcfoundation.org

• Advosol HDA test client. You can download this client from http://www.advosol.com/tfreetools.aspx

Filtering OPC HDA Server Browser

Proficy Historian OPC HDA Server supports filtering on the following attributes:

• OPC_HDA_ITEM_ID

• OPC_HDA_DESCRIPTION

• OPC_HDA_DATA_TYPE

• OPC_HDA_ENGINEERING_UNITS

The following table provides the correspondence between OPC HDA attributes and Proficy Historian tag attributes, and shows the supported operators:

Historian OPC HDA

Attribute

OPCHDA_DATA_TYPE

Supported Operators Historian Property

Type

OPC_HDA_EQUAL_TO Data Type

OPCHDA_DESCRIPTION OPC_HDA_EQUAL_TO Tag Description

13

HDA Server

Historian OPC HDA

Attribute

OPCHDA_ENG_UNITS

Supported Operators Historian Property

Type

OPC_HDA_EQUAL_TO Engineering Units

OPCHDA_ITEMID OPC_HDA_EQUAL_TO Item ID

IMPORTNAT: OPC HDA Server filter strings are case sensitive.

Proficy Historian HDA Server supports filtering on OPC_HDA_ARCHIVING attribute, but the filtering on OPC_HDA_ARCHIVING attribute should not be used by the clients, since the

OPC_HDA_ARCHIVING attribute value is always true.

You can refer to the log file to trace a history of communication events dealt with by the Historian

OPC HDA Server. You can also turn on the debug mode to more know more details in the log file.

If an invalid filter is passed by a HDA Client, then the Proficy Historian HDA Server returns all the available items in the address space.

Tips:

The wildcard character (*) will return all the tags.

The wildcard (key*) will return tags which begins with “key”

The wildcard (key) returns an exact tag name.

How Do I

Configure OPC HDA Server - Specific DCOM Settings

Historian OPC HDA Server supports DCOM (Distributed Component Object Model) to browse the

Historian OPC HDA Server remotely. If you want to grant only certain users permission to launch or access the remote Historian OPC HDA Server, you can use the Windows utility, DCOMCNFG.EXE for configuring DCOM applications. DCOMCNFG.EXE is usually located in your operating system’s

\system32 folder.

When OPC Servers register, they set up initial custom DCOM security settings to enable users on the network to access and launch the Server. On large networks, it is recommended that you modify these settings to avoid confusion and inadvertent changes to a running OPC Server.

If Firewall security is enabled on Windows XP or Vista, you must also modify or add items to the

Exceptions list. Refer to Setting Up the Windows XP or Vista Firewall for Use with Remote OPC

14

Historian OPC HDA Server

Servers.

NOTES:

GE Intelligent Platforms recommends that all users that need to access remote OPC Servers

be members of the Administrators group. To facilitate this, GE Intelligent Platforms recommends creating a users group to contain individual users that need to access remote

OPC servers.

To make any OPC HDA Client / OPC HDA Server application work via DCOM, changes

need to be made on both sides, especially if you intend to use Asynchronous I/O communications.

OPCENUM must reside on the remote machine with the OPC server. While most OPC Server

applications install and register this file, some do not. You can download this file from www.opcfoundation.org. Currently, it is contained within the OPC Core Components 2.00

Redistributable 2.30.msi file. After you download OPCENUM, run the .msi file.

This section applies to OPC HDA servers that need to use DCOM communications,

regardless of whether the OPC server uses Serial or Ethernet devices.

If OPC communications is confined to a single machine (that is, using COM, but not DCOM),

it continues to work properly without making changes to DCOM settings.

If Historian OPC HDA Server and OPC HDA Client are on same machine, then you do not

need to change your DCOM settings.

If this is the first time you are connecting to (or allowing connections from) other machines on the network, you must run the Windows Network Wizard (from Start > Control Panel) to set up your computer to run on your network. This allows you to share resources on your computer with other computers on your network. It is recommended that you run the Network

Setup Wizard before modifying the DCOM settings.

DCOM Settings

The following procedures provide general guidelines for configuring DCOM settings. Differences between Windows 2003, Windows XP, and Windows Vista are noted.

To launch the DCOM configurator:

1. From the Start menu, select or type Run. The Run dialog box appears.

2. Type dcomcnfg and click OK. The Component Services dialog box appears.

System-wide COM/DCOM Limits Settings

This procedure modifies the system-wide DCOM settings for the computer on Windows XP and

Windows Vista operating systems. When these steps are implemented, they apply to all programs that use COM/DCOM communications on the computer.

IMPORTANT: Be careful when making any system-wide security changes. Any inadvertent changes may affect the entire system and may cause some or all programs to stop working.

15

HDA Server

For Windows XP and Windows Vista:

To update system-wide COM/DCOM limits settings:

1. On the Component Services dialog box, expand Component Services, then expand the

Computers item.

2. Right-click My Computer and choose Properties. The My Computer Properties dialog box appears.

3. Click the COM Security tab. There are four permissions on this dialog box.

You may need to make changes to the Edit Limits… for Access Permissions and Launch and

Activation Permissions.

Do not change the Edit Default… settings, since this will change the default settings for all programs and applications running on the computer.

4. Click Access Permissions > Edit Limits… The Access Permission dialog box appears. i.Select the user labeled ANONYMOUS LOGON, and then select the Allow check box for Remote

Access.

NOTE: This setting is necessary for applications that use OPCenum.exe to function and also for some OPC Servers and OPC Clients that set their DCOM ‘Authentication

Level’ to ’None’ to allow anonymous connections. If you do not use such applications, you may not need to enable remote access for anonymous logon users.

ii. Select the user labeled Everyone, and then select the Allow check box for Remote

Access.

IMPORTANT: Since “Everyone” includes all authenticated users, it is recommended to add these permissions to a smaller subset of users. One way of doing this is to create a Group named “OPC” and add all user accounts to this Group that will access any

OPC server. Then substitute “OPC” everywhere that “Everyone” appears in the entire

DCOM configuration dialogs.

iii. Click OK to close the Access Permissions dialog box and return to the My Computer

Properties dialog box.

5. Click Launch and Activation Permissions > Edit Limits… The Launch Permission dialog box appears.

For each user or group (preferably add the “OPC” group) that needs to launch or activate the

OPC server, or participates in OPC / DCOM communications, make sure that the Local

Launch, Remote Launch, Local Activation, and Remote Activation check boxes are selected.

6. Click OK to save your changes, then click OK again to save and close the My Computer

Properties dialog box.

OPC Server-specific DCOM Settings

The following procedures detail the OPC HDA server-specific COM/DCOM settings on all supported

Windows operating systems. You must change the OPC HDA server settings so remote users can access the OPC HDA server as an OPC Data Access Server.

GE Intelligent Platforms recommends that all users requiring access to remote OPC HDA servers be members of the Administrators group.

IMPORTANT: Since the “Everyone” group includes all authenticated users, it is recommended to add these permissions to a smaller subset of users.

16

Historian OPC HDA Server

GE Intelligent Platforms recommends creating a group to contain individual users that need to access remote OPC HDA Servers. GE Intelligent Platforms also recommends that all users who require access to remote OPC HDA Servers be members of the Administrators group.

To modify driver-specific DCOM settings:

In Windows 2003

1. Access the DCOM configurator (dcomcnfg.exe). The Component Services dialog box appears.

2. Expand the Component Services item, then expand the Computers item, and then expand the

My Computer item.

3. Select the DCOM Config object. A list of applications displays.

4. Right-click the Proficy Historian HDA server 3.5 and choose Properties. The Proficy

Historian HDA server 3.5 Properties dialog box appears.

5. Click the General tab. The Authentication Level should be left as “Default”. This uses the default authentication rules that are set in the system-wide DCOM settings.

6. Click the Location tab and make sure that the Run Application on this computer check box is selected.

7. Click the Security tab and select the Customize option for each of the permissions in this dialog box and edit them as described in the following steps.

8. In the Launch Permissions area, click Edit. The Launch Permissions dialog box appears.

9. Click the Add button. The Select Users and Groups dialog box appears.

10. Click the Advanced Button. The Select Users and Groups dialog box appears.

11. Click the Find Now button. In the search results, select the OPC group and click OK. The

Select Users and Groups dialog box displays the OPC group.

12. Click OK to return to the Launch Permission dialog box. The OPC group is displayed in the

Group or user names list.

13. Select the OPC group and select the Allow check box for Launch Permission.

14. Click OK to return to the Proficy Historian HDA server 3.5 Properties dialog box.

15. In the Access Permissions area, click Edit. The Access Permission dialog box appears.

16. Click the Add button. The Select Users and Groups dialog box appears.

17. Click the Advanced Button. The Select Users and Groups dialog box appears.

18. Click the Find Now button. In the search results, select the OPC group and click OK. The

Select Users and Groups dialog box displays the OPC group.

19. Click OK to return to the Access Permission dialog box. The OPC group is displayed in the

Group or user names list.

20. Select the OPC group and select the Allow check box for Access Permission.

21. Click OK to return to the Proficy Historian HDA server 3.5 Properties dialog box.

22. In the Configuration Permissions area, click Edit. The Change Configuration Permission dialog box appears.

23. Click the Add button. The Select Users and Groups dialog box appears.

24. Click the Advanced Button. The Select Users and Groups dialog box appears.

17

HDA Server

25. Click the Find Now button. In the search results, select the OPC group and click OK. The

Select Users and Groups dialog box displays the OPC group.

26. Click OK to return to the Change Configuration Permission dialog box.

27. Select the OPC group and select the Allow check boxes for Full Control and Read.

28. Click OK to return to the Proficy Historian HDA server 3.5 Properties dialog box.

29. Click OK.

30. Repeat steps 2 through 29 for each OPC server you need to access remotely.

31. When you are done, close the Component Services dialog box.

In Windows XP, Windows Vista, Windows 7, and Windows Server 2008

1. Access the DCOM configurator (dcomcnfg.exe). The Component Services dialog box appears.

2. Expand the Component Services item, then expand the Computers item, and then expand the

My Computer item.

3. Select the DCOM Config object. A list of applications displays.

4. Right-click the Proficy Historian HDA server 3.5 and choose Properties. The Proficy

Historian HDA server 3.5 Properties dialog box appears.

5. Click the General tab. The Authentication Level should be set to “Default,” if it is not already.

This uses the default authentication rules that are set in the system-wide DCOM settings.

6. Click the Location tab and make sure that the "Run Application on this computer" check box is selected.

7. Click the Security tab and select the Customize option for each of the permissions in this dialog box and edit them as described in the following steps.

8. In the Launch and Activation Permissions area, click Edit. The Launch Permission dialog box appears for Windows XP, or the Launch and Activation Permission dialog box appears for

Windows Vista.

9. Click the Add button. The Select Users or Groups dialog box appears.

10. Click the Advanced Button. Another Select Users or Groups dialog box appears.

11. Click the Find Now button. In the search results, select the OPC group and click OK. The

Select Users or Groups dialog box displays the OPC group.

12. Click OK to return to the Launch Permission dialog box. The OPC group is displayed in the

Group or user names list.

13. Select the OPC group and then select the Allow check boxes for Local Launch, Remote

Launch, Local Activation, and Remote Activation permissions.

14. Click OK to return to the Proficy Historian HDA server 3.5 Properties dialog box.

15. In the Access Permissions area, click Edit. The Access Permission dialog box appears.

16. Click the Add button. The Select Users or Groups dialog box appears.

17. Click the Advanced Button. Another Select Users or Groups dialog box appears.

18. Click the Find Now button. In the search results, select the OPC group and click OK. The

Select Users or Groups dialog box displays the OPC group.

19. Click OK to return to the Access Permission dialog box. The OPC group is displayed in the

Group or user names list.

18

Historian OPC HDA Server

20. Select the OPC group and then select the Allow check boxes for Local Access and Remote

Access permissions.

21. Click OK to return to the Proficy Historian HDA server 3.5 Properties dialog box.

22. In the Configuration Permissions area, click Edit. The Change Configuration Permission dialog box appears.

23. Click the Add button. The Select Users or Groups dialog box appears.

24. Click the Advanced Button. Another Select Users or Groups dialog box appears.

25. Click the Find Now button. In the search results, select the OPC group and click OK. The

Select Users or Groups dialog box displays the OPC group.

26. Click OK to return to the Change Configuration Permission dialog box. The OPC group is displayed in the Group or user names list.

27. Select the OPC group and then select the Allow check boxes for Full Control and Read permissions.

28. Click OK to return to the Proficy Historian HDA server 3.5 Properties dialog box.

29. Click OK.

30. Repeat steps 2 through 29 for each OPC server you need to access remotely.

31. When you are done, close the Component Services dialog box.

Trace Logging OPC HDA Server Communications

NOTE: The Trace Logging feature is designed for use by support personnel only to assist in diagnosing issues with the Proficy Historian OPC HDA Server.

This feature logs communications with the Historian OPC HDA Server into a html file. Advanced users can use this log file to trace a history of communication events dealt with by the Historian OPC

HDA Server.

The Trace Log file is a simple html file and is placed in the Logfiles folder. By default, this is

C:\Proficy Historian Data\LogFiles.

The information logged includes:

• The date and time of the event occurred.

• Errors and Exceptions parameters passed by the clients

• The status of the client.

Use the following steps to turn on debug mode to find more information in the trace log file.

To turn on the debug mode:

1. From the Start menu, select Run and enter Regedit.

2. Open the following key folder

HKEY_LOCAL_MACHINECLASSES_ROOT\SOFTWARE\Intellution,inc\iHistoria n\HDAServer\.

NOTE: On a 64-bit Windows Operating System, open the following key folder

19

HDA Server

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\\Intellution,

Inc.\iHistorian\HDAServer\.

3. Double-click DebugMode DWORD value

4. Select Base as Decimal.

5. In the Value data field, type 255.

6. Click OK.

7. Close the Registry Editor and open the Proficy OPC HDA Server trace log file.

Example Trace Log File

The following messages illustrate the type of information that the trace log file provides.

---------

3/5/2009 10:12:19 AM HDA Client is connecting ...

3/5/2009 10:12:20 AM Connected to Historian server : [ES-4FCNR1S]

3/5/2009 10:12:20 AM HDA Client Connected

3/5/2009 10:12:21 AM HDA Address Space Created

3/5/2009 10:12:36 AM HDA Client Disconnected

3/5/2009 11:50:04 AM HDA Client is connecting ...

3/5/2009 11:50:05 AM Connected to Historian server : [ES-4FCNR1S]

3/5/2009 11:50:05 AM HDA Client Connected

3/5/2009 11:50:25 AM Historian Archiver : Tag Added [ES-4FCNR1S.Simulation00261]

3/5/2009 11:50:25 AM Historian Archiver : Tag Added [ES-4FCNR1S.Simulation00262]

3/5/2009 11:50:25 AM Historian Archiver : Tag Added [ES-4FCNR1S.Simulation00264]

3/5/2009 11:50:32 AM HDA Address Space Created

3/5/2009 11:50:59 AM Historian Archiver : Tag Added [ES-

4FCNR1S.SimulationString00001]

3/5/2009 11:51:25 AM Historian Archiver : Tag Added [ES-

4FCNR1S.SimulationString00002]

3/5/2009 11:51:25 AM Historian Archiver : Tag Added [ES-4FCNR1S.Ramp_20%Noise]

3/5/2009 11:51:25 AM HDA Client Disconnected

3/5/2009 2:34:27 PM HDA Client is connecting ...

3/5/2009 2:34:28 PM Connected to Historian server : [ES-4FCNR1S]

3/5/2009 2:34:28 PM HDA Client Connected

3/5/2009 2:34:28 PM HDA Address Space Created

3/5/2009 2:34:45 PM HDA Client Disconnected

3/5/2009 2:35:06 PM HDA Client is connecting ...

3/5/2009 2:35:07 PM Connected to Historian server : [ES-4FCNR1S]

3/5/2009 2:35:07 PM HDA Client Connected

3/5/2009 2:35:08 PM HDA Address Space Created

3/5/2009 2:35:08 PM HDA Address Space Created

3/5/2009 2:35:08 PM Invalid attribute at index [0]

3/5/2009 2:35:08 PM HDA Address Space Created

3/5/2009 2:35:08 PM Invalid type at index [0]

3/5/2009 2:35:08 PM HDA Address Space Created

3/5/2009 2:36:00 PM HDA Client is connecting ...

3/5/2009 2:36:01 PM Connected to Historian server : [ES-4FCNR1S]

3/5/2009 2:36:01 PM HDA Client Connected

3/5/2009 2:36:11 PM HDA Client is connecting ...

3/5/2009 2:36:11 PM HDA Client Connected

3/5/2009 2:36:12 PM HDA Address Space Created

3/5/2009 2:36:12 PM Invalid attribute at index [0]

3/5/2009 2:36:12 PM HDA Address Space Created

3/5/2009 2:36:12 PM Invalid type at index [0

---------

NOTE:

20

Historian OPC HDA Server

The Black color code indicates the status of the events.

The Blue color code indicates the status of the clients.

The Red color code indicates the Errors and Exceptions parameters passed by clients.

Browse large number of tags

Proficy Historian OPC HDA Server supports Dual Address Space Model: Hierarchical address space and Flat address space.

Hierarchical address space allows you to browse data from large numbers of collectors and tags without affecting the HDA server browse performance. Flat address space allows you to browse smaller number of tags. By default, the Flat address space is enabled.

If you want to browse large number of collectors and tags, then you must enable Hierarchical address space.

To enable Hierarchical address space:

1. On the Start menu, click Run, type Regedit, and then click OK. The Registry editor appears.

2. Open the following key folder HKEY_LOCAL_MACHINE\SOFTWARE\Intellution,

Inc.\iHistorian\HDAServer\.

NOTE: On a 64-bit Windows Operating System, open the following key folder

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\\Intellution,

Inc.\iHistorian\HDAServer\.

3. Create a new DWORD called "HierarchicalAddressSpace ".

4. In the Value data field, type 255 (to enable Flat address space, set this value to 0).

5. Click OK, and then close the Registry Editor.

6. Restart the Proficy Historian HDA server by disconnecting and reconnecting all HDA clients.

Troubleshooting Historian OPC HDA

Server

FAQ About Running a Historian OPC HDA Server

Question Answer

21

HDA Server

FAQ About Running a Historian OPC HDA Server

Answer Question

Can a Historian OPC

HDA server connect to more than one Historian

Server at a single time?

The Historian OPC HDA Server cannot connect to more than one Historian Server at a single time. If you want to connect to another Historian server, you must disconnect all OPC HDA clients, re-configure the Historian OPC HDA Server, and then reconnect OPC HDA clients.

How do I configure

Historian OPC HDA

Server?

The Historian OPC HDA Server works without configuration.

By default, the Historian OPC HDA Server will connect to the default Proficy Historian Server. Optionally, you can configure

Historian OPC HDA Server. For more information, refer to

Setting up the Historian OPC HDA Server

Does Historian OPC

HDA Server consume a

"Client Access License

(CAL)"

No. Historian OPC HDA Server does not consume a "Client

Access License (CAL)" whenever Historian OPC HDA Server connects to the Proficy Historian.

Can I view the Historian

OPC HDA Server trace log file?

Yes. By default, the Historian OPC HDA Server trace log file is located in C:\Proficy Historian Data\LogFiles.

Can I turn on the debug mode to get more information in the trace log?

Yes, you can turn on the debug mode to find more information in the trace log file. For more information, refer to the To turn on the debug mode section.

22

Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project