Im Linux

Instruction
Manual
FAST/TOOLS
FAST/TOOLS
Installation Manual Linux

and Unix
IM50C03C01-01EN/9.05
YOKOGAWA
YOKOGAWA ELECTRIC CORPORATION

9-32 Nakacho 2-chome,
Musashino-shi, Tokyo 180-8750, Japan
Tel: +81-422-52-5616
Email:GSC_Sales@ml.jp.yokogawa.com
IM50C03C01-01EN/9.05
Copyright October 2012
YOKOGAWA
Yokogawa Electric Corporation
The information in this document is subject to change without notice and should not
be construed as a commitment by Yokogawa.
Yokogawa assumes no responsibility for any errors that may appear in this
document.
The software described in this document is furnished under license and may only be
used or copied in accordance with the terms of such license.
ii
Table of Contents
Table of Contents
1
Preface ...................................................................................1-1
1.1
Introduction ...............................................................1-1
1.2
Prerequisites ...............................................................1-1
1.3
Supported Unix/Linux platforms ...............................1-1
1.4
Structure of this document .........................................1-1
1.5
Conventions and abbreviations ..................................1-2
FAST/TOOLS basic concepts ..............................................2-1

2.1
Introduction ...............................................................2-1
2.2
FAST/TOOLS configurations ...................................2-1
2.3
The FAST/TOOLS package ......................................2-2
2.4
FAST/TOOLS for Linux and Unix ...........................2-3
2.4.1
2.4.2
2.5
Required Disk Space .................................................2-4

2.5.1
2.5.2
2.5.3
2.5.4
2.5.5
2.6
2.7
Read the Release Notes document ............................ 2-6

FAST/TOOLS installation ........................................ 2-6
Requesting a FAST/TOOLS licence ......................... 2-7
Validating FAST/TOOLS ......................................... 2-7
Setting up you HMI connection ................................ 2-7
Where to get your FAST/TOOLS licence .................2-7
FAST/TOOLS installation ...................................................3-1

3.1
Introduction ...............................................................3-1
3.2
Preparing your system ...............................................3-1
3.2.1
3.2.2
3.3
3.4
3.5
4
Item definition file .................................................... 2-4

Item history files ....................................................... 2-4
Alarms history ........................................................... 2-5
Classes and object ..................................................... 2-5
Reports ...................................................................... 2-6
Required Systemem Memory ....................................2-6

The installation procedure .........................................2-6
2.7.1
2.7.2
2.7.3
2.7.4
2.7.5
2.8
Supported configurations .......................................... 2-3

Supported Unix versions ........................................... 2-4
Create a FAST/TOOLS directory (optional) ............ 3-1

Create a FAST/TOOLS user and group (optional) ... 3-1
Installing FAST/TOOLS ...........................................3-2

Requesting a licence ..................................................3-4
Validating FAST/TOOLS ..........................................3-4
Setting up a HMI connection ...............................................4-1

4.1
Prerequisites ...............................................................4-1
4.1.1
4.2
Firewall configuration ............................................... 4-1
Server configuration ..................................................4-4
FAST/TOOLS Installation Manual Linux and Unix
iii
Table of Contents
4.3
5
HMI configuration .................................................... 4-4
Using FAST/TOOLS ........................................................... 5-1

5.1
Introduction ............................................................... 5-1
5.2
Starting and stopping FAST/TOOLS ........................ 5-1
5.3
Manually starting and stopping ................................. 5-1
5.4
Running FAST/TOOLS as a service ......................... 5-1
5.4.1
5.4.2
5.4.3
5.5
5.6
RedHat Enterprise Linux .......................................... 5-2

Sun Solaris ................................................................ 5-4
IBM AIX ................................................................... 5-4
Clearing FAST/TOOLS Runtime Data ..................... 5-4

Removing FAST/TOOLS ......................................... 5-5
5.6.1
5.6.2
5.6.3
RedHat Enterprise Linux .......................................... 5-5

Sun Solaris ................................................................ 5-6
IBM AIX ................................................................... 5-6
Appendix A:Distributed systems .................................................. A-1

A.1
Introduction .............................................................. A-1
A.2
HMI, Host, Front-end components .......................... A-1
A.3
Interconnecting components .................................... A-2
A.4
Distribution of data sets ........................................... A-3
A.5
Item copy processes ................................................. A-4
A.6
Distributed ALARM/FAST ..................................... A-4
A.7
Distributed Item Interface (GIN DII) ....................... A-5
A.8
Stepwise configuration actions ................................ A-5
iv
Introduction
Preface
1
1.1
Preface
Introduction
This manual describes the procedure for installing FAST/TOOLS on

any of the supported Unix and Linux platforms. It will provide
step-by-step instructions on how to setup, install and licence your
FAST/TOOLS system.
1.2
Prerequisites
It is assumed that you have some basic Unix/Linux system

administration knowledge. You should have a basic understanding of
Unix/Linux file ownership, user accounts, and user groups.
If you are installing FAST/TOOLS on Linux it is assumed that you are
using Redhat Enterprise Linux 6, which is the officially supported Linux
distribution for the current FAST/TOOLS release. If you are using
another Linux distribution, you might need a more detailed knowledge
on how to configure your system.
1.3
Supported Unix/Linux platforms
In FAST/TOOLS release 9.05 the following Unix/Linux platforms are

supported:
1.4
IBM AIX 6.1

Redhat Enterprise Linux 6 (RHEL 6)
Structure of this document
The FAST/TOOLS Installation Manual can be divided into a number of

chapters/appendices.
Chapter 1, Preface, Introduction and Conventions.

Chapter 2, FAST/TOOLS basic concepts, explains the basic
concepts behind the available FAST/TOOLS configurations and
licensing options. This will help you to choose the right
configuration and license for your situation.
Chapter 3, FAST/TOOLS installation, a step by step guide on how
1-1
Preface
Conventions and abbreviations
to install and license FAST/TOOLS.

Chapter 4, Setting up a HMI connection, explains how to setup a
HMI (Human Machine Interface) between your Unix/Linux system
and a FAST/TOOLS HMI station running on Microsoft Windows.
Chapter 5, Using FAST/TOOLS, very brief introduction on how to
start FAST/TOOLS and how FAST/TOOLS can be setup to run as
a service.
In Appendix A, a description is given of the configuration of a
distributed FAST/TOOLS system.
1.5
Conventions and abbreviations
The following conventions may be used in this manual:
1-2
CONVENTION
MEANING
[]
Indicates that the enclosed item is the default.
UPPERCASE
letters
Indicate reserved words and predefined names,

e.g. NULL, TRUE, DUR_NOWAIT.
(I)
Indicates that the specified parameter is input.
(O)
Indicates that the specified parameter is output.
""
Used in format descriptions. Double quotes indicate that the character is to be taken literally.
<name>
Used in format descriptions. <name> indicates a

variable.
file_name
This type-setting is used to indicate file names.
output
This type-setting is used to indicate output on a

terminal.
input
This type-setting is used to indicate input from

the user.
n.u.
not used.
Introduction
FAST/TOOLS basic concepts
2
2.1

Introduction
This chapter introduces some basic FAST/TOOLS concepts you need to

be aware of when setting up your FAST/TOOLS system.
2.2
FAST/TOOLS configurations
A FAST/TOOLS configuration can consist of one single FAST/TOOLS

system or of a number of FAST/TOOLS systems connected to a central
server. A configuration with one FAST/TOOLS system is called a
stand-alone system. A configuration with more than one FAST/TOOLS
systems is called a distributed system.
The individual FAST/TOOLS systems in a distributed configuration are
called the nodes of that system. Each FAST/TOOLS node is given a
unique node-name and node-number when FAST/TOOLS is licenced.
The nodes in a distributed FAST/TOOLS configuration can be assigned
different tasks. There are three types of FAST/TOOLS nodes, they are
called called Server, Front-end and HMI.
- Server
The server is the central system within a distributed
configuration. It contains the configuration and historical
databases.
- Front-end node
A Front-end node takes care of data gathering from attached
equipment (PLC, RTU). In addition some local control is
possible.
- HMI node
A HMI node (Human Machine Interface) is used for system
configuration and he process visualization.
Note: The HMI-node in a FAST/TOOLS configuration is only
available on the Microsoft Windows version of FAST/TOOLS. This
means that a stand-alone Unix configuration consists of a Unix server
and one Microsoft Windows HMI node for system configuration and
process visualization.
2-1
The FAST/TOOLS package
In a distributed configuration all the HMI nodes must be Microsoft

Windows systems. The Server and Front-end nodes can be Unix/Linux
based.
2.3
The FAST/TOOLS package
The FAST/TOOLS software package is divided in a number of

functional components called TOOLS. Each tool provides a part of the
total FAST/TOOLS functionality.
The following table gives a short overview of the different tools and
their function within the FAST/TOOLS package.
Table 1: The FAST/TOOLS collection
Tool name
Description
BUS/FAST
Basic support and communications
DATABASE/ FAST
ISAM based file support

Distributed data set services
HISTORY/FAST
History scheduler
AUDIT/FAST
Audit trailing
ITEM/FAST
Real time item data handling
EQUIPMENT/ FAST
Equipment drivers
ALARM/FAST
Alarm handling
PROCESS/ FAST
Sequences, processing and calculations
REPORT/FAST
Reporting
ACCESS/FAST
Open DataBase Connectivity (ODBC) interface
USER/FAST
FAST/TOOLS User Interface (only available on the

Microsoft Windows) version of FAST/TOOLS
INTEGRATION
Miscellaneous FAST/TOOLS functionality and

placeholder for user applications.
The difference between the three FAST/TOOLS node types (server,

Front-end and HMI) lies in the combination of tools that are installed on
each of these node types.
2-2
FAST/TOOLS for Linux and Unix
The following table lists the tools and in which component they are
found:
Table 2: Tools in relation to the node type
Node type
Tool name
Server
Front-end
HMI
SDK
BUS/FAST
DATABASE/FAST
HISTORY/FAST
AUDIT/FAST
ITEM/FAST
EQUIPMENT/FAST
ALARM/FAST
PROCESS/FAST
REPORT/FAST
ACCESS/FAST
USER/FAST
INTEGRATION
*
*
*
*
The installation of FAST/TOOLS is based upon node types. For

example: When you install the server node you will get the tools as listed
in the Server column in the previous table. Whether or not a certain
tool will be activated is depending on whether or not the tool is licensed.
2.4
FAST/TOOLS for Linux and Unix
This section gives some specific information you need when installing
FAST/TOOLS for Linux/Unix.
2.4.1
Supported configurations
As explained in section 2.2, the FAST/TOOLS HMI node type is only

available on the Microsoft Windows platform. Because FAST/TOOLS
requires the HMI for system configuration each FAST/TOOLS system
will need to include at least one Microsoft Windows as HMI node. Unix
2-3
Required Disk Space
based FAST/TOOLS systems can be used as Server or as Front-end

node.
2.4.2
Supported Unix versions
The supported Unix versions for FAST/TOOLS are listed in section 1.3
of this manual. It is assumed that you are using one of these Unix/Linux
versions.
If you need to install FAST/TOOLS on Linux distribution other than
Redhat Enterprise Linux, you may require some distribution specific
knowledge.
2.5
Required Disk Space
To installing the FAST/TOOLS software you will require about 200

Mbytes of disk space.
While running FAST/TOOLS, additional disk space is required to store
configuration and historical data:
2.5.1
Item definition file
The item definition requires 1800 bytes for each item defined (Server
component only).
Add 350 bytes per item for each system where the Front-end component
is installed.
2.5.2
Item history files
The size of an item history file depends on the type of storage you
choose. This paragraph gives an overview of the commonly uses storage
types. These values should be seen as a rule of thumb. All file size
aspects like key file overhead and bucket slack size are counted in the
sample size values.
Disk compression is not counted.
2-4
Event based collection/event based storage

This storage type is used when you define a storage group of type
Event/Event in the HMI. On average you can expect each sample
Required Disk Space
to take 100 bytes of disk space.
Scan based collection/Time based storage

Scan/Time in the HMI. This storage group has the optional
compression and can be configured to store the items quality code
as well as the value and status. Depending on the choices you make
the following table gives the average disk space each item sample
will take:
Table 3: Disk space required for Scan/Time sample
Use compression
Store quality code
Bytes used per sample
No
No
14
Yes
No
10
No
Yes
18
Yes
Yes
14
Event based collection/Item based storage

Event/Item in the HMI. This storage type is intended to be used for
frequently changing analog values which are time stamped in the
field. Its efficiency increases with the number of samples per file
rollover. Frequently changing analogs with more than 100 events
per file rollover will use on average 30 bytes per sample. Slow
changing signals (less then 10 events per file rollover) will use on
average 100 bytes of disk space per sample.
2.5.3
Alarms history
ALARM/FAST can store events for a period of time. One event costs on
average 550 byte disk space. The number of events and the life time is
completely user-dependent and/or process-dependent.
2.5.4
Classes and object
Each class defined and compiled, typically costs 18 Kbytes of disk space
typical. Each object consumes 2 Kbytes in average.
2-5
2.5.5
Required Systemem Memory
Reports
Each defined report takes about 2 Kbytes. The size of a generated report
is undefined because of the nature of a report definition.
2.6
Required Systemem Memory
The following system memory sizes are advised:

Table 4: Advised memory sizes
Software
Advised
memory size
(Mbytes)
Small stand alone system with Server or Front-end component (up to 2000 items)
512
FAST/TOOLS Server system
2048
Large FAST/TOOLS server system (100.000 items or more)
4096
Note that additional non FAST/TOOLS applications may require

additional memory.
2.7
The installation procedure
This section gives you overview of the FAST/TOOLS installation

procedure. Later in this manual the steps are explained in detail.
2.7.1
Read the Release Notes document
Before you start the installation procedure you should read the Release
Notes document, available on the FAST/TOOLS distribution DVD. It
may contain valuable information and tips.
2.7.2
FAST/TOOLS installation
During the installation, the FAST/TOOLS software package is

transferred to your system. For this step you require the system root
password.
2-6
Where to get your FAST/TOOLS licence
2.7.3
Requesting a FAST/TOOLS licence
Next you need to request a FAST/TOOLS licence from Yokogawa. The

licence file you will receive is linked to the FAST/TOOLS node name
and number. Requesting a licence can be done using the Licence
Request Wizard that is part of the FAST/TOOLS distribution. The
Licence Request Wizard has to be installed on a Microsoft Windows
system.
You are able to run FAST/TOOLS without a licence for one hour for
evaluation purposes.
2.7.4
Validating FAST/TOOLS
Once you have received your licence file you can validate your
FAST/TOOLS system and it will be assigned its node number and node
name.
2.7.5
Setting up you HMI connection
Next you need to setup the connection to your HMI station.

FAST/TOOLS for Unix/Linux requires at least one HMI station for
system configuration.
2.8
FAST/TOOLS licences can be obtained by sending a licence request to

the following address:
YOKOGAWA ELECTRIC CORPORATION
9-32 Nakacho 2-chome, Musashino-shi,
Tokyo 180-8750, Japan
Telephone: +81-422-52-5616
email: GSC_Sales@ml.jp.yokogawa.com
2-7
2-8
Introduction
3
3.1
Introduction
This chapter gives a step by step explanation on how to install

FAST/TOOLS on your Unix/Linux system.
3.2
Preparing your system
Before you start installing FAST/TOOLS, you need to prepare your

FAST/TOOLS system.
3.2.1
Create a FAST/TOOLS directory (optional)
The FAST/TOOLS installer program suggests installing FAST/TOOLS

into the directory /opt. On Unix systems, this is the directory intended
for application software. Furthermore it is recommended to create a
separate file system for FAST/TOOLS and to mount this under /opt,
especially if the disk space available in this partition is limited. The
advantage of using a seperate filesystem is that in case it becomes full it
will not affect operation of system software or other applications.
If you want to install FAST/TOOLS anywhere else, you should create
the install directory before starting the install procedure.
The installer will create a directory called fasttools beneath the install
directory.
3.2.2
Create a FAST/TOOLS user and group (optional)
Before you install FAST/TOOLS you should decide who will be the
'owner' of the FAST/TOOLS package. File ownership will be given to
the user account from which FAST/TOOLS is installed. Also the files
will get the group id of the installers account.
It is a good idea to create a new user account for FAST/TOOLS.
Traditionally the user name "tools" and group name "tools" were used
for this but you are free to choose any user and group name.
Add the paths /tls/com and /tls/exe to the PATH environment
variable for the FAST/TOOLS user in the users profile so that the user
has access to the runtime environment of FAST/TOOLS.
3-1
3.3
Installing FAST/TOOLS
Finally we are ready to install FAST/TOOLS. For this we have to be

logged in as the FAST/TOOLS user. In this manual we will assume that
you have created a user call "tools" and a group "tools" for this purpose.
The first thing to do is to copy the install pack from the FAST/TOOLS
distribution DVD to a temporary directory in the home directory of the
user "tools"
$ mkdir tmp_install
Copy the install pack, the name of you cd-rom device on your system
may be different.
On RedHat Enterprise Linux:
$ cp
$ cd
-r /media/cdrom/fasttools* ~/tmp_install
~/tmp_install
On Sun Solaris:
$ cp -r /cdrom/fasttools* $HOME/tmp_install
$ cd $HOME/tmp_install
On IBM AIX:
$ cp
$ cd
-r /cdrom/fasttools* ~/tmp_install
~/tmp_install
The temporary install directory will now contain a tar file called
fasttools_<rel_nr>.tar where <rel_nr> is the number of the
FAST/TOOLS release you are installing. You now have to unpack the
tar file:
$ tar -xvf fasttools_<rel_nr>.tar
The tar file is unpacked into a directory called fasttools<rel_nr>. Enter

the directory and start the installation script:
$ cd fasttools_<rel_nr>
$ ./ft_install
The first question the install script will ask is if you have read the licence
terms and whether you agree with them:
3-2
Have you read the FAST/TOOLS licence terms and do you agree with
these terms?
Please enter Yes if you agree or No to exit installation [Yes]
If you do not agree you should answer No and the installation will
stop. Otherwise you can press enter to select the default answer Yes.
Next you are asked to enter the root password:
The FAST/TOOLS installation procedure requires root privileges.
Please enter the root password to continue.
Password:
After you entered the password the install script will ask for the
FAST/TOOLS install directory. The default is /opt/fasttools.
Please enter the FAST/TOOLS install directory or press enter
to accept default.
Install directory: [/opt/fasttools]
FAST/TOOLS is installed on your system. Next you are asked if you

want FAST/TOOLS to be started automatically when you startup your
system.
FAST/TOOLS can be configured to start automatically
when your system is started.
Do you want FAST/TOOLS to start with your system? .
* Please enter Yes or No [Yes]
When the install script is finished FAST/TOOLS is installed on your

system. The next step is to request a licence file.
Note:
By default the /tls/com and /tls/exe paths

are added to /etc/profile. For AIX systems
these paths should added manually to
/etc/environment.
Note:
Selecting the start automatically will add

an entry to /etc/rc.o/init.o/fasttools.
3-3
3.4
Requesting a licence
Requesting a licence
Requesting a FAST/TOOLS licence from Yokogawa can be done using

the Licence Request Wizard that is found on the FAST/TOOLS
distribution DVD. Install the wizard on a Microsoft Windows System.
After installing the wizard is activated from the FAST TOOLS start
menu. Follow the steps of the wizard to request a licence for the system.
3.5
Validating FAST/TOOLS
Once you have received your FAST/TOOLS licence file form

Yokogawa you are ready to validate FAST/TOOLS. Validating means
applying your licence.
Validating is done by passing the licence file as parameter to the
ft_validate script in the install directory of the Unix/Linus system:
$ cd ~/tmp_install/fasttools_<rel_nr>
$ ./ft_validate NODE_1.lic
-------------------------------------------------------------F A S T / T O O L S L i c e n s e
I n f o r m a t i o n
-------------------------------------------------------------License
License
License
License
Customer Name
Node Name
Node Number
System Number
:
:
:
:
Acme Scada Corporation.

NODE_1
1
C3311158839
Your FAST/TOOLS system was successfuly validated !.
You have now installed FAST/TOOLS on your Unix system
3-4
Prerequisites
Setting up a HMI connection
Because the FAST/TOOLS visualization and system managers interface

is only available on the Microsoft Windows platform every Unix based
FAST/TOOLS configuration requires a Microsoft Windows based HMI
station.
This section describes how to setup a HMI connection.
4.1
Prerequisites
Before you can connect you Unix system to a Microsoft Windows HMI
you should have the following information available:
Unix/Linux Server:
- Host name or IP address
- FAST/TOOLS node number
Microsoft Windows HMI Station:
- Host name or IP address
- FAST/TOOLS node number
4.1.1
Firewall configuration
You should also allow the FAST/TOOLS communication through any

firewall. FAST/TOOLS nodes communicate with each other using the
an UPD connection on port 17001.
By default the Redhat Enterprise Linux firewall will not allow any UDP
connections.
To open this port we can use the Firewall Configuration. Start this
application from the System menu:
4-1
Prerequisites
After starting the Firewall Configuration you must enter the super user
(root) password to continue:
4-2
Prerequisites
Then select Other Ports and add the 17001 UDP port:
Apply the new settings:
4-3
Server configuration
Finally effectuate the settings:
If you later need to open more ports for example for equipment
managers you, can add more UPD or TCP ports.
4.2
Server configuration
On the Unix/Linux server, we need to edit the file durm_1_udp.sup

setup file in the directory /tls/sup.
At the end of this file the addresses of the other machines to which this
system should be connected are specified by the remote parameter.
Create a new remote_set entry and set it to the value of the IP addresses
or Host names of the HMI node(s) you want to connect. For example:
remote_set = "HMI-1"
Thats it for the Unix server.
4.3
HMI configuration
On the HMI node, modify the file dur.sup in the .../tls/sup directory of
your FAST/TOOLS installation. Change the "host_node" parameter to
the BUS/FAST node number of the server system.
4-4
HMI configuration
Next copy the file durm_start from the .../tls/tpl directory to

../tls/com.
Finally edit the file durm_1_udp.sup setup file in the directory .../tls/sup.
At the end of this file the addresses of the other machines to which this
system should be connected are specified by the remote_set parameter.
Create a new remote entry and set it to the value of the IP addresses or
Host names of the server node. For example:
remote_set = "SERVER-1"
Now restart FAST/TOOLS on both Server and HMI-node and the
connection will be established.
4-5
4-6
HMI configuration
Introduction
Using FAST/TOOLS
Using FAST/TOOLS
5.1
Introduction
This sections contains a basic introduction to managing your

FAST/TOOLS system.
5.2
Starting and stopping FAST/TOOLS
A FAST/TOOLS system can be started manually by a user or

automatically when the system is booted. FAST/TOOLS will then run
as a Service.
If you start an unlicensed FAST/TOOLS system it will run for one hour.
This is done for evaluation/demo purposes.
5.3
Manually starting and stopping
Starting and stopping FAST/TOOLS manualy is done by running the

fast_start and fast_stop script that can be found in /tls/com. To start
FAST/TOOLS type:
$ fast_start
This command will start FAST/TOOLS by calling the start scripts of all
the individual tools in the right order. To stop FAST/TOOLS type:
$ fast_stop
This will stop FAST/TOOLS by calling the stop scripts of all the
individual tools in the right order.
5.4
Running FAST/TOOLS as a service
FAST/TOOLS can be configured to be started when your system is

started. This will ensure FAST/TOOLS is running after a booting your
system.
5-1
Using FAST/TOOLS
During installation you were asked if you wanted to start FAST/TOOLS

at startup of your system. If you answered yes, the installer will use the
command (on RedHat Enterprise Linux):
$ /sbin/chkconfig --add fasttools
to register the file fasttools.rc as a service, or another appropriate

command for AIX or Solaris. This file can be found in the installer
directory in .../fasttools_<rel_nr>/bin.
Unfortunately, different Unix versions and Linux distributions use
slightly different ways to register services. If you are using another
Linux distribution, you can use the fasttools.rc file as a starting
point and register it in the way required by your Linux distribution.
5.4.1
RedHat Enterprise Linux
On RedHat Enterprise Linux, if you have FAST/TOOLS registered as a

service you can start and stop the from the service dialog in the Gnome
desktop.
Start the Service Configuration from the System menu:
5-2
Using FAST/TOOLS
Scroll to the fasttools services en click the Enable button. If enabled

FAST/TOOLS will start as soon as the Linux system is started:
Finally you have to grant the changes by entering the password of the
super user (root):
5-3
Using FAST/TOOLS
Clearing FAST/TOOLS Runtime Data
5.4.2
Sun Solaris
On Sun Solaris, it is possible to enable and disable the script by

renaming the symbolic link found in /etc/rc3.d/ according to the
SystemV init style. For example, to disable FAST/TOOLS startup
service:
# cd /etc/rc3.d
# mv S99fasttools K10fasttools
And to enable FAST/TOOLS startup service again:

# cd /etc/rc3.d
# mv K10fasttools S99fasttools
5.4.3
IBM AIX
On IBM AIX, FAST/TOOLS must be enabled and disabled from within

the /etc/inittab file by commenting or uncommenting the line
which starts the service. To disable, the FAST/TOOLS line should read
(note the beginning colon character)
:
:fasttools:234:once:/etc/rc.fasttools start
And to enable the service, remove the commenting character, as follows:

fasttools:234:once:/etc/rc.fasttools start
5.5
Clearing FAST/TOOLS Runtime Data
To clear FAST/TOOLS runtime data, the fast_clear script should

be run with the appropriate parameter. In order to use this script,
FAST/TOOLS should first be stopped if it is running using the
fast_stop script.
To clear gathered history units and generated reports:
fast_clear -u
To clear all runtime and historical data:
5-4
Removing FAST/TOOLS
Using FAST/TOOLS
fast_clear -a
In both cases, the script will ask you to confirm the action that is to be
taken. Adding -q as the second parameter to the script will suppress this
confirmation request, as follows:
fast_clear -a -q
fast_clear -u -q
5.6
Removing FAST/TOOLS
To un-install the FAST/TOOLS software you need to take the following

steps depending on your platform:
5.6.1
RedHat Enterprise Linux
Stop FAST/TOOLS.
Remove the FAST/TOOLS service.
Start the Service Configuration from the System menu:
5-5
Using FAST/TOOLS
Removing FAST/TOOLS
Select the fasttools services and click Disable:
Remove the fasttool directory. If you selected the default location

during installation this directory can be found within the /opt
directory.
5.6.2
Sun Solaris
Stop FAST/TOOLS
Enter the following commands as root:
# rm /etc/rc3.d/*fasttools
# rm /etc/init.d/fasttools

directory.
5.6.3
IBM AIX
Stop FAST/TOOLS
Enter the following commands as root:
# rm /etc/rc.fasttools
In addition, on IBM AIX, the following line should be removed

from the /etc/inittab file:
fasttools:234:once:/etc/rc.fasttools start
5-6

directory.
Introduction
Appendix A: Distributed systems

A.1 Introduction
This appendix is intended to describe the starting points on a distributed
FAST/TOOLS configuration. Furthermore it describes what kind of
actions must be taken to configure a distributed FAST/TOOLS system.
The structure of this chapter is as follows:
First an introduction is given on various notions/concepts that are

directly related to the configuration of a distributed FAST/TOOLS
system. Since these notions/concepts are already covered in much
more detail in other parts of the FAST/TOOLS product
documentation, the notions are just introduced globally. Each of the
paragraphs globally describing a specific concept, contains a
reference to the product document in which the concept is
elaborated further.
The intention of this global introduction to these concepts is, to
make sure that you understand what kind of actions are needed to
configure a distributed FAST/TOOLS system.
Secondly, the configuration actions are described in more detail and
in a stepwise fashion.
A.2 HMI, Host, Front-end components

The FAST/TOOLS product can be used both in stand-alone- and
distributed configurations.
In a standalone configuration the FAST/TOOLS product is installed on
one physical computer system. In a distributed configuration, the FAST/
TOOLS product is installed on multiple physical computer systems
where each of the computer systems is given a specific role. From here
on the notions "computer system" and "node", are used interchangeably.
In a FAST/TOOLS system, the following roles are distinguished with
respect to the configuration:
HMI component:
The component that acts as user interface to the FAST/TOOLS
product. One or more of these HMI components exist in a
A-1
Interconnecting components
distributed configuration.
Host component:
The component that primarily acts as central data concentrator.
In many situations one such Host component exists in a FAST/
TOOLS system. From an "availability" point of view however, it is
possible to have redundant/dual Host components. This latter
situation however, is beyond the scope of this discussion.
Front-end component:
The component that primarily acts as a local data concentrator. In
that role this component gathers/controls a subset of the total
amount of process signals.
In a stand-alone configuration, the roles of HMI, Host and Front-end are

actually combined in one physical computer system. In a distributed
configuration the roles of HMI, Host and Front-end are often mapped
one to one on separate physical computer systems. However, it is also
possible to combine these roles in one and the same physical computer
system (for example a physical computer system that acts as Host and
HMI component).
A.3 Interconnecting components

Although various combinations are possible, in the context of this
discussion and as a reference implementation of a distributed FAST/
TOOLS system, it is assumed that each HMI, Host and Front-end
component, is mapped upon a separate physical computer system. Each
of these physical systems is connected to a network. Furthermore it is
assumed that:
One Host component exists in such a configuration.
Each HMI component is connected via a DURM connection to the
Host component and each of the Front-end components.
The Host component is connected via a DURM connections to each
of the Front-end components.
By logically connecting the various FAST/TOOLS components to each
other in the above described way, there is some form of inherent fallback
scenario configured.
Suppose for example that a HMI component fails. Since the other HMI
component is also connected to the Host- and Front-end components,
there is still access to the Host- and Front-end components via this other
HMI component.
A-2
Distribution of data sets
Suppose for example that the Host component fails. Without a

redundant/dual Host in place, undoubtedly some FAST/TOOLS
functionality will not be available. However by having a DURM
connection between the HMI- and Front-end components, it is still
possible to monitor and control vital functions in the process being
supervised.
Remark:
Although possible, it is normally not the case that an HMI component is
connected (via DURM) to other HMI components and/or a Front-end
component is connected to other Front-end components.
Detailed information about DURM and configuring DURM can be
found in the BUS/FAST System Integrators Manual.
A.4 Distribution of data sets

Via the FAST/TOOLS data set model, configuration- and process data
is, exhibited to and controlled/manipulated by, among others, the HMI
components under strict conditions. The FAST/TOOLS functionality
that implements this data set model is called Data Set Services (DSS).
Thanks to DSS, the configuration- and process data can be redundantly
stored in more than one physical computer system. Such a dataset is said
to be "distributed". The advantage of this is obvious: should a physical
computer system fail, there is still the possibility to read the required
data elsewhere. This is entirely transparent to the DSS clients, among
which the HMI components.
Updating data that is redundantly stored in more than one physical
computer system, works slightly different. With one exception (the
dataset containing item-values), updating a distributed data set, requires
the availability of all physical computer systems on which the data is
stored. If one of the computer systems on which the data should be
stored cannot be "reached", the data in the dataset cannot be updated.
The definition of where the data is stored, is done via the so called data
set definitions.
Detailed information about DSS and data set definitions can be found in
DATABASE/FAST System Integrators Manual
DSS Language Manual
A-3
Item copy processes
A.5 Item copy processes

In a distributed FAST/TOOLS system, the System Manager makes
specific choices regarding the so called "distribution group" and
"distribution type" attributes of an item. Together the "value" of these
attributes for a FAST/TOOLS item, determine:
Whether an item is distributed (image available at Host and Frontend) or not.
At most, a FAST/TOOLS item is replicated on 2 nodes.
Where the master image of the item resides (in the Host- or Frontend component).
In case the item image is solely stored in the Front-end component
(not distributed) or in case of a distributed item, which Front-end
component (which node) is involved.
For distributed items the so called item copy processes in the FAST/
TOOLS system, are responsible for updating the "slave" image of an
item. The item copy processes play no role for non-distributed items
(non distributed items, only have their image in the Host component).
Note:
It is intentional that the plural form is used here: item copy processes.
These processes always act as a pair on a given computer system;
The Master Item copy process on a given computer system is
responsible for passing updates from a master item on its node, to the
slave image. It does so by communicating with the Slave Item copy
process on the node where the "slave" image of the item resides.
Briefly then; in a distributed FAST/TOOLS system a pair of item copy
processs (a master and a slave) must be active on each of the nodes
acting as Host and Front-end.
Detailed information about distributed items and the item copy
processes can be found in the ITEM/FAST System Integrators Manual.
A.6 Distributed ALARM/FAST

In a distributed FAST/TOOLS system it is possible to use the ALARM/
FAST functionality without the link between Host and Front-end being
active. In such a configuration, the systems on which the Host- and
Front-end components are installed, offer independent ALARM/FAST
A-4
Distributed Item Interface (GIN DII)
functionality although they can not communicate with each other.

Whether or not the distributed ALARM/FAST functionality must be
available, can be configured via the alm.sup file.
Deatiled information about distributed ALARM/FAST functionality can
be found in ALARM/FAST System Integrators Manual.
A.7 Distributed Item Interface (GIN DII)

The purpose of the Distributed Item Interface is to make item
manipulation transparent across nodes in a distributed FAST/TOOLS
system. When one of the nodes in a distributed environment goes offline, the distributed FAST/TOOLS system must continue to operate in
the best possible way. The Distributed Item Interface represents this
functionality transparently to its clients:
Obtains item attributes from the correct node.
Sets item attributes on the correct node.
Redirect item event requests when the node currently servicing the
event request, fails.
The Distributed Item Interface uses a (default) node approach/access
scheme to perform these tasks. Important to note here is that this default
scheme can be configured via a setup file.
Detailed information about the Distributed Item Interface and the
modification of the node default access scheme, can be found in the GIN
Programmers Manual.
A.8 Stepwise configuration actions

1
Make sure that all nodes involved, "know" which one of them acts
as Host component.
This can simply be configured in the "dur.sup" setup file on each
node by specifying the Host node number in this setup file.
Configure the DURM connections.

Make sure a durm_start (Unix)/durm_start.cmd (Microsoft
Windows) file is present on the FAST/TOOLS command directory
A-5
Stepwise configuration actions
(../tls/com for Microsoft Windows, ../tls/com_node for Unix). This

durm_start(.cmd) file is used by the FAST/TOOLS startupprocedure to start the (various) DURM connection(s).
Make sure a setup file is configured for each of the DURM
processes to be started on a given node. One of the most important
aspects to configure in these setup files is/are the Host-name(s) or
IP-address(es) of the counterpart computer systems (the node(s)
with which we want to establish a DURM connection).
3
Configure the distribution of datasets

Configure the distribution of datasets in such a way that all datasets
are present on all Host- and Front-end- nodes. This can be done by
editing the file "dss_global.dss" on the FAST/TOOLS source
directory (../tls/src) on the node containing the Host component.
Look in this file for the macro definition for "mcStorageNodes" and
add "node-labels" to this macro for each of the additional nodes in
the FAST/TOOLS system. Since this macro is used by almost all of
the dataset definitions, all datasets will use this "storage node"
definition automatically. Once the data set definitions are compiled
(during first startup of FAST/TOOLS on the node containing the
Host component), DSS knows where the various FAST/TOOLS
data sets can be found.
Note: When the contents of a DSS file is changed, run the DSS
compiler on the directory where the DSS files are stored (usually ../
tls/src). Then stop and restart the FAST/TOOLS.
Configure the startup of item copy processes.

Since the item copy processes are not started by default, the file
item_start (Unix)/item_start.cmd (Microsoft Windows) must be
changed manually.
Look in this file for the startup commands for the ITMCPM and
ITMCPS executables and uncomment these startup commands.
Configure PROCESS/FAST node connection scheme.

Next we must tell PROCESS/FAST running on the host node that
it must connect to all the Front-end. This is done by modifying the
setup file opc.sup. In this file remove the line:
NODE_IGNORE = -1
This must only be done on the HOST node.
A-6
If distributed ALARM/FAST functionality is required activate this
in the "alm.sup" on each node where distributed ALARM/FAST

functionality must be available.
7
Activate the option Check all MDUR nodes in the gin.sup setup
file and if required, re-configure the default access scheme.
Note: If adding a Front-end to an existing
configuration as the result of system
expansion for example, run the following
commands on the FAST/TOOLS server once
the Front-end has been connected:
dsschk -r
dsschk -e r
A-7
A-8
Index
Index
A
PROCESS/FAST 2-2
abbreviations 1-2
ACCESS/FAST 2-2
ALARM/FAST 2-2
AUDIT/FAST 2-2
Server 2-1
REPORT/FAST 2-2
BUS/FAST 2-2
C
conventions 1-2
D
DATABASE/FAST 2-2
E
EQUIPMENT/FAST 2-2
F
fasttools.rc 5-2
Firewal 4-1
Front-end node 2-1
H
HISTORY/ FAST 2-2
HMI node 2-1
I
INTEGRATION 2-2
ITEM/FAST 2-2
L
Licensing 2-7
O
objectives 1-1
ODBC 2-2
P
Prerequisites 4-1
Index
YOKOGAWA ELECTRIC
CORPORATION
9-32 Nakacho 2-chome,
Musashino-shi,
Tokyo 180-8750, Japan
tel: +81-422-52-5616
email:
GSC_Sales@ml.jp.yokogawa.com
Readers Comment
Manual name: ......................................................................................Version: .........................
Did you find this manual understandable, usable, well organized? Please make suggestions for
improvement.
.....................................................................................................................................................
.....................................................................................................................................................
.....................................................................................................................................................
.....................................................................................................................................................
.....................................................................................................................................................
.....................................................................................................................................................
.....................................................................................................................................................
.....................................................................................................................................................
.....................................................................................................................................................
Did you find any errors in this manual? If so, please specify the error and page number.
.....................................................................................................................................................
.....................................................................................................................................................
.....................................................................................................................................................
.....................................................................................................................................................
.....................................................................................................................................................
.....................................................................................................................................................
.....................................................................................................................................................
.....................................................................................................................................................
.....................................................................................................................................................
Note: Yokogawa will use comments submitted on this form at its own discretion.
Name:....................................................................................................Date ..............................
Organization: ...............................................................................................................................
Address: .......................................................................................................................................
City and Zip code:........................................................................................................................
Country: .......................................................................................................................................

Im Linux

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Im Linux

Caricato da

Copyright:

Formati disponibili

Instruction

Installation Manual Linux

YOKOGAWA ELECTRIC CORPORATION

Yokogawa Electric Corporation

FAST/TOOLS basic concepts ..............................................2-1

Required Disk Space .................................................2-4

Read the Release Notes document ............................ 2-6

Where to get your FAST/TOOLS licence .................2-7

FAST/TOOLS installation ...................................................3-1

Item definition file .................................................... 2-4

Required Systemem Memory ....................................2-6

Supported configurations .......................................... 2-3

Create a FAST/TOOLS directory (optional) ............ 3-1

Installing FAST/TOOLS ...........................................3-2

Setting up a HMI connection ...............................................4-1

Firewall configuration ............................................... 4-1

Server configuration ..................................................4-4

FAST/TOOLS Installation Manual Linux and Unix

HMI configuration .................................................... 4-4

Using FAST/TOOLS ........................................................... 5-1

RedHat Enterprise Linux .......................................... 5-2

Clearing FAST/TOOLS Runtime Data ..................... 5-4

RedHat Enterprise Linux .......................................... 5-5

Appendix A:Distributed systems .................................................. A-1

FAST/TOOLS Installation Manual Linux and Unix

This manual describes the procedure for installing FAST/TOOLS on

It is assumed that you have some basic Unix/Linux system

Supported Unix/Linux platforms

In FAST/TOOLS release 9.05 the following Unix/Linux platforms are

IBM AIX 6.1

Structure of this document

The FAST/TOOLS Installation Manual can be divided into a number of

Chapter 1, Preface, Introduction and Conventions.

FAST/TOOLS Installation Manual Linux and Unix

Conventions and abbreviations

to install and license FAST/TOOLS.

Conventions and abbreviations

The following conventions may be used in this manual:

Indicates that the enclosed item is the default.

Indicate reserved words and predefined names,

Indicates that the specified parameter is input.

Indicates that the specified parameter is output.

Used in format descriptions. <name> indicates a

This type-setting is used to indicate file names.

This type-setting is used to indicate output on a

This type-setting is used to indicate input from

FAST/TOOLS Installation Manual Linux and Unix

FAST/TOOLS basic concepts

FAST/TOOLS basic concepts

This chapter introduces some basic FAST/TOOLS concepts you need to

A FAST/TOOLS configuration can consist of one single FAST/TOOLS

FAST/TOOLS basic concepts

The FAST/TOOLS package

In a distributed configuration all the HMI nodes must be Microsoft

The FAST/TOOLS package

The FAST/TOOLS software package is divided in a number of

Basic support and communications

ISAM based file support

Real time item data handling

Sequences, processing and calculations

Open DataBase Connectivity (ODBC) interface

FAST/TOOLS User Interface (only available on the

Miscellaneous FAST/TOOLS functionality and