PowerSCADA
Expert v7.30
Installation and Configuration Guide
November 2012
Legal Information
DISCLAIMER
Schneider Electric (Australia) Pty. Ltd. makes no representations or warranties with respect to this manual and, to the maximum
extent permitted by law, expressly limits its liability for breach of any warranty that may be implied to the replacement of this manual
with another. Further, Schneider Electric (Australia) Pty. Ltd. reserves the right to revise this publication at any time without incurring
an obligation to notify any person of the revision.
The Example Projects are provided to you for the purpose of illustrating how the SCADA software 7.30 could be used in an operational
environment ("the Purpose").Schneider Electric grants you a royalty free, non exclusive, non transferable license to use the example
projects installed with your SCADA software version 7.30 (“the Example Projects”) for the Purpose only.
The Example Projects are provided by Schneider Electric as part of the SCADA software version 7.30 on an "as is" basis and Schneider
Electric does not guarantee the reliability, serviceability or function of the Example Projects.
Should you modify the Example Projects, you bear the risk of any use of such modified Example Projects.
Schneider Electric gives no express warranties, guarantees or conditions and to the extent permitted under applicable laws, Schneider
Electric disclaims all implied warranties, including any implied warranties of merchantability, fitness for a particular purpose or noninfringement of third parties’ intellectual property rights.
Schneider Electric shall not be liable for any direct, indirect or consequential damages or costs of any type arising out of any action
taken by you or others related to the Example Projects.
COPYRIGHT
© Copyright 2012 Schneider Electric (Australia) Pty. Ltd. All rights reserved.
TRADEMARKS
Schneider Electric (Australia) Pty. Ltd. has made every effort to supply trademark information about company names, products and
services mentioned in this manual.
Citect, CitectHMI, PowerSCADA Expert and CitectSCADA are either registered trademarks or trademarks of Schneider Electric (Australia) Pty. Ltd. .
Pelco, Spectra, Sarix, Endura, are registered trademarks of Pelco, Inc.
IBM, IBM PC and IBM PC AT are registered trademarks of International Business Machines Corporation.
MS-DOS, Windows, Windows NT, Microsoft, and Excel are either registered trademarks or trademarks of Microsoft Corporation in the
United States and/or other countries.
DigiBoard, PC/Xi and Com/Xi are trademarks of Digi International Inc.
Novell, Netware and Netware Lite are either registered trademarks or trademarks of Novell, Inc. in the United States and other
countries.
dBASE is a trademark of dataBased Intelligence, Inc.
All other brands and products referenced in this document are acknowledged to be the trademarks or registered trademarks of their
respective holders.
GENERAL INFORMATION
Some product names used in this manual are used for identification purposes only and may be trademarks of their respective companies.
November 2012 edition for PowerSCADA Expert Version 7.30.
Manual Revision Version 7.30.
PLEASE NOTE
Electrical equipment should be installed, operated, serviced, and maintained only by qualified personnel. No responsibility is assumed
by Schneider Electric (Australia) Pty. Ltd. for any consequences arising out of the use of this material. © 2012 Schneider Electric (Australia) Pty. Ltd. . All Rights Reserved.
Validity Note
The present documentation is intended for qualified technical personnel responsible for the implementation, operation and maintenance of the products described. It contains information necessary for the proper use of the products. However, those who wish to
make a more "advanced" use of our products may find it necessary to consult our nearest distributor in order to obtain additional information.
The contents of this documentation are not contractual and in no way constitute an extension to, or restriction of, the contractual warranty clauses.
Contact Schneider Electric today at www.schneider-electric.com
Contents
Legal Information
1
Contents
3
Safety Information
5
Chapter 1: Introduction
7
About This Guide
Purpose
Maintaining System Currency
Audience
Chapter 2: Migration
Changes in Functionality
Resolving cluster context with unique tag names
Network Support
New Features
Introduced in v7.0
Introduced in v7.10
Cicode Functions From v7.0
Introduced in v7.20
Introduced in 7.30
The Migration Process
Low Impact Changes
Changes Impacting Migration
Migration Aids
Upgrading a Runtime-only Installation
Chapter 3: Installation Description
Task Selection Dialogs
7
7
7
7
9
9
9
9
10
11
13
17
17
22
25
25
26
28
29
31
31
3
Contents
Installation Profiles
Documentation Installation
Add-ons Installation
Communication Drivers
Chapter 4: Installation Requirements
All Core Components
System Hardware
System Software
Microsoft IIS Compatibility
System Software
Software Licensing
Updating Your Hardware Key
PowerSCADA Expert License Point Count
Demo Mode
Chapter 5: Installation
The Installation Process
Chapter 6: Configuration
Local Area Network Configuration
Network Communications Overview
Configuring Communications Over a WAN
Web Server Configuration
The IIS Virtual Directory
Setting Up Security
Web Client user account types
Configuring Security Using IIS
Testing the Web Server Security Settings
Logging on to the Web Server
Index
4
31
33
33
34
35
35
35
36
37
38
39
39
40
40
43
43
45
45
46
47
47
48
49
49
50
53
54
57
Safety Information
Hazard categories and special symbols
The following symbols and special messages may appear in this manual or on the product to warn of potential hazards or to call attention to information that clarifies or simplifies a procedure.
Symbol
or
Description
The addition of either symbol to a “Danger” or “Warning” safety
label indicates that an electrical hazard exists which will result in
personal injury if the instructions are not followed.
This is the safety alert symbol. It is used to alert you to personal
injury hazards. Obey all safety messages that follow this symbol to
avoid possible injury or death.
DANGER indicates an imminently hazardous situation, which, if not avoided, will result in
death or serious injury.
WARNING indicates a potentially hazardous situation, which, if not avoided, can result in
death or serious injury.
CAUTION indicates a potentially hazardous situation which, if not avoided, can result in
minor or moderate injury.
NOTICE
NOTICE used without a safety alert symbol, indicates a potentially hazardous situation
which, if not avoided, can result in property or equipment damage.
Please Note
5
Safety Information
Electrical equipment should be installed, operated, serviced, and maintained only by
qualified personnel. No responsibility is assumed by Schneider Electric (Australia) Pty.
Ltd. for any consequences arising out of the use of this material.
Before You Begin
PowerSCADA Expert is a Supervisory Control and Data Acquisition (SCADA) solution.
It facilitates the creation of software to manage and monitor industrial systems and processes. Due to PowerSCADA Expert's central role in controlling systems and processes,
you must appropriately design, commission, and test your PowerSCADA Expert project
before implementing it in an operational setting. Observe the following:
UNINTENDED EQUIPMENT OPERATION
Do not use PowerSCADA Expert or other SCADA software as a replacement for PLC-based
control programs. SCADA software is not designed for direct, high-speed system control.
Failure to follow these instructions can result in death, serious injury, or equipment damage.
LOSS OF CONTROL
l
l
l
l
l
The designer of any control scheme must consider the potential failure modes of control paths and, for certain critical control functions, provide a means to achieve a safe
state during and after a path failure. Examples of critical control functions are emergency stop and overtravel stop, power outage and restart.
Separate or redundant control paths must be provided for critical control functions.
System control paths may include communication links. Consideration must be given
to the implications of unanticipated transmission delays or failures of the link.
Observe all accident prevention regulations and local safety guidelines. 1
Each implementation of a control system created using PowerSCADA Expert must be
individually and thoroughly tested for proper operation before being placed into service.
Failure to follow these instructions can result in death, serious injury, or equipment damage.
1. For additional information, refer to NEMA ICS 1.1 (latest edition) "Safety Guidelines
for the Application, Installation, and Maintenance of Solid State Control", and to NEMA
ICS 7.1 (latest edition) "Safety Standards for Construction and Guide for Selection, Installation and Operation of Adjustable-Speed Drive Systems" or their equivalent governing
your particular location.
6
Chapter 1: Introduction
About This Guide
Purpose
This document is a guide for installing PowerSCADA Expert. It describes the installation
process and optional components which can be installed in each environment.
The configuration section provides an overview of using PowerSCADA Expert in a Local
Area Network (LAN), a Wide Area Network (WAN), and as a Web Server.
It includes information on the following aspects of installing PowerSCADA Expert:
l
"Migration"
l
"Installation Description"
l
"Installation Requirements"
l
"Installation"
l
"Configuration "
Maintaining System Currency
After you have completed the installation and configuration of PowerSCADA Expert and
deployed it as your production system, it is very important that you keep your software
up to date. Schneider Electric (Australia) Pty. Ltd. will periodically publish updates in
the form of Service Packs, Hot Fixes or Advisories relating to safety, security and functionality of PowerSCADA Expert. These updates are available from the Knowledge Base
page of the “MyCitect” web site or http://www.citect.schneider-electric.com/servicepacks.
We especially recommend that you nominate a person in your organization to refer, and
subscribe, to the RSS feeds for Safety and Security, as well as the latest articles on the
web site.
Audience
This document is primarily for those who install PowerSCADA Expert, either on a single
workstation or on a network. It is also useful for system administrators and new users of
PowerSCADA Expert.
7
Chapter 1: Introduction
8
Chapter 2: Migration
This chapter describes changes in functionality and new features introduced in PowerSCADA Expert 7.0, 7.10, 7.20 and 7.30 and how it may effect your installation and
migration from a previous version. Migration information in this chapter covers only
migration from PowerSCADA Expert 6.x to 7.30. If you are running a version earlier
than 6.10 it is recommended that you upgrade to v 6.x before migrating to v7.30.
Changes in Functionality
Resolving cluster context with unique tag names
With the release of version 7.30, PowerSCADA Expert will allow tags that do not have a
cluster context specified to be automatically resolved if every tag name in the project is
unique. This means customers who have used a unique tag naming convention will be
able to migrate a project to a multi-clustered system without having to specify cluster
context.
As further development of a project takes place, ambiguous tag resolution will continue
successfully as long as unique tag names are maintained. PowerSCADA Expert's existing behavior will apply for any tags that are not unique across all clusters, which means
by default #COM will be displayed for a tag if cluster context can not be determined.
Note: This capability is controlled via the parameter [General]TagDB which is enabled by default.
Network Support
In order to incorporate the many benefits provided with the introduction of the New
Communications Architecture in PowerSCADA Expert 7.0, it was necessary to remove
the support for NetBIOS network communications. PowerSCADA Expert 7.10 and later
only supports TCP/IP networking.
If you are currently using TCP/IP as your network protocol you may ignore this section.
However, if you currently implement NetBIOS, change your network communication
over in your current version of PowerSCADA Expert to TCP/IP before installing PowerSCADA Expert 7.30.
9
Chapter 2: Migration
Converting from NetBIOS to TCP/IP
This conversion is a two part operation. The first part is to convert each of your servers
(Alarms, Reports, Trends). For the transition time that you are performing the conversion
of your entire system you need to maintain network communication between your
servers and your clients, this requires that your servers support both NetBIOS and
TCP/IP for a brief period. Do this by directly editing the appropriate parameter in the
LAN section of the Citect.ini file on each server. This can be done by using the Computer
Setup Editor.
In order to support both NetBIOS and TCP/IP set the TCP/IP parameter to 1 in the
Citect.ini file as shown below.
[LAN]
NetBIOS =1
TCPIP =1
Also set the server parameters in the DNS section as described in the v6.0 online help
under the topic "Using TCP/IP for network communications " under the topic "Using
PowerSCADA Expert on a Network".
Once you have configured your servers to use TCP/IP (and maintain NetBIOS) edit the
Citect.ini file on each of your client machines, set TCPIP=1 and NetBIOS=0 for each of
those clients. You do not need to maintain NetBIOS on the clients as they are now communicating with the servers using TCP/IP.
It is essential to set up your servers to use TCP/IP before you set up your client
machines. Once you have finished the conversion on all client machines, return to the
Citect.ini file of each server and set the NetBIOS parameter to 0, so disabling NetBIOS on
each server as this is now redundant.
On completion of the conversion described above to your existing system to use TCP/IP,
you can then continue with the remainder of the "The Migration Process" and installation procedure to 7.30.
New Features
PowerSCADA Expert 7.30 includes the following new features or changes in functionality. In many cases these new features will not impact the installation or initial configuration. However, some of them may impact your project configuration and
functionality. Once you have installed this version, refer to the online help for information on how to reconfigure your projects to take advantage of the new features and
improved functionality.
10
Chapter 2: Migration
Introduced in v7.0
PowerSCADA Expert 7.0 incorporates the following new features
Improved Support for Clustering
The concept of "clustering" was introduced in an earlier version of PowerSCADA Expert.
The original concept allowed the "grouping" of duplicated elements, and gave you the
ability to cluster Alarms, Reports and Trends servers. However, there were limitations.
The concept of clustering has since evolved and has the advantage of greater flexibility
and improved performance. Each of the servers (IO, Alarm, Trend and Report) has a
unique name and is part of a Cluster. Each Cluster has a unique name and clients can
refer to clusters by it.
A PowerSCADA Expert project can now include separate clusters allowing for geographical or logical divisions to be implemented in a single project.
Configure PowerSCADA Expert's clustering as a direct reflection of the system that is to
be deployed, and in particular:
l
The requirements for the system
l
The physical layout of the facility
l
The strategy for maintenance and deployment of the system
Online Changes for Clients
Server decoupling allows changes to be implemented at runtime on clients without a
shutdown of the client being required. Regardless of whether a server requires a restart
for an online change, the client does not require a restart.
Clients currently contain a copy of Trend, Alarm and Variable Tags which has to match
the server copy. In v7.0, the need for the variable tag configuration to be loaded by the
clients has been removed. The client retrieves the configuration from the server when
required and is notified by the server when changes occur.
The following list describes the online changes that can be made without the client
machine having to be restarted:
l
Adding Trends, Alarms, Alarm categories and Address based Variable Tags
l
Modifying a subset of properties of Trends, Alarms and Alarm categories
l
Modifying Address based Variable Tag properties
l
Deleting Address based Variable Tags
l
Adding and deleting pages and PAV files (except the current one)
11
Chapter 2: Migration
l
Modifying pages and PAV files (except the current one)
l
Adding, deleting or modifying user profiles
New Communications Architecture
A new publish-subscribe architecture removes much of the need for polling. It is an enabling technology and a step towards improved performance, project deployment, server
side online changes, and discovery services.
Local Variables
Memory I/O devices have been removed from PowerSCADA Expert 7.0 and a new tag
has been introduced called Local Variable to replace the “Memory PLC” based variable
tag. A Local Variables allows you to store data in memory when you start your runtime
system. Local variables are created each time your runtime system starts, and therefore
do not retain their values when you shut down your system. They can be of any data
type supported by PowerSCADA Expert.
Each process has its own copy of each local variable configured in the project, the values
in a local variable are available only to the process that wrote them.
Publish Alarm Property
Alarm devices were defined as devices with their Protocol field set to "Alarm". The function of these devices are now configured on an Alarm Server by setting the “Publish
Alarm Properties” property to True.
Memory Mode for Devices
Devices can now be run in simulation mode. When configuring an I/O device, you have
the option to set memory mode. This means that the I/O device will be created in memory and its values stored in memory at runtime.
This is useful when you are configuring a system for the first time, as you can design
and test your system before using a physical I/O device in the system.
As with local variables, the values of an I/O device in memory mode are not retained
when you shut down.
Persist Mode for Devices
When configuring an I/O device, you have the option to set persist mode. This means
that the value of each variable in the I/O device is stored on the computer’s hard disk.
Since the values are saved to disk, when you restart your system after a system becomes
inoperative or a shutdown, the latest values are immediately available.
Persist mode is useful for status information or predefined data that is required as soon
as the system restarts.
Improved Hardware Alarms
12
Chapter 2: Migration
The limitation in previous releases of PowerSCADA Expert of only a single alarm from
multiple alarm situations being displayed has been lifted. All and any alarms are now
displayed simultaneously, allowing for immediate response to multiple situations.
Event Driven Cicode
Cicode can now be triggered by the change of a specific tag. This improves the efficiency
of the PowerSCADA Expert system by removing the need to poll for changing tag
values.
Publisher-Subscriber Model
PowerSCADA Expert now uses a Publisher-Subscriber data acquisition model. Client
computers subscribe to configured tags and receive notification when the tag values
change. Cicode functions can also be triggered by the change of a tag, removing the need
to poll, and improving the efficiency of the system.
Dual Network Support
Previous PowerSCADA Expert versions have been able to support redundant networks
via NetBIOS. From v7.0, users can specify multiple IP addresses for each server using
only TCP/IP, providing native support for network redundancy.
Project-Based Network Configuration
From v7.0, the project topology is embedded in the project, and network configuration
can be performed from within the Project Editor. Servers and their IP addresses are set
up in the Network Addresses dialog in the Project Editor.
This means that physical computers in the system can easily be changed. As long as the
IP address or computer name of the new machine is the same as the one being replaced,
the new computer will be able to immediately take the same role.
Introduced in v7.10
PowerSCADA Expert 7.10 incorporates the following new features
New Location for Configuration and User Files
To improve the security of your SCADA system and provide compatibility with Windows Vista, PowerSCADA Expert 7.10 can now be run under a standard user account
(i.e. one without administrator privileges). To achieve this, some modifications to the
location of files installed by PowerSCADA Expert have been made. These changes apply
to all supported operating systems. Specifically, it is no longer possible for standard
users to write to the Program Files or System directories, which means the citect.ini file
cannot live in the Bin or Windows directory, and the User folder cannot live under Pro-
13
Chapter 2: Migration
gram Files. It is advisable that you accept the default installation path when installing ,
or that your chosen User/Data folder is writable by standard users.
File type
Configuration files such as the citect.ini file
Platform
Install
Path
PreVista
Vista
User directory
PreVista
Vista
Data directory
PreVista
Vista
Log files. All log files produced by drivers are written to a sub-folder
called ‘Drivers’.
PreVista
Vista
Windows® Integrated Security
In PowerSCADA Expert 7.10 you have the ability to incorporate PowerSCADA Expert
users and security options with the standard Windows security system. Of course you
can still use the PowerSCADA Expert native security if you prefer to define users in the
project and logon to PowerSCADA Expert runtime.
Using the integrated Windows security feature, the Windows user can logon to PowerSCADA Expert runtime with runtime privileges configured within the project.
Multi-Signature Support
PowerSCADA Expert 7.10 provides the facility for up to four users to approve an action
or tag write operation using the new Cicode functions MultiSignatureForm and MultiSignatureTagWrite.
Two further Cicode functions, VerifyPrivilegeForm and VerifyPrivilegeTagWrite, enable
you to restrict access to a specific action or tag write for a user with a specific set of privileges.
Edit .dbf Files in Microsoft Excel
PowerSCADA Expert allows you to edit and save .dbf files (tables) used inPowerSCADA
Expert by opening them in Microsoft® Office Excel®.
14
Chapter 2: Migration
Microsoft Office Excel 2007 and later does not allow you to save files in .dbf format
though you may open and edit them using the File > Open command. In order to overcome this limitation PowerSCADA Expert now includes an Add-In for Microsoft Excel
called ProjectDBFAddIn. When this Add-In is loaded into Excel, it allows you to browse,
open, edit and save .dbf files in the correct format.
Enhanced Driver Installation
The installation of PowerSCADA Expert prior to v7.10 installed all the available communication drivers automatically with the installation of the product. From v7.10 the
installation of these drivers is performed at the final stage of the product installation
using a separate installation process. This installation process allows you to select
individual drivers that you want to install, specific to your system and its I/O Devices.
Note: There are certain drivers that the product installation will install that are necessary for PowerSCADA Expert to function correctly. These will be installed automatically as in previous releases.
New Font Selection for Graphics Button
In previous releases of PowerSCADA Expert, you were not able to change the properties
of text such as font, size, style on buttons in the Graphics Editor. This inability to configure the button text properties led to graphics with text from different source objects
having different font settings on the same page, which appears aesthetically untidy and
inconsistent on the runtime displays.
From v7.10 the text displayed on a button object can be configured in the same manner
as other PowerSCADA Expert text objects within the Graphics Editor and the automation
interface. This will allow you to present a more polished and consistent user interface to
meet individual project runtime presentation requirements.
When migrating from a previous release, button object text properties are preserved and
converted to the new button object text properties with the appropriate default property
values automatically placed in the new configuration such as Font=Arial, Size=12, Alignment=centre, style=regular, etc.
Microsoft® Windows Vista® Support
PowerSCADA Expert 7.10 and later has achieved the Microsoft "Works with Windows
Vista" certification. However, merely meeting the requirements of this certification was
not sufficient to make PowerSCADA Expert functional on Vista. A number of other
changes were required to achieve satisfactory functionality on the Vista operating system.
15
Chapter 2: Migration
v7.10 satisfies many of the requirements of the "Certified for Windows Vista" certification, and by having this level of qualification we are confident that you will find
minimal differences when running the product on the Vista operating system compared
to previous operating systems.
New Alarm Field Enhancements
There are four enhancements to alarm fields:
l
Runtime writes to custom alarm fields
l
Alarm summary field changes
l
Alarm display field changes
l
Alarm paging
Runtime Writes to Custom Alarm Fields
It is now possible to write to the eight custom alarm fields during runtime. In previous
releases these fields could really only be used for alarm filtering.
Alarm Summary Field Changes
Alarm Summary Fields can now be used to format an alarm display or alarm log
device. In addition any Alarm Display Field can be used in your alarm summary, apart
from State.
New Alarm Summary Fields
Field Name
Description
{SumType,n}
Type of alarm summary (similar to alarm display "Type").
Alarm Display Field Changes
Now any alarm display field can be used for any type of alarm. Where not applicable for
a particular alarm type, zero or an empty string will be displayed.
Alarm Paging
The PowerSCADA Expert alarm facility constantly monitors equipment data and alerts
operators of any equipment errors (sometimes called "faults"), or alarm condition. When
an alarm is triggered it is displayed on the standard alarm display page. The operator
has to be continuously sitting in front of an HMI monitoring the system. PowerSCADA
Expert 7.10 provides the facility to link alarms with a remote paging system for operators.
16
Chapter 2: Migration
Two Alarm Properties have been added to enable PowerSCADA Expert to interface with
any third-party paging system. The Paging property is a flag to indicate that the alarm is
going to be paged, the PagingGroup property is a freeform text field indicating the
sequence of people to notify in the event the alarm occurred.
See your third-party paging system documentation for information on how to interface
with PowerSCADA Expert.
New Time Synchronization Service
In order to maintain time synchronization PowerSCADA Expert 7.10 installs a Windows
service called TimeSyncService, which runs under the built-in LocalSystem account. This
replaces the existing time synchronization server which is not compatible with Windows Vista. This purpose of this service is to maintain the time on the local computer
against one or more time sources.
A Time synchronization utility is provided by PowerSCADA Expert to assist you to configure time synchronization, and control the service as part of your administration environment. This utility requires administrator rights as it configures and controls a
windows service. When run on Windows Vista with User Access Control (UAC) on, you
will be prompted to elevate to an administrator. When run on earlier operating systems,
the utility will exit after displaying a message if the current user is not an administrator
on the local machine.
Cicode Functions From v7.0
Changes have been made to Cicode functions from PowerSCADA Expert 7.0 onwards.
These changes incorporated functions that have been added, modified or made redundant. For a detailed explanation of these changes refer to the “What's New in PowerSCADA Expert” topic of the PowerSCADA Expert online help.
Introduced in v7.20
Improved Installation process
The installation process of PowerSCADA Expert has been improved to simplify the operation and guide the user through the installation by use of Installation Profiles and the
creation of default component selections. Whilst still allowing for complete flexibility for
the experienced user, the complexity and multiple installation paths and options have
been greatly reduced. The installer has been enhanced to allow the installation of a runtime-only version of the product. This allows the runtime environment to be installed
without the project tools of the PowerSCADA Expert Integrated Environment. The Runtime Only installation provides not only a smaller installation footprint but also the abil-
17
Chapter 2: Migration
ity to set up workstations which do not allow project configuration. This automatically
improves the security of the system configuration.
Control SCADA Client Connections
Two Citect.ini parameters determine how a client will behave if it is unable to maintain
a connection with a primary Alarms, Reports or Trends server. Each server type has
access to these parameters:
[Type.<ClusterName>.<ServerName>]Priority
and
[Type.<ClusterName>.<ServerName>]DisableConnection
where Type is the relevant server type (Report, Trend or Alarm).
Dynamically Optimized Writes
Following the move to the new Publish-Subscribe infrastructure with v7.0, a number of
customers were adversely affected by a change in the way the product behaves in
respect to combining multiple writes together. This change is generic across ALL drivers
and specific issues have been raised with in regard to HITACHI, MODBUS and OPC.
In v7.20 changes have been made to the way that writes are performed at the I/O Server
in order to restore the pre-v7.0 behavior.
These changes result in a similar level of blocking as occurred in previous versions. It
does not guarantee that writes will be blocked, but it is more than likely that they will be
if they are initiated close enough together.
This will also allow use of the re-instated Citect.ini parameter [IOServer]BlockWrites in
order to choose whether to use the Block Writes functionality.
Graphics Enhancements
Enhancements have been made to how you can configure graphic pages and the objects
you place on the page. These enhancements can be used in the creation and implementation of Genies and Super Genies.
Improved Security
Security enhancements have been implemented in this release to address known security
issues from previous versions and to reduce the potential risk of malicious attack. These
security enhancements include, improved inter-operability through the introduction of
new INI parameters, trusted network authentication, and the addition of assigning roles
to runtime users, as you currently do for Windows users.
New Example Project
18
Chapter 2: Migration
The Example Project has been updated to demonstrate the new tab menu templates that
are available with v7.20.
The project includes a "What's New?" menu to introduce some of the new features
offered. This menu links to pages that demonstrate:
l
the use of tag extensions and tag properties on graphics pages
l
server monitoring and the ability to implement online changes for alarm and trend
servers
l
multi-monitor support
l
Instant Trending using the Process Analyst
The new content complements pages drawn in from the existing Example Project and
CSV_Example Project, which are now superseded.
To view the new Example Project, select and run it from Citect Explorer. For more information, use the help button included in the project on the main navigation panel.
OFSOPC Driver
The release of PowerSCADA Expert coincides with the availability of the OFSOPC Driver
for Schneider Electric's OPC Factory Server (OFS).
OFS is a foundation component for communication with certain Schneider Electric PLCs.
The OFSOPC Driver allows PowerSCADA Expert to tightly integrate with OFS, minimizing the amount of configuration required for an end-to-end Schneider Electric system.
You can install the OFSOPC Driver and its supporting documentation via the Driver
Selection page of the PowerSCADA Expert installer.
Pelco Camera Support
This feature adds two buttons to the Graphics Builder toolbox, which will allow two of
the Pelco Camera ActiveX controls to be easily added to a graphics page. This control
provides an ActiveX component that will connect to Pelco IP cameras with configurable
bandwidth usage for slow network connections and auto-resizes video to fit the ActiveX
control size.
The two ActiveX controls supported are:
Video Streaming - Fully Resizable, multiple bandwidth levels, MPEG4 Video, returns
the camera name and model.
Camera Control PTZ (Pan, Tilt and Zoom) - Communicates with DVRs and IP cameras.
Featuring pan zoom and tilt, iris, focus, presets, patterns and adjustable speed.
Performance Improvements
19
Chapter 2: Migration
The architecture of v7.20 includes a new threading model that offers significant performance improvements. The new Platform Task Framework (PTF) defines an explicit
threading environment for each subsystem, providing a standard protocol for work to be
created and passed between them.
The performance improvements have been implemented in a way that retains all existing functionality.There is no changes to the configuration or operation of a system, just
performance benefits and improved stability.
Persisted I/O Memory Mode
Many customers use DiskPLC I/O devices to provide system-wide global variable tags
that are managed by I/O Servers and are persisted to disk to maintain their latest values.
DiskPLC I/O devices take advantage of the standard I/O system redundancy features,
such that, if one I/O server is unavailable, another can provide client(s) with tag values.
They also perform a level of synchronization by using features such as standby write
and by providing redundant paths to the persisted binary data files, so that, at startup of
an I/O server, the latest value can be read into the system from the most recently modified data file.
However, there is no synchronization when network connections are inoperative and
regained, resulting in several scenarios in which redundant DiskPLC I/O devices can
end up with different values for the same tag.
With v7.20, the new feature of persistence when applied to I/O Devices in memory
mode, provides an improved alternative to a DiskPLC device, as there is full synchronization in scenarios involving one of the servers becoming unavailable for a period
of time. Persistence is enabled using the Persist field in the extended section of the I/O
Devices Properties dialog.
Post Compile Commands
After a project has compiled successfully you can execute an optional command, script
or batch file. This offers useful functionality if you have tasks that could be automated
after a successful compile. This provides an expansion point for you to add your own
script or command to perform additional tasks. You can also launch an optional command, script or batch file to execute after an unsuccessful compile.
Server Side Online Changes
To improve the ability to change configurations on a live system without having to
restart the servers, PowerSCADA Expert now provides the facility to reload server configurations during runtime either programmatically or using the Runtime Manager.
Microsoft® Windows 7 Support
20
Chapter 2: Migration
PowerSCADA Expert also supports the Microsoft Windows 7 and Microsoft Windows
Server® 2008 R2 operating systems. The changes to PowerSCADA Expert undertaken in
the v7.10 release to support Windows Vista significantly reduced the changes that were
required to support Windows 7 and Server 2008 R2. Previous Vista users will experience
no functional differences when migrating to Windows 7. However if you migrate to Windows 7 from Widows XP there are functional differences with PowerSCADA Expert
between XP and Vista, as described in “New Locations for Configuration and Project
Files” in the PowerSCADA Expert online help.
Supportability Enhancements
Supportability Enhancements have been added to provide easier access to the diagnostics functionality of the product. Although the enhancements were primarily introduced to assist Technical Support personnel with system analysis, they have resulted in
many benefits to the end user. These include:
l
Timestamp harmonization across all log files.
l
Additional [Debug] parameters to support category and severity filtering (see
Citect.ini Parameters in v7.20).
l
Support for online logging adjustments using the new SetLogging() and GetLogging()
Cicode functions.
l
A set of parameters that can be modified while online due to periodic or an ondemand read of the citect.ini file during runtime.
Additionally, the home page of the Computer Setup Editor now includes a link to the
Logging Parameters page, which provides comprehensive instructions for the configuration of logging.
New Tab Menu Templates
To improve the user interface of projects and integrate the look and feel with the latest
Windows® systems, PowerSCADA Expert now features new templates with a tab style
menu system. Main menu items can be represented as tabs along a menu bar, below
which subsidiary items are displayed in a ribbon. New projects have the new Tab_Style_
Include templates already available to them.
Tag Extensions
With the addition of Tag Extensions in v7.20, the variable tag can now represent data as
a collection of elements, and each of these elements can contain a collection of items. For
example, the tag variable data received from the PLC can be represented as the “Field”or
"Valid" element, which contains the following items within the "VQT Tag Element":
v- the value of the tag.
vt- the timestamp of when the value last changed.
21
Chapter 2: Migration
q- the quality of the value , GOOD, UNCERTAIN or BAD. The Quality variable
can be further identified using Cicode QUALITY functions.
qt- the timestamp of when the quality last changed.
t- the timestamp of when the element was last updated.
Introduced in 7.30
NOTICE
The minimum and recommended hardware requirements have changed in this release.
Upgrading customers should load test their system as part of their upgrade procedure to
ensure that the hardware in use is adequate for the needs of their system.
The following list of new features introduced in this release is only a brief description.
For more details, and links to using the features in your projects, refer to the "What's
New in PowerSCADA Expert 7.30" page in the main PowerSCADA Expert help.
ActiveX Data Objects(ADO)
Vijeo Citect v7.30 features a new interface between SCADA and your SQL database
using ADO.NET. If your project currently uses SQL Cicode commands, then the existing
behavior will remain unchanged. A number of new Cicode commands have been introduced in the following categories:
l
Creation/connection - functions that separate the creation of DB connection objects
from connection initialization, and the ability to work with connected and disconnected recordsets
l
Multiple recordsets per connection - functions that enable users to obtain and use
handles to recordsets
l
Parameterization - functions that provide a more secure way of building SQL queries
l
Multiple queries per connection - functions that enable users to obtain and use handles to queries
Alarm Enhancements
There have been numerous improvements made to alarms in PowerSCADA Expert.
Improvements include:
22
l
Active alarm and historical alarm events synchronization
l
Handling of event information with the introduction of a new sequence of events
page
l
Ability to insert a user event into the event journal
Chapter 2: Migration
l
Named filter
l
Sorting of alarms and events
l
Dynamic alarm count at runtime
l
User comments on events
l
Can configure more than 65535 alarms for each type of alarm
l
New alarm template with equipment tree view
Refer to the topics Alarm Server Upgrade and Migrating Alarm Event History for information you need to know before upgrading.
Equipment Hierarchy
The concept of "equipment" was introduced in 7.20 as a means of applying an hierarchical structure to SCADA objects specified in your system. In the 7.30 release, it has
been expanded to form logical groups of SCADA objects by linking equipment to tags.
Each item in the equipment database can be assigned a place in a hierarchy of equipment. The hierarchy is based on the equipment name, and each item of equipment is specifically identified to signify it's level in the hierarchy.
This provides the opportunity to browse, find, identify and quantify the values of tags
and other objects assigned to a piece of equipment using a number of new or modified
CtAPI and Cicode functions.
Importing Equipment
The concept of equipment has been introduced in 7.30 to provide a way of browsing,
finding, identifying and quantifying the values of tags and other objects assigned to a
piece of equipment.
In addition, equipment can be created by importing them in much the same way as tags
can be imported using TagGen. An XML template is used to specify the fields of input
and output databases, and define filters and transformation rules that create equipment
and associated alarm, trend, report or variable tags from existing database fields.
New Licensing Protection Method
PowerSCADA Expert now supports two different software licensing protection models to
help maintain license conformance:
l
Sentinel Licensing products which are the existing methods used by the product.
o
l
Using a SafeNet hardware dongle
A new licensing mechanism which is introduced with 7.30 as part of the Schneider
Electric offering.
o
Using a FLEXERA softkey
23
Chapter 2: Migration
In both cases the hardware dongle is a physical key that plugs into either the parallel
port or USB port of your computer, and contains details of your user license, such as
type and I/O point count.
You may choose to use either the Sentinel licensing method, or the new FLEXERA
method.
To install the new licensing manager, select it from the PowerSCADA Expert Core Components dialog at the beginning of your installation.
OPC DA Server
OPC (OLE for Process Control) is a set of communication standards maintained by the
OPC Foundation for the industrial automation industry. OPC provides a common platform for applications to share data from typically disparate sources, such as PLCs and
databases, without the need to comprehend native protocols.
The OPC Data Access solution (OPC DA) provides specifications for client and server
applications that are focused on the continuous communication of real-time data. To this
end, Vijeo Citect supports a runtime OPC DA server that implements mandatory OPC
DA v2.05 and OPC DA v3 interface specifications.
This allows PowerSCADA Expert to provide real-time data to any compliant OPC DA
clients, including applications such as AMPLA, OSI-PI and Historian.
Schneider Electric Software Update
Schneider Electric Software Update is a software tool that has been designed to provide
the latest news and updates of Schneider Electric software.
You can adapt it to your individual requirements by:
l
Configuring it to check for only those Schneider Electric software updates that you
are really interested in, even from PCs other than where any of your Schneider Electric software products are installed.
l
Scheduling the intervals it checks for updates according to your needs.
To install the Software Update select it from the PowerSCADA Expert Core Components
dialog at the beginning of your installation.
Supportability Enhancements
Further Supportability Enhancements have been added to PowerSCADA Expert to harmonize logging features of the product. Although the enhancements were primarily introduced to assist Technical Support personnel with system analysis, they have resulted in
many benefits to the end user.
Scheduler
24
Chapter 2: Migration
The Scheduler was first released in PowerSCADA Expert 7.20 SP3. It is a calendar based
programming tool that allows you to manipulate equipment within a Vijeo Citect
project. It can be used to create a sequence of automatically executed commands, delivering a valuable scheduling tool for applications.
Tag Browsing
You can now browse a list of variable tags at runtime. You can also browse selected runtime and configuration fields of the tag via Cicode and CtApi, and while browsing you
can apply a filter using a set of predefined field names using regular expressions.
The Migration Process
UPGRADE ALTERS COMMUNICATIONS CONFIGURATIONS
After upgrading, confirm and adjust the configuration of all I/O devices in your project.
Failure to follow these instructions can result in death, serious injury, or equipment damage.
There are a number of considerations that you need to make before migrating your
projects to PowerSCADA Expert 7.30 from v 6.x. These considerations relate primarily to
the introduction of new features, or changes to existing functionality, as described earlier.
Low Impact Changes
The following list identifies the changes which will have low impact on your existing
PowerSCADA Expert 6.x projects when they are migrated to this version. These changes
can optionally be incorporated into your existing projects during later development, or
may be ignored if they are of no benefit to the way that PowerSCADA Expert is used in
your organization.
l
Improved Support for Clustering
l
Online Changes for Clients
l
New Communications Architecture
l
Memory Mode for Devices
l
Persist Mode for Devices
l
Improved Hardware Alarms
25
Chapter 2: Migration
l
Event Driven Cicode
l
Windows® Integrated Security
l
Multi-Signature Support
l
Edit .dbf Files in Microsoft® Excel
l
New Font Selection for Graphics Button
l
New Alarm Field Enhancements
l
Runtime Writes to Custom AlarmFields
l
Alarm Summary Field Changes
l
Alarm Display Field Changes
l
New Time Synchronization Service
l
Improved Installation process
l
Control SCADA Client Connections
l
Dynamically Optimized Writes
l
Graphics Enhancements
l
New Example Project
l
OPC Factory Server (OFSOPC) Driver
l
Pelco Camera Support
l
Performance Improvements
l
Persisted I/O Memory Mode
l
Post Compile Commands
l
Server Side Online Changes
l
Supportability Enhancements
l
Tab Menu Templates
l
Tag Extensions
Note: It is optional for you to utilize the extensive capability of clustering, however,
after you have installed PowerSCADA Expert 7.30 you need to create a minimum of
one cluster. For details on creating a cluster refer to the “Upgrading Procedure” topic
in the PowerSCADA Expert online help after you have installed the product.
Changes Impacting Migration
The following list identifies functionality changes that may impact migration of your
existing projects to PowerSCADA Expert 7.30.
26
Chapter 2: Migration
l
Network Support
l
Local Variables
l
Publish Alarm Property
l
Dual Network Support
l
Project-Based Network Configuration
l
Parameters and Cicode Functions
l
New Location for Configuration and User Files
l
Enhanced Driver Installation
l
Microsoft® Windows Vista® Support
l
Microsoft® Windows 7 Support
l
Improved Security
In order to understand any implication these changes in functionality may have on your
existing projects, refer to the “Upgrading to PowerSCADA Expert 7.30” topic in the PowerSCADA Expert online help after you have installed the product.
Alarm Server Upgrade
When upgrading to PowerSCADA Expert 7.30, be aware legacy alarm servers and clients
(those prior to 7.30) will be unable to communicate with the new alarm server.
Only v7.30 alarm client and servers will be able to communicate.
See Also
Migrating Alarm Event History
Migrating Alarm Event History
Migration of alarm event history from any 7.x versions is supported.
Alarm event history migration is triggered automatically at runtime if :
1. A valid alarm history file exists (defined using the parameters [Alarm]SavePrimary
or [Alarm]SaveSecondary). If two save files exist, one from the primary alarm Server
and one from the standby Alarm Server, the system uses the save file with the latest
date.
2. The Alarm database does not exist in the system. This implies that runtime is
launched initially or the database has been manually deleted. The alarm database
will be created when runtime is launched for the first time.
To undo the migration of the alarm event history manually delete the database. The
alarm history file should be valid.
27
Chapter 2: Migration
Note: Deleting the alarm database will cause the entire 7.30 alarm history to be lost. The
database can be deleted by deleting the directory located in the PowerSCADA Expert
data directory and has the same name as the project. The PowerSCADA Expert data
directory is defined in INI parameter [CtEdit]Data.
For example, if the data directory defined in the INI parameter is:
[CtEdit]Data=C:\ProgramData\Schneider Electric\Vijeo Citect 7.30\Data, then the alarm
database directory would be C:\ProgramData\Schneider Electric\Vijeo Citect 7.30\Data\Example.
See Also
Alarm Server Upgrade
Migration Aids
In order to assist in the migration of your existing projects PowerSCADA Expert provides two migration aids. One aid is an automatic update of the project database, the
other is a manually invoked Migration Tool.
Automatic Update
The automatic update is carried out when you initially launch PowerSCADA Expert
7.30. This update is a passive action which typically updates the database field definition for any database that has been changed between the two versions and copies
new files that are required in v7.30. Prior to the automatic upgrade proceeding you are
given the option of canceling the upgrade. The upgrade can be invoked at a later time by
adjusting the Update parameter in the Citect.ini file.
Migration Tool
The Migration Tool is a separate application which needs to be manually run after the
automatic upgrade has been executed, and initiated by you after you have prepared the
project for final migration. This tool will accommodate many of the changes in project
functionality which are incorporated in v7.30.
It is important you prepare your existing projects for a successful upgrade using this
tool. For details on the Migration Tool, and the preparatory steps that you need to make
prior to its use, refer to the “Migration Tool” topic in the PowerSCADA Expert online
help after you have installed the application.
28
Chapter 2: Migration
Upgrading a Runtime-only Installation
You can upgrade a runtime-only installation of PowerSCADA Expert to a complete
installation that incorporates the configuration environment by simply running the
installer again and selecting the All Core Components option from the Installation Profiles page.
However, if a project has been restored and operated under the runtime-only environment, it will not automatically appear in Citect Explorer following the upgrade to a
complete installation.
If you would like to add a missing project to Citect Explorer, you can use the Add
Project Link feature, accessible via the File menu. You can select the project from the
Add Project Directory dialog when it appears.
29
Chapter 2: Migration
30
Chapter 3: Installation Description
Before you begin the installation of PowerSCADA Expert, you need to first decide which
components you want to install. This is determined by the functionality you want the
installation to support.
After you have decided on the PowerSCADA Expert environment, and any additional
stand alone components that you want to install, refer to Chapter 4 "Installation Requirements" so that your hardware and system software meet the requirements for your
selected installation.
Once you have progressed through the preliminary dialogs of the installation interface,
you will be requested to begin selecting the components that you want to install. The
options that the installation interface will present to you are described below.
Task Selection Dialogs
Installation Profiles
The installer provides a set of profiles to help you select the appropriate components for
installation. Depending on the profile that you choose, the next dialog will have default
selections recommended for installation. You may accept the default components, or
select the ones of your choice on the components selection screen which is displayed
after you click Next on the Installation Profiles dialog.
The options are:
l
All Core Components
l
Runtime Only Server
l
Runtime Only Client
l
Custom
The All Core Components option will select the .Net Framework 4 (if not installed), Configuration Environment, Runtime, Drivers and Sentinel Driver for installation. It is a
“Complete” installation which will install a fully functional PowerSCADA Expert development and server/client system. Such an installation will include the PowerSCADA
Expert development environment, runtime infrastructure files, Client, I/O Server, Alarm
Server, Trend Server and Reports Server. Select this option if this is an initial installation
31
Chapter 3: Installation Description
of PowerSCADA Expert which will run as a single system, or act as a server to service a
number of client installations.
If the .NET Framework 4.0 installation does not complete, you can install it manually
from the installation file in the Extras folder of the PowerSCADA Expert installation
disk, then install PowerSCADA Expert. Note that .NET Framework 4.0 requires Windows
Imaging Component (available on the Windows Download Center web site) to be
installed first.
The Runtime Only Server option will select Runtime, Sentinel Driver and Communications Drivers for installation. It is an installation which will install the runtime
components for both a Server and Client. Such an installation will include runtime infrastructure files, Client and I/O Server, Alarm Server, Trend Server and Reports Server.
Select this option if this is an installation of PowerSCADA Expert which will act as a
server to service a number of client installations.
The Runtime Only Client option will only select the Runtime system for installation. It
is an installation which will install the runtime components and a Client. Such an installation will include runtime infrastructure files, but will exclude drivers.
Select this option if this is an installation of PowerSCADA Expert which will be used as
a client.
If you wish to upgrade either of the Runtime installations to a full installation, including
the Development and Configuration environment, insert the original installation media
and select "All Core Components" or "Custom" from the Installation Profiles dialog.
Note:You can also install the PowerSCADA Expert Runtime Only Client from a single installation file. This file is named PowerSCADA Expert 7.30.exe and located in
the <discmedia>\PowerSCADA Expert 7.30\Extras\Runtime Installer folder of the
installation DVD. This allows installation of the software to computers which only
require the runtime. The file can be copied to a network location for remote installation
The single-file installation does not include Communication Drivers, the Sentinel Driver,
or the Microsoft® .NET Framework which is a prerequisite of the runtime. If the .NET
Framework is not already installed on the target computer, you cannot use the single-file
installation. In this case, you may use the full package installer to automatically install
the .NET Framework during the installation of PowerSCADA Expert. Alternatively you
can install .NET Framework from another source, then carry out the single file runtime
installation.
The Custom option will not select any components for installation; it will allow you to
select the core components that you specifically need, or allow you to install Add-ons or
documentation only.
32
Chapter 3: Installation Description
Documentation Installation
The Product Documentation option will install a comprehensive library of user guides
and references in Adobe Portable Document Format (PDF). These can be accessed from a
master contents HTML page.
It is highly recommended that you install the product documentation for future reference.
Add-ons Installation
Once you have selected the components that you want to install, the next dialog allows
you to select any Add-ons that you wish to use in your installed system..
The options are:
l
Project DBF Add-in for Excel™
l
Web Server for IIS
The Project DBF Add-in for Excel option will install an Add-In for Microsoft™ Excel.
When this Add-In is loaded into Excel, it allows you to browse, open, edit and save PowerSCADA Expert .dbf files in the correct format. This is only available for selection if
Microsoft Excel 2003 or above is installed on the computer. Otherwise, it is visible but is
deselected and disabled.
The Web Server option will install a Web Server running on Microsoft Internet Information Service (IIS). The Web Server performs the server-side functionality of a Web Service to the Web Client. As well as facilitating communication, it directs a client to the
graphical and functional content of a PowerSCADA Expert project and the location of
the runtime servers. This information is stored on the Web Server when a PowerSCADA
Expert project is deployed. A Web Server can contain multiple deployments.
Note: If the Web Server and PowerSCADA Expert runtime server are set up on different machines, and it is not possible to establish a trust relationship between them,
the two machines need to be on the same domain so that the Web server can access
the directory on the PowerSCADA Expert server that's hosting the web deployment
files. If, conversely, a trust relationship can be established between the Web Server
and the PowerSCADA Expert server, they can be on different domains as long as the
Web server has read access to the project folder on the PowerSCADA Expert server.
33
Chapter 3: Installation Description
Communication Drivers
PowerSCADA Expert communicates with control or monitoring I/O Devices that have a
communication port or data highway - including PLCs (Programmable Logic Controllers), loop controllers, bar code readers, scientific analyzers, remote terminal units
(RTUs), and distributed control systems (DCS). This communication takes place with
each device through the implementation of a communications driver. It is important that
these drivers are the latest version.
The installation of PowerSCADA Expert prior to v7.10 installed all the available communication drivers automatically with the installation of the product. From v7.10 the
installation of these drivers is performed at the final stage of the product installation
using a separate installation process. This installation process allows you to select
individual drivers that you want to install, specific to your system and its I/O devices.
There are certain drivers that the product installation will install that are necessary for
PowerSCADA Expert to function correctly. These will be installed automatically as in previous releases.
Only install drivers which are identified as being compatible with the computers operating system. If you select any driver that is not yet identified as being compatible, or is
specifically identified as not compatible, the installation process will provide an alert to
that effect, and will allow you to deselect the driver prior to continuing with the installation.
INCOMPATIBLE DRIVERS
Do not ignore alerts during driver installation. If you choose to ignore such alerts, the
driver will be installed but may operate incorrectly.
Failure to follow these instructions can result in death, serious injury, or equipment damage.
The communication driver installation can also be invoked individually at any time
after the product installation to install additional drivers.
34
Chapter 4: Installation Requirements
This chapter describes the requirements for hardware, operating system software and system configuration prior to installing PowerSCADA Expert and any of its components.
These requirements will vary subject to the components of PowerSCADA Expert that you
intend to install on any computer. Refer to chapter 3"Installation Description" to determine the components that you want to install. This chapter identifies the basic hardware
and system software requirements, as well as requirements specific to each particular
component.
Before you begin to install PowerSCADA Expert it is important that you install the latest
updates from Microsoft® for your operating system and system software.
All Core Components
System Hardware
NOTICE
The minimum and recommended hardware requirements have changed in this release.
Upgrading customers should load test their system as part of their upgrade procedure to
ensure that the hardware in use is adequate for the needs of their system.
The following tables indicate the computer hardware requirements for the PowerSCADA
Expert “All Core Components” installation and all optional components.
Description
Minimum Specification
Processor Speed
2 GHz
Random Access Memory
(RAM)
2GB if SCADA client
or
4GB if SCADA server
Available Disk Space
160GB
Graphics Adapter (see
note below)
With 64MB of VRAM
35
Chapter 4: Installation Requirements
Description
Recommended Specification or Higher
Processor Speed
3.2GHz, if server 3.2 GHz quad-core
Random Access memory
(RAM)
4GB if SCADA client
or
8GB if SCADA server
Available Disk Space
250GB
Graphics Adapter (see
note below)
With 128 MB of VRAM
Note:In PowerSCADA Expert it isrecommended that screen resolution be set at 1024
by 768 pixels or higher.
System Software
The following table indicates the system software that is needed on any computer onto
which you want to install the PowerSCADA Expert All Core Components installation
and all optional components.
PowerSCADA Expert
Component
All Core Components
Minimum System Software
Operating System
Windows 7 with Service Pack 1(32 Bit and 64 Bit)or
Windows Server 2008 R2 with Service Pack 1 (32 Bit and 64
Bit)
or
Windows XP Professional with Service Pack 3 - (32 Bit and 64
Bit)
or
Windows Server 2003 Standard Edition with Service Pack 2
(32 Bit and 64 Bit)
or
Windows Vista with Service Pack 2 (32 Bit and 64 Bit)
or
Windows Server 2008 Standard Edition with Service Pack 2
(32 Bit and 64 Bit)
and
Microsoft .NET Framework 4.0 (installed with PowerSCADA
Expert if not already installed).
Microsoft .NET Framework 2.0 (x64) is required by "Schneider
36
Chapter 4: Installation Requirements
PowerSCADA Expert
Component
Minimum System Software
Electric License Manager" and "Schneider Electric Software
Update" if using 64 bit Windows XP or 64 bit Windows Server
2003.
Internet Explorer Version 6.0 or greater.
A Local Area Network (LAN) if you want to have multiple clients
access a remote server.
If running under virtualization with VMWare, the minimum system requirement is VMWorkstation 6.03 and later.
PowerSCADA Expert
WebServer
As for PowerSCADA Expert all Core Components with the addition of:
A LAN running TCP/IP
and
Microsoft Internet Information Services (IIS) See Microsoft IIS
Compatibility for information.
Product Documentation
As for All Core Components.
Project DBF Add-in for
Excel
As for All Core Components, and Microsoft Excel 2007, or
2010.
Note: Use an NTFS file system on the target drive for the Web Server software, otherwise you won't have effective access to the necessary Windows security settings (that
is, the Folder Properties dialog will not have a Security tab). If you are currently
using a FAT/FAT32 system, convert the drive to NTFS before installing the Web
Server software.
Microsoft IIS Compatibility
For correct operation of the WebServer, install the appropriate Microsoft Internet Information Services (IIS) feature for your operating system:
l
For Windows XP install IIS v5.0
l
For Windows Server 2003 or 2008 install IIS v6.0
l
For Windows Vista and Windows 7 install IIS v7.0 and follow the Microsoft documentation for IIS7 to install the following components:
37
Chapter 4: Installation Requirements
Component
Install?
- FTP Publishing services
no to all
- Web Management Tools
- IIS6 Management Compatibility
- IIS6 management console
- IIS6 Scripting tools
- IIS6 WMI Compatibility
- IIS6 Metabase and IIS6 Configuration compatibility
- IIS Management Console
- IIS Management scripts and tools
- IIS Management Service
yes
yes
no
no
no
yes
yes
no
yes
- World Wide Web services
- Application Development Features
- .NET Extensibility
- ASP
- ASP.NET
- CGI
- ISAPI Extensions
- ISAPI Filters
- Server-Side Includes
- Common Http features
- Health and Diagnostics
- Performance features
- Security
- Basic Authentication
- Client Certificate Mapping authentication
- Digest Authentication
- IIS Client Certificate Mapping authentication
- IP Security
- Request filtering
- URL Authorization
- Windows Authentication
yes
yes
yes
yes
yes
no
yes
yes
no
yes to all
no to all
no to all
yes
no
no
no
no
no
yes
no
yes
Note: In the above table, 'yes' means the feature is essential or recommended for the
WebServer installation and 'no' means the feature is optional or not relevant to the
WebServer.
System Software
The hardware and system software that is needed on any computer onto which you
want to install the PowerSCADA Expert Runtime Only Server or Client has the same
requirements as the Core.
38
Chapter 4: Installation Requirements
Software Licensing
PowerSCADA Expert uses a hardware key to help manage the software licensing. The
hardware key is a physical key that plugs into either the parallel port or USB port of
your computer. The hardware key contains details of your user license, such as type and
I/O point limit. There is also the new licensing mechanism introduce with 7.30. Refer to
"New Licensing Method" in the section Introduced in 7.30.
Updating Your Hardware Key
When you upgrade to a new version of PowerSCADA Expert, you might need to update
your hardware key to enable the system to run. See the PowerSCADA Expert Readme file
to confirm whether you need to perform an update.
Updating the hardware key involves running the PowerSCADA Expert Key Update command, which is found in the Help menu of Citect Explorer.
Note: If you have CitectSCADA 5.21 or 5.20, run ciusafe.exe from the Citect bin directory. You can also download the latest version of the upgrade program from the
AuthCode Generator section of the PowerSCADA Expert website at http://www.citect.schneider-electric.com/.
To update the hardware key:
1. In Citect Explorer choose Help | Sentinel Key Update. A Key ID is displayed. The
hardware key's serial number might also appear. If not, read the serial number from
the label on the key.
2. Visit http://www.citect.schneider-electric.com/authcode/ and enter the serial number
as prompted. You might also be asked for the Key ID and your web login name and
password.
3. The authorization code is displayed. Type the code (or copy and paste it from the
web site) into the Authorization Code field in CiUSAFE. Do not use any spaces when
entering the characters.
4. Click Update.
The Return Code field indicates whether the hardware key was updated successfully.For
a detailed explanation of the fields in the CiUSAFE dialog, click the Help button on the
dialog.
39
Chapter 4: Installation Requirements
Note: Each time you run the Sentinel Key Update, a different Key ID is generated
which is normal. However, if you obtain an authorization code but do not immediately update the hardware key, you can enter the same authorization code the next
time you run the update.
PowerSCADA Expert License Point Count
The point limit is the maximum number of I/O device addresses (variable tags) that can
be read, and is specified by your PowerSCADA Expert license. PowerSCADA Expert
counts all I/O device addresses dynamically at runtime.
This includes all tags used by alarms, trends, reports, events, pages, in Super Genies, use
of the TagRead() and TagWrite() Cicode functions, or internal values written using DDE,
ODBC, or the CTAPI.
It does not count any points statically at compile time.
l
Dynamic points are counted only once, regardless of how many times they are used.
l
At runtime, the dynamic point counts are available through the Kernel and the CitectInfo() Cicode function.
l
Existing MEMORY_PLC tags from before v7.0 are converted to the new "local variables" during migration. Local variables are stored on the client and resolved on the
client and they are not included in the point count.
l
When you plan your system be aware of your point count so that you do not exceed
your point limit. This is particularly important, as at runtime, you can incrementally
add to your point count by using tags that have not yet been included in the total
count.
When you run PowerSCADA Expert at runtime, the dynamic point count is continuously checked against your hardware key. When the total number of dynamic points
(at runtime) pushes the total point count above the point license limit, PowerSCADA
Expert will refuse to get values for the additional points.
PowerSCADA Expert has two preconfigured 'watermark' messages that will display to
the user when the dynamic point count reaches 95% and 98% of their point license limit.
You can configure these percentages in the Citect.ini file.
Demo Mode
You can run PowerSCADA Expert without the hardware key in demonstration (Demo)
mode. Demonstration mode lets you use all PowerSCADA Expert features normally, but
with restricted runtime and I/O.
The following demonstration modes are available:
40
Chapter 4: Installation Requirements
l
15 minutes with a maximum of 50,000 real I/O.
l
10 hours with a maximum of 1 dynamic real I/O. This is useful for demonstrations
using memory and disk I/O. PowerSCADA Expert starts in this mode if no hardware
key is available. If the system detects that you are using more than 1 real I/O point at
runtime then it will swap to the 15 minutes demo mode.
Note: Writing to any tag through DDE, CTAPI, or ODBC will cause that tag to contribute to the dynamic point count even if it is a memory or disk I/O point. So if you
write to more than 1 point through these interfaces it will swap to the 15 minute
demo mode.
l
8 hours with a maximum of 42,000 real I/O. This is only available through special
PowerSCADA Expert Integration Partners (CIP) keys.
41
Chapter 4: Installation Requirements
42
Chapter 5: Installation
The Installation Process
Please refer to the PowerSCADA Expert Installation Supplement for installation instructions specific to PowerSCADA Expert.
Note: Backup your existing projects then uninstall prior versions before installing
7.30, as PowerSCADA Expert does not support different versions running side-byside.
43
Chapter 5: Installation
44
Chapter 6: Configuration
In all but the smallest system, PowerSCADA Expert will need to operate over a Local
Area Network (LAN) or a Wide Area Network (WAN).
You can use TCP/IP with PowerSCADA Expert. PowerSCADA Expert supports scalable
architecture, which lets you initially implement PowerSCADA Expert on a single computer, or over a small network, and then expand the system later without changing your
existing hardware, software, or system configuration.
Using PowerSCADA Expert on a LAN adds more flexibility to the system, and coordination within large plants can be more easily achieved. You can control and monitor
autonomous areas within the plant separately, and interrogate the whole plant using
any PowerSCADA Expert computer on the network if you want.
In any of these scenarios there are basic configurations that you have to make for the successful operation of your PowerSCADA Expert system. The configuration steps are
described in this chapter.
Local Area Network Configuration
To set up a local area network (LAN) for PowerSCADA Expert, you need to have successfully installed network hardware and software in strict accordance with the instructions provided by the manufacturer, and also be familiar with the basic operation of the
network.
Install the PowerSCADA Expert software on every PC you want to use as a PowerSCADA Expert design-time development machine, PowerSCADA Expert Runtime Only
Client, PowerSCADA Expert I/O server, PowerSCADA Expert Alarm, Report, or Trend
server.
Also, set up PowerSCADA Expert for your network, using the Computer Setup Wizard
on every one of the machines. To access the Computer Setup Wizard, Open Citect
Explorer. In the project list area, select My Projects and double-click the Computer Setup
Wizard icon, or choose Tools, Computer Setup.
Note: You need a compiled project to select in order to run the Computer Setup Wizard.
For a detailed explanation on the Computer Setup Wizard, and its options refer to “Running the Computer Setup Wizard” in the online help.
45
Chapter 6: Configuration
Network Communications Overview
Networking and Microsoft Windows 7
Microsoft Windows 7 distinguishes between Public, Home and Work networks. Each network has its own firewall profile, which allows you to configure different firewall rules
depending on the security requirements of your location. The PowerSCADA Expert
installers automatically modify the windows firewall settings for the current active network profile during installation. If you later change network settings, you will need to
manually modify the firewall settings within Windows.
Note:PowerSCADA Expert networking and redundancy needs the options "PowerSCADA Expert FTP server" and "PowerSCADA Expert Runtime" to communicate
through a Windows firewall. You will need to manually add an application to the
Windows 7 firewall exception list for a particular network profile.
Using TCP/IP for network communications
PowerSCADA Expert uses TCP/IP to facilitate communications across a network.
To set your system to TCP/IP-based communications, a number of parameters need to be
set in the citect.ini file. These parameters will be set automatically when you run the
Computer Setup Wizard and select TCP/IP, after you have completed the installation of
PowerSCADA Expert. For details of these parameters, and others, refer to “Citect.ini File
Parameters” in the online help.
The Computer Setup Wizard will recognize the computers IP address and match it to the
IP address configured in the project for the various servers in the Networking Addresses
dialog under the Servers menu in the PowerSCADA Expert Project Editor.
For example, if you had the following servers in your system:
Citect_IO_1
Citect_IO_2
Citect.PrimaryAlarm
Citect.StandbyAlarm
Citect.PrimaryTrend
Citect.StandbyTrend
Citect.PrimaryReport
Citect.StandbyReport
46
Chapter 6: Configuration
If the role you need for your PC is not available, you will also have to determine the IP
address and update the project accordingly. You can use the DOS command “ipconfig”
to obtain this information. Alternatively, you can change the PCs IP address to match
that defined in the project.
Configuring Communications Over a WAN
You can configure your system for use with wide area networks (WANs).
Using a Wide Area Network (WAN) is configured in much the same way as using a
LAN, with several additional considerations:
1. That the PCs on the WAN can see each other.
2. That appropriate security precautions (eg: VPN) are used when connecting networks
over a potentially public link (eg: the Internet).
3. Performance of the connections is appropriate to the data being transferred.
4. Reliability of the connection is appropriate to the requirement for access.
Web Server Configuration
To display a live PowerSCADA Expert project in an Internet browser, you need to publish the content of the project pages and the current data these pages present using standard, Web-based communication protocols.
For the web server to function you need to create an exception in the Windows firewall
or any other third party firewall to allow TCP traffic to flow on port 80. Specifically, if
the machine hosting the web server is running the Windows Vista or Windows 7 operating system, enable the World Wide Web Services (HTTP) option in the Windows Vista
inbound firewall.
To understand the communication architecture for the PowerSCADA Expert Web Client,
it's easiest to consider the role each of the following components play in achieving this
outcome:
l
PowerSCADA Expert Web Server - Performs the server-side functionality of the system. As well as providing communication, it directs a client to the graphical and
functional content of a PowerSCADA Expert project and the location of the runtime
servers. This information is stored on the Web Server when a PowerSCADA Expert
project is configured as a “deployment”. A PowerSCADA Expert Web Server can contain multiple deployments.
l
PowerSCADA Expert Runtime Servers (including the I/O Server, Alarms Server,
Trends Server and Report Server) - Monitor the physical production facility and contain the live variable tag data, alarms and trends that the Web Client will display.
47
Chapter 6: Configuration
l
Web Client - provides the platform to merge a deployed project's pages and content
with the raw data drawn from the runtime servers. Again, standard Web technologies are needed, so the client uses Microsoft Internet Explorer.
Once you've installed PowerSCADA Expert Web Server for IIS, you will find the following directories under the \Inetpub\wwwroot\Citect folder.
l
The base directory primarily hosts the administrative pages that are displayed by a
Web Server.
l
The cgi-bin and images directories contain the content necessary to display these
pages.
l
The client folder contains the client components (.cab files) that are delivered to a
remote computer to run a deployment. Any subdirectories includes the components
associated with a particular release (in this case, v7.30).
l
The deploy folder includes the files associated with any deployments (PowerSCADA
Expert projects) configured on the Web Server.
l
The #displayclientfolder (located in the Deploy folder) plays a key role in the Web
Server security, as the permissions defined for this folder determine the access rights
for each user.
l
The locales folder contains the files necessary to support different languages for the
client interface. See “Implementing Multiple Language Support” in the Web Client
topic of the PowerSCADA Expert online help.
The IIS Virtual Directory
The installation process also adds a virtual directory called Citect to Windows IIS (Internet Information Services). This virtual directory establishes the Web Server as a valid
destination for client applications. However, it also plays an important role in managing
which users have access to the site.
You can view evidence of this virtual directory in the IIS management console, which is
launched by selecting Internet Information Services from Windows' Administration
Tools menu. The PowerSCADA Expert virtual directory is shown under the list of
default web sites.
You can view the properties for the directory by selecting Properties from the right-click
menu.
The Virtual Directory inherits all security settings from the computer's default web site,
with the following exceptions:
48
l
Directory Browsing is enabled
l
Script Source Access is disabled
l
The default document is set to default.htm only
Chapter 6: Configuration
l
Anonymous access is disabled
l
Integrated Authentication is disabled
l
Basic Authentication is enabled
These security settings, including integrated authentication, anonymous access and SSL
Encryption, can be customized by the local administrator. However, proper configuration needs experience with IIS and an understanding of the implications of adjusting its settings.
Setting Up Security
If you want to use a Web Server/Client for communications in your PowerSCADA Expert
system there are configuration requirements for both the server and the client. The major
configuration needed is that of security on the server.
Security on the Web Server is based on the implementation of user accounts. In the case
of an IIS-based Web server, security is tightly integrated with Windows user authentication. For information on setting security on each of these, refer to Configuring Security Using IIS.
Web Client user account types
Both systems support the same three user account types on a Web Client.
Client type
Description
Administrator
User is permitted to remotely view, add, update and delete deployments.
Control Client
User can view project pages and make adjustments to writable
values.
View-only Client
User can only view the project pages.
The Web Server tests the access rights for each user when they log in and then displays
or hides the appropriate buttons on the home page accordingly.
Note: Although the Web Client security architecture controls access to your projects
on the Web Server, the PowerSCADA Expert system security (privilege/area settings)
still manages the control system, maintaining a primary level of security.
49
Chapter 6: Configuration
Configuring Security Using IIS
Setting up security on an IIS-based Web Server primarily involves creating three Windows user groups, each representing one of the Web Client user account types. Individual users can then be assigned to the relevant user group, and automatically inherit
appropriate access rights based on the Windows security settings defined for the group.
Note: To avoid security access issues for operating systems Windows Vista® and
above, creation of these Windows user groups is mandatory.
Client Type Access Rights
The following table defines the access rights that each type of user has to the Web
Server's installed directories, as defined by the properties for each.
In the table, read means Read & Execute, List Folder Contents and Read user permissions are allowed; read and write means Full Control is allowed, and access denied
means Full Control is denied.
Installed directory
ADMINISTRATOR
CONTROL
VIEW-ONLY
Citect
read
read
read
Citect \ cgi-bin
read
read
read
Citect \ client
read
read
read
Citect \ deploy
read and write
read
read
Citect \ deploy \ #displayclient
read
read
access denied
Citect \ images
read
read
read
For example, an administrator client needs to be able to read all the installed folders to
fully access the components of the home page. Additionally, they need write access to
the Deploy subdirectory to create new deployments.
By comparison, a View-only Client needs to be denied access to the #displayclient folder
to deny the ability to write back to a PowerSCADA Expert project.
Therefore, when setting up security on the Web Server, your user accounts need to align
appropriately with the permissions outlined in the table above.
To implement the Web Server’s security strategy successfully, follow the procedure
below to configure your system, and simplify managing client accounts.
The ongoing management of your Web Server security then involves adding and removing individual accounts as needed.
Note:
50
Chapter 6: Configuration
l
The installation and initial configuration of the Web Server needs to be performed by
a Windows user with local administrator permissions; that is, they need to be able to
add and edit Windows User accounts, and modify files and folders. This capability is
needed to set up Web Client user accounts and manage security settings.
l
It is important to understand the distinction between the role of the Windows Local
Administrator, and the Web Client’s Administrator users:
l
Windows Administrator - configures security on the Web Server and sets up
client accounts.
l
Web Client Administrator - an end user capable of modifying and managing
projects deployed on the Web Server.
The two roles parallel a PowerSCADA Expert configuration engineer and a runtime operator
To create the client account user groups:
1. From the Computer Management tool, locate Local Users and Groups in the directory
tree. This is where the users and groups for the local machine are configured and
managed.
2. Right-click the Groups folder and select New Group. This displays the New Group
dialog.
3. In the Group Name, type Web Client Administrator (or something appropriate), and
describe the group's purpose.
4. Click Create.
The group you have just created will appear in the list of groups presented in the Computer Management console.
Repeat the steps above to create Control Client and View-only Client user groups.
To test your security settings, add at least one user to each group.
Preparing the Citect folder
You need to set the security settings for the Citect folder and its sub-directories, as this
will determine the access granted to each type of client account.
To prepare the Citect folder:
1. Log on to the Web Server computer as a Windows Administrator.
2. Launch Windows Explorer and browse to the Citect folder. The Citect folder is
located in the installation directory. By default, this is Inetpub\wwwroot\Citect on
the web server computer.
3. Right-click the Citect folder and select Properties.
4. From the Properties dialog, select the Security tab to display the users currently configured for the folder.
51
Chapter 6: Configuration
There will probably be several groups already defined in this folder. The two you need to
pay attention to are the Administrators group and the Everyone group.
l
The Administrators group represents all the Windows users recognized by the
Web Server computer with Local Administrator rights. This group has Full Control permissions on the folder, facilitating the ability to adjust the Web Server
security settings. If this is the case, there should be no reason to modify this
group.
l
The Everyone group represents all other users recognized by the local machine.
Give this group the following access to the Citect folder; allow Read & Execute,
List Folders Contents, and Read permissions. This provides local users on the
Web Server machine with the equivalent of Control Client permissions.
5. Add the three groups that you created in Configuring Client Account User Groups to
the Citect folder.
6. Confirm the security settings for the three newly created groups. Each has to have the
same access as the Everyone group: Read & Execute, List Folders Contents, and
Read permissions
7. All the subdirectories have to inherit the permissions set for the Citect folder. To do
this click the Advanced button on the Security tab of the properties dialog, and select
Replace permission entries on all child objects, then click OK.
This provides consistent security settings across all the installed directories. A Security
dialog might appear to alert you that this will “remove or reset explicitly defined permissions on child objects”. Click Yes to continue.
Setting Access Rights for Client Accounts
The three client account types supported by the Web Client are defined by the security
settings for each within the installed directories on the Web Server machine.
The differences, outlined in the table in Client Type Access Rights, need specific security
settings for the Administrator Client and View-only Client types. An Administrator
needs write access to the Deploy subdirectory, and the View-only Client needs to be
denied access to the #displayclient subdirectory.
To configure security setting for the Administrator Client group:
The Administrator Client needs full access to the Deploy subdirectory to enable the creation and modification of deployments.
1. Locate the Deploy subdirectory in the Citect folder. By default, this is InetPub\wwwroot\Citect\Deploy.
2. Right-click the folder and select Properties to display the Deploy folder properties.
3. Click the Security tab and locate the Web Client Administrator group you created in
52
Chapter 6: Configuration
the list of users and groups.
4. Edit the permissions set for the group to Allow Full Control.
To configure the security settings for the View-only Client group:
The View-only Client needs to be denied access to the #displayclient subdirectory to
deny write changes being made to a deployed PowerSCADA Expert project.
1. Locate the #displayclient subdirectory in the Citect folder. By default, this is Inetpub\wwwroot\Citect\Deploy\#displayclient.
2. Right-click the folder and select Properties to display the folder properties.
3. Click the Security tab and locate the View-only Client group you created in the list of
users and groups.
4. Edit the permissions set for the group, and change to Deny Full Control
5. A Security dialog appears “Deny entries take priority over all Allow entries”. Click
Yes to continue.
Note: The Control Client group needs no additional configuration, as it uses the settings outlined in Preparing the Citect folder.
Set security permissions accurately in order for the web server to operate correctly. If you
experience any problem with communicating from the web client check that the security
settings are correct for your installation.
Deleting a User Account
You can deny a user access to the Web Server by removing them from the groups that
have permissions set for the Citect folder.
However, if security is a concern, deny the user access to the Citect folder before you
delete the user. This avoids a situation where the operating system doesn't immediately
acknowledge that a user account has been deleted, creating a short period where a
deleted user can still log on.
To absolutely delete a user account:
1. Add the user as an individual to the Citect folder.
2. Set their access rights to Deny Full Control.
3. Remove the user from the groups that have permissions set for the Citect folder.
With all access denied, they cannot do anything even if they gain access.
Testing the Web Server Security Settings
To test the security settings for your Web Server client groups:
53
Chapter 6: Configuration
1. Launch Internet Explorer on the Web Server machine.
2. Call up the Web Client home page by typing in the following address:
http://localhost/Citect
3. Log in to the home page using a user name and password that's been added to the
Administrator Client group.
If successful, the System Messages dialog will read “LOGINADMIN Admin (UserName) logged in”.
If the message starts with LOGINDC (for Control Client) or LOGINMC (for Viewonly Client), there is a problem with your configuration. Confirm that you are
using the correct user name for the group you are testing. If the problem still
occurs, revisit the process in Setting up security using IIS to check that an error
hasn't been made.
4. Repeat this process with a Control Client and View-only Client user.
Once you have confirmed that security is correctly set up on the Web Server, you can
now prepare your PowerSCADA Expert project for deployment. For more information see
Configuring a deployment in the online help.
Logging on to the Web Server
After setting up your client accounts, you need to provide the following details to each
end user so they can log on to the Web Server:
l
Address of the Web Server
This is the address users have to type into their Web browser to gain access to the
PowerSCADA Expert Web Server. If they are doing this remotely, the address is:
http://<machine name>/Citect
or
http://<machine IP address>/Citect
If they are logging on to the Web Server computer, the address is:
http://localhost/Citect
l
User name and password
Once the browser has arrived at the Web Server, the end user is asked to provide a
user name and password. Typically, you just need to tell them that their Windows
user name and password will provide appropriate access. If you had to create a
new user profile for someone, provide them with the details.
54
Chapter 6: Configuration
Note: In some operating systems users may be logged in automatically. To modify
this behavior so the user is prompted to login, go to User Authentication in Internet
Explorer|Tools|Internet Options|Security Settings.
Once you have finalized the security setup on the Web Server, you are ready to prepare
your PowerSCADA Expert projects for deployment.
55
Chapter 6: Configuration
56
Index
A
architecture 12
C
Citect license point count 40
clustering 11
resolving context with unique tag names 9
Computer Setup Wizard configuration 45
configuration 45
D
demo mode 40
description
Integrated Environment 31
H
hardware alarms 12
hardware key 39
I
IIS components 37
Installation Requirements 35
IPX/SPX 45
L
LAN 45
license points
dynamic 40
static 40
local variable 13, 27
M
memory mode 12
migration 9
multi-cluster system 9
N
NetBEUI 45
Network Support 9
Networking and Microsoft Windows 7 46
new features 9
new functionality 9
O
online changes 11
P
persist mode 12, 25
R
Requirements
hardware 36
IIS 37
LAN 37
operating system 36
RAM 35
System Software 36
T
TCP/IP 9, 45
TCP/IP setup 46
U
unique tag names 9
W
WAN 45
Download PDF