Table of Contents
Advertisement
Servers
The server starts
n
A report is generated
n
Server scripts can also include:
Periodic scripts, which run at specified intervals while the server is running
n
Library scripts, which perform specialized functions when called by other server scripts
n
Server scripts don't block point processing, and don't impact other server functions because
they run at a low priority.
Note that server scripting has been optimized for relatively short scripts (less than 30 lines),
and is not designed for implementing control strategies (which should be done in the
controller). If a task is computationally intensive, or requires extensive file handling, you
should write a custom application in Visual C/C++ or Visual Basic.
For more information about server scripts, see the Server Scripting Reference.
Naming rules for computers
Every Experion node (for example, Experion server, Console Station, and Flex Station
computers) must have a unique name and IP address. The unique name must comply with the
following rules:
The length of the node name must comply with the table below.
n
The name must begin with an alphabetic character, such as a to z, or A to Z.
n
The name must not contain spaces or other non-standard characters.
n
The names of redundant server pairs must consist of a common base name (which must
n
also follow the other naming restrictions), plus an A suffix for the primary server and a
B suffix for the backup server.
For example, if the base name of the redundant servers is HSSERV:
The name of the primary server is HSSERVA.
l
The name of the backup server name is HSSERVB.
l
The base name must not end with 'A' or 'B'. (The use of A and B as the last letter in a
n
name is reserved for naming redundant servers.)
To avoid potential confusion, the node name should not end with a '0' or '1', as these
n
numbers are used in hosts files to identify redundant links.
Honeywell 2017
31
Advertisement
Table of Contents
