B0400EC

REV A

I/A Series®
Isolation Station Software
User’s 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 affiliates
All 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 .......................................................................................................... 1
Isolation Station AW ............................................................................................................ 2
Isolation Station Firewall ...................................................................................................... 2
Isolation Station Server AW ................................................................................................. 2
Product Features ....................................................................................................................... 3
Requirements ............................................................................................................................ 5
Customer Supplied Network ................................................................................................ 5
I/A Series Platform ............................................................................................................... 5
Isolation Station AW (Remote Station) ........................................................................... 5
Isolation Station Server AW (Local Station) .................................................................... 6
Implementation ........................................................................................................................ 6
Redundancy .............................................................................................................................. 7

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

Isolation Station Server AW (Local Station) .............................................................................. 9
AOS/INI Applications ........................................................................................................ 10
OM Connections for AIM*API and FoxAPI Applications .................................................. 10
Isolation Station AW (Remote Station) ................................................................................... 11
AOS Software - Restrictions and Conventions ........................................................................ 11
Reserved Compound Level Names ..................................................................................... 12
Object Level Names ........................................................................................................... 12
Object Manager Limitations ............................................................................................... 12
Informix Software .............................................................................................................. 13
Solaris System Specifics ................................................................................................. 13
Windows System Specifics ............................................................................................. 13
INI Software ........................................................................................................................... 13

iii
B0400EC – Rev A Contents

Data Transfer Limitations .................................................................................................. 13

Message Forwarding Limitations ........................................................................................ 15
Message Relay Limitations .................................................................................................. 15
Isolation Station Configurator ................................................................................................. 15
Intermediate Application Objects ....................................................................................... 15

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

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

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

Isolation Station Server AW Installation .................................................................................. 25
Installing FoxAPI Related Software .................................................................................... 25
FoxSpy Software ................................................................................................................. 26
NetFoxAPI Client Software ................................................................................................ 26
Latest FoxAPI Quick Fix .................................................................................................... 27
AOS Software ..................................................................................................................... 27
INI51 Software .................................................................................................................. 29
Message Forwarding ...................................................................................................... 32
Message Relay ................................................................................................................ 32
Isolation Station AW Installation ............................................................................................ 33
NetFoxAPI Client Software ................................................................................................ 33
Latest FoxAPI Quick Fix .................................................................................................... 33
AOS Software ..................................................................................................................... 34
Controller Hosts Installation ................................................................................................... 36
Isolation Station Configurator ............................................................................................ 36

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

Isolation Station Server AW (Local Station) ............................................................................ 37
AOS Software ..................................................................................................................... 38
INI Software ...................................................................................................................... 38
Message Forwarding ...................................................................................................... 39
Message Relay ................................................................................................................ 39
Manual Startup .................................................................................................................. 39
Automatic Startup .............................................................................................................. 40
Isolation Station AW (Remote Station) ................................................................................... 40
AOS Software ..................................................................................................................... 40

iv
Contents B0400EC – Rev A

Message Forwarding ........................................................................................................... 41

Message Relay .................................................................................................................... 41
Isolation Station Configurator ................................................................................................. 41
Windows Stations .............................................................................................................. 41
Use Local Station ........................................................................................................... 43
Intermediate Compound Names ........................................................................................ 44

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

Isolation Station Server AW (Local Station) ............................................................................ 47
AOS Software ..................................................................................................................... 48
INI Software ...................................................................................................................... 48
Message Forwarding ...................................................................................................... 49
Message Relay ................................................................................................................ 49
Manual Startup .................................................................................................................. 49
Automatic Startup .............................................................................................................. 50
Isolation Station AW (Remote Station) ................................................................................... 51
AOS Software ..................................................................................................................... 51
Message Forwarding ........................................................................................................... 51
Message Relay .................................................................................................................... 51
Isolation Station Configurator ................................................................................................. 51
Solaris Stations ................................................................................................................... 52
Use Local Station ........................................................................................................... 53
Intermediate Compound Names ........................................................................................ 54

7. Operation........................................................................................................................ 57
Application Object Services (AOS) .......................................................................................... 57
Typical Uses ....................................................................................................................... 58
Information Network Interface (INI) ...................................................................................... 59
Message Forwarding ........................................................................................................... 59
Message Relay .................................................................................................................... 61
Message Relay and Well-Known Names ........................................................................ 61
Message Relay and Locally Known Names .................................................................... 61
Message 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 .................................................................................... 65
Data Backup ...................................................................................................................... 65
Package Removal ................................................................................................................ 65
Upgrades ............................................................................................................................ 65
I/A Series Software Upgrades .............................................................................................. 65
Day 0 and Day 1 .......................................................................................................... 65
Quick Fixes ........................................................................................................................ 65
INI70 Software ....................................................................................................................... 66

v
B0400EC – Rev A Contents

Package Removal ................................................................................................................ 66

I/A Series Software Upgrades .............................................................................................. 66
Day 0 Upgrades ............................................................................................................. 66
Non-Day 0 Upgrades .................................................................................................... 67
INI Package Upgrades ........................................................................................................ 67
Saving Configuration Data ............................................................................................ 67
Stopping the INI Package .............................................................................................. 68
Loading INI Package ..................................................................................................... 68
Restoring Configuration Information ............................................................................ 68
Restart the INI Package ................................................................................................. 69
Quick Fixes ........................................................................................................................ 69
AOS Software ......................................................................................................................... 69
Package Removal ................................................................................................................ 69
I/A Series Software Upgrades .............................................................................................. 70
Day 0 Upgrades ............................................................................................................. 70
Non-Day 0 Upgrades .................................................................................................... 70
AOS Software Upgrades ..................................................................................................... 70
Saving Configuration Data ............................................................................................ 70
Loading AOS Package ................................................................................................... 70
Restoring Configuration Information ............................................................................ 71
Restart the AOS Package ............................................................................................... 71
Quick Fixes ................................................................................................................... 71

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

Isolation Station Configuration Utility .................................................................................... 73
Data Backup ...................................................................................................................... 73
Package Removal ................................................................................................................ 73
Upgrades ............................................................................................................................ 73
I/A Series Software Upgrades .............................................................................................. 73
Day 0 and Day 1 .......................................................................................................... 73
Quick Fixes ................................................................................................................... 73
INI51 Software ....................................................................................................................... 74
Package Removal ................................................................................................................ 74
I/A Series Software Upgrades .............................................................................................. 74
Day 0 Upgrades ............................................................................................................. 74
Non-Day 0 Upgrades .................................................................................................... 74
INI51 Software Upgrades ................................................................................................... 75
Saving Configuration Data ............................................................................................ 75
Stopping the INI Package .............................................................................................. 75
Loading INI Package ..................................................................................................... 76
Restoring Configuration Information ................................................................................. 76
Restart the INI Package ................................................................................................. 76
Quick Fixes ........................................................................................................................ 76
AOS Software ......................................................................................................................... 76
Package Removal ................................................................................................................ 76
I/A Series Software Upgrades .............................................................................................. 77
Day 0 Upgrades ............................................................................................................. 77

vi
Contents B0400EC – Rev A

Non-Day 0 Upgrades .................................................................................................... 77

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

10. Troubleshooting............................................................................................................ 79
General ................................................................................................................................... 79
Station Overload ..................................................................................................................... 79
CPU Cycles ........................................................................................................................ 79
I/O Loading ....................................................................................................................... 79
Memory ............................................................................................................................. 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 ...................................................................................................................... 85
Synopsis ............................................................................................................................. 85
Examples ....................................................................................................................... 85

Index .................................................................................................................................... 87

vii
B0400EC – Rev A Contents

viii
Figures
1-1. Shared Map Files ........................................................................................................... 3
1-2. Data Flow ..................................................................................................................... 5
1-3. Redundancy Example 1 ................................................................................................. 7
1-4. Redundancy Example 2 ................................................................................................. 7
5-1. Isolation Station System Overview .............................................................................. 37
5-2. Staring the Isolation Station Configurator (Windows Stations) ................................... 42
5-3. INI and IS Map File Builder (Windows Stations) ....................................................... 42
5-4. INI and IS Map File Builder - Local Station (Windows Station) ................................. 43
5-5. INI and IS Map File Builder - Map File View (Windows Stations) ............................. 44
5-6. Intermediate Compound Naming (Windows Stations) ............................................... 45
6-1. Isolation Station System Overview .............................................................................. 47
6-2. Starting the Isolation Station Configurator (Solaris Stations) ...................................... 52
6-3. INI and IS Map File Builder (Solaris Stations) ............................................................ 52
6-4. INI and IS Map File Builder - Local Station (Solaris Stations) .................................... 53
6-5. INI and IS Map File Builder - Map File View (Solaris Stations) .................................. 54
6-6. Intermediate Compound Naming (Solaris Stations) .................................................... 55
7-1. AOS Software Data Flow ............................................................................................ 58
7-2. Data Flow from Remote Station to Local Station in a Peer-to-Peer Application .......... 59
7-3. Message Forwarding Functionality .............................................................................. 60
7-4. Message Relay of Broadcast Messages .......................................................................... 62

ix
B0400EC – Rev A Figures

x
Tables
1-1. Mapping Operators ....................................................................................................... 4
5-1. Application Naming .................................................................................................... 44
6-1. Application Naming .................................................................................................... 54

xi
B0400EC – Rev A Tables

xii
Preface

Purpose
This 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.

Audience
This document assumes a user who is familiar with:
♦ The system’s 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 Information
This is the initial release of this document.

Reference Documents
The 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 User’s Guide (B0400BZ)
♦ Information Network Interface for Solaris and Windows Software User Guide
(B0400BM)
♦ Networked FoxAPI™ Client Software Installation Instruction (Solaris Only)

Terms and Definitions

The 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 program’s 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 Concept

The 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 AW
This 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 system’s 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 Firewall

A 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 AW

The 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 Features
The 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 AW’s (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.

Map Files

Informix

AOS INI Customer

Control
C:B.P Network
_A:O.A Supplied A:O.A
Network
CP Isolation Station Server AW Isolation Station AW

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.

3
B0400EC – Rev A 1. Overview

In this situation there are only a very few mapping operators that can work.

TIP
For more information about mapping, please reference the Application Object
Services User’s Guide (B0400BZ) manual’s map File section and the Information
Network Interface for Solaris and Windows Software User Guide (B0400BM)
manual’s map File section.

Table 1-1. Mapping Operators

Station Operator Description Purpose

Isolation C Constant Holds the external values.
Station
Isolation p AOS g for STRING Used to update the outside values.
Station (lower case) AOS R for non-STRING Does not secure the target outer AOA.
Server INI P for STRING
INI P for non-STRING
Isolation w AOS g for STRING Used to update outside values. Secures
Station (lower case) AOS R for non-STRING the target outer AOA.
Server INI W for STRING
INI W for non-STRING

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.

4
1. Overview B0400EC – Rev A

Isolation Station Server AW Isolation Station AW

(Local Station ) (Remote Station )

Isolation
Station
Configuration
Utility

Local Map File Remote Map File

.map file with intermediate name for AOA ;

AOS .map file for Isolation Station.
used as buffer by INI local station.
C:B.P X C
_C:B.P C:B.P P

Informix aos builddb Informix aos builddb

aos create
aos create
User
Applications

_C:B.P C:B.P
AOS (Intermediate A:O.A)
INI FoxView
(Replicated Data)

AIM*
Protected Unprotected

Control Network Plant Information Network

C:B.P

CP

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.

5
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.

Implementation
The 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

Redundancy
Isolation 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.

Isolation Station
Isolation Station
Server AW
AW #1
#1
Firewall #1

Control Network

Isolation Station
Isolation Station
Server AW
AW #2
#2
Firewall #2

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.

Isolation Station
Isolation Station
Server AW
AW #1
#1

Control Network Plant Information Network

Isolation Station Firewall

Isolation Station
Server AW
AW #2
#2

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.

7
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.

NOTE
There 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.

NOTE
If 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 User’s Guide (B0193YN) and FoxAPI V4.3 Release
Notes (B0193UC).

9
B0400EC – Rev A 2. Assumptions and Limitations

AOS/INI Applications
It 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 Server’s 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 Applications

When 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.

NOTE
The 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 AW70s
c:\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 OM’s 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 Conventions

The 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 block’s 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 Names

Each 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 User’s Guide.

NOTE
As 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 Names

Each 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 User’s Guide.

Object Manager Limitations

By 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 user’s 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 User’s
Guide (B0400BZ).

NOTE
There 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 Software
The 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 Specifics

The 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 Specifics

The 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 Limitations
A 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 Limitations

Each 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 Limitations

Each 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 Objects
The 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 Installation

This 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.00

The 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 Foundation
IBM Informix-Connect 2.90.TC3
IBM 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_<pcname> (for example ol_1aw70f ) and select Next. Where <pcname> 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 \\<PCNAME>
(for example \\1AW70F) and select Finish. Where <PCNAME> 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_<pcname> (This line is in lower case letters.)
(For example: INFORMIXSERVER=ol_2aw70b) Where <pcname> is the name
(letterbug) given to this PC.
c. INFORMIXSQLHOSTS= \\<PCNAME> (This line is in upper case letters.)
(For example: INFORMIXSQLHOSTS=\\2AW70B) Where <PCNAME> 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_<pcname> 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 system’s 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_<pcname>.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 successfully
15: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_<pcname>
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.

TIP
If 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 Software

The 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.

NOTE
The 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\<OperatingSystem>
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_<OS>).
4. Follow the instructions provided in the QFxxxxxx.txt instructions.

AOS Software
This 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 User’s 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\<MSK8_HPS_SPS>\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 Software

This 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\<MSK8_HPS_SPS>\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 Installation

This 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 Software

The 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.

NOTE
The 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\<OperatingSystem>
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_<OS>).
4. Follow the instructions provided in the QFxxxxxx.txt instructions.

AOS Software
This 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 AW (remote station). Please refer-
ence the Application Object Services User’s Guide, B0400BZ, document for more detailed installa-
tion 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:).

23
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\<MSK8_HPS_SPS>\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.

Controller Hosts Installation

This section deals with the software that should be installed on the controller hosts in the system
holding the Isolation Station Server AW (local station).

Isolation Station Configurator

The Isolation Station Configurator is dependent upon the AOS and INI packages being installed
and configured properly. This software should be installed on the CP hosts in the system holding
the Isolation Station Server AW.
Install the Isolation Station Configurator:
1. Insert the Isolation Station Configurator media into the CD-ROM drive of the AW.
2. Start the installation process by selecting My Computer, then the CD-ROM drive
letter (for example, E:)
3. Select the E:\Windows\ISS folder.
4. Select the setup.exe file.
5. At the Welcome to the Install Shield Wizard for Isolation Station window, select Next.
6. At the License Agreement window, accept the terms and then select Next.

24
4. Installation - Solaris 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 Support Center for the latest.
2. Enter the Single User Mode.
3. Install the AOS software on both the Isolation Station Server AW and the Isolation
Station AW.
4. Install the FoxAPI software on just the Isolation Station Server AW.
5. Install the INI software on just the Isolation Station Server AW.
6. This software should be installed on the CP hosts in the system holding the Isolation
Station Server AW.
7. Configure the I/A Series software to support the required number of Application
Objects.
8. Reboot the machine into multi-user mode.
9. Verify that the required software processes are running.

Isolation Station Server AW Installation

This section describes the installation process for the Isolation Station Server AW (local
station) on a 50 Series station with a Solaris operating system.

Installing FoxAPI Related Software

There are three pieces of FoxAPI software to install:
1. Local FoxAPI Quick Fix
2. NetFoxAPI™ tools
3. foxspy - FoxAPI diagnostic tool
This software should be installed before the INI51 software.

25
B0400EC – Rev A 4. Installation - Solaris Stations

NOTE
The FoxAPI Quick Fix and the foxspy utility should be installed on the Isolation
Station AW (remote station).

Once these items are installed, the Isolation Station Server AW (local station) and Isolation
Station AW (remote station) are prepared for the INI51 software installation.

FoxSpy Software
Only the FoxSpy Software has to be installed, if the foxspy executable does not exist in the
/opt/fox/ais/bin directory. Generally, the FoxSpy software should be loaded on each machine
furnishing data to the INI51 host.
1. Start a VT100 session on the INI51 host machine.
2. Check to make sure that the foxspy executable does not exist.
ls -l /opt/fox/ais/bin/foxspy
3. If FoxSpy does not exist, mount the INI51 CD-ROM:
mount -F hsfs -o ro /dev/sr0 /cdrom
4. Change to the Solaris/FoxUtilDir/FoxSpy directory on the CD-ROM:
cd /cdrom/Solaris/FoxUtilDir/FoxSpy
5. Copy the foxspy executable to the /opt/fox/ais/bin directory.
cp foxspy /opt/fox/ais/bin

NetFoxAPI Client Software

On the Isolation Station Server AW (local station), install the NetFoxAPI Client software
supplied as part of the INI51 deliverable.
1. Start a VT100 session on the INI51 host machine.
2. Change to the /opt directory.
cd /opt
3. Mount the INI51 CD-ROM:
mount -F hsfs -o ro /dev/sr0 /cdrom
4. Extract the files from the CD-ROM. This will create a directory holding the
NetFoxAP deliverables (/opt/netFoxAPIClient).
tar xvf /cdrom/Solaris/FoxUtilDir/NetFoxAPI/netFoxAPI.tar
5. Place the libnetfox.a library in the /usr/lib directory.

26
4. Installation - Solaris Stations B0400EC – Rev A

Latest FoxAPI Quick Fix

Before installing the Quick Fix shipped with the INI51 software, contact the IPS Global Cus-
tomer Support Center to ensure that it is the latest available FoxAPI Quick Fix.

NOTE
The newest FoxAPI Quick Fix should always be used.

After confirming that the Quick Fix is the latest. Install it from the INI51 media or download
and install the later Quick Fix.
1. Start a VT100 session on the INI51 host machine.
2. Mount the INI51 CD-ROM:
mount -F hsfs -o ro /dev/sr0 /cdrom
3. Check the provided Quick Fix for your Operating System and ensure that it is the
latest Quick Fix available.
cd /cdrom/Solaris/FoxUtilDir/QuickFix/<OperatingSystem>
4. Use the file2dsk utility to create the Quick Fix floppy disks.
(The file2dsk utility can be located on the INI51 CD-ROM at
/cdrom/Solaris/FoxUtilDir/file2dsk_<OS>).
5. Follow the instructions provided in the QFxxxxxx.txt instructions.

AOS Software
This section describes the installation of the AOS software on a 50 Series station with a
Solaris operating system that is to be the Isolation Station Server AW (local station) or the
Isolation Station AW (remote station). Please reference the Application Object Services User’s
Guide, B0400BZ, document for more detailed installation and configuration instructions.

NOTE
Initial installations should be performed while in single user mode because the
operating system is modified to allow larger numbers of Application Objects to be
created. If the installation is an update, the -override and -online options of
installAOS may be used.

In the examples that follow the chosen installation directory is /opt.

Installation requires the following steps.

1. Enter single user mode on the AP or AW to host the AOS package and do
the following:
a. On an AW51, select the Shutdown_AW menu pick under SftMnt in the
Proc_Eng_Env. Select Shutdown to confirm. When the password prompt appears,
enter the root password.
b. From the System Console directly connected to the AP51, type
shutdown -y -g0. When the password prompt appears, enter the root password.
2. Mount any partitions that have become unmounted.
a. Type cd / to move to the root directory.

27
B0400EC – Rev A 4. Installation - Solaris Stations

b. Check to see what is currently mounted. Type df -F ufs -k

c. If the partition for software installation is not mounted, mount it now. For
example, if /opt is the location for the software installation and it is not mounted,
mount it by typing: mount /opt
3. Check free disk space in the /opt partition by typing df -k -F ufs. The AOS soft-
ware is normally loaded in the /opt partition. If the /opt partition is too small to hold
the 12 megabytes of software that comprise the AOS package, either mount another
hard drive or concatenate another hard drive to the /opt partition per the System
Administration for Solaris document. The installation script uses symbolic links from
the user specified installation directory to /opt if /opt is not the user specified instal-
lation directory.
4. Change to /opt and create the aos directory to load the install script regardless of
where the final destination is by typing:
cd /opt
mkdir aos
5. Insert the AOS for Solaris OS media in the CD-ROM drive attached to the target AP
or AW.
6. Mount the CD-ROM:
mount -F hsfs -o ro /dev/sr0 /cdrom
7. Change to the aos directory on the CD-ROM:
cd /cdrom/Solaris/SPS/aos
8. To begin the installation of the AOS software, simply type:
./installAOS or
./installAOS -online
./installAOS -override
./installAOS -online -override
The choice depends on whether or not the machine needs to be placed in single-user
mode. If the OM changes need to be made, use the first choice listed. If not, the
-online option is appropriate.

NOTE
* The -online option is typically used on upgrades since the OM settings typically
do not need to be changed during an upgrade.
* The -online option in this sense simply refers to the AW as a whole. It does not
mean that the AOS software can be running during an update.
* The -override option forces the new software installation over of a previous ver-
sion.

The following is displayed on the screen:

InstallAOS: Starting Now.

installAOS: Checking AOS Versions.
**** AOS no yet installed on this system. ***

Where is the AOS software to be installed? [/opt]?

28
4. Installation - Solaris Stations B0400EC – Rev A

At this point, the directory to hold the AOS software should be entered. The default is
taken by simply pressing the Enter key. Once the directory has been entered, it will be
confirmed as follows:

Moving to install directory [/opt]

Once a target directory is specified, the following will appear:
Extracting files...
Installing Application Object Services (AOS) Version 3.00.Beta20
07/24/01
At this point files are uncompressed and are placed in the appropriate directories. If
any version of the AOS software is already installed on the target machine, the
installAOS script refuses to install the new version of the AOS software, and exits.
Refer to the Application Object Services User’s Guide, B0400BZ, for instructions on
how to remove a previous version of the AOS package.
9. Before rebooting into multi-user mode, the following should be completed:
♦ Modify the Operating System OM_NUM_OBJECTS according to the instruction in the
Application Object Services User’s Guide, B0400BZ. The modification of
OM_NUM_OBJECTS must be made before the machine is rebooted.
The changes made above take effect after the machine is rebooted or restarted into multi-user
mode.
♦ Type:
sync;sync;sync
reboot
Please reference the Application Object Services User’s Guide, B0400BZ, document for more details
installation instructions.

INI51 Software
This section describes the installation of the INI51 software on a 50 Series station with a
Solaris operating system that is to be the Isolation Station Server AW (local station). Please ref-
erence the Information Network Interface for Solaris and Windows Software User Guide, B0400BM,
document for more detailed installation and configuration instructions.

NOTE
Initial installations should be performed while in single user mode because the
operating system is modified to allow larger numbers of Application Objects to be
created. If the installation is an update, the -override and -online options of
installAOS may be used.

In the examples that follow the chosen installation directory is /opt.

Installation requires the following steps:

1. Enter single user mode on the AP or AW to host the INI51 package, i.e., the Isolation
Station Server AW (local station), by doing one of the following:

29
B0400EC – Rev A 4. Installation - Solaris Stations

a. On an AW51, select the Shutdown_AW menu pick under SftMnt in the

Proc_Eng_Env. Select Shutdown to confirm. When the password prompt appears,
enter the root password.
b. From the System Console directly connected to the AP51, type
shutdown -y -g0. When the password prompt appears, enter the root password.
2. Mount any partitions that have become unmounted.
a. Type cd / to move to the root directory.
b. Check to see what is currently mounted. Type df -F ufs -k
c. If the partition for software installation is not mounted, mount it now. For
example, if /opt is the location for the software installation and it is not mounted,
mount it by typing: mount /opt
3. Check free disk space in the /opt partition by typing df -k -F ufs. INI51 package is
normally loaded in the /opt partition. If the /opt partition is too small to hold the
12 megabytes of software that comprise the INI51 package, either mount another
hard drive or concatenate another hard drive to the /opt partition per the System
Administration for Solaris operating systems document. The installation script uses
symbolic links from the user specified installation directory to /opt if /opt is not the
user specified installation directory.
4. Change to /opt and create the aos directory to load the install script regardless of
where the final destination is by typing:
cd /opt
mkdir aos
5. Insert the INI51 Media in the CD-ROM drive attached to the target AP or AW.
6. Mount the CD-ROM:
mount -F hsfs -o ro /dev/sr0 /cdrom
7. Change to the Solaris directory on the CD-ROM:
cd /cdrom/Solaris/SPS/INI
8. To begin the installation of the INI51 software, simply type:
./installAOS or
./installAOS -online
./installAOS -override
./installAOS -online -override
The choice depends on whether or not the machine needs to be placed in single-user
mode. If the OM changes specified in step 8 need to be made, use the first choice
listed. If not, the -online option is appropriate. Reference the Application Object Ser-
vices User’s Guide, B0400BZ, for more information about the installAOS command.

30
4. Installation - Solaris Stations B0400EC – Rev A

NOTE
The -online option is typically used on upgrades since the OM settings typically do
not need to be changed during an upgrade.

Though the option is -online, the INI51 software must be stopped before install-
ing the upgrade. Online in this sense simply refers to the AW as a whole. It does not
mean that the INI51 software can be running during an update.

The -override option forces the new software installation over of a previous ver-
sion.

The following is displayed on the screen:

InstallAOS: Starting Now.

installAOS: Checking AOS Versions.
**** AOS no yet installed on this system. ***

Where is the AOS software to be installed? [/opt]?

At this point, the directory to hold the INI51 software should be entered. The default
is taken by simply pressing the Enter key. Once the directory has been entered, it will
be confirmed as follows:

Moving to install directory [/opt]

Once a target directory is specified, the following will appear:
Extracting files...
Installing Application Object Services (AOS) Version 3.00.Beta20
07/24/01
At this point files are uncompressed and are placed in the appropriate directories. If
any version of AOS is already installed on the target machine, the installAOS script
refuses to install the new version of the INI51 software, and exits. Reference the
Information Network Interface for Solaris and Windows Software User Guide,
B0400BM, for instructions on how to remove a previous version of the INI51 pack-
age.
9. Before rebooting into multi-user mode, the following should be completed:
a. Modify the FoxAPI software configuration file, foxapi.cfg, according to the
instructions in the Information Network Interface for Solaris and Windows Software
User Guide, B0400BM, if this machine will be a server to a different INI51
instance. This would occur in an INI51:Symmetric configuration. The FoxAPI
software changes can be implemented at any time by stopping the FoxAPI process
(aisstop), altering the file, and restarting the FoxAPI software (aisstart).
b. Modify the Operating System OM_NUM_OBJECTS according to the instructions
found in the Information Network Interface for Solaris and Windows Software User
Guide, B0400BM. The modification of OM_NUM_OBJECTS must be made before the
machine is rebooted.

31
B0400EC – Rev A 4. Installation - Solaris Stations

The Message Forwarding and Message Relay components of the INI51 package require remote
side software to be installed. The Data Transfer portion does not require any software to be
installed on the Isolation Station AW (remote station).
The software can be installed over the network connecting the Isolation Station Server AW (local
station) and the Isolation Station AW (remote station).

Message Forwarding
If the Message Forwarding component of the INI51 package is to be installed across the network,
type the following commands from the Isolation Station Server AW (local station) after
installing the Isolation Station Server AW (local station) software:
♦ At a VT100 or cmdtool prompt:
cd /opt
tar cvf msgfwd.tar aos/MsgFwd
compress msgfwd.tar
Then use ftp(1) to transfer the file msgfwd.tar.Z to the Isolation Station AW (remote station)
and place it in the /opt directory. Once the file has been transferred, telnet(1) to the Isolation
Station AW (remote station) and install the transferred file by typing the following commands:
♦ At a VT100 or cmdtool prompt:
cd /opt
uncompress msgfwd.tar.Z
tar xvf msgfwd.tar

Message Relay
If the Message Relay component of the INI51 package is to be installed across the network, then
type the following commands from the Isolation Station Server AW (local station) after install-
ing the Isolation Station Server AW (local station) software:
♦ At a VT100 or cmdtool prompt:
cd /opt
tar cvf MsgRelay.tar aos/MsgRelay
compress MsgRelay.tar
Then use ftp to transfer the file MsgRelay.tar.Z to the Isolation Station AW (remote station)
and place it in the /opt directory. Once the file has been transferred, telnet to the Isolation
Station AW (remote station) and install the transferred file by typing the following commands:
♦ At a VT100 or cmdtool prompt:
cd /opt
uncompress MsgRelay.tar.Z
tar xvf MsgRelay.tar
The changes made above take effect after the machine is rebooted or restarted into multi-user
mode.
♦ Type:
sync;sync;sync
reboot
Please reference the Information Network Interface for Solaris and Windows Software User Guide,
B0400BM, document for more details installation instructions.

32
4. Installation - Solaris Stations B0400EC – Rev A

Isolation Station AW Installation

This section describes the installation process for the Isolation Station AW (remote station) on a
50 Series station with a Solaris operating system.

NetFoxAPI Client Software

On the Isolation Station Server AW (local station), install the NetFoxAPI Client software
supplied as part of the INI51 deliverable.
1. Start a VT100 session on the INI51 host machine.
2. Change to the /opt directory.
cd /opt
3. Mount the INI51 CD-ROM:
mount -F hsfs -o ro /dev/sr0 /cdrom
4. Extract the files from the CD-ROM. This will create a directory holding the
NetFoxAPI deliverables (/opt/netFoxAPIClient).
tar xvf /cdrom/Solaris/FoxUtilDir/NetFoxAPI/netFoxAPI.tar
5. Place the libnetfox.a library in the /usr/lib directory.

Latest FoxAPI Quick Fix

Before installing the Quick Fix shipped with the INI51 software, contact the IPS Global Cus-
tomer Support Center to ensure that it is the latest available FoxAPI Quick Fix.

NOTE
The newest FoxAPI Quick Fix should always be used.

After confirming that the Quick Fix is the latest. Install it from the INI51 media or download
and install the later Quick Fix.
1. Start a VT100 session on the INI51 host machine.
2. Mount the INI51 CD-ROM:
mount -F hsfs -o ro /dev/sr0 /cdrom
3. Check the provided Quick Fix for your Operating System and ensure that it is the
latest Quick Fix available.
cd /cdrom/Solaris/FoxUtilDir/QuickFix/<OperatingSystem>
4. Use the file2dsk utility to create the Quick Fix floppy disks.
(The file2dsk utility can be located on the INI51 CD-ROM at
/cdrom/Solaris/FoxUtilDir/file2dsk_<OS>).
5. Follow the instructions provided in the QFxxxxxx.txt instructions.

33
B0400EC – Rev A 4. Installation - Solaris Stations

AOS Software
This section describes the installation of the AOS software on a 50 Series station with a
Solaris operating system that is to be the Isolation Station AW (remote station). Please reference
the Application Object Services User’s Guide, B0400BZ, document for more detailed installation
and configuration instructions.

NOTE
Initial installations should be performed while in single user mode because the
operating system is modified to allow larger numbers of Application Objects to be
created. If the installation is an update, the -override and -online options of
installAOS may be used.

In the examples that follow the chosen installation directory is /opt.

Installation requires the following steps.

1. Enter single user mode on the AP or AW to host the AOS package and do
the following:
a. On an AW51, select the Shutdown_AW menu pick under SftMnt in the
Proc_Eng_Env. Select Shutdown to confirm. When the password prompt appears,
enter the root password.
b. From the System Console directly connected to the AP51, type
shutdown -y -g0. When the password prompt appears, enter the root password.
2. Mount any partitions that have become unmounted.
a. Type cd / to move to the root directory.
b. Check to see what is currently mounted. Type df -F ufs -k
c. If the partition for software installation is not mounted, mount it now. For
example, if /opt is the location for the software installation and it is not mounted,
mount it by typing: mount /opt
3. Check free disk space in the /opt partition by typing df -k -F ufs. The AOS soft-
ware is normally loaded in the /opt partition. If the /opt partition is too small to hold
the 12 megabytes of software that comprise the AOS package, either mount another
hard drive or concatenate another hard drive to the /opt partition per the System
Administration for Solaris document. The installation script uses symbolic links from
the user specified installation directory to /opt if /opt is not the user specified instal-
lation directory.
4. Change to /opt and create the aos directory to load the install script regardless of
where the final destination is by typing:
cd /opt
mkdir aos
5. Insert the AOS for Solaris OS media in the CD-ROM drive attached to the target AP
or AW.
6. Mount the CD-ROM:
mount -F hsfs -o ro /dev/sr0 /cdrom

34
4. Installation - Solaris Stations B0400EC – Rev A

7. Change to the aos directory on the CD-ROM:

cd /cdrom/Solaris/SPS/aos
8. To begin the installation of the AOS software, simply type:
./installAOS or
./installAOS -online
./installAOS -override
./installAOS -online -override
The choice depends on whether or not the machine needs to be placed in single-user
mode. If the OM changes need to be made, use the first choice listed. If not, the
-online option is appropriate.

NOTE
* The -online option is typically used on upgrades since the OM settings typically
do not need to be changed during an upgrade.
* The -online option in this sense simply refers to the AW as a whole. It does not
mean that the AOS software can be running during an update.
* The -override option forces the new software installation over of a previous ver-
sion.

The following is displayed on the screen:

InstallAOS: Starting Now.

installAOS: Checking AOS Versions.
**** AOS no yet installed on this system. ***

Where is the AOS software to be installed? [/opt]?

At this point, the directory to hold the AOS software should be entered. The default is
taken by simply pressing the Enter key. Once the directory has been entered, it will be
confirmed as follows:

Moving to install directory [/opt]

Once a target directory is specified, the following will appear:
Extracting files...
Installing Application Object Services (AOS) Version 3.00.Beta20
07/24/01
At this point files are uncompressed and are placed in the appropriate directories. If
any version of the AOS software is already installed on the target machine, the
installAOS script refuses to install the new version of the AOS software, and exits.
Refer to the Application Object Services User’s Guide, B0400BZ, for instructions on
how to remove a previous version of the AOS package.
9. Before rebooting into multi-user mode, the following should be completed:
♦ Modify the Operating System OM_NUM_OBJECTS according to the instruction in the
Application Object Services User’s Guide, B0400BZ. The modification of
OM_NUM_OBJECTS must be made before the machine is rebooted.

35
B0400EC – Rev A 4. Installation - Solaris Stations

The changes made above take effect after the machine is rebooted or restarted into multi-user
mode.
♦ Type:
sync;sync;sync
reboot
Please reference the Application Object Services User’s Guide, B0400BZ, document for more details
installation instructions.

Controller Hosts Installation

This section deals with the software that should be installed on the CP hosts in the system hold-
ing the Isolation Station Server AW (local station).

Isolation Station Configurator

The Isolation Station Configurator is dependent upon the AOS and INI packages being installed
and configured properly. This software should be installed on the CP hosts in the system holding
the Isolation Station Server AW.
To start the Isolation Station Software installation process:
1. Insert the Isolation Station Configurator media into the CD-ROM drive of the AW.
mount -F hsfs -o ro /dev/sr0 /cdrom
2. Change to the Solaris directory on the CD-ROM:
cd /cdrom/Solaris/SPS/iss/scripts
3. Start the installation
InstallISS
4. When the installation is complete, unmount the CD-ROM.
cd /
umount /cdrom
5. Eject the CD-ROM.

36
5. Configuration-Windows Stations
This section describes how to configure the components of an Isolation Station System.
Figure 5-1 depicts the overview of an Isolation Station system.

Figure 5-1. Isolation Station System Overview

Isolation Station Server AW (Local Station)

The Isolation Station Server AW (local station) requires the AOS software, INI software and
Isolation Station Configurator to be installed and configured.
It 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 reinitialized tags will not be propagated to the Isolation Station AW until the tags
change on the Isolation Stations Server’s 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

37
B0400EC – Rev A 5. Configuration-Windows Stations

(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.

AOS Software
Configuring the AOS software on the Isolation Station Server AW includes the following
activities. Reference the Application Object Services User’s Guide, B0400BZ, for detailed AOS
configuration information.

TIP
The AOS software attempts to minimize the resources it uses. Any prefiltering, for
example, grouping applications (compounds) by the CP can, also, have a significant
impact of minimizing resources used.

♦ Installing the Informix software. (Windows stations only.)

♦ Resizing the I/A Series system limits.
♦ Setting the Correct OM_NUM_OBJECTS.
♦ Altering the Sizing Files
♦ Increasing the Shared Memory Limit
♦ Configuring the I/O Subsystem (FoxAPI software)
♦ Configuring AOS applications to start on reboot.

INI Software
Configuring the INI software on the Isolation Station Server AW includes the following activi-
ties. Reference the Information Network Interface for Solaris and Windows Software User Guide,
B0400BM, for detailed INI configuration information.
♦ Install the Informix software. (Windows stations only.)
♦ Resizing the I/A Series system limits.
♦ Setting the Correct OM_NUM_OBJECTS.
♦ Altering the Sizing Files
♦ Configuring the I/O Subsystem (NetFoxAPI and FoxAPI software)
♦ License the NetFoxAPI software.
♦ Configure FoxAPI Software on the Isolation Station Server AW (Local) and
Isolation Station AW (Remote).
♦ Set the required environment variables for the “C” shell.
♦ Edit for INI error logging.
♦ Configure INI applications to start on reboot.

38
5. Configuration-Windows Stations B0400EC – Rev A

Message Forwarding
If Message Forwarding is to be used in conjunction with the INI software then the following
must be configured.
♦ Define the service.
♦ Define the message destinations.
♦ Configure to start iaToQ on reboot.

Message Relay
If Message Relay is to be used in conjunction with the INI software then the following must be
configured.
♦ Define the service.
♦ Define the message destinations.
♦ Configure to start msgRelay on reboot.

Manual Startup
This section discusses how to setup and start a multiple application instance of the INI execut-
able. The names of the applications to be mapped are: APP_01, APP_02, and APP_03. The directory
/opt/foxind/INI70Apps is the project directory, see the Operation section of the Information
Network Interface for Solaris and Windows Software User Guide (B0400BM) for a suggested layout
for your projects.
With the files in their standard locations, the steps to use multimapping are:
1. Populate the Informix database with the definition of the objects using INIBUILDDB.
The directory path to the map file has to be specified with this command.
2. Create the objects using INICREATE. This command does not require knowledge of
the map files. It reads the Informix database.
3. Start mapping of multiple applications using INIMAP.
Here are the actual steps for three applications, APP_01, APP_02, and APP_03.
♦ At the Isolation Station Server AW type the following from a NutCracker shell
window:
cd D:/opt/foxind/INI70Apps
INIBUILDDB APP_01/data APP_01 /opt/aos/wf/APP01.map
INIBUILDDB APP_02/data APP_02 /opt/aos/wf/APP02.map
INIBUILDDB APP_03/data APP_03 /opt/aos/wf/APP3.map
INICREATE APP_01
INICREATE APP_02
INICREATE APP_03
INIMAP APP_01 APP_02 APP_03 -SR 5 -L APP_01/logs
The logs will be placed in the D:/opt/foxind/INI70Apps/APP_01/logs directory.
♦ If the environment is setup properly the INI executable may be used directly:
cd D:/opt/foxind/INI70Apps
INI70 builddb APP_01 APP_01/data/APP_01.map
INI70 builddb APP_02 APP_01/data/APP_02.map
INI70 builddb APP_03 APP_01/data/APP_03.map
INI70 create APP_01

39
B0400EC – Rev A 5. Configuration-Windows Stations

INI70 create APP_02

INI70 create APP_03
INI70 mmap APP_01 APP_02 APP_03 - SR 5 >APP_01/logs/ini.oout 2>APP_01/logs/ini.err

TIP
Once the applications have been built using either INIBUILDDB or INI70 builddb,
they do not need to be rebuilt unless the mix of objects and attributes needs to be
changed.

Once the objects have been created using INICREATE or INI70 create, they do not
need to be recreated unless they have been deleted or the station has been rebooted.

Automatic Startup
At reboot, there are two operations that must occur for each application assuming that the
application definitions have been stored previously in the Informix database using INIBUILDDB or
INI70 build:
♦ Creation of the Application Objects and
♦ Startup of the mapping service.
The following steps must be performed to automatically start on reboot.
1. Create a d:/opt/aos/script/go_INI70.ksh script in the d:/usr/fox/bin directory.
2. Edit the go_INI70.ksh script with a line similar to the one that follows.
/opt/aos/scripts/go_INI51 /opt/INI70Apps ‘/opt/aos/scripts/lsApp INI’
This invocation tells the script to create and start all INI based applications and it tells
the script that the log directory is d:/opt/INI70Apps/<appName>/logs.
A typical line to start a single application would be:
/opt/aos/scripts/go_INI51 /opt/INI70Apps APP_01
where APP_01 is the name of the application to start.
3. Add the following line to the end of the d:/usr/fox/bin/usr_apps.dat file:
INI70

Isolation Station AW (Remote Station)

The Isolation Station AW requires the AOS software installed and configured.

AOS Software
Configuring the AOS software on the Isolation Station AW includes the following activities.
Reference the Application Object Services User’s Guide, B0400BZ, for detailed AOS configuration
information.
♦ Install the Informix software. (Windows stations only.)
♦ Resizing the I/A Series system limits.
♦ Setting the Correct OM_NUM_OBJECTS.
♦ Altering the Sizing Files

40
5. Configuration-Windows Stations B0400EC – Rev A

♦Increasing the Shared Memory Limit

♦ Configuring the I/O Subsystem (FoxAPI software)
♦ Configuring AOS applications to start on reboot.

Message Forwarding
Message Forwarding is part of the INI product. Reference the Information Network Interface for
Solaris and Windows Software User Guide, B0400BM, for detailed Message Forwarding configura-
tion information.
♦ If Message Forwarding is to be used the following has to be configured:
♦ Update the FileOfNames file.
♦ Modify the alarm destination via ICC.
♦ Define the services.
♦ Configure to netToIA to start on reboot.

Message Relay
Message Relay is part of the INI product. Reference the Information Network Interface for Solaris
and Windows Software User Guide, B0400BM, for detailed Message Relay configuration informa-
tion.
♦ If Message Relay is to be used the following has to be configured:
♦ Update the FileOfNames file.
♦ Define the service.
♦ Configure to start msgRelay on reboot.

Isolation Station Configurator

The Isolation Station Configurator provides a graphical user-interface (GUI) that consolidates all
the activities required to generate the map files used by the INI software. These map files are the
keys to replicate data for consumption by the outside world. This utility eliminates the manual
steps formerly used to generate map files. This utility assumes that the AOS and INI software
have been installed since the utility makes use of the existing scripts and executables installed with
the AOS and INI packages.

Windows Stations
Select Start, then Programs, Isolation Station SW, and then BuildIniIssmaps, Figure 5-2, to
start the Isolation Station Configurator. The Isolation Station Configurator can, also, be invoked
by running the D:\opt\iss\exe\BuildIniIssmaps command.

41
B0400EC – Rev A 5. Configuration-Windows Stations

Figure 5-2. Staring the Isolation Station Configurator (Windows Stations)

The initial Isolation Station Configurator window then appears, Figure 5-3.

Figure 5-3. INI and IS Map File Builder (Windows Stations)

The Isolation Station Configurator fields and buttons are defined below.

42
5. Configuration-Windows Stations B0400EC – Rev A

Button/Field Description
Local Station Name This field displays the local station name.
Select Control Station Select the control station name to be used for building the map
in <LBUG> file.
mapDef Name Identify the map definition file to be used to build the map
files. The default location is d:/opt/iss/data/mapDefIss.
Build Map Files (Button) This button starts the map file building process.
Reset (Button) This button resets all fields and entries on the screen.
IS Server Map Files This list box displays all the generated IS Server map files.
IS Map Files This list box displays all the generated IS Map files.
View Server Map File This button will display the selected Server map file.
(Button)
View Station Map File This button will display the selected Station map file.
(Button)
Exit (Button) Exits the Isolation Station Configurator.

Use Local Station

To invoke map building for the location station:
1. Identify the Control Station to be used for map file generation and then select the
pathname to the map definition file, mapDef Name.
2. Select the Build Map Files button to start the map file building process. The
progress is shown in the text box, see Figure 5-4.

Figure 5-4. INI and IS Map File Builder - Local Station (Windows Station)

43
B0400EC – Rev A 5. Configuration-Windows Stations

Generated map files can be viewed by double-clicking on a map file or by highlighting a map file
and selecting the corresponding view button, see Figure 5-5.

Figure 5-5. INI and IS Map File Builder - Map File View (Windows Stations)

Intermediate Compound Names

Intermediate compound names in the Isolation Station Server map file are formed by prefixing
the application name with an underscore, “_”. If the application name has the maximum length
of 12 characters, then the first character is replaced with an underscore, “_”. The configurator tool
then checks if there is an existing name in the CSA that matches this intermediate application
name. If so, a new intermediate name is attempted by restoring the first character and replacing
the second character of the name with an underscore. This process continues until a unique name
is found.
The following example shows an application name that is not the maximum length of 12 charac-
ters, e.g. EXAMPL_27A: (10 characters). In this example, the first two attempts just prefix the
name with an underscore and from the third attempt on one characters is replaced until the last
character is reached. Table 5-1 is an example of application naming:

Table 5-1. Application Naming

Attempts Application Name Comment

1 _EXAMPL_27A 11 characters
2 __EXAMPL_27A 12 characters, maximum length reached
3 ___XAMPL_27A Starts to replace on catchers at a time with an
underscore.
4 __E_MPL_27A
5 __EX_MPL_27A

44
5. Configuration-Windows Stations B0400EC – Rev A

Table 5-1. Application Naming

Attempts Application Name Comment

6 __EXA_PL_27A
7 __EXAM_L_27A
8 __EXAMP__27A
9 __EXAMPL_27A
10 __EXAMPL__7A
11 __EXAMPL_2_A
12 __EXAMPL_27_

When the character replacement reaches the last character and an application still exists for the
name attempted, the map file creation is aborted for that application. Figure 5-6 shows such an
incident:

Figure 5-6. Intermediate Compound Naming (Windows Stations)

45
B0400EC – Rev A 5. Configuration-Windows Stations

46
6. Configuration - Solaris Stations
This section describes how to configure the components of an Isolation Station System.
Figure 6-1 depicts the overview of an Isolation Station system.

Figure 6-1. Isolation Station System Overview

Isolation Station Server AW (Local Station)

The Isolation Station Server AW (local station) requires the AOS software, INI software and
Isolation Station Configurator to be installed and configured.
It 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 reinitialized tags will not be propagated to the Isolation Station AW until the tags
change on the Isolation Stations Server’s 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

47
B0400EC – Rev A 6. Configuration - Solaris Stations

(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.

AOS Software
Configuring the AOS software on the Isolation Station Server AW includes the following
activities. Reference the Application Object Services User’s Guide, B0400BZ, for detailed AOS
configuration information.

TIP
The AOS software attempts to minimize the resources it uses. Any prefiltering, for
example, grouping applications (compounds) by the CP can, also, have a significant
impact of minimizing resources used.

♦ Installing the Informix software. (Windows stations only.)

♦ Resizing the I/A Series system limits.
♦ Setting the Correct OM_NUM_OBJECTS.
♦ Altering the Sizing Files
♦ Increasing the Shared Memory Limit
♦ Configuring the I/O Subsystem (FoxAPI software)
♦ Configuring AOS applications to start on reboot.

INI Software
Configuring the INI software on the Isolation Station Server AW includes the following activi-
ties. Reference the Information Network Interface for Solaris and Windows Software User Guide,
B0400BM, for detailed INI configuration information.
♦ Install the Informix software. (Windows stations only.)
♦ Resizing the I/A Series system limits.
♦ Setting the Correct OM_NUM_OBJECTS.
♦ Altering the Sizing Files
♦ Configuring the I/O Subsystem (NetFoxAPI and FoxAPI software)
♦ License the NetFoxAPI software.
♦ Configure FoxAPI Software on the Isolation Station Server AW (Local) and Isola-
tion Station AW (Remote).
♦ Set the required environment variables for the “C” shell.
♦ Edit for INI error logging.
♦ Configure INI applications to start on reboot.

48
6. Configuration - Solaris Stations B0400EC – Rev A

Message Forwarding
If Message Forwarding is to be used in conjunction with the INI software then the following
must be configured. Reference the Information Network Interface for Solaris and Windows Software
User Guide (B0400BM) for details instructions.
♦ Define the service.
♦ Define the message destinations.
♦ Configure to start iaToQ on reboot by modifying the /etc/fox/user_apps file.

Message Relay
If Message Relay is to be used in conjunction with the INI software then the following must be
configured. Reference the Information Network Interface for Solaris and Windows Software User
Guide (B0400BM) for details instructions.
♦ Define the service.
♦ Define the message destinations.
♦ Configure to start msgRelay on reboot by modifying the /etc/fox/user_apps file.

Manual Startup
This section discusses how to setup and start a multiple application instance of the INI
executable. The names of the applications to be mapped are: APP_01, APP_02, and APP_03. The
directory /opt/foxind/INI51Apps is the project directory, see the Operation section of the
Information Network Interface for Solaris and Windows Software User Guide (B0400BM) for a
suggested layout for your projects.
With the files in their standard locations, the steps to use multimapping are:
1. Populate the Informix database with the definition of the objects using INIBUILDDB.
The directory path to the map file has to be specified with this command.
2. Create the objects using INICREATE. This command does not require knowledge of
the map files. It reads the Informix database.
3. Start mapping of multiple applications using INIMAP.
Here are the actual steps for three applications, APP_01, APP_02, and APP_03.
♦ At the Isolation Station AW create the directory structure required for the
applications. For example:
cd /opt/foxind/
mkdir -p /INI51Apps/APP_01/data
mkdir -p /INI51Apps/APP_01/logs
mkdir -p /INI51Apps/APP_02/data
mkdir -p /INI51Apps/APP_02/logs
mkdir -p /INI51Apps/APP_03/data
mkdir -p /INI51Apps/APP_03/logs

49
B0400EC – Rev A 6. Configuration - Solaris Stations

♦ At the Isolation Station Server AW type the following from a command window:
cd /opt/foxind/INI51Apps
INIBUILDDB APP_01/data APP_01 /opt/aos/wf/APP01.map
INIBUILDDB APP_02/data APP_02 /opt/aos/wf/APP02.map
INIBUILDDB APP_03/data APP_03 /opt/aos/wf/APP3.map
INICREATE APP_01
INICREATE APP_02
INICREATE APP_03
INIMAP APP_01 APP_02 APP_03 -SR 5 -L APP_01/logs
The logs will be placed in the /opt/foxind/INI51Apps/APP_01/logs directory.
♦ If the environment is setup properly, and the Bourne shell (sh(1)) is in use, the INI
executable may be used directly:
cd /opt/foxind/INI51Apps
INI51 builddb APP_01 APP_01/data/APP_01.map
INI51 builddb APP_02 APP_01/data/APP_02.map
INI51 builddb APP_03 APP_01/data/APP_03.map
INI51 create APP_01
INI51 create APP_02
INI51 create APP_03
INI51 mmap APP_01 APP_02 APP_03 - SR 5 >APP_01/logs/ini.oout 2>APP_01/logs/ini.err

TIP
Once the applications have been built using either INIBUILDDB or INI51 builddb,
they do not need to be rebuilt unless the mix of objects and attributes needs to be
changed.

Once the objects have been created using INICREATE or INI51 create, they do not
need to be recreated unless they have been deleted or the station has been rebooted.

Automatic Startup
At reboot, there are two operations that must occur for each application assuming that the
application definitions have been stored previously in the Informix database using INIBUILDDB or
INI51 builddb:
♦ Creation of the Application Objects and
♦ Startup of the mapping service.
To make automatic startup simpler, the script, go_INI51, is provided. A line is then placed in the
/etc/fox/user_apps file to start the INI applications at reboot. A typical line would be:
/opt/aos/scripts/go_INI51 /opt/INI51Apps “/opt/aos/scripts/lsApp INI”
This invocation tells the script to create and start all INI based applications and it tells the script
that the log directory is /opt/INI51Apps/<appName>/logs.
A typical line to start a single application would be:
/opt/aos/scripts/go_INI51 /opt/INI51Apps APP_01
where APP_01 is the name of the application to start.

50
6. Configuration - Solaris Stations B0400EC – Rev A

Isolation Station AW (Remote Station)

The Isolation Station AW requires the AOS software installed and configured.

AOS Software
Configuring the AOS software on the Isolation Station AW includes the following activities.
Reference the Application Object Services User’s Guide, B0400BZ, for detailed AOS configuration
information.
♦ Install the Informix software. (Windows stations only.)
♦ Resizing the I/A Series system limits.
♦ Setting the Correct OM_NUM_OBJECTS.
♦ Altering the Sizing Files
♦ Increasing the Shared Memory Limit
♦ Configuring the I/O Subsystem (FoxAPI software)
♦ Configuring AOS applications to start on reboot.

Message Forwarding
Message Forwarding is part of the INI product. Reference the Information Network Interface for
Solaris and Windows Software User Guide, B0400BM, for detailed Message Forwarding
configuration information.
♦ If Message Forwarding is to be used the following has to be configured:
♦ Update the FileOfNames file.
♦ Modify the alarm destination via ICC.
♦ Define the services.
♦ Configure to netToIA to start on reboot.

Message Relay
Message Relay is part of the INI product. Reference the Information Network Interface for Solaris
and Windows Software User Guide, B0400BM, for detailed Message Relay configuration informa-
tion.
♦ If Message Relay is to be used the following has to be configured:
♦ Update the FileOfNames file.
♦ Define the service.
♦ Configure to start msgRelay on reboot.

Isolation Station Configurator

The Isolation Station Configurator provides a graphical user-interface (GUI) that consolidates all
the activities required to generate the map files used by the INI software. These map files are the
keys to replicate data for consumption by the outside world. This utility eliminates the manual
steps formerly used to generate map files. This utility assumes that the AOS and INI software
have been installed since the utility makes use of the existing scripts and executables installed with
the AOS and INI packages.

51
B0400EC – Rev A 6. Configuration - Solaris Stations

Solaris Stations
Select Config, IsolationStation and then BuildIniIssmaps, Figure 6-2 to start the Isolation
Station Configurator. The Isolation Station Configurator can, also, be invoked by running the
/opt/aos/exe/BuildIniIssmaps command.

Figure 6-2. Starting the Isolation Station Configurator (Solaris Stations)

Figure 6-3 is a picture of the initial Isolation Station Configurator for Solaris stations.

Figure 6-3. INI and IS Map File Builder (Solaris Stations)

52
6. Configuration - Solaris Stations B0400EC – Rev A

The Isolation Station Configurator, for Solaris stations, fields and buttons are defined below.

Button/Field Description
Local Station Name This field displays the local station name.
Select Control Station Select the control station name to be used for building the map
in <LBUG> file.
mapDef Name Identify the map definition file to be used to build the map
files. The default location is /opt/iss/data/mapDefIss.
Build Map Files (Button) This button starts the map file building process.
Reset (Button) This button resets all fields and entries on the screen.
IS Server Map Files This list box displays all the generated IS Server map files.
IS Map Files This list box displays all the generated IS Map files.
View Server Map File This button will display the selected Server map file.
(Button)
View Station Map File This button will display the selected Station map file.
(Button)
Exit (Button) Exits the Isolation Station Configurator.

Use Local Station

To invoke map building for the location station:
1. Check the Use Local Station check box.
2. Identify the pathname to the map definition file, mapDef Name.
3. Select the Build Map Files button to start the map file building process. The
progress is shown in the text box, see Figure 6-4.

Figure 6-4. INI and IS Map File Builder - Local Station (Solaris Stations)

53
B0400EC – Rev A 6. Configuration - Solaris Stations

Generated map files can be viewed by highlighting a map file and selecting the corresponding
view button, see Figure 6-5.

Figure 6-5. INI and IS Map File Builder - Map File View (Solaris Stations)

Intermediate Compound Names

Intermediate compound names in the Isolation Station Server map file are formed by prefixing
the application name with an underscore, “_”. If the application name has the maximum length
of 12 characters, then the first character is replaced with an underscore, “_”. The configurator tool
then checks if there is an existing name in the CSA that matches this intermediate application
name. If so, a new intermediate name is attempted by restoring the first character and replacing
the second character of the name with an underscore. This process continues until a unique name
is found.
The following example shows an application name that is not the maximum length of 12 charac-
ters, e.g. EXAMPL_27A: (10 characters). In this example, the first two attempts just prefix the
name with an underscore and from the third attempt on one characters is replaced until the last
character is reached. Table 6-1 is an example of application naming:

Table 6-1. Application Naming

Attempts Application Name Comment

1 _EXAMPL_27A 11 characters
2 __EXAMPL_27A 12 characters, maximum length reached
3 ___XAMPL_27A Starts to replace on catchers at a time with an
underscore.
4 __E_MPL_27A

54
6. Configuration - Solaris Stations B0400EC – Rev A

Table 6-1. Application Naming

Attempts Application Name Comment

5 __EX_MPL_27A
6 __EXA_PL_27A
7 __EXAM_L_27A
8 __EXAMP__27A
9 __EXAMPL_27A
10 __EXAMPL__7A
11 __EXAMPL_2_A
12 __EXAMPL_27_

When the character replacement reaches the last character and an application still exists for the
name attempted, the map file creation is aborted for that application. Figure 6-6 shows such an
incident:

Figure 6-6. Intermediate Compound Naming (Solaris Stations)

55
B0400EC – Rev A 6. Configuration - Solaris Stations

56
7. Operation
This section discusses the operation of the Isolation Station software packages.

Application Object Services (AOS)

The AOS software consists of the following items:
1. An executable, named aos, which implements the critical Application Object Services:
a. Creating and filling an Informix database with the information defining an Appli-
cation.
b. Creating the Application
c. Transferring (mapping) the data between an Application Object Attribute and it
source or sink OM variables.
d. Deleting the Application
2. A configuration utility, named AppObjSrv, that allows the user to establish and
maintain an Application Object database via a VT100 screen interface.
3. Individual scripts that allow the user the same functionality as that contained in
AppObjSrv, but which do not require the VT100 screen interface.
4. A set of Application Object commands which allow creation, deletion, and
manipulation of individual Application Objects.
5. A script, MkMapFile, to facilitate the creation of the map file used by AppObjSrv
and/or the individual scripts mentioned in 3) above.
6. An executable, named aoAlm, which provides Application Object alarming capability.
This program is an optional service since not all Applications require process
alarming. It supports all I/A Series Alarm Types.
7. A selection of standard object templates used in the implementation of Application
Object alarming.
Figure 7-1 shows the overall functionality provided by the AOS package:

57
B0400EC – Rev A 7. Operation

USER Responsibility AOS Software Functionality Global Process Database

Alarm
aoAlm aos map
Devices

Memory

aod file User

map file aos buildDB database aos create
Manipulation
Template

Figure 7-1. AOS Software Data Flow

The information supplied by the user of Application Object Services is a map file. The map file
defines all of the objects belonging to an Application, their attributes, data types, default values,
and change deltas. It may also include the types of alarms that the AOS software alarming process
should scan for and detect, as well as the resulting alarm message text to be displayed, and the I/A
alarm destinations. This file is read in by the AOS software and stored in an Informix database.

Typical Uses
There are at least two typical uses of Application Objects:
1. Providing an interface to the I/A Series Alarm Management sub-system to a user
written application program,
2. Providing an external (OM Based) representation of the internal data structures used
by a user written application program, and
Collecting data values in disparate systems or blocks into a single I/A Series Object such that these
values can be accessed using a systematic naming convention.

58
7. Operation B0400EC – Rev A

Information Network Interface (INI)

The INI software provides local representation of remote data by creating local application
objects with the same name as the remote points that they represent. The data is transferred from
the Remote Station to the Local Station through the use of the networked version of the FoxAPI
software. The Figure 7-2 shows an asymmetric configuration performing data transfer.

Local NetFoxAPI Put Connection Remote

Customer Supplied TCP/IP

Network
Isolation Station Server AW
NetFoxAPI Server Isolation Station AW
FoxAPI
Local System
Remote System

OM Connection
Control Station
containing
TOWER:FT101.PNT

Figure 7-2. Data Flow from Remote Station to Local Station in a Peer-to-Peer Application

Message Forwarding
The INI software provides forwarding of the following message types:
♦ Control Station Messages
♦ Process Alarms
♦ Sequence Block Messages generated using SENDMSG and SENDCONF
♦ Sequence of Events Messages generated by the EVENT block
♦ System Monitor Messages
♦ Operator Action Journal Messages
♦ Generic messages generated by any user of I/A Series connectionless IPC messages.
The Message Forwarding component of the INI package application is an extension of the
I/A Series Message Handling system. The Message Forwarding component of the INI package
application allows messages to be passed to the Alarm Annunciators, printers, and/or historians
on a remote I/A Series node over a TCP/IP communications link.
Message Forwarding functionality is detailed in Figure 7-3 and accompanying text.

59
B0400EC – Rev A 7. Operation

Target_a (Printer) Target_y (hist01) Target_x (WP)

Isolation Station Server AW
(Local Station)
Machine: AW2001 Machine: AW200n Machine: AW200n
Letterbug: xx10yy

netToIA
List of Target Globally
known Logical Names
for each name handled
by ia2q.
qToNet

Machine: IN2001

Shared
Memory

iaToq
Alarm Devices:
APRINT
WP0001
Machine: CP1001 ...
WPxxxx
Sequence Block Alarm Contacts: Isolation Station AW
SendMsg CBP1 (Remote Station)
Machine: CP1002 ... Letterbug: xx20yy
CBPx
Programs:
WP hist01
DM/FV OAJ ...
Machine: WP1002 FoxAMI

Machine: IN1001

Figure 7-3. Message Forwarding Functionality

The process iaToQ can be configured to run on the Isolation Station AW (remote station) and
collects the messages that are to be sent to the Isolation Station Server AW (local station).
The process qToNet can be configured to run on the Isolation Station AW (remote station),
establishes a TCP/IP connection, and sends the collected messages to the Isolation Station Server
AW (local station).
The process netToIA runs on the Local Station, receives the messages sent across the TCP/IP
connection from Remote Station, delivers them to their final destination. The final destination
for the messages could be a printer, historian, or Alarm Alert task in an AW/WP.
It is important to note that even though Alarm Messages can be sent from a Remote Station to a
Local Station, the messages still must be acknowledged on the Remote Station where the messages
originated.
If the INI’s software data transfer package is used to implement a P mapping of the remote block's
UNACK parameter, the alarms can be acknowledged locally. Otherwise, please review the methods
to accomplish remote alarm acknowledgment discussed later in this document.

60
7. Operation B0400EC – Rev A

Message Relay
The INI package can be used as a transparent communications link between programs running
on the two systems if the programs use connectionless IPC messages.
The package can:
♦ Act as a proxy for programs with well-known names, i.e., those registered with the
OM.
♦ Act as a proxy for programs with locally known names communicating to those with a
globally known name assuming that the locally known program initiates the
communication.
♦ Relay a broadcast message from one system to the next.

Message Relay and Well-Known Names

A common form of Message Relay involves the transfer of information between two programs
whose IPC names are registered with the Object Manager. OM registration of an IPC name
allows clients that wish to communicate with the application to find it without knowing the name
of the station hosting the application.
For example, the AIM*Historian software uses this facility to receive Process Alarm messages
from Control Stations. Each AIM*Historian instance has a globally known name that may be
used by Control Stations as an alarm destination.
The INI software fully supports this style of operation. Each msgRelay instance can act as a proxy
for up to 20 remote applications.

Message Relay and Locally Known Names

If the application has a locally known name, there are only two ways for a client to communicate
with it: by knowing its station name (or PSAP address) or by using broadcast messages. The next
section discusses broadcast messages. This one is focussed on those applications that use station
names (or PSAP addresses) to find the application.
The INI’s Message Relay facility can handle programs with locally known names if the locally
known program initiates communication. When communication occurs, the Message Relay
facility remembers the name and address of the program that sent it a message. This information
can be used to return a reply. The locally named program may be on either the Local Station or
the Remote Station.

Message Relay and Broadcast Messages

Broadcast message support is required by applications that need to address programs in multiple
stations in parallel. In the I/A Series network, broadcast messages are used to query all Object
Managers about a list of tags and to extract compound lists from Control Stations in support of
the Select display.
Most broadcast messages will not be relayed through the INI software. However, some custom
applications need this service.
A typical use is the IRIS reporting package, a portion of the RBatch II software offering. IRIS
servers may exist on each AP or AW in the system and IRIS clients need to know which servers are
available in the system. The IRIS clients gather this knowledge using broadcast messages. The use
of broadcast messages greatly simplifies the configuration of the IRIS package.

61
B0400EC – Rev A 7. Operation

Figure 7-4 and the discussion that follows, illustrate the use of broadcast Message Relay.

Isolation Station Server AW iris_srv (b’cast name) iris_srv (b’cast name)

(Local Station) IRDBS_AW1001 (local name) IRDBS_AW100n (local name)
Letterbugs: xx10yy
Machine: AW1001 Machine: AW100n

msg Relay
Point-to-Point Proxies:
IROPD_DM1001
...

qToNet IROPD_DM100n

Broadcast Proxies:
None
Machine: IN2001

Shared
Memory

Shared
Memory
msgRelay
Broadcast Proxies:
IRIS overlay iris_srv
IROPD_DM1001
Point-to-Point Proxies:
DM: DM1001 IRDBS_AW1001 qToNet
Machine: AW1001 ...

IRDBS_AW100n Isolation Station AW

(Remote Station)
Machine: IN1001 Letterbugs: xx20yy

Figure 7-4. Message Relay of Broadcast Messages

The preceding figure provides an overview of the Message Relay process. In this case, the program
msgRelay on the Local Machine (IN1001) is acting as a proxy for a program that requires broad-
cast Message Relay. The program in this case is a portion of the IRIS component of the Off-sites
Automation Suite.
In this example, the IRIS overlay sends a broadcast message to all programs named iris_srv on
all APs and AWs.
Since the msgRelay component of the INI’s Message Relay functionality is acting a broadcast
proxy for this name, it receives the message and stores it in the outgoing queue. The qToNet
component takes messages from this queue and forwards them over the CSN to another copy of
the msgRelay component.
This component, based on information in the message header, places the message on the
Nodebus using an I/A Series IPC broadcast message.
The IRIS servers each get the broadcast message and reply to the sending program. They know
the local name of the sending program and its address on the network from the information
included in the broadcast message.

62
7. Operation B0400EC – Rev A

The msgRelay component on the Local Station acts as the proxy for all possible clients on the
Remote Station and as their proxy receives the message from the IRIS server and puts it in the
outgoing queue. The qToNet component takes messages from this queue and forwards them over
the CSN to the remote msgRelay component.
The remote msgRelay component sends the message directly to the IRIS overlay.

Securely Moving Data from the DMZ to a CP

Moving data from the “outside” into a CP can be securely accomplished as follows:
1. On the outer AW set the tag to be a C in the map file for AOS.
2. If the data flow is one way - outside in - do this:
a. In the INI map file set the point up as a R mapping. This will cause the INI appli-
cation to read the value from outside the fire wall and store it in a shadow AOA
on the inner AW.
b. In the inner AW's AOS map file set the mapping as W or I. This is a better
solution but not all parameters can be configured with an AOA name as a source.
3. If the data flow is bidirectional, do this:
a. In the INI map file set the mapping to P.
b. In the inner AW's AOS map file, set the mapping to P.
c. The P mapping implements a read back so that the data flow will be bi-direc-
tional.

Isolation Station Configurator

Once the Isolation Station Configurator has generated the required map files:
1. Place the Isolation Station Server AW (local station) map file (e.g.
DMCPLUS10A_IsServer.map) in a directory (i.e. issmapdir) of the Isolation Station
Server AW (local station).
2. Place the map file (e.g. DMCPLUS10A_Is.map) in a directory (i.e. ismapdir) of the
Isolation Station AW (remote station).
3. Execute the following lines to create the AOAs in the Isolation Station Server AW
(local station). Ensure the an_init.cfg file exists in the directory specified in Step 1 and
verify the host specified in the an_init.cfg file is the Isolation Station AW (remote
station). (Note: The application name starts with an underscore (_).)
For 70 Series:
d:/opt/aos/exe/INI70.exe builddb issmapdir _DMCPLUS10A DMCPLUS10A_IsServer.map
d:/opt/aos/exe/INI70.exe create _DMCPLUS10A
For 50_Series:
d:/opt/aos/exe/INI51 builddb issmapdir _DMCPLUS10A DMCPLUS10A_IsServer.map
d:/opt/aos/exe/INI51 create _DMCPLUS10A
4. Execute the following lines to build the duplicate application in the Isolation Station
AW (remote station).
For 70 Series
d:/opt/aos/exe/aos.exe builddb ismapdir DMCPLUS10A_Is.map
d:/opt/aos/exe/aos.exe create DMCPLUS10A

63
B0400EC – Rev A 7. Operation

For 50 Series
/opt/aos/exe/aos builddb ismapdir DMCPLUS10A_Is.map
/opt/aos/exe/aos create DMCPLUS10A
5. Start the mapping on the Isolation Station Server AW (local station):
For 70 Series
d:/opt/aos/exe/aos.exe map _DMCPLUS10A
d:/opt/aos/exe/INI70.exe map _DMCPLUS10A
For 50 Series
/opt/aos/exe/aos map _DMCPLUS10A
/opt/aos/exe/INI51 map _DMCPLUS10A

64
8. Maintenance - Windows Stations
This section deals with the maintenance and troubleshooting of the Isolation Station
configuration on Windows stations.

Isolation Station Configuration Utility

Data Backup
The map files are generated in the directory d:/opt/iss/tmp/<AWname> where AWname is the name
of the host station. The user should archive the map files into another directory for safe-keeping
because at the beginning of each generation of the map files, the directory d:/opt/iss/tmp is
emptied of its contents.

Package Removal
The following steps should be taken when removing the Isolation Station Configuration Utility
software.
1. Uninstall the Isolation Station Software using Add or Remove Programs and
selecting the Isolation for Windows - SPS, HPS, MKS8 entry.
2. If needed save the d:/opt/iss/data and d:/opt/iss/tmp directories to another
location to preserve the current map files.
3. Remove the d:/opt/iss directory.

Upgrades
Before upgrading the Isolation Station Configuration Utility software preserve the current map
files prior to upgrading. After the upgrade the d:/opt/iss/data and d:/opt/iss/tmp directories
can be restored.

I/A Series Software Upgrades

Day 0 and Day 1
Preserve the current map files and remove the Isolation Station Configuration Utility Software
prior to upgrading. After the upgrade the d:/opt/iss/data and d:/opt/iss/tmp directories can
be restored.

Quick Fixes
Preserve the current map files and remove the Isolation Station Configuration Utility Software
prior to upgrading. After the upgrade the d:/opt/iss/data and d:/opt/iss/tmp directories can
be restored.

65
B0400EC – Rev A 8. Maintenance - Windows Stations

INI70 Software
The following maintenance information is for the INI70 package.

Package Removal
Take the following steps to remove the INI70 package.
1. Stop all mapping applications on the Isolation Station AW (remote station) by using
INIUNMAP. Create a script as follows to generate a list of those processes to stop with
INIUNMAP.
#!/bin/sh
cd /opt/aos/status
FILES=`ls INI51_map_* | grep -v '_monitor'`
for file in $FILES
do
/opt/aos/exe/testStatusLock $file | grep Locked >/dev/null 2>&1
status=$?
if [ $status = 0 ]
then
echo $file | awk -F_ '{ print $3 }'
fi
done
2. Use the script d:/opt/aos/MsgFwd/scripts/stop_MsgFwd on both the Isolation
Station Server AW (local station) and Isolation Station AW (remote station) to stop
message forwarding:
cd d:/opt/aos/MsgFwd/scripts ./stop_MsgFwd
3. Use the script d:/opt/aos/MsgFwd/scripts/stop_MsgRelay on either the Isolation
Station Server AW (local station) or the Isolation Station AW (remote station) to stop
message forwarding:
cd d:/opt/aos/MsgRelay/scripts ./stop_MsgRelay
4. From Windows select Start, then Settings, and then select the Control Panel.
a. Select Add or Remove Programs.
b. Select either the INI70 with Message Services or the INI70 without Message
Services item.
c. Select the Remove button.
5. Remove the startup commands (go_INI) from the file
d:/usr/fox/bin/fox_apps.dat file machines.
6. Remove the /opt/aos directory from both machines.

I/A Series Software Upgrades

Day 0 Upgrades
In the case of a Day 0 upgrade, preserve the INI70 configuration. The INI70 package should
then be reinstalled from the original or replacement media. Frequently, the most recent version of
the INI70 is available upon request so please investigate obtaining the latest materials by contact-
ing your Foxboro Field Service or Account Representative.

66
8. Maintenance - Windows Stations B0400EC – Rev A

Non-Day 0 Upgrades
Other than the file d:/usr/fox/bin/fox_apps.dat file, the INI70 software should not be
impacted by a non-Day 0 upgrade. However, it would be wise to backup the d:/opt/aos
directory and the information in the Informix database.

INI Package Upgrades

In all cases, consult the specific upgrade instructions that come with the upgrade materials. The
following information is generic.
The INI70 software can be upgraded without rebooting the hosting AW. However, the INI70
package must be shutdown first.
The steps in an upgrade are:
1. Backup configuration data.
2. Stop the package.
3. Load the new files.
4. Install the new files.
5. Restore the configuration data.
6. Restart the package.

Saving Configuration Data

1. Preserve the system file c:/windows/system32/drivers/etc/services (Windows
XP OS) or c:/winnt/system32/drivers/etc/services (Windows NT® OS).
2. Preserve the startup file d:/usr/fox/bin/fox_apps.dat.
3. Preserve the startup file d:/usr/fox/bin/go_INI.ksh.
4. The configuration file used by the Message Forwarding component of the INI70
package that may be replaced during an upgrade is:
♦ /opt/aos/MsgFwd/data/FileOfNames (The configuration file for the Message
Forwarding service.)
5. The configuration files used by the Message Relay component of the INI70 package
that may be replaced during an upgrade is:
♦ d:/opt/aos/MsgFwd/data/FileOfProxies
♦ d:/opt/aos/MsgFwd/data/FileOfTargets
An Informix database stores the configuration information related to the Data Transfer portion
of the INI70 package. The information in this database can be converted back into map files by
the use of the INIREPORT script. Most upgrades will not require this step, but any upgrade that
alters the aos database will.

67
B0400EC – Rev A 8. Maintenance - Windows Stations

Stopping the INI Package

To halt the INI70 software, use the INIUNMAP command to unmap the INI70 instances currently
running.
1. Use the following example to create a script to see a list of the current INI70 instances.
#!/bin/sh
cd /opt/aos/status
FILES=`ls INI51_map_* | grep -v '_monitor'`
for file in $FILES
do
/opt/aos/exe/testStatusLock $file | grep Locked >/dev/null 2>&1
status=$?
if [ $status = 0 ]
then
echo $file | awk -F_ '{ print $3 }'
fi
done
2. Once the INI70 instances are stopped, suspend Message Forwarding, on each
machine, by issuing the command:
d:/opt/aos/MsgFwd/scripts/stop_MsgFwd
3. Once the INI70 instances are stopped, suspend Message Relay facility by issuing the
command:
d:/opt/aos/MsgFwd/scripts/stop_MsgRelay

Loading INI Package

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:).
5. Select the E:\Windows\<MKS8_HPS_SPS>\INI folder.
6. Select the setup.exe file.
7. Turn the I/A Series software back on. Modify the Foxboro I/A startup options.
Reference your specific I/A Series documentation for detailed instructions on setting
these features.
8. Reboot the PC.

Restoring Configuration Information

To restore configuration information, please do the following:
♦ Confirm the contents of d:/usr/fox/bin/fox_apps.dat. Do not simply restore the
previous copy.

68
8. Maintenance - Windows Stations B0400EC – Rev A

♦ Confirm the contents of the c:/windows/system32/drivers/etc/services

(Windows XP OS), or c:/winnt/system32/drivers/etc/services (Windows NT
OS) file. Do not simply restore the previous copy.
♦ Restore the FileOfNames file used by Message Forwarding.
♦ Restore the FileOfProxies and FileOfTargets files used by the Message Relay
facility.
♦ Rebuild the Informix database from the map files if necessary.

Restart the INI Package

The simplest restart mechanism would be to reboot.

Quick Fixes
After non-INI software related Quick Fixes are installed, the following should be checked:
♦ The file d:/usr/fox/bin/fox_apps.dat (Windows systems) should contain the
INI70 Package startup commands.
♦ The file c:/windows/system32/drivers/etc/services (Windows XP OS), or
c:/winnt/system32/drivers/etc/services (Windows NT OS) should contain the
Message Forwarding and Message Relay service definitions.
♦ The command show_params should show the same information as before the Quick
Fix was installed.

AOS Software
The following maintenance information is for the AOS for Windows OS package.

Package Removal
Take the following steps to remove the AOS for Windows OS package.
1. Stop all mapping applications on the Client by using AOSUNMAP. Create a script as
follows to generate a list of those processes to stop with AOSUMAP.
#!/bin/sh
cd /opt/aos/status
FILES=`ls INI51_map_* | grep -v '_monitor'`
for file in $FILES
do
/opt/aos/exe/testStatusLock $file | grep Locked >/dev/null 2>&1
status=$?
if [ $status = 0 ]
then
echo $file | awk -F_ '{ print $3 }'
fi
done
2. Select Start, then Settings, and then select the Control Panel.
a. Select Add or Remove Programs
b. Select either the AOS with Alarms or the AOS without Alarms item.

69
B0400EC – Rev A 8. Maintenance - Windows Stations

c. Select the Remove button.

3. Remove the /opt/aos directory from both machines.

I/A Series Software Upgrades

Day 0 Upgrades
In the case of a Day 0 upgrade, preserve the AOS for Windows OS software configuration.
The AOS for Windows OS package should then be reinstalled from the original or replacement
media. Frequently, the most recent version of the AOS for Windows OS software is available
upon request so please investigate obtaining the latest materials by contacting your Foxboro Field
Service or Account Representative.

Non-Day 0 Upgrades
Other than the file d:/usr/fox/bin/fox_apps.dat file, the AOS for Windows OS software
should not be impacted by a non-Day 0 upgrade. However, it would be wise to backup the
d:/opt/aos directory and the information in the Informix database.

AOS Software Upgrades

The AOS for Windows OS software can be upgraded without rebooting the hosting AW.
However, the AOS for Windows OS package must be shutdown first. In all cases, consult the
specific upgrade instructions that come with the upgrade materials. The following information is
generic.
The steps in an upgrade are:
1. Backup configuration data.
2. Stop the package.
3. Load the new files.
4. Install the new files.
5. Restore the configuration data.
6. Restart the package.

Saving Configuration Data

1. Preserve the startup file d:/usr/fox/bin/fox_apps.dat.
2. Preserve the startup file d:/usr/fox/bin/go_AOS.ksh.
3. Stop all mapping applications by using AOSUNMAP.
An Informix database stores the configuration information related to the Data Transfer portion
of the AOS for Windows OS package. Most upgrades will not require this step, but any upgrade
that alters the aos database will.

Loading AOS Package

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

70
8. Maintenance - Windows Stations B0400EC – Rev A

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

3. Insert the AOS for Windows OS software 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:).
5. Select the E:\Windows\<MKS8_HSP_SPS>\aos folder.
6. Select the setup.exe file.
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.

Restoring Configuration Information

To restore configuration information, please do the following:
♦ Confirm the contents of d:/usr/fox/bin/fox_apps.dat. Do not simply restore the
previous copy.
♦ Rebuild the Informix database from the map files if necessary.

Restart the AOS Package

The simplest restart mechanism would be to reboot.

Quick Fixes
After non-AOS for Windows OS software related Quick Fixes are installed, the following should
be checked:
♦ The file d:/usr/fox/bin/fox_apps.dat (Windows systems) should contain the AOS
Package startup commands.
♦ The command show_params should show the same information as before the Quick
Fix was installed.

71
B0400EC – Rev A 8. Maintenance - Windows Stations

72
9. Maintenance - Solaris Stations
This section deals with the maintenance and troubleshooting of the Isolation Station
configuration on Solaris Stations.

Isolation Station Configuration Utility

Data Backup
The map files are generated in the directory /opt/iss/tmp/<AWname> where AWname is the name
of the host station. The user should archive the map files into another directory for safe-keeping
because at the beginning of each generation of the map files, the directory opt/iss/tmp is
emptied of its contents.

Package Removal
The following steps should be taken when removing the Isolation Station Software.
1. The Isolation Station Configuration Utility Software can be uninstalled executing the
UninstallISS script:
/opt/iss/scripts/UninstallISS
2. If needed save the /opt/iss/data and /opt/iss/tmp directories to another location
to preserve the current map files.
3. Remove the /opt/iss directory.

Upgrades
Preserve the current map files and remove the Isolation Station Configuration Utility Software
prior to upgrading. After the upgrade the /opt/iss/data and /opt/iss/tmp directories can be
restored.

I/A Series Software Upgrades

Day 0 and Day 1
Preserve the current map files and remove the Isolation Station Configuration Utility Software
prior to upgrading. After the upgrade the /opt/iss/data and /opt/iss/tmp directories can be
restored.

Quick Fixes
Preserve the current map files and remove the Isolation Station Configuration Utility Software
prior to upgrading. After the upgrade the /opt/iss/data and /opt/iss/tmp directories can be
restored.

73
B0400EC – Rev A 9. Maintenance - Solaris Stations

INI51 Software
The following maintenance information is for the INI51 package.

Package Removal
Take the following steps to remove the INI51 package:
1. Stop all mapping applications on the Isolation Station AW (remote station) by using
INIUNMAP.
The command: ps -ef | grep -v grep | grep INI51 | grep map
will generate a list of those processes to stop with INIUNMAP.
2. Use the script /opt/aos/MsgFwd/scripts/stop_MsgFwd on both the Isolation Station
Server AW (local station) and Isolation Station AW (remote station) to stop message
forwarding:
cd /opt/aos/MsgFwd/scripts
./stop_MsgFwd
3. Use the script /opt/aos/MsgFwd/scripts/stop_MsgRelay on either the Isolation
Station Server AW (local station) or the Isolation Station AW (remote station) to stop
message forwarding:
cd /opt/aos/MsgRelay/scripts
./stop_MsgRelay
4. Remove the startup commands from the file /etc/fox/user_apps.dat both
machines.
5. Remove the /opt/aos directory from both machines.
6. If the package was physically installed in another location, delete the aos directory
there as well.

I/A Series Software Upgrades

Day 0 Upgrades
In the case of a Day 0 upgrade, preserve the INI51 configuration. Refer to the Information
Network Interface for Solaris and Windows Software User Guide, B0400BM, for information on to
preserve the configuration information.
The INI51 package should then be reinstalled from the original or replacement media.
Frequently, the most recent version of the INI51 is available upon request so please investigate
obtaining the latest materials by contacting your Foxboro Field Service or Account
Representative.

Non-Day 0 Upgrades
Other than the file /etc/fox/user_apps.dat the INI51 software should not be impacted by a
non-Day 0 upgrade. However, it would be wise to backup the /opt/aos directory and the
information in the Informix database.
The discussion on INI51 Package Upgrades explains how to preserve the configuration informa-
tion.

74
9. Maintenance - Solaris Stations B0400EC – Rev A

INI51 Software Upgrades

The INI51software can be upgraded without rebooting the hosting AW/AP. However, the INI51
package must be shutdown first. In all cases, consult the specific upgrade instructions that come
with the upgrade materials. The following information is generic.
The steps in an upgrade are:
1. Backup configuration data.
2. Stop the package.
3. Load the new files.
4. Install the new files.
5. Restore the configuration data.
6. Restart the package.

Saving Configuration Data

1. Preserve the system file /etc/services.
2. Preserve the startup file /etc/fox/user_apps.dat.
3. The configuration file used by the Message Forwarding component of the INI51
package that may be replaced during an upgrade is:
♦ /opt/aos/MsgFwd/data/FileOfNames (The configuration file for the Message
Forwarding service.)
4. The configuration files used by the Message Relay component of the INI51 package
that may be replaced during an upgrade are:
♦ /opt/aos/MsgFwd/data/FileOfProxies
♦ /opt/aos/MsgFwd/data/FileOfTargets
An Informix database stores the configuration information related to the Data Transfer portion
of the INI51 package. The information in this database can be converted back into map files by
the use of the INIREPORT script.
Most upgrades will not require this step, but any upgrade that alters the aos database will.

Stopping the INI Package

To halt the INI51 software, use the INIUNMAP command to unmap the INI51 instances currently
running.
1. Use the following command to see a list of the current INI51 instances.
ps -ef | grep INI51 | grep map
2. Once the INI51 instances are stopped, suspend Message Forwarding, on each
machine, by issuing the command:
/opt/aos/MsgFwd/scripts/stop_MsgFwd
3. Once the INI51 instances are stopped, suspend Message Relay facility by issuing the
command:
/opt/aos/MsgFwd/scripts/stop_MsgRelay

75
B0400EC – Rev A 9. Maintenance - Solaris Stations

Loading INI Package

To load the updated INI51 software without rebooting, follow the normal installation procedure,
but invoke the installAOS script with the -online option as shown here:
installAOS -online

Restoring Configuration Information

To restore configuration information, please do the following:
♦ Confirm the contents of /etc/fox/user_apps.dat. Do not simply restore the previ-
ous copy.
♦ Confirm the contents of /etc/services. Do not simply restore the previous copy.
♦ Restore the FileOfNames file used by Message Forwarding.
♦ Restore the FileOfProxies and FileOfTargets files used by the Message Relay
facility.
♦ Rebuild the Informix database from the map files if necessary.

Restart the INI Package

The simplest restart mechanism would be to reboot or run the commands in user_apps.dat by
hand.

Quick Fixes
After non-INI51 software related Quick Fixes are installed, the following should be checked:
♦ The file /etc/fox/user_apps.dat for INI Package startup commands.
♦ The file /etc/services should contain the Message Forwarding and Message Relay
service definitions.
♦ The command show_params should show the same information as before the Quick
Fix was installed.

AOS Software
The following maintenance information is for the AOS for Solaris OS package.

Package Removal
Take the following steps to remove the AOS for Solaris OS package:
♦ Stop all mapping applications on the Isolation Station AW (remote station) by using
AOSUNMAP. The command:
ps –ef | grep –v grep | grep aos | grep map
generates a list of those processes.
♦ Remove the startup commands from the file /etc/fox/user_apps.dat.
♦ Remove the /opt/aos directory.
♦ If the package was physically installed in another location, delete the aos directory
there as well.

76
9. Maintenance - Solaris Stations B0400EC – Rev A

I/A Series Software Upgrades

Day 0 Upgrades
In the case of a Day 0 upgrade, preserve the AOS for Solaris OS software configuration. See the
Application Object Services User’s Guide, B0400BZ, for an explanation on how to preserve the
configuration information.
The AOS for Solaris OS package should then be reinstalled from the original or replacement
media.

NOTE
The most recent version of the AOS for Solaris OS software is available upon
request so please investigate obtaining the latest materials by contacting your
Foxboro Field Service or Account Representative.

Non-Day 0 Upgrades
Other than the file /etc/fox/user_apps.dat, the AOS for Solaris OS product should not be
impacted by a non-Day 0 upgrade. However, it would be wise to backup the /opt/aos directory
and the information in the Informix database.

AOS Software Upgrades

The AOS for Solaris OS software can be upgraded without rebooting the hosting AW/AP.
However, the aos process must be shutdown first. In all cases, consult the specific upgrade
instructions that come with the upgrade materials. The following information is generic.
The steps in an upgrade are:
1. Backup configuration data.
2. Stop the package
3. Load the new files
4. Install the new files
5. Restore the configuration data
6. Restart the package

Saving Configuration Data

The startup file to preserve is /etc/fox/user_apps.dat.
The Data Transfer portion of the AOS for Solaris OS package stores its configuration informa-
tion in the Informix database. The information in this database can be converted back into map
files by the use of the AOSREPORT script. Most upgrades do not require this step, but any upgrade
that alters the aos database does.

Stopping the AOS Package

To halt the AOS for Solaris OS software, use the AOSUNMAP command to unmap the aos instances
currently running. Use the command that follows to see the list of current aos instances.
ps –ef | grep –v grep | grep aos | grep map

77
B0400EC – Rev A 9. Maintenance - Solaris Stations

Loading AOS Software

To load the updated AOS for Solaris OS software without rebooting, follow the normal installa-
tion procedure, but invoke the installAOS script with the -online option as shown here:
installAOS -online

Restoring Configuration Information

To restore configuration information, please do the following:
♦ Confirm the contents of /etc/fox/user_apps.dat. Do not simply restore the
previous copy.
♦ Rebuild the Informix database from the map files if necessary.

Restart the AOS Package

The simplest restart mechanism would be to reboot. Otherwise, run the commands in
user_apps.dat by hand.

Quick Fixes
After non-AOS for Solaris OS related Quick Fixes are installed, the following should be checked:
♦ The file /etc/fox/user_apps.dat should contain the AOS package startup
commands.
♦ The command show_params should show the same information as before the Quick
Fix was installed.

78
10. Troubleshooting
This section deals with the troubleshooting of the Isolation Stations.

General
Reference the Application Object Services User’s Guide (B0400BZ) and the Information Network
Interface for Solaris and Windows Software User Guide (B0400BM), that are provided as part of the
Isolation Station Software deliverable, for more troubleshooting information.

Station Overload
There are three types of overload that can occur in CPs and AWs as in any computer:
1. CPU Cycles (Seen in OM overruns and Control Block overruns.)
2. I/O - IPC connections or OM lists run out. (Most commonly seen as cyan points on
WPs that try to look at the CP.)
3. Memory - OM lists take RAM.

CPU Cycles
The following can be done to reduce CPU load:
♦ Run AOS/INI applications less often.
♦ Run another workstation.

I/O Loading
There are only two solutions sure to make a difference:
1. Run the INI software on the same box with the AIM*Historian and share the OM
lists. This could require multiple copies of the INI and AOS software (1 per
AIM*Historian host)
♦ This approach reduces the OM IPC connections, OM lists, RAM consumption,
and CPU cycles required since generally many or all of the points are already in
the AIM* Historian.
2. Reduce the number of points that are monitored.
There are two other handles that one can use:
1. The update rate on the aos instances can be increased to reduce the CPU load on the
CP.
♦ For example, if the default is set to 2 seconds, it could be increased for an applica-
tion like this one to the maximum of 10 seconds.
2. The change deltas of the values monitored by the aos instances feeding the INI may
be small enough to cause extra traffic.
a. This is a far less common source of problems unless they are set to 0.0.

79
B0400EC – Rev A 10. Troubleshooting

b. Review the deltas set in the Isolation Station Server AW’s AOS map file.

Memory
The only option available, to reduce memory use, is to use fewer variables.

Baseline
The following steps can be taken to establish a baseline and a measure of impact created by the
Isolation Station Server AW.
1. Stop the FoxAPI and AOS processes on the Isolation Station Server AW. This will
eliminate the load of the CP introduced by the Isolation Station Server AW. Stopping
the INI process alone has no impact on CP loading.
2. Trend the following values from the CPs in the system. This provides the baseline
that you need. Collect this data for at least 24 hours with the FoxAPI and AOS
processes off.
a. Idle Time
b. Control Block Loading
c. OM Loading
d. I/O Loading
3. Start the Isolation Station Server AW software (AOS and INI) to reestablish the
operation of the Isolation Station System and the load on the CPs.
4. Examine the impact of the trends to see the image of the Isolation Station Server AW
software.

Slow Displays
If displays are slow it is probably because the display was raised before the required AOAs were
created. In this case, the OM table in the file will be flushed and need to be repopulated by calling
the display up multiple times.

Delay of Use After Reboot

The only way to speed up object creation is to specify the skipCSA option when creating the tags.
The skipCSA option skips registration checks with CSA and greatly improves the speed of
creation. However, there is some risk. If the database has new applications since the last time the
objects were created with CSA registration, it is possible that you could create the same objects in
multiple stations.
A few examples are:
AOSCREATE <applicationName> skipCSA
aos create <applicationName> skipCSA
INICREATE <applicationName> skipCSA
INI51 create <applicationName> skipCSA
INI70 create <applicationName> skipCSA

80
10. Troubleshooting B0400EC – Rev A

Speed Up Database Build

There is no way to speed this up. However, the database build only needs to be done once if the
.map file has not changed. There is no reason to rebuild the database at reboot because the .map
file cannot have changed while the machine was down. Be sure that the database is not being
rebuilt by not running the commands: AOSBUILD, aos builddb, INIBUILD, or INI70 builddb at
reboot.

Isolation Station Tag Not Updating

This diagnostic procedure requires someone who is familiar with FoxAPI, the OM, and the
related tools, e.g., oma, som, and rsom found in the /opt/fox/bin/tools directory and foxtst
and foxspy found in the /opt/fox/ais/bin directory. Some of these utilities have manual pages
in that directory and some of them are documented in the manual Software Utilities (B0193JB).
There are people in Field Service and the Global Product Support center with the correct skills.
Contact them if you are not familiar with the tools being used.
Here is the general approach to follow:
1. Get some background information
a. Determine the name of a tag that is not updating.
b. Determine the source control station for that tag by using
/opt/aos/exe/locate <compound>.
♦ Is this station a CP10 or CP15?
♦ Is this station exhibiting a heavy CPU load?
♦ Are the communication resources heavily taxed?
The following instructions can help answer these questions:
1) Examining the free memory in the control station using the STATION block
display,
2) Examining the OM load on the STATION block display, and
3) Using rsom:
* To examine the number of OM lists that are active in the station and
* To determine the number of stations to which the controller is
sending data or from which it is receiving data on a change-driven
basis.
2. Determine where the failure to update occurs:
a. Use aoGet command on the Isolation Station AW (remote) station (the one in the
DMZ) to get the current value of an AOA that is the target of a ‘p’ map
/opt/aos/exe/aoGet -VSW A:O.A
If this value is not updating the problem could be with the netFoxAPI, INI, AOS,
FoxAPI, OM, or Control Station.
b. Use aoGet command on the Isolation Station Server AW (local) station to get the
value of the shadow object. For example:
/opt/aos/exe/aoGet -VSW S_A:O.A

81
B0400EC – Rev A 10. Troubleshooting

If this value is not updating, the problem could be with AOS, FoxAPI, OM, or
Control Station.
c. Use foxtst and/or foxspy, in the /opt/fox/ais/bin directory, to examine the
FoxAPI data sets on the Isolation Station Server AW (local) station and
created/used by AOS to determine if FoxAPI is reporting changes.
♦ If FoxAPI is reporting changes, the issue is in AOS.
♦ If FoxAPI is not reporting changes, the issue could be the FoxAPI, OM or the
Control Station.
d. Use som, found in the /opt/fox/bin/tools directory, to examine the OM lists on
the AW running to determine if the tag is in a local OM list and if it is updating.
♦ If the tag is neither a local OM list nor in FoxAPI, the problem is in the AOS.
♦ If the tag is not on a local OM list and is in FoxAPI, the problem is in the OM
(or maybe with FoxAPI). Contact the Global Product Support center.
♦ If the tag is in both places (FoxAPI and OM), the problem is most likely that
the OM is not reporting updates to FoxAPI. Go to the next step to determine
what the situation is.
e. Use rsom, found in /opt/fox/bin/tools directory, to examine the OM lists in
the Control Station that holds the tag.
♦ If the tag is in a remote OM list and it is not updating (per the earlier tests),
the problem is either:
1) In the control station and you need support from the Global Product
Support center or
2) Much more likely, the change delta is too large.
♦ If the tag is not in a remote OM list and it is in the local OM list (per the
earlier tests), the problem is in the Control Station. It is most likely caused by
opening OM lists too quickly. Alternate causes include lack of communica-
tion resources in the control station.
3. Corrective Actions
a. If it is suspected that the problem is communication resources in the control sta-
tion, you need to review their consumption. The most resources to monitor
include
♦ IPC connections (use rsom)
1) OM lists (use rsom)
2) Free memory (used to populate lists; use the station block display)
3) CPU time (needed to respond to the OM opens; use the station
block display)
b. If it is suspected that the problem is that the Control Station is too loaded,
commonly CP10s and CP15s, to respond to the OM list opens do the following:
♦ Shutdown AOS.
♦ Change the ctdlay parameter in the /opt/fox/ais/bin/foxapi.cfg file to a
larger value.
♦ Stop and start FoxAPI

82
10. Troubleshooting B0400EC – Rev A

♦ Restart AOS
♦ Retest - It is common to write a script to get the value from the CBP and from
the AOA that matches it to look for problems. This can be done using foxspy
to some degree.
c. If the issue is in FoxAPI based on the analysis above, i.e., the local OM list is
updating, but foxtst and foxspy do not show the updates:
♦ Examine the change delta (found in the map file) and determine if it is too
large.
♦ If the change delta is appropriate, contact the Global Product Support center
to resolve the FoxAPI issue.
d. If the issue is in AOS based on the analysis above, i.e., foxtst and foxspy show
value changes, but the AOAs are not updating, do the following:
♦ Turn on debugging: /opt/aos/exe/aos debug <AppName> <count>
♦ Examine the standard output of the AOS instance and look for changes.
♦ If the trace does not show changes when the Control Station value changes (as
reported by FoxAPI), there may have an AOS error or a FoxAPI error.
Contact the Global Product Support center for AOS support.
♦ If the trace does show changes when the Control Station value changes (as
reported by FoxAPI), there is an AOS application issue. Contact the Global
Product Support center for AOS product support.
e. If the AOA on the Isolation Station Server AW (local) station is changing, but the
AOS application on the DMZ machine is not, the issue is in the INI application.
Do the following:
♦ Turn on debugging (/opt/aos/exe/INI70 debug <AppName> <count>)
♦ Examine the standard output of the INI application and look for changes.
♦ If the trace does not show changes when the AOA value changes, we may have
an INI application error. Contact the Global Product Support center for AOS
product support.
♦ If the trace does show changes when the Control Station value changes (as
reported by FoxAPI), we have a netFoxAPI issue.
f. If we have a netFoxAPI issue, do the following:
♦ Examine the FoxAPI data sets on the Isolation Station AW (remote) station to
determine if tags read by the INI application are present. This establishes that
the netFoxAPI setup is correct.
♦ If the INI application appears to be sending the value per its trace, but the
value is not reaching the Isolation Station AW (remote) station, there is a
netFoxAPI issue. Contact the Global Product Support center for support.

83
B0400EC – Rev A 10. Troubleshooting

84
Appendix A. Command Usage

BuildIniIssmaps
The Isolation Station Configuration Utility can be invoked by running the command
D:\opt\aos\exe\BuildIniIssMaps (Windows stations) or /opt/aos/exe/BuildIniIssMaps
(Solaris stations).

Synopsis
BuildIniIssMaps [local | all] <mapDefName> [-output] <LogFileName>
where:
<mapDefName> The map definition path and name. If no map definition name is entered the
default path and name, /opt/iss/data/mapDefIss, is used.
<LogFileName> Used in conduction with the output parameter and specifies output to a log file.
The output parameter can only be used on Windows operating systems.

Examples
The following are different examples of the BuildIniIssMaps command usage.
BuildIniIssMaps local d:/opt/iss/data/mapDefIss -output d:/opt/iss/log/buildmap.log
(This command can be executed only from a Windows workstation and builds map files for the
local station and creates the log file d:/opt/iss/log/buildmap.log.)
BuildIniIssMaps all /opt/iss/data/mapDefIss
(This command builds map files for all CPs on the local host using the default mapDef file.)
BuildIniIssMaps local
(This command builds map files for the local station using the default mapDef file.)
BuildIniIssMaps all
(This command builds map files for all CPs on the local hosts using the default mapDef file.)

85
B0400EC – Rev A Appendix A. Command Usage

86
Index
A
AIM*API 9, 10
AIM*AT 11
AIM*Historian 9, 79
aimapi.cfg 9, 10, 11
aisstart 31
aisstop 31
AOA xiv
aoAlm 57
AOAs 12
aod xvii
AOS xiv, 3, 10, 25, 27, 34, 37, 47, 57, 77
Configuration 40, 51
Isolation Station Server AW 38, 48
Contraints 11
Limitations 9, 11
Operation Services 57
Restrictions 11
AOs xiv
Restrictions 11
aos 57
Database 12
aos builddb 13, 64, 81
aos create 13, 64, 80
aos database xiv
aos map 13, 64
aos.exe builddb 63
aos.exe create 63
aos.exe map 64
AOSBUILD 81
AOSCREATE 80
AOSREPORT 77
AOSUNMAP 69, 76, 77
Application xiv, 11
Application Definition xiv
Application Object Attribute xiv
Application Object Services xiv
Application Objects xiv
Application Objects Services (AOS) 3
AppObjSrv 57
Automatic Startup 40, 50

B
BuildIniIssmaps 85
Solaris 52

87
B0400EC – Rev A Index

Windows 41

C
CBP xv
Compound Block Parameter xv
Configuration 37, 47
Configuration Backup
AOS 70, 77
INI51 75
INI70 67
Configuration Restore
INI51 76, 78
INI70 71
Configuration Utility 65, 73
Solaris 52
Windows 41
Control Network xv
Controller Hosts
Solaris 36
Windows 24
CSN xv
Customer Supplied Network xv, 5

D
Data Backup
Configuration Utility 65, 73
database xv
DCS 1
Delay of Use After Reboot 80

E
EVENT 59

F
file2dsk 27, 33
FileOfNames 41, 51, 67, 69, 75, 76
FileOfProxies 67, 69, 75, 76
FileOfTargets 67, 69, 75, 76
Firewall 2
FoxAPI 9, 10, 11, 12, 21, 23, 25, 31, 59, 80
foxapi.cfg 31
foxspy 25, 26
FoxView xv

G
go_INI 66
go_INI.ksh 67

88
Index B0400EC – Rev A

I
iaToQ xv, 39, 49, 60
ICC 12
Implementation 6
Information Network Interface xv
Information Network Interface (INI) 3
Informix 13
Installation 18
INI xv, 3, 10, 13, 22, 25, 37, 47, 59
Configuration
IS Server 38, 48
Data Transfer 3
Data Transfer Limitations 13
Limitations 9
Message Forwarding 3
Configuration
IS 41, 51
Isolation Station Server AW 39, 49
Limitations 15
Operation 59
Message Relay 3
Configuration
IS 41, 51
Isolation Station Server AW 39, 49
Limitations 15
Operation 61
Operation 59
INI Data Flow 59
INI15 13
INI51 25, 26, 27, 29, 30, 31, 32, 33
INI51 builddb 63
INI51 create 63, 80
INI51 map 64
INI70 21, 22, 23
INI70 builddb 81
INI70 create 80
INI70.exe builddb 63
INI70.exe create 63
INI70.exe map 64
INIBUILD 81
INICREATE 80
INIREPORT 67, 75
INIUNMAP 68, 74, 75
installAOS 28, 29, 30, 31, 35, 76, 78
-online 31
-override 31
Installation
Solaris 25
Windows 17
InstallISS 36

89
B0400EC – Rev A Index

IPC 15
IPC/COMEX xv, xvi
IRIS 61
Isolation Station 1
Isolation Station AW 2, 5, 6, 11, 40, 51
Isolation Station AW Installation
Windows 23
Isolation Station Configurator 3, 24, 36, 41, 51, 63
Isolation Station Firewall 2, 6
Isolation Station Server AW 2, 6, 9, 37, 47
Isolation Station Server AW Installation
Solaris 25, 33
Windows 18

L
LGV
Last Good Value 14
Limitations 9
Loading
AOS 78
INI51 76
INI70 68
Local Station xvi, 6, 37, 47
logical name xv, xvi
global xv
local xvi

M
Maintenance
Solaris 73
Windows 65
Manual Startup 39, 49
map 58
map file xvi
Map File Builder 42, 52
Local Station 43, 53
Map File View 44, 54
mapDef 4
mapDefIss 4, 43, 53
mapping xvi
Mapping Operators 4
Message Forwarding xvi
Functionality 60
Message Relay xiii
Broadcast Messages 61
MkMapFile xvii, 57
msgRelay xvi, 39, 41, 49, 51, 61, 62, 63

90
Index B0400EC – Rev A

N
netToIA xvii, 41, 51, 60
NIC xvii

O
Object Level Names 12
Object Manager xvii
Limitations 12
Object Template xvii
OM 9, 10, 11
Connections 10
Resources 9
OM_NUM_OBJECTS 29, 31, 35

P
P mapping 60
Package Removal
INI51 74
INI70 66

Q
qToNet xvii, 60, 62, 63
Quick Fixes 71, 78
Solaris 73, 76
Windows 65, 69

R
R mappings 11
Redundancy 7
redundancy 13
Remote Station xvii, 5, 40, 51
Removal
AOS 69, 76
Configuration Utility 65, 73
Reserved Names 12
Restart
AOS 71, 78
INI51 76
INI70 69
Restore
INI70 68

S
Script
installAOS 27, 34
-online 27, 34

91
B0400EC – Rev A Index

-override 27, 34
Scripts
INI Operation
INIUNMAP 66
Securely Moving Data 63
SENDCONF 59
SENDMSG 59
services 67, 69
show_params 69, 76, 78
skipCSA 80
Solaris
AOS
Installation 27, 34
FoxAPI
Installation 25
QF Installation 27, 33
FoxSpy
Installation 26
INI
Installation 29
Message Forwarding
Installation 32
Message Relay
Installation 32
NetFoxAPI
Installation 26, 33
stop_MsgFwd 66, 68, 74, 75
stop_MsgRelay 66, 68, 74, 75
Stopping
AOS 77
INI51 75
INI70 68

T
Tag Not Updating 81
Tips 10, 38, 48
Troubleshooting 79
Database Build 81
Slow Displays
Reboot 80
Station Overload 79
Baseline 80

U
Unix Commands
df 30
mkdir 30
mount 26, 27, 30, 33

92
Index B0400EC – Rev A

tar 26, 33
Upgrades 65, 73
AOS 70
Day 0
AOS 70, 77
Configuration Utility 65, 73
INI51 74
INI70 66
Day 1
Configuration Utility 65, 73
INI51 75
Loading 70
INI70 67
Non-Day 0
AOS 70
Configuration Utility 67
non-Day 0
AOS 77
INI51 74
USEAIMAPI 10, 11

W
Windows
AOS
Installation 21, 23
FoxAPI
Installation 21, 23
INI
Installation 22

93
B0400EC – Rev A Index

33 Commercial Street
Foxboro, Massachusetts 02035-2099
United States of America
www.foxboro.com
Inside U.S.: 1-866-746-6477
Outside U.S.: 1-508-549-2424 or contact your local Foxboro representative.
Facsimile: 1-508-549-4999
Printed in U.S.A. 0508