IDEC WindSRV - Manual (Page 100)

99
www.kepware.com
KEPServerEX5 Help
Descriptions of the General Options dialog parameters are as follows.
 Immediately attempt to establish a Runtime connection on start: This parameter is used to specify
whether the configuration tool will connect to the Runtime when started. It is checked by default. If it is
unchecked, users must manually connect.
 Keep track of the __ most recently used project files: This parameter is used to specify how many project
files will be presented on the MRU (Most Recently Used) list of projects. The valid range is 1 to 16.
 Always backup the last saved project prior to overwriting: Select this check box in order to have the
system automatically make a backup copy of the last saved (*.opf) project before overwriting it with a new
project file. The backup file will be named projectname.opf.bak and will be stored in the \Project Backups
folder.
 CSV Import: The Delimiter setting is used to select the comma-separated variable that the server will use
while importing and exporting tag data in a CSV (comma separated variable) file. Users can select either the
default comma or a semicolon. See Also:
Tag Management .
 Confirmations: This parameter is used to specify the conditions that will force the server to present warning
pop-ups to an operator. When Deleting an object is enabled, all delete operations will invoke a warning popup
to be displayed to the operator that requires confirmation before the delete operation can be completed. When
Disconnect is enabled, all operations that would cause client applications to be disconnected from the server will
invoke a warning popup to be displayed that requires confirmation before the disconnect sequence can be
initiated. If Prompt to save is enabled, a popup will be invoked if the server is being shut down while the
project has outstanding changes. When connected to the Runtime and opening a project, Confirm Runtime
project replacement will warn that the project can be opened and edited offline.
Exit Options
The server supports the Data Access 2.0 server shutdown event. If an operator action will cause connections to OPC
clients that are using the 2.0 Data Access specifications to be lost, the server will issue a server shut down event to
those clients. If the clients are designed to utilize this event, they can properly disconnect their OPC resources. OPC
clients that do not support the server shutdown event may have issues once the server shuts down. When an OPC
server is invoked from a client application, the server automatically loads itself and begins running the last project
used. Normally when the OPC client is finished using the OPC server and disconnects, the OPC server would then exit.
Due to the server's online full-time mode of operation, the operator may have made changes to the project while it was