Imnttools

YOKOGAWA
FAST/TOOLS
Installation Manual
Windows
FAST/TOOLS
Instruction
Manual
IM50C03C00-01EN/R9.04
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
IM50C03C00-01EN/R9.04
Copyright April 2011
ii

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.
FAST/TOOLS Installation Manual Windows iii
Table of Contents
Table of Contents
0 Preface ...................................................................................0-1
0.1 Objectives ..................................................................0-1
0.2 Intended audience ......................................................0-1
0.3 Structure of this document .........................................0-1
0.4 Associated document .................................................0-1
0.5 Conventions and abbreviations ..................................0-2
1 General ..................................................................................1-1
1.1 Introduction ...............................................................1-1
1.2 Requirements .............................................................1-3
1.2.1 Required Software .................................................... 1-3
1.2.2 Required Disk Space ................................................. 1-4
1.2.3 Required Memory Space .......................................... 1-6
1.3 The phases of installation ..........................................1-7
1.3.1 Read the Release Notes document ............................ 1-7
1.3.2 FAST/TOOLS installation ........................................ 1-7
1.3.3 Re-installing .............................................................. 1-7
1.3.4 Directory structure .................................................... 1-7
1.4 How to obtain your licence numbers .........................1-9
3 SimbaServer ..........................................................................2-1
3.1 Installing the SimbaServer .........................................2-1
4 SimbaClient ...........................................................................3-1
4.1 Installing SimbaClient ...............................................3-1
4.2 Supported ODBC enabled applications .....................3-2
5 FAST/TOOLS Components ................................................4-1
5.1 Installing FAST/TOOLS components .......................4-1
5.2 Licensing FAST/TOOLS ...........................................4-1
5.3 Starting and stopping FAST/TOOLS ........................4-2
5.4 Starting and stopping the HMI ..................................4-3
5.4.1 Manually ................................................................... 4-3
5.4.2 Automatically ............................................................ 4-4
5.4.3 Stopping .................................................................... 4-4
5.5 Time synchronisation ................................................4-4
5.6 Using the Default User account .................................4-4
5.7 Available Procedures .................................................4-5
5.8 Uninstallation of FAST/TOOLS ...............................4-6
5.9 Changing FAST/TOOLS service startup-time ..........4-6
Table of Contents
iv FAST/TOOLS Installation Manual Windows
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-6
Objectives Preface
FAST/TOOLS Installation Manual Windows 0-1
0 Preface
0.1 Objectives
This manual has the following objective:
To provide all information needed to install the FAST/TOOLS
package on the Windows platform.
This includes information about the installation of third party
packages used by the FAST/TOOLS product.
To provide information about concepts and step-by-step
instructions related to the configuration of a distributed
FAST/TOOLS system.
0.2 Intended audience
This manual is intended for anyone wanting to install one or more of the
tools of the FAST/TOOLS package.
The reader is assumed to be familiar with the Windows platform and the
Windows operating system and is assumed to have some knowledge of
the FAST/TOOLS philosophy.
0.3 Structure of this document
The FAST/TOOLS Installation Manual is divided into a number of
chapters / appendices
Chapter 1 describes the general procedure that should be followed
when installing any configuration of FAST/TOOLS.
Subsequent chapters describe how to install the FAST/TOOLS
software and related third-party packages.
In Appendix A, a description is given of the configuration of a
distributed FAST/TOOLS system.
0.4 Associated document
Windows platform dependent documentation set.
Preface Conventions and abbreviations
0-2 FAST/TOOLS Installation Manual Windows
0.5 Conventions and abbreviations
The following conventions may be used in this manual:
CONVENTION MEANING
[ ] Indicates that the enclosed item is the default.
UPPERCASE Indicates reserved words and predefined names,
letters 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 indi-
cate 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 General
1 General
1.1 Introduction
This manual describes the procedure for installing FAST/TOOLS on a
Windows system based upon the Intel x86 PC architecture.
This chapter describes the philosophy behind the procedures as well as
the Windows specific information.
FAST/TOOLS consists of a number of functional tools:
This FAST/TOOLS functionality may be contained by one system
(stand-alone configuration) or distributed over more than one system
(distributed configuration).
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
OPC server and client functionality
COLOUR/FAST Graphical support functions for USER/FAST
USER/FAST FAST/TOOLS User Interface
INTEGRATION Various pieces of FAST/TOOLS functionality (e.g.
quick load, int-server).
General Introduction
A system in a distributed configuration has a certain function
(component). The following components are defined:
In addition a system may contain mixed components. For example a
system may contain the Server, Front-end and HMI components. This
may be a stand-alone system.
The following table lists the tools and in which component they are
found:
Table 2: The components within a distributed configuration
Function Description
Server The server is the central system within a distributed configura-
tion.
Front-end A front-end takes care of gathering data from the attached equip-
ment. In addition some local control is possible.
HMI A Human Machine Interface enables the Operator to monitor and
control the process.
SDK The Software Development Kit enables the System Integrator to
modify the basic functionality of FAST/TOOLS.
Setup File
Editor
The FAST/TOOLS Setup File Editor provides a graphical user
interface to ease the process of editing setup files.
FAST/Start FAST/Start setup installs additional files to get started quickly. It
supplies a user interface that hides features that are less com-
monly used.
Remark: This component is technically equal to the Server
component plus the additional files meant to get started quickly.
Table 3: Tools in relation to the components
Tool name
Component
Server Front-end HMI SDK
BUS/FAST * * * *
DATABASE/FAST * * * *
HISTORY/FAST * *
AUDIT/FAST * *
ITEM/FAST * * *
EQUIPMENT/FAST * * *
ALARM/FAST * * *
Requirements General
The installation of FAST/TOOLS is based upon components. For
example, when you install the server component you will get the tools
as listed in the previous table. Whether or not a certain tool will be
activated depends on whether or not the tool is licensed.
1.2 Requirements
To install FAST/TOOLS, you must have administrator privileges on
your system. Therefore you must be logged in as an Administrator or as
a user with administrator privileges.
Make sure that no other applications are active during installation of
FAST/TOOLS.
1.2.1 Required Software
Before you install FAST/TOOLS, other software must be installed. For
the version number of the various software packages, please consult the
Release Notes document.
Windows
Windows 2008 SERVER-R2 SP1, Windows 7 Professional 64-bit
SP1or Windows XP Professional SP3 must be installed. The disks
must be formatted using the NTFS file system.
Visual C++ 6.0 and Visual Basic 6.0
The Microsoft Visual C++ and Visual Basic are required when you
install the FAST/TOOLS SDK component and want to compile and
link applications.
PROCESS/FAST * * *
REPORT/FAST * *
ACCESS/FAST * *
(OPC only)
*
COLOUR/FAST * * *
USER/FAST * * *
INTEGRATION * * *
Table 3: Tools in relation to the components
Tool name
Component
Server Front-end HMI SDK
General Requirements
SimbaServer
When you want to enable PC applications to access FAST/TOOLS
datasets via the ODBC interface, the SimbaServer is required. This
server must be installed on the system where the FAST/TOOLS
Server component is to be installed. The SimbaServer can be found
on your FAST/TOOLS CD. However, it is installed separately from
FAST/TOOLS. See Chapter 3 for installing SimbaServer.
SimbaClient
When you want to enable an application running on a Windows
system to access FAST/TOOLS data located on a FAST/TOOLS
system via an ODBC interface, then you have to install
SimbaClient on the client system.
SimbaClient can be found on your FAST/TOOLS CD. See Chapter
4 for installing SimbaClient.
When you want to use the FAST/TOOLS archiving functionality in
combinations with CDs, you must install a CD creation software
package that has the possibility to format CDs in Universal Disk
Format (UDF).
1.2.2 Required Disk Space
To install the FAST/TOOLS software you will require about 400
Mbytes of disk space.
Whilst running FAST/TOOLS, additional disk space is required to store
configuration and historical data:
Item definition file
The item definition requires 1,800 bytes for each item defined (Server
component only).
Add 350 bytes per item for each system where the front-end component
is installed.
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 used storage
types. These values should be seen as a rule of thumb. All file size
Requirements General
aspects such as key file overhead and bucket slack size are counted in
the sample size values.
Disk compression is not counted.
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
to take 100 bytes of disk space.
Scan based collection/Time based storage
Scan/Time in the HMI. This storage group has optional
compression and can be configured to store the quality code of the
item as well as the value and status. The following table gives the
average disk space each item sample will take, depending on the
choices you make:
Event based collection/Item based storage
Event/Item in the HMI. This storage type is intended to be used for
frequently changing analog values that 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.
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.
Table 4: 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
General Requirements
Classes and objects
Each class defined and compiled typically costs 18 Kbytes of disk space.
Each object consumes 2 Kbytes in average.
Reports
Each defined report takes about 2 Kbytes. The size of a generated report
is undefined due to the nature of a report definition.
Displays and symbols
On average a display or symbol takes 30 Kbytes of disk space.
1.2.3 Required Memory Space
The following system memory sizes are advised:
Note that additional non FAST/TOOLS applications may require
additional memory.
Table 5: Advised memory sizes
Software
Advised
memory size
(Mbytes)
Small stand alone system with Server, Front-end and HMI
component installed (up to 2000 items)
2048
FAST/TOOLS Server system 2048
Large FAST/TOOLS Server system (100.000 items or more) 4096
HMI component only 2048
Front-end component only 1024
SDK component 512
The phases of installation General
1.3 The phases of installation
1.3.1 Read the Release Notes document
Before you start the installation of software, read the Release Notes
document. Among other things, it contains information about the
versions of third party software packages, required Service Packs, etc.
1.3.2 FAST/TOOLS installation
The installation of FAST/TOOLS is divided into a number of phases:
1 Installation of third party software components.
2 The components of the FAST/TOOLS package are installed.
3 After installation of the FAST/TOOLS package, the functional
tools should be licensed by running the License and Authorize
options from the Licence Wizard. When you omit this phase, you
still can explore the functionality of FAST/TOOLS for one hour
each time you start FAST/TOOLS.
Make sure that these phases are performed under a user account with
administrator privileges.
After installation, the tools can be started using the commands in the
FAST/TOOLS entry in the Start menu.
1.3.3 Re-installing
Whenever the hardware and/or software configuration is changed in
some way, it may be necessary to reinstall some of the FAST/TOOLS
components as appropriate. Make sure that FAST/TOOLS is not
running when components are added or re-installed.
1.3.4 Directory structure
During installation of FAST/TOOLS, the following directory structure
is created (note that not all subdirectories may be there, depending on the
components installed):
%TLS_ROOT_PATH%
The directory where FAST/TOOLS is installed.
General The phases of installation
%TLS_ROOT_PATH%\tls
Directory which contains the FAST/TOOLS components.
%TLS_ROOT_PATH%\tls\dat
Directory for data files that are indispensable for programs to
function correctly (not to be confused with
%TLS_ROOT_PATH%\tls\sav).
%TLS_ROOT_PATH%\tls\lst
Directory for list and output files created by programs.
%TLS_ROOT_PATH%\tls\sav
Directory to store files that can be re-generated if they should be
lost, e.g. code files for PROCESS/ FAST and warm-start files for
ITEM/FAST.
%TLS_ROOT_PATH%\tls\sup
Directory for setup files that contain setup parameters which can be
changed in a run-time environment.
%TLS_ROOT_PATH%\tls\com
Directory for command files, procedures and scripts.
%TLS_ROOT_PATH%\tls\exe
Directory for executables (binaries).
%TLS_ROOT_PATH%\tls\hlp
Directory that contains help files.
%TLS_ROOT_PATH%\tls\inc
Directory for FAST/TOOLS include files. Typically *.h files are
stored here, but *.inc files containing programming fragments are
also present.
%TLS_ROOT_PATH%\tls\lib
Directory for object libraries.
%TLS_ROOT_PATH%\tls\src
Directory for source files.
%TLS_ROOT_PATH%\tls\tpl
Directory for template files, typically used when installing tools or
specifying parameters.
%TLS_ROOT_PATH%\tls\upg
Directory for upgrade utilities.
%TLS_ROOT_PATH%\tls\his
Directory for historical data files.
%TLS_ROOT_PATH%\tls\wap
Directory for web application files
%TLS_ROOT_PATH%\tls\jre
Java runtime environment directory
How to obtain your licence numbers General
1.4 How to obtain your licence numbers
To obtain the licence numbers for the any tools of the FAST/TOOLS
collection, start the FAST/TOOLS Licence Wizard from the
FAST/TOOLS program group in the start menu and follow the
instructions given.
Contact Yokogawa to obtain licence numbers at the following address:
Global SCADA Center
Yokogawa Electric Corporation
Musashino-shi,
Tokyo 180-8750, Japan
Telephone: +81-422-52-5616
email: GSC_Sales@ml.jp.yokogawa.com
General How to obtain your licence numbers
Installing the SimbaServer SimbaServer
3 SimbaServer
3.1 Installing the SimbaServer
Note: When you are going to install SimbaServer
on a Windows system that has Terminal
Services installed, always install
SimbaServer via Add/Remove Programs
control panel found in the
Start/Settings/Control Panel folder.
Then follow the instructions given.
Go to the SimbaServer directory on the FAST/TOOLS CD.
Activate the setup application.
Follow the instructions on your screen.
SimbaServer Installing the SimbaServer
Installing SimbaClient SimbaClient
4 SimbaClient
4.1 Installing SimbaClient
Note: When you are going to install SimbaClient
on a Windows system that has Terminal
Services installed, always install
SimbaClient via Add/Remove Programs
control panel found in the
Go to the SimbaClient directory on the FAST/TOOLS CD.
The setup application can activate an Explorer window. You can ignore
and close this window.
After installing SimbaClient then the ODBC data sources need to be
updated with the FAST/TOOLS ODBC driver. To do this run the
SimbaClient Configuration Utility simutl32.exe located in the
SimbaClient installation directory (default installation is c:\Program
Files\Simba Technologies\SimbaClient).
SimbaClient Supported ODBC enabled applications
Make sure FAST/TOOLS is running on the server machine.
Select Apply above to system data sources from the dialog.
Click the Advanced button and enter the IP address of the
FAST/TOOLS server machine or use the loopback address
127.0.0.1 when configuring the client on the same machine as the
server.
Click the Update button to add FAST/TOOLS to the list of data
sources.
4.2 Supported ODBC enabled applications
SimbaClient installed on Windows 95 or 98 supports both 16 bit and 32
bit ODBC enabled applications.
SimbaClient installed on supports only 32 bit ODBC enabled
application.
Installing FAST/TOOLS components FAST/TOOLS Components
5 FAST/TOOLS Components
5.1 Installing FAST/TOOLS components
Note: When you are going to install
FAST/TOOLS on a Windows system that
has Terminal Services installed, always
install FAST/TOOLS via Add/Remove
Programs control panel found in the
Go to the FAST/TOOLS directory on the FAST/TOOLS CD.
Go to one of the following sub directories:
- eng
For the English version of FAST/TOOLS.
- fre
For the French version of FAST/TOOLS.
- ger
For the German version of FAST/TOOLS.
Select a directory where the FAST/TOOLS files should be placed.
This directory can include long directory names. The default
directory is C:\Program Files\Yokogawa\FAST TOOLS
Select the FAST/TOOLS components you want to install. Select
Custom when you want to compose a configuration not listed
here.
Select the Program menu folder where the menu items of
FAST/TOOLS are placed in. The default is FAST TOOLS
When setup has copied the files from the CD to the system and
setup has determined that the system should be restarted, it shows
the Setup Complete form.
5.2 Licensing FAST/TOOLS
You may run FAST/TOOLS without licensing it. The full functionality
is then available to you. However, FAST/TOOLS will shutdown
automatically after one hour. You can then start FAST/TOOLS again for
one hour to explore its functionality.
FAST/TOOLS Components Starting and stopping FAST/TOOLS
To license FAST/TOOLS, you must start the Licence Wizard from the
FAST TOOLS program group in the Start menu and follow the
instructions given by the wizard.
Note: when you install FAST/TOOLS and intend to license it, it is better
not to start FAST/TOOLS before licensing it. When you have run
FAST/TOOLS before licensing it, all data that you entered whilst
running FAST/TOOLS will be lost at the moment you license it.
5.3 Starting and stopping FAST/TOOLS
A licensed FAST/TOOLS system can be started manually or
automatically. Both ways of starting FAST/TOOLS does not include
starting the HMI (see the next Section 5.4).
An unlicensed FAST/TOOLS system can only be started manually via
the FAST TOOLS" program group in the Start menu. In this case, the
HMI is automatically started. FAST/TOOLS will shutdown
automatically after one hour.
The following information is valid only for a licensed FAST/TOOLS
system:
FAST/TOOLS is started via a service installed during installation of
FAST/TOOLS. This service can be configured to be started
automatically or manually. The result of the start procedure is output in
a log file called fast_start.log located in the
%TLS_ROOT_PATH%\tls directory. Previous log files are preserved
and named fast_start-<n>.log where <n> = 1 for the log file of the
previous start and so on.
To configure the FAST/TOOLS service, the following steps must be
taken:
Login as administrator.
Define an account for running FAST/TOOLS.
The account defined for running FAST/TOOLS and the account
under which you login to the the computer can be different
accounts. However, make sure that both accounts have at least read,
write and execute permissions on the folders and sub-folders where
FAST/TOOLS is installed.
In the Control Panel, select Administrative Tools and then Services.
Set the Startup Type for the StartFASTTOOLS service to
Automatic.
If you do not want FAST/TOOLS to be started automatically, set
the Startup Type for the StartFASTTOOLS service to either
Starting and stopping the HMI FAST/TOOLS Components
Manual if you still want to start FAST/TOOLS manually later or
Disable if you want to prevent someone from starting
FAST/TOOLS altogether.
Set the account for starting the FAST/TOOLS service to the
FAST/TOOLS specific account (the account defined for running
FAST/TOOLS).
Note: Do not leave the service account to System
Account.
When the service is configured to Manual start, a user can start
FAST/TOOLS via the Start FAST TOOLS entry of the FAST/TOOLS
menu.
FAST/TOOLS will stop in a controlled way when the system is stopped,
or a user can stop FAST/TOOLS via the Stop FAST TOOLS entry of
the FAST/TOOLS menu.
The FAST-Start and FAST-Stop are shortcuts to the faststarter
utility. The faststarter utility can be used in your own command scripts
too and accepts the following arguments:
faststarter -s
Start FAST/TOOLS.
faststarter -e
Stops FAST/TOOLS when the user clicks on YES in a
confirmation window.
faststarter -f
Stops FAST/TOOLS unconditionally.
faststarter
Shows a help window.
5.4 Starting and stopping the HMI
The FAST/TOOLS HMI can be started in either of two ways; manually
or automatically.
5.4.1 Manually
When a user has logged into the Windows system, he or she may select
the HMI option from the FAST/TOOLS menu in the Start menu. This
is the default way after FAST/TOOLS is installed.
FAST/TOOLS Components Time synchronisation
5.4.2 Automatically
As soon as the user logs in, the FAST/TOOLS HMI is started. For this
method, copy the HMI menu item to the Startup folder of the user.
5.4.3 Stopping
The HMI is stopped when you log off from the HMI.
5.5 Time synchronisation
If, in a distributed FAST/TOOLS configuration, the time of the systems
is synchronised using the durutl utility, then the user who starts
FAST/TOOLS must have the Change system time privilege. This also
applies if an external time synchronisation device is attached using the
durecs utility or the equipment manager process eqp.
5.6 Using the Default User account
Section 5.3 describes how to create a user account for FAST/TOOLS.
This user account should have all resources assigned to it that are
required by the FAST/TOOLS configuration, such as printer queues and
mapped drives.
It may be useful to have the same resources used by FAST/TOOLS also
available to other user accounts. Examples are printer queues and
mapped network drives. In order to make the same resources available
to everyone that logs in on a machine without having to define it
separately for each user, the Default User account should be modified.
The following steps describe how to change the Default User account.
1 Log on as the local administrator for the machine.
2 Make sure the Show hidden files and folders option is enabled in
folder viewing options of Windows Explorer. This is necessary to
be able to copy all of the required folders to the Default User
profile.
3 Make a backup copy of the existing Default User profile. The
profile is located in folder Default User under folder Documents
and Settings.
4 Create a new, local user account. This will be used to define the new
characteristics of the Default User.
5 Log off again and log in under the newly created local user account.
Available Procedures FAST/TOOLS Components
6 Customise the local account by defining the required printer queues
and mapping the necessary network drives. Set one of the defined
printer queues to the desired default printer.
7 Log off and log back on as administrator.
8 Replace the current Default User profile with the customised
account as follows:
- Activate the Control Panel via the Windows Start menu.
- Double-click System.
- On the User Profiles tab, select the new user account and
click Copy To.
- In the Copy To dialog box, under Copy profile to, click
Browse, click the \Documents and Settings\Default User
folder and then OK.
- Under Permitted to use, click Change, click Everyone and
then OK.
5.7 Available Procedures
A number of command procedures are available. Most of them are
activated when an option is selected from the FAST/TOOLS menu in the
Start menu. The command procedures are available in the
%TLS_ROOT_PATH%\tls\com directory. The procedures may also be
started from a Command Prompt. In this case go to the
%TLS_ROOT_PATH%\tls\com directory and issue the commands from
there.
fast_start.cmd
Procedure that is called by the FAST/TOOLS services to start
FAST/TOOLS.
fast_stop.cmd
Procedure that is called by the FAST/TOOLS services to stop
FAST/TOOS.
setenv.cmd
Procedure to setup the FAST/TOOLS environment within the
Command Prompt. It is mostly included by the other procedures.
fast_clear.cmd
Procedure to cleanup the FAST/TOOLS environment. It resets the
FAST/TOOLS environment to its initial state as being freshly
installed. It can also be used to remove all gathered history and
generated reports only. To remove the history only, enter:
fast_clear -u
To remove all runtime data enter:
fast_clear -a
FAST/TOOLS Components Uninstallation of FAST/TOOLS
You will be prompted to continue unless you specified the -q
(quiet) switch in addition to the -u or -a switch.
Note: Be extremely careful when using fast_clear.
It removes all your definitions and history
gathered by the system.
Not all procedures may be available. This depends on the FAST/TOOLS
components you have installed.
5.8 Uninstallation of FAST/TOOLS
To un-install the FAST/TOOLS software, perform the following
actions:
Stop FAST/TOOLS.
Remove the FAST/TOOLS service by issuing the following
command in a Command Prompt window:
instsrv StartFASTTOOLS remove
Via the Add/Remove Programs Control Panel, remove the
FAST/TOOLS software from your system.
Since the FAST/TOOLS software creates several data files as soon
as it is started, not all FAST/TOOLS files will be removed
automatically. Therefore you should also perform the last step.
Remove the entire %TLS_ROOT_PATH% directory from your
system.
5.9 Changing FAST/TOOLS service
startup-time
If a large FAST/TOOLS configuration is started or stopped from the
Windows Start menu, it sometimes takes longer than the default timeout
for windows services. If stopping a service takes too long, Windows
will show an error message such as "Failed to stop in a timely fashion".
This timeout is a system wide setting that is used for all Windows
services. You can override de default by adding a entry called
ServicesPipeTimeout to the windows registry.
Warning: If you use Registry Editor incorrectly, you may cause serious
problems that may require you to reinstall your operating system.
Always make a backup of your registry before applying any changes
Changing FAST/TOOLS service startup-time FAST/TOOLS Components
To resolve this issue, increase the time-out value for service startup
process. When you increase this value, FAST/TOOLS has more time to
start and stop. To increase the service startup time, create the following
registry entry:
To create this registry entry, follow these steps:
Click Start, click Run, type regedit, and then click OK.
Locate and then click the following registry subkey:
"HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\
Control
Right-click Control, point to New, and then click DWORD
Value.
In the New Value #1 box, type ServicesPipeTimeout, and then
press ENTER.
Right-click ServicesPipeTimeout, and then click Modify.
Click Decimal, type the number of milliseconds that you want
to wait until the service times out, and then click OK. For
example, to wait 60 seconds before the service times out, type
60000.
Quit Registry Editor, and then restart the computer.
Subkey HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSe
t\Control
Name ServicesPipeTimeout
Type REG_DWORD
Data The number of milliseconds that you want to give the
services to start or stop. This value depends on the size of
you FAST/TOOLS configuration. For example, to use a
time-out value of 60 seconds, assign a data value of 60,000
to the ServicesPipeTimeout registry entry. A larger data
value does not decrease your computer's performance.
FAST/TOOLS Components Changing FAST/TOOLS service startup-time
Introduction
FAST/TOOLS Installation Manual Windows A-1
Appendix A: Distributed systems
A.1 Introduction
This appendix describes how to set up 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
Interconnecting components
A-2 FAST/TOOLS Installation Manual Windows
product. One or more of these HMI components exist in a
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 both host
and HMI components).
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 way described above, 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
Distribution of data sets
HMI component.
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 are the HMI components.
Updating data that is redundantly stored in more than one physical
computer system works slightly differently. 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
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 front-
end) 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 front-
end 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
Distributed Item Interface (GIN DII)
functionality, although they cannot 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 off-
line, 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. It is important to note that this default
scheme can be configured via a setup file.
The access scheme works by polling connected FAST/TOOLS nodes to
check for the presence of an items. However this mechanism is
deactivated by default since this generates unnecessary overhead in
system configurations that do not use front-end systems. In a distributed
environment this mechanism must be activated in the setup file of each
system by checking the Check connected all MDUR nodes option in
the GIN 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.
Stepwise configuration actions
A.8 Stepwise configuration actions
1 Make sure that all nodes involved "know" which one of them acts
as the host component.
This can be configured in the "dur.sup" setup file on each node, by
simply specifying the host node number in this setup file.
2 Configure the DURM connections.
Make sure a durm_start (UNIX)/durm_start.cmd (Windows) file is
present on the FAST/TOOLS command directory (../tls/com). This
durm_start(.cmd) file is used by the FAST/TOOLS startup-
procedure 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.
4 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 (Windows) must be changed
manually.
Look in this file for the startup commands for the ITMCPM
executable and uncomment these startup commands.
5 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.
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. If required, re-configure the default access scheme.
Note: When a front-end system is
connected to an existing configuration as a
result of system expansion or upgrade then
the following commands must be run on the
server machine once the new front-end has
been connected:
dsschk -r
dsschk -e -r
Index
FAST/TOOLS Installation Manual Windows 1
Index
A
abbreviations 0-2
ACCESS/FAST 1-1
ALARM/FAST 1-1
audience 0-1
AUDIT/FAST 1-1
B
BUS/FAST 1-1
C
component 1-2
front-end 1-2
HMI 1-2
SDK 1-2
server 1-2
configuration
distributed 1-1
stand-alone 1-1
conventions 0-2
D
DATABASE/FAST 1-1
directory
%TLS_ROOT_PATH% 1-7
com 1-8, 4-5
dat 1-8
exe 1-8
his 1-8
hlp 1-8
inc 1-8
lib 1-8
lst 1-8
sav 1-8
src 1-8
sup 1-8
tls 1-8
tpl 1-8
upg 1-8
directory structure 1-7
distributed configuration 1-1
durecs 4-4
durutl 4-4
E
eqp 4-4
equipment manager 4-4
EQUIPMENT/FAST 1-1
F
FAST/Start 1-2
fast_clear.cmd 4-5
fast_start.cmd 4-5
fast_stop.cmd 4-5
front-end 1-2
functional tools 1-1
H
HISTORY/ FAST 1-1
I
installation
philosophy 1-1
INTEGRATION 1-1
Intel PC 1-1
ITEM/FAST 1-1
L
license numbers 1-9
M
MMI 1-2
O
objectives 0-1
ODBC 1-1
P
phases of installation 1-7
privileges 1-3
PROCESS/FAST 1-1
Index
2 FAST/TOOLS Installation Manual Windows
R
REPORT/FAST 1-1
S
SDK 1-2
server 1-2
setenv.cmd 4-5
Setup File Editor 1-2
SimbaClient 1-4, 3-1
SimbaServer 1-4, 2-1
stand-alone configuration 1-1
StartFASTTOOLS 4-2
V
Visual Basic 1-3
Visual C++ 1-3
W
Windows 1-3
Windows 2000 1-1
YOKOGAWA ELECTRIC
CORPORATION
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: .......................................................................................................................................

Imnttools

Caricato da

Informazioni sul documento

Descrizione originale:

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

Imnttools

Caricato da

Copyright:

Formati disponibili

YOKOGAWA

Potrebbero piacerti anche