Professional Documents
Culture Documents
Powerfactory Installation Manual
Powerfactory Installation Manual
http://www.digsilent.de
Published by
DIgSILENT GmbH, Germany
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
1 Introduction
1.2 Overview
The delivery of the software includes:
CD-ROM with PowerFactory setup and License Server setup
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.
Installing the PowerFactory Demo version is quite simple, read chapter 2
(Demo Version). The further installation options hold only for the Full version.
If a network license is to be used the License Server must be installed and
configured. This step is not required for a single-user license. Chapter 3
(License) explains the different ways to install license keys. Especially the
setup of the License Server is covered.
If you are using PowerFactory with a multi-user database (e.g. Oracle or
MS SQL Server) the database server must be configured. The various
database options are covered in chapter 4 (Database).
full version:
network license:
single-user license:
demo version:
multi-user database:
configure PowerFactory for application server configure PowerFactory for file server
multi-user database:
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.
Place the installation CD into your CD-ROM-drive.
The setup will start automatically. If this does not occur then the setup may
be manually started using PreInstall.exe, located in the CD-ROM‟s root
directory.
During the installation select PowerFactory - Demo.
After completion of the installation start the program:
Start the PowerFactory application
A Log on dialog will appear (see figure 2.1).
Insert Demo as Name in the Log on dialog page. No Password is required.
The License page of this dialog should read as shown in figure 2.2.
On the other dialog pages leave the default settings.
Press OK .
When you‟re starting PowerFactory for the first time, the database is
initialized which may take several minutes.
Fig. 2.1 Demo Log On Settings (1) Fig. 2.2 Demo Log on Settings (2)
3 License
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.
Please make sure the following requirements are fulfilled before starting with the
installation of DIgSILENT PowerFactory:
Windows XP/Vista/Windows 7, Windows Server 2003 / 2008 / 2008 R2 only
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:
In the installation directory of the license server start diglsvc32.exe
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.
Copy getlicense.bin to the installation directory and overwrite the existing
file.
First run the license server application diglise.exe directly as Windows
application (not as windows service). Error messages will then pop up in case
of any installation problems (c.f. figure 3.3). The option Menu About
shows more details.
3.2.2 License Server Upgrade - Hardlock with floating license feature enabled
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.
DIgSILENT PowerFactory (client) will communicate with the license server via RPC
protocol by using binary files written to the license server working directory (Run):
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.
If the number of users is LIMITED, the PowerFactory client will periodically
check for the continued existence of the *.use file, and will modify the file to
reflect the time and date of its check. When the user terminates PowerFactory
the *.use file is deleted by the client.
If, for some reason, the link between the client and License Server is
broken, or if PowerFactory terminates abnormally, the *.use file remains in
the Run directory of the License Server. The file is automatically deleted
periodically and/or during the next software startup.
The number of *.use files that may be generated in response to client
requests corresponds to the number of user licenses the license key will allow
(dependent on how many user licenses have been purchased) compared to
how many other users are currently working with PowerFactory (as shown
in the License Server About Box).
If the number of license files is greater or equal to the maximum permitted
number of users, the license server will not respond.
When the license server program is terminated it will delete all license files!
Note: A PowerFactory client will be closed if his license file has
been deleted, or if the link to the license server is missing
when the periodic check for the *.use file is made. This will be
The License Server has several options, which can be modified by editing the file
diglise.ini:
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 DIgSI-
LENT 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.
Any firewall between license server and PowerFactory should open RPC port
135 (TCP) and also the preconfigured RPC-Endpoint port 4000 (TCP).
The DIgSILENT license server‟s task is to provide license information for each
PowerFactory client. This task includes the monitoring of the number of concurrent
users as well as the monitoring of the number of concurrently used functions. The
access to the various calculation functions is thus controlled by the License Server.
If the license agreement contains different number of functions, e.g. 4 base
packages and 2 stability functions for 4 concurrent users, then it is also possible to
configure the users account such that the user‟s functionality is limited.
The user‟s dialog box itself determines the functions this user has access to when he
is logged on to PowerFactory.
A right mouse click on a certain user in the data manager offers the menu entry
Edit. Selecting this entry opens the user‟s 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.
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.
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.
Activate using a local activation file: Merge a previous downloaded activation
file to the installation directories. The path to the previously downloaded
activation file must be specified.
4 Database
DIgSILENT PowerFactory uses a database to store the user‟s 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)).
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.
Move the archive to a secure place e.g. another hard disk.
Restoring the database is as easy as creating the backup:
Close PowerFactory if it‟s running.
Rename the existing DB folder in your PowerFactory working directory to
DBOLD.
Create a new empty DB folder.
Extract the archive into it.
4.2 Oracle
PowerFactory uses Oracle’s OCCI/OCI programming interface to communicate
with the server. OCCI/OCI itself uses a proprietary communication scheme on top of
TCP/IP.
PowerFactory supports Oracle versions as shown below:
Client: 11.2:
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).
SID_LIST_LISTENER =
(SID_LIST =
[...]
(SID_DESC =
(SID_NAME= PFSERVER)
(ORACLE_HOME = /opt/oracle/product/10.2.0)
)
)
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-
called tablespaces. It is suggested to create a new tablespace where
PowerFactory (and only PowerFactory) stores its data. You can adapt the
following SQL statement to your purposes:
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.
Define a password for PF. In this example we use aPasswordForPf.
Associate Default and Temporary tablespaces to schema PF. It is assumed
that a temporary tablespace TEMP is available.
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;
Start the Oracle instance process and Oracle listener process if they are not
already started.
Oracle Client: This package includes many Oracle tools (e.g. management
console, management tools, networking services, utilities etc.) which are not
actually required for using PowerFactory; supports TNS names.
Oracle Instant Client: This package contains only the files required for using
PowerFactory; doesn‟t support TNS names.
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, you‟ll have to install Oracle client 32bit.
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:
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.
Database driver: On the Database page select Oracle (Client Version 11.2) as
Database driver.
Database service: The Database service must conform to the format
//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 you‟ve 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
C:\app\product\11.2.0\client_1\oci\lib\msvc\vc9;C:\app\product\11.2.0\client_1\BIN
4.2.2 Backup
Describing Oracle’s 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.
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.
Standard Edition
Workgroup Edition
Express Edition
The Windows Installer 4.5 has to be installed first, as it is required to install the
.NET framework.
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.
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).
Microsoft provides the Express Edition as free download. You can download the
package from the Microsoft web site.
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
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.
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.
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.
The Instance Name 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 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.
Click Next.
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
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 it‟s 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
After starting PowerFactory, switch to the Database tab on the Log On dialog
shown below.
4.3.5 Backup
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 command prompt and enter (all in one line):
USE pfdb
GO
sp_change_users_login AUTO_FIX, pf
GO
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.
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):
Windows XP/Vista only
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.
The setup application copies the files to an installation directory, e.g. C:\DIg-
SILENT\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
and for the Spanish version
digpf.exe /lang:es
If you‟re using a single-user license: attach your license key to your computer
now.
Start the PowerFactory (digpf.exe) application.
A Log On dialog pops up. Insert the settings as follows:
Insert Demo as Name in the Log on dialog page. No Password is required (see
figure 5.2).
Leave the default settings on the Network page (see figure 5.4) (i.e. on local
machine) for now.
C:
+- DIgSILENT
+ pf140 // Installation directory
+- digpf.exe
+- set.dz
+- ...
D:
+- PowerFactoryData
+- Administrator
+- Demo
+- Frodo
+- Sam
+- Pippin
c:
cd c:\DIgSILENT\pf140b501
digpf.exe /config