Updated the menu selections for Windows 7 and Windows Server 2008 for all proce-dures in this chapter.
Appendix B “DCOM Configuration”
Removed “Starting the DCOM Configuration Utility”.
Updated “Setting Default Properties” on page 57
Reference Documents
In addition to the information presented herein, you should be familiar with the following I/A Series documents:
AIM*AT Suite AIM API™ User’s Guide (B0193YN)
AIM*AT Suite AIM Installation Guide (B0193YM)
AIM*AT Suite NetAPI MFC Class User’s Guide (B0400BJ).
These are available on the I/A Series Electronic Documentation CD-ROM or DVD (K0173TQ or K0173WT) provided by the Foxboro business unit of Invensys. The latest revisions may also be available through the Global Customer Support at http://support.ips.invensys.com.
You should also reference the following OPC Foundation specifications:
OPC Data Access Custom Interface Standard V 2.05a and V 1.0a
OPC Historical Data Access Custom Interface Standard V 1.0
OPC Data Access 2.05a Automation Interface Standard.
Request For Comments
Please direct your comments and suggestions concerning the AIM*AT OPC Server software, other AIM*AT Suite products, and this user documentation to:
Global Customer Support Center B52-AA
Telephone: 1-866-746-6477 within the U.S. or 1-508-549-2424 outside the U.S.
For web assisted technical support, visit: http://support.ips.invensys.com.
1. Overview
This chapter introduces AIM*OPC Server software and describes how the server enables OPC clients to communicate with data servers to access real-time and historical data.
AIM*AT OPC Server
AIM*AT OPC Server software (OPC server) enables the transfer of data between OPC clients and the following systems:
I/A Series Application Workstations for real-time data
AIM*Historian for real-time data and process history In this document, these three sources are referred to as data servers.
Figure 1-1 illustrates how the OPC server functions as a gateway between OPC clients and data servers.
The OPC server communicates with data servers over TCP/IP using AIM*API software included with the product. The AIM*AT OPC Server software runs either on the same workstation as the data server or remotely on a Windows based workstation.
The AIM*AT OPC Server software features:
Full compliance with OPC Data Access Specification 2.05a and 1.0a
Full compliance with OPC Historical Data Access Specification 1.0
Read and write access to items configured within a data server
Access to multiple local and remote data servers
Automatic detection of available data servers
Automatic detection of available item IDs
Minimal configuration required following installation
Easy-to-use graphical configuration utility
Extensive error tracking and management
Matrikon™ OPC Explorer, a general purpose OPC client for testing and configuring the OPC server
Matrikon™ OPC Automation Component, a dynamically linked library enabling you to access OPC data from OPC client applications developed using automation tools such as Visual Basic™, VBA™, and VB Script™.
Figure 1-1. Data Transfer Between OPC Clients and Data Servers via the OPC Server
The OPC Standard
The OPC standard is designed to connect Windows® based applications with process control hardware and software applications. This open standard permits a consistent method of accessing field data that remains constant regardless of data type or source.
OPC servers use the Component Object Model (COM) to communicate with clients. This Microsoft® OLE technology permits a standard for real-time information exchange between software applications and process hardware to be defined.
OPC Data Access
The OPC Data Access (DA) standard was the first specification released by the OPC Foundation.
Its primary purpose is to enable the transfer of real-time data. The OPC server conforms to Ver-sions 2.05a and 1.0a of the OPC Data Access Specification. Refer to Appendix E “OPC Compli-ance” for a list of OPC DA interfaces supported by the OPC server.
OPC Client
OPC Historical Data Access
The OPC Foundation Historical Data Access (HDA) specification defines a consistent mechanism for communicating with process historians.
This specification is written for management information systems, expert systems, and other higher level applications that need to access historical data. A single client application designed to the HDA standard can connect to and retrieve data from any historian.
The OPC server conforms to Revision 1.0 of the OPC Historical Data Access Specification. Refer to Appendix E “OPC Compliance” for a list of OPC HDA interfaces supported by the OPC server.
2. System Requirements
This chapter lists AIM*AT OPC Server installation prerequisites.
The workstation on which you install the AIM*AT OPC Server must meet the following requirements:
Pentium® class processor, recommend 500 MHz or higher
128 MB of RAM
25 MB of available disk space.
One of the following operating systems:
Windows Server® 2008 R2
Windows® 7
Windows Server 2003 R2
Windows XP (Service Pack 3)
3. AIM*AT OPC Server Installation
This chapter provides procedures for installing the AIM*AT OPC Server Software and describes important files installed during server installation.
Overview
The OPC Server Software V3.4 is a complete installation of the OPC Server software:
The AIM*OPC Server components can be installed on a Windows based workstation or an I/A Series (Windows based) workstation.
The AIM*AT API Server can be installed on any I/A Series workstation.
The software install program detects the OPC server currently installed on the target station allowing you to abort the installation should you need to un-installed an earlier version of the OPC Server software. The installation of the OPC server also allows you to install an AIM*AT API Server component to an I/A Series workstation, if one is required.
Installing the AIM*AT OPC Server Software
To install the AIM*OPC Server Software, refer to the AIM*AT Suite Installation Guide (B0193YM, Rev. G or later).
Once the AIM*OPC Server software is installed then edit the DCOM settings, as described in Appendix B “DCOM Configuration”. This must be performed whether or not DCOM is being used. These edits set the proper permissions for the OPC server to be launched and accessed by client programs.
Configurators
The AIM*OPC Server is configured using one of two available configurators:
AIM OPC Configurator
Matrikon Configurator.
Regardless of which configurator is installed, the delta values for all the client tags are defaulted to a value of .001.
NOTE
Only one configurator can be installed.
AIM OPC Configurator
The AIM OPC Configurator, installed by default, is the preferred configurator. This configurator provides the ability to change delta values for all the client tags and provides all of the same func-tionality as the Matrikon Configurator.
Matrikon Configurator
The Matrikon Configurator was distributed on earlier versions of the AIM OPC Server and is still supported as the “legacy configurator”. The Matrikon configurator does not have the ability to configure change delta values.
If an earlier version of the OPC server was installed with the Matrikon Configurator and the OPC server parameters were saved to the Matrikon XML configuration file, this file can be re-applied to the new OPC Server installation.
NOTE
The saved Matrikon configuration file works with either the Matrikon or the AIM OPC Configurator.
Software Components Description
This section describes software components as they appear on the Selected Components screen and the associated files that get installed with each component. Some files are common to several components and are therefore listed more than once.
AIM*OPC Server
The aim\opc directory contains:
The version independent Program ID for the AIM*AT OPC Server is: AIM.OPC.
The version specific Program ID for this version of the server is: AIM.OPC.1.
AIM OPC Configurator
The aim\opc directory contains:
AIMOPCConfig.exe OEM_Matrikon_OPC.dll pstcfgps.dll
Standard OPC Server Browser
In compliance with OPC Standards, the installation program installs and registers the official OPC Server Browser (OPCEnum.exe). This file contains version information which protects the browser from being overwritten by an older version of the file. The installation program also ensures that the ActiveX Interface Marshalling Library (ACTXPRXY.DLL) is already installed on the station so that the server browser functions properly.
The WINDOWS\system32 directory contains: OPCEnum.exe The \aim\common directory contains: servutil.dll
File Description
AIMOPCSVR.exe AIM*OPC Server executable
AIMOPChelp.chm Help file
PSTCFGAIM.ocx Configuration utility ActiveX component
OPC Automation Components
The OPC Automation Components consist of DLLs that provide a programmatic interface to the OPC Server. The OPC automation components enable you to develop client applications that can access OPC data. Client applications can be written in programming languages, such as Visual Basic, VBA and VB Script, that support automation. The Program ID is
Matrikon.OPC.Automation. Refer to the OPC Data Access 2.05a Automation Interface Standard for information about automation objects.
The OPC Automation Components consists of the following three subsections and associated files:
OPC DA Automation DLL The aim\opc directory contains:
OPCAuto.dll OPCDA20auto.doc OEM_Matrikon_OPC.dll PSTcfgps.dll
The WINDOWS\SYSTEM32 directory contains:
ExprEval.dll OPCEnum.exe
OPC HDA Automation DLL The aim\opc directory contains:
OPCHDAAuto.dll OPCHDA10auto.doc OEM_Matrikon_OPC.dll PSTcfgps.dll
The WINDOWS\SYSTEM32 directory contains:
ExprEval.dll OPCEnum.exe
Standard OPC Proxy Stubs (OPC Marshalling Libraries) The WINDOWS\SYSTEM32 directory contains:
OPCProxy.dll
The AIM*AT OPC Server must connect to one or more AIM*AT API servers in order to:
Get the process values that are requested by an OPC client
Browse the OPC client server to locate the desired client tags.
Before you can use the OPC server to communicate with AIM servers, each AIM Server must have an Invensys supplied license authorization code entered on the AIM Server. License codes are available to an unlimited number of AIM servers.
The package code determines the type of connection authorized for the OPC server. The two types of package codes are as follows:
The OPCDAO package code enables the OPC server to establish a connection for real-time data transfer.
The OPCHDA package code enables the OPC server to establish a connection for both real-time and historical data transfer.
In addition, the computer name of the station that is hosting the OPC server must be configured as a user name on the AIM server.
NOTE
If the station that hosts the OPC Server is an I/A Series station (AW70), then the computer name is the station letterbug name.
The AIM*AT ApiAdmin utility allows you to configure the authorization code, user name, and security read/write privileges to the AIM server(s). Refer to the AIM*AT Installation Guide (B0193YM) for information on installing and using the ApiAdmin utility. The guide also pro-vides instructions and the forms for obtaining the authorization codes from Invensys.
Instructions for obtaining the authorization code and configuring the AIM server using the Api-Admin utility are described in the following section.
Obtaining an Authorization Code
To obtain an authorization code, proceed as follows:
1. Perform one of the following:
a. Run the AIM ApiAdmin utility and connect to the AIM server station(s) to which the OPC Server is required to connect. After a connection is made, go to the Authorization page. The station HostID is automatically displayed on this page.
b. Alternately, use the “hostname” utility available from a DOS command window on the local station AW station.
2. Fill out the “Request for Authorization Codes” form that is included in the AIM*AT Installation Guide (B0193YM).
a. Enter the required information and include the Server Host ID for the OPC Server.
b. Indicate which license you want: OPCDAO for real-time or OPCHDA for both real-time and historian data access.
c. FAX the request to the person and location indicated at the top of the form.
Configuring the AIM Server
To configure the AIM Server, proceed as follows:
Once you receive the authorization code(s), run the ApiAdmin utility to connect to the appropriate AIM server station and configure the following information:
a. On the Authorization page, enter the authorization code for the appropriate OPCDAO or OPCHDA Package Name.
b. On the User Names page, enter the name of the station hosting the OPC Server.
This is the station name as it appears on the network; it is not the user logon name. If the station is an I/A Series AW station, then the user name is the station letterbug.
c. On the Packages page, expand the appropriate user name and mark the check box for the OPC package code that applies (OPCDAO or OPCHDA).
d. On the Security page, expand on the appropriate user name and check the security options that are to be granted to the OPC clients via the AIM*AT OPC Server application that resides on the (user name) station.
e. On the Read List page, optionally restrict the user name (the OPC clients) to a specific list of database object names and shared variables that the OPC clients are allowed to read.
f. On the Write List page, optionally restrict the user name (the OPC clients) to a specific list of database object names and shared variables to which the OPC cli-ents are allowed to write.
4. AIM*AT API Server Component Installation
This chapter explains how to install the AIM*AT API Server Component on an I/A Series station.
When the OPC Server is required to connect to an AIM*AT API Server that is on a networked I/A Series station, you must install the AIM*AT API Server component if no API Server software is already installed. The installation program on the AIM*AT CD allows you to separately install the API Server software on an AW70 station (Windows operating system) by selecting the AIM*Historian component and the Remote Collector subcomponent.
Optionally, install the AIM*AT ApiAdmin. The AIM ApiAdmin utility allows you to configure authorization codes, user privileges, and so forth for all the AIM server(s).
NOTE
Do not install the ApiAdmin utility to the local station if AIM server configuration is done exclusively by a system administrator from another station. Only one Api-Admin utility is needed to configure all the AIM servers on the same network.
5. OPC Server Startup and Shutdown
This chapter discusses starting and stopping the OPC Server.
Starting the OPC Server
The OPC server starts automatically when an OPC client requests a connection to the server.
Alternatively, the server can be started manually. Manual startup of the OPC server is different depending on whether you installed the server to run as a local executable or as a Windows Ser-vice.
OPC Server Installed as an Executable Program
To start an OPC Server when installed as an executable program, 1. Select Start > Programs > AimAT OPC Server for DA
2. Depending on the configurator installed, the OPC server starts as follows:
a. If the AIM*OPC Configurator is installed, the server starts, but no server screen appears and no icon appears on the Windows task bar. Access the Windows Task Manager to verify that the AIMOPCSVR.EXE process is running.
b. If the Matrikon Configurator is installed, the OPC server starts, its splash screen appears briefly, and a small red X appears on the right side of the Windows task bar.
OPC Server Installed as a Windows Service
To start an OPC Server when installed as a Windows Service, proceed as follows:
1. Click the Start button and select Control Panel > Administrative Tools. 2. Click the Services icon. The Services dialog box lists the OPC Service among the
configured services.
Figure 5-1. Services Dialog Box on a Windows XP Station
3. Select Action menu > Start to select the AIM AT OPC Server in the Services dia-log box.
OPC Server Control Panel
NOTE
If the AIM Configurator is installed, the OPC Server control panel is NOT avail-able.
When you install the OPC Server as an executable program, the OPC Server Control Panel is accessible if the Matrikon Configurator is installed. The OPC server control panel (Figure 5-2) presents: server status, current time, and number of clients using the server.
The three menu items displayed along the bottom of the panel are:
Configure which starts the server configuration utility.
Shutdown which closes the control panel and shuts down the OPC server.
About which opens a dialog box that shows the software version number and licensing information.
The help button [?] in the title bar displays a description of the AIM*AT OPC Server software.
Figure 5-2. AIM*AT OPC Server Control Panel
To open the server control panel, do one of the following:
Double-click the red X icon in the task bar.
Right-click the red X icon, and choose Show Control Panel from the shortcut menu.
To reduce the control panel to its title bar,
Double-click the button on the left end of the title bar. The title bar displays the num-ber of clients (Figure 5-3).
Figure 5-3. Reduced Control Panel
To restore the control panel to full view,
Double-click the title bar.
To close the control panel,
Click the X button in the top right corner of the window.
Shutting Down the OPC Server
OPC Server shutdown is dependent on the OPC Server installation.
OPC Server Installed as an Executable Program (with the AIM Configurator)
To shutdown an OPC Server when it has been installed with the AIM configurator, 1. Access the Windows Task Manager to find the AIMOPCSVR.EXE process.
2. Click EndTask.
OPC Server Installed as an Executable Program (with the Matrikon Configurator)
To shutdown an OPC Server when it has been installed with the Matrikon configurator, 1. Access the OPC Server control panel from the OPC server icon in the Windows task
bar as described in “OPC Server Control Panel” on page 16.
2. Click Shutdown. NOTE
A warning appears if clients are currently connected to the OPC Server.
OPC Server Installed as a Windows Service
To shutdown an OPC Server when it has been installed as a Windows Service, proceed as follows:
1. Click the Start button and select Control Panel > Administrative Tools. 2. Click Services. The Services dialog box lists the OPC Service among the configured
services.
3. Select Action menu > Stop to select the AIM AT OPC Server in the Services dialog box.