Installation Guide On Solaris: I/A Series Intelligent SCADA System

Installation Guide on Solaris (SY-5005013)
I/A Series
Intelligent SCADA System
Installation Guide
on Solaris
For the Master Station
Document ID: SY-5005013 Revision: 1.21

I/A Series Intelligent SCADA System Page 1 of 50
Installation Guide on Solaris (SY-5005013)
Invensys Process Systems Pty Ltd The Foxboro Company

738 Blackburn Road, 33 Commercial Street,
Clayton North, Foxboro Massachusetts 02035-2099
Victoria 3168
Australia United States of America
Telephone: +61 3 9589 9222 Telephone: +1-866-746-6477
Acknowledgements
Foxboro and I/A Series are registered trademarks of The Foxboro Company.
Invensys is a trademark of Invensys plc.
Sun, Sun Microsystems®, OpenWindows™ and Solaris are registered trademarks of Sun
Microsystems, Inc.
ULTRA SPARC® and SPARC® are registered trademarks of SPARC International, Inc.
UNIX® is a registered trademark of AT&T.
Checked by & Date: Approved by & Date:

Dev Manager Quality Manager Group Manager
Vasudha Gandhi Ganesh Natesan Shahid Ansari
DOCUMENT REVISION HISTORY:
Rev. Date Comments Prepared By

Created from previous Installation Manual V. Resman
1.01 14 Dec 01
(Document no. 2005426 v2.04). C. Ireland
S. Stevenson,
1.02 10 May 02 Updated for release 5.6.
D. Boyce
1.03 15 Dec 03 Updated for release 6.3 S. Stevenson
1.10 20 Dec 07 Updated for release 8.2 P.Srinivas
1.20 23 Feb 09 Updated the copyright information Prasanna Sivadas
1.21 30 Mar 09 Updated the part number to prefix SY- for release 9.0 Gnana Vasudha
COPYRIGHT RESERVED
The information and design as detailed in the document are the property of Invensys Process Systems
Pty Ltd and/or its associates and must be returned on demand. It is issued on the strict condition that
except with our written permission, it must not be reproduced, copied or communicated to any third
party, nor be used for any purposes other than that stated in the particular inquiry, order or contract
with which it is issued. The reservation of copyright in this document extends from each date
appearing thereon and in respect of the subject matter as it appeared at that relevant date.
© Invensys Process Systems Pty. Ltd. 2001-2009

ACN 000 522 261
All rights reserved

Installation Guide on Solaris (SY-5005013) Table of Contents
Table of Contents
1 Introduction ................................................................................................................................. 5
1.1 Overview ............................................................................................................................. 5
1.2 Contents of the Intelligent SCADA Package....................................................................... 6
1.3 System Requirements......................................................................................................... 6
1.4 Information Requirements................................................................................................... 8
1.5 Task Sequence ................................................................................................................... 9
2 Before Installing the Intelligent SCADA Software ................................................................. 12
2.1 Overview and Recommendations ..................................................................................... 12
2.2 User Setup Prior to Installation ......................................................................................... 13
3 Installing the Operating System and CDE .............................................................................. 14
3.1 Installing the Operating System ........................................................................................ 14
4 Accessing the Installation Interface........................................................................................ 18
5 Installing the Intelligent SCADA System ................................................................................ 20

5.1 Installing a New System.................................................................................................... 20
5.2 Upgrading the Intelligent SCADA Software ...................................................................... 22
5.3 Examine System & Export Databases .............................................................................. 22
6 Configuring the SCADA Station Type ..................................................................................... 23
7 Configuring the Packages for Installation .............................................................................. 31

7.1 HMI Locale ........................................................................................................................ 31
7.2 Installation Type ................................................................................................................ 31
7.3 Importing Configuration Settings....................................................................................... 32
7.4 Saving Configuration Settings........................................................................................... 32
7.5 Install now ......................................................................................................................... 33
8 Post installation procedures.................................................................................................... 35
8.1 Creating a History Database............................................................................................. 35
8.2 Archive Medium Interface ................................................................................................. 36
8.3 Printer Administration and Server Software...................................................................... 37
8.4 NTP Configuration............................................................................................................. 42
8.5 Tcp to Serial Interface ....................................................................................................... 42
8.6 Application Management .................................................................................................. 44
9 Product Licenses ...................................................................................................................... 45
9.1 Scada License................................................................................................................... 45
9.2 Versant License ................................................................................................................ 45
10 Advanced Configuration........................................................................................................... 46
10.1 Overview and Recommendations ..................................................................................... 46
10.2 Database Conversion ....................................................................................................... 46
10.3 Event Subsystem Optimisation ......................................................................................... 46
10.4 Large Distributed History Database Creation ................................................................... 47
11 Troubleshooting ........................................................................................................................ 49
11.1 Auto-Installer GUI.............................................................................................................. 49
11.1.1 Log files ............................................................................................................. 49
11.1.2 Known Limitations.............................................................................................. 49
11.2 Time Zones with Daylight Savings Changes .................................................................... 50

Installation Guide on Solaris (SY-5005013) List of Figures & Tables
List of Figures
Figure 4-1 Intelligent SCADA Installation Menu Window ..................................................................... 19
Figure 5-1 The Install Window.............................................................................................................. 21
Figure 6-1 Database Station HMI Domain Names window.................................................................. 24
Figure 6-2 Database-less Station HMI Domain Names window .......................................................... 25
Figure 6-3 Database-less Domainless Station HMI Domain Names window ...................................... 26
Figure 6-4 Units & Station Names window........................................................................................... 27
Figure 6-5 Scada Server Entries for Dom_1 window ........................................................................... 28
Figure 6-6 Server Entries for dom_2 window ....................................................................................... 29
Figure 7-1 Locale Settings window ...................................................................................................... 31
Figure 7-2 Export Setup File window ................................................................................................... 32
Figure 7-3 Settings Saved confirmation Message window .................................................................. 33
Figure 7-4 Install Versant Window ...................................................................................................... 33
Figure 7-5 Installation Complete Window............................................................................................ 34
List of Tables
Table 1-1 Memory requirements for the Intelligent SCADA software .................................................... 7
Table 1-2 Disk space requirements for the Sun workstations................................................................ 7
Table 1-3 Recommended 20GB disk partitioning (for a small system).................................................. 7
Table 1-4 Recommended 40+ GB disk partitioning ............................................................................... 8
Table 1-5 System Directory Structure .................................................................................................... 9
Table 1-6 Task Sequence for Installation of Intelligent SCADA Software on a New System .............. 10
Table 1-7 Upgrading the Intelligent SCADA Software on an Existing System..................................... 10
Table 11-1 Known Auto-Installer GUI Limitations ................................................................................ 49

Installation Guide on Solaris (SY-5005013) Chapter 1: Introduction
1 INTRODUCTION
1.1 Overview
ABOUT THE MANUAL
The I/A Series Intelligent SCADA System Solaris Software Installation Manual describes the
installation procedure for the I/A Series Intelligent SCADA System Revision 9.0.
The Solaris Software Installation Manual is arranged according to the logical sequence of tasks that
the user is required to perform in order to install the Intelligent SCADA System.
ABOUT THE USERS

This manual is designed for designated I/A Intelligent SCADA system administrators who are
responsible for the daily maintenance of the Intelligent SCADA hardware and software at their
allocated site installation. The following assumptions are made concerning the Intelligent SCADA
system administrator:
 Knowledgeable about UNIX system administration.
 Familiar with TCP/IP network installation.
 Understand mouse-based graphical windows environments on UNIX workstations.
 Recognize the point representations of the Intelligent SCADA System database.
DOCUMENTATION CONVENTIONS
The following documentation conventions are utilized throughout this manual:
Syntax Example Comments
bold Warning Information that the user should take

(Unix) particular notice of.
(NT) Type of HMI station.
italics Events List window The name of windows, buttons, fields,
Enter button functions, documents, etc.
Delete Annotation option
Database Name field
bold italics dbtable Commands or input that must be
cd /opt/scada/bin entered by the user.
Sammi_license -w
<angled brackets> <RETURN> The word or symbols between the <
Press <F1> to continue. and > refer to a keyboard key,
/<pointName>/cvq function.
Also information that is to be inserted.
Courier New LNA_Dispatcher::instance(); Applications Programming Interface or
font void *upt1 program code.
REFERENCES
The following documents are referenced in this manual:
 I/A Series Intelligent SCADA System - Functional Specification – Part No. SY-2005415
 I/A Series Intelligent SCADA System - Database Configurator User’s Manual – Part No.
SY-5005003
 I/A Series Intelligent SCADA System - HMI Engineer’s Manual – Part No. SY-5005005

1.2 Contents of the Intelligent SCADA Package

MEDIA
I/A Series Intelligent SCADA System package should contain the following items:
 1 CD-ROM containing all the necessary software. Part Number SY-1104179. I/A
SCADA UNIX Software Media Only - latest Version. This is the Media with all required
UNIX software for installation of the I/A SCADA Master Station Product.
 License(s) dependent on the project requirements.
INSTALLATION SCRIPT
The CD ROM(s) contains the installation GUI (Graphical User Interface) that allows the user to select
various installation options, but otherwise operates automatically.
The Intelligent SCADA installation script is used to:
 Install the Intelligent SCADA software onto a new system.
 Upgrade the Intelligent SCADA software on an existing system.
DOCUMENTATION
The I/A Series Intelligent SCADA System Manuals (including Installation and Operator’s Manuals) are
supplied as part of the I/A Series Intelligent SCADA - Master Station User Documentation (part
number SY-2005664) on CD-ROM, and must be ordered separately.
1.3 System Requirements

EQUIPMENT AND SOFTWARE
The minimum recommended Solaris platform is specified in the applicable I/A Series Intelligent
SCADA System - Functional Specification document (document no. SY-2005415).
Minimum equipment recommendations are given for the following items:
 Operating system
 Memory
 Hard Disk
 Video Card
 Screen
 Keyboard
 Mouse
 Sound
 Network Card
PHYSICAL MEMORY REQUIREMENTS

Depending on the system configuration, a machine may require more memory than the minimum
recommendation. The precise memory requirements can be calculated using the parameters listed in
Table 1.1.

Table 1-1 Memory requirements for the Intelligent SCADA software
Software Memory Requirement

Full Graphics 64MB per console
Solaris 10 512MB
VERSANT 20MB
Intelligent SCADA Database Configurator 30MB
Intelligent SCADA Database Process 20MB + (8KB / point)
Intelligent SCADA History Subsystem 20MB + (8KB / point)
Intelligent SCADA Process Monitor 1MB
DISK SPACE
The target workstation must have enough disk space for the software as listed in Table 1.2.
Table 1-2 Disk space requirements for the Sun workstations
Software Disk Space

Full Graphics 200MB
Intelligent 600MB
SCADA
Solaris 10 2GB
The information presented in Table 1.2 represents the disk space requirements for the software only.
More disk space must be allocated for the Intelligent SCADA databases. It is recommended that 1GB
of disk space is allocated to each of:
 Solaris, Full Graphics and other third party packages.
 The Intelligent SCADA software.
The target workstation must have at least 200MB of free disk space for the Full Graphics installation
process. It must also have at least 100MB free for the Sammi installation. Additional space must also
be allocated to customer formats (this is entirely dependent on the number of customer displays and
the language used).
DISK PARTITIONING
If the target workstation is not operating the History Subsystem, Full Graphics and Intelligent SCADA
can be compressed onto a 20GB disk. Table 1.3 lists the partitioning of a 20GB disk.
Table 1-3 Recommended 20GB disk partitioning (for a small system)
Partition Physical Size

/ 200MB
Swap 3 x Physical Memory (RAM)
i.e. 3 x 500MB RAM = 1500MB
/var 400MB
/usr 2000MB
/opt Remainder of disk
If the target workstation operates the History Subsystem, larger memory requirements are necessary.
A 40+ GB disk should be used and partitioned according to the information listed in Table 1.4.

Table 1-4 Recommended 40+ GB disk partitioning
Partition Physical Size

/ 350MB
swap 3 x Physical Memory (RAM)
i.e. 3 x 500MB RAM = 1500MB
/var 650MB
/usr 3000MB
/opt Remainder of disk
LAN
The Intelligent SCADA local area network (LAN) may be an Ethernet or Fibre Data Distributed
Interface (FDDI).
1.4 Information Requirements

REQUIRED INFORMATION
It is important for the Intelligent SCADA System Administrator to plan the Intelligent SCADA System
Installation. The system administrator must know the:
 System configuration of the domain.
 Number of stations operating within the domain.
 Network organization.
 Network connections to all the stations.
 Level of redundancy that is required within the domain.
DOMAIN SUPPORT
The Intelligent SCADA System currently supports multi domains for HMI only.
SUPERUSER LOGON
It is imperative that the system administrator be logged on as superuser on the target workstation
during Intelligent SCADA System installation or any administrative tasks.
No one, apart from the system administrator, should be logged on to the target workstation during the
installation procedure. Also, ensure that there are no other processes operating while installing the
Intelligent SCADA System.
INTELLIGENT SCADA USERS

There are two default user accounts in the Intelligent SCADA System:
 Operator
 Engineer
Both users are in the LN2068 group.
The home directory for the user operator is /opt/fg/operator and for the user engineer is
/opt/fg/engineer. The default shell for both users is /bin/ksh. The user characteristics are recorded in
the files /etc/passwd and /etc/group.
If the user accounts, operator and engineer do not exist, they are created during the installation
process.
If the user characteristics are different, they can be altered using the useradd UNIX command.
NETWORK
Each workstation on the network must be given a unique unit number and IP host name. The host
name should appear in the /etc/hosts file to define the IP address. The host name should also appear
in the /.rhosts file to enable remote host access to install databases across multiple stations.
DIRECTORY STRUCTURE
Table 1.5 lists the recommended system directory structure used with the Intelligent SCADA System.
The Solaris installation program provides size recommendations based on the software selected for
the installation. Options should be selected to correspond to the slice size recommendations given in
’Disk Partitioning’.
Table 1-5 System Directory Structure
Slice File System Purpose

0 root or / Slice 0 contains the system files and directories of the operating
system.
1 swap Slice 1 provides virtual memory or swap space. Swap space is used
as a form of virtual physical memory when the memory requirement
of the currently launched applications exceeds that value.
2 backup Slice 2 is used by the operating system to reference the entire disk.
Sun’s format and installation programs define it automatically. This is
a raw partition that can be used to make an image of the disk.
3 /opt System application software resides on this slice. If there is not
enough room on the disk to place the /opt directory in slice 3, then it
is placed in slice 0.
4 /usr The operating system commands or executables are located in this
slice.
5 /var Slice 5 contains the system files and directories. It is used by the
operating system services and application software.
1.5 Task Sequence

INTRODUCTION
The overall process for the Intelligent SCADA System installation involves:
 Ensuring that the system requirements are met in terms of hardware and overall system
setup and configuration.
 The installation of the operating system.
 The installation of the Intelligent SCADA software.
Table 1.6 represents the sequence of activities or tasks that must be performed to install the Intelligent
SCADA software on a new system.
Table 1.7 represents the task sequence to upgrade the Intelligent SCADA software on an existing
system.
THE TASK SEQUENCE CAN BE USED:

 As a checklist to ensure that the installation process is followed correctly.
 By those who are already familiar with the installation procedure.
 By those who are upgrading software versions.

Table 1-6 Task Sequence for Installation of Intelligent SCADA Software on a New System
Step Action Details x/√

1 Start • Ensure that system (hardware and software)
and information requirements are met.
2 Install the Sun Solaris • Log on as superuser
Operating System • Boot from the applicable Solaris 10
Operating System CD/DVD.
• Install the operating system with the
developer option.
• Select the appropriate disks to partition and
customize.
3 Access the Intelligent SCADA • Login as superuser.
installation interface • Insert the Intelligent SCADA CD-ROM.
• ./install from the CD-ROM directory.
• Set the DISPLAY environment.
• Create default users.
4 Install the Intelligent SCADA • Select the New option.
Software • Select applicable Type of This HMI Station.
• Select Full Installation.
• Enter the Location of the REGISTRY_OS
file.
• Click Install Now.
5 Post Installation Procedures • Create a History Database
• Configure Archive Medium Interface
• Configure Printer Administration and Server
Software
• Configure tcp to Serial Interface (if
applicable).
6 Product Licenses • Master Station Software
• Versant (if applicable)
Table 1-7 Upgrading the Intelligent SCADA Software on an Existing System
Step Action Details x/√

1 Take the System Off-Line
2 Access the Intelligent SCADA • Login as superuser.
installation interface • Insert the Intelligent SCADA CD-ROM.
• ./install from the CD-ROM directory.
• Set the DISPLAY environment.

3 Install the Intelligent SCADA • Select the Upgrade option.

Software • Select the Examine and Export options to
backup the custom configuration settings and
databases.
• Select Installation on a Server.
• Select Upgrade Type of Installation.
• Select Partial Installation.
• Select the appropriate packages to be
installed. Typically, these are only SCADA
and Full Graphics packages.
• Enter the Location of the REGISTRY_OS file.
• Enter the directory location of the saved setup
file.
• Click Install Now.
• Click OK to reboot the system to complete the
final installation phase.
4 Update development and • Use the update Perl script.
history databases
5 Full Database Install • Use the Database Configurator to perform a
full database install from the workstation that
contains the master development database.
6 Reload the new real-time
Database
7 Check that the Stations are
Synchronized

Installation Guide on Solaris (SY-5005013) Chapter 2: Before Installing the Intelligent
SCADA Software
2 BEFORE INSTALLING THE INTELLIGENT

SCADA SOFTWARE
CONTENTS
This section describes information that the user should read prior to installing the Intelligent SCADA
software.
2.1 Overview and Recommendations

SYSTEM BACKUP
Prior to any installation procedure, backup or archive the existing system files and directories.
For users with an existing system, it is advisable to perform a system backup prior to installing the
Intelligent SCADA software or upgrading the existing Intelligent SCADA System. It is important to do
this step, as the installation process initially deletes any old software that it detects. Consequently,
some customized files or directories may be inadvertently deleted.
Refer to document no. SY-5005005 I/A Series Intelligent SCADA System - HMI Engineer’s Manual for
detailed information on HMI files to backup.
Refer to document no. SY-5005003 I/A Series Intelligent SCADA System - Database Configurator
User’s Manual for detailed information on how to backup development databases.
DISTRIBUTION MEDIUM
The Intelligent SCADA System installation is initiated from the CD-ROM supplied by Foxboro.
INSTALLATION SCRIPT
The CD-ROM contains the installation interface that prompts the user for various installation options,
but otherwise operates automatically.
The Intelligent SCADA installation interface is used to:
 Install the Intelligent SCADA software onto a new system.
 Re-install the Intelligent SCADA software or upgrade to a later version of the software,
on an existing system.
SUPERUSER LOGON
The Intelligent SCADA installation procedure requires the system administrator to be logged on to the
system as superuser.
To ensure that the superuser has the necessary execution path for the software installation, type the
following command on a command line:
PATH=/usr/sbin:/usr/bin:$PATH;export PATH <RETURN>
No one should be logged on to the machine during the installation procedure, except the superuser.
CAUTION
Ensure that no other processes are operating while installing the Intelligent SCADA System.
INSTALL TIME
In a Solaris 10 machine, full installation of Intelligent SCADA is successfully completed within 30
minutes.

Installation Guide on Solaris (SY-5005013) Chapter 2: Before Installing the Intelligent
SCADA Software
2.2 User Setup Prior to Installation

For users with workstations in a network server named environment, the files associated with
passwords, groups, hosts, protocols and services originate from the server machine, rather than the
files on the local machine. This causes problems during the creation of the Intelligent SCADA default
users engineer and operator. The Intelligent SCADA installation script modifies local files only and
many systems do not revert to the local files, if data is not available from the network server.
The user must ensure that there is compatibility in the user groups on the local machine and the
server machine. There are two solutions, of which one should be performed prior to installing the
Intelligent SCADA System.
SOLUTION 1
The system administrator should add the users, groups, services and hosts, as required, on the
information server. This ensures that the updates are performed only once and the updates will apply
to all systems.
The modifications involve adding single line entries to the network information tables (/etc/group and
/etc/services respectively), as described below:
Step 1 Add the engineer and operator user.
Step 2 Add the LN2068 group.
Step 3 Add the following services:
procmonitor 49494/tcp
pmonmgr 5099/tcp
SOLUTION 2
This solution involves enabling the machines on which the Intelligent SCADA software is to be
installed, to use the local files first rather than reverting to the network information services tables.
Step 1 In the /etc/nsswitch.conf file, change the following lines:
passwd
group
services
So that files is the first entry for the name service lookups.
Example: passwd nisplus [NOTFOUND=return] files changes to
passwd files nisplus [NOTFOUND=return] files

Installation Guide on Solaris (SY-5005013) Chapter 3: Installing the Operating
System and CDE
3 INSTALLING THE OPERATING SYSTEM AND

CDE
OVERVIEW
Installing the Intelligent SCADA software on a new system requires that the user:
 Install the Sun Solaris 10 operating system
3.1 Installing the Operating System

GETTING STARTED
For networked systems, the system administrator must have the following information prior to installing
the operating system:
 The host name or machine name for the workstation.
 The IP address of the workstation.
 The network.
REFERENCE
A comprehensive guide to installing the operating system can be obtained from the Solaris Installation
Manual. The following brief description only gives the required information in relation to the Intelligent
SCADA System.
The Solaris Common Desktop Environment (CDE) is the preferred X-Windows manager for use with
the Intelligent SCADA System. It provides users with a graphical window environment to organise and
manage their work. It also allows user to select required Open Windows session during the login into
the station as operator. Solaris 10 Operating System now includes CDE as part of the standard
installation.
PROCEDURE
Step 1 Log on as superuser.
Step 2 Type init 0 <RETURN>.
Step 3 Insert the Solaris 10 Operating System DVD in to the Drive and the boot from the DVD
Details: Type boot cdrom <RETURN>
Result: The Solaris installation program copies the Solaris software from the DVD to the
system’s local disk. This is performed interactively using a graphical or character
interface, or automatically without user intervention.
Step 4 Use the following table of appropriate responses and selections to install the operating
system.
Name of Installation Window Action or Selection

Select the Language • Select the Language for installation.
Welcome window • Click the Next button.
Network Connectivity • Select Network connectivity.
• Click the Next button.
Configure Multiple Network interfaces • Select the Network interfaces that
NOTE: This window is displayed, if your need to be configured.
system has Dual Ethernet cards. • Click the Next button.

Installation Guide on Solaris (SY-5005013) Chapter 3: Installing the Operating
System and CDE
Primary Network Interface • Select the Network card which you

NOTE: This window is displayed, if you want to make Primary.
select both interface cards in the previous • Click the Next button.
window.
DHCP for bge0(ce0) • If you use DHCP, select Yes and
click Next button and proceed to
IPv6 Configuration.
• If a DHCP server cannot be used,
obtain the following information
before proceeding.
o Host name for the system
o IP address
o Net mask
o Default router
• Select No, click Next button.
Hostname for bge0(ce0) • Enter a hostname for the system.
IP Address for bge0(ce0) • Enter the IP Address for bge0(cge0)
Net mask for bge0(ce0) • Enter the net mask.
IPv6 for bge0(ce0) • Select No.
Default Router for bge0(ce0) • Select Detect one
Note: This window appears if DHCP was • Click the Next button.
not selected in the step 6
Note: If the system has multiple network interface cards and you had selected both in
step 4, then repeat the above four steps for configuring the second network interface
card.
Kerberos • Select No.
Name Services • Select None
Time Zone • Select Geographical Region.
Continent and country • Select the appropriate Continent and
Country based on your Local
Settings.
Date and Time • Change as necessary.
Root password • Enter the Root password.
Summary window • Click the Change button to make
alterations
• Click the Confirm button.
Solaris Welcome window • Click the Next button.
Installer options • Click the Next button.
Specify Media • Select CD/DVD
License • Select Accept.

Installation Guide on Solaris (SY-5005013) Chapter 8: Post Installation Procedures
Select Type of Install • Select Custom Install.

Select Software Localizations • Select the appropriate Localization.
Select System Locale • Select English( POSIX)
Select Products • Click the Next button.
Additional Products • Click the Next button.
Solaris Software Group • Select Entire Group.

Disk Selection • Select the boot disk
Preserve Data • Select Yes, if an existing file system
needs to be preserved, else select
No.
Layout File System • Customize the various file systems
• /
• swap
• /usr
• /var
• /opt
• Click the Next button
Ready to Install • Click Install Now button.
NOTE: An Installation progress bar appears. Once the bar reaches 100 percent, the
system asks for Pause/Continue. Just click the Continue button to proceed. Then, the
system asks for reboot and the CD/DVD is ejected. In case the CD/DVD is not ejected
automatically, eject the CD/DVD manually from the drive.
The first time the system boots, a question is displayed in text mode on-screen asking
if the NFS protocol should be overridden. Accept the default (No) and let the boot
process continue.
Step 5 Once the machine has been rebooted, enter the superuser password and confirm it.
Step 6 Select N to disable auto-shutdown.
Step 7 Select Y to stop repetition of the above question.
Step 8 On the console screen, log in as superuser.
DUAL MONITOR
For dual monitor systems, perform the following additional procedure:
Step 1 Log in as superuser.
Step 2 Change to the /etc directory.
Details: Type cd /etc <RETURN>
Step 3 Create a new directory called dt.
Details: Type mkdir dt <RETURN>
Step 4 Change to the newly-created directory.
Details: Type cd dt <RETURN>

Step 5 Create a new sub-directory named config.

Details: Type mkdir config <RETURN>
Step 6 Change to the new sub-directory.
Details: Type cd config <RETURN>
Step 7 Copy the Xservers attributes to the current directory.
Details: Type cp /usr/dt/config/Xservers <RETURN>
Step 8 Edit Xservers.
Step 9 Append the following line to the end of the last line (do not add a new line)
-dev /dev/fb0 -dev /dev/fb1
Step 10 Exit the Xservers file.

Installation Guide on Solaris (SY-5005013) Chapter 4: Accessing the
Installation Interface
4 ACCESSING THE INSTALLATION INTERFACE

BEFORE STARTING
Prior to proceeding with the Intelligent SCADA installation:
 Ensure that a version of the software is not currently running.
 Ensure that Sammi is installed prior to SCADA installation.
PROCEDURE
To access the installation interface from the supplied CD-ROM:
Step 1 Exit the Intelligent SCADA System software.
Step 2 Login as superuser.
Step 3 Insert the Intelligent SCADA CD into the CD-ROM drive.
Step 4 Open a console window and change to the directory location of the installation script.
NOTE: For a CD-ROM installation this will be /cdrom/cdrom0. It is recommended that the
installation be done from the local CD-ROM drive. If the installation is to be undertaken
from a different location (i.e. a file or network share CD-ROM), the user should first
review the Trouble-shooting section of this manual to ensure the proposed installation
proceeds successfully.
Step 5 Execute the install script.
./install
Step 6 Set the DISPLAY environment.
If the DISPLAY environment Then:

has:
not been set Result: The installation script prompts the user for a
DISPLAY variable.
• If using the local host, press <RETURN>.
• If using a remote login, enter the name of the
DISPLAY in the form <hostname>:0.0.
Result: The installation script displays the Intelligent
SCADA Installation Menu window.
been set Result: if the default users "engineer" and "operator"
are set then:
The installation script displays the Intelligent SCADA
Installation Menu window.
Else: You need to create users.
Step 7 Install the foxinstall package that will create users for you.
Answer Y to " Do you want to continue with the installation of >foxinstall> (y,n,?)
Step 8 Enter a new password to the default user "engineer"
Confirm the password
Step 9 Enter new password for the default user "operator"
Confirm the password
Step 10 The Intelligent SCADA Installation Menu window is displayed.

Installation Guide on Solaris (SY-5005013) Chapter 4: Accessing the
Installation Interface
Figure 4-1 Intelligent SCADA Installation Menu Window

Installation Guide on Solaris (SY-5005013) Chapter 5: Installing the Intelligent
SCADA System
5 INSTALLING THE INTELLIGENT SCADA

SYSTEM
OVERVIEW
This section describes the procedures for new installation, upgrade installation and the Examine
system & Export databases procedure of the Intelligent SCADA software on a system.
5.1 Installing a New System

OVERVIEW
A full installation on a new system requires that the user:
 Install the Sun Solaris operating system
 Install the Intelligent SCADA software (including configuring the SCADA station type,
and the packages for installation)
 Run the applicable Post Installation Procedures
PROCEDURE
Step 1 Access the installation interface.
Details: Refer to Accessing the Installation Interface.
Result: The Intelligent SCADA Installation Menu is displayed.
Step 2 Select the New option.
Details: Click the option with the left mouse button.
Step 3 Click the OK button.
Result: The Install window is displayed.

SCADA System
Figure 5-1 The Install Window

SCADA System
5.2 Upgrading the Intelligent SCADA Software
The “Upgrade Instalaltion” feature is disabled users are requested not to use this option.
Existing user upgrading to Revision 9.0 from previous version of IA SCADA are requested to
contactsupport@ips.invensys.com for assistance.
5.3 Examine System & Export Databases
The “Examine System / Export” feature is disabled and users are requested not to use this option.
Existing user upgrading to Revision 9.0 from previous version of IA SCADA are requested to contact
support@ips.invensys.com for assistance.

SCADA System
6 CONFIGURING THE SCADA STATION TYPE

OVERVIEW
This section describes the procedure for the configuration of the SCADA Station Type.
SCADA Station Type options are:
1. A Station with Database within a domain, such as a server station or engineering
workstation.
2. A Database-less Station within a Domain, such as an operator station.
3. A Database-less Domainless Station, such as a remote operator station or supervisor
station.
Configuration of the SCADA Station Type requires that the user:
 Choose the SCADA Station Type option.
 Configure the Local HMI domain. (Except for Database-less Domainless Stations)
 Configure the Remote HMI Domains (If required).
NOTE: Even if the station being configured is not intended (or not licensed) for HMI the station, Local
and Remote HMI Domains must still be configured correctly to ensure that events are collected for the
station.
PROCEDURE
Step 1 On the Install window, select the Type of This HMI Station to be installed.
Result: The corresponding Config Domains or Config Remote Domains button becomes
available.
Step 2 Click on Config Domains button.
Result: HMI Domain Names window opens.

Installation Guide on Solaris (SY-5005013) Chapter 6: Configuring the
SCADA Station Type
Figure 6-1 Database Station HMI Domain Names window

SCADA Station Type
Figure 6-2 Database-less Station HMI Domain Names window

SCADA Station Type
Figure 6-3 Database-less Domainless Station HMI Domain Names window
Step 3 If the chosen installation is a Domainless Database-less Station, proceed to Configuring

Remote Domains; otherwise continue with Configuring Local Domain 1.
CONFIGURING LOCAL DOMAIN 1
Step 4 In the HMI Domain Names window, enter the (LOCAL) Domain 1 Domain Name.
Details: Any name containing alphanumeric characters (a-z, A-Z and 0-9), beginning with
an alpha character (a-z or A-Z), up to 16 characters in length, is allowed. No wildcard
characters such as \#+$%*/- or _ (underscore) are allowed.
NOTE: The default (LOCAL) Domain 1 Domain Name is FoxSCADA. It is recommended
that (LOCAL) Domain 1 Domain Name be set to the default value.
Step 5 Enter the (LOCAL) Domain 1 Dom. Nbr (Domain Number).
Details: The valid range is 1 to 32. Each Domain Number entry must be unique.
NOTE: The default LOCAL) Domain 1 Dom. Nbr is 1. It is recommended that the (LOCAL)
Domain1 Dom Nbr be set to the default value.
Step 6 Click on Config Stations button (located at the top right of the display to the right of the
Dom. Nbr column label).
Result: Units & Station Names window opens.

SCADA Station Type
Figure 6-4 Units & Station Names window
Step 7 Enter the unit number, host name and alternative name of each of the stations containing
events within the system, starting with the station on which the current installation is being
done. Events stations are all server, engineering and operator stations within the same
domain.
Details: The unit number must be a unique number between 1 and 64.
Step 8 Click on the Apply Units button in the bottom left of the window.
Result: The Finish button becomes available.
Step 9 Click on the Finish button at the bottom of the window.
Result: The Units & Station Names closes and the user is returned to the HMI Domain
Names window.
Step 10 Click on Config Stations button (located at the right of the (LOCAL) Domain 1 Dom Nbr
field).
Result: The Scada Server Entries for dom_1 window opens.

SCADA Station Type
Figure 6-5 Scada Server Entries for Dom_1 window
Step 11 Fill in the station names for the local domain. The order of stations entered determines
the priority of the station to which the HMI connects in the event of failure. Then select the
Apply button.
NOTE: The Stations must contain a SCADA database. If more than one server is selected,
then these stations will be accessible for viewing from HMI. If only one (localhost) is
selected, then only this station HMI will be accessible.
Step 12 Click the Apply button in the bottom of the window.
Result: The default port number of 49494 will be defined in the port number field for all
entered stations. Enter a new port number if different from the predefined default value.
Errors: Checking (ping command) is used to determine if the servers configured exist on
the network. If a server is not ping-able from the current station, it cannot be configured
as a server. Configuration of these stations must be done either by hand editing
configuration files or re-installation when the servers become available. Refer to the HMI
Engineer’s Manual for further information.

SCADA Station Type
Step 13 Click on the Finish button at the bottom right of the window.
Result: The Server Entries for Dom_1 window is closed and the user is returned to the
HMI Domain Names window.
Step 14 If required, configure any Remote Domains.
CONFIGURING REMOTE DOMAINS
Step 15 In the HMI Domain Names window, enter the (REMOTE) Domain name.
Details: Any name containing alphanumeric characters (a-z, A-Z and 0-9), beginning with
an alpha character (a-z or A-Z), up to 16 characters in length, is allowed. No wildcard
characters such as \#+$%*/- or _ (underscore) are allowed.
Step 16 Enter the (REMOTE) Domain Dom. Nbr (Domain Number).
Details: Valid range is 1 to 32. Each Domain Number entry must be unique.
Step 17 Click the corresponding Config Servers button.
Result: The Server entries for dom_x window opens up.
Figure 6-6 Server Entries for dom_2 window

SCADA Station Type
Step 18 Enter Server names for Domain x. The order of stations entered determines the priority of
the station to which the HMI connects in the event of failure.
Step 19 Click the Apply button in the bottom of the window.
Result: The default port number of 49494 will be defined in the port number field for all
entered stations. Enter a new port number if different from the predefined default value.
Errors: A check (ping command) is done that the servers exist on the network. If the
servers do not exist on the network or are not able to be pinged from the current station,
they cannot be configured as servers.
Step 20 Click the Finish button at the bottom right of the window.
Result: The Server Entries for Dom_x window is closed and the user is returned to the
HMI Domain Names window.
Step 21 Repeat steps for all remote domains (up to 32)
Step 22 Click the Apply Domain button.
Step 23 If the user has finished configuring Domains, click the Finish button.
Result: The HMI Domain Names window is closed and the user is returned to the Install
window.

Installation Guide on Solaris (SY-5005013) Chapter 7: Configuring the Packages
for Installation
7 CONFIGURING THE PACKAGES FOR

INSTALLATION
OVERVIEW
This section describes the procedure for the configuration of the SCADA packages for installation.
Configuration of the SCADA packages for installation requires that the user:
 Select the HMI Locale setting.
 Choose the Installation Type and Select Packages for Installation.
 Import the configuration settings (If desired).
 Save the configuration settings (If desired).
 Install now.
7.1 HMI Locale

PROCEDURE
Step 1 Click on the Locale Settings button.
Result: The Locale Settings window is displayed.
Figure 7-1 Locale Settings window
Step 2 Select the desired Locale.

Details: Only the English, Chinese and Korean locales are supported by the HMI.
Details: The default locale setting “C” is for the English locale.
Result: The Locale Settings window is closed and the user is returned to the Install
window.
7.2 Installation Type

PROCEDURE
Step 1 Select Full or Partial Installation as Full or Partial.
for Installation
Details: All the options listed under Options for Installation are selected automatically for a
Full Installation i.e. Install Versant, Install SCADA and Install Full Graphics.
NOTE: Installation of Versant package deletes all databases.
A Partial Installation allows the user to selectively install SCADA packages.
7.3 Importing Configuration Settings

PROCEDURE
Step 1 Enter the Location of Install packages.
NOTE: This is the location of the installation media. The default location is the CD-ROM.
The install script was started from. e.g. /cdrom/cdrom0 .
Step 2 Enter the Location of the REGISTRY_OS file.
NOTE: If a REGISTRY_OS file already exists, the user can import the existing file by
clicking the Import REGISTRY_OS file button.
7.4 Saving Configuration Settings

PROCEDURE
Step 1 The user has the option to save the installation settings.
If the installation settings are: then:

to be saved • Proceed to next step.
not to be saved • Proceed to next section.

Result: The Export Setup File window is displayed.
Figure 7-2 Export Setup File window
Step 3 Enter the directory location where the setup file will be saved.
NOTE: By default, the directory location of the saved setup file is
/opt/custom/upgrade/REGISTRY_OS.
Result: A Message window is displayed prompting the user to confirm the entered
directory location of the setup file.

for Installation
Figure 7-3 Settings Saved confirmation Message window
Step 5 Respond to the Message window Prompt
If the entered directory location is to be: then:

Accepted • Click the OK button.
Rejected • Click the Cancel button.
• Return to the Export Setup File
window to enter another directory
location for the setup file.
Result: The Export Setup File window is closed and the user is returned to the Install
window.
7.5 Install now

OVERVIEW
In this section, the physical SCADA installation occurs. Up to this point, it has all been configuration of
the system characteristics and SCADA packages for installation. The final step is to install the
software with the configured system characteristics.
PROCEDURE
Step 1 Click the Install Now button.
Result: The Intelligent SCADA software installation commences.
The Status section at the bottom of the Install window informs the user of what is
currently being installed.
Step 2 If a versant database exists and "Install Versant" has been selected, then a warning
message is displayed prompting the user to confirm.
Figure 7-4 Install Versant Window

SCADA System
If Cancel is selected, "Install Versant" is unselected and the rest of the installation
continues.
Step 3 A Message window is displayed on completion of the installation.
Step 4 The user is prompted that in order to complete the installation, the system will need to be
rebooted. Respond to the message.
Figure 7-5 Installation Complete Window
If the system is to be then:

rebooted:
Now • Click the OK button.
Result: The system is rebooted and the final installation
phase is completed.
Later • Click the Cancel button.
Result: The user exits the Install window and the installation
script and returns to the UNIX terminal window.
In order to finalise the installation, the user must run:
/opt/fg/bin/lnastart at a later stage.
Step 5 The Intelligent SCADA software installation is complete and the software is ready for use.

8 POST INSTALLATION PROCEDURES
8.1 Creating a History Database

WHEN TO CREATE
To collect the SCADA history data, create a history database skeleton on completion of the
installation.
CONDITIONS
 The real-time database should not be running whilst creating a history database.
 Only one history database can be created for each station.
 The history database that is created by default is subdisthist. This name can be altered.
 History data is collected from the online real-time database.
DETERMINING DATABASE SIZE

A guide for approximating the History database size is given by the following formula:
History size = (value x no. points x change rate x history time span) + 25%
where:
value is equivalent to 16 bytes.
change rate is the rate at which a point changes during a given time frame.
history time is the length of time history is required.
25% is added as a precaution.
Realistic values, change rates and time frames should be chosen as large volumes of disk space are
readily filled with history data.
PROCESS
On creation of a new history database, any existing history database (named subdisthist) is deleted
and a skeleton history database of the desired size is created.
TIME AND SPACE

This process takes approximately 10 minutes for each 100MB of disk space required for the file.
The history database also requires double the amount of free disk space on the disk partition where
VERSANT was installed.
PROCEDURE
To create a history database:
Step 1 Log on to the Intelligent SCADA System as an engineer.
Step 2 Access a xterm window.
Step 3 Type the command
newhistorydb <RETURN>
Step 4 Enter the desired database size in megabytes.
NOTE: The default database size is 2047 megabytes.
Result: The history database is created.

8.2 Archive Medium Interface

WHEN TO CREATE
To collect the SCADA history data and event archive, a history and event archive medium interface
script file must be customised on completion of the installation. The shell script presents a uniform
interface to the history and event subsystem, which can then be translated into the specific driver
commands for a specific installation.
The recommended DVD-RAM driver software for Solaris is UDF Master. UDF Master is produced by
K-PAR Archiving Software. For information and sales, refer to the K-PAR Archive Software web site:
www.k-par.com
UDF Master supports a large range of hardware devices. Foxboro recommends SCSI DVD-RAM
drives made by Panasonic/Matshita compatible with the LF-D200 model drive (model numbers may
vary in different regions). For information and sales, refer to the Panasonic web site:
www.panasonic.com.
Foxboro have validated correct operation of archive functionality using UDF Master v2.00 with a
Panasonic LF-D291NS DVD-RAM drive.
The supplied script maintains compatibility with the previously recommended DVD driver, BakBone
MagnaVault Software.
NOTE: BakBone was TracerTech, visit www.bakbone.com for further information.
Contact Foxboro for further information on other supported drive types.
PURPOSE OF THIS PROCEDURE

The optical drive command interface is implemented in the /opt/scada/bin/opticalcmds.sh script which
can select between different optical drives determined by the OPTICALDRIVE environment variable.
Other application processes can also use this interface to perform optical disk commands.
The opticalcmds.sh script performs all translations from logical to physical device identifiers and
device driver function calls. The script should be reviewed for compatibility with the driver software and
hardware to be used.
PROCEDURE
Install archive media drive and driver software.
Set the OPTICALDRIVE variable in the /opt/scada/bin/histproc script to select the appropriate driver
commands for the optical disk to be used. i.e. KPAR_DVDRAM for the K-PAR Archiving Software
driver.
It may be necessary to change the raw device identifier. The installation may be different from the
released defaults for the drive selection. These settings are in the "translateDrive()" function at the
beginning of the "opticalcmds.sh" shell script. If the appropriate device id is not known, the dmesg
output for the appropriate driver should be studied. Contact Foxboro for further information, if
necessary.
Experience with the DVD Ram drive shows that different raw device identifiers are used. The script
default is /dev/gd/c1t5l0s2 while the validation test setup used /dev/rgd/c0t2l0s2.
When using UDFmaster driver with the DVD Ram drive, it is necessary to run the UDFmounter script
before issuing any optical commands through history. This script starts the 'daemon' process to work
with the existing opticalcmds.sh script and new KPAR UDFmaster driver.
This script must be run manually after each reboot from the UNIX prompt in two steps:
1. Login as root.
2. Run: /opt/scada/bin/UDFmounter start &
To stop the daemon, run: /opt/scada/bin/UDFmounter stop

Test satisfactory operations of the archive media manually from a UNIX window. Follow these steps
as engineer. Note that the script commands are described in the script header. The optical disk mount
point is automatically created by the script the first time the disk is mounted.
Set the OPTICALDRIVE environment variable for the UNIX window shell.
e.g. export OPTICALDRIVE= KPAR_DVDRAM
If a formatted disk is not available, perform a new file system command on a new disk.
e.g. opticalcmds newfs 0 test
Attempt a mount of the disk in drive.
e.g. opticalcmds mt 0
Perform an ls on the optical disk mount directory.
e.g. ls -l /optical0
Result: At least 2 files should be listed. These are lost_and_found and label.
Check if other files on the optical disk can be copied and deleted.
8.3 Printer Administration and Server Software

.
Printer Configuration in Solaris 10
To add a printer using the Solaris Print Manager (SPM), login as root user and execute the following
command.
# /usr/sbin/printmgr &.
When the print manager starts, the user is presented with a dialog box as shown below.
Click OK to continue.
Printer configuration under Solaris 10 can be done in one of following ways.
1. Add access to Printer( Print Client)

2. New attached Printer ( Local Printer)
3. New Network printer ( Print Server)

Configuring (Print Client) Add Access to Printer:
If the user wants to access the network printer through a printer server, select Add access to Printer.
When the user selects this option from the Printer menu, the following dialog box is displayed.
Here, the user has to enter the following data.

1. Printer Name: Enter the printer name (e.g.; LP1)
2. Printer Server: The Name of the Server on which the “Print Server” is configured.
3. Description: Enter the description of the Printer.

Configuring (Local Printer) New Attached Printer:
If the printer is a local printer, connected locally to the system, select New attached Printer.
When the user selects this option from the Printer menu, the following dialog box is displayed.
The user has to enter all the required data for configuring the printer.
1. Printer Name: Enter the printer name

2. Printer Server: Enter the system name
3. Description: Enter the description
4. Printer Port: For parallel port printer(/dev/lp1 to be entered)
5. Printer Make: Enter the printer make (e.g.; HP/Epsilon etc.)
6. Printer Model: Enter the printer model
7. Printer Driver: Select default(Foomatic/hpijs(recommended))
8. Fault Notification: Select default( Write to Superuser)
9. Options: Select the check box, if the printer is default printer.

10. Banner: From the drop down list, select “ Never Print Banner”
11. Click Apply or OK to complete the printer configuration

Configuring Network Printer (Print Server):
To configure the print server, select New Network Printer from the Printer menu. When New Network
Printer is selected, the following dialog box is displayed; where in all the data concerned to the printer
should be entered.
The user has to enter all the required data for configuring the printer.
1. Printer Name: Enter the printer name

2. Printer Server: Enter the system name
3. Description: Enter the description of the printer
4. Printer make: Enter the printer make (e.g.; HP/Epsilon etc.)
5. Printer Model: Enter the printer model
6. Printer Driver: Select default(Foomatic/hpijs(recommended))
7. Fault Notification: Select default( Write to Superuser)
8. Destination: Is usually the IP address of the printer to be configured. Instead of entering
IP address, user can enter the printer name, and make sure that the printer name exists
in the /etc/hosts file.
9. Protocol: Select the default Protocol (BSD).
10. Options: Select the check box, if the printer is default Printer.
11. Banner: From the drop down list, select “ Never Print Banner”
12. Click Apply or OK to complete the printer configuration
8.4 NTP Configuration

DESCRIPTION
The Network Time Protocol (NTP) utility is provided as part of the Solaris 10 Operating System. NTP,
which is a distributed hierarchical client-server protocol, manages time synchronization between a
station and an NTP compatible time source on the network (such as another station or a GPS).
The iSCADA System time is based on Universal Coordinated Time (UTC). The user is presented with
local time, which is UTC plus the local time zone information. Conversion is handled in time
presentation and time entry. Therefore, it is possible for stations in the system to be located in different
time zones. For system configurations that possess multiple stations (such as a system comprising
servers and HMI stations), the user must configure a time synchronization methodology for each
station, including any HMI only stations. All stations within a system must be in time synchronization to
ensure the operational integrity of the system is maintained.
The different time synchronization methodologies available for the master station include NTP to GPS
or another station, CLS to FEP or RTU to FEP. See document number SY-5005415, I/A Series
Intelligent SCADA System - Functional Specification for the Master Station, for more information on
the various time synchronization options available. It is important that each station only have one type
of time synchronization configured.
8.5 Tcp to Serial Interface

WHEN TO CREATE
The tcp to Serial program allows the FEP to communicate over the Sun serial ports. Currently, FEP
can only communicate over TCP/IP. The tcpToSerial process operates as a TCP/IP server that binds
a TCP/IP socket to a local serial port.
WHAT SCRIPT DOES

There are three programs associated with tcpToSerial:
1. tcpToSerial
This is the TCP/IP server itself. tcpToSerial executable resides in /opt/scada/bin. It is not directly
started by the engineer. Instead, the tcp2serial script is used.
2. tcp2serial
This is a shell script used to initiate a tcpToSerial process on each serial port. This script is run
automatically when the machine is restarted (i.e. a machine reboot, not a database process restart).
This program can be used to restart the tcpToSerial processes, if they have ceased to operate. This
script is located in /opt/scada/auto_start.
3. stopTcp
A shell script used by the engineer to shutdown any operating tcpToSerial processes. This script is
located in: /opt/scada/bin.
TCP CHANNEL CONFIGURATION
The development database TCP/IP channel parameters must be configured in order to connect to the
tcpToSerial process. These parameters are: “Connect to Server on Host” and “at port”.
“Connect to Server on Host” is the LAN connection name for the TCP/IP connection. The name must
also be in the /etc/hosts file with the IP address. For Sun workstation RS232 serial ports, the name of
the FEP station is used (this is the same as the LAN connection name).
“at Port” is the port number for the TCP/IP connection. For Sun workstation RS232 serial ports, the
port numbers are normally 2008 for Port A, and 2009 for Port B.
Refer to SY-5005003 I/A Series Intelligent SCADA System - Database Configurator User’s Manual for
more information on configuring the development database parameters.
TCP2SERIAL FILE CONFIGURATION VARIABLES
The tcp2serial shell script file contains a number of parameters that need to be configured for each
machine’s hardware profile.
The configurable parameters are:
SERIAL_PORT_A and SERIAL_PORT_B - The names of machine’s serial port A and B devices,
respectively. By default, these are set to /dev/cua/a and /dev/cua/b respectively. It should not be
necessary to change the names of the serial port devices unless there are other ports apart from the
standard A and B. e.g. a multi-port serial board.
TCP_PORT_A=2008 and TCP_PORT_B=2009 - The respective TCP/IP port numbers for serial ports
A and B. It should not be necessary to change the default TCP/IP port numbers, unless there are
other servers operating on the default ports.
PORT_A_BAUD=9600 and PORT_B_BAUD=9600 - The baud speed of serial port A and B
respectively. The default is 9600 baud. Any other standard speed may also be used.
ENABLE_PORT_A=YES and ENABLE_PORT_B=NO - The serial port enable flags for ports A and B
respectively. The appropriate Enable flag should be set to "YES" for each serial port that is to be used
by TcpToSerial. By default only port A is enabled.
SERIAL PORT PERMISSIONS

Serial ports should be set with chmod 666 permissions to allow read and write by all users. The
tcp2serial startup script attempts to do this, but may not have permission (the port devices are usually
owned by root in the default Solaris operating system installation). The script checks the permissions,
and TcpToSerial runs only if the permissions are valid. If permissions are incorrect, a message is
written to the log file (see tracing below for location of this file), and also the console.
TROUBLESHOOTING
Tracing is disabled by default. Tracing may be enabled to log the data transmitted and received over
both the serial ports A and B. It is not possible to enable tracing to serial ports A and B independently.
Tracing is enabled by setting the ENABLE_TRACING parameter in the tcp2serial file to YES.
The trace output is placed in two trace log files for ports A and B, respectively,
PORT_A_LOGFILE=$SCADA_HOME/log/tcp2serial_a.log and
PORT_B_LOGFILE=$SCADA_HOME/log/tcp2serial_b.log.
NOTE: The $SCADA_HOME default setting is /opt/scada.

The log files can be viewed continuously as data is being written to them, by using standard UNIX
prompt command: tail -f /opt/scada/log/tcp2serial_a.log.
The trace log file output contains the file descriptor of the serial port (or an error if it could not open the
serial port), and displays the file descriptor of any connections made to the tcp port. The tracing output
also indicates when tcpToSerial receives a connection from FEP. If this message is not displayed, the
user should check the channel configuration and confirm that the database has been started with
Telemetry.
WARNING: As all data sent and received by the serial port is logged, tracing should only be enabled for
the time period that debugging is required. If tracing is left enabled for an extended period of time, as
there are no restrictions on log file size, the tracing log file will grow abnormally large and has the
potential to grow until all hard disk space is consumed.
8.6 Application Management

Applications are software components that augment the basic functionality of the iSCADA System.
Application programs are made known to the iSCADA System via the following file directories:
Directory Description
Contains all the script files for applications that are managed by
apps/progs
the applications management.
Contains soft links to the apps/progs directory for the applications

apps/auto_start/before
that must be started before starting iSCADA.
Contains soft links to the apps/progs directory for the applications

apps/auto_start/after
that must be started after starting iSCADA.
Contains the scripts moved from apps/progs directory (by

applications management) for applications that have failed to start
within the grace period.
apps/failed
These scripts are not available for automatic restart or manual
start. Manual intervention by the Engineer is necessary to move
the failed script from “apps/failed” back to “apps/progs”.
Used to store the log files for recording the log output of each
application under applications management. Each log file is
apps/log
named with a suffix denoting the associated real-time database
name.
SCRIPT FILES FOR APPLICATIONS

A shell script for starting and stopping each application process must be placed in directory
/opt/scada/apps/progs. The file mode must be set to read+execute for all users. Information on how to
write the script is provided in the file /opt/scada/apps/sampleScript.
AUTO START
This section is only applicable for applications that are to be automatically started.
Start process before starting iSCADA
If the application is to be automatically started before starting iSCADA, then the directory
/opt/scada/apps/auto_start/before must contain a soft link to the script in /opt/scada/apps/progs. The
link is created using the following commands:
cd /opt/scada/apps/auto_start/before
ln –s /opt/scada/apps/progs/myApplication myApplication
Where myApplication is the application file name.
Start process after starting iSCADA
If the application is to be automatically started after starting iSCADA, then the directory
/opt/scada/apps/auto_start/after must contain a soft link to the script in /opt/scada/apps/progs. The link
is created using the following commands:
cd /opt/scada/apps/auto_start/after
ln –s /opt/scada/apps/progs/myApplication myApplication
Where myApplication is the application file name.
The delay period (seconds) to when processes are started is specified by the following environment
variable defined in /opt/scada/bin/dbproc:
export APPS_AUTO_START_DELAY=90

Installation Guide on Solaris (SY-5005013) Chapter 9: Product Licenses
9 PRODUCT LICENSES
INTRODUCTION
The Master Station software requires valid electronic licenses to operate. The different components
that can be licensed are listed in PSS 21S-2M1 B3 - I/A Series Intelligent SCADA - SCADA Platform
Product Specifications Sheet.
9.1 Scada License

The user must obtain a permanent license from Foxboro for all Master Station Software. Only once a
permanent license is obtained, can the different components of the product be run on the station.
PROCEDURE
Step 1 Login as root user.
Step 2 Open a console/terminal prompt.
Step 3 Run the license information file.
./opt/scada/bin/licinfo
Result: The machine’s hostname, hostid and ipaddress are output to the screen.
Step 4 Copy this information, clearly indicate the corresponding PSS Part Number required for
this machine and the Purchase Order Number and send it to Foxboro.
Step 5 Foxboro will supply a file for the machine of the format iaSCADA_license.<hostname>,
where <hostname> is the name of the machine the file should be copied to.
Step 6 Copy the iaSCADA_license.<hostname> file to the /etc directory, ensuring that the
resulting file permissions are readable by all users.
chmod 644 iaSCADA_license.<hostname>
Step 7 ./opt/scada/bin/activationkey <activaton key number>
The machine is now licensed to run the applicable Master Station software components.
9.2 Versant License

The user must obtain a permanent license from Foxboro for Versant. Only once a permanent license
is obtained, can a database be run on the station. The information sent to obtain a Scada License is
also used to generate the Versant License.
PROCEDURE
Step 1 Login as engineer user.
Step 2 Open a UNIX prompt.
Step 3 Copy the provided license.xml for the machine to the /opt/versant/vod7010 directory.
Step 4 Change the ownership permissions of the file to engineer:LN2068 and the executable
permissions to readable by all users, as follows:
chmod 644 license.xml
chown engineer:LN2068
Step 5 The machine is now licensed to run Versant databases.
For further information on Versant Licensing, refer to the Versant User Manuals.

Installation Guide on Solaris (SY-5005013) Chapter 10: Advanced Configuration
10 ADVANCED CONFIGURATION
CONTENTS
This section describes information that the user should read for advanced configuration of the
Intelligent SCADA software.
10.1 Overview and Recommendations

SYSTEM BACKUP
Prior to any changes to the configuration, backup or archive the existing system, files and directories.
For users with an existing system, it is advisable to perform a system backup prior to installing the
Intelligent SCADA software or upgrading the existing Intelligent SCADA System. It is important to do
this step, as the configuration process overwrites the existing configuration files. Consequently, some
files may be inadvertently deleted.
SUPERUSER LOGON
The Intelligent SCADA advanced configuration procedures requires the system administrator to be
logged on to the system as superuser.
To ensure that the superuser has the necessary execution path for the configuration, type the
following command on a command line:
PATH=/usr/sbin:/usr/bin:$PATH;export PATH <RETURN>
No one should be logged on to the machine during the installation procedure, except the superuser.
CAUTION
Ensure that there are no other processes operating while installing the Intelligent SCADA System.
10.2 Database Conversion
A new version of the Versant OODBMS is employed in release 8.x and 9.0 .For system upgrades, it
is necessary to migrate the existing databases to the new version of Versant. For details on the
procedure for migrating databases from previous releases, contact SCADA Product Support
(email:Support@ips.invensys.com).
10.3 Event Subsystem Optimisation

PROBLEM
The event subsystem is optimised for an expected maximum of 10,000 events per day. For systems
with higher numbers of events per day, it is recommended that the event manager startup options be
changed.
SYMPTOM
The event manager process will consume excessive amounts of CPU. Stopping and starting the event
manager will not make the problem go away. The only way to stop it temporarily is to re-initialise the
event manager by the eventinit command.
SOLUTION
The events list file size can be re-configured. It limits on both file size and timeframe. These options
Installation Guide on Solaris (SY-5005013) Chapter 10: Advanced Configuration
are added to the startup script for the eventmgr in the /opt/fg/progs/eventmgr.
Usage: eventmgr [-N<num>] [-T<sec>] [-S<num>] [-I<num>] [-H<num>] [-C<num>]
Options:
-N allow a maximum of <num> non-archive event files, default 8 (e.g. 8 days).
-T set event file maximum period to <sec> seconds, default 86400 (1 day).
-S set event file maximum size to <num> events, default 100000.
-I set event file size increment to <num> events, default 10000.
-H set holding buffer size (the memory buffer used before flushing events to disc) to <num>
events, default 1000.
-C set event cache size (the memory buffer used to hold the current event file) to <num>
events, default 110000 (typically S + I).
For example, for 1 week (7 * 24) of hourly files containing a maximum of 5000 events each:
eventmgr -N 168 -T 3600 -S 5000
WARNING:
1. All stations must have the same parameters.
2. Re-initialising the event manager by the eventinit command erases all events.
3. It is not recommended to use continuous list mode. In Continuous List mode, the system
memory usage and CPU load may be impacted depending on the total number of online
event file records.
NOTE: The Event List display can be selected to treat the online event files as one continuous list,
by pressing the 0 button. The startup file defines which mode the Event List is in when it is
invoked. The default is Current File mode.
10.4 Large Distributed History Database Creation

It is possible to create large history databases using the addvol feature of Versant. At this stage, the
newhistorydb setup script does not employ the technique. The history database name should be kept
as subdisthist.
This operation requires knowledge of Versant and would only be attempted by a suitably trained
engineer.
PROCEDURE
To create a large history database, perform the following steps as engineer:
Step 1 Create database directory:
makedb -g subdisthist
Step 2 Change profile settings as required
Step 3 Change directory to the $VERSANT_DB/subdisthist directory
Step 4 Edit the profile.be file and change the sysvol setting to 1024M (recommended size), also
review and potentially edit the volume count (refer Versant documentation) based on the
expected storage requirements of the database.
Step 5 Create database:
createdb subdisthist
Step 6 Set database for public access:
dbuser -add -P subdisthist
Step 7 Import schemas to database:

sch2db -y -D subdisthist /opt/scada/lib/histdb_sch/*.sch

Step 8 Initialise extension volumes:
addvol -n volName -p volPath -s volSize subdisthist
e.g. addvol -n vol1 -p /bigvol/databases/subdisthist.vol1 -s 1024M subdisthist
NOTE:
1. Extension volumes can be specified by full path. The path must already exist. It does not
need to be in the default versant database subdirectory (but it is recommended that it
is).
2. The volume name is arbitrary.
3. The specified options create the file framework for the database extension. A -i option
can be used to reserve the maximum file space to be allocated to the file at creation
time.
Step 9 Run historydbskeleton to instance the root and storage block objects in the history
database. The historydbskeleton utility supports 2 parameter protocols for activation.
Either the history database size in Mbytes, or the number of fixed blocks and the block
size can be specified.
Method 1: When the database size is specified, historydbskeleton selects the block size
according to the following simple rules, and creates blocks for 80% of the specified size.
The other 20% is reserved for variable size blocks.
1024 bytes for <= 50Mb
4096 bytes for <= 500Mb
16312 bytes for > 500Mb
In this case, the historydbskeleton activation is as follows:
historydbskeleton databaseName domainName databaseSize
where:
databaseName is the history database name (typically subdisthist).
domainName is the domain name (typically ".") This is important for long path
creation.
databaseSize is the size in Mbytes.
e.g. historydbskeleton subdisthist . 500
Method 2: When the number of blocks and block size are specified, the specified
numbers of blocks are generated, and 20% extra space is reserved for variable size
blocks. The activation command is:
historydbskeleton databaseName domainName blockCount blockSize
e.g. historydbskeleton subdisthist . 100000 16312
For large history databases, the recommended fixed block size is 16312 bytes, this being
determined experimentally as the most efficient usage of space for the Versant persistent
object management.

Installation Guide on Solaris (SY-5005013) Chapter 11: Troubleshooting
11 TROUBLESHOOTING
CONTENTS
This section comprises of information that helps the users to assist with the troubleshooting of the
initial setup and configuration of the Intelligent SCADA software.
11.1 Auto-Installer GUI
11.1.1 Log files

The results of the installation are stored in the /opt/custom/upgrade/install.log file. It is possible to
monitor the progress of an install by viewing the contents of this log file at the UNIX prompt using the
tail -f opt/custom/upgrade/install.log command.
The results of Examine and Export scripts are stored in the /opt/custom/upgrade directory.
11.1.2 Known Limitations

This section consists of information that helps the users to assist with the troubleshooting of the Auto-
Installer GUI.
Table 11-1 Known Auto-Installer GUI Limitations
Problem Description Resolution

Cannot eject the CD-ROM. It is not possible to eject the CD-ROM whilst you (or any other
(Device Busy message may be user) are located in any of the CD-ROM directories.
displayed.) Change directories to a directory location outside the CD-ROM
and attempt to eject the CD-ROM again.
In addition, under some circumstances the eject command will

not eject the CD-ROM, if the file manager window launched by
the automount demon is still open.
Installation from file or from CD- The auto-installer GUI is able to install from either a file system
ROM mounted at different points or from a CD-ROM mounted at different points in the file
in the file system system. However, it determines the media type by searching
for the string 'cdrom' in the path passed to the install.tcl shell
script.
Shared CD-ROM installation. It is possible to install the software from a shared CD-ROM.
- To mount the first disk as a shared CD-ROM, stop, and then
restart the NFS server on the machine in which the CD-ROM is
inserted. Then, stop and restart the NFS clients on the
machines on which the install is being performed, and which
'see' the shared CD-ROM.
/cdrom directory does not contain There have been instances where the physical directory under
the installation CD-ROM /cdrom has not been removed when the CD-ROM is ejected.
Why the Solaris operating system vold process does not clean
this is presently unknown, and these directories should be
manually deleted if this occurs.
Inserting the CD-ROM When prompted to insert the CD-ROM, please ensure the tray
is closed before clicking OK on the dialog box. This ensures
that the CD-ROM has time to be mounted and, when the
search occurs for the packages they will be located.
NOTE: The installer does not "retry". In some instances, the
installer may be left in a state in which the buttons are inactive
even though the CD-ROM will now be mounted in the correct

location.
Full Graphics Installation fails due Checking (ping command) is used to determine if the servers
to servers not being connected to configured exist on the network. If a server is not ping-able
the station being installed. (ie. do from the current station, it cannot be configured as a server.
not respond to the UNIX ping Configuration of these stations must be done either by hand
command) editing configuration files or re-installation when the servers
become available. Refer to the HMI Engineer’s Manual for
further information.
11.2 Time Zones with Daylight Savings Changes

DESCRIPTION
In the I/A Series® SCADA system, all RTU, CLS and GPS devices utilize UTC time (Coordinated
Universal Time) in all time transactions. The Master Station utilizes both local and UTC time
depending on the function performed. Local time is used when presenting data to the SCADA System
user at the HMI (Human Machine Interface) on the Master Station.
If you do not change your I/A Series® SCADA system clocks to reflect changes in Daylight Savings or
Summer Time, you do not need to be concerned.
PROBLEMS
HMI applications like SAMMI™ running on Solaris® stations and the Windows NT® base platforms do
not handle time changes correctly. The most noticeable symptom is a lack of on-screen updates to the
time displayed on formats within these applications for a period equalling the length of time that the
clocks were set back. A refresh of the format, including purging of any cached in memory, will correct
the problem of a frozen clock. A re-start of the SAMMI™ application will also correct the problem.
Other confusing symptoms are trend displays and system lists (event, alarm, off normal lists) with a
time period of one hour repeated twice, which corresponds to the repeated local time hour when the
clocks are set back, or a gap in the data displayed equal to one hour, which corresponds to the
missing local time when the clocks move forward.
The Master Station scanning subsystem has been tested extensively on a number of different
architectures and protocols, for both entry and exit from Daylight Savings Time, without any problems
observed. However, if systems experience problems with scanning scheduling of remote devices from
the Master Station after a time change, taking the remote device out-of-scan and then returning the
device in-scan will correct the scanning to the device.
Users in time zones where the Daylight Savings Time change occurs at midnight local time (i.e. South
American time zones) will experience problems when the time jumps forward (i.e. midnight does not
exist in local time). The SCADA database abnormally terminates at 23:00:01 local time, one hour prior
to the Daylight Savings Time or Summer Time, time change forward is to occur, and the database will
not successfully restart until one hour later, after the time change has occurred at the new 01:00:00
local time. To work around the problem, it is recommended that the affected users edit the Solaris®
time zone file to ensure the time change does not occur at 12am (midnight) local time. It is
recommended that the time change occurs at 1 or 2 am local time.

Installation Guide On Solaris: I/A Series Intelligent SCADA System

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Installation Guide On Solaris: I/A Series Intelligent SCADA System

Uploaded by

Copyright:

Available Formats

Installation Guide on Solaris (SY-5005013)

Document ID: SY-5005013 Revision: 1.21

Invensys Process Systems Pty Ltd The Foxboro Company

Checked by & Date: Approved by & Date:

DOCUMENT REVISION HISTORY:

Rev. Date Comments Prepared By

© Invensys Process Systems Pty. Ltd. 2001-2009

I/A Series Intelligent SCADA System Page 2 of 50

5 Installing the Intelligent SCADA System ................................................................................ 20

7 Configuring the Packages for Installation .............................................................................. 31

I/A Series Intelligent SCADA System Page 3 of 50

I/A Series Intelligent SCADA System Page 4 of 50

ABOUT THE USERS

Syntax Example Comments

bold Warning Information that the user should take

I/A Series Intelligent SCADA System Page 5 of 50

1.2 Contents of the Intelligent SCADA Package

1.3 System Requirements

PHYSICAL MEMORY REQUIREMENTS

I/A Series Intelligent SCADA System Page 6 of 50

Table 1-1 Memory requirements for the Intelligent SCADA software

Software Memory Requirement

Table 1-2 Disk space requirements for the Sun workstations

Software Disk Space

Table 1-3 Recommended 20GB disk partitioning (for a small system)

Partition Physical Size

I/A Series Intelligent SCADA System Page 7 of 50

Table 1-4 Recommended 40+ GB disk partitioning

Partition Physical Size

1.4 Information Requirements

INTELLIGENT SCADA USERS

Table 1-5 System Directory Structure

Slice File System Purpose

1.5 Task Sequence

THE TASK SEQUENCE CAN BE USED:

I/A Series Intelligent SCADA System Page 9 of 50

Step Action Details x/√

Table 1-7 Upgrading the Intelligent SCADA Software on an Existing System

Step Action Details x/√

I/A Series Intelligent SCADA System Page 10 of 50

3 Install the Intelligent SCADA • Select the Upgrade option.

I/A Series Intelligent SCADA System Page 11 of 50

2 BEFORE INSTALLING THE INTELLIGENT

2.1 Overview and Recommendations

I/A Series Intelligent SCADA System Page 12 of 50

2.2 User Setup Prior to Installation

I/A Series Intelligent SCADA System Page 13 of 50

3 INSTALLING THE OPERATING SYSTEM AND

3.1 Installing the Operating System

Name of Installation Window Action or Selection

I/A Series Intelligent SCADA System Page 14 of 50

Primary Network Interface • Select the Network card which you

I/A Series Intelligent SCADA System Page 15 of 50

Select Type of Install • Select Custom Install.

Additional Products • Click the Next button.

Solaris Software Group • Select Entire Group.

I/A Series Intelligent SCADA System Page 16 of 50

Step 5 Create a new sub-directory named config.

I/A Series Intelligent SCADA System Page 17 of 50

4 ACCESSING THE INSTALLATION INTERFACE

If the DISPLAY environment Then:

I/A Series Intelligent SCADA System Page 18 of 50

Figure 4-1 Intelligent SCADA Installation Menu Window