Isolation Station Software

B0400ECREV AI/A Series

Isolation Station Software

Users Guide

May 28, 2008

Invensys, Foxboro, I/A Series, AIM*AT, AIM*Historian, FoxAPI, FoxCAE, FoxDraw, FoxView and Net FoxAPI are trademarks of Invensys plc, its subsidiaries and affiliatesAll other brand names may be trademarks of their respective owners.

Copyright 2008 Invensys Systems, Inc.All rights reserved

SOFTWARE LICENSE AND COPYRIGHT INFORMATION

Before using the Invensys Systems, Inc. supplied software supported by this documentation, you should read and understand the following information concerning copyrighted software.

1. The license provisions in the software license for your system govern your obligations and usage rights to the software described in this documentation. If any portion of those license provisions is violated, Invensys Systems, Inc. will no longer provide you with support services and assumes no further responsibilities for your system or its operation.

2. All software issued by Invensys Systems, Inc. and copies of the software that you are specifically permitted to make, are protected in accordance with Federal copyright laws. It is illegal to make copies of any software media provided to you by Invensys Systems, Inc. for any purpose other than those purposes mentioned in the software license.

Contents

Figures.................................................................................................................................... ix

Tables..................................................................................................................................... xi

Preface................................................................................................................................. xiii

Purpose .................................................................................................................................. xiii

Audience ................................................................................................................................ xiii

Revision Information ............................................................................................................. xiii

Reference Documents ............................................................................................................ xiii

Terms and Definitions ........................................................................................................... xiv

1. Overview ........................................................................................................................... 1

Isolation Station Concept .......................................................................................................... 1Isolation Station AW ............................................................................................................ 2Isolation Station Firewall ...................................................................................................... 2Isolation Station Server AW ................................................................................................. 2

Product Features ....................................................................................................................... 3

Requirements ............................................................................................................................ 5Customer Supplied Network ................................................................................................ 5I/A Series Platform ............................................................................................................... 5

Isolation Station AW (Remote Station) ........................................................................... 5Isolation Station Server AW (Local Station) .................................................................... 6

Implementation ........................................................................................................................ 6

Redundancy .............................................................................................................................. 7

2. Assumptions and Limitations ............................................................................................ 9

Isolation Station Server AW (Local Station) .............................................................................. 9AOS/INI Applications ........................................................................................................ 10OM Connections for AIM*API and FoxAPI Applications .................................................. 10

Isolation Station AW (Remote Station) ................................................................................... 11

AOS Software - Restrictions and Conventions ........................................................................ 11Reserved Compound Level Names ..................................................................................... 12Object Level Names ........................................................................................................... 12Object Manager Limitations ............................................................................................... 12Informix Software .............................................................................................................. 13

Solaris System Specifics ................................................................................................. 13Windows System Specifics ............................................................................................. 13

INI Software ........................................................................................................................... 13iii

B0400EC Rev A Contents Data Transfer Limitations .................................................................................................. 13Message Forwarding Limitations ........................................................................................ 15Message Relay Limitations .................................................................................................. 15

Isolation Station Configurator ................................................................................................. 15Intermediate Application Objects ....................................................................................... 15

3. Installation - Windows Stations ...................................................................................... 17

Isolation Station Server AW Installation .................................................................................. 18Informix Dynamic Server (IDS), Version 10.00 ................................................................. 18Installing FoxAPI Related Software .................................................................................... 21AOS Software ..................................................................................................................... 21Installing the INI70 Software ............................................................................................. 22

Isolation Station AW Installation ............................................................................................ 23Installing FoxAPI Related Software .................................................................................... 23AOS Software ..................................................................................................................... 23

Controller Hosts Installation ................................................................................................... 24Isolation Station Configurator ............................................................................................ 24

4. Installation - Solaris Stations ........................................................................................... 25

Isolation Station Server AW Installation .................................................................................. 25Installing FoxAPI Related Software .................................................................................... 25FoxSpy Software ................................................................................................................. 26NetFoxAPI Client Software ................................................................................................ 26Latest FoxAPI Quick Fix .................................................................................................... 27AOS Software ..................................................................................................................... 27INI51 Software .................................................................................................................. 29

Message Forwarding ...................................................................................................... 32Message Relay ................................................................................................................ 32

Isolation Station AW Installation ............................................................................................ 33NetFoxAPI Client Software ................................................................................................ 33Latest FoxAPI Quick Fix .................................................................................................... 33AOS Software ..................................................................................................................... 34

Controller Hosts Installation ................................................................................................... 36Isolation Station Configurator ............................................................................................ 36

5. Configuration-Windows Stations .................................................................................... 37

Isolation Station Server AW (Local Station) ............................................................................ 37AOS Software ..................................................................................................................... 38INI Software ...................................................................................................................... 38


Manual Startup .................................................................................................................. 39Automatic Startup .............................................................................................................. 40

Isolation Station AW (Remote Station) ................................................................................... 40AOS Software ..................................................................................................................... 40iv

Contents B0400EC Rev A Message Forwarding ........................................................................................................... 41Message Relay .................................................................................................................... 41

Isolation Station Configurator ................................................................................................. 41Windows Stations .............................................................................................................. 41

Use Local Station ........................................................................................................... 43Intermediate Compound Names ........................................................................................ 44

6. Configuration - Solaris Stations....................................................................................... 47

Isolation Station Server AW (Local Station) ............................................................................ 47AOS Software ..................................................................................................................... 48INI Software ...................................................................................................................... 48


Manual Startup .................................................................................................................. 49Automatic Startup .............................................................................................................. 50

Isolation Station AW (Remote Station) ................................................................................... 51AOS Software ..................................................................................................................... 51Message Forwarding ........................................................................................................... 51Message Relay .................................................................................................................... 51

Isolation Station Configurator ................................................................................................. 51Solaris Stations ................................................................................................................... 52

Use Local Station ........................................................................................................... 53Intermediate Compound Names ........................................................................................ 54

7. Operation........................................................................................................................ 57

Application Object Services (AOS) .......................................................................................... 57Typical Uses ....................................................................................................................... 58

Information Network Interface (INI) ...................................................................................... 59Message Forwarding ........................................................................................................... 59Message Relay .................................................................................................................... 61

Message Relay and Well-Known Names ........................................................................ 61Message Relay and Locally Known Names .................................................................... 61Message Relay and Broadcast Messages .......................................................................... 61

Securely Moving Data from the DMZ to a CP .................................................................. 63

Isolation Station Configurator ................................................................................................. 63

8. Maintenance - Windows Stations .................................................................................... 65

Isolation Station Configuration Utility .................................................................................... 65Data Backup ...................................................................................................................... 65Package Removal ................................................................................................................ 65Upgrades ............................................................................................................................ 65I/A Series Software Upgrades .............................................................................................. 65

Day 0 and Day 1 .......................................................................................................... 65Quick Fixes ........................................................................................................................ 65

INI70 Software ....................................................................................................................... 66v

B0400EC Rev A Contents Package Removal ................................................................................................................ 66I/A Series Software Upgrades .............................................................................................. 66

Day 0 Upgrades ............................................................................................................. 66Non-Day 0 Upgrades .................................................................................................... 67

INI Package Upgrades ........................................................................................................ 67Saving Configuration Data ............................................................................................ 67Stopping the INI Package .............................................................................................. 68Loading INI Package ..................................................................................................... 68Restoring Configuration Information ............................................................................ 68Restart the INI Package ................................................................................................. 69

Quick Fixes ........................................................................................................................ 69

AOS Software ......................................................................................................................... 69Package Removal ................................................................................................................ 69I/A Series Software Upgrades .............................................................................................. 70


AOS Software Upgrades ..................................................................................................... 70Saving Configuration Data ............................................................................................ 70Loading AOS Package ................................................................................................... 70Restoring Configuration Information ............................................................................ 71Restart the AOS Package ............................................................................................... 71Quick Fixes ................................................................................................................... 71

9. Maintenance - Solaris Stations......................................................................................... 73

Isolation Station Configuration Utility .................................................................................... 73Data Backup ...................................................................................................................... 73Package Removal ................................................................................................................ 73Upgrades ............................................................................................................................ 73I/A Series Software Upgrades .............................................................................................. 73

Day 0 and Day 1 .......................................................................................................... 73Quick Fixes ................................................................................................................... 73

INI51 Software ....................................................................................................................... 74Package Removal ................................................................................................................ 74I/A Series Software Upgrades .............................................................................................. 74


INI51 Software Upgrades ................................................................................................... 75Saving Configuration Data ............................................................................................ 75Stopping the INI Package .............................................................................................. 75Loading INI Package ..................................................................................................... 76

Restoring Configuration Information ................................................................................. 76Restart the INI Package ................................................................................................. 76

Quick Fixes ........................................................................................................................ 76

AOS Software ......................................................................................................................... 76Package Removal ................................................................................................................ 76I/A Series Software Upgrades .............................................................................................. 77

Day 0 Upgrades ............................................................................................................. 77vi

Contents B0400EC Rev A Non-Day 0 Upgrades .................................................................................................... 77AOS Software Upgrades ..................................................................................................... 77

Saving Configuration Data ............................................................................................ 77Stopping the AOS Package ............................................................................................ 77Loading AOS Software .................................................................................................. 78Restoring Configuration Information ............................................................................ 78Restart the AOS Package ............................................................................................... 78

Quick Fixes ........................................................................................................................ 78

10. Troubleshooting............................................................................................................ 79

General ................................................................................................................................... 79

Station Overload ..................................................................................................................... 79CPU Cycles ........................................................................................................................ 79I/O Loading ....................................................................................................................... 79Memory ............................................................................................................................. 80

Baseline ................................................................................................................................... 80

Slow Displays .......................................................................................................................... 80

Delay of Use After Reboot ...................................................................................................... 80

Speed Up Database Build ........................................................................................................ 81

Isolation Station Tag Not Updating ........................................................................................ 81

Appendix A. Command Usage............................................................................................. 85

BuildIniIssmaps ...................................................................................................................... 85Synopsis ............................................................................................................................. 85

Examples ....................................................................................................................... 85

Index .................................................................................................................................... 87vii

B0400EC Rev A Contents viii

Figures

1-1. Shared Map Files ........................................................................................................... 31-2. Data Flow ..................................................................................................................... 51-3. Redundancy Example 1 ................................................................................................. 71-4. Redundancy Example 2 ................................................................................................. 75-1. Isolation Station System Overview .............................................................................. 375-2. Staring the Isolation Station Configurator (Windows Stations) ................................... 425-3. INI and IS Map File Builder (Windows Stations) ....................................................... 425-4. INI and IS Map File Builder - Local Station (Windows Station) ................................. 435-5. INI and IS Map File Builder - Map File View (Windows Stations) ............................. 445-6. Intermediate Compound Naming (Windows Stations) ............................................... 456-1. Isolation Station System Overview .............................................................................. 476-2. Starting the Isolation Station Configurator (Solaris Stations) ...................................... 526-3. INI and IS Map File Builder (Solaris Stations) ............................................................ 526-4. INI and IS Map File Builder - Local Station (Solaris Stations) .................................... 536-5. INI and IS Map File Builder - Map File View (Solaris Stations) .................................. 546-6. Intermediate Compound Naming (Solaris Stations) .................................................... 557-1. AOS Software Data Flow ............................................................................................ 587-2. Data Flow from Remote Station to Local Station in a Peer-to-Peer Application .......... 597-3. Message Forwarding Functionality .............................................................................. 607-4. Message Relay of Broadcast Messages .......................................................................... 62ix

B0400EC Rev A Figures x

Tables

1-1. Mapping Operators ....................................................................................................... 45-1. Application Naming .................................................................................................... 446-1. Application Naming .................................................................................................... 54xi

B0400EC Rev A Tables xii

Preface

PurposeThis document explains the purpose and use of the Isolation Station software package. The Isolation Station software packages when combined with the correct network and I/A Series hardware provides controlled isolation between the I/A Series control network and the customer supplied network.

AudienceThis document assumes a user who is familiar with:

The systems Operating System (OS), i.e. UNIX or Windows,

The use of a text editor, e.g., vi(1), textedit(1), or NotePad,

The configuration of the I/A Series display manager for remote operation,

If the Message Forwarding Service is to be used, the user needs to be familiar with:

The I/A Series Alarm System,

The configuration of the I/A Series Alarm Manager, and

The configuration of the I/A Series Annunciator Keyboards and horns.

If the Message Relay Service is to be used, the user needs to be familiar with:

The I/A Series software IPC Communication Mechanism

If troubleshooting data transfers, the user needs to be familiar with foxtst, som, and oma.

Revision InformationThis is the initial release of this document.

Reference DocumentsThe following standard I/A Series system documents are referenced in this manual and may be worth reviewing prior to using the Isolation Station Software.

50 Series Configurable OPSYS (B0193MJ)

50 Series X Client/Server Support, (B0193NV)

Display Engineering for 50 Series (B0193MQ)

Display Manager/FoxView Calls (B0193DF)

FoxRemote Configurations Guide for Solaris Installation and Configuration Guide (B0193WZ)

I/A Series System FoxAPI User's Guide (B0193UD)

I/A Series System FoxAPI Installation Guide (B0193UC)

Integrated Control Block Descriptions (B0193AX)xiii

B0400EC Rev A Preface Inter-Process Communications Calls (B0193BB)

I/A Series Software Utilities (B0193JB)

Process Alarm Configuration (B0193AU)

Workstation Alarm Management (B0193RV)

The following documents are supplied with the Isolation Station but are not necessarily available on FoxDoc:

Application Object Services Users Guide (B0400BZ)

Information Network Interface for Solaris and Windows Software User Guide (B0400BM)

Networked FoxAPI Client Software Installation Instruction (Solaris Only)

Terms and DefinitionsThe following is a list of terms and definitions as they pertain to the Isolation Station software.

Application

A collection of Application Objects. Generally, an Application (or several) is associated with a program that populates some of the Application Object Attributes and consumes data from others. If the data transfer services are used, the program can use the Applica-tion Object API to obtain process data and to move data into the process.

Application Definition

An Application Definition is a set of records in the aos Informix database that defines a particular Application. An up to date map file is considered by some to be the Application Definition, but this is incorrect. The true Application Definition is the information about the Application in the Informix database.

Application Object Attribute (A:O.A or AOA)

An attribute of an Application Object. The attributes of an Application Object hold the value, status, and time tag associated with a name.

Application Object Services (AOS)

AOS provides a set of services to users of Application Objects. These services include create, deletion, mapping, checkpointing, and alarming.

Application Objects (AOs)

Application Objects is the generic term for a type of OM variable object. The term is used to refer to:

All Application Object Attributes collectively.

The collection of Application Object Attributes belonging to a particular second level name.

Application Objects reside in an AP/AW and are hierarchal like the objects found in a Control Station. The hierarchy is: Application (A), Object (A:O or AO), and Attribute (AOA or A:O.A).

Though their names resemble Control Block Names, AOs do not have the support of a Block Processor.xiv

Preface B0400EC Rev A Application Objects are often used to represent data structures that would normally be internal to a program (application), but which are more useful if they are globally accessible through the OM. The DMCplus Bridge, Connoisseur, and the I/A Series Off-sites Suite (BOSS/OMIS/TIS) use the AOS software in that manner.

Compound Block Parameter (CBP or C:B.P)

The name of a value associated with an I/A Series Control Block

Control Network

The network that connects I/A Series stations. Components of this network may include nodebus segments, Carrierband LAN segments, and/or Mesh Network segments.

Customer Supplied Network (CSN)

The network used to connect the Isolation Station Server AW (local machine) and the Isolation Station AW (remote machine). Typically, the connection between these two systems uses the optional 2nd Ethernet port found on I/A Series AWs.

FoxView Software

One of the I/A Series display manager packages.

globally known (logical) name

The I/A Series IPC mechanism is based on communication by logical name. A name can be locally known or globally known.

Locally known names are known only by the IPC services in the AP/AW running the program. Globally known names are registered with the I/A Series Object Manager. The station address of globally known programs can be found using OM calls. Locally known programs cannot be found in that manner.

Programs using I/A Series IPC to communicate with a locally known program must either know the other programs station address or must use the I/A Series broadcast message. The station address of the other program can be obtained from its globally known name if available.

iaToQ

Process on the Isolation Station Server AW (local machine) that is responsible for intercepting and collecting the Control Station, System Monitor, and Operator Action Journal messages. It places the messages in an outgoing message queue for processing by the qToNet.

Information Network Interface (INI)

A suite applications that loosely couples separate I/A Series systems. This loose coupling allows data exchange and message transfer. The INI process runs on the Isolation Station Server AW (local machine).

Informix Database

AOS and the INI packages use the Informix relational database to create databases to hold Application Definitions. The Solaris based I/A Series system ships with a runtime license for an Informix relational database. The Isolation Station software includes the required Informix license.

IPC/COMEX

IPC/COMEX is the communication services used by all I/A Series programs including the OM.xv

B0400EC Rev A Preface Local Station

The Isolation Station Server AW is the station that sends the alarm messages and/or pro-cess data off-node. It is the machine that runs the INI process and the iaToNet process.

locally known (logical) name

The I/A Series IPC mechanism is based on communication by logical name. A name can be locally known or globally known.

Locally known names are known only to the IPC service in the AW running the program. Globally known names are registered with the I/A Series Object Manager. The station address of globally known programs can be found using OM calls. Locally known programs cannot be found in that manner.

Programs written to communicate with a locally known program must either know its station address or must use the I/A Series broadcast message.

logical name

A logical name is an ASCII string used to represent and I/A Series object. An I/A Series object may be a value, a program, device, or alias. The INI software is concerned only with values and programs. The I/A Series Object Manager knows globally known logical names like the value of a control block parameter (CBP) and the name of a historian. Locally known names are used only with programs. They are not registered with the OM, but they are registered with the Foxboro IPC layer.

map file

An ASCII file used to define the Application Object attributes to be stored in the Informix database used to hold Application definitions.

mapping

The term used for the transfer of data between Application Object and other OM variable under the control of the AOS/INI mapping service.

Message Forwarding

Communication within the I/A Series network is based on a message passing system built upon a set of communication services known as IPC/COMEX, or the Inter-Process Communication/Communication Executive. IPC/COMEX provides support for transporting a block of data, or packet, from one I/A Series station to another in an efficient and reliable manner.

The Message Forwarding component of the INI package is built on top of these IPC services and allows forwarding of I/A Series system messages from remote I/A Series system to the local I/A Series system. Message types forwarded include messages generated by Control Stations, System Monitors, and Operator Workstations.

It is important to understand the basics of I/A Series Messaging before attempting to understand the Message Forwarding component of the INI package.

msgRelay

The INI software component responsible for relaying Foxboro IPC messages between application programs.xvi

Preface B0400EC Rev A netToIA

Process on the Isolation Station Server AW (local station) this is responsible for receiving all messages sent across the TCP/IP connection from qToNet and delivering them to their final destination. The final destination could be a printer, historian, or an AW/WP on the Isolation Station AW (remote station) network, if any.

Object Manager

The I/A Series Name Server. It provides services that allow programs to locate and access I/A Series objects. The most common objects are values and programs using Foxboro IPC.

Object Template

A Bourne shell script that defines the attributes of an Application Object. It is combined with the information found in an aod file by MkMapFile to form a map file.

NIC

Network Interface Card. A card used to connect a computer to a network.

qToNet

Process on the Isolation Station Server AW (local station) that is responsible for establishing the TCP/IP connection and sending the collected messages to its partner netToIA. It reads the messages placed in the outgoing message queue by iaToQ.

Remote Station

The Isolation Station AW (remote station) on the CSN. This is the station that is to receive process data and/or I/A Series messages from the Isolation Station Server AW (local station). It is the station that runs the netToIA application.xvii

B0400EC Rev A Preface xviii

1. Overview

The Isolation Station Software, when combined with the correct network and I/A Series equipment, strictly controls access to the I/A Series Process Control equipment while enabling complete access to selected process data. Isolation with data transparency is the distinguishing feature of the product.

Isolation Station ConceptThe Isolation Station concept was developed in response to the need to improve DCS isolation while maintaining access to DCS data. The Isolation Station concept, combines hardware and software to completely control external access to the DCS. The Isolation Station concept is imple-mented by combining three pieces of hardware and associated software.

The Isolation Station concept combines two I/A Series workstations and a standard firewall. The equipment is as follows:

The first I/A Series workstation attaches to the DCS Control Network and serves as the information server. It is known as the Isolation Station Server AW.

The firewall is placed between the two workstations with all ports closed on its non-DCS side which restricts communication initiation to the DCS based equipment.

The second I/A Series workstation is not directly attached to an I/A Series control network. It is known as the Isolation Station AW.

The Isolation Station software package provides the additional software required by the worksta-tion to implement the Isolation Station concept. There are three packages included in the Isolation Station software: Application Object Services (AOS), Information Network Interface (INI), and the Isolation Station software configurator. The Isolation Station AW is loaded with AOS software, the Isolation Station Server AW is loaded with the AOS software and INI software. The Isolation Station software configurator is loaded on each controller host.

The Isolation Station solution by itself is only a component of a plant-wide security program. The IPS Cyber Security Team, [email protected], has comprehensive service offerings that build on procedures and tools like the Isolation Station concept to design and implement comprehensive security solutions.

Key features of the Isolation Station concept are:

Strictly controlled access to the I/A Series DCS network.

Segregation of the I/A Series DCS network from third-part and nonessential applications.

Strict control of reads and writes to I/A Series tags.

Complete support for standard I/A Series services like: Display Manager and FoxView instances, Alarm Managers, FoxAPI, AIM*API, and the OM API calls.1

B0400EC Rev A 1. Overview Isolation Station AWThis station strictly controls access to I/A Series Process Control equipment while enabling complete access to selected process data and is the dedicated platform that hosts all third-party applications and Invensys applications that interface to the plant control network or office network.

The Isolation Station AW represents the data in the protected system to applications that reside in the unprotected network. The Isolation Station software package allows the Isolation Station AW to represent the protected systems data using exactly the same tag names as those on the original system. This commonality of names makes the movement of applications from the protected DCS to the Isolation Station AW simple and straightforward.

The Isolation Station concept is flexible enough to support Isolation Stations that have identical data for redundancy and scalable enough to support multiple Isolation Stations if the system is very large.

The Isolation Station machine is a standard I/A Series AW loaded with standard I/A Series software plus the Isolation Station software components appropriate to an Isolation Station AW.

This station supports the following functionality (as examples):

Invensys Packages

AIM (OPC DA/HDA Server, OPC A&E Server (as of 04/1/2008), ODBC) The AIM OPC Server is used to support external applications access to real time DCS data.

Connoisseur

Remote access to FoxView or Display Manager displays.

Third-party Packages

PI-API

DMCplus

Base Software

Tag Data

Data transfer

Virus Detection

Isolation Station FirewallA dedicated firewall that is the sole line between the Isolation Station AW and the Isolation Station Server AW. This firewall is configured such that no ports are open on the non-DCS side. This prevents issues on the non-DCS network from reaching the protected, DCS equipment.

Isolation Station Server AWThe Isolation Station Server AW is an I/A Series AW residing on the DCS network that has been configured with the Isolation Station software. This station connects to the firewall, using a second Network Interface Card. It is the source of the information being sent to the Isolation Station AW.2

1. Overview B0400EC Rev A Product FeaturesThe Isolation Station Software is comprised of the following software packages:

Application Objects Services (AOS) Software - provides services to facilitate data representation, data transfer and alarm generation. The AOS software is installed on both the Isolation Station Server AW (local station) and Isolation Station AW (remote station).

Information Network Interface (INI) Software - provides services that enable data transfer and message forwarding. The INI software is installed on the Isolation Station Server AW (local station) only. The INI software consists of three modules:

The Data Transfer facility which makes the Isolation Station Server AWs (local station) objects available to the Isolation Station AW (remote station).

The Message Forwarding facility which forwards messages from the Isolation Station Server AWs (local station) to the Isolation Station AW (remote station) for annunciation.

The Message Relay facility that supports two-way communications between Foxboro Inter-Process Communication based programs.

Isolation Station Configurator - provides a graphical user-interface (GUI) utility that consolidates all the activities required to generate the map files used by the Informa-tion Network Interface (INI) software. These map files are the keys to replicate data for consumption by the outside world. The Isolation Station Software eliminates the manual steps formerly used to generate map files.

In the Isolation Station Server AW (local station) the AOS and INI applications share the same application and the same map file, Figure 1-1.

Figure 1-1. Shared Map Files

Since the AOS and INI instances are on the same machine and share the AOA, they share the same map file. For this reason only two map files are required for implementation.

One on the Isolation Station Server AW (local station) used by AOS and INI applica-tions for mapping and

One with the C (constant) mapping on the Isolation Station AW (remote station) to hold the transferred values.

Isolation Station AW

Map Files

Informix

Control Network

AOSC:B.P _A:O.A

INI Customer SuppliedNetwork

A:O.A

CP Isolation Station Server AW3

B0400EC Rev A 1. Overview In this situation there are only a very few mapping operators that can work.

TIPFor more information about mapping, please reference the Application Object Services Users Guide (B0400BZ) manuals map File section and the Information Network Interface for Solaris and Windows Software User Guide (B0400BM) manuals map File section.

The mapping process from a C:B.P accessible by the Isolation Station Server AW to an applica-tion object in the Isolation Station AW is as follows:

1. The Isolation Station Configurator produces 2 map files, one for the Isolation Station Server AW and the other for the Isolation Station AW. The inputs to the Isolation Station Configurator are:

a. The name of the control station (in the local host) for which the map files are to be produced. If the control station name is set to All, then map files for all control stations in the local host will be produced.

b. The pathname to the mapDef file. The mapDef file is a modified version of the one used by the INI software. This file contains only C, p and w mapping types. The default name is /opt/iss/data/mapDefIss. See the Information Network Interface for Solaris and Windows Software User Guide, B0400BM, Command Usage, Map Definition File (mapdef ), sections for a detailed explanation of the mapDef file.

2. The AOS software running in the Isolation Station Server AW maps the C:B.P to an intermediate application object with the same name prefixed by an underscore (_), i.e. _C:B.P.

3. The INI software maps the intermediate application object across the customer supplied network to the application object C:B.P in the Isolation Station AW, which is managed by its own copy of the AOS software.

The Figure 1-2 illustrates the replicated data flow from the Isolation Station Server AW (local station) to the Isolation Station AW (remote station). The thicker arrows indicate the data flow direction.

Table 1-1. Mapping Operators

Station Operator Description Purpose

Isolation Station

C Constant Holds the external values.

Isolation Station Server

p (lower case)

AOS g for STRINGAOS R for non-STRINGINI P for STRINGINI P for non-STRING

Used to update the outside values. Does not secure the target outer AOA.

Isolation Station Server

w (lower case)

AOS g for STRINGAOS R for non-STRINGINI W for STRINGINI W for non-STRING

Used to update outside values. Secures the target outer AOA.4

1. Overview B0400EC Rev A Figure 1-2. Data Flow

Requirements

Customer Supplied Network Any network for which a Network Interface Card is available. Invensys offers a variety

of Ethernet NICs.

IP suite based.

I/A Series Platform

Isolation Station AW (Remote Station)An Isolation Station AW hardware and software requirements are:

I/A Series AW51 with standard AW licenses. (Provides remote access to multiple display managers.)

I/A Series AW70 running a Windows Server 2003 operating system with standard AW licenses. (Provides remote access to multiple display managers.)

I/A Series AW70 running a Windows XP operating system with standard AW licenses. (Multiple display manager access not required.)

Extra NIC to link to Isolation Station Server AW.

FoxAPI interface software.

I/A Series software Version 4.3/6.1 and later.

AOS

Isolation Station Server AW (Local Station )

Isolation Station AW (Remote Station )

Informix

INI_C:B.P(Intermediate A:O.A)

aos builddb

Isolation Station

Configuration Utility

.map file with intermediate name for AOA ; used as buffer by INI local station.

_C:B.P C:B.P P

Informix

C:B.P(Replicated Data)

aos builddb

AOS .map file for Isolation Station.C:B.P X C

Local Map File Remote Map File

User Applications

FoxView

AIM*

Plant Information Network

Protected Unprotected

aos createaos create

C:B.P

CP

Control Network5

B0400EC Rev A 1. Overview Application Object Services (AOS) software. (Ships as part of the Isolation Station Software deliverable.)

Additional RAM may be required based on the use of the AW. This is a project specific need and must be evaluated on a case by case basis.

Isolation Station Server AW (Local Station)An Isolation Station Server AW hardware and software requirements are:

I/A Series AW51 with standard AW licenses. (Provides remote access to multiple display managers.)

I/A Series AW70 running a Windows Server 2003 operating system with standard AW licenses. (Provides remote access to multiple display managers.)

I/A Series AW70 running a Windows XP operating system with standard AW licenses. (Multiple display manager access not supported.)

Extra NIC to link to Isolation Station AW.

FoxAPI interface software.

I/A Series software Version 4.3/6.1 and later.

Application Object Services (AOS) software.(Ships as part of the Isolation Station Software deliverable.)

Information Network Interface (INI) software. (Ships as part of the Isolation Station Software deliverable.)

Additional RAM may be required based on the use of the AW. This is a project specific need and must be evaluated on a case by case basis.

ImplementationThe Isolation Station AW and the Isolation Station Server AW use the functionality of the Isolation Station Software to replicate data required by the customer supplied network PCs.

The Isolation Station solution consists of the following pieces:

Isolation Station AW (Remote Station) - An equipped AW (sold separately) that is connected to the customer supplied network. This station is the platform that hosts all third party applications and Invensys applications that interface to the customer supplied network.

Isolation Station Firewall - A dedicated firewall (sold separately) that is the sole link between the Isolation Station AW and the Isolation Station Server AW.

Isolation Station Server AW (Local Station) - An AW (sold separately) residing on the control network that has been configured with the Isolation Station Software. This station connects to the firewall using a second NIC.6

1. Overview B0400EC Rev A RedundancyIsolation Station redundancy can be achieved by using two pairs of independent Isolation Station Server AW/Isolation Station AW. The following figures show two possible examples of how redundancy can be achieved.

Figure 1-3 shows redundancy using two independent Isolation Station Server AW/Isolation Station AW pairs with two independent firewalls.

Figure 1-3. Redundancy Example 1

Figure 1-4 shows redundancy using two independent Isolation Station Server AW/Isolation Station AW pairs with both using the same firewall.

Figure 1-4. Redundancy Example 2

In both examples, the Isolation Station AW #1 and Isolation Station AW #2 must be separate I/A Series stations.

Each Isolation Station Server AW/Isolation Station AW pair will need different map files so that the AOAs on each Isolation Station Server AW will have unique names.

Control Network

Isolation Station Server AW

#1


#2

Isolation Station AW #2


Firewall #1

Firewall #2

Plant Information Network



Firewall

Control Network


#1


#27

B0400EC Rev A 1. Overview 8

2. Assumptions and Limitations

This chapter describes the assumptions and limitation of the Isolation Station concept.

Isolation Station Server AW (Local Station)The following are limitations concerning the Isolation Station Server AW (local station).

The INI package uses a lot of RAM, so check the Isolation Station Server to deter-mine if it is low on RAM.

The AOS package on the Isolation Station Server AW can consume a fair number of OM resources if the configuration is trying to read lots of data.

For that reason, it is good to use an AIM*Historian machine as the Isolation Station Server AW and configure the AIM*API software (used by the AIM* Historian package) to share lists with the FoxAPI interface software (used by the AOS package).

Configure the maximum number of OM lists allowed by the software.

In general, increase the OM_NUM_OBJECTS setting to create room for the AOAs. You get between 2 and 4 AOAs per increment of OM_NUM_OBJECTS.

NOTEThere is a defect in the OM of the 70 Series stations, running FoxView/FoxDraw v10.1, which limits the number of AOAs that can be created to far less than one is likely to want to create. Quick Fix 1008989 has been issued to resolve this problem.

Configure both AIM*API and FoxAPI interface software to use 255 entries per OM list.

Both the AOS and INI packages can add to the CPU load of the Isolation Station Server AW, but generally this is not a significant burden.

NOTEIf the Isolation Station Server AW is also running the AIM*Historian software, then the OM load can be minimized by sharing the OM lists with the AIM*API software. The the aimapi.cfg file can be modified to enable this share. See the following documents for more information: AIM*AT Service Pack 3.2.3 Release Notes (B0400EL), AIM*API Users Guide (B0193YN) and FoxAPI V4.3 Release Notes (B0193UC).9

B0400EC Rev A 2. Assumptions and Limitations AOS/INI ApplicationsIt is important to understand that both the AOS and INI applications read the Informix database and initialize the AOAs in the Isolation Station Server AW when mapping is started. As a result of this sharing keep in mind that:

If the INI application is started first, there is no issue. The INI application initializes the AOAs to the value in Informix and the AOS application does the same thing before starting the update.

If the AOS application is started first, it puts valid data in the AOAs for transmittal to the Isolation Station AW (remote station), but when the INI application starts it sets the values back to the initial values specified in the Informix database. At that point, any re-initialized tags will not be propagated to the Isolation Station AW until the tags change on the Isolation Stations Servers control network.

Since the AOS and INI packages share application objects, each one thinks it is the sole user of the A:O.action attribute, so the first package to see the unmapping request (a certain value in A:O.action) will unmap the application object. The unmap command must be performed twice to unmap the application object and there is no guarantee which package will unmap first.

Both the AOS and INI programs handle shared variables, simply put the name in the right place in the map file.

OM Connections for AIM*API and FoxAPI ApplicationsWhen the AIM*AT software is initially installed for use with AIM*AT applications, it does not replace the FoxAPI interface, the application programming interface for the I/A Series systems. While very similar, the two APIs are two separate subsystems. I/A Series products such as the FoxCAE software and the FoxDraw application require the FoxAPI interface. The AIM*AT applications require only the AIM*API interface, which must be running to operate. The AIM*API interface and the FoxAPI interface can share I/A Series Object Manager connection resources. The shared connection can save resources and reduce the time to open OM connections when the I/A Series workstation is rebooted.

NOTEThe workstation must have the FoxAPI software Version 4.3 or later to support the USEAIMAPI option.

To activate connection sharing for Windows workstations:

1. Open the aimapi.cfg file in the AIM*AT program directory.d:\opt\aim\bin\aimapi.cfg on AW70sc:\Program Files\aim\bin\aimapi.cfg on off-platform Windows workstations

2. Edit the file to include the following line:USEAIMAPI = 0

3. Use the Control Panel applet to start FoxAPI.10

2. Assumptions and Limitations B0400EC Rev A Use the Control Panel applet to start AIM*AT Applications.To activate connection sharing for Solaris workstations:

1. Open the aimapi.cfg file in the AIM*AT program directory./opt/aim/bin/aimapi.cfg on AW51s/opt/aim/bin/aimapi.cfg on off-platform Solaris workstations

2. Edit the file to include the following line:USEAIMAPI = 0

3. Use the /opt/fox/ais/bin/aisstop command to stop the FoxAPI process.

4. Use the /opt/fox/ais/bin/aisstart command to restart the FoxAPI process.

5. Use the /opt/fox/ais/bin/apistop command to stop the AIM*AT process.

6. Use the /opt/fox/ais/bin/apistart command to restart the AIM*AT process.

Thus, the AOS software load can be close to zero additional assuming that the historian is already getting the same points.

Isolation Station AW (Remote Station)The following are limitations concerning the Isolation Station AW (remote station).

AOS software does configure a certain amount of RAM in the OMs Shared Memory Segment, so more than the normal amount of RAM may be required. Each AOA uses about 100 bytes of RAM so it takes a lot of them to cause problems.

AOS Software - Restrictions and ConventionsThe AOS software can map any I/A Series OM variable that is connectable for read. Not all Control Block Parameters are connectable for read. The Control Block documentation provides a table for each blocks parameters that specifies if the parameter can be connected for read.

Typical parameters that cannot be read/mapped include SUPOPT and the various alarm enabling options, e.g. HLOPT. If these variables need to be displayed, a constant mapping (C) must be used and the map file on the Isolation Station AW should contain the value to display.

The names of the Application Objects (AOs) must meet the following restrictions:

AOs names must be of the format, Application:Object.Attribute, where Application may be 12 characters long, Object may be 12 characters long, and Attribute may be 6 characters long.

AOs names must meet the constraints of the I/A Series software, i.e., only uppercase alphabetic characters, numeric characters and underscores (_) are allowed.

AOs names must be unique within the set of I/A Series Object Names, e.g., one can-not have an Application whose name is the same as an existing Compound.

The following general constraints apply to the AOS software:

An Application must first be built (stored into Informix) from its mapping text file.

An Application must be created before it can be mapped.

An Application must be mapping for checkpointing to occur.

Mapping prefers that the source and sink variables both have the identical data type. However, type casting is supported on R mappings.11

B0400EC Rev A 2. Assumptions and Limitations All data types must have positive dead bands; otherwise, unnecessary mappings occur. If a mapped AOA or CBP has a deadband of 0, then its value is copied across to is associated CBP or AOA every mapping scan rate cycle. THIS IS TRUE FOR ALL DATA TYPES.

Character data types must have dead bands greater than or equal to 1; otherwise, unnecessary mappings occur as in the above note.

The initial values of a character data type AOA must be a non-space printable ASCII characters in the mapping text file.

There is no limit on the number of AOAs in an application, other than that imposed by the size of shared memory on the machine.

The maximum number of objects per application is 10,000.

The maximum number of attributes per object is 10,000.

The maximum number of unique attribute names in the aos database is 10,000.

The FoxAPI software scan rate of all AOS software data sets can range from 2 to 10 seconds.

The 10,000 limit mentioned above is imposed by the number of rows in a table that the AOS product can handle in a single query.

Reserved Compound Level NamesEach Application created using the AOS software has the standard set of 31 Compound level attributes, i.e., TYPE (string), DESCRP (string), PERIOD (integer), PHASE (integer), ON (integer), INITON (integer), CINHIB (integer), GR1DV1-8 (string), GR2DV1-8 (string), GR3DV1-8 (string).

Additionally, the Application has extra attributes and a complete list of these attributes can be located in Chapter 2 of the Application Object Services Users Guide.

NOTEAs a general rule, designers of Applications Objects should avoid the use of lower case attribute names. Lower case names should be avoided for two reasons: the ICC will not let them be entered and the AOS software may be extended to include new reserved parameters. It is expected that names of new reserved attributes will be all lower case characters.

Object Level NamesEach Application Object created using the AOS software has the standard set of 4 Block level attributes, i.e., TYPE (string), DESCRP (string), PERIOD (integer), and PHASE (integer).

Additionally, the Application Object has extra attributes and a complete list of these attributes can be located in Chapter 2 of the Application Object Services Users Guide.

Object Manager LimitationsBy default, the current versions of the I/A Series software supports up to 4000 Object Manager variables as AP or AW. Of the 4000, 1250 need to be reserved for normal operation of the station. This leaves 2750 OM objects available for use by the users application in a normal 12

2. Assumptions and Limitations B0400EC Rev A system. This limit can be raised following the instructions in the Application Object Services Users Guide (B0400BZ).

NOTEThere is a defect in the OM of the 70 Series stations, running FoxView/FoxDraw v10.1, which limits the number of AOAs that can be created to far less than one is likely to want to create. Quick Fix 1008989 has been issued to resolve this problem.

Informix SoftwareThe AOS software uses the Informix database to store its Object definitions and initial/check-pointed values.

A single Informix user license is required for each simultaneous Application Object build (aos builddb) and create (aos create) process. When the build or create completes, the license is freed. While the mapping process (aos map) is running, it too requires a single Informix user license.

Solaris System SpecificsThe I/A Series for Solaris operating systems supports 32 concurrent users of the Informix database at any one time. Therefore, no more that 32 Applications are able to map at any one time. The practical limit is less than 32 because other packages are likely to be using Informix as well.

Windows System SpecificsThe I/A Series software at Version 6.2 or later running on a Windows operating system does not include the Informix software or license. For this reason, the AOS software for a Windows operat-ing system includes an Informix server license and 5 client licenses. A client license is used by each mapping application so some projects will require more client licenses. Part numbers exist to order additional licenses.

INI Software

Data Transfer LimitationsA TCP/IP network between the Isolation Station Server AW (local station) and Isolation Station AW (remote station) must be in place and operating before this software is installed.

The INI package has some limitations:

1. Unlike the INI15, the INI package does not have a dynamic database. Tag names must be configured if they are to be available.

2. Unlike the INI15, INI software tags do not appear in the Select or FoxSelect dis-plays. However, if the proper CBPs are monitored, the local detail display file works with the INI tags.

3. The release of the INI package covered by this document does not directly support redun-dancy. However, the non-redundant INI hosts can be attached to a redundant CSN. In this case, the INI package will be immune to cable faults within the CSN, but it will be susceptible to faults in its host, the NIC in the host, and the cable between the CSN and the NIC. In addition, application level redundancy can be provided.13

B0400EC Rev A 2. Assumptions and Limitations 4. It is possible for race conditions to exist over an INI software link that are not normally detectable in a Control Network based system. A race condition occurs when two events happen more or less simultaneously, but the scanning of the software causes it to see one, but not the other on the same scan. In this case, one may see the change in values in what is perceived to be an out-of-order sequence. Some applications use the change of a CBP to signal completion of certain data value changes. In the INI software, it is possible for the change in this flag to be reported before the values that it is signaling are reported. Applications need to be aware of this phenomenon. The same condition could occur in a Control Network based system, but the delays in the INI software make it more pronounced.

5. The INI software handling of Last Good Value (LGV) may differ from expectations. There are two forms of LGV. Restoration of value at bootup and holding values when they go bad.

The INI software restores the value from the Informix database when an object is created, but it does not update these values except for U or g maps. There are several reasons for this behavior:

While it might be possible to update the Informix database during a normal shutdown, doing so during an abnormal shutdown would be difficult to guar-antee.

There may be a long time between save and re-create and the value restored might be just as invalid as zero. For this reason, we feel that handling all such cases identically is better.

The time it takes to update the Informix database is quite high. If the attempt was made to update it frequently enough to catch a LGV, the load on the machine would increase and the updates would fall behind because Informix would not be able to keep up for large applications.

6. If the multi-map mode of the INI executable is used, all of the applications for a given instance must be in the same Isolation Station Server AW (local station). That is, a given INI instance can communicate with exactly one Isolation Station AW (remote station). The Isolation Station Server AW (local station) can, of course, retrieve data from any CP on its I/A Series Control Network.

The INI software uses the standard I/A Series data status flags (BAD and OOS) to indicate that the data value should not be used. Most of the control blocks (PID, RATIO, etc) validate their inputs by checking these bits. At startup, the INI software sets the BAD bit. During loss of communications, it sets BAD and OOS. This may mean that control schemes using Sequence Blocks or CALC blocks may need review.

The second type of LGV is implemented by the INI software. In this case, if a value is reported from the remote site and that value has a BAD bit set or an OOS bit set, we update the local status, but we do not change the local value. The belief is that the value returned with the BAD or OOS bit is unlikely to be useful.

7. The INI uses Informix. Informix is licensed for a fixed number of users (programs). The limit for Solaris systems is 32. For Windows systems, 5 licenses are supplied. Additional licenses are available for Windows operating systems.14

2. Assumptions and Limitations B0400EC Rev A Message Forwarding LimitationsEach instance of the Message Forwarding facility running in the Isolation Station Server AW (local station) is limited to 20 logical names each of which represents 20 targets on the Isolation Station AW (remote station). The limit of 20 logical names is an I/A Series IPC limitation.

Multiple copies of the Message Forwarding component may be run to work around this limita-tion. Each instance will require its own service name.

If the file specifying the alarm message destinations is changed, the Message Forwarding software must be stopped and restarted so that the file is re-read.

The Message Forwarding software is based on the assumption that the remote Compound:Block and the local Application:Object have exactly the same name. The Message Forwarding software does not convert the tag names contained in the forwarded messages.

Message Relay LimitationsEach instance of the Message Relay facility is limited to representing 20 processes in the other system. This limitation is imposed by the I/A Series IPC mechanism.

In some cases, the problem can be worked around by running multiple copies of the Message Relay facility in each box. Each instance will require its own service name.

If the file specifying the alarm message destinations is changed, the Message Relay software must be stopped and restarted so that the file is re-read.

Isolation Station Configurator

Intermediate Application ObjectsThe Isolation Station configurator uses intermediate Application Objects in the process of mov-ing data. The AOS application reads values from the process and stores them in the intermediate AOs. The INI application reads the intermediate AOs and moves the data to the target on the Isolation Station AW (remote station).

By convention, the intermediate AOs are the compound name of the source prefixed by an underscore (_). If the compound name is already 12 characters long, the Isolation Station config-urator uses an algorithm to search for an alternate name. Please see page 44 and page 54for details.15

B0400EC Rev A 2. Assumptions and Limitations 16

3. Installation - Windows Stations

The Isolation Station Software consists of the following software packages:

Application Object Services software - To be installed on both the Isolation Station Server AW and the Isolation Station AW.

Information Network Interface software - To be installed on just the Isolation Station Server AW.

Isolation Station Configurator - This software should be installed on the CP hosts in the system holding the Isolation Station Server AW.

The following is a brief explanation of the installation process of the Isolation Station software.

1. Install any relevant Foxboro I/A Series Quick Fixes as per Quick Fix Installation instructions. The FoxAPI software has frequent upgrades, so check with the IPS Glo-bal Customer Suport Center for the latest. Depending on the I/A Series version num-ber the following Quick Fixes might need to be applied before the AOS software is installed.

a. Quick Fix 1008285 - Updates the fox.dll installed during a Server 2003 Version 8.1 Day 0 installation.

b. Quick Fix 1008859 - Eliminates a problem that can prevent large numbers of Application Objects from being created.

c. Quick Fix 1009515 - Updates MKS/NutCracker v8.7 software to v9.1p1. Run the command, mksinfo, at a DOS prompt to check the current version of MKS/NutCracker before installing this Quick Fix.

2. Turn off the I/A Series software and reboot the PC.

3. Install and configure the Informix software package on both the Isolation Station Server AW and the Isolation Station AW and enable this software to start on reboot. The Informix software must be installed and configured before Application Objects can be created.

4. Install the AOS software on both the Isolation Station Server AW and the Isolation Station AW.

5. Install the FoxAPI software on just the Isolation Station Server AW.

6. Install the INI software on just the Isolation Station Server AW.

7. Install the Isolation Station Configurator software on the CP hosts in the system.

8. Configure the I/A Series software to support the required number of Application Objects.

9. Restore the machine to running condition: re-enable the starting of I/A Series soft-ware and FoxAPI software on reboot, and reboot the machine.

10. Verify that the required software processes are running.17

B0400EC Rev A 3. Installation - Windows Stations Isolation Station Server AW InstallationThis section describes the installation process for the Isolation Station Server AW (local station) on a 70 Series station with a Windows operating system.

Informix Dynamic Server (IDS), Version 10.00The Informix Dynamic Server software is used for the AOS database and is only installed on the Isolation Station Server AW. Before the AOS software is installed the Informix Dynamic Server (IDS) software must be installed, configured and properly running.

Be sure to note the following before installing the IDS Version 10.00 software.

The I/A Series software must be turned off and PC rebooted before installing the IDS software.

The IDS software must be installed in the D:\WIN32APP\Informix folder.

The IDS Version 10.00 software should be installed on PCs running the Microsoft Windows Server 2003 and Windows XP operating systems. (The IDS Version 9.40 software is only to be installed on PCs running the Microsoft Windows NT operating system.)

Be sure the IDS software is properly running before attempting to install the AOS software.

The following steps must be taken when installing the Informix Dynamic Server Version 10.00 software on a PC running the Windows Server 2003 or Windows XP operating system.

1. The I/A Series software must be turned off and PC rebooted before proceeding with the installation of the IDS software. Reference the specific I/A Series documentation for detailed instructions on setting this feature.

2. Insert the IBM Informix Dynamic Server (IDS) Version 10.00 media into the CD-ROM drive in the AW/WP.

3. Start the installation process by selecting My Computer, then the CD-ROM drive letter (for example E:) and double click setup.exe.

4. At the Welcome window select Next

5. At the Product Selection window only check the following:IBM Informix Dynamic Server w/J FoundationIBM Informix-Connect 2.90.TC3IBM Informix Client-SDK 2.90.TC3

6. Accept the license agreement.

7. At the Installation Wizard window select Next.

8. At the Domain Install Option window select Next.

9. The installation directory must be set to D:\WIN32APP\Informix. (This entry is not case sensitive.)

10. Select the Install Method of Typical and select Next.

11. At the Role Separation window leave the option unchecked and select Next.

12. At the System Administration window create the user informix with the password gnomes and then select Next.

13. At the Copy Installation Files window select Next. Installation begins.18

3. Installation - Windows Stations B0400EC Rev A 14. At the Configure the Dynamic Server window select Finish.

15. At the Server Number window leave the default set to 0 (zero) and select Next.

16. At the Name the Dynamic Server window confirm that the default Dynamic Server Name is ol_ (for example ol_1aw70f ) and select Next. Where is the name (letterbug) given to this PC and must be entered in lower case letters.

17. At the TCP Sockets - olsoctcp window leave the default settings of Service Name: turbo and Port Number: 1526 and select Next.

18. At the System Administration window leave the Computer options set to \\ (for example \\1AW70F) and select Finish. Where is the name (letterbug) given to this PC and must be entered in upper case letters.

19. At the Installation Message window do not initialize now. Select NO. Ignore any message regarding OnSNMP that might display. Select OK.

20. At the next Installation Message window verify that you are skipping the initialization process at this time. Select Yes.

21. At the Server Installed window select OK.

22. The IBM Informix-Connect installation starts immediately.

a. At the Welcome to the InstallShield Wizard for IBM Informix-Connect 2.90 window select Next.

b. Accept the license agreement and select Next.

c. Enter the customer information and select Next.

d. At the Setup Type window select Custom and select Next.

e. At the Destination Folder window, select the Change button and enter the folder name D:\WIN32APP\Informix, select OK, and then select Next. The Informix-Connect software must be installed to this folder.

f. At the Custom Setup window leave the default set to IBM Informix-Connect and select Next.

g. At the Ready to Install the Program window select Install. The installation begins.

h. At the IBM Informix-Connect Installation Validation window select Next.

i. At the InstallShield Wizard Completed window select Finish.

23. The IBM Informix Client-SDK installation starts immediately.

a. At the Welcome to the IBM Informix Client-SDK 2.90 Setup Wizard window select Next.

b. Accept the license agreement and select Next.

c. Enter the customer information and select Next.

d. At the Setup Type window select Custom and select Next.

e. At the Destination Folder window, select the Change button and enter the folder name D:\WIN32APP\Informix, select OK, and then select Next. The Client-SDK software must be installed to this folder.

f. Set INFORMIXDIR to the newly chosen directory and select Next.19

B0400EC Rev A 3. Installation - Windows Stations g. At the Custom Setup window leave the default set to IBM Informix Client-SDK and select Next.

h. At the Ready to Install the Program window select Install.

i. At the IBM Informix Client-SDK Installation Validation window select Next.

j. At the Completing the IBM Informix Client-SDK 2.90 Setup Wizard window select Finish.

After the Informix Client-SDK software installation is complete, verify the following variables in the Informix Setnet32 utility. If any of the following variable settings are missing, set the variable accordingly.

1. Select Start, then Programs, the IBM Informix Connect 2.90, and then Setnet32.

a. INFORMIXDIR= D:\WIN32APP\Informix (This line is not case sensitive.)

b. INFORMIXSERVER= ol_ (This line is in lower case letters.)(For example: INFORMIXSERVER=ol_2aw70b) Where is the name (letterbug) given to this PC.

c. INFORMIXSQLHOSTS= \\ (This line is in upper case letters.)(For example: INFORMIXSQLHOSTS=\\2AW70B) Where is the name (letterbug) given to this PC.

d. Select OK.

2. Setup the Informix Services to restart automatically. From the Services window:

a. Select Informix IDS - ol_ and set the Startup option to Automatic and set the Startup Parameters option to -iy, select Start and then select OK. If required, reference you specific operation systems help screens for information regarding starting services with startup parameters.

b. Select Informix Dynamic Messaging Services and set the Startup option to Automatic.

3. Setup the Informix Server SNMP Service to restart manually. From the Services window select Informix Server Discovery Process for SNMP and set the Startup option to Manual and then select OK. (AOS software does not require SNMP services.)

4. Verify that the Informix database server is up and running correctly by:

a. Ensuring that the oninit.exe process is running using the Task Manager.

b. Verify that the d:/win32app/informix/ol_.log file has ended with lines similar to these:15:41:53 'sysmaster' database built successfully.15:41:54 'sysutils' database built successfully.15:41:54 'sysuser' database built successfully15:42:00 Init operation complete - Mode Online Initialized

c. Select Start, then Programs, the IBM Informix Connect 2.90, and then launch the ILogin Demo utility to verify proper installation.

At the ILogin Demo window select File and then Run.

Take the default settings in the window. For this test the default settings are:Server default setting is ol_Stores Database default setting is stores7 Select OK to start the test.20

3. Installation - Windows Stations B0400EC Rev A The test is successful if the message Database stores7 not found on the server appears.

TIPIf any of the tests in step 3 fails:* Close the test window and carefully verify/correct the Informix Setnet32 settings and then repeat the ILogin Demo test.* Wait a couple of minutes to give Informix plenty of time to initialize, then repeat the ILogin Demo test.* If the test still fails uninstall the Informix and SDK software and start the third-party installation process over.

Installing FoxAPI Related SoftwareThe latest FoxAPI software Quick Fix should be installed before installing the INI70 software. Before installing the Quick Fix shipped with the INI70 software, contact the IPS Global Cus-tomer Support Center to ensure that it is the latest available.

NOTEThe newest FoxAPI software Quick Fix should always be used.

After confirming that the Quick Fix is the latest, either install it from the INI70 media with the instructions below or download the latest FoxAPI Quick Fix.

1. Open a DOS command window.

2. Check the provided Quick Fix for your Operating System and ensure that it is the lat-est.cd E:\Windows\FoxUtilDir\QuickFix\

3. Use the file2dsk utility to create the Quick Fix floppy disks. (The file2dsk utility can be located on the INI70 media, E:\FoxUtilDir\file2dsk_).

4. Follow the instructions provided in the QFxxxxxx.txt instructions.

AOS SoftwareThis section describes the installation of the AOS software on a 70 Series station with a Windows operating system that is to be the Isolation Station Server AW (local station). Please reference the Application Object Services Users Guide, B0400BZ, document for more detailed installation and configuration instructions.

1. The I/A Series software must be turned off before proceeding with the installation of the AOS software. Modify the Foxboro I/A Series software startup options. Reference your specific I/A Series documentation for detailed instructions on setting these fea-tures.

2. Use the I/A Series shutdown mechanism to reboot the PC.

3. Insert the AOS software for the Windows operating system CD-ROM into the CD-ROM drive in the AW/WP.

4. Start the installation process by selecting My Computer, then the CD-ROM drive letter (for example E:).21

B0400EC Rev A 3. Installation - Windows Stations CAUTION!In the next step, it is critical to select the correct folder (MKS8, HSP or SPS) to install the AOS software from. This folder selection is based upon the I/A Series software version and operating system the PC is running. * The MKS8 folder is for 70 Series stations running I/A Series V8.1.1, V8.2 and later software (Windows XP Service Pack 2 or Windows Server 2003 OS).* The HPS folder is for 70 Series stations running I/A Series V8.0x and V8.1x software (Windows XP Service Pack 1 OS).* The SPS folder is for 70 Series stations running I/A Series V4.3, V6.1+ and V7.x software (Windows XP Service Pack 1 OS).

5. Select the E:\Windows\\AOS folder.

6. Select the setup.exe file.

7. After the installation is complete, turn the I/A Series software back on. Modify the Foxboro I/A Series startup options. Reference your specific I/A Series documentation for detailed instructions on setting these features.

8. Reboot the PC.

Installing the INI70 SoftwareThis section describes the installation of the INI70 software on a 70 Series station with a Windows operating system that is to be the Isolation Station Server AW (local station). Please reference the Information Network Interface for Solaris and Windows Software User Guide, B0400BM, document for more detailed installation and configuration instructions.

1. The I/A Series software must be turned off before proceeding with the installation of the INI70 software. Modify the Foxboro I/A startup options. Reference your specific I/A Series documentation for detailed instructions on setting these features.

2. Use the I/A Series shutdown mechanism to reboot the PC.

3. Insert the INI70 media into the CD-ROM drive in the AW/WP.

4. Start the installation process by selecting My Computer, then the CD-ROM drive letter (for example E:).

CAUTION!In the next step, it is critical to select the correct folder (MKS8, HSP or SPS) to install the INI70 software from. This folder selection is based upon the I/A Series software version and operating system the PC is running. * The MKS8 folder is for 70 Series stations running I/A Series V8.1.1, V8.2 and later software (Windows XP Service Pack 2 or Windows Server 2003 OS).* The HPS folder is for 70 Series stations running I/A Series V8.0x and V8.1x software (Windows XP Service Pack 1 OS).* The SPS folder is for 70 Series stations running I/A Series V4.3, V6.1+ and V7.x software (Windows XP Service Pack 1 OS).

5. Select the E:\Windows\\INI70 folder.

6. Select the setup.exe file.22

3. Installation - Windows Stations B0400EC Rev A 7. Turn the I/A Series software back on. Modify the Foxboro I/A startup options. Refer-ence your specific I/A Series documentation for detailed instructions on setting these features.

8. Reboot the PC.

Isolation Station AW InstallationThis section describes the installation process for the Isolation Station AW (remote station) on a 70 Series station with a Windows operating system.

Installing FoxAPI Related SoftwareThe latest FoxAPI software Quick Fix should be installed before installing the INI70 software. Before installing the Quick Fix shipped with the INI70 software, contact the IPS Global Cus-tomer Support Center to ensure that it is the latest available.

NOTEThe newest FoxAPI software Quick Fix should always be used.

After confirming that the Quick Fix is the latest, either install it from the INI70 media with the instructions bel

Isolation Station Software

Documents

Transcript of Isolation Station Software