Installation Manual 15.1 en

D
I
G
SILENT
PowerFactory
I NT E GR AT E D P OWE R S YS T E M ANALYS I S S OF T WAR E
DIgSILENT
PowerFactory 15.1
Installation Manual
DIgSILENT GmbH
Heinrich-Hertz-Strae 9
72810 Gomaringen / Germany
Tel.: +49 (0) 7072-9168-0
Fax: +49 (0) 7072-9168-88
info@digsilent.de
Please visit our homepage at:
http://www.digsilent.de
Copyright 2013 DIgSILENT GmbH
All rights reserved. No part of this
publication may be reproduced or
distributed in any form without permission
of DIgSILENT GmbH.
30. October 2013
CONTENTS
Contents
1 Introduction 1
1.1 Typographic Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.2 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.3 Hardware and Software Requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.4 Change History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.4.1 Changes in 15.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.4.2 Changes in 15.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2 Basic Installation 5
2.1 Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.2 PowerFactory Demo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.2.1 Install PowerFactory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.2.2 Demo License Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.3 PowerFactory Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.3.1 PowerFactory Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.3.2 Hardlock Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.4 PowerFactory Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.4.1 Install and congure License Server . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.4.2 Install and congure PowerFactory . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.5 Workspace and Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
2.5.1 Export and Import Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
2.5.2 Workspace Directory Conguration . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
2.6 Uninstall PowerFactory and License Server . . . . . . . . . . . . . . . . . . . . . . . . . 33
3 Advanced Installation 35
3.1 Multi-User Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
DIgSILENT PowerFactory 15.1, Installation Manual i
CONTENTS
3.1.1 Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
3.1.2 Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
3.1.3 Microsoft SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
3.1.4 Vault (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
3.1.5 User Management in PowerFactory . . . . . . . . . . . . . . . . . . . . . . . . . . 49
3.1.6 Housekeeping (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
3.2 Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
3.2.1 Workspace directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
3.2.2 PowerFactory Conguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
3.3 Ofine Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
3.3.1 PowerFactory in Normal Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
3.3.2 Ofine Proxy Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
3.3.3 PowerFactory in Ofine Mode Conguration . . . . . . . . . . . . . . . . . . . . . 68
3.3.4 PowerFactory Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
4 Upgrade and Migration 73
4.1 License Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
4.1.1 Upgrade Softkey License (Demo or Test Licenses) . . . . . . . . . . . . . . . . . . 73
4.1.2 Upgrade Hardlock License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
4.2 Install a PowerFactory Service Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
4.3 Upgrade PowerFactory Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
4.3.1 License Server Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
4.4 Data Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
4.4.1 Local Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
4.4.2 Multi-User Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
5 Reference 85
5.1 PowerFactory Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
5.2 PowerFactory Conguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
5.2.1 General Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
5.2.2 Database Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
5.2.3 License Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
5.2.4 Workspace Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
ii DIgSILENT PowerFactory 15.1, Installation Manual
CONTENTS
5.2.5 Advanced Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
5.3 PowerFactory Command Line Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 95
5.4 License Server Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
5.4.1 Advanced License Server Conguration . . . . . . . . . . . . . . . . . . . . . . . 96
5.4.2 Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
5.4.3 User Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
DIgSILENT PowerFactory 15.1, Installation Manual iii
CONTENTS
iv DIgSILENT PowerFactory 15.1, Installation Manual
CHAPTER 1. INTRODUCTION
Chapter 1
Introduction
1.1 Typographic Conventions
Typographical conventions used in this document:
Products of DIgSILENTGmbH 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 sub menu structures are denoted by an arrow in front of the rst element and all
following sub entries e.g. Menu Sub Menu Sub Sub Menu.
Internet addresses are written in http://underlined.fixed.width/font.
1.2 Overview
Depending on the installation type, a PowerFactory system can have several components which have
to be installed and congured separately.
chapter 2 on page 5 covers the basic installation options Demo Version, Workstation Version, and
Server Version
More advanced installation options e.g. multi-user database, installation on an application server,
and the Ofine mode installation covers chapter 3 on page 35.
1.3 Hardware and Software Requirement
DIgSILENT PowerFactory is a standard Windows desktop application. Both a 32-bit and a 64-bit ver-
sion are available. For PowerFactory 15.1 run efciently should, as a minimum, be equipped with:
DIgSILENT PowerFactory 15.1, Installation Manual 1
CHAPTER 1. INTRODUCTION 1.4. CHANGE HISTORY
Operating system: Windows XP, Windows Vista (x86/x64), Windows 7 (x86/x64). Windows Server
2003, 2008, 2008 R2
Processor: x86- or x64-bit with 1 GHz or faster
Memory: 2 GB RAM minimum
Hard disk with 1 GB of available disk space
SVGA graphic card with a resolution of at least 1280x1024 pixels
Requirements for DIgSILENT License Server are described in section 2.4.1.1 on page 18.
Some parts of the PowerFactory documentation are available only in PDF format. In order to read
these documents a separate viewer application (e.g. Adobe Acrobat Reader) is required.
1.4 Change History
This section gives a short overview over the installation-relevant changes in recent PowerFactory ver-
sions.
1.4.1 Changes in 15.1
The PowerFactory installation is now implemented according to ofcial Microsoft Windows guidelines
which brings many essential changes for users of former PowerFactory versions.
The default Installation directory is now
C:\Program Files\DIgSILENT\PowerFactory 15.1
instead of C:\DIgSILENT\pf151.
During normal operation PowerFactory does not write into the installation directory. The only
action that requires write access is changing the PowerFactory conguration (which is now stored
in a readable PowerFactory.ini le). In such rare cases Windows Administrator credential must
be provided in an User Account Control dialogue (see gure 2.1.1 on page 6).
The conguration is now stored in a readable and editable text le PowerFactory.ini (instead of
the binary set.dz).
PowerFactory does not write to the installation directory. So any user data (e.g. the database or
temporary les) have to be somewhere else. As suggested by Microsoft PowerFactory stores its
data now in a Workspace directory inside the Windows user prole e.g. in
C:\Users\UserName\AppData\Local\DIgSILENT\PowerFactory 15.1
The workspace concept including workspace backup and restore and workspace migration is
covered in section 2.5 on page 31.
The PowerFactory executable is nowPowerFactory.exe instead of digpf.exe or digkernel.exe
The installation on Application Server is much simpler now (section 3.2 on page 54).
The PowerFactoryDemo activation process was simplied (see section 2.2 on page 7).
This document has been thoroughly revised for 15.1.
2 DIgSILENT PowerFactory 15.1, Installation Manual
1.4. CHANGE HISTORY CHAPTER 1. INTRODUCTION
1.4.2 Changes in 15.0
New features:
Ofine Mode (see section 3.3 on page 58).
Housekeeping in multi-user databases (see section 3.1.6.2 on page 53).
Vault directory in multi-user scenarios (see section 3.1.4 on page 47).
CHAPTER 1. INTRODUCTION 1.4. CHANGE HISTORY
CHAPTER 2. BASIC INSTALLATION
Chapter 2
Basic Installation
This chapter describes the basic PowerFactory installation types: Demo Version (see section 2.2),
Workstation Version (see section 2.3 on page 12), and Server Version (see section 2.4 on page 18).
More advanced installation options (e.g. Multi-User Database, installation on Application Server, and
Ofine Mode) are discussed in chapter 3 on page 35.
Note: Installing PowerFactory requires Windows Administration rights. On Windows XP and Win-
dows Server 2003 please start the installer as Administrator user. Otherwise the installation will
fail. On newer Windows versions Windows asks for Administrator credentials when needed sec-
tion 2.1.1 on page 6.
2.1 Installer
DIgSILENT PowerFactory is an application for standard Windows operation systems. Both a 32 bit
and a 64bit version are available. The 32-bit version is shipped via CD. If the 64 bit version is required,
please download the installation le from our Customer Portal https://support.digsilent.de on the
DIgSILENTwebsite:
32-bit version: PF-15.1.X x86.exe
64-bit version: PF-15.1.X x64.exe
Installation from CD Insert the PowerFactory 15.1 CD into your CD or DVD drive. This will launch the
DIgSILENTSoftware PreInstaller which guides you the installation options. If the PreInstaller is
not started automatically, run PreInstall.exe manually.
Installation with installer Start the setup PF-15.1.X x64.exe (32 bit) or PF-15.1.X x86.exe (64 bit)
Windows User Account Control dialogue shows a list of Administrator users that are allowed to perform
administrative actions (see gure 2.1.1)
CHAPTER 2. BASIC INSTALLATION 2.1. INSTALLER
Figure 2.1.1: User Account Control Dialogue
Select a user and insert the appropriate password
Press Yes
The DIgSILENTSoftware PreInstaller is shown (see gure 4.2.1).
Figure 2.1.2: Software PreInstaller Dialogue
2.2. POWERFACTORY DEMO CHAPTER 2. BASIC INSTALLATION
The PreInstaller provides several install options which are described in the next sections:
PowerFactory Demo (see section 2.2)
PowerFactory Workstation (see section 2.3)
PowerFactory Server (see section 2.4)
On the bottom there links to various PDF documents.
2.2 PowerFactoryDemo
The demo version can run most implemented options and features, allows calculation of small networks
and the prepared tutorials and examples. It comes with a full tutorial net, accompanied with an on-
line 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 conguration are permitted by the program.
Note: Using the Demo version requires a license activation (see section 2.2.2).
2.2.1 Install PowerFactory
Start the DIgSILENTSoftware PreInstaller as described in section 2.1 on page 5. A DIgSILENT Soft-
ware PreInstaller dialogue is shown (see gure below).
Press PowerFactory Demo
The PowerFactory Setup Wizard is started (see gure below).
CHAPTER 2. BASIC INSTALLATION 2.2. POWERFACTORY DEMO
Figure 2.2.2: PowerFactory Setup: Welcome
Click Next and step through the wizard pages. Use the default settings.
After completion a success message is shown as shown in the gure below.
Figure 2.2.3: PowerFactory Setup: Completion
Click Finish
The PowerFactory Installation Wizard window is closed.
Close the DIgSILENTSoftware PreInstaller dialogue by pressing Close
PowerFactory is usually installed in C:\Program Files\DIgSILENT\PowerFactory 15.1. If you in-
stalled the 32 bit version on a 64 bit Windows the installation directory will be C:\Program Files
(x86)\DIgSILENT\PowerFactory 15.1. The Setup created a start short cut PowerFactory 15.1 on the
Windows desktop. You can start PowerFactory by double-clicking this short cut.
Figure 2.2.4: PowerFactory Start Short Cut on the Desktop
Besides two short cuts are created in Windows Start menu (Start All Programs DIgSILENT Software).
Figure 2.2.5: PowerFactory Short Cuts in Start Menu
Run PowerFactory 15.1 (Conguration) for conguring the application (section 5.2 on page 86). Run Pow-
erFactory 15.1 (Administrator) for administrative purposes (section 5.1 on page 85).
2.2.2 Demo License Activation
The software must be activated on your computer before it can be used. The activation involves several
steps:
1. Start PowerFactory which will create an Activation Request text for your installation.
2. Send an email with the Activation Request text to DIgSILENT
3. DIgSILENTs sales department sends an email with the Activation Key text back to you.
4. Import the Activation Key text into a PowerFactory
Lets begin: launch PowerFactory for the rst time.
Double-click the PowerFactory start short cut on your Windows desktop
CHAPTER 2. BASIC INSTALLATION 2.2. POWERFACTORY DEMO
A License Activation Overview dialogue is shown (see gure 2.2.6).
Figure 2.2.6: License Activation Overview dialogue
Press Create Activation Request
A License Activation Request dialogue is shown (see gure 2.2.7).
Figure 2.2.7: License Activation Request dialogue
Send the Activation Request text to DIgSILENTalong with some customer information:
If an default email application (e.g. Microsoft Outlook or Mozilla Thunderbird) is installed on
your computer, just press Open Mail Program and an email to DIgSILENTwill be prepared.
Adapt the email text and send it to license@digsilent.de
Otherwise send the email manually to license@digsilent.de. Copy and paste the email subject
and email text from the dialogue.
DIgSILENTs Sales Team will send a response email. Besides other information it will contain an Acti-
vation Key text that resembles the text below:
-----BEGIN ACTIVATION KEY-----
OD1bRz1AOUJIFEBdV1liZ1kUSiQkJCQkKiQlISYrKyiCcBhsXPZrccxL2ODYNn5utW/kOuuq
ThWowlQ1K5k/cNcFY0pksdl/MGsQu3sphd36wy2GBYAH2eNPgav8lAkmJKmlVPD6+p+R9L9R
tawITjtButTuj8zidIv575P96FhSZikjjCKh4rROPzti7CFsvjJsNK/op1EuuJ8kGhgq0cJh
Usu6VM3uwzb0KvlnUTr5PgfL6jxWJtSODSjAix25S1+WTAWJubd44mfrcHMFEPonWThgty4/
Aws10/TN
-----END ACTIVATION KEY-----
Import the key text now into PowerFactory .
In the License Overview Dialogue (gure 2.2.6) press Enter Activation Key.
An License Activation Key dialogue is shown (see gure 2.2.8).
Figure 2.2.8: License Activation Key dialogue
Copy the text (including the BEGIN ACTIVATION KEY line and the END ACTIVATION KEY line) from
the email and paste it into the text eld.
Press Apply Activation Key
Restart PowerFactory
CHAPTER 2. BASIC INSTALLATION 2.3. POWERFACTORY WORKSTATION
Then the application is ready to use (see gure 2.2.9).
Figure 2.2.9: PowerFactory after successful installation
2.3 PowerFactoryWorkstation
PowerFactoryWorkstation is delivered with a license hardlock (also known as hardware license key
or dongle). DIgSILENTprovides USB hardlocks.
Figure 2.3.1: Workstation License
Only one hardlock can be connected to one computer at the same time (see gure 2.3.1). The Power-
FactoryWorkstation installation takes two steps:
1. Install PowerFactory software
2. Activate the hardlock
2.3.1 PowerFactory Installation
If youre upgrading an existing PowerFactoryWorkstation installation: remove all existing USB
hardlocks
2.3. POWERFACTORY WORKSTATION CHAPTER 2. BASIC INSTALLATION
Press PowerFactory Workstation
Three packages are going to be installed now:
1. A system driver for the hardlock.
2. The License Server tool. This tool is required because PowerFactory is not able access the
hardlock hardware directly.
3. Finally, the PowerFactory application itself.
A Hardlock Driver Setup is started (see gure below).
Figure 2.3.3: Hardware Driver Setup
press Next and follow the instructions of the setup.
After having installed the hardlock driver successfully, the DIgSILENT License Server Setup wizard is
started (see gure 2.3.4).
Figure 2.3.4: License Server Setup
Press Next and follow the instructions of the installer. Use the default settings.
A success message conrms that the License Server service correctly congured (see gure 2.3.5).
Click Finish
The Hardlock needs activation before it can be used.
2.3.2 Hardlock Activation
The hardlock is required to run PowerFactory .
Plug in your hardlock.
A dongle activation is required when
a new dongle was delivered, or
an outdated guarantee was substituted by a maintenance contract, or
an outdated maintenance contract was resumed
An activation is simply downloading an activation le from the DIgSILENTsupport website and saving it
to the PowerFactory and License Server installation folder. DIgSILENTprovides the tool digactivate.exe
that is automatically for you. In order to get access to the DIgSILENTsupport website youve to provide
the users customer credentials are required. They can be found in the license agreement document.
run the activation tool digactivate.exe in the License Server installation directory
C:\Program Files\DIgSILENT\License Server\digactivate.exe
A License Activation Wizard dialogue is shown and will guide you through the activation process (see
gure below).
Figure 2.3.10: License Activation
Press Next
The dialogue provides three options (see gure below).
CHAPTER 2. BASIC INSTALLATION 2.4. POWERFACTORY SERVER
Activate directly from the Internet Download the activation le and save it to the appropriate installa-
tion directories.
Download the activation le without installation Download the activation le only. This options is
useful when the computer you installed License Server has no direct access to the internet.
Activate using a local activation le Save a previous downloaded activation le into to the installation
directories. The path to the previously downloaded activation le must be specied.
2.4 PowerFactoryServer
DIgSILENToffers the Network License to simplify the handling of hardlocks for companies using Pow-
erFactory on several computers. Network Licenses are shipped with a special hardlock, the Network
Hardlock. This hardlock is plugged to one computer in the computer network e.g. to a server or an-
other machine that runs continuously. All PowerFactory processes installed on any workstation in the
network is able to access a license from this server (see gure 2.4.1).
Figure 2.4.1: License Server
The network license requires an additional program which is also part of the installation package pro-
vided by download or CD-ROM: the DIgSILENT License Server . Setting up PowerFactory in an
License Server environment requires two steps:
1. Install and congure License Server on the server machine (see section 2.4.1).
2. Install and congure PowerFactory on all workstation machines (see section 2.4.2 on page 25).
The License Server does not need to be installed on a separate server computer. Instead the installa-
tion on one of the Workstation computers is also possible. License Server is started automatically as
a service when Windows starts up.
2.4.1 Install and congure License Server
2.4.1.1 Requirements
DIgSILENT License Server requires
Operating System: Windows XP, Vista, or Windows 7, Windows Server 2003, 2008, or 2008 R2.
2.4. POWERFACTORY SERVER CHAPTER 2. BASIC INSTALLATION
2.4.1.2 License Server Installation
Note: The installation has to be done on the console. A remote desktop session as Adminstrator will
not work correctly.
Remove all existing hardlocks
If a previous version of DIgSILENT License Server is already installed remove it completely as
described in section 4.3.1 on page 77.
Press PowerFactory Server
The Software PreInstaller dialogue allows now to choose the components to install (see gure 2.4.3).
check Hardlock Device Driver
uncheck PowerFactory
check Network License Server
press Start Installation...
A Hardlock Driver Setup is started (see gure below).
Figure 2.4.4: Hardware Driver Setup
press Next and follow the instructions of the setup.
After having installed the hardlock driver successfully, the License Server Setup wizard is started (see
gure 2.4.5).
Press Next and follow the instructions of the installer.
The default installation directory is C:\Program Files\DIgSILENT\License Server (see gure 2.4.6).
Figure 2.4.6: License Server Installation Directory
Plug network dongle in the server computer.
Verify that the dongle is valid and can be accessed by running License Server as a normal Windows
desktop application (and not as Windows service).
Run C:\Program Files\DIgSILENT\License Server\diglise.exe
A small DIgSILENT License Server application window appears (see gure 2.4.7).
Figure 2.4.7: DIgSILENT License Server Application
Error messages will be shown in case of any Hardlock or Hardlock driver problems.
Menu About displays useful information about the dongle (see gure 2.4.8).
Figure 2.4.8: License Server About Window
Close the DIgSILENT License Server application with Menu Exit.
DIgSILENT License Server is now congured correctly. Now it has to be registered as a service starting
automatically when Windows starts up.
Run the License Server Service Conguration tool diglsvc32.exe in the installation directory
(see gure 2.4.9).
Figure 2.4.9: License Server About Window
Press Install Service
Press Start Service
Verify that the License Server 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: After installation of a License Server which is Softkey (instead of Hardlock) protected, the Li-
cense Server has to be started as a Windows application rst. A dialogue box will pop up, please
follow the instructions.
Note: A network hardlock cannot be used as a local key for PowerFactoryWorkstation. It can only
be accessed PowerFactoryServer. However PowerFactory and the License Server may be in-
stalled and run on the same machine, so that a network hardlock may be used on a local machine
as long as the License Server is also running.
2.4.1.3 Other Settings
Any rewall between license server and PowerFactory should open RPC port 135 (TCP) and also
the precongured RPC-Endpoint port 4000 (TCP).
Advanced License Server conguration options are covered in the reference chapter (see section 5.4
on page 96).
2.4.1.4 Hardlock Activation
The hardlock is required to run PowerFactory .
Plug in your hardlock.
A dongle activation is required when
a new dongle was delivered, or
an outdated guarantee was substituted by a maintenance contract, or
an outdated maintenance contract was resumed
An activation is simply downloading an activation le from the DIgSILENTsupport website and saving it
to the PowerFactory and License Server installation folder. DIgSILENTprovides the tool digactivate.exe
that is automatically for you. In order to get access to the DIgSILENTsupport website youve to provide
the users customer credentials are required. They can be found in the license agreement document.
run the activation tool digactivate.exe in the License Server installation directory
C:\Program Files\DIgSILENT\License Server\digactivate.exe
A License Activation Wizard dialogue is shown and will guide you through the activation process (see
gure below).
Press Next
The dialogue provides three options (see gure below).
Activate directly from the Internet Download the activation le and save it to the appropriate installa-
tion directories.
Download the activation le without installation Download the activation le only. This options is
useful when the computer you installed License Server has no direct access to the internet.
Activate using a local activation le Save a previous downloaded activation le into to the installation
directories. The path to the previously downloaded activation le must be specied.
2.4.2 Install and congure PowerFactory
On each workstation computer PowerFactory must be installed and congured to connect to the Li-
cense Server .
2.4.2.1 Install PowerFactory
Press PowerFactory Server
The Software PreInstaller dialogue allows now to choose the components to install (see section 2.4.13).
uncheck Hardlock Device Driver
check PowerFactory
uncheck Network License Server
press Start Installation...
Click Finish
2.4.2.2 Congure PowerFactory
License Server must be congured in PowerFactory .
Start PowerFactory in Conguration Mode:
Open Windows Start menu and run Start All Progams DIgSILENT Software PowerFactory
(Conguration) (see gure 5.1.1 on page 85).
A PowerFactory Conguration dialogue is shown.
switch to the License page and insert the setting as shown below (see gure 2.4.18)
License Select PowerFactory Server
Server Name Insert the License Server computer address (e.g. 192.168.111.222) or computer name
(e.g. LICSERVER or LICENSE.COMPANY.COM).
Figure 2.4.18: License Server Conguration
License Server can be congured with advanced settings (see section 5.4.1 on page 96). These must
be also set on the Advanced sub page.
Finally, save the settings to conguration le PowerFactory.ini:
Press OK in the PowerFactory Conguration dialogue
Windows eventually shows an User Access Control dialogue and asks for an Administrator users
credentials in order to save the conguration le into the PowerFactory installation directory (see g-
ure 4.2.1 on page 75). Select an Administrative Windows user from the list, insert the users password,
and press Yes.
2.4.2.3 License Management
The License Server s task is to provide license information for each PowerFactory process. 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 congure the users account such that the
users functionality is limited.
The users dialogue 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 users dialogue box, which appears as gure 2.4.19 shows.
Figure 2.4.19: PowerFactory User Function Settings
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 user has the right to modify these settings. Section sec-
tion 5.1 on page 85 who start PowerFactory as Administrator.
If there are not enough licenses already occupied, the user will get an appropriate message when
starting PowerFactory . The Help About dialogue in PowerFactory then includes a list of all functions
the user occupies (see gure 2.4.20).
Figure 2.4.20: PowerFactoryHelp/About Dialogue
2.5. WORKSPACE AND BACKUP CHAPTER 2. BASIC INSTALLATION
2.5 Workspace and Backup
Since version 15.1 PowerFactory stores data in a workspace directory in the Windows user prole.
When a user named Frodo runs PowerFactory , the application data is stored usually in e.g.
C:\Users\Frodo\AppData\Local\DIgSILENT\PowerFactory 15.1\Workspace.ComHLsIb
The workspace directory contains
The local database including all projects and libraries.
Result les (e.g. results of simulation calculations)
Log les which are very useful when analysing application problems.
Temporary les.
2.5.1 Export and Import Workspace
Its possible to manipulate e.g. backup and copy Workspace directories directly. However PowerFac-
tory provides functionality for saving a workspace (including all les in all subdirectories) as a conve-
nient
*
.zip archive which can be used as data backup. Similarly an exported workspace
*
.zip le
can be easily be re-imported into the same PowerFactory installation (i.e. restoring a backup) or into a
completely different PowerFactory installation on another computer (data transfer, data migration).
Figure 2.5.1 shows the Workspace functions in PowerFactory s main menu.
Figure 2.5.1: PowerFactory Workspace Functions
Exporting a Workspace is straightforward:
Select Tools Workspace Export Workspace
A Save As dialogue is shown (see gure 2.5.2).
CHAPTER 2. BASIC INSTALLATION 2.5. WORKSPACE AND BACKUP
Figure 2.5.2: Export Workspace
(Optional) Select another target directory or le name
Press Save
The export may take some seconds.
Note: Its strongly suggested to create workspace backups on a regular basis.
A Workspace import is done quite similar:
Select Tools Workspace Import Workspace
Specify a
*
.zip le containing a valid PowerFactory workspace in the Open dialogue and press
Open.
Restart PowerFactory
Note: A Workspace import replaces the current Workspace with the imported Workspace i.e. the cur-
rent Workspace is completely deleted and can not be recovered.
2.5.2 Workspace Directory Conguration
Storing the Workspace in the Windows user prole is convenient, but it might not be suitable under
some special circumstances. Customers might want to choose a different Workspace directory:
A company-wide policy recommends that application data should be stored inside a given direc-
tory (e.g. D:\Data) which is part of the company-wide backup strategy.
Several Windows users e.g. Frodo, Sam, and Pippin want to work on the very same local
database. Though they cant work concurrently at the same time, they might work in turns. Then
the workspace should be in a directory accessible by all three users.
Several Windows users are running PowerFactory concurrently on an Application Server. The
installation on Application Server is described in section 3.2 on page 54.
Under these circumstances it makes sense to adapt the Workspace directory.
2.6. UNINSTALL POWERFACTORY AND LICENSE SERVER CHAPTER 2. BASIC INSTALLATION
If youre already working with PowerFactory and want to use the existing workspace to the new
location, export the workspace as described in section 2.5.1 on page 31.
Switch to the Workspace page (see gure 2.5.3).
Uncheck Use Default Workspace Directory
Insert e.g. D:\Data\PowerFactory as Workspace Directory
Figure 2.5.3: Workspace Conguration
and press Yes.
If you have exported the Workspace before: import the workspace now as described in sec-
tion 2.5.1 on page 31.
2.6 Uninstall PowerFactoryand License Server
Windows Program and Features dialogue (available via Control Panel Programs Programs and Fea-
tures) allows to un-install PowerFactory and/or License Server from the computer (see gure 2.6.1).
CHAPTER 2. BASIC INSTALLATION 2.6. UNINSTALL POWERFACTORY AND LICENSE SERVER
open Program and Features dialogue
nd DIgSILENT PowerFactory 15.1 or DIgSILENT License Server in the list
open the context menu by right-click and select Uninstall/Change
an Uninstaller wizard is shown. Follow its instructions.
Figure 2.6.1: Program and Features dialogue
Note: The un-installer removes the whole PowerFactory installation folder. Ensure that you saved im-
portant les somewhere else.
Un-installer doesnt remove the Workspace (see section 2.5 on page 31) which is usually stored in the
Windows users prole directory e.g. in
C:\Users\Frodo\AppData\Local\DIgSILENT\PowerFactory 15.1
If youre sure that you dont need this data any more: delete the Workspace directory manually
e.g. with Windows Explorer
CHAPTER 3. ADVANCED INSTALLATION
Chapter 3
Advanced Installation
The installation variants in this chapter usually make only sense in a multi-user context with a the
PowerFactory Server version (section 2.4 on page 18).
A multi-user database allows several PowerFactory users to work concurrently and share their
data (see section 3.1).
Several users can work on the same application server (see section 3.2 on page 54).
Ofine Mode is based on a multi-user database. It allows to run PowerFactory without a perma-
nent connection to the server (see section 3.3 on page 58).
3.1 Multi-User Database
Normally PowerFactory stores the user data in a local database on the computer where PowerFac-
tory is installed. When three PowerFactory users working three computers want to exchange data
between their database by exporting data to les from one database and importing the les into the
other database (see gure 3.1.1).
Figure 3.1.1: Local Databases
In a multi-user database all data is stored in one central database server (see gure 3.1.2).
CHAPTER 3. ADVANCED INSTALLATION 3.1. MULTI-USER DATABASE
Figure 3.1.2: Multi-User Database
Advantages of a multi-user database are
read-only or read-write sharing of projects
project locking mechanisms
better organization of company-wide data (e.g. library, DPL scripts, template projects)
backups have to be taken only from one database
PowerFactory supports two common commercial database systems:
Oracle Database Server (see section 3.1.2 on page 37)
Microsoft SQL Server (see section 3.1.3 on page 43)
3.1.1 Installation Overview
Steps:
1. Install PowerFactoryServer Version (see section 2.4 on page 18). Verify that the application runs
smoothly before proceeding with the next actions
2. Install and congure Oracle Database Server (see section 3.1.2 on page 37) or Microsoft SQL
Server (see section 3.1.3 on page 43) and congure connection settings in PowerFactory
3. (Optionally) Set up and congure a Vault directory (see section 3.1.4 on page 47)
4. Administrate the PowerFactory database e.g. create PowerFactory user accounts and user
groups (see section 3.1.5 on page 49).
5. (Optionally) Import projects, libraries, or other data from other PowerFactory installations
3.1. MULTI-USER DATABASE CHAPTER 3. ADVANCED INSTALLATION
3.1.2 Oracle
3.1.2.1 Requirements
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.
PowerFactory supports Oracle versions as shown below:
Server: 10.2 or higher
Client: 11.2:
PowerFactory 32bit (x86) requires the 32bit Oracle Client
PowerFactory 64bit (x64) requires the 64bit Oracle Client
Server Requirements: The Oracle server machine should full requirements as follows:
Dedicated server: the server machine should be used exclusively for PowerFactory .
CPU: two or more cores/processors
Memory: 2GB RAM or more
Hard disk: 100 GB or more
High network bandwidth (100 Mbit/s or higher) connection between the Oracle server and the
machines where PowerFactory is running.
Depending on the number of users and projects the above numbers have to be adapted.
This section describes the installation and usage of the Oracle database server and client.
Before you set up and congure the client computers in section 3.1.2.3 (Client Installation), the server
must be prepared as explained in section 3.1.2.2 (Server Installation).
3.1.2.2 Server Installation
Install the Oracle server software on the server computer (ORACLESERVER being the server computer
name used in this section). Please follow the Oracle Server installation instructions.
Let us assume that ORACLESERVER is accessible by the name oracleserver.domain.com in the net-
work. In order to use the Oracle server for PowerFactory you have to do the steps as follows:
Create a new Oracle database with a database name (SID) of PFSERVER (stands for: Power-
Factory Server) or use an existing one. The character set for the Oracle instance should be
WE8MSWIN1252.
An Oracle listener is needed on the server, in order to pass on connection requests from
clients to the database. If you created the database with the Oracle installer, the listener
is congured for you automatically. If you create the database manually, then congure the
listener using the Oracle Net Conguration Assistant tool.
(Recommended but not essential) create the database with redo log les sized at 500MB.
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 might adapt and use the SQL statement below to your purposes:
CREATE TABLESPACE "POWERFACTORYTABLESPACE"
LOGGING
DATAFILE D:\ORACLE\ORADATA\DIGSI\POWERFACTORYTABLESPACE.ora
SIZE 5000M REUSE
EXTENT MANAGEMENT LOCAL
The statement creates a newtablespace named POWERFACTORYTABLESPACE which is stored in a POWERFACTORYTABLESPACE.ora
le in the given directory. The le size is restricted to 5000M i.e. about 5GB.
In order to use the Oracle instance for PowerFactory one new Oracle schema is required. Create
a new schema with the default prole. We suggest the schema name PF.
Dene a password for PF. In this example we use aPasswordForPf.
Associate default and temporary tablespaces to schema PF. It is assumed that a temporary ta-
blespace TEMP is available.
Grant the roles CONNECT and RESOURCE and the system privileges UNLIMITED TABLESPACE and
ALTER SESSION to PF. You might use and adapt the SQL script below 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;
GRANT ALTER SESSION TO PF;
Start the Oracle instance process and Oracle listener process if they are not already started.
Note: The amount of tablespace space PowerFactory requires depends heavily on how PowerFac-
tory is used. The space is roughly proportional to the number of objects in PowerFactory . Ob-
serve the tablespace ll-state regularly (e.g. once per month) and increase the size limit accord-
ingly.
Note: Regarding the recommended sizing of the redo log les when creating the database; this con-
guration of the redo log les is to increase performance. PowerFactory can generate very large
quantities of redo data in short bursts. This is particularly the case when importing data, copying
large projects or deleting large projects. If for other reasons you require smaller redo log les, (for
example to reduce database recovery time), you should increase the number of log le groups as
an alternative to increasing the le size.
Note: It is highly recommended to backup the Oracle schema on a daily basis. A backup procedure is
described in section 3.1.2.5 on page 42
3.1.2.3 Client Installation
Two Oracle client packages can be used:
(Normal) 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 les required for using PowerFactory ;
doesnt support TNS names.
Both (normal) 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
will have to install Oracle Client 32bit.
Install and congure Oracle Instant Client Instant Client is a package of DLL les 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 (see
gure 3.1.3). PowerFactory uses these DLL les in order to communicate with the Oracle Database
server.
Figure 3.1.3: Database Figure: Oracle Instant Client installation folder
Install and congure (normal) Oracle Client
Please use the newest version of the 11.2 client and follow the installation documentation. It is as-
sumed that the client software is installed in C:\app\product\11.2.0\client 1 (see gure 3.1.4).
Figure 3.1.4: (Normal) Oracle Client installation folder
(Optionally) Its possible to add an TNS name entry for PFSin the conguration le
C:\app\product\11.2.0\client_1\network\admin\TNSNAMES.ORA
The entry could be e.g.
PFS =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = oracleserver)(PORT = 1521))
)
(CONNECT_DATA =
(SERVICE_NAME = PFSERVER)
)
)
Then the PFS TNS name can be used in the PowerFactory conguration.
3.1.2.4 PowerFactory Conguration
Switch to the Database page
Insert the database connection settings as described below (see gure 3.1.5)
Figure 3.1.5: PowerFactory Conguration for Oracle Server
Database driver select Oracle (Client Version 11.2)
Database service this eld describes the connection. It must be conform to the format
//host[:port][/servicename]
With the values used above (host=oracleserver, port=1521 (default port), and SID=PFSERVER)
the connection name is
//oracleserver/PFSERVER
If we had used a non-default port=8888 the connection name would be
//oracleserver:8888/PFSERVER
If youve installed a (normal) Oracle Client and made an entry (e.g. PFS) in the TNSNAMES.ORA
conguration le, you can use the TNS name instead. Then the Database service is just
PFS
Username and Password During the Oracle server setup an Oracle schema PF with the password
aPasswordForPf has been created. Enter these values in the Username and Password elds.
PowerFactory uses les in the Oracle Client installation folder the communication with the server. In
order to nd them, the installation folders must be congured explicitly:
Switch to the Advanced page
Insert the folders as described below (see gure 3.1.6)
Additional directories in PATH Oracle Instant Client installed e.g. in C:\instantclient 11 2:
C:\instantclient_11_2\vc9
C:\instantclient_11_2
(Normal) Oracle Client installed e.g. in 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
and press Yes.
3.1.2.5 Backup
Create Backup Describing Oracles backup facilities is far beyond the scope of this installation man-
ual. 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:\backups\database.dump owner=PF
where PF is the schema, aPasswordForPf is his password, PFS is the TNS name, and d:\backup
\database.dump is the lename of the dump le.
Note: During the export or import process no PowerFactory user should must not be active. This
backup strategy is suitable only for e.g. nightly backups.
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.
Restore Backup To re-import a database dump, rst drop and re-create the Oracle schema PF. Then
run the imp.exe tool:
imp.exe PF/aPasswordForPf@PFS file=d:\backup\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.
3.1.3 Microsoft SQL Server
Microsoft provides several editions of its relational database systemSQL Server, depending on Version
used (2005, 2008 and 2012 are supported):
Enterprise Edition
Standard Edition
Workgroup Edition
Express Edition
DIgSILENT PowerFactory is capable to use all editions as database engine. The free Express Edition
provides almost the same functionality as the other editions but limits database size to 4 GB and lacks
some of the more advanced administration tools. For a complete list of features for all editions consult
the ofcial SQL Server Homepage.
SQL Server operates as a service. Services are applications that run as background processes. The
behaviour of services differs from that of other applications. For example, while most applications
are executed only when a user launches the application from the Start menu, services such as SQL
Server are generally started and stopped by the operating system environment. A service runs in the
background and waits for processing requests. In the case of SQL Server, these requests are for
database operations.
All actions described in this section are to be done on the server computer. Throughout this section
SERVERNAME is used as computer name.
3.1.3.1 Server Installation
Install the SQL Server software according to its documentation.
3.1.3.2 Server Conguration
Before the SQL Server service can be used it must be congured to allow for connections over the
network.
From the Start Menu select:
Microsoft SQL Server 20xx, depending on the version installed
Conguration Tools
SQL Server Conguration Manager
Expand the SQL Server 20xx Network Conguration node
Click on Protocols for SQLEXPRESS node (or the instance name you congured during installa-
tion respectively)
On the right side, right click the TCP/IP entry and select Enable from the context menu
Click on the SQL Server 20xx services node
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 congured to allow network connections. With the next steps a
database for PowerFactory is created.
Again, from the Start Menu select:
Microsoft SQL Server 20xx
SQL Server Management Studio Express
Change Authentication to SQL Server Authentication
Enter the login name sa and enter the Password for sa, chosen during installation
Select File New Query with Current Connection
Enter the following lines in the Query Window to the right:
sp_addlogin pf, aPasswordForPf
GO
CREATE DATABASE pfdb
GO
ALTER DATABASE pfdb SET ALLOW_SNAPSHOT_ISOLATION ON
GO
USE pfdb
GO
sp_grantdbaccess pf
GO
GRANT CREATE TABLE TO pf
GO
Click Execute in the toolbar
You have now created a database named pfdb with a corresponding login named pf which uses the
password aPasswordForPf. Feel free to change the values according to your needs.
Note: It is highly recommended to create daily backups of the database. The backup procedure for
SQL Server is described in section 3.1.3.4
3.1.3.3 PowerFactory Conguration
Figure 3.1.7: PowerFactory Conguration for SQL Server
Database driver select Microsoft SQL Server
Database service The Database service uses the format server name\instance name. If you
used the default values SQL Server provides, it would be SERVERNAME\SQLEXPRESS for the 2008
edition. SERVERNAME is our virtual server name during this manual, as stated earlier. Note that
the 2005 edition uses something called default instance, which must be accessed by omitting
the instance name in the Database service. So its just SERVERNAME for the 2005 edition.
Username, Password, and Database name for this manual it would be pf as username, aPasswordForPf
as password and pfdb as database name.
and press Yes.
3.1.3.4 Backup
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 ofcial Microsoft documentation for detailed
backup strategies. We present a very simple method to backup a database and must stress that this
method only satises 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):
sqlcmd -S SERVERNAME\SQLEXPRESS -U sa -P aPasswordForSa -e
-Q "BACKUP DATABASE pfdb TO DISK=d:\backupdir\pfdb.dump WITH INIT"
This dumps the database named pfdb to a le d:\backupdir\pfdb.dump, sa and
aSecurePasswordForSa are username and password of the database administrator user.
It is suggested to create a batch script which performs this task. To do so:
Open a new batch le e.g. d:\backupdir\backup.bat with a text editor (e.g. Windows Notepad
editor).
Insert the above text into the le (all in one line!).
Close the le.
Windows Scheduled Tasks utility allows you to run this batch script automatically, for example every
day at midnight.
Open the scheduler manager Windows Start menu:
Start Programs AccessoriesSystem Tools Scheduled Tasks
Add a new scheduler task PowerFactory backup and congure it as follows (see the Windows
documentation for further information)
Enter the backup script d:\backupdir\backup.bat to be run.
Select the daily option and 00:00 as start time.
This conguration creates nightly backups. The pfdb.dump le is overwritten each time. If you want to
keep the latest three backup dumps enhance the above backup.bat script as follows.
Open the batch script created earlier
Replace its contents with the following lines (again, the sqlcmd command in one line)
copy d:/backupdir/pfdb2.dump d:/backupdir/pfdb3.dump
copy d:/backupdir/pfdb1.dump d:/backupdir/pfdb2.dump
copy d:/backupdir/pfdb.dump d:/backupdir/pfdb1.dump
sqlcmd -S SERVERNAME\SQLEXPRESS -U sa -P aPasswordForSa -e
-Q "BACKUP DATABASE pfdb TO DISK=d:/backupdir/pfdb.dump WITH INIT"
Save the le.
Restore a Backup The RESTORE DATABASE command recovers a database from a dump le. To
restore a database backup on the same database server where it was created follow the instructions
below.
Run sqlcmd from the command prompt
sqlcmd -S SERVERNAME\SQLEXPRESS -U sa -P aPasswordForSa
Run the following commands inside sqlcmd
DROP DATABASE pfdb
GO
RESTORE DATABASE pfdb FROM DISK=c:/backupdir/pfdb.dump WITH RECOVERY
GO
Restoring the database on a different SQL Server installation is more complicated. Let c:\msde2 be
the installation folder of the target SQL Server. All commands are to be run inside sqlcmd.
First create a database user pf for PowerFactory usage.
sp_addlogin pf, aPasswordForPf}
GO
Import the database dump as follows:
RESTORE DATABASE pfdb
FROM DISK = d:\backup\pfdb.bak
WITH MOVE pfdb TO C:\msde2\mssql\data\pfdb.mdf,
MOVE pfdb_log TO C:\msde2\mssql\data\pfdb.ldf,
RECOVERY
GO
Adjust the access rights of the pf user
USE pfdb
GO
sp_change_users_login AUTO_FIX, pf
GO
3.1.4 Vault (optional)
The Vault is a shared directory where all PowerFactory instances can read and write les. Two Pow-
erFactory features require a Vault:
Shared Result Files PowerFactory stores almost all data in the database. Result Files are an
exception. Result Files are binary les containing the result of simulation calculation. Due to
performance reasons (these results can be arbitrarily large) they are not stored in the database
but directly in les on the hard disk of the local computer.
Result Files are actually redundant since they are re-created when re-running the calculation.
However since a simulation calculation can take hours to nish, its worth to keep them at hand.
In a multi-user database scenario where two PowerFactory users USER1 and USER2 work on
the very same project, USER2 cannot access the Result Files created by USER1 because theyre
stored on USER1s hard disk.
Result Files in a Vault directory can be accessed by all PowerFactory users working on the same
multi-user database (see gure 3.1.8).
Project Archiving: since PowerFactory version 15.1 users can archive their projects. The projects
are exported into an Archive folder in the Vault directory and then deleted from the database.
Users can restore them later. The Housekeeping conguration allows to archive projects that
have not been used for a long time automatically.
Figure 3.1.8: Fileserver Vault
The Vault is a shared directory on a le server where all PowerFactory users (i.e. the Windows users
running PowerFactory ) have read and write access. The Vault directory path has to be congured in
PowerFactory .
Figure 3.1.9: PowerFactory Conguration for SQL Server
Vault Directory specify a path e.g. a mapped network drive
E:\path\to\vault\directory
or the raw network path.
\\vaultserver\path\to\vault\directory
The specied directory must exist and the current Windows must have read and write access to
this directory.
and press Yes.
Note: A Vault directory is required only in rare scenarios e.g. when PowerFactory users often run
long-running simulations and work on the very same shared project, or when using the project
archiving feature. In all other cases dont set up a Vault.
Note: Its strongly suggested to create Vault backups on a regular basis.
3.1.5 User Management in PowerFactory
Using PowerFactory in a multi-user environment requires some additional administrative management
which is subject of this section.
User accounts and credentials must be created and congured.
Users can be organized in User Groups.
In this section the term User always refers to a PowerFactory user (and not to physical database server
user e.g. on Oracle, SQL Server, or the Windows users).
3.1.5.1 User Authentication
In a multi-user database users usually have to log in with user credentials i.e. user name and password
(see gure 3.1.10).
Figure 3.1.10: User Authentication Dialogue
3.1.5.2 Administrator User and Password
Administrative actions have to be carried out as a special built-in PowerFactory user: the Administrator
user. The default Administrator password is Administrator. In a multi-user environment it is strongly
suggested to change this password immediately after the installation:
Start PowerFactory in Administrator mode:
(Administrator) (see gure 5.2.1 on page 87).
If no Data Manager window is opened: create a new one by clicking on the icon .
Double-click the Administrator.IntUser object in the data manager.
A user dialogue pops up (see gure 3.1.11).
Figure 3.1.11: Setting the Administrator Password
Click on the Change Password button.
Enter a new Password. Repeat the password in the Confirm Password eld.
Press OK to save the changes.
3.1.5.3 User Creation
The PowerFactory Administrator user is able to create and modify PowerFactory user accounts in a
multi-user database.
Start PowerFactory in Administrator mode:
(Administrator) (see gure 5.2.1 on page 87).
If no data manager is opened: create a new one by clicking on the icon .
Edit the User Manager object inside the Configuration folder by double clicking it.
A dialogue is shown (c.f. gure 3.1.12).
Figure 3.1.12: Create PowerFactory User
Click the button Add User....
In the User dialogue insert at least the eld User name.
Click Change Password and ll out the New Password and Confirm Password elds.
Create the new user by pressing OK.
A new user object (e.g. Frodo.IntUser) is created and shown in the data manager. Assign the function
rights to the new user.
Edit the Frodo.IntUser object (gure 3.1.13).
On the License page of the dialogue enable the functions the user is allowed to use. Enable at
least the Multi User Database option.
Press OK.
Figure 3.1.13: Congure PowerFactory User
3.1.6 Housekeeping (optional)
Over the course of time the database grows and is cluttered with old data that might have a general
negative impact on the database performance. PowerFactory provides a Housekeeping job that can
be congured to be run as periodical background job e.g. every night.
Deletion of items older than a congurable age in all users recycle bin.
Archiving (or even complete deletion) of projects that have not been activated recently.
Regular purge of project storage.
3.1.6.1 Housekeeping Conguration
The PowerFactory Administrator user is able to congure the Housekeeping settings (see gure 3.1.14).
Please nd the details in the PowerFactoryUser Manual.
Figure 3.1.14: Housekeeping Conguration
3.1.6.2 Scheduling Housekeeping
This is an optional installation step that can be carried out at a later date. Housekeeping is described in
the Program Administration chapter of the PowerFactoryUser Manual.
Housekeeping is executed via a Windows Scheduled Task from a computer with PowerFactory in-
stalled. Typically this will be a terminal server (e.g. Citrix) or some other application server. Housekeep-
ing makes use of a command line initiation of PowerFactory . An example execution is as follows:
"C:\Program Files\DIgSILENT\PowerFactory 15.1\PowerFactory.exe" /housekeeping:8:60
In the example above, 8 species the maximum run duration of the housekeeping as eight hours. If
the housekeeping is scheduled to start at 11 p.m. and is still not nished at 7 a.m., it will exit after
completing its current action.
In the example above, 60 species the sleep period, in seconds, after a housekeeping action. If there
were no sleep period the housekeeping would place a heavy workload on the system, possibly affecting
other active users.
Housekeeping connects as a special administrative PowerFactory user called Housekeeper, which is
automatically created when housekeeping is run for the rst time.
The housekeeping execution should be triggered via a Windows Scheduled Task (Windows 2008: Con-
trol Panel/Administrative Tools/Task Scheduler/Create Task). An example of the action conguration is
shown in gure 3.1.15.
CHAPTER 3. ADVANCED INSTALLATION 3.2. APPLICATION SERVER
Figure 3.1.15: Conguring a scheduled task to run housekeeping
Program/script Insert the path to the PowerFactory executable e.g.
"C:\Program Files\DIgSILENT\PowerFactory 15.1\PowerFactory.exe"
The leading and trailing quote characters (") are required since the path contains space charac-
ters.
Add arguments (optional) Insert the housekeeping parameters e.g.
/housekeeping:8:60
Windows scheduled tasks can be automatically stopped. It is preferable to congure this via the house-
keeping maximum run duration parameter, but the scheduled task conguration can be used as a back-
stop. When conguring the scheduled task, choose an appropriate operating system user to run the
task. The user does not need to be logged on.
3.2 Application Server
An Application Server (e.g. Citrix Application Server) allows to run an application several times in
parallel Windows sessions. A typical scenario for a PowerFactory installation is shown in gure 3.2.1.
Several machines and components are involved:
3.2. APPLICATION SERVER CHAPTER 3. ADVANCED INSTALLATION
Many Workstations The actual PowerFactory user works locally on his Workstation. When the user
starts the application, a PowerFactory process is started on the Application Server. The applica-
tion windows is shown on the Workstation.
One or more Application Servers One or more instances of PowerFactory are running on this server.
There might be several Application Server Computers organized in a Server Farm.
Database Server Manages the central PowerFactory database. All PowerFactory instances commu-
nicate with it.
Vault File Server (Optional) provides a shared Vault directory (section 3.1.4 on page 47).
License Server Part of a normal Server Version installation (see section 2.4 on page 18). The License
Server doesnt have to run necessarily on a separate computer, it can be hosted on the Application
Server.
Figure 3.2.1: Application Server Environment
Installing PowerFactory on an Application Server offers several advantages over a normal multi-user
database installation:
PowerFactory has to be congured only once on the Application Server computer, but can be
used by potentially hundreds of Workstations.
A high-bandwidth network connection is necessarily required between PowerFactory and a database
server. Bigger companies have their PowerFactory users distributed over several remote loca-
tions with low-bandwidth network.
Figure 3.2.1 suggests that all components have to be installed on different machines. But its possible
to deploy several components on the same computer e.g. the Application Server machine can host
PowerFactory , License Server , and the Vault directory.
Note: PowerFactory is executed in its entirety on the application server. It is important that the server
complies with PowerFactory s computing requirements: RAM, CPU(s), hard disk space, etc.
This section describes how to congure PowerFactory on application server for three Windows users
Frodo, Sam, and Pippin. It is assumed that
PowerFactory Server Version is already installed on the computer according to section 2.4 on
page 18.
CHAPTER 3. ADVANCED INSTALLATION 3.2. APPLICATION SERVER
Additionally a multi-user database should be up and running as described and PowerFactory is
congured to use it section 3.1 on page 35.
The PowerFactory installation directory (usually C:\Program Files\DIgSILENT\PowerFactory 15.1)
contains
PowerFactory the application binary PowerFactory.exe along with several DLL les
the conguration le PowerFactory.ini
other data e.g. a template for initial database content, Demo examples etc.
C:\
+ Program Files
+- DIgSILENT
+- PowerFactory 15.1
+- PowerFactory.exe // executable
+- PowerFactory.ini // configuration
+- ...
Each Windows user that runs PowerFactory requires a separate workspace directory which will hold
temporary data and log les. The workspace directories are subfolder of a common workspace directory
e.g. d:\Data\PowerFactory Workspaces:
D:\
+- Data
+- PowerFactory Workspaces
+- Frodo // Frodos workspace directory
+- Sam // Sams workspace directory
+- Pippin // Pippins workspace directory
+- ...
+- vault // (optional) common Vault data
The vault directory is optional (see section 3.1.4 on page 47). The workspaces directory must not be
necessarily on a local hard disk. It can be on an network drive instead e.g. \\SERVER\PowerFactory
Workspaces.
3.2.1 Workspace directories
Create a root directory for all Workspaces e.g.
D:\Data\PowerFactory Workspaces
Create a Workspace directory for each Windows user:
D:\Data\PowerFactory Workspaces\Frodo
D:\Data\PowerFactory Workspaces\Sam
D:\Data\PowerFactory Workspaces\Pippin
Verify that each Windows user has read and write access to his Workspace directory
(optional) Create a Vault directory e.g.
3.2. APPLICATION SERVER CHAPTER 3. ADVANCED INSTALLATION
D:\Data\PowerFactory Workspaces\vault
Verify that each Windows user has read and write access to the Vault directory.
3.2.2 PowerFactory Conguration
Switch to the Workspace page
Insert the directory settings as described below (see gure 3.2.2)
Use Default Workspace Directory Uncheck this item.
Directory Insert
D:\Data\PowerFactory Workspaces\%USERNAME%
%USERNAME% will be replaced by the current Windows username.
(Optional) If your using a vault directory, set the Vault Directory on the Database as described in
section 3.1.4 on page 47.
and press Yes.
CHAPTER 3. ADVANCED INSTALLATION 3.3. OFFLINE MODE
3.3 Ofine Mode
Since Version 15.0 PowerFactory provides the ability to work in Ofine Mode when a network con-
nection to the database server is unavailable. The required project data is cached to the users local
machine, which can then later be synchronized to the server database. Floating licenses are generated
which allow to work without a permanent connection to a License Server .
Note: Ofine Mode requires Multi-user database and Floating Licenses module.
This section describes the installation and conguration of the Ofine Proxy Service, a software com-
ponent of PowerFactory to be used with the Ofine Mode database driver on Microsoft Server 2008
R2. Figure 3.3.1 gives an overview over all components.
Figure 3.3.1: Ofine Mode Components Overview
The installation procedure consists of the following steps:
1. First a PowerFactory environment in normal (i.e. not-ofine) mode has to be set up. It contains at
least a PowerFactory installation, a License Server , and a multi-user database server (Oracle
or SQL Server) (see section 3.3.1).
2. Installation of the Ofine Proxy Serviceon an application server (see section 3.3.2).
3. Conguration of an Ofine PowerFactory (see section 3.3.3).
A nal section describes the procedure when upgrading to a newer PowerFactory version (see sec-
tion 3.3.4).
3.3.1 PowerFactory in Normal Mode
Before Ofine Mode can be set up PowerFactory Server Version (see section 2.4 on page 18) must
be installed and a multi-user database must be congured and initialized (see section 3.1 on page 35).
The Floating License module must be part of the license.
3.3. OFFLINE MODE CHAPTER 3. ADVANCED INSTALLATION
Figure 3.3.2: Ofine Mode Components Overview for Online PowerFactory
The Database page of the PowerFactory Conguration might resemble gure 3.3.3
Figure 3.3.3: PowerFactory Database Conguration
Relevant for the Ofine Proxy Serviceconguration are the parameters below:
Oracle Database Server parameters
Connection specier (e.g //servername/instancename)
Oracle user name (e.g. schemaname) and password
A network path to the vault directory (e.g. \\vaultserver\vaultfolder)
SQL Server parameters
Connection specier (e.g servername\instancename)
SQL Server user name (e.g. schemaname) and password
SQL Server database name
A network path to the vault directory (e.g. \\vaultserver\vaultfolder)
3.3.2 Ofine Proxy Service
Figure 3.3.4: Ofine Mode Components Overview for Ofine Proxy Service
3.3.2.1 Requirements for Oracle
Either Oracle Instant Client 11.2 or a normal Oracle Client 11.2 is required. The architecture must
match the one of the Ofine Proxy Serviceto be installed, either 32 Bit or 64 Bit.
Oracle Instant Client To be able to access the Oracle Database you need to install a driver called Or-
acle Instant Client. It is also used with PowerFactory and can be obtained from the Oracle Homepage.
The Ofine Proxy Servicerequires version 11.2.
Download the ZIP package from there.
Unzip the package to the hard drive, preferably to C:\oracle\instantclient 11 2.
(Normal) Oracle Client Install the Oracle Client using the installer.
3.3.2.2 Requirements for SQL Server
There are no additional requisitions.
3.3.2.3 Ofine Proxy ServiceInstallation
The Ofine Proxy Serviceis installed using a Microsoft Installer (MSI) package. The installer les can
be found in the offlinemode sub directory in the PowerFactory installation directory. They are named
OfflineServiceInstaller 2 2 x86.msi (32bit)
OfflineServiceInstaller 2 2 x64.msi (64bit)
Both PowerFactory 32bit and 64bit works with both the 32bit and the 64bit version of the Ofine Proxy
Service.
Run the appropriate MSI installer
The installer will rst check if the prerequisites are fullled. You will get the error shown below if the
Microsoft .NET Framework 3.5 is missing (see gure 3.3.5).
Figure 3.3.5: Installer error for missing .NET Framework
Press No in this dialogue and add the Application Server Role using the Server Manager Tools.
To do this, navigate from the Start Menu to Administrative Tools / Server Manager. Select the Roles
section to the left. In the right pane click on Add Role and select the Application Server role.
Continue until the Role Services are shown. Make sure the .NET framework is selected and continue
until the installation starts.
If you meet the prerequisites for installing the Ofine Proxy Serviceyou will be greeted by the Setup
Wizard (see gure 3.3.6).
Figure 3.3.6: Ofine Proxy ServiceInstaller: Welcome
Press Next until you can select the Installation Folder (see gure 3.3.7).
Figure 3.3.7: Ofine Proxy ServiceInstaller: Select Installation Folder
Press Next
Figure 3.3.8: Ofine Proxy ServiceInstaller: Conrm Installation
Press Next
Finally the service installation is completed (see gure 3.3.9):
Figure 3.3.9: Ofine Proxy ServiceInstaller: Installation Complete
Press Close
The Ofine Proxy Serviceexecutable and conguration les are located in the folder
C:\Program Files\DIgSILENT\Offline Service
Figure 3.3.10: Ofine Proxy ServiceInstallation Directory
Before starting the Ofine Proxy Service, it must be congured.
3.3.2.4 Conguration le offline.ini
Navigate to the directory where you have installed the Ofine Proxy Serviceand nd the le offline.ini.
Open it with any Text Editor, for example Notepad. It will look like this:
[Network]
Port=9401
[Database]
Type=Oracle
DataSource=//servername/instancename
UserId=schemaname
Password=schemapassword
VaultPath=\\vaultserver\vaultfolder
[Folders]
DataRoot=E:\temp\offline
AdditionalPath=C:\oracle\instantclient_11_2
The different sections and their contents in detail:
Network Settings
[Network]
Port=9401
Port This port is opened by the server machine to accept incoming connections. It may be necessary
to add an inbound rule to the Windows Firewall. This is covered later in this document.
Database settings for Oracle
[Database]
Type=Oracle
DataSource=//servername/instancename
UserId=schemaname
Password=schemapassword
Type Must be set to Oracle
DataSource A string dening the server machine and Oracle instance to connect to.
UserId The Oracle user/schema id where the PowerFactory database schema is stored.
Password The encrypted (!) password for the Oracle user. Must be set using the console.exe using
the /setdbpassword command from a command shell. Open a command window in the installa-
tion directory and type
console /setdbpassword <password>
VaultPath the vault network folder by PowerFactory
These values should match the Database settings in the Online PowerFactory log on dialogue as
described in section 3.3.1.
Database settings for SQL Server
[Database]
Type=SqlServer
Server=servername\instancename
UserId=sqlserverUsername
Password=sqlserverPassword
Database=sqlserverDatabase
Type Must be set to SqlServer
Server A string dening the SQL Server machine and the instance name.
UserId The SQL Server user id
Password The encrypted (!) password. Must be set using the console.exe using the /setdbpassword
command from a command shell. Open a command window in the installation directory and type:
console /setdbpassword <password>
Database the database name
VaultPath the vault network folder by PowerFactory
These values should match the Database settings in the Online PowerFactory log on dialogue as
described in section 3.3.1.
Folder settings
[Folders]
DataRoot=E:\temp\offline
AdditionalPath=C:\oracle\instantclient_11_2
DataRoot This is a directory for temporary les created by the Ofine Proxy Service. It may be
necessary to change the access rights on this directory. This is covered later in this document.
AdditionalPath The directories added here are temporarily added to the system PATH variable for
this application only. This can be used to tell the Ofine Proxy Servicewhere to nd the Ora-
cle Instant Client libraries without modifying the systems PATH variable using Windows system
settings.
Per default, the Ofine Proxy Servicewill write log messages to the Windows application log. This
behaviour is congurable through the le service.exe.config.
3.3.2.5 Setting up Security and Access Rights
The Ofine Proxy Serviceis run as using the system NETWORK SERVICE user account.
It is mandatory for the NETWORK SERVICE account to have read and write access to the directory
specied as Folders/DataRoot folder. It is also mandatory to allow incoming connections on the
port specied under Network/Port.
It is mandatory for the NETWORK SERVICE account to have read&write access to the directory
specied as Database/VaultPath
It is mandatory for the NETWORK SERVICE account to have read&write access to the folder con-
gured for logging C:\Program Files\DIgSILENT\Offline Service
Oracle only: Besides the NETWORK SERVICE account requires a read access to the Oracle Instant
Client directory.
3.3.2.6 Firewall Settings
To allow connections from remote clients to the Ofine Proxy Service, the congured port must be
added as Inbound Rule to the Windows Firewall. Open the Windows Firewall with Advanced Secu-
rity MMC Snap-In via Start / Administrative Tools.
Right click on Inbound Rules and select New Rule...
Set Rule Type to Port and click Next
Set Protocol to TCP. Enter the Port number that is congured in the conguration le for Net-
work/Port and click Next.
Select Allow the Connection and click Next.
Check whatever is suitable for when this new rule is to be applied. This depends on your corporate
network policy and click Next.
Enter a Name and Description and click Finish.
Service Conguration in the MMC: No special actions needed. All general settings are working as usual.
3.3.2.7 Verify Conguration
Log on to the server as the Windows user, which will run the Ofine Proxy Serviceas Windows
service.
Open a DOS console
Change directory to the installation directory
Run console
Now the Ofine Proxy Serviceis started as a normal console application and writes messages into the
console window:
C:\Program Files\DIgSILENT\Offline Service>console
2011-11-09 14:48:50,343 [1] INFO Offline.Program - Acting as OfflineProxy Server.
2011-11-09 14:48:50,390 [1] DEBUG Offline.Engine - Engine.Start() ...
2011-11-09 14:48:50,781 [1] DEBUG Offline.Sockets.SocketServer -
FileServerHandler(d:\tmp\offline_tmp) ...
2011-11-09 14:48:50,781 [1] DEBUG Offline.Sockets.SocketServer - ...
FileServerHandler(d:\tmp\offline_tmp)
2011-11-09 14:48:50,781 [1] DEBUG Offline.Sockets.SocketServer -
FileServerHandler(\\oracleserver\fullshared\offline_vault) ...
2011-11-09 14:48:50,781 [1] DEBUG Offline.Sockets.SocketServer - ...
FileServerHandler(\\oracleserver\fullshared\offline_vault)
2011-11-09 14:48:50,781 [1] DEBUG Offline.Engine - ... Engine.Start()
Press Return to exit
Verify that no errors are reported.
press Return key and close window
If there are any errors, adapt the conguration accordingly and restart console until there are no more
errors.
3.3.2.8 Start the Ofine Service
Having resolved all conguration errors Ofine Proxy Serviceis ready to run as a Windows Service.
Open Windows Services console window and start the Service.
Right-click on Offline Service, and select Start in the context menu (see gure 3.3.11).
Figure 3.3.11: Windows Services
Adapt the service settings:
Right-click on Ofine Service, and select Properties in the context menu
An Ofine Service Properties dialogue is shown.
Set the Startup type to Automatic.
Figure 3.3.12: Ofine Service Properties
Eventually adapt the Windows user in the Log On tab.
The service writes messages into the log le
C:\Program Files\DIgSILENT\Offline Service\service.log
Before you proceed with the next section, verify that this log le was created and that there are no error
messages in the log le.
3.3.3 PowerFactory in Ofine Mode Conguration
On each of the Workstations PowerFactory has to be congured in order to communicate with the
Ofine Proxy Service(see gure 3.3.13).
Figure 3.3.13: Ofine Mode Components Overview for Ofine PowerFactory
Figure 3.3.14: PowerFactory Conguration for Ofine Mode
Database driver select Offline Proxy Server
Database service insert the host name or IP address of the Ofine Server machine, followed by :
and the port number e.g. servername:9401 or 192.168.32.367:45600
Switch to the License page
Insert the license connection settings as described below (see gure 3.3.15)
Figure 3.3.15: License Settings for Ofine Mode
License Select PowerFactory Server.
License Server Name insert the host name or IP address of the DIgSILENT License Server server.
Switch to the Advanced sub page
Insert the advanced license connection settings as described below (see gure 3.3.16)
Figure 3.3.16: Advanced License Settings for Ofine Mode
Ofine licensing Choose Create offline license if the license should be locked for a Offline
License Validity days. Choose Create online server license only, if there is a per-
manent connection to the License Server .
and press Yes.
3.3.4 PowerFactory Upgrade
This section describes the steps to take when PowerFactory is upgraded to a new version e.g. from
15.0.3 to 15.1.0.
3.3.4.1 Step 0: Create Data Backups
Before changing the system create backups of
Oracle Schema or SQL Server database used for PowerFactory
the Vault directory on the Vault le server
workspaces of all Ofine PowerFactory instances
3.3.4.2 Step 1: Upgrade PowerFactory Online instance(s)
Figure 3.3.17: Upgrade PowerFactory Online instance(s)
Run the PowerFactory installer and replace the existing version with the new version.
3.3.4.3 Step 2: Migrate Online Database
With the upgraded PowerFactory installation its possible to upgrade the database on the Database
server (see gure 3.3.18).
Figure 3.3.18: Migrate Database
Start an upgraded online PowerFactory installation
Conrm when asked for database migration.
3.3.4.4 Step 3: Upgrade Ofine PowerFactory instances, migrate Ofine Database
Figure 3.3.19: Migrate Ofine Database(s)
Run the PowerFactory installer and replace the existing version with the new version.
Start PowerFactory . The local ofine database is migrated automatically.
3.3.4.5 Step 4: Upgrade Ofine Proxy Service
Figure 3.3.20: Upgrade the Ofine Proxy Service
Make a Backup of all conguration les: console.exe.config, offline.exe.config, and offline.ini
Stop the service
Uninstall the service using the Add or remove programs tool
Install the new service
Restore the conguration les
Restart the service
CHAPTER 4. UPGRADE AND MIGRATION
Chapter 4
Upgrade and Migration
This chapter addresses typical scenarios where an existing PowerFactory installation is modied.
License Upgrade: an existing license is upgraded (see section 4.1 on page 73)
Apply a PowerFactory service pack e.g. PowerFactory15.1 Service Pack 2 (see section 4.2 on
page 74)
Upgrade to a newer PowerFactory version e.g. from 14.1 to 15.1 (see section 4.3 on page 76).
4.1 License Upgrade
An existing license is upgraded.
4.1.1 Upgrade Softkey License (Demo or Test Licenses)
DIgSILENTs sales team will prepare a new Activation Key for the upgraded license. First youve to
send an Activation Request to DIgSILENT.
Select the License page (see gure 4.1.1).
CHAPTER 4. UPGRADE AND MIGRATION 4.2. INSTALL A POWERFACTORY SERVICE PACK
Figure 4.1.1: License Settings (Demo)
Press Create Activation Request, which opens a dialog with an Activation Request text.
Send Activation Request text to DIgSILENTs sales team.
When you received an Activation Key text from DIgSILENTPress Enter Activation Key and
insert the key.
4.1.2 Upgrade Hardlock License
Run the digactivate.exe tool as described in section 2.4.1.4 on page 23.
4.2 Install a PowerFactoryService Pack
DIgSILENTprovides for each PowerFactory version e.g. 15.1 a series of Service Packs e.g.
PowerFactory15.1 Service Pack 1 (15.1.1)
A Service Pack usually contains bug xes but no new features. A Service Pack is always cumulative
i.e. Service Pack 4 contains all bug xes Service Pack 3 and earlier Service Packs. Its suggested to
apply the most recent Service Pack.
A PowerFactoryService Pack is technically a normal PowerFactory installer which is delivered as
a Installer (e.g. PF-15.1.3 x64.exe or on a CD-ROM. An existing PowerFactory installation can be
easily upgraded (or patched) by a Service Pack.
Ensure that no user runs PowerFactory (especially on an Application Server)
4.2. INSTALL A POWERFACTORY SERVICE PACK CHAPTER 4. UPGRADE AND MIGRATION
According to your PowerFactory version press PowerFactory Demo, PowerFactory Workspace,
or PowerFactory Server.
Follow the instruction.
Eventually PowerFactorySetup suggests to upgrade the existing PowerFactory installation (see g-
ure 4.2.2).
Figure 4.2.2: PowerFactory Setup: Upgrade
Select Upgrade most recent installation package
Press Next
CHAPTER 4. UPGRADE AND MIGRATION 4.3. UPGRADE POWERFACTORY VERSION
At the rst start PowerFactory asks to update the database (see gure 4.2.3).
Figure 4.2.3: Database Update
Press Yes.
If youre using a multi-user database you will be asked for the Administrator password. The database
update will take some minutes. Please dont interrupt the update process.
In a multi-user database environment where PowerFactory is installed on several workstations, all ac-
cessing the same multi-user database as shown in gure 3.1.2 on page 36, PowerFactory on all work-
stations has to be upgraded. A not-yet-upgraded PowerFactory can still access the updated multi-user
database but warning message shown (see gure 4.2.4).
Figure 4.2.4: Database Update
4.3 Upgrade PowerFactoryVersion
This section describes the upgrade of an existing PowerFactory installation to a newer version e.g. 15.0
15.1 or 14.1 15.1. The upgrade process can be quite complex depending on the environment:
1. (PowerFactoryServer only) Upgrade DIgSILENT License Server on the server computer (see
section 4.3.1 on page 77).
2. (PowerFactoryWorkstation only) Unplug all hardlocks.
3. Install the new PowerFactory version into a new installation directory. Follow the instructions in
chapter 2 on page 5.
4. (PowerFactoryWorkstation only) Re-insert hardlock.
4.3. UPGRADE POWERFACTORY VERSION CHAPTER 4. UPGRADE AND MIGRATION
5. Congure the new PowerFactory installation: start PowerFactory in Conguration Mode (see
section 5.2 on page 86) and insert the settings from the former installation.
Since version 15.1 the conguration is stored in the PowerFactory.ini le in the installation
directory. Its possible to copy this le into the new installation directory. Youll probably need
Windows Administrator rights for this.
6. Usually you want to continue using your existing PowerFactory database. For database import
and migration see section 4.4 on page 78.
7. (Optional) Uninstall the former PowerFactory installation (see section 2.6 on page 33).
Upgrading an environment with Ofine Mode is covered by section 3.3.4 on page 71.
4.3.1 License Server Upgrade
A License Server can not be upgraded directly. Instead the former License Server has to be stopped
and un-installed completely, before the new License Server version can be installed.
Note: If youre using the Floating License module, youll have to do addtional actions (see section 4.3.1.1
on page 77).
Stop and uninstall the License Server service:
In the installation directory of the license server start diglsvc32.exe
Stop and Uninstall the service.
Deinstall License Server from the computer (see section 2.6 on page 33).
The Uninstaller doesnt remove the les that were created during runtime. Delete the installation
folder manually.
Now the new License Server can be installed as described in section 2.4.1 on page 18. The nal
activation with digactivate.exe is not necessary and can be omitted.
4.3.1.1 Upgrade with Floating License Module
If the License Server hardlock is congured with the Floating License module, the le getlicense.bin
must copied from the former License Server installation directory into the new License Server installa-
tion directory. The oating license parity is synchronized with the le getlicense.bin in the installation
directory. If synchronizing fails the license server stops working properly and must be activated manu-
ally. In this case DIgSILENTmust be contacted.
make a backup copy of getlicense.bin before you stop and uninstall the License Server
uninstall former License Server ; install new License Server software dont run it
copy getlicense.bin into the new License Server installation directory
proceed with the normal License Server installation
If the License Server using the Floating License hardlock is expired because of some reasons please
contact DIgSILENTsupport https://support.digsilent.de to provide an activation le. This acti-
vation le has to used via the menu entry Menu Upgrade License.... The License Server has to be
restarted afterwards.
CHAPTER 4. UPGRADE AND MIGRATION 4.4. DATA MIGRATION
4.4 Data Migration
4.4.1 Local Database
4.4.1.1 Migration from 15.1 or higher
Since version PowerFactory 15.1 workspaces (including the local database) can be easily exported
and imported.
Start the former PowerFactory and export the workspace to a
*
.zip le (section 2.5.1 on page 31)
Start the new PowerFactory and import the
*
.zip le.
4.4.1.2 Migration from 15.0/14.X
Since version 15.1 PowerFactory allows to import 15.0/14.X workspaces automatically.
Start the new PowerFactory
Open the workspace import with Tools Workspace Import Workspace from 14.x or 15.0 (see
gure 4.4.1).
Figure 4.4.1: Import 15.0 Workspace (1)
Select a valid 15.0/14.x working directory in the Browse For Folder dialogue e.g. C:\DIgSILENT\pf150
and press OK (see gure 4.4.2).
4.4. DATA MIGRATION CHAPTER 4. UPGRADE AND MIGRATION
Figure 4.4.2: Import 15.0 Workspace (2)
The 15.0/14.X workspace les are copied into the new workspace and PowerFactory needs a restart
which migrates the database to the new format.
4.4.1.3 Migration from 13.X
Data has to be transferred manually as
*
.dz les.
Start PowerFactory 13.X as Administrator user (default password is Administrator).
Export all PowerFactory users except Administrator and Demo to
*
.dz les.
Start the new PowerFactory as Administrator user (default password is Administrator).
Import the
*
.dz les.
4.4.2 Multi-User Database
4.4.2.1 Migration from 14.0 or higher
Since version 14.0 PowerFactory can access and use multi-user database from former versions. The
database is migrated automatically when the new PowerFactory version is started. The PowerFactory
Administrator password is required.
Note: A multi-user database is always migrated in-place. After migration the former PowerFactory
version wont be able to use the database anymore. Ensure that the former version is disabled or
completely removed.
The migration resets all changes in these top-level objects:
System
Library
Demo (version 14.X only)
Before you migrate, please make sure that these folders dont contain any data you need afterwards.
Inform all PowerFactory users about the migration.
(Optional) Disable the former PowerFactory version (e.g. on Application Server).
Ensure that no PowerFactory user is logged on.
Create a database backup.
The new PowerFactory installation must be congured to use the same database connection
parameters.
Start the new PowerFactory version. A warning dialogue is shown (see gure 4.4.3).
Figure 4.4.3: DB Migration Dialogue
Press Yes to start the migration.
Before the migration is started youre asked for the PowerFactory Administrator password.
Oracle only: PowerFactory provides the Selective Migration that combines migration with deletion of
old projects (see section 4.4.2.3 on page 81). Therefore PowerFactory shows a Database Migration
Settings dialogue (see gure 4.4.4).
Figure 4.4.4: Database Migration Settings Dialogue
Press OK without enabling Selective migration, unless you really want to run a Selective
Migration, and you know about its concepts an consequences, and you have prepared your Oracle
server accordingly.
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 several hours. Please dont interrupt the
migration process. When the migration is completed a success dialogue will appear (see gure 4.4.5).
Figure 4.4.5: Successful Database Migration
4.4.2.2 Migration from 13.X
Each PowerFactory version uses its own database format. Therefore the same database cant be
shared between different PowerFactory builds. If you want to use a new PowerFactory build you have
to migrate the database.
The same applies if you want change the database server (e.g. you move the Oracle server from a
Windows 2003 server to a HP-UX workstation) or the whole database system (e.g. Oracle is replaced
by SQL Server).
Migration consists of two steps: First the former database must be exported to DZ les using the former
PowerFactory version. Then these les can be imported with the new PowerFactory version into the
new database.
To export a complete database:
Terminate all PowerFactory sessions.
Start the former (original) version on one machine, log on as Administrator (default password
Administrator). Export each user except Administrator and Demo to a separate DZ le.
Before you can import the les you have to create a new database on the database server. The
database system-specic sections describe how to do this.
Install the new PowerFactory version on one client machine.
Log on as Administrator using the new database in the database settings on the Database page.
This will create the database of the new version from scratch.
Then the DZ les exported should be imported. These les can be imported in any sequence.
4.4.2.3 Selective Migration
Introduction This section describes a method of migrating data to a new version of PowerFactory ,
selective migration, in which only recently active projects are migrated. In effect, old unused projects are
deleted rather than migrated. When there are a lot of old projects, this process is much more efcient
than the alternative of deleting the data and then migrating.
Note: Selective Migration is available for Oracle databases only.
Project Retention Criteria Only PowerFactory projects that meet the selection criteria are migrated.
Other projects are not migrated (and are thus effectively deleted).
The selection criteria for the migration depend on when the project was last touched in the Pow-
erFactory database. Actions that touch the project include purging, editing the description, updating
the storage statistics as well as project activation. The project retention period for the migration can be
specied at the begin of the migration. This numeric setting species that only projects touched recently
within this number of days are retained by the migration.
Base projects are always retained if there are existing derived projects.
Special projects such as user settings and template projects in the PowerFactory System or
Conguration folders are always retained.
The project retention period is calculated from the moment (near the migration start) that the criterion
is applied. For example if you chose a Retention setting of 2 (days) and started the migration at 6 p.m.
on Friday, then all projects that had been touched since 6 p.m. Wednesday would be retained (and their
base projects).
Preparing for a Selective Migration If you want to keep an old project that has not been used for
a while, then a quick way of marking it is to edit the project description. This is much quicker than
activating the project as a way of ensuring it meets the migration criteria.
Note: PowerFactory Users should not try to help out by deleting projects in the days leading up to a
migration, since deleting a project places it in the recycle bin - this touches the project and leads
to it being migrated. It would still be in a recycle bin after the migration though, so just processing
time is wasted.
Pre-requisites for the Migration Please also see the details for standard Migration, as these also
apply (section 4.4.2.1).
Database backed up;
Old projects archived (if desired);
Extra disk space allocated;
New version of PowerFactory installed;
Users logged off.
Executing a Selective Migration The migration is triggered in the same way as a normal migration:
by logging into to the PowerFactory database using a new version of PowerFactory . A Database
Migration Settings dialogue will be shown if Selective Migration is possible (see 4.4.6).
Figure 4.4.6: Conguring selective migration on the log-on dialogue
Enable Selective migration
Dene a Retention period (in days). Only projects that have been created or activated or
touched within this number of days will be migrated.
Start the migration with OK
When the migration is running, you can check the Administrator.log le to ensure that selective
migration is congured; messages like the following will appear within 15 minutes of the migration
starting (prior to this the database scheme is altered):
2012-04-17 15:39:25 [INFO]
persistence.migration.OracleDb - Selective migration processing...
2012-04-17 15:39:25 [INFO]
persistence.migration.OracleDb - Project retention setting is 60 days
Backup Requirements PowerFactory migration already requires you to backup your database be-
fore migration. However the selective migration also requires that an Oracle backup is taken after
migration. The reason for this is that the new OBJECT and REFERENCE tables are inserted to in
NOLOGGING mode (to boost performance); this greatly reduces the Oracle redo activity. However
redo is an integral part of Oracles backup and recovery functionality, and so the database administra-
tors must be made aware of what is happening during the migration process and take action accordingly.
If desired the no logging aspect can be overridden by conguring the database to be in forced logging
mode.
Considering the large change to the nature of the PowerFactory database (e.g. the data space could
reduce from say 500GB to 50GB) the database administrators should check over the backup strategy.
Disk Space Requirements Since the data is selectively copied, additional database space is re-
quired during the migration. The extra space can be estimated simply as the expected size of the new
database. For example, if the database is expected to be 60GB at the end of selective migration, then
an extra 60GB is required on top of the existing space. This ought to be generous, since the selective
migration only adds indexes to the object and reference tables after the original tables are dropped).
The expected size of the new database depends on the project selection criterion (e.g. 60 days).
Although estimations can be made, this size can be discovered via testing.
Points of note for Database Administrators (Oracle)
1. Enable extra Oracle space.
2. Ensure full backups are taken both before and after migration.
3. Oracle redo logs should be a minimum of 100MB each (preferably larger).
4. The quantity of redo generated by the migration is mainly dependent on the nal quantity of data
left after the migration. An example test migration for an end result 29GB migrated database
generated 56GB redo.
5. If database is left in archive log mode for the duration of the migration, please check that there is
sufcient space for the archive logs (according to the expected quantity of redo).
6. Selective migration recreates the large OBJECT and REFERENCE tables and indexes with the
default Oracle STORAGE settings inherited from the tablespace, thus it is possible that the result-
ing tables do not have the same storage characteristics as before.
7. There should be a lot less Oracle space used at the end of migration compared to before. However
the Oracle datales are not shrunk by the process, and so total disk usage will not reduce until the
datales are shrunk by the database administrators.
CHAPTER 5. REFERENCE
Chapter 5
Reference
5.1 PowerFactoryAdministrator
Some functions (e.g. user management or changing the conguration in the PowerFactory database)
require to start PowerFactory as Administrator user (Administrator Mode).
A separate short cut starts PowerFactory in Administrator Mode.
Open Windows Start menu and run Start All Programs DIgSILENT Software PowerFactory
(Administrator) (see gure 5.1.1).
Alternatively its possible re-start PowerFactory and log as Administrator via the menu Tools Switch
User... (see gure 5.1.2).
CHAPTER 5. REFERENCE 5.2. POWERFACTORY CONFIGURATION
Figure 5.1.2: Switch User Function
Usually the PowerFactory Administrator user has a password. Therefore youre asked to insert a pass-
word (see gure 5.1.3).
Figure 5.1.3: Log on Dialogue
Insert the password (The default Administrator password is Administrator).
Press OK.
5.2 PowerFactoryConguration
A separate short cut starts PowerFactory in Conguration Mode.
Open Windows Start menu and run Start All Programs DIgSILENT Software PowerFactory
(Conguration) (see gure 5.2.1).
5.2. POWERFACTORY CONFIGURATION CHAPTER 5. REFERENCE
Alternatively you can review and change the conguration from within a running PowerFactory via the
menu Tools Congure PowerFactory... (see gure 5.2.2).
Figure 5.2.2: Open Conguration Function
The Conguration dialogue contains several pages which are explained in the next sub sections.
and press Yes.
5.2.1 General Settings
See gure 5.2.3.
Figure 5.2.3: General Settings
Language Species the application language.
5.2.2 Database Settings
Depending on the database type the there are different settings.
5.2.2.1 Local Database
See gure 5.2.4.
Figure 5.2.4: Database Settings (Local Database)
5.2.2.2 Oracle
The Database page allows to set the Oracle connection settings (see gure 5.2.5).
Figure 5.2.5: Database Settings (Oracle)
Database driver select Oracle (Client Version 11.2)
Database service this eld describes the connection. It must be conform to the format
//host[:port][/servicename]
With the values used above (host=oracleserver, port=1521 (default port), and SID=PFSERVER)
the connection name is
//oracleserver/PFSERVER
If we had used a non-default port=8888 the connection name would be
//oracleserver:8888/PFSERVER
If youve installed a (normal) Oracle Client and made an entry (e.g. PFS) in the TNSNAMES.ORA
conguration le, you can use the TNS name instead. Then the Database service is just
PFS
Username and Password During the Oracle server setup an Oracle schema PF with the password
aPasswordForPf has been created. Enter these values in the Username and Password elds.
Vault Directory (Optional) Vault directory as described in section 3.1.4 on page 47.
Note: Usually the Oracle Client installation directory path must be congured on Advanced page.
Otherwise PowerFactory cant nd the required Oracle Client Runtime les.
5.2.2.3 SQL Server
The Database page allows to set the SQL Server connection settings (see gure 5.2.6).
Figure 5.2.6: Database Settings (SQL Server)
Database driver select Microsoft SQL Server
Database service The Database service uses the format
host\instancename
e.g.
MYSERVER\SQLEXPRESS
Note that the 2005 Edition uses something called default instance, which must be accessed by
omitting the instance name in the Database service: MYSERVER.
Username and Password The SQL Server name and password.
Database name The database name.
Vault Directory (Optional) Vault directory as described in section 3.1.4 on page 47.
5.2.2.4 Ofine Proxy Server
PowerFactory s Ofine Mode (section 3.3 on page 58) requires to congure a server.
Figure 5.2.7: Database Settings (Ofine Mode)
Database driver select Ofine Proxy Server
Database service Specify server host name and port, separated by a colon e.g.
OFFLINEPROXYSERVER:9401
5.2.3 License Settings
Depending on the license type there are different settings
5.2.3.1 Activation or Demo Requeset
Theres nothing to specify for this license option (see gure 5.2.8).
Figure 5.2.8: License Settings (Demo)
The button Create Activation Request creates an Activation Request text required for activate
the Demo version. The Activation Key text can be imported with Enter Activation Key (see sec-
tion 2.2.2 on page 9).
5.2.3.2 Workstation
Theres nothing to specify for this license option (see gure 5.2.9).
Figure 5.2.9: License Settings (Workstation)
5.2.3.3 Server
See gure 5.2.10.
Figure 5.2.10: License Settings (Server)
License Select PowerFactory Server
Server Name Insert the License Server computer address (e.g. 192.168.111.222) or computer name
(e.g. LICSERVER or LICENSE.COMPANY.COM).
The Advanced page allows to set advanced settings (see gure 5.2.11) which must match the License
Server conguration (see section 5.4.1 on page 96).
Figure 5.2.11: Advanced License Settings (Server)
RPC Protocol Insert the RPC Protocol name specier
RPC Endpoint Insert a valid RPC Endpoint specier
In Ofine Mode there are additional parameters for Ofine Licenses (see section 5.2.12).
Figure 5.2.12: Advanced License Settings (Server) in Ofine Mode
Ofine licensing Choose Create offline license if the license should be locked for some days.
Choose Create online server license only, if there is a permanent connection to the Li-
cense Server .
Ofine License Validity Period Only if Create offline license is selected. Number of days the
license should locked on the License Server .
5.2.4 Workspace Settings
The Workspace page allows to change the Workspace directories (see 5.2.13).
Figure 5.2.13: Workspace Settings
Use Default Workspace Directory Uncheck this option to specify a own Workspace directory.
Workspace Directory Path of the current Workspace directory.
Open Workspace Directory Opens Windows Explorer showing the Workspace directory.
Use Default Backup Directory Uncheck this option to specify a own Workspace Backup directory.
This directory is used when workspaces are exported (section 2.5.1 on page 31).
Backup Directory Path of the current Workspace Backup directory.
Open Backup Directory Opens Windows Explorer showing the Workspace Backup directory.
Note: Be careful when changing the Workspace Directory. The new workspace directory is not
initialized with the current workspace directory. First export the workspace to a
*
.zip le and
re-import it afterwards as described in section 2.5.1 on page 31.
5.2.5 Advanced Settings
See gure 5.2.14.
5.3. POWERFACTORY COMMAND LINE PARAMETERS CHAPTER 5. REFERENCE
Additional directories in PATH A set of directories (each directory on a separate line) where Power-
Factory should look for
*
.dll les e.g. the Oracle Client Runtime.
Startup Commands List of commands that are executed when PowerFactory is started.
The Advanced sub page allows to specify some really advanced settings (see gure 5.2.15).
Debug Runs PowerFactory in Debug mode.
Master in Distributed Simulation If checked: this PowerFactory instance acts as Master, otherwise
as slave.
Runtime Engine Mode If checked: PowerFactory runs in non-interactive mode i.e. there no dialogues
are shown which wait for user input.
Enable Multi-Threading Allows to run a simulation calculation with multiple threads (experimental)
Authentation Server Species an Authentication Server.
5.3 PowerFactoryCommand Line Parameters
/cong Show and edit PowerFactory conguration.
/lang:<LANGUAGE> Ignore the Language setting in the conguration, and run PowerFactory with a
different language. Valid are /lang:en (English), /lang:de (German), or /lang:fr (French).
/housekeeping Execute a database Housekeeping in the database (section 3.1.6.2 on page 53).
/username:<USERNAME> /password:<PASSWORD> Species PowerFactory user and password
to use. Example: Start as Administrator user with default password
PowerFactory.exe /username:Administrator /password:Administrator
CHAPTER 5. REFERENCE 5.4. LICENSE SERVERREFERENCE
5.4 License Server Reference
5.4.1 Advanced License Server Conguration
The License Server has several options, which can be modied by editing the le diglise.ini in the
installation directory:
Protocol based communication: PowerFactory and the License Server communicate via RPC
protocol. The following lines show the standard settings for the communication parameters:
RPC-Protocol=ncacn_ip_tcp
RPC-Endpoint=4000
If you change these values, you will also have to adapt the License of the PowerFactory congu-
ration accordingly (see gure 5.4.1).
Figure 5.4.1: License Server Conguration
Working directory (default: subdirectory Run) request les are read from, and user license les
are written to this directory.
The conguration changes take effect when the License Server service is restarted.
5.4.2 Functionality
This section describes in short the interaction between PowerFactory and License Server .
DIgSILENT PowerFactory communicates with DIgSILENT License Server via RPC protocol by using
binary les written to the license server working directory (Run). For each PowerFactory client a
*
.req
request le will be created in the Run sub directory in the License Server installation directory.The
License Server responds by creating a user license le
*
.use in the Run sub directory, then the request
le is deleted.
The client gets the license information via RPC protocol. The corresponding
*
.use license le exists
in the Run directory as long as the license is valid. If the number of users is UNLIMITED, the user
license les
*
.use will be deleted immediately after the client has read the le. If the number of users is
LIMITED, PowerFactory will periodically check the existence of the
*
.use le, and will modify the le to
5.4. LICENSE SERVERREFERENCE CHAPTER 5. REFERENCE
reect the time and date of its check. When the user terminates PowerFactory the
*
.use le is deleted
by the client.
If, for some reason, the connection between PowerFactory and License Server is broken, or if Pow-
erFactory terminates abnormally, the
*
.use le is not deleted but remains in the Run directory of the
License Server . It is automatically deleted periodically and/or during the next software startup.
The number of
*
.use les 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 les 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 les i.e. all occupied licenses are
freed.
Note: A PowerFactory session will be closed if the corresponding license le has been deleted, or if
the connection to the License Server is lost during the periodical checks. PowerFactory shows
an appropriate message when the connection to the License Server is lost.
5.4.3 User Authentication
Since Version 15.0 the License Server allows to restrict license requests to a list of named PowerFac-
tory users. For example there are PowerFactory users as shown in gure 5.4.2:
Figure 5.4.2: List of PowerFactory users
There are eight users (besides the Administrator user) in total, but e.g. only the three users User 03
(user id 15), User 04 (user id 16), and User 05 (user id 5) should be able to request licenses from this
License Server . Then the users have to be specied in a text le AuthenticatedUsers.txt in the
Run sub-directory, each user in a separate line in the format
<PF user name> ; <PF user id> ; <license mode>
where license mode is
CHAPTER 5. REFERENCE 5.4. LICENSE SERVERREFERENCE
0: User can request a license
1: User even can request a oating license
The AuthenticatedUsers.txt le should have a content as shown below:
User_03;15;0
User_04;16;0
User_05;5;1
User 05 is able to request a oating license.

Installation Manual 15.1 en

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Installation Manual 15.1 en

Transféré par

Droits d'auteur :

Formats disponibles

D

Vous aimerez peut-être aussi