1. technology and computing
2. software
3. databases

MicroSCADA Pro DMS600 4.4 FP1
DMS600 Installation Manual
Trace back information:
Workspace Main version a32
Checked in 2014-09-22
1MRS757318
Issued:
Version:
24.2.2012
B/19.9.2014
MicroSCADA Pro
DMS600 4.4 FP1
DMS600 Installation Manual
Installation Manual
Contents
1
About this manual ................................................................................. 5
1.1
1.2
1.3
1.4
1.5
1.6
1.7
1.8
2
5
5
6
6
7
8
9
9
Requirements for installation .............................................................. 11
2.1
2.2
2.3
3
Copyrights .....................................................................................
General .........................................................................................
Use of symbols .............................................................................
Document conventions .................................................................
Terminology ..................................................................................
Abbreviations ................................................................................
Related documents .......................................................................
Document revisions ......................................................................
System requirements .................................................................... 11
Other requirements ....................................................................... 11
Licenses ........................................................................................ 12
Installation of DMS600 .......................................................................... 13
3.1
3.2
3.3
3.4
3.5
Alternative methods to install DMS600 to server computers ........
Database server installation .........................................................
3.2.1
About the database software installation ........................
3.2.2
Divided databases ..........................................................
3.2.3
Database server names ..................................................
3.2.4
Manually creating a database and database objects in
MS SQL Server ...............................................................
3.2.5
Creating a database and database objects in Oracle
10g ..................................................................................
3.2.6
Updating existing database ............................................
Demo package ..............................................................................
Starting Setup program .................................................................
Installation wizard .........................................................................
3.5.1
Welcome to the MicroSCADA Pro DMS600 Setup
program ..........................................................................
3.5.2
DMS600 Core .................................................................
3.5.2.1
Install mode selection ....................................
3.5.2.2
Destination location .......................................
3.5.2.3
Select license ................................................
3.5.2.4
Select components ........................................
3.5.2.5
Database type ...............................................
3.5.2.6
Define servers ...............................................
3.5.2.7
ODBC DSN definitions ..................................
3.5.2.8
Backup replaced files ....................................
3.5.2.9
Start installation .............................................
3.5.3
DMS Service Framework ................................................
13
14
14
15
15
15
15
16
17
18
18
18
19
19
19
19
20
20
21
22
23
23
23
3
DMS600 4.4 FP1 MicroSCADA Pro
DMS600 Installation Manual
1MRS757318
Installation Manual
3.5.4
3.5.5
3.5.6
4
Setting up DMS600 ............................................................................... 27
4.1
4.2
4.3
4.4
4.5
5
27
27
28
28
28
29
29
29
Installing Hot Stand By support (HSB) afterwards ........................
Redundant hot standy by (HSB) system configuration with
database replication ......................................................................
5.2.1
Setting Up Replication Using MS SQL Server ................
5.2.2
Replication using MS SQL Server ..................................
5.2.3
Replication using Oracle .................................................
31
31
32
35
36
Uninstallation of DMS600 ..................................................................... 39
6.1
6.2
6.3
7
General about configuring settings ...............................................
Server settings ..............................................................................
License updating ...........................................................................
Setting up DMS600 SA interfaces ................................................
4.4.1
Configuring SCIL API interface .......................................
Setting up DMS Service Framework interfaces ............................
4.5.1
Configuring OPC interface ..............................................
4.5.2
Using DMS600 OPC DA client to connect to OPC DA
server in a remote computer ...........................................
Hot Stand By support (HSB) ................................................................ 31
5.1
5.2
6
DMS600 SA service ........................................................ 24
Binary database update .................................................. 25
Username and password ................................................ 25
General about uninstallation ......................................................... 39
Starting uninstallation ................................................................... 39
Manual checking after uninstallation ............................................ 40
The computer network ......................................................................... 41
7.1
7.2
Regional servers ........................................................................... 41
Terminal services .......................................................................... 41
Index ....................................................................................................... 43
4
1MRS757318
Issued:
Version:
24.2.2012
B/19.9.2014
MicroSCADA Pro
DMS600 4.4 FP1
DMS600 Installation Manual
Installation Manual
1
About this manual
1.1
Copyrights
The information in this document is subject to change without notice and should not be
construed as a commitment by ABB Oy. ABB Oy assumes no responsibility for any
errors that may appear in this document.
In no event shall ABB Oy be liable for direct, indirect, special, incidental or consequential
damages of any nature or kind arising from the use of this document, nor shall ABB Oy
be liable for incidental or consequential damages arising from the use of any software
or hardware described in this document.
This document and parts thereof must not be reproduced or copied without written
permission from ABB Oy, and the contents thereof must not be imparted to a third party
nor used for any unauthorized purpose.
The software or hardware described in this document is furnished under a license and
may be used, copied, or disclosed only in accordance with the terms of such license.
Copyright © 2014 ABB Oy. All rights reserved.
Trademarks
ABB is a registered trademark of ABB Group. All other brand or product names
mentioned in this document may be trademarks or registered trademarks of their respective
holders.
Guarantee
Please inquire about the terms of guarantee from your nearest ABB representative.
Third Party Copyright Notices
List of Third Party Copyright notices are documented in "3rd party licenses.txt" and
included in SYS600 and DMS600 installation packages.
1.2
General
This document complies with the DMS600 program version 4.4 FP1.
Additional information such as Release Notes can be found on the program distribution
media.
5
DMS600 4.4 FP1 MicroSCADA Pro
DMS600 Installation Manual
1MRS757318
Installation Manual
1.3
Use of symbols
This publication includes warning, caution and information symbols where appropriate
to point out safety-related or other important information. It also includes tips to point
out useful hints to the reader. The corresponding symbols should be interpreted as follows:
!
Warning icon indicates the presence of a hazard which could
result in personal injury.
Caution icon indicates important information or a warning
related to the concept discussed in the text. It might indicate
the presence of a hazard, which could result in corruption of
software or damage to equipment/property.
Information icon alerts the reader to relevant factors and
conditions.
Tip icon indicates advice on, for example, how to design a
project or how to use a certain function.
Although warning hazards are related to personal injury, and caution hazards are
associated with equipment or property damage, it should be understood that operation
of damaged equipment could, under certain operational conditions, result in degraded
process performance leading to personal injury or death. Therefore, comply fully with
all warnings and caution notices.
1.4
Document conventions
The following conventions are used for the presentation of material:
•
•
•
•
The names of menus and menu items are boldfaced. For example, the File menu.
The following convention is used for menu operations: MenuName > MenuItem
> CascadedMenuItem. For example: select View > Coloring > Topology by
Feeders.
The Start menu name always refers to the Start menu on the Windows® Task Bar.
System prompts/messages and user responses/input are shown in the Courier font.
For example, if a value out of range is entered, the following message is displayed:
Entered value is not valid. The value must be 0 to 30.
•
•
•
6
The names of push and toggle buttons are boldfaced. For example, click OK.
The words in names of screen elements (for example, the title in the title bar of a
window, the label for a field of a dialog box) are initially capitalized.
Capital letters are used for the name of a keyboard key if it is labeled on the keyboard.
For example, press the CTRL key. Although the Enter and Shift keys are not labelled
they are written in capital letters, for example press ENTER.
1MRS757318
Issued:
Version:
24.2.2012
B/19.9.2014
MicroSCADA Pro
DMS600 Installation Manual
Installation Manual
•
•
•
•
•
1.5
DMS600 4.4 FP1
Lowercase letters are used for the name of a keyboard key that is not labeled on the
keyboard. For example, the space bar, comma key, and so on.
Press CTRL+C indicates that the CTRL key must be held down while pressing the
C key (to copy a selected object in this case).
Press ESC E C indicates that each key must be pressed and released in sequence.
The names of directories and files (for example, DMS600/common.prm) are initially
capitalized and shown in italics.
The names of database tables, queries and fields are capitalized (for example CODE
field in CODEINFO table).
Terminology
Terms associated with the DMS600 that the user should be familiar with are listed in
the following table. The table contains terms that are unique to ABB or have a usage or
definition that is different from the standard industry usage.
Term
Description
ActiveX
A set of technologies that enable software components to interact
with one another in a networked environment, regardless of the
language in which the components were created.
Classic monitor graphics
Graphics style of older DMS system versions. Can still be used
in DMS600.
Disturbance Data Form
A part of Trouble Call Management, which is used to handle
customer complaints and fault notifications.
DMS600 database
Relational database for dynamic data in DMS600.
DMS600 Network Editor
DMS600 NE
A program primarily used to model the distribution network onto
the network database.
DMS Interface Package
Tools used to integrate MicroSCADA and DMS600 using SCIL
API. The DMS Interface Package contains Virtual Point Creation
Tool and DMS Grouping Tools.
DMS600 Server Application
DMS600 SA
A service used for data exchange between MicroSCADA and
instances of DMS600 WS.
DMS600 Service Framework
A windows service, which runs modules (DLL-files). The DMS600
Service Framework can be controlled using DMS600 Service
Monitor.
DMS600 Service Monitor
A monitoring program, which connects to all DMS600 Service
Frameworks in the system and displays info about them
(statuses, logs, actions, ....).
DMS600 Workstation
DMS600 WS
A program for the operative personnel of electric companies to
monitor and operate their medium and low voltage distribution
networks.
DXF import
A tool used for reading DXF/DWG files containing the network
data exported from 3rd party GIS systems, and writing them to
the DMS600 database.
Free data form
Free data forms are the general way to present DMS600 database content.
7
DMS600 4.4 FP1 MicroSCADA Pro
DMS600 Installation Manual
1MRS757318
Installation Manual
Term
Description
Free database object
Free database objects are user-defined object types, which can
be added to the network database.
Free data form control
A control which can present data from a database table or a
query in a user-defined layout. See also Data Access Objects.
Hot Stand By; HSB
A system to secure database connection with two servers. Each
server is capable of continuing the service by itself if the connection to the other server is lost.
MicroSCADA monitor
MicroSCADA Monitor Pro
Enables interaction with the operator and the base system
computer. The monitor may be of Visual SCIL or X-monitor type.
MicroSCADA monitors are always connected to SYS 500 or
SYS600. MicroSCADA Monitor Pro is an application that can
show the Monitor Pro graphics of SYS600.
MicroSCADA OPC Server
An implementation of the interface specification OPC Data Access Custom Interface Standard, Version 2.05A, on the MicroSCADA system.
Monitor Pro graphics
The graphics style in SYS600.
Network database
Database for network data.
OPC item
OPC item is an index for MicroSCADA process object containing
the whole path with an application number. OPC item has
properties (process object attributes) like alarms and time
stamps.
SCIL API
MicroSCADA API that is used to connect DMS600 to MicroSCADA.
Support System Interface; SSI A standardized method of transferring data between the applications.
1.6
8
Temporary network file
The file containing temporary network data (Tempnet.dat).
Trouble Call Management
Trouble Call Management (TCM) is a way to handle customer
complaints and fault notifications. Operator can use this information to make conclusions about fault locations and types, and
by means of them, be able to restore electricity for number of
customers and advice maintenance personnel to fix the fault.
Abbreviations
Abbreviation
Description
API
Application Program Interface
DMS
Distribution Management System
DMS600
MicroSCADA Pro Distribution Management System DMS600
dxf
Vector file format
HSB
Hot Stand By
LIB 500
MicroSCADA Application Library
LIB 510
MicroSCADA MV Application Library
LV
Low voltage
1MRS757318
Issued:
Version:
1.7
24.2.2012
B/19.9.2014
MicroSCADA Pro
DMS600 4.4 FP1
DMS600 Installation Manual
Installation Manual
Abbreviation
Description
MicroSCADA
MicroSCADA SYS 500 version 8.4.2, 8.4.3, 8.4.4 or 8.4.5 or
MicroSCADA Pro Control System SYS600 version 9.x
MV
Medium voltage
SCADA
Supervisory Control And Data Acquisition
SSI
Support System Interface
SYS600
MicroSCADA Pro Control System SYS600 version 9.x
TCM
Trouble Call Management
Related documents
Table 1.1: MicroSCADA Pro related documents
1.8
Name of the manual
MRS number
MicroSCADA Pro DMS600 4.4 FP1
System Overview
1MRS757322
MicroSCADA Pro DMS600 4.4 FP1
Integration with SYS600
1MRS757320
MicroSCADA Pro DMS600 4.4 FP1
Operation Manual
1MRS757319
MicroSCADA Pro DMS600 4.4 FP1
System Administration
1MRS757321
MicroSCADA Pro SYS600 9.4
Installation and Administration Manual
1MRS758086
Document revisions
Version
Revision number
Date
History
A
4.4
24.12.2012
New document
B
4.4 FP1
19.9.2014
Document updated
9
1MRS757318
Issued:
Version:
24.2.2012
B/19.9.2014
MicroSCADA Pro
DMS600 4.4 FP1
DMS600 Installation Manual
Installation Manual
2
Requirements for installation
2.1
System requirements
The following table shows the minimum software and hardware requirements for the
DMS600 Distribution Management System. The proposed system configuration contains
1 to 3 PC's with possible Hot Stand By support.
DMS600 can also be used without MicroSCADA or with other SCADA systems.
Table 2.1: System requirements for DMS600
2.2
Component
Requirement
Optional components
One or more network adapter cards, when using DMS600 software on a LAN with a TCP/IP protocol
Software
DMS600 supports the Microsoft Windows Server operating
systems from Windows Server 2008 to Windows Server 2012
R2 and the Microsoft Windows workstation operating systems
from Windows 7 to Windows 8.1.
DMS600 also supports 64-bit versions of aforementioned systems.
Installation is possible also to Windows Vista and Server 2003
but those are not officially supported since full testing has not
been done with those operating systems.
Relational database software. MS SQL Server 2005, 2008 or
2012 or Oracle 10g or 11g.
.NET Framework version 4 or newer is required.
Optional software
MicroSCADA SYS 500 version 8.4.2, 8.4.3, 8.4.4, 8.4.5 with LIB
500 Application Library and LIB 510 MV Application Library
version 4.0.2. 4.0.3, 4.0.4 or 4.0.5 or MicroSCADA Pro Control
System SYS600 version 9.x.
MS Word to create documents. Supported versions are 97, 2000,
2002, 2003, 2007, 2010 and 2013.
Other requirements
MS SQL Server or Oracle can be used as database for DMS600. Other database servers
can also be used if they support the required features of a DMS600 database. MS SQL
Server 2005, 2008, 2008 R2 and 2012 and Oracle 10g and 11g have been tested by ABB.
DMS600 can be installed with MicroSCADA, without SCADA, or with other SCADA
systems using OPC Data Access interface. However, if DMS600 will be used with
MicroSCADA SYS 500 or SYS600, these applications must be installed on the server
computer before the installation of DMS600. On the workstation computers,
MicroSCADA workstation and the Hummingbird™ Exceed version 5.1.3 or later may
be used.
In order to install the full DMS600 system, a MS Windows user needs to have
Administrator rights. They are needed to be able to update the MS Windows registry
settings.
11
DMS600 4.4 FP1 MicroSCADA Pro
DMS600 Installation Manual
1MRS757318
Installation Manual
It is recommended to define a shared directory in the fileserver computer before the
installation of DMS600 fileserver, primary or secondary.
If more than one operating system is used and the disk is shared, DMS600 must be
installed on the same disk as the operating system.
In order to use a resource that is not administered by the local computer (for example,
a Hot Stand By server), the "MicroSCADA" user name must be defined on the remote
computer that administers that resource. The password of MicroSCADA user has to be
the same on different computers as well.
The MicroSCADA application must be shut down before installing DMS600 Server
(including the MicroSCADA interface) on a computer with an existing DMS600 Server
installation.
In Hot Stand By systems, the DMS Server must be installed to both computers when
they are cold. Therefore, the hot MicroSCADA server must be changed between
installations.
Additional software requirements
The following additional software updates or newer versions are required before installing
DMS600 especially if SQL Server and its tool Management Studio are in use:
1.
2.
Windows Installer 4.5 (Windows restart is required after the installation)
Powershell 1.0
Always restart Windows before installing DMS600.
New Windows installations have these software updates automatically depending on the
Windows in question. The necessary updates and software can be found and downloaded
from www.microsoft.com.
2.3
Licenses
DMS600 is initialized using a license file (for more information about DMS600 licenses,
see System Administration). The license consists of two files, LicenseInformation.txt
and License.ini, which are delivered by ABB.
The file License.ini is needed during a full installation of DMS600. License information
updates are performed with a separate setting program (for more information on updating
license information, see Section 4.3 License updating).
DMS600 can be installed with a special demonstration license. The full license can be
added later on.
12
1MRS757318
Issued:
Version:
24.2.2012
B/19.9.2014
MicroSCADA Pro
DMS600 4.4 FP1
DMS600 Installation Manual
Installation Manual
3
Installation of DMS600
3.1
Alternative methods to install DMS600 to server computers
The used drive names are examples. Programs in one computer
can also be installed in the same drive.
Alternatives 3, 4 and 5 describe how the redundant server system (the Hot Stand By
system) can be installed.
Figure 3.1: Different methods for installing DMS600
When terminal services are used, alternative 1, or, in case of HSB, alternative 3 is
normally used. In this case, no workstation installations are required since the workstation
uses Windows Remote Desktop connection or terminal server client. However, standard
13
DMS600 4.4 FP1 MicroSCADA Pro
DMS600 Installation Manual
1MRS757318
Installation Manual
client installations can be used in parallel with terminal server clients. For advanced
automatic operations, such as automatic fault restoration and creating HTML documents,
use of separate workstations is recommended.
It is also recommended to install DMS Service Framework to SCADA computer(s) since
this would not require OPC connections to a remote computer. However, DMS Service
Framework can be installed to a file server computer as well.
3.2
Database server installation
3.2.1
About the database software installation
If you want to manually create or edit databases, install database software (SQL Server
or Oracle) separately into the file server computer or a separate computer. The DMS600
installation software includes MS SQL Server 2008 R2 SP2 Express and ready made
SQL scripts that create database objects, for example tables and views. Installation
program includes an option to install an empty DMS600 database automatically.
For Hot Stand By systems, use the database server software. Set the replication features
of the database to allow two databases to be updated reliably.
The database software cannot be installed to the Windows
operating system compressed directories. If the disk is
compressed, remove the compression from the installation
directory (for example, C:\Program Files\Microsoft SQL
Server), as well as from the DMS installation directory. This
is required also in the demo installation since it installs the
SQL Server.
After installing SQL Server all cumulative updates shall be
installed, not only the latest service pack.
After installing DMS600, the file server directory includes a subdirectory SQL which
contains the scripts for creating database and database objects in the SQL Server and
Oracle, depending on database software used. For further information, see Section 3.2.4
Manually creating a database and database objects in MS SQL Server and Section 3.2.5
Creating a database and database objects in Oracle 10g.
If a database will be created in Oracle, keep the password used
when installing the database software. It will be needed when
creating a database. For further information, see Section 3.2.5
Creating a database and database objects in Oracle 10g.
14
1MRS757318
Issued:
Version:
3.2.2
24.2.2012
B/19.9.2014
MicroSCADA Pro
DMS600 4.4 FP1
DMS600 Installation Manual
Installation Manual
Divided databases
The DMS600 installation supports divided databases so that the user can create a Network
database (Network DSN) with static network data by running 44_FP1_Network_mdb.sql,
and a DMS600 database for operational data by running 44_FP1_Opera_mdb.sql.
Dividing databases is neither required nor recommended. However, if divided databases
are used, for example to limit the amount of tables in each database, create views by
running the scripts 44_FP1_Network_Views.sql and 44_FP1_Opera_Views.sql for the
SQL Server. These scripts use the database names OPERA_ONLY and
NETWORK_ONLY. Rename them according to the database name.
3.2.3
Database server names
DMS600 requires database server names in order to run correctly with redundant
databases. If database server names are left empty when the MS SQL or Oracle database
is selected during installation or when server settings are edited, the names will be filled
in automatically as the names of the primary and the secondary file server.
The server names are network addresses, for example, Computer1, or an IP-address, for
example 10.10.200.200. The DSN definitions are filled in automatically as DMS600.dsn
if left empty. Also, network DSN1 and network DSN2 can be left empty if the same data
source is used for them as for the DMS600 DSNs.
3.2.4
Manually creating a database and database objects in MS SQL Server
After installing the MS SQL Server database software, create a database manually using
Microsoft SQL server Management Studio. For automatic installation of an empty
database, see Section 3.5.2.7 ODBC DSN definitions.
1.
2.
3.
4.
Open the first file 44_FP1_Network_mdb.sql with the Management Studio.
Select the correct database in the drop-down list.
Click the Execute button.
Do the same for the following files in the given order.
a. 44_FP1_Opera_mdb.sql
b. 44_FP1_Network_Views.sql
c. 44_FP1_Opera_Views.sql
d. Network_default_data.sql
e. Opera_default_data.sql
44_FP1_Network_mdb.sql and 44_FP1_Opera_mdb.sql create database tables.
3.2.5
Creating a database and database objects in Oracle 10g
After installing the Oracle database software, create the database and database objects.
This can be done by using the Oracle tool Database Configuration Assistant.
1.
Start and continue the process as guided by the Database Configuration Assistant.
15
DMS600 4.4 FP1 MicroSCADA Pro
DMS600 Installation Manual
1MRS757318
Installation Manual
2.
3.
In the Database Content step, select Custom Scripts.
Add the scripts to the list in the given order:
a.
b.
c.
d.
44_FP1_Network_mdb.sql
44_FP1_Opera_mdb.sql
44_FP1_Network_Views_ORACLE.sql
44_FP1_Opera_Views_ORACLE.sql
Figure 3.2: Database Content dialog
4.
5.
Open the DMS600User.sql script file.
Change the password from the default 1234 to the one used in the installation phase.
Change the username to DMS600.
The password must be the same as used when installing
the database software, and the username must be DMS600.
Otherwise, the schema name DMS600 must be modified
in all scripts for the given username.
6.
7.
3.2.6
Run the scripts by clicking Next.
After finishing the installation, redefine (if necessary) the Oracle server settings for
the DMS600 installation by opening Settings located in the created DMS600 program
group in the Windows Start Menu.
Updating existing database
Existing MS SQL Server or Oracle database needs to be updated before starting DMS600
applications. Follow these steps to update the database.
16
1MRS757318
Issued:
Version:
24.2.2012
B/19.9.2014
MicroSCADA Pro
DMS600 4.4 FP1
DMS600 Installation Manual
Installation Manual
When an existing version of DMS600 uses the MS Access
database, it needs to be updated to a relational database server.
MS Access is not supported anymore. See Section 3.2.4
Manually creating a database and database objects in MS SQL
Server or Section 3.2.5 Creating a database and database objects
in Oracle 10g
1.
2.
3.
4.
5.
6.
If the old DMS600 version is 4.3 or earlier, see DMS600 4.4 documentation for
database conversion
Run DMS600 installation program. When Oracle is used, select Use Oracle on the
database type selection page. See Section 3.5.2.5 Database type
Start SQL Server Management studio or Oracle SQL Developer
Execute all 4.4 Hotfix patches found in the <installation
directory>\SQL\SQLServer\PATCH or <installation directory>\SQL\Oracle\PATCH
Start DatabaseUpdater.exe from the SQL folder
Select all patches from the left pane and press Execute selected script(s)
In case some of the DMS600 4.4 Hotfixes is installed, only
patches released after that hotfix need to be executed before
starting the database updater tool.
3.3
Demo package
The demo package is included in the installation package. The setup program includes
the MicroSCADA application (directory name Aplopera) which is modified from the
LIB 500 demo application. This program includes all definitions for the MicroSCADA
- DMS600 interface.
The easiest way to get the DMS600 to properly communicate with MicroSCADA is to
install the LIB 500 demo application. It is also possible to use any other application
available by performing all required actions. In this case, see more detailed description
in the Integration with SYS600 manual.
Demo installation also installs a demo package for DMS600 (for example, databases
and background maps). The demo installation package is designed to be as easy as
possible for a single computer. If the demo application is used on several workstation
systems, use the settings program (Settings.exe) to define fileserver names (for more
information about defining fileserver names, see Section 4.2 Server settings).
The demo installation installs SQL Server Express as an instance with the name computer
name\DMS600. The demo databases are restored from the backup file DMS.bak to this
installation. If a database with the name DMS600 already exists, it is first backed up to
DMS600_RECOVERY.bak, which makes it possible to get the previous database back
into use.
17
DMS600 4.4 FP1 MicroSCADA Pro
DMS600 Installation Manual
1MRS757318
Installation Manual
3.4
Starting Setup program
Although the setup program retains the original databases, it
is still recommended to make backup copies of the original
databases containing valuable data before starting the setup
program.
Before reinstalling or upgrading DMS600, make sure that all
DMS600 programs are shut down. It is also strongly
recommended to exit all Windows applications before running
the setup program.
Administration rights are required in order to properly install
DMS600.
3.5
Installation wizard
3.5.1
Welcome to the MicroSCADA Pro DMS600 Setup program
The Installation Wizard guides the user through the installation of DMS600. The dialogs
that open during installation depend on the selections made during the installation.
When the wizard is started, a Welcome dialog opens. It provides a possibility to select
which DMS components are installed. They are all selected by default.
•
•
•
•
MS SQL Server 2008 R2 SP2 is the Express version of the software. Check this
to install SQL Server with DMS600 installation.
DMS600 Core is the main DMS600 installer. It contains DMS600 applications and
related files.
DMS Service Framework is a service framework which is used to execute multiple
tasks
SA Service is a service to communicate with SYS600. This is successor of DMS600
Server Application of earlier versions of DMS600.
Use Options button to insert SQL server instancename. If SQL server is selected to be
installed, the inserted name is used as a name of the new instance. DMS600 database
can be installed to an existing SQL server instance by inserting its name on the options
page and unselecting SQL server package. DMS600 Core, DMS Service and SA Service
packages use the inserted instance name in their database operations. Default value is
DMS600 and it is used if the field is left empty.
Pressing Install launches selected packages with their own user interfaces. SQL server
installation shows the user interface but it doesn’t allow user interaction.
18
1MRS757318
Issued:
Version:
24.2.2012
B/19.9.2014
MicroSCADA Pro
DMS600 4.4 FP1
DMS600 Installation Manual
Installation Manual
Note that the welcome page is shown only on the first
installation. On the second time the installer shows a
maintenance page which only allows uninstallation. Thus select
all the relevant packages to be installed on the first time. If the
configuration needs to be changed afterwards it is required to
uninstall MicroSCADA Pro DMS600 and start again.
3.5.2
DMS600 Core
3.5.2.1
Install mode selection
DMS600 Core installer contains DMS600 applications and file server files. Also Demo
environment is included in DMS600 core. When the DMS600 Core installer is started,
it first shows a welcome page which is followed by an installation mode selection page.
It provides two alternatives: Custom installation for configuring DMS600 and Demo
installation for as easy as possible installation of DMS600 demo. Custom mode can be
used to update the existing environment. In that case, relevant files are replaced with
new ones.
The Installation Wizard dialogs contain the following buttons:
•
•
•
•
3.5.2.2
Next >, which continues the installation.
< Back, which returns to previous dialog boxes.
Cancel, which cancels the installation.
After Cancel has been clicked, the setup program asks for confirmation. Click Yes
to exit the wizard or No to continue the installation.
Help in some dialogs, which opens a help window for different options or fields.
Destination location
Destination Folder shows the default installation path (for example C:\DMS600). This
directory should be shared or located under a shared directory. The destination folder
information is saved in the DMS600 environment variable of MS Windows.
To change the destination directory, click Browse. When updating a previous installation,
Browse is unavailable, and the default installation directory of the previous installation
is used.
If Demo installation is selected, clicking Next in the Destination Folder dialog takes you
directly to the Ready to install dialog.
3.5.2.3
Select license
The options in this dialog are:
19
DMS600 4.4 FP1 MicroSCADA Pro
DMS600 Installation Manual
1MRS757318
Installation Manual
•
•
3.5.2.4
Install demo license. This option installs the demo license.
I have another license. DMS600 License tool is started after the installation is
completed. The selected license file must contain the new license delivered by ABB.
Select components
The Select Components dialog includes the following information:
•
•
•
All DMS600 custom installation options.
Disk space required for each option and total required disk space.
Disk Usage button shows disk space remaining on the selected destination drive.
Table 3.1: Check box options in the Select Components dialog
Option:
Functioning:
File Server
If checked, DMS600 is installed on a computer that will act as
a primary fileserver.
Network Editor
If checked, DMS600 NE is installed on a computer using the
services of fileservers and DMS600 SA.
Workstation
If checked, DMS600 WS is installed on a computer using the
services of fileservers and DMS600 SA.
Esti
If checked, Esti is installed on a computer using the services of
fileservers.
Pdf Documents
If checked, DMS600 document files (pdf files) are installed on
the computer. Online help files are installed during DMS600 File
Server installation.
DXF import Tool
If checked, the DXF import tool is installed on a computer using
the services of fileservers and DMS600 SA.
Disturbance Data Form
If checked, the Disturbance Data Form (DDF) is installed on a
computer. If this is checked without File Server or Workstation
components, a separate stand alone installation of DDF is used,
in which the configuration data is still needed in ODBC database
settings.
Data Access Objects (DAO 3.5) If checked, the data access objects are installed on the computer.
The DAO are needed for database handling.
3.5.2.5
Database type
Alternatives in this dialog are:
•
•
•
20
Install empty database. This installs empty database to the SQLServer instance
specified on the Options page of the welcome dialog.
Use Oracle can be selected when Oracle is used as the database. Oracle login data
can be filled to enable automatic login to the database. The format of the string is:
UID=user; PWD=password; where user is the username and password is the database
password. Note that the semicolon (;) characters are required.
Don't install DB. Database is not installed by the DMS600 installer. However, you
can insert database addresses on the following dialogs and create database manually
1MRS757318
Issued:
Version:
24.2.2012
B/19.9.2014
MicroSCADA Pro
DMS600 4.4 FP1
DMS600 Installation Manual
Installation Manual
by using scripts provided by the installer. See Section 3.2.4 Manually creating a
database and database objects in MS SQL Server or Section 3.2.5 Creating a database
and database objects in Oracle 10g
3.5.2.6
Define servers
Fileserver directories should be shared directories and given in the format
\\Computer_name\<Shared directory name>. Fileserver directories can also be defined
as Not shared (for example, C:\DMS600). However, note that the correct use of DMS600
WS and DMS600 NE requires that the disk resources of DMS600 fileservers can be
mapped from the workstation. To use the system without a network connection for demo
purposes, the file server directory must be defined (for example, C:\DMS600).
Table 3.2: Boxes in the Define Servers dialog
Option:
Function:
Primary File Server
Contains the address of the primary DMS600 fileserver (same
as the destination folder). For example C:\DMS600 or \\Computername\DMS600
Primary Server Application
Computername
Contains the name of the computer in which the primary DMS600
SA is run. DMS600 SA can be installed in a different computer
than the fileserver (See Section 3.1 Alternative methods to install
DMS600 to server computers). This computer button inserts
current computername to the field.
Redundant Server System
(HSB) exists
Can be selected to insert data of the second server during installation. In a single server system, there is only one DMS600
fileserver and one DMS600 SA, but the redundant server system
consists of two DMS600 fileservers and two DMS600 SA systems. Requires a Hot Stand By sublicense.
Secondary File Server
Contains the address of the secondary DMS600 fileserver.
Secondary Server Application Contains the location where the secondary DMS600 SA is run.
Computername
DMS600 SA can be located in a different computer than the
fileserver.
DMS600 NE uses only one static network database even in a
redundant server system. Therefore, the primary fileserver path
of each DMS600 WS and DMS600 NE must be addressed to
the primary server.
The setup program will not check if the file server directories
exist. User needs to verify that before or during the installation.
The DMS600 file servers and Server Application computer names can be changed after
installation (for more information about servers, see Section 4.2 Server settings).
21
DMS600 4.4 FP1 MicroSCADA Pro
DMS600 Installation Manual
1MRS757318
Installation Manual
3.5.2.7
ODBC DSN definitions
The ODBC connection to the database must be defined by defining a Data Source Name
(DSN). This is done using the Data Sources (ODBC) tool found in the MS Windows
Control Panel. In Hot Stand By systems, both servers must have their own DSN
definitions. The DSNs must be defined for each workstation that run DMS600
applications.
After the Data Source has been defined, names can be given during installation in the
ODBC database settings dialog. Then DSN names can be given for both servers.
Static network data can reside in a separate database. In this case, the Network DSN can
be defined. Usually, this is not needed since all data can be in same database and the
Network DSNs can be left empty as the system copies the DSN name to the network
DSN.
The DSN names must be the same in every workstation since
names are saved to common settings on file server.
Centralized ODBC data source name (DSN) definitions
Instead of defining the DSN name to every workstation where DMS600 is used, a central
DSN definition file can be created. The file name has to end with .dsn. Name the file
either in installation or in the Server settings program. When the MS SQL Server is used,
the file content has to be following (values are examples):
[ODBC]
DRIVER=SQL Server
DATABASE=DMS600
SERVER=SYS1
An IP address can be used instead of a server name. Integrated Windows authentication
is the default with MS SQL Server but if needed, the username and password can be
added to the .dsn file for SQL Server login. This requires that MS SQL Server is set to
be in "SQL Server and Windows Authentication mode" and an SQL Server user (for
example DMS600) is created with correct access rights. In this case the .dsn file must
have UID and PWD lines to define the used SQL Server username and its password. An
example can be found below.
UID=DMS600
PWD=1111
A separate file has to be defined for both database servers. These files need to be stored
in redundant systems on both fileservers in Data subdirectories. When a filename without
a path is given, the file is searched from the fileserver Data subdirectory. If a full path
is given, it is used directly.
22
1MRS757318
Issued:
Version:
24.2.2012
B/19.9.2014
MicroSCADA Pro
DMS600 4.4 FP1
DMS600 Installation Manual
Installation Manual
Figure 3.3: Define servers dialog of the installation
3.5.2.8
Backup replaced files
If a DMS600 fileserver has been installed previously in the same working directory, the
existing setting files, databases and executables are always copied to the <Install
directory>\DMS_Backup folder during installation.
The names of the backup files are the same as names of original files.
3.5.2.9
Start installation
Click Install in the Ready to install dialog box to start the installation.
The Installing dialog box shows the progress of the installation with a graphics bar. The
text label above the graphic bar shows the ongoing operation at that moment. Clicking
Cancel will open the Exit setup dialog with the option to stop the installation before it
is finished. In this case, all the changes made by the installation are rollbacked.
3.5.3
DMS Service Framework
When DMS600 Core installation is completed succesfully, the installation of DMS
Service Framework is started. A welcome page is followed by an info dialog where text
box gives last minute info about the service framework.
Define destination path in the destination location dialog. It is recommended to install
service framework to a different location than DMS600 core. However, there are no
23
DMS600 4.4 FP1 MicroSCADA Pro
DMS600 Installation Manual
1MRS757318
Installation Manual
technical limitations for install directory. Also, insert credentials to install and run DMS
Service. It is recommended to run DMS Service with MicroSCADA user, which is also
suggested by the installer.
Before installing DMS Service, verify that the user has
administrator right to the computer. Installation will fail if
privileges are not sufficient.
Clicking Next verifies that inserted passwords match with each other. If the checkbox
in the Ready to install dialog is checked, the service is started after installation. For Demo
installation it is recommended to leave the box unchecked and restart the computer after
installation. The DMS Services starts automatically after computer startup.
The installer adds database login for the defined user so that the service can connect to
DMS database when it starts. It also configures certificate for DMS service so that Service
Monitor can connect to it also remotely. CreateCertificate.exe can be used later to create
certificates for other users. It is used via command prompt by giving user as a parameter.
For the DMS Service Framework, there is no dedicated update mode. However, the
framework and modules can be updated simply by installing a later package. It will
handle removing the old version internally.
3.5.4
DMS600 SA service
After successful installation of DMS Service Framework, the installation of SA service
is started. After welcome page and info page, a destination location is asked. Credentials
are asked similarly to DMS service. <computer name>\MicroSCADA is suggested as
default. The given user is used to run the service. It is also used to register COM interface
for MicroSCADA connection. The COM registration is done by using a separate program
found in the SA service directory.
If the MicroSCADA password is not known, it can be changed by using the MicroSCADA
control panel and the MicroSCADA administrator program. The registration with the
correct password is required to enable Server Application to provide the interfaces for
other MicroSCADA Pro applications, such as Monitor Pro.
After installing DMS600 Server Application, the installation must be completed as
described in Integration with SYS600.
If the working directory is not on the C: drive, or if the Aplopera application is not used
as the application number 1:
1.
2.
3.
Open the DMS Grouping Tool.
Update the working directory.
Click Apply.
For more information about the DMS Grouping Tool, see Integration with SYS600.
24
1MRS757318
Issued:
Version:
3.5.5
24.2.2012
B/19.9.2014
MicroSCADA Pro
DMS600 4.4 FP1
DMS600 Installation Manual
Installation Manual
Binary database update
After the installation of DMS600, it is recommended to first start DMS600 NE, since
DMS600 NE updates the binary network file when necessary.
To update the binary database in DMS600 NE, answer Yes to the question "Read network
from database?", or select File > Update Network Database and answer Yes to the
question.
The Network.dat file is required to start DMS600 SA and DMS600 WS. If DMS600 SA
or DMS600 WS is started first and Network.dat is incompatible, the text "Binary database
(Network.dat) must be updated" is shown and the program is quit.
3.5.6
Username and password
A username and password are required to login to DMS600 programs. After installation,
use the username ADMIN and the password Admin to log in DMS600 programs. For
more information about user management, see System Administration.
Change the password for the ADMIN user right after
installation to prevent unauthorized access to the system.
DMS600 passwords are case sensitive. In addition, the
following special characters are accepted: % * . – _ .
25
1MRS757318
Issued:
Version:
24.2.2012
B/19.9.2014
MicroSCADA Pro
DMS600 4.4 FP1
DMS600 Installation Manual
Installation Manual
4
Setting up DMS600
4.1
General about configuring settings
There is a separate program Settings.exe for configuring the settings of DMS600 after
installation. The program is located in the Windows Start menu (by default, in the
MicroSCADA Pro DMS600 group) under Settings.
The program can be used to configure:
•
•
Server settings
License updating
Running Settings.exe opens the DMS600 Settings dialog. One check box or all check
boxes can be selected at a time.
Restart the DMS600 application(s) after changing the settings.
4.2
Server settings
Configure server settings for DMS600 and MicroSCADA SCIL API connection in the
Server Settings dialog.
The DMS600 fileserver and DMS600 SA computer name fields are described in
Section 3.5.2.6 Define servers. The secondary server and computer names are used if
the Hot Stand By sublicense exists. If the secondary fields are defined to be empty, the
redundant server system is not used even if the Hot Stand By sublicense exists.
Fileserver directories should be shared and given in the format
\\Computer_name\<Shared directory name>. The fileserver
directories can be defined as Not shared (for example,
C:\DMS600) However, note that the correct use of DMS600
WS and DMS600 NE requires that both disk resources of
DMS600 fileservers can be mapped from the workstation.
The Server Settings program will check if the directories of the file servers exist. The
program also checks the permissions of the directories. If the file server directory is not
found or the permissions are not sufficient, a message is displayed. Share the directory
manually or define the file server name again. If the Secondary File Server field is left
empty, the checking process of secondary server is bypassed.
The addresses of the MicroSCADA SCIL API connection can also be changed with this
dialog. The fields to change are described in Section 4.4.1 Configuring SCIL API
interface. These fields are used if the SCADA connection sublicense exists. ODBC DSN
27
1MRS757318
DMS600 4.4 FP1 MicroSCADA Pro
DMS600 Installation Manual
Installation Manual
definitions can also be changed with this tool. For more information, see Section 3.5.2.7
ODBC DSN definitions.
4.3
License updating
DMS600 license information can be updated after program installation by using License
Updating tool.
The options available in the tool depend on the existence of a License.ini file. The possible
alternatives are:
•
•
Install a new License.ini file. Click OK to select the license file from the directory
tree. Click OK or double-click the file to install the new license. The installation
program automatically changes the file name to license.ini and makes a backup copy
of the old license.ini. The selected license file must contain the new license delivered
by ABB.
Use the License.ini file already installed on the computer. Click Next if no changes
are required in the existing license information.
If no license is installed, DMS600 generates a No License error message after start up.
4.4
Setting up DMS600 SA interfaces
4.4.1
Configuring SCIL API interface
To change the DMS600 SA specific Support System Interface settings after start up:
1.
2.
Open DMS600 Service Monitor. Select DMS600 SA service from list and select
settings tab.
Define the settings described in the following table.
Table 4.1: SCIL API parameters
Box
Function
Username
Username for the Support Sys- 1...20 characters
tem Interface
Default: ABB
Password
Password for the Support Sys- 1...20 characters
tem Interface
Default: Opera
IP-address (Primary MicroSCADA)
IP address of the primary Micro- Default: 127.0.0.1
SCADA (normal state hot)
Used only if the SCADA Connection sublicense is included.
TCP-port (Primary MicroSCADA)
TCP port of the primary Micro- Default: 1333
SCADA (normal state hot)
Used only if the SCADA Connection sublicense is included.
IP-address (Secondary Micro- IP address of the secondary
SCADA)
MicroSCADA (normal state
warm)
28
Notes
Default: 127.0.0.1
Used only if the SCADA Connection sublicense is included.
1MRS757318
Issued:
Version:
24.2.2012
B/19.9.2014
MicroSCADA Pro
DMS600 4.4 FP1
DMS600 Installation Manual
Installation Manual
Box
Function
Notes
TCP-port (Secondary MicroSCADA)
TCP port of the secondary Mi- Default: 1333
croSCADA (normal state warm) Used only if the SCADA Connection sublicense is included.
Data transfer intensity level
Defines DMS600 SA frequency
of operation and its internal
waiting times
Analog username, password, IP address and TCP port settings are defined in the DMS
Grouping Tool. For more information about the DMS Grouping Tool, see Integration
with SYS600.
Updating connections to MicroSCADA server computers is done through a separate
program. For more information about updating MicroSCADA connections, see Section 4.2
Server settings.
4.5
Setting up DMS Service Framework interfaces
4.5.1
Configuring OPC interface
MicroSCADA Pro Control System SYS600 version 9.x and MicroSCADA SYS 500
version 8.4.5 have a communication feature based on OPC Data Access. The feature can
be used in parallel with SCIL API interface. In DMS600 4.4 FP1 the OPC interface is
provided by an OPC client which runs as a DMS Service Framework component. The
OPC client can also be used with third party OPC servers.
For configuring OPC client, see System administration.
DMS Service Monitor is used to insert OPC username to a configuration file. It can be
inserted or edited on the SA settings tab in Service monitor. See System administration.
4.5.2
Using DMS600 OPC DA client to connect to OPC DA server in a
remote computer
Because of the enhanced security settings in Windows, additional configuration changes
are required in DMS. To open the OPC interface on a remote computer using DCOM,
access rights have to be defined also for the client (DMS) computer. It is not recommended
to run OPC server on a remote computer.
29
1MRS757318
Issued:
Version:
24.2.2012
B/19.9.2014
MicroSCADA Pro
DMS600 4.4 FP1
DMS600 Installation Manual
Installation Manual
5
Hot Stand By support (HSB)
5.1
Installing Hot Stand By support (HSB) afterwards
If the primary server has been used before the installation of the secondary server, its
databases and files are not empty. The secondary server installation installs empty
databases (or no databases) and empty files to the secondary server. The data inserted
using the primary server has to be copied to the secondary server.
The installation needs a Hot Stand By sublicense. Contact your
vendor to acquire the license.
To install the secondary server of HSB system afterwards:
1.
2.
3.
4.
Install the secondary server by checking the File Server check box during installation
(for more information about installation, see Section 3.5.2.4 Select components).
Copy manually the DMS600 database, Common.prm, Genlang.mdb and License.ini
files (including the HSB license) from the Data directory of the primary server to
the Data directory of the secondary server.
Copy manually the maps from the Map directory of the primary server to the Map
directory of the secondary server.
Use the Settings tool (Settings.exe) to update server settings in every workstation
(for more information about settings, see Section 4.2 Server settings).
DMS600 WS and DMS600 SA can be used with a primary or secondary server. DMS600
WS and DMS600 SA updates the DMS600 database in both servers. When a server is
reconnected, DMS600 SA or DMS600 WS notices this and updates data automatically.
DMS600 NE can only be used when the primary server is
connected. The network database is only at the primary
fileserver. This means that network editing and some
administrative tasks can be done only when the primary
fileserver is connected.
For HSB configuration of DMS Service Framework, see System administration.
5.2
Redundant hot standy by (HSB) system configuration with
database replication
A database replication feature is needed to present the data updated only to DMS (manual
disconnectors, open line cuts, etc.) correctly in switch-over situations. All tables shall
be inlcuded in replications to make sure that DMS works correctly.
31
DMS600 4.4 FP1 MicroSCADA Pro
DMS600 Installation Manual
1MRS757318
Installation Manual
When database replication is in use, Network Editor can also be used when either of the
database servers is available. The replication arrangement makes the databases identical
even if the installation tools use the words primary and secondary server.
5.2.1
Setting Up Replication Using MS SQL Server
Creating a publication on the server
1.
2.
3.
4.
Start the SQL Server Management Studio and connect to server.
Create the new publication by right-clicking Replication > Local Publication.
Choose the database to be replicated.
Choose the publication type:
a. Snapshot publication is good for replicating views.
b. Merge publication is good for constantly changing data, i.e. tables.
5. Create replications for Views and Tables separately for both Network and DMS600
databases. Based on which is being created, snapshot for views or merge for tables,
choose either Tables or Views.
6. For table data only: do not choose any filters.
7. Choose the snapshot to run immediately, do not select any scheduled runs.
8. Click Security settings....
9. Click Run under the SQL Server Agent Service Account and By impersonating
the Process Account.
10. Give the publication a name. It is useful to give a name that implies the publication's
function. For example, a publication of DMS_NETWORK database tables would
be named DMS_NETWORK_TABLES, and, correspondingly, publication of its
views would be DMS_NETWORK_VIEWS.
11. Fix the replication so that it will expire by right-clicking Replication and choosing
Properties from the Object explorer of the main window of SQL Management
Studio. This removes any unneccessary log information from the database.
12. Choose a expiration period of sufficient length, for example 3 months, to prevent
storage of extra replication data.
Fixing SQL Server settings to enable connection from subscriber
side
1.
2.
32
Run SQL Server Configuration Manager from Windows Start Menu > MS SQL
Server > Configuration Tools.
Enable TCP/IP, shared memory and Named pipes from Protocols for
MSSQLSERVER and Client Protocols.
1MRS757318
Issued:
Version:
24.2.2012
B/19.9.2014
MicroSCADA Pro
DMS600 4.4 FP1
DMS600 Installation Manual
Installation Manual
3.
In order for the changes to take effect, restart the SQL Server Service from SQL
Server Services.
Registering the Subscribers
1.
2.
3.
In order for the subscribers to become more easily managed, they should first be
added to the list of registered servers. Expand the Database Engine and right-click
Local Server Groups. Either create a new group or add the server directly to the
root. See figure below.
Give the server a unique and easily distinguishable name.
From the Connection properties tab use Connect to database. Test the connection
and click Save.
33
DMS600 4.4 FP1 MicroSCADA Pro
DMS600 Installation Manual
1MRS757318
Installation Manual
Figure 5.1: Registering a server
Adding subscribers
1.
2.
3.
4.
5.
6.
7.
34
Right-click the publication on MS SQL Server's main window Object Explorer >
Local Publications and select New subscriptions…
The publication information will be OK as the subscription was created directly to
the publication.
In the Merge Agent Location dialog, if the subscribers are SQL Express installations,
the only option is to Run all the agents at the distributor. If the subscribers are
full SQL's and there are many of them, choosing Run each agent at its Subscriber
(Pull subscriptions) is advised.
In the Subscribers dialog, Click Add SQL Server Subscriber.
Choose the server from the list. To add multiple servers simultaniously, click Add
SQL Server Subscriber multiple times.
In the Subscribers dialog, choose the database for the subscriber by clicking the
check box.
In the Merge Agent Security dialog, choose Click … to set security settings.
1MRS757318
Issued:
Version:
24.2.2012
B/19.9.2014
MicroSCADA Pro
DMS600 Installation Manual
Installation Manual
8.
9.
10.
11.
12.
13.
5.2.2
DMS600 4.4 FP1
Choose Run under the SQL Server Agent service account.
In the Synchronization Schedule dialog's Agent Schedule tab, choose Run on
demand only for snapshots and Recurring for merge replications.
Let the replication occur daily every 30 minutes and from 0:00:00 to 23:59:59.
Select the Initialize check box from the Initialize Subscriptions dialog and choose
Initialize immediately.
In the Subscription Type dialog, to set priority for one subscriber over other, give
a subscriber a greater value on a scale from 0 to 100 than the others.
In the Wizard Actions dialog, click Create the subscription and click Finish.
Replication using MS SQL Server
Replication with two redundant servers requires the usage of Merge Replication. In
replication, one server is defined as the Publisher and the other one is defined as the
Subscriber. Changes made to both servers are replicated, when possible, continuously
in both directions. The continuous replication keeps both databases updated in normal
conditions. When one of the servers is unavailable, it cannot receive updates. However,
when servers are reconnected through a LAN, the agent service will automatically update
all the database changes made during downtime.
Before starting the replication process, change the log on the account for the SQL Server
(MSSQLSERVER) and SQL Server Agent services to This account using Services in
35
DMS600 4.4 FP1 MicroSCADA Pro
DMS600 Installation Manual
1MRS757318
Installation Manual
Windows Control Panel. Use a Windows username with the same password for both
database servers (for example username MicroSCADA). This is required so that
replication run by SQL Server Agent Service can access the other server. The selected
username has to be defined in SQL Server Logins, and it must have sysadmin,
processadmin and bulkadmin server roles. Restart the MSSQLSERVER service after
making the changes.
The DMS600 database is installed using the available scripts on the first database server.
This server can be defined as the Publisher. The whole DMS600 database can be published
for replication. In the other server, an empty database is created. After that, a subscription
to the previously created publication can be added. In this phase, both tables and views
must be selected. When the subscription is taken into use, the whole database structure
with the data is copied to the server.
When the publication is created, the Merge Agent Security has to be defined. Select Run
under the SQL Server Agent service account. (Before replication definition, the service
account has been changed.)
When the database structure needs to be changed, the entire replication can be recreated.
Overview of the Merge Replication can be found, for example, in the following link:
http://msdn2.microsoft.com/en-us/library/ms152746.aspx.
5.2.3
Replication using Oracle
Oracle has several Distributed Databases Concepts. For HSB systems with two redundant
database servers, Oracle Multimaster Replication with Asynchronous Replication can
be used for high availability. When using asynchronous replication, information about
a data manipulation language (DML) change on a table is stored in the deferred
transactions queue at the master site where the change occurred. These changes are called
deferred transactions. The deferred transactions are pushed (or propagated) to the other
participating master sites at regular intervals, which can be defined.
36
1MRS757318
Issued:
Version:
24.2.2012
B/19.9.2014
MicroSCADA Pro
DMS600 4.4 FP1
DMS600 Installation Manual
Installation Manual
Oracle Enterprise Manager Console can be used to configure and administer replication
environments. The tool can be used to define Master databases for a master group. For
more information, see the Oracle 10g manual.
37
1MRS757318
Issued:
Version:
24.2.2012
B/19.9.2014
MicroSCADA Pro
DMS600 4.4 FP1
DMS600 Installation Manual
Installation Manual
6
Uninstallation of DMS600
6.1
General about uninstallation
The uninstallation program uninstalls DMS600 from the computer. Basically the uninstall
program is the same as the installation program. When MicroSCADA Pro DMS600 is
installed and the installer is started again, it starts in the uninstallation mode. The
uninstaller removes all the installed DMS specific components i.e. DMS600 Core, DMS
Service and SA Service. If needed, MS SQL Server has to be uninstalled separately.
After executing the uninstallation program it may be necessary to remove the rest of the
installed parts manually (for more information about removing files manually, see
Section 6.3 Manual checking after uninstallation).
6.2
Starting uninstallation
Before uninstalling DMS600, make sure that all DMS600
programs are shut down.
To uninstall DMS600 from Windows Server 2003:
1.
2.
3.
4.
5.
6.
Open Control Panel.
Select Add/Remove Programs.
Select Change or remove programs.
Select MicroSCADA Pro DMS600.
Click Change/Remove. An uninstallation wizard opens.
Uninstall DMS600 according to the wizard.
To uninstall DMS600 from Windows Vista:
1.
2.
3.
4.
5.
Open Control Panel.
Select Programs and Features.
Select MicroSCADA Pro DMS600.
Select Uninstall/Change.
Uninstall DMS600 according to the wizard.
To uninstall DMS600 from Windows 7, Windows 8, Windows 8.1, Windows Server
2008, Windows Server 2012, Windows Server 2012 R2:
1.
2.
3.
4.
5.
6.
Open Control Panel.
Select Programs.
Select Programs and Features.
Select MicroSCADA Pro DMS600.
Select Uninstall/Change.
Uninstall DMS600 according to the wizard.
The DMS600 can also be uninstalled by double-clicking the installation program, or by
running the program by typing the file name and path in the Run command.
39
DMS600 4.4 FP1 MicroSCADA Pro
DMS600 Installation Manual
1MRS757318
Installation Manual
6.3
Manual checking after uninstallation
The complete uninstallation of DMS600 assumes that the following steps are carried out
with the uninstallation program or manually:
•
•
Deletion or renaming of the DMS600 directories.
Deletion or renaming of the DMS600 registry settings. The registry settings can be
changed via the Run command by typing Regedit. Check the following registry
keys in a 32bit/64bit system:
HKEY_LOCAL_MACHINE\software\ABB\Opera\Packages\MS-OPERA INTF
HKEY_LOCAL_MACHINE\software\ABB\Opera\Packages\OPERANE
HKEY_LOCAL_MACHINE\software\ABB\Opera\Packages\OPERAWS
HKEY_LOCAL_MACHINE\software\ABB\Products\Opera
HKEY_LOCAL_MACHINE\software\Wow6432Node\ABB\Opera\Packages\MS-OPERA INTF
HKEY_LOCAL_MACHINE\software\Wow6432Node\ABB\Opera\Packages\OPERANE
HKEY_LOCAL_MACHINE\software\Wow6432Node\ABB\Opera\Packages\OPERAWS
HKEY_LOCAL_MACHINE\software\Wow6432Node\ABB\Products\Opera
•
•
40
Deletion or renaming of the DMS600 environment system variable. The system
variable can be changed by clicking the System icon in the Control Panel. Select
the Environment tab and select the DMS600 variable for deleting or renaming.
Deletion of the DMS600 variable from the MS Windows Path variable. The Path
variable can be changed by clicking System in the Control Panel. Click the
Environment tab and delete the character string "%DMS600%" from Path variable.
1MRS757318
Issued:
Version:
24.2.2012
B/19.9.2014
MicroSCADA Pro
DMS600 4.4 FP1
DMS600 Installation Manual
Installation Manual
7
The computer network
7.1
Regional servers
DMS600 can be optimized for slow network connections. This feature is useful if there
is a slow Wide Area Network (WAN) connection instead of a LAN between central and
district offices and any terminal services are not used. Additional regional servers can
be used to store network data locally to keep the start-up time of the programs reasonable.
These regional servers can store the binary network file and on-line help information.
The local workstations can use the data from the regional server. The regional servers
must be in operation all the time, or at least when network data is updated at the central
office. If these regional servers are specified in the system, DMS600 NE also updates
network data to these servers. For performance reasons the binary network file data
should be updated only in a central office where the network database server is located.
Direct editing of Common.prm and Opera.prm files has to be
done with special care.
EXAMPLE:
The additional servers are defined manually to the [Additional_Servers] section
of the Common.prm file.
[Additional_Servers]
number=2
1=\\server1\DMS600\testdir1
2=\\server2\DMS600\testdir2
For each workstation using an additional server, the directory for the network data is
defined manually to the [General] section of the Opera.prm file.
[General]
Server1_Netdata=\\server1\DMS600\testdir1
7.2
Terminal services
Normally, the DMS600 uses client-server architecture, which means that, for example,
DMS600 WS applications are run using the client computer processor and memory. The
network model is loaded into the main memory of the client workstation.
However, DMS600 programs can be run with Windows versions where terminal services
are supported. This is advantageous, for example, in case of slow network connections
or when using dial-up networking with modems.
With MicroSCADA Pro SYS600, new monitor type (MicroSCADA Monitor Pro) terminal
services are used instead of Exceed to spread applications to workstations at least when
41
DMS600 4.4 FP1 MicroSCADA Pro
DMS600 Installation Manual
1MRS757318
Installation Manual
Monitor Pro graphics and tools are used. In this case, DMS600 will also be run under
terminal services so that the integration of user interfaces can work.
DMS600 supports running several instances of DMS600 WS in the same workstation
computer. In standard workstations, only one DMS600 NE is allowed. However, in
terminal services, each session can run one DMS600 NE.
42
1MRS757318
Issued:
Version:
24.2.2012
B/19.9.2014
MicroSCADA Pro
DMS600 4.4 FP1
DMS600 Installation Manual
Installation Manual
Index
A
license.ini .............................................................. 19
adapter card .......................................................... 11
M
B
MS SQL Server .................................................... 15
binary database .................................................... 25
N
C
Network.dat .......................................................... 25
Network database ................................................ 31
Common.prm ........................................................ 41
D
database server .................................................... 14
names ............................................................... 15
Data Source Name ............................................... 22
demo ..................................................................... 17
destination ............................................................ 19
divided databases ................................................ 15
DMS600 OPC DA client ....................................... 29
F
fileserver
directories ......................................................... 21
H
hot stand by .......................................................... 31
I
O
ODBC DSN ........................................................... 22
OPC DA server ..................................................... 29
OPC interface ....................................................... 29
Opera.prm ............................................................ 41
Oracle 10g ............................................................ 15
R
replication
using MS SQL Server ....................................... 35
using Oracle ..................................................... 36
S
server
settings ............................................................. 27
settings ................................................................. 27
Settings.exe .................................................... 17, 27
system requirements ............................................ 11
installation
starting .............................................................. 23
installation wizard ................................................. 18
T
L
U
licence file ............................................................. 19
license
updating ............................................................ 28
uninstalling ............................................................ 39
terminal services .................................................. 41
43
ABB Oy
Substation Automation Products
P.O. Box 699
FI-65101 Vaasa
FINLAND
Tel. +358 10 22 11
Fax. +358 10 224 1094
www.abb.com/substationautomation
1MRS757318 B/19.9.2014 © Copyright 2014 ABB. All rights reserved.
Contact us