Professional Documents
Culture Documents
Digsilent Installation Manual PDF
Digsilent Installation Manual PDF
DIgSILENT GmbH
Heinrich-Hertz-Strasse 9
D-72810 Gomaringen
Tel.: +49 7072 9168 - 50
Fax: +49 7072 9168 - 88
http://www.digsilent.de
Table of Contents
Table of Contents
1 INTRODUCTION ......................................................................................... 5
1.1 TYPOGRAPHIC CONVENTIONS ........................................................................ 5
1.2 OVERVIEW ..................................................................................................... 5
1.3 HARDWARE AND SOFTWARE REQUIREMENT ................................................... 7
2 DEMO VERSION .......................................................................................... 8
3 LICENSE...................................................................................................... 9
3.1 LICENSE OPTIONS .......................................................................................... 9
3.2 NETWORK LICENSE AND LICENSE SERVER .................................................... 10
3.2.1 License Server Installation .......................................................................... 10
3.2.2 License Server Upgrade - Hardlock with floating license feature enabled ....... 12
3.2.3 License Server Functionality ....................................................................... 13
3.2.4 License Server Settings .............................................................................. 14
3.2.5 Client Settings ........................................................................................... 15
3.2.6 Firewall Settings ........................................................................................ 15
3.2.7 Function Management ................................................................................ 15
3.3 LICENSE ACTIVATION .................................................................................. 16
4 DATABASE ................................................................................................ 18
4.1 SINGLE-USER DATABASE/LOCAL DATABASE .................................................. 19
4.1.1 Backup ...................................................................................................... 20
4.2 ORACLE ....................................................................................................... 20
4.2.1 Server Installation ...................................................................................... 21
4.2.1.1 Server Requirements ............................................................................... 21
4.2.1.2 Install Oracle server software .................................................................. 21
4.2.1.3 Prepare the server for PowerFactory ........................................................ 21
4.2.1 Client Installation ....................................................................................... 23
4.2.1.1 Install and configure Oracle Instant Client ................................................ 24
4.2.1.2 Install and configure Oracle Client ............................................................ 24
4.2.1.3 PowerFactory Configuration ..................................................................... 25
4.2.2 Backup ...................................................................................................... 27
4.3 MICROSOFT SQL SERVER ............................................................................. 28
4.3.1 Windows Installer 4.5 and .NET Installation ................................................. 29
4.3.2 SQL Server 2005 Installation ...................................................................... 30
4.3.3 SQL Server 2008 Installation ...................................................................... 32
4.3.4 Server Configuration (all Editions) ............................................................... 34
PowerFactory Installation Manual
Table of Contents
1 Introduction
1 Introduction
1.1 Typographic Conventions
Products of DIgSILENT GmbH are printed in bold italic.
Third party products are printed in bold.
Values given as example or ones the user can chose according to his needs are
written in italic.
File names, directories, listings and values the user is asked to enter are written in
fixed width font.
Button and window captions or menu entries the user is asked to click or select are
written in bold fixed width font.
Menus and submenu structures are denoted by an arrow () in front of the first
element and all following subentries.
Internet addresses are written in underlined fixed width font.
1.2 Overview
The delivery of the software includes:
License Key(s)
Manual(s)
License Agreement
Depending on the installation type, a PowerFactory system can have several
components which have to be installed and configured separately. Figure 1.1
provides an overview of these installation steps.
1 Introduction
full version:
network license:
install and configure license server
single-user license:
demo version:
multi-user database:
single-user database:
multi-user database:
1 Introduction
Operating system:
- Windows XP / Windows Vista / Windows 7
- Windows Server 2003 / 2008 / 2008 R2
Personal computer with a 3.0 GHz Pentium processor (or similar processor)
2 Demo Version
2 Demo Version
The demo version can run most implemented options and features, but will not allow
calculations to take place (besides the prepared tutorials and examples). It comes
with a full tutorial net, accompanied with an online do-it-yourself tutorial. This
tutorial explains the principles and functionality of PowerFactory by letting you
build the tutorial net yourself, step by step. The tutorial net contains all the major
features of PowerFactory, and calculations for this network configuration are
permitted by the program.
The setup will start automatically. If this does not occur then the setup may
be manually started using PreInstall.exe, located in the CD-ROMs root
directory.
The License page of this dialog should read as shown in figure 2.2.
Press OK .
When youre starting PowerFactory for the first time, the database is
initialized which may take several minutes.
3 License
3 License
3.1 License Options
Figure 3.1 shows different configuration models using different license keys, where
the license key is denoted by the
symbol.
The top row shows three Demo installations where no license keys are required.
Demo installations are explained in chapter 2 (Demo Version). The middle row shows
three independent Single-user clients. At the bottom, the usage of a Network license
for three users is displayed. Section 3.2 (Network License and License Server) covers
this installation mode.
Depending on whether the license key (also known as a dongle or hardlock) is
connected to DIgSILENT PowerFactory or not, PowerFactory will either be a full
runtime version or a restricted demo version. DIgSILENT provides license keys for
the USB port as well as for the parallel port.
The license key can either be individually connected to each computer where
PowerFactory is running, or a special license key, the network license key, may be
employed to allow access by several users over a network. This key is plugged to
one computer in the computer network, e.g. to a server or another machine that
runs continuously (the license server). The number of users that the key will allow at
any one time depends on the number of user licenses purchased. Simultaneous use,
up to the number of permissible users, is catered for.
3 License
To install the full version you must have administrator rights. Without these,
setup will fail.
USB license keys can only be used if USB ports are enabled
Settings Control Panel System Hardware Device Manager
Universal Serial Bus controllers.
Windows Server:
Additionally the installation has to be done on the console. A remote
administrator session will not work correctly.
If a previous version of the license server is already installed remove it completely:
Stop the License Server service in the Windows control panel or, if exists for
new versions, startup the License Server Service Configuration application
diglsvc32.exe.
If the License Server hardlock is configured with the "Floating License" module, the
file getlicense.bin out of the existing installation directory should be backed up to
import it to the new installation directory. The floating license parity is synchronized
with the file getlicense.bin within the installation directory. If synchronizing fails
the license server stops working properly and must be activated manually. In this
case DIgSILENT must be contacted.
Copy getlicense.bin to a backup directory.
Stop and uninstall the License Server service:
10
3 License
The setup will start automatically. If this does not occur then the setup may
be manually started using PreInstall.exe, located in the CD-ROMs root
directory.
After completion of the installation attach your network license key to your
computer
If the License Server hardlock is configured with the "Floating License" module, the
file getlicense.bin must be overwritten by the previously backed up file.
11
3 License
Verify that the service process is really started automatically at the Windows
startup. Note that it can take up to one minute until the process diglise.exe is
up and running. Check for existence of the processes diglise.exe
Note:
3.2.2 License Server Upgrade - Hardlock with floating license feature enabled
During a reinstallation or an upgrade of the License Server using a hardlock
including the floating license functionality, the following steps have to be done to
make available the license after the installation:
12
3 License
After installing the new License Server the file getlicense.bin has to be
copied from the old to the new installation directory.
If the License Server using the floating license hardlock is expired because of some
reasons please contact DIgSILENT support (support@digsilent.de) to provide an
activation file.
This activation file has to used via the menu entry Menu Upgrade License...
The application has to be restarted afterwards.
For each PowerFactory client a *.req request file will be created in the Run
directory that is within the license server installation path.
The license server will respond by creating a user license file *.use in its Run
directory, then the request file is deleted.
The client gets the license information via RPC protocol. The corresponding
*.use license file will be stored in the Run directory as long as the license is
valid.
If the number of users is UNLIMITED, the user license files *.use will be
deleted immediately after the client has read the file.
When the license server program is terminated it will delete all license files!
Note:
13
3 License
RPC-Protocol=ncacn_ip_tcp
RPC-Endpoint=4000
Working directory (default: subdirectory Run) request files are read from, and
user license files are written to this directory.
Note:
The network license key cannot be used as a local key for DIgSILENT PowerFactory Workstation. It can only be accessed
using the license server (PowerFactory Server). However
DIgSILENT PowerFactory and the license server may be
installed and run on the same machine, so that a network license
key may be used on a local machine as long as the license server
is also running.
14
3 License
The Computer Name is the computer name of the license server or its IP
network address e.g. 192.168.200.200.
Any firewall between license server and PowerFactory should open RPC port
135 (TCP) and also the preconfigured RPC-Endpoint port 4000 (TCP).
15
3 License
A right mouse click on a certain user in the data manager offers the menu entry
Edit. Selecting this entry opens the users dialog box, which appears as figure 3.7
shows.
The License page includes a list of all PowerFactory functions. Each function can
be enabled or disabled for this user. The standard setting enables the base package
only.
Hint:
Only the PowerFactory Administrator (default password: Administrator) has the right to modify these settings in a multiuser database environment. In a single-user environment the
user may override these settings.
If there are not enough licenses available the user will get an appropriate message
when logging on. The Help About PowerFactory dialog box then includes a list
of all remaining functions the user occupies.
16
3 License
Activate directly from the Internet: Download the activation file and merge it
to the appropriate installation directories.
Download the activation file without installation: Download the file only to
distribute it later on to the installations.
17
4 Database
4 Database
DIgSILENT PowerFactory uses a database to store the users project data. There
are two ways to use the database:
As single-user database which resides locally on each computer. Figure 4.1 shows
three PowerFactory instances on three computers with their local databases. The
single-user (or local) database is described in section 4.1 (Single-User
Database/Local Database).
As multi-user database which resides on a remote server computer, where all users
have access to the same data simultaneously. Figure 4.2 shows three
PowerFactory clients (THORIN, GLOIN, and BALIN) accessing the same multi-user
database on FEANOR. DIgSILENT PowerFactory provides drivers for two multi-user
database systems:
Oracle (c.f. section 4.2 (Oracle)), and Microsoft SQL Server (c.f. section 4.3
(Microsoft SQL Server)).
Note:
18
4 Database
Note:
19
4 Database
4.1.1 Backup
The local database is stored in the DB subfolder of your working directory which may
reside on the local hard disk, or the file server or application server depending on the
network installation mode (see section 5 (Installation and Configuration)) you are
using. To create a backup:
Close PowerFactory.
Archive the DB folder and its sub folders with an archiver/zipper utility.
4.2 Oracle
PowerFactory uses Oracles OCCI/OCI programming interface to communicate
with the server. OCCI/OCI itself uses a proprietary communication scheme on top of
TCP/IP.
Client: 11.2:
o PowerFactory 32bit (x86) requires the 32bit Oracle Client
o PowerFactory 64bit (x64) requires the 64bit Oracle Client
This chapter describes the installation and usage of the Oracle database server and
client. We assume you want to set up three clients and the server as shown in figure
4.2.
Before you set up and configure the client computers in section 4.2.2 (Client
Installation), the server must be prepared as explained in section 4.2.1 (Server
Installation).
20
4 Database
FEANOR be accessible as feanor.domain.com in the network. In order to use the Oracle server for PowerFactory you have to do the steps as follows:
Create a new Oracle instance with the SID PFSERVER (stands for:
PowerFactory Server) or use an existing one. The character set for the
Oracle instance should be WE8MSWIN1252.
Add an entry for the new instance PFSERVER. Heres an example for the
listener.ora file:
21
4 Database
The default Oracle port 1521 and the TCP protocol is used. The server has the host
name feanor. You can use the full DNS name e.g. feanor.company.com instead.
PowerFactory needs a place to store its data. Oracle stores data in so-
22
4 Database
In order to use the Oracle instance for PowerFactory one new Oracle
schema is required. Create a new schema with the default profile. We suggest
the schema name PF.
Grant the roles CONNECT and RESOURCE and the system privilege UNLIMITED
TABLESPACE to PF. You may use this small SQL script to create the schema:
CREATE USER PF
PROFILE DEFAULT
IDENTIFIED BY aPasswordForPf
DEFAULT TABLESPACE POWERFACTORYTABLESPACE
TEMPORARY TABLESPACE TEMP
ACCOUNT UNLOCK;
GRANT UNLIMITED TABLESPACE TO PF;
GRANT CONNECT TO PF;
GRANT RESOURCE TO PF;
Start the Oracle instance process and Oracle listener process if they are not
already started.
Note:
Note:
Oracle Client: This package includes many Oracle tools (e.g. management
Oracle Instant Client: This package contains only the files required for using
PowerFactory; doesnt support TNS names.
console, management tools, networking services, utilities etc.) which are not
actually required for using PowerFactory; supports TNS names.
23
4 Database
Both Oracle Client and Oracle Instant Client are available for 32bit applications and
64bit applications. PowerFactory 64bit requires a 64bit Oracle Client;
PowerFactory 32bit requires a 32bit Oracle Client.
Note: The Windows version is not relevant: if you install PowerFactory 32bit
on Windows 7 64bit, youll have to install Oracle client 32bit.
4.2.1.1 Install and configure Oracle Instant Client
Oracle Instant Client: This is a package of DLL files which can be downloaded
freely from the Oracle website. The package names are:
32bit: instantclient-basic-win32-11.2.0.1.0.zip
64bit: instantclient-basic-win-x86-64-11.2.0.1.0.zip
The packages are ZIP archives that can be extracted anywhere e.g. to
c:\instantclient_11_2:
Please use the newest version of the 11.2 client and follow the installation
documentation. It is assumed that the client software is installed in
c:\app\product\11.2.0\client_1
24
4 Database
configuration
PFS =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = feanor)(PORT = 1521))
)
(CONNECT_DATA =
(SERVICE_NAME = PFSERVER)
)
)
Then the PFS TNS name can be used in the PowerFactory configuration.
4.2.1.3 PowerFactory Configuration
Starting PowerFactory the Database page of the Log On dialog should have settings
as shown below:
25
4 Database
Database driver: On the Database page select Oracle (Client Version 11.2) as
Database driver.
service
//host[:port][/servicename
With the values used above (host=feanor, port=1521 (default port), and
SID=PFSERVER) the connection name is
//feanor/PFSERVER
//feanor:2521/PFSERVER
If youve installed a full Oracle client and made an entry (e.g. PFS) in the
TNSNAMES.ORA configuration file, you can use the TNS name instead. Then the
Database service is just
PFS
with the password aPasswordForPf has been created. Enter these values in
the Username and Password fields.
content:
PATH
C:\instantclient_11_2\vc9;C:\instantclient_11_2
C:\app\product\11.2.0\client_1):
C:\app\product\11.2.0\client_1\oci\lib\msvc\vc9;C:\app\product\11.2.0\client_1\BIN
26
4 Database
4.2.2 Backup
Describing Oracles backup facilities is far beyond the scope of this installation
manual. In this section only a simple technique is described. Please consult the
Oracle documentation for detailed information or other backup strategies.
One backup method is the creation of database dumps. The exp.exe and imp.exe
tools are part of the Oracle distribution. To export all data of the schema PF run the
exp.exe tool:
exp.exe PF/aPasswordForPf@PFS \
file=d:/tmp/database.dump \
owner=PF
where PF is the schema, aPasswordForPf is his password, PFS is the TNS name, and
d:/tmp/database.dump is the filename of the dump file.
Note:
27
4 Database
Oracle also supports so-called hot backups where clients can still use the database
during the backup process. Please consult the Oracle documentation for this backup
strategy.
To re-import a database dump, first drop and re-create the Oracle schema PF. Then
run the imp.exe tool:
imp.exe PF/aPasswordForPf@PFS \
file=d:/tmp/database.dump \
fromuser=PF touser=PF
If you import the dump into another Oracle instance ensure that there is a
tablespace with the same name as the source instance.
Enterprise Edition
Standard Edition
Workgroup Edition
Express Edition
28
4 Database
Click Next.
Click Next.
Click Continue.
Windows may ask you to restart your system to complete the installation.
Now the .NET framework can be installed. The current version is 3.5, so we use this.
You can download it for free.
Download the file via the Download button above the Quick Details section.
29
4 Database
Click Install.
To install SQL Server 2005 continue with section 4.3.2 (SQL Server 2005
Installation). To install SQL Server 2008 continue with section 4.3.3 (SQL Server
2008 Installation).
In the SQL Server 2005 Express Edition SP2 column, download both SQL Server 2005
Express Edition and SQL Server Management Studio Express.
Click Next.
Click Next.
The system configuration check should have passed without any errors. If not make
sure to correct them.
Click Next.
On the Feature Selection page click the hard drive Symbol next to Database
Services
30
4 Database
Select Entire feature will be installed on local hard drive from the popup
menu.
Click Next.
The sa user is an administration account built into SQL Server 2005. We will need
this password later. Make sure to select a secure password, as this user has full
administration privileges over the database service.
Click Next.
On the Configuration Options page, activate both checkboxes and click Next.
On the Error and usage Report Settings page, uncheck both checkboxes
and click Next.
Click Finish.
SQL Server 2005 is now installed on your system. In the next steps an advanced
administration tool is installed, SQL Server Management Studio Express.
Click Next.
Click Finish.
31
4 Database
You can now continue with section 4.3.4 to configure SQL Server 2005 for
PowerFactory.
Download the package via the Download button after you validated your
Windows Installation
Click Next.
Click Finish.
After the installation of PowerShell is finished you can install SQL Server 2008.
Microsoft provides the Express Edition as free download. You can download the
package from the Microsoft web site.
Double click the file you just downloaded to begin the installation.
32
4 Database
Enter the product key in case you are not installing the Express Edition. Click
Next.
On the Setup support Rules page click Next. Note that you have to correct all
errors on this page before setup can continue.
On the Feature Selection page make sure to select the following options:
Click Next.
The Instance Configuration page is now shown. It allows you to change the
Instance Root directory, the Instance Name and the Instance ID used by SQL
Server 2008.
The Instance Root directory is used by SQL Server to store its system databases.
Those databases tend to grow with time and also impact performance of SQL
Server. You should select an appropriate location on your server. You cannot
change this setting later on. Additionally, every new database will have its default file
location set to this directory.
identifies your SQL Server 2008 installation. This is useful as
you are allowed to have more then one installation of SQL Server 2008 running in
parallel on the same machine. In most cases the default value is fine. Just make sure
that the option is set to Named Instance.
The Instance Name
The Instance ID is used to identify installation directories and registry keys for your
instance of SQL Server. Use the same value as for the Instance Name.
The Disk Space Requirements page is shown.
Click Next.
33
4 Database
Choose Mixed Mode authentication and enter a password for the sa account.
The sa user is an administration account built into SQL Server 2008. We will
need this password later. Make sure to select a secure password, as this user
has full administration privileges over the database service.
Click Next.
On the Error And Usage Reporting page, uncheck both checkboxes and click
Next.
Click Next.
Click Close.
Click on Protocols for SQLEXPRESS node (or the instance name you
configured during installation respectively)
On the right side, right click the TCP/IP entry and select Enable from the
context menu
34
4 Database
On the right side, right click the SQL Server (SQLEXPRESS) entry and select
Restart from the context menu. The value in braces is the instance name, so
make sure to select the correct one.
On the right side, right click the SQL Server Browser entry and select Start
from the context menu if its not already running.
Your newly installed instance is now configured to allow network connections. With
the next steps a database for PowerFactory is created.
Enter the login name sa and enter the Password for sa, chosen during
installation
35
4 Database
4.3.5 Backup
4.3.5.1 Create a Backup
As with Oracle, SQL Servers backup facilities are far beyond the scope of this
documentation. It is highly suggested you consult the official Microsoft
documentation for detailed backup strategies. We present a very simple method to
PowerFactory Installation Manual
36
4 Database
backup a database and must stress that this method only satisfies the most basic
needs.
A full SQL Server database backup can be easily created from a DOS console on the
server computer.
Open a new batch file e.g. d:\backupdir\backup.bat with a text editor (e.g.
Windows Notepad editor).
Insert the above text into the file (all in one line!).
Replace its contents with the following lines (again, the sqlcmd command in
one line)
37
4 Database
USE pfdb
GO
sp_change_users_login AUTO_FIX, pf
GO
38
On one File server, where only the working directory of each client resides on
the local hard disk (c.f. section 5.2)
Section 5.1 describes the local installation which must be performed for all
installation types. The further configuration for application server or file server usage
is explained in the corresponding sections.
39
5.1 Installation
Before installing the hardlock drivers for a single-user license, please ensure that the
requirements as follows are fulfilled (they do not apply for a network license):
To install the full version you must have administrator rights. Without these,
setup will fail.
USB license keys can only be used if USB ports are enabled
Settings Control Panel System Hardware Device Manager
Universal Serial Bus controllers
The actual installation procedure runs as follows:
If you are using a single-user license: remove all existing USB license keys.
Insert the PowerFactory installation CDROM. The setup application will start
automatically. If this does not occur then setup may be started manually by
running the setup application (PowerFactory\setup.exe).
Follow the instructions during the setup. During the installation procedure
please select the Full Version option.
Later you will be asked for your serial number. The serial number can be
found in the license agreement.
40
The setup application copies the files to an installation directory, e.g. C:\DIgSILENT\pf140b501. The PowerFactory application file digpf.exe is stored in this
folder. You can start PowerFactory by double-clicking this file in Windows explorer.
The file digpf.exe is the English version. For the German version use
digpf.exe /lang:de
If youre using a single-user license: attach your license key to your computer
now.
Insert Demo as Name in the Log on dialog page. No Password is required (see
figure 5.2).
Single-user license:
select the option on local port and enter your Serial Number (see figure 5.3).
The serial number can be found in the license agreement.
Network license:
Enter the settings as described in section 3.2.5.
41
Leave the default settings on the Network page (see figure 5.4) (i.e. on local
machine) for now.
42
Press OK.
When you are starting PowerFactory for the first time, the database is initialized
automatically. This may take several minutes.
Close PowerFactory
PowerFactory is now configured for the usage on the local machine. If you want to
configure PowerFactory for file server follow the instructions in section 5.2. The
configuration for PowerFactory on an application server is described in section 5.3.
If you are using a multi-user database proceed with the User Creation in section 6.2.
On the local PCs create a shortcut to the main program digpf.exe (English
version), digpf.exe /lang:de (German version) or digpf.exe /lang:es
(Spanish version) which will be found in the PowerFactory installation
directory on the file server (e.g. N:\DIgSILENT\pf140b501 where N: is
mounted to a network drive). Additionally the full path to the set.dz
configuration file in the working directory must be provided. The complete
shortcut target for a German installation for the above example should be:
Start PowerFactory using the shortcut. Insert the Network page of the Log on
dialog is shown in figure 5.5.
Every time the program is started the executable file and its libraries will be loaded
via network from the file server. The process will however run on the local machine.
43
DIgSILENT PowerFactory is executed in its entirety on the application server. It is important that the server complies with
PowerFactorys computing requirements: RAM, CPU(s), hard
disk space, etc.
44
C:
+- DIgSILENT
+ pf140
// Installation directory
+- digpf.exe
+- set.dz
+- ...
D:
+- PowerFactoryData
+- Administrator
+- Demo
+- Frodo
+- Sam
+- Pippin
Note:
Within this root directory create directories for the built-in users Administrator
and Demo and for the users Frodo, Sam and Pippin.
Now the Log on configuration can be defined. Start PowerFactory in configuration
mode:
c:
cd c:\DIgSILENT\pf140b501
digpf.exe /config
45
Insert in the License and the Database dialog pages the license and database
configuration parameters as described in section 5.1.
In the Network page insert the settings as follows (c.f. figure 5.8).
Having configured all settings press the OK button to save the settings to the set.dz
configuration file.
46
47
To begin, each application server client should start PowerFactory, and the
Network page of the Log on dialog must be manually adapted, i.e. enter the
specific working directory and press the button OK, then terminate the
program. The Network page of the Log on dialog should read as shown in
figure 5.10.
This first run will copy all the required files to the working directory. The Log on
settings themselves will be stored in a file named set.dz which also resides in the
working directory.
After the first run add the complete path and name of the settings file (e.g.
C:\DIgSILENT\pf140b501\Client1\set.dz) as a main argument to the
shortcut.
If you are using a multi-user database proceed with section 6.2.
48
49
Enter a new Password. Repeat the password in the Confirm Password field.
50
Edit the User Manager object inside the Configuration folder by double
clicking it.
A dialog is shown (c.f. figure 6.2).
51
Click Change Password and fill out the New Password and Confirm Password
fields.
On the License page of the dialog enable the functions the user is allowed to
use. Enable at least the Multi-User Database option.
Press OK.
52
53
Installation directory,
start the new PowerFactory version; logon as Administrator user and use the
same Database settings as used in the previous version
The existing database is now migrated to the new PowerFactory database structure.
Depending on the size of the database this may take several minutes up to hours.
Please don't interrupt the migration process.
Note: The migration resets all changes in these top-level objects:
System
Library
Demo
Administrator
Before you migrate, please make sure that these folders dont contain any data you
need afterwards.
Note: Since the existing database is migrated in-place, after the migration the
database can be accessed exclusively by the new PowerFactory version.
54
Then the DZ files exported should be imported. These files can be imported in
any sequence.
55