installation manual 15.1 en

7/22/2019 Installation Manual 15.1 En

1/104

DIG

SILENT

PowerFactory

I N T E G R A T E D P O W E R S Y S T E M A N A L Y S I S S O F T W A R E

DIgSILENT

PowerFactory 15.1

Installation Manual


2/104

DIgSILENT GmbH

Heinrich-Hertz-Strae 9

72810 Gomaringen / Germany

Tel.: +49 (0) 7072-9168-0

Fax: +49 (0) 7072-9168-88

[email protected]

Please visit our homepage at:

http://www.digsilent.de

Copyright 2013 DIgSILENT GmbHAll rights reserved. No part of this

publication may be reproduced or

distributed in any form without permission

of DIgSILENT GmbH.

30. October 2013
mailto:[email protected]://www.digsilent.de/http://www.digsilent.de/mailto:[email protected]


3/104

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 PowerFactoryDemo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2.2.1 Install PowerFactory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2.2.2 Demo License Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2.3 PowerFactoryWorkstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

2.3.1 PowerFactoryInstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

2.3.2 Hardlock Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

2.4 PowerFactoryServer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

2.4.1 Install and configureLicense Server . . . . . . . . . . . . . . . . . . . . . . . . . 18

2.4.2 Install and configure PowerFactory . . . . . . . . . . . . . . . . . . . . . . . . . . 25

2.5 Workspace and Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

2.5.1 Export and Import Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

2.5.2 Workspace Directory Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

2.6 Uninstall PowerFactoryandLicense Server . . . . . . . . . . . . . . . . . . . . . . . . . 33

3 Advanced Installation 35

3.1 Multi-User Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

DIgSILENTPowerFactory 15.1, Installation Manual i


4/104

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 Ser ver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

3.2.1 Workspace directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

3.2.2 PowerFactoryConfiguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

3.3 Offline Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

3.3.1 PowerFactoryin Normal Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

3.3.2 Offline Proxy Ser vice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

3.3.3 PowerFactoryin Offline Mode Configuration . . . . . . . . . . . . . . . . . . . . . 68

3.3.4 PowerFactoryUpgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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 PowerFactoryService Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

4.3 Upgrade PowerFactoryVersion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

4.3.1 License ServerUpgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

4.4 Data Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

4.4.1 Local Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

4.4.2 Multi-User Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

5 Reference 85

5.1 PowerFactoryAdministrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

5.2 PowerFactoryConfiguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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 DIgSILENTPowerFactory15.1, Installation Manual


5/104

CONTENTS

5.2.5 Advanced Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

5.3 PowerFactoryCommand Line Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 95

5.4 License ServerReference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

5.4.1 AdvancedLicense ServerConfiguration . . . . . . . . . . . . . . . . . . . . . . . 96

5.4.2 Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

5.4.3 User Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

DIgSILENTPowerFactory 15.1, Installation Manual iii


6/104

CONTENTS

iv DIgSILENTPowerFactory15.1, Installation Manual


7/104

CHAPTER 1. INTRODUCTION

Chapter 1

Introduction

1.1 Typographic Conventions

Typographical conventions used in this document:

Products of DIgSILENTGmbH are printed inbold italic.

Third party products are printed inbold.

Values given as example or ones the user can chose according to his needs are written initalic.

File names, directories, listings and values the user is asked to enter are written infixed widthfont.

Button and window captions or menu entries the user is asked to click or select are written inboldfixed width font.

Menus and sub menu structures are denoted by an arrow in front of the first element and allfollowing sub entries e.g. Menu Sub Menu Sub Sub Menu.

Internet addresses are written inhttp://underlined.fixed.width/font.

1.2 Overview

Depending on the installation type, a PowerFactorysystem can have several components which haveto be installed and configured separately.

chapter2on page5covers the basic installation optionsDemo Version,Workstation Version, andServer Version

More advanced installation options e.g. multi-user database, installation on an application server,and the Offline mode installation covers chapter 3on page35.

1.3 Hardware and Software Requirement

DIgSILENT PowerFactoryis a standard Windows desktop application. Both a 32-bit and a 64-bit ver-sion are available. For PowerFactory15.1 run efficiently should, as a minimum, be equipped with:

DIgSILENTPowerFactory 15.1, Installation Manual 1


8/104

CHAPTER 1. INTRODUCTION 1.4. CHANGE HISTORY

Operating system: Windows XP, Windows Vista (x86/x64), Windows 7 (x86/x64). Windows Server2003, 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 DIgSILENTLicense Serverare described in section2.4.1.1on page18.

Some parts of the PowerFactorydocumentation are available only in PDF format. In order to readthese 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 PowerFactoryver-sions.

1.4.1 Changes in 15.1

ThePowerFactoryinstallation is now implemented according to official Microsoft Windowsguidelineswhich brings many essential changes for users of former PowerFactoryversions.

The default Installation directory is now

C:\Program Files\DIgSILENT\PowerFactory 15.1

instead of C:\DIgSILENT\pf151.

During normal operation PowerFactorydoes not write into the installation directory. The onlyaction that requires write access is changing the PowerFactoryconfiguration (which is now storedin a readablePowerFactory.inifile). In such rare cases Windows Administrator credential mustbe provided in anUser Account Controldialogue (see figure2.1.1on page6).

The configuration is now stored in a readable and editable text file PowerFactory.ini(instead ofthe binary set.dz).

PowerFactorydoes not write to the installation directory. So any user data (e.g. the database ortemporary files) have to be somewhere else. As suggested by MicrosoftPowerFactorystores itsdata now in aWorkspacedirectory inside theWindowsuser profile e.g. in

C:\Users\UserName\AppData\Local\DIgSILENT\PowerFactory 15.1

The workspace concept including workspace backup and restore and workspace migration iscovered in section2.5on page31.

The PowerFactoryexecutable is now PowerFactory.exe instead of digpf.exe or digkernel.exe

The installation on Application Server is much simpler now (section3.2on page54).

ThePowerFactory Demoactivation process was simplified (see section2.2on page7).

This document has been thoroughly revised for 15.1.

2 DIgSILENTPowerFactory15.1, Installation Manual


9/104

1.4. CHANGE HISTORY CHAPTER 1. INTRODUCTION

1.4.2 Changes in 15.0

New features:

Offline Mode(see section3.3on page58).

Housekeeping in multi-user databases (see section3.1.6.2on page53).

Vaultdirectory in multi-user scenarios (see section 3.1.4on page47).



10/104

CHAPTER 1. INTRODUCTION 1.4. CHANGE HISTORY



11/104

CHAPTER 2. BASIC INSTALLATION

Chapter 2

Basic Installation

This chapter describes the basic PowerFactoryinstallation types: Demo Version (see section 2.2),

Workstation Version(see section2.3on page12), andServer Version(see section2.4on page18).

More advanced installation options (e.g. Multi-User Database, installation on Application Server, andOffline Mode) are discussed in chapter3on page35.

Note: Installing PowerFactoryrequires Windows Administration rights. On Windows XP and Win-dows Server 2003please start the installer as Administrator user. Otherwise the installation willfail. On newer Windows versionsWindowsasks for Administrator credentials when needed sec-tion2.1.1on page6.

2.1 Installer

DIgSILENT PowerFactoryis an application for standard Windows operation systems. Both a 32 bitand a 64bit version are available. The 32-bit version is shipped via CD. If the 64 bit version is required,please download the installation file from our Customer Portal https://support.digsilent.deon theDIgSILENTwebsite:

32-bit version: PF-15.1.X x86.exe

64-bit version: PF-15.1.X x64.exe

Installation from CD Insert thePowerFactory 15.1CD into your CD or DVD drive. This will launch theDIgSILENTSoftware PreInstallerwhich guides you the installation options. If the PreInstaller isnot started automatically, run PreInstall.exemanually.

Installation with installer Start the setup PF-15.1.X x64.exe(32 bit) or PF-15.1.X x86.exe(64 bit)

WindowsUser Account Controldialogue shows a list of Administrator users that are allowed to performadministrative actions (see figure2.1.1)



12/104

CHAPTER 2. BASIC INSTALLATION 2.1. INSTALLER

Figure 2.1.1: User Account ControlDialogue

Select a user and insert the appropriate password

PressYes

TheDIgSILENTSoftware PreInstaller is shown (see figure4.2.1).

Figure 2.1.2: Software PreInstallerDialogue



13/104

2.2. POWERFACTORYDEMO CHAPTER 2. BASIC INSTALLATION

ThePreInstallerprovides several install options which are described in the next sections:

PowerFactoryDemo (see section2.2)

PowerFactoryWorkstation (see section2.3)

PowerFactoryServer (see section2.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 networksand 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 PowerFactorybyletting you build the tutorial net yourself, step by step. The tutorial net contains all the major features of

PowerFactory, and calculations for this network configuration are permitted by the program.

Note: Using the Demo version requires a license activation (see section 2.2.2).

2.2.1 InstallPowerFactory

Start the DIgSILENTSoftware PreInstalleras described in section2.1 on page5. A DIgSILENT Soft-ware PreInstallerdialogue is shown (see figure below).


PressPowerFactory Demo

The PowerFactorySetup Wizard is started (see figure below).



14/104

CHAPTER 2. BASIC INSTALLATION 2.2. POWERFACTORYDEMO

Figure 2.2.2: PowerFactorySetup: Welcome

ClickNextand step through the wizard pages. Use the default settings.

After completion a success message is shown as shown in the figure below.

Figure 2.2.3: PowerFactorySetup: Completion

ClickFinish

The PowerFactoryInstallation Wizard window is closed.

Close theDIgSILENTSoftware PreInstallerdialogue by pressingClose

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.1on theWindows desktop. You can start PowerFactoryby double-clicking this short cut.



15/104


Figure 2.2.4: PowerFactoryStart Short Cut on the Desktop

Besides two short cuts are created in Windows Start menu (Start All Programs DIgSILENT Software).

Figure 2.2.5: PowerFactoryShort Cuts in Start Menu

RunPowerFactory 15.1 (Configuration) for configuring the application (section5.2 on page86). Run Pow-erFactory 15.1 (Administrator)for administrative purposes (section5.1on page85).

2.2.2 Demo License Activation

The software must be activated on your computer before it can be used. The activation involves severalsteps:

1. Start PowerFactorywhich will create anActivation Request textfor your installation.

2. Send an email with theActivation Request textto DIgSILENT

3. DIgSILENTs sales department sends an email with theActivation Key textback to you.

4. Import theActivation Key textinto a PowerFactory

Lets begin: launch PowerFactoryfor the first time.

Double-click the PowerFactorystart short cut on your Windows desktop



16/104

CHAPTER 2. BASIC INSTALLATION 2.2. POWERFACTORYDEMO

ALicense Activation Overviewdialogue is shown (see figure2.2.6).

Figure 2.2.6: License Activation Overviewdialogue

Press Create Activation Request

ALicense Activation Requestdialogue is shown (see figure2.2.7).

Figure 2.2.7: License Activation Requestdialogue

Send theActivation Request text to DIgSILENTalong with some customer information:



17/104


If an default email application (e.g. Microsoft Outlook or Mozilla Thunderbird) is installed onyour computer, just press Open Mail Program and an email to DIgSILENTwill be prepared.Adapt the email text and send it to [email protected]

Otherwise send the email manually to [email protected]. Copy and paste the email subjectand email text from the dialogue.

DIgSILENTs Sales Team will send a response email. Besides other information it will contain an Acti-vation Key textthat 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 theLicense Overview Dialogue(figure2.2.6)pressEnter Activation Key.

AnLicense Activation Keydialogue is shown (see figure2.2.8).

Figure 2.2.8: License Activation Keydialogue

Copy the text (including the BEGIN ACTIVATION KEYline and the END ACTIVATION KEYline) fromthe email and paste it into the text field.

PressApply Activation Key

Restart PowerFactory



18/104

CHAPTER 2. BASIC INSTALLATION 2.3. POWERFACTORYWORKSTATION

Then the application is ready to use (see figure2.2.9).

Figure 2.2.9: PowerFactoryafter successful installation

2.3 PowerFactoryWorkstation

PowerFactoryWorkstationis delivered with a license hardlock(also known as hardware license keyordongle). DIgSILENTprovides USB hardlocks.

Figure 2.3.1: Workstation License

Only one hardlock can be connected to one computer at the same time (see figure 2.3.1). ThePower-FactoryWorkstationinstallation takes two steps:

1. Install PowerFactorysoftware

2. Activate the hardlock

2.3.1 PowerFactoryInstallation

If youre upgrading an existing PowerFactory Workstationinstallation: remove all existing USBhardlocks

Start the DIgSILENTSoftware PreInstalleras described in section2.1 on page5. A DIgSILENT Soft-

ware PreInstallerdialogue is shown (see figure below).



19/104

2.3. POWERFACTORYWORKSTATION 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 Servertool. This tool is required because PowerFactoryis not able access thehardlock hardware directly.

3. Finally, the PowerFactoryapplication itself.

AHardlock Driver Setupis started (see figure below).

Figure 2.3.3: Hardware Driver Setup



20/104


pressNextand follow the instructions of the setup.

After having installed the hardlock driver successfully, the DIgSILENT License ServerSetup wizard isstarted (see figure2.3.4).

Figure 2.3.4: License ServerSetup

PressNextand follow the instructions of the installer. Use the default settings.

A success message confirms that theLicense Serverservice correctly configured (see figure2.3.5).





21/104






ClickFinish



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.1on theWindows desktop. You can start PowerFactoryby double-clicking this short cut.



22/104






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



23/104


An activation is simply downloading an activation file from the DIgSILENTsupport website and saving itto the PowerFactoryand License Serverinstallation folder. DIgSILENTprovides the tool digactivate.exethat is automatically for you. In order to get access to the DIgSILENTsupport website youve to providethe users customer credentials are required. They can be found in the license agreement document.

run the activation tooldigactivate.exein theLicense Serverinstallation directory

C:\Program Files\DIgSILENT\License Server\digactivate.exe

A License Activation Wizarddialogue is shown and will guide you through the activation process (seefigure below).

Figure 2.3.10: License Activation

PressNext

The dialogue provides three options (see figure below).




24/104

CHAPTER 2. BASIC INSTALLATION 2.4. POWERFACTORYSERVER

Activate directly from the Internet Download theactivation fileand save it to the appropriate installa-tion directories.

Download the activation file without installation Download the activation file only. This options isuseful when the computer you installedLicense Serverhas no direct access to the internet.

Activate using a local activation file Save a previous downloaded activation fileinto to the installation

directories. The path to the previously downloaded activation file must be specified.

2.4 PowerFactoryServer

DIgSILENToffers theNetwork Licenseto simplify the handling of hardlocks for companies usingPow-erFactoryon several computers. Network Licenses are shipped with a special hardlock, theNetworkHardlock. This hardlock is plugged to one computer in the computer network e.g. to a server or an-other machine that runs continuously. All PowerFactoryprocesses installed on any workstation in thenetwork is able to access a license from this server (see figure2.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 PowerFactoryin anLicense Serverenvironment requires two steps:

1. Install and configureLicense Serveron the server machine (see section2.4.1).

2. Install and configure PowerFactoryon all workstation machines (see section2.4.2on page25).

TheLicense Serverdoes not need to be installed on a separate server computer. Instead the installa-tion on one of the Workstation computers is also possible. License Serveris started automatically asa service whenWindowsstarts up.

2.4.1 Install and configureLicense 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.



25/104

2.4. POWERFACTORYSERVER 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 willnot work correctly.

Remove all existing hardlocks

If a previous version of DIgSILENT License Serveris already installed remove it completely asdescribed in section4.3.1on page77.



PressPowerFactory Server

TheSoftware PreInstallerdialogue allows now to choose the components to install (see figure2.4.3).



26/104



checkHardlock Device Driver

uncheckPowerFactory

checkNetwork License Server

pressStart Installation...

AHardlock Driver Setupis started (see figure below).

Figure 2.4.4: Hardware Driver Setup

pressNextand follow the instructions of the setup.



27/104


After having installed the hardlock driver successfully, the License ServerSetup wizard is started (seefigure2.4.5).


PressNextand follow the instructions of the installer.

The default installation directory is C:\Program Files\DIgSILENT\License Server(see figure2.4.6).

Figure 2.4.6: License ServerInstallation Directory

Plug network dongle in the server computer.

Verify that the dongle is valid and can be accessed by running License Serveras a normalWindowsdesktop application (and not as Windowsservice).

Run C:\Program Files\DIgSILENT\License Server\diglise.exe

A smallDIgSILENT License Serverapplication window appears (see figure2.4.7).



28/104


Figure 2.4.7: DIgSILENT License ServerApplication

Error messages will be shown in case of any Hardlock or Hardlock driver problems.

Menu Aboutdisplays useful information about the dongle (see figure2.4.8).

Figure 2.4.8: License ServerAbout Window

Close theDIgSILENT License Serverapplication with Menu Exit.

DIgSILENT License Serveris now configured correctly. Now it has to be registered as a service startingautomatically whenWindowsstarts up.

Run the License Server Service Configuration tool diglsvc32.exe in the installation directory(see figure2.4.9).

Figure 2.4.9: License ServerAbout Window



29/104


PressInstall Service

Press Start Service

Verify that the License Serverservice process is really started automatically at the Windowsstartup. Note that it can take up to one minute until the process diglise.exeis up and running.Check for existence of the processes diglise.exe.

Note: After installation of a License Serverwhich is Softkey (instead of Hardlock) protected, the Li-cense Serverhas to be started as a Windows application first. A dialogue box will pop up, pleasefollow the instructions.

Note: A network hardlock cannot be used as a local key for PowerFactory Workstation. It can onlybe accessedPowerFactory Server. However PowerFactoryand theLicense Servermay be in-stalled and run on the same machine, so that a network hardlock may be used on a local machineas long as theLicense Serveris also running.

2.4.1.3 Other Settings

Any firewall between license server and PowerFactoryshould open RPC port 135(TCP) and alsothe preconfigured RPC-Endpoint port 4000(TCP).

AdvancedLicense Serverconfiguration options are covered in the reference chapter (see section5.4on page96).

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 file from the DIgSILENTsupport website and saving itto the PowerFactoryand License Serverinstallation folder. DIgSILENTprovides the tool digactivate.exethat is automatically for you. In order to get access to the DIgSILENTsupport website youve to providethe users customer credentials are required. They can be found in the license agreement document.

run the activation tooldigactivate.exein theLicense Serverinstallation directory

C:\Program Files\DIgSILENT\License Server\digactivate.exe



30/104


A License Activation Wizarddialogue is shown and will guide you through the activation process (seefigure below).


PressNext

The dialogue provides three options (see figure below).


Activate directly from the Internet Download theactivation fileand save it to the appropriate installa-tion directories.

Download the activation file without installation Download the activation file only. This options isuseful when the computer you installedLicense Serverhas no direct access to the internet.

Activate using a local activation file Save a previous downloaded activation fileinto to the installationdirectories. The path to the previously downloaded activation file must be specified.



31/104


2.4.2 Install and configurePowerFactory

On each workstation computer PowerFactorymust be installed and configured to connect to the Li-cense Server.

2.4.2.1 Install PowerFactory



PressPowerFactory Server

TheSoftware PreInstallerdialogue allows now to choose the components to install (see section2.4.13).



32/104



uncheckHardlock Device Driver

checkPowerFactory

uncheckNetwork License Server

pressStart Installation...






33/104




ClickFinish



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.1on theWindows desktop. You can start PowerFactoryby double-clicking this short cut.





34/104




2.4.2.2 Configure PowerFactory

License Servermust be configured in PowerFactory.

Start PowerFactoryinConfiguration Mode:

Open Windows Start menu and run Start All Progams DIgSILENT Software PowerFactory(Configuration)(see figure5.1.1on page85).

APowerFactory Configurationdialogue is shown.

switch to the Licensepage and insert the setting as shown below (see figure2.4.18)

License SelectPowerFactory Server

Server Name Insert the License Servercomputer address (e.g. 192.168.111.222) or computer name(e.g. LICSERVERor LICENSE.COMPANY.COM).



35/104


Figure 2.4.18: License Server Configuration

License Servercan be configured with advanced settings (see section5.4.1on page96). These mustbe also set on the Advancedsub page.

Finally, save the settings to configuration file PowerFactory.ini:

PressOK in thePowerFactory Configurationdialogue

Windows eventually shows an User Access Control dialogue and asks for an Administrator userscredentials in order to save the configuration file into the PowerFactoryinstallation directory (see fig-ure4.2.1on page75). Select an Administrative Windows user from the list, insert the users password,and pressYes.

2.4.2.3 License Management

TheLicense Servers task is to provide license information for each PowerFactoryprocess. This taskincludes the monitoring of the number of concurrent users as well as the monitoring of the number ofconcurrently used functions. The access to the various calculation functions is thus controlled by theLicense Server.

If the license agreement contains different number of functions, e.g. 4 base packages and 2 stabilityfunctions for 4 concurrent users, then it is also possible to configure the users account such that theusers functionality is limited.

The users dialogue box itself determines the functions this user has access to when he is logged on toPowerFactory.

A right mouse click on a certain user in the data manager offers the menu entry Edit. Selecting thisentry opens the users dialogue box, which appears as figure2.4.19shows.



36/104


Figure 2.4.19: PowerFactoryUser Function Settings

The License page includes a list of all PowerFactoryfunctions. Each function can be enabled ordisabled for this user. The standard setting enables the base package only.

Hint: Only the PowerFactoryAdministratoruser has the right to modify these settings. Section sec-tion5.1on page85who start PowerFactoryas Administrator.

If there are not enough licenses already occupied, the user will get an appropriate message whenstarting PowerFactory. TheHelp Aboutdialogue in PowerFactorythen includes a list of all functionsthe user occupies (see figure2.4.20).

Figure 2.4.20: PowerFactoryHelp/AboutDialogue



37/104

2.5. WORKSPACE AND BACKUP CHAPTER 2. BASIC INSTALLATION

2.5 Workspace and Backup

Since version 15.1 PowerFactorystores data in a workspace directory in the Windows user profile.When a user namedFrodoruns 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 files (e.g. results of simulation calculations)

Log files which are very useful when analysing application problems.

Temporary files.

2.5.1 Export and Import Workspace

Its possible to manipulate e.g. backup and copy Workspace directories directly. However PowerFac-toryprovides functionality for saving a workspace (including all files in all subdirectories) as a conve-nient *.zip archive which can be used as data backup. Similarly an exported workspace *.zip filecan be easily be re-imported into the same PowerFactoryinstallation (i.e. restoring a backup) or into acompletely different PowerFactoryinstallation on another computer (data transfer, data migration).

Figure2.5.1shows the Workspace functions in PowerFactorys main menu.

Figure 2.5.1: PowerFactoryWorkspace Functions

Exporting a Workspace is straightforward:

SelectTools Workspace Export Workspace

ASave Asdialogue is shown (see figure2.5.2).



38/104

CHAPTER 2. BASIC INSTALLATION 2.5. WORKSPACE AND BACKUP

Figure 2.5.2: Export Workspace

(Optional) Select another target directory or file name

PressSave

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:

SelectTools Workspace Import Workspace

Specify a *.zipfile containing a valid PowerFactoryworkspace in theOpendialogue and pressOpen.

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 Configuration

Storing the Workspace in the Windows user profile is convenient, but it might not be suitable undersome 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 localdatabase. Though they cant work concurrently at the same time, they might work in turns. Thenthe workspace should be in a directory accessible by all three users.

SeveralWindows users are running PowerFactoryconcurrently on an Application Server. Theinstallation on Application Server is described in section3.2on page54.

Under these circumstances it makes sense to adapt the Workspace directory.



39/104

2.6. UNINSTALLPOWERFACTORYANDLICENSE SERVER CHAPTER 2. BASIC INSTALLATION

If youre already working with PowerFactoryand want to use the existing workspace to the newlocation, export the workspace as described in section2.5.1on page31.




Switch to theWorkspacepage (see figure2.5.3).

UncheckUse Default Workspace Directory

Insert e.g. D:\Data\PowerFactoryas Workspace Directory

Figure 2.5.3: Workspace Configuration




If you have exported the Workspace before: import the workspace now as described in sec-tion2.5.1on page31.

2.6 UninstallPowerFactoryandLicense Server

WindowsProgram and Featuresdialogue (available via Control Panel Programs Programs and Fea-tures) allows to un-install PowerFactoryand/orLicense Serverfrom the computer (see figure2.6.1).



40/104

CHAPTER 2. BASIC INSTALLATION 2.6. UNINSTALLPOWERFACTORYANDLICENSE SERVER

openProgram and Featuresdialogue

find DIgSILENT PowerFactory 15.1or DIgSILENT License Serverin the list

open the context menu by right-click and select Uninstall/Change

anUninstallerwizard is shown. Follow its instructions.

Figure 2.6.1: Program and Featuresdialogue

Note: The un-installer removes the whole PowerFactoryinstallation folder. Ensure that you saved im-portant files somewhere else.

Un-installer doesnt remove the Workspace (see section 2.5on page31)which is usually stored in theWindowsusers profile 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. withWindows Explorer



41/104

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

PowerFactoryServer version (section2.4on page18).

A multi-user databaseallows several PowerFactoryusers to work concurrently and share theirdata (see section3.1).

Several users can work on the sameapplication server (see section3.2on page54).

Offline Modeis based on amulti-user database. It allows to run PowerFactorywithout a perma-nent connection to the server (see section3.3on page58).

3.1 Multi-User Database

Normally PowerFactorystores the user data in a local databaseon the computer where PowerFac-toryis installed. When three PowerFactoryusers working three computers want to exchange databetween their database by exporting data to files from one database and importing the files into theother database (see figure3.1.1).

Figure 3.1.1: Local Databases

In amulti-user databaseall data is stored in one central database server (see figure3.1.2).



42/104

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

PowerFactorysupports two common commercial database systems:

Oracle Database Server(see section3.1.2on page37)

Microsoft SQL Server(see section3.1.3on page43)

3.1.1 Installation Overview

Steps:

1. InstallPowerFactory Server Version(see section2.4on page18). Verify that the application runssmoothly before proceeding with the next actions

2. Install and configureOracle Database Server(see section3.1.2on page37) orMicrosoft SQLServer(see section3.1.3on page43)and configure connection settings in PowerFactory

3. (Optionally) Set up and configure a Vault directory (see section3.1.4on page47)

4. Administrate the PowerFactorydatabase e.g. create PowerFactoryuser accounts and usergroups (see section3.1.5on page49).

5. (Optionally) Import projects, libraries, or other data from other PowerFactoryinstallations



43/104

3.1. MULTI-USER DATABASE CHAPTER 3. ADVANCED INSTALLATION

3.1.2 Oracle

3.1.2.1 Requirements

PowerFactoryuses Oracles OCCI/OCI programming interface to communicate with the server. OCCI/OCI

itself uses a proprietary communication scheme on top of TCP/IP.

PowerFactorysupports Oracleversions as shown below:

Server: 10.2 or higher

Client: 11.2:

PowerFactory32bit (x86) requires the 32bitOracle Client

PowerFactory64bit (x64) requires the 64bitOracle Client

Server Requirements: The Oracle server machine should fulfil 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 themachines where PowerFactoryis 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 Oracledatabase server and client.

Before you set up and configure the client computers in section 3.1.2.3 (Client Installation), the servermust be prepared as explained in section3.1.2.2(Server Installation).

3.1.2.2 Server Installation

Install the Oracle server software on the server computer (ORACLESERVERbeing the server computername used in this section). Please follow the Oracle Serverinstallation instructions.

Let us assume that ORACLESERVER is accessible by the name oracleserver.domain.com in the net-work. In order to use theOracleserver for PowerFactoryyou have to do the steps as follows:

Create a new Oracle database with a database name (SID) of PFSERVER (stands for: Power-FactoryServer) or use an existing one. The character set for the Oracle instance should beWE8MSWIN1252.

An Oracle listener is needed on the server, in order to pass on connection requests fromclients to the database. If you created the database with the Oracle installer, the listeneris configured for you automatically. If you create the database manually, then configure thelistener using theOracle Net Configuration Assistant tool.

(Recommended but not essential) create the database with redo log files sized at 500MB.

PowerFactoryneeds a place to store its data. Oracle stores data in so-called tablespaces. It issuggested to create a new tablespace where PowerFactory(and only PowerFactory) stores itsdata. You might adapt and use the SQL statement below to your purposes:



44/104


CREATE TABLESPACE "POWERFACTORYTABLESPACE"

LOGGING

DATAFILE D:\ORACLE\ORADATA\DIGSI\POWERFACTORYTABLESPACE.ora

SIZE 5000M REUSE

EXTENT MANAGEMENT LOCAL

The statement creates a new tablespace named POWERFACTORYTABLESPACE which is stored in a POWERFACTORYTABLESPAfile in the given directory. The file size is restricted to 5000M i.e. about 5GB.

In order to use the Oracle instance for PowerFactoryone new Oracle schema is required. Createa new schema with the default profile. We suggest the schema name PF.

Define a password for PF. In this example we use aPasswordForPf.

Associate default and temporary tablespaces to schema PF. It is assumed that a temporary ta-blespaceTEMPis available.

Grant the roles CONNECT and RESOURCE and the system privileges UNLIMITED TABLESPACEandALTER SESSIONto 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 theOracle instanceprocess andOracle listener process if they are not already started.

Note: The amount of tablespace space PowerFactoryrequires depends heavily on how PowerFac-toryis used. The space is roughly proportional to the number of objects in PowerFactory. Ob-serve the tablespace fill-state regularly (e.g. once per month) and increase the size limit accord-ingly.

Note: Regarding the recommended sizing of the redo log files when creating the database; this con-figuration of the redo log files is to increase performance. PowerFactorycan generate very large

quantities of redo data in short bursts. This is particularly the case when importing data, copyinglarge projects or deleting large projects. If for other reasons you require smaller redo log files, (forexample to reduce database recovery time), you should increase the number of log file groups asan alternative to increasing the file size.

Note: It is highly recommended to backup theOracleschema on a daily basis. A backup procedure isdescribed in section3.1.2.5on page42

3.1.2.3 Client Installation

TwoOracleclient packages can be used:



45/104


(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 usingPowerFactory; supports TNS names.

Oracle Instant Client: This package contains only the files required for using PowerFactory;doesnt support TNS names.

Both (normal) Oracle Client and Oracle Instant Client are available for 32bit applications and 64bitapplications. PowerFactory64bit requires a 64bit OracleClient; PowerFactory32bit requires a 32bitOracleClient.

Note: The Windows version is not relevant: if you install PowerFactory32bit on Windows 7 64bit, youwill have to installOracle Client32bit.

Install and configure Oracle Instant Client Instant Client is a package of DLL files which can bedownloaded freely from theOraclewebsite. 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 (seefigure3.1.3). PowerFactoryuses these DLL files in order to communicate with the Oracle Databaseserver.

Figure 3.1.3: Database Figure: Oracle Instant Clientinstallation folder

Install and configure (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 figure3.1.4).



46/104


Figure 3.1.4: (Normal)Oracle Clientinstallation folder

(Optionally) Its possible to add an TNS name entry for PFSin the configuration file

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 PowerFactoryconfiguration.

3.1.2.4 PowerFactoryConfiguration




Switch to theDatabasepage

Insert the database connection settings as described below (see figure3.1.5)



47/104


Figure 3.1.5: PowerFactoryConfiguration forOracle Server

Database driver select Oracle (Client Version 11.2)

Database service this field 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=8888the connection name would be

//oracleserver:8888/PFSERVER

If youve installed a (normal) Oracle Client and made an entry (e.g. PFS) in the TNSNAMES.ORAconfiguration file, you can use the TNS name instead. Then theDatabase serviceis just

PFS

Username and Password During the Oracle server setup an Oracle schema PF with the passwordaPasswordForPfhas been created. Enter these values in the Usernameand Passwordfields.

PowerFactoryuses files in the Oracle Client installation folder the communication with the server. Inorder to find them, the installation folders must be configured explicitly:

Switch to theAdvancedpage

Insert the folders as described below (see figure3.1.6)



48/104



Additional directories in PATH Oracle Instant Clientinstalled 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




3.1.2.5 Backup

Create Backup DescribingOracles backup facilities is far beyond the scope of this installation man-

ual. In this section only a simple technique is described. Please consult the Oracledocumentation fordetailed information or other backup strategies. One backup method is the creation of database dumps.The exp.exeand imp.exetools are part of the Oracledistribution. To export all data of the schema PFrun the exp.exetool:

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.dumpis the filename of the dump file.

Note: During the export or import process no PowerFactoryuser should must not be active. Thisbackup strategy is suitable only for e.g. nightly backups.



49/104


Oraclealso supports so-called hot backups where clients can still use the database during the backupprocess. Please consult theOracledocumentation for this backup strategy.

Restore Backup To re-import a database dump, first drop and re-create theOracleschema PF. Thenrun the imp.exetool:

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 samename as the source instance.

3.1.3 Microsoft SQL Server

Microsoft provides several editions of its relational database system SQL Server, depending on Versionused (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 Editionprovides 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 consultthe officialSQL ServerHomepage.

SQL Server operates as a service. Services are applications that run as background processes. Thebehaviour of services differs from that of other applications. For example, while most applicationsare executed only when a user launches the application from the Start menu, services such as SQLServer are generally started and stopped by the operating system environment. A service runs in thebackground and waits for processing requests. In the case of SQL Server, these requests are fordatabase operations.

All actions described in this section are to be done on the server computer. Throughout this sectionSERVERNAME is used as computer name.

3.1.3.1 Server Installation

Install theSQL Serversoftware according to its documentation.

3.1.3.2 Server Configuration

Before the SQL Server service can be used it must be configured to allow for connections over thenetwork.

From the Start Menu select:

Microsoft SQL Server 20xx, depending on the version installed



50/104


Configuration Tools

SQL Server Configuration Manager

Expand the SQL Server 20xx Network Configuration node

Click onProtocolsforSQLEXPRESSnode (or the instance name you configured during installa-

tion respectively)

On the right side, right click theTCP/IPentry and selectEnablefrom 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 fromthe context menu. The value in braces is the instance name, so make sure to select the correctone.

On the right side, right click theSQL Server Browserentry and selectStartfrom the contextmenu if its not already running.

Your newly installed instance is now configured to allow network connections. With the next steps adatabase for PowerFactoryis created.

Again, from theStartMenu select:

Microsoft SQL Server 20xx

SQL Server Management Studio Express

Change Authenticationto SQL Server Authentication

Enter the login name sa and enter the Password for sa, chosen during installation

SelectFile New Query with Current Connection

Enter the following lines in the Query Windowto 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

ClickExecutein the toolbar

You have now created a database named pfdbwith a corresponding login named pf which uses thepassword 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 forSQL Serveris described in section3.1.3.4



51/104


3.1.3.3 PowerFactoryConfiguration


Open Windows Start menu and run Start All Progams DIgSILENT Software PowerFactory

(Configuration)(see figure5.1.1on page85).




Figure 3.1.7: PowerFactoryConfiguration forSQL Server

Database driver select Microsoft SQL Server

Database service The Database service uses the format server name\instance name. If youused the default valuesSQL Server provides, it would be SERVERNAME\SQLEXPRESSfor the 2008edition. SERVERNAME is our virtual server name during this manual, as stated earlier. Note thatthe 2005 edition uses something called default instance, which must be accessed by omittingthe 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 pfdbas database name.






52/104


3.1.3.4 Backup

Create a Backup As with Oracle, SQL Servers backup facilities are far beyond the scope of thisdocumentation. It is highly suggested you consult the official Microsoft documentation for detailedbackup strategies. We present a very simple method to backup a database and must stress that thismethod only satisfies the most basic needs.

A fullSQL Serverdatabase 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 pfdbto a file d:\backupdir\pfdb.dump,sa andaSecurePasswordForSa 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 file e.g. d:\backupdir\backup.batwith a text editor (e.g. Windows Notepadeditor).

Insert the above text into the file (all in one line!).

Close the file.

WindowsScheduled Tasks utility allows you to run this batch script automatically, for example everyday at midnight.

Open the scheduler manager Windows Start menu:Start Programs AccessoriesSystem Tools Scheduled Tasks

Add a new scheduler task PowerFactorybackup and configure it as follows (see the Windowsdocumentation for further information)

Enter the backup script d:\backupdir\backup.batto be run.

Select the dailyoption and00:00as start time.

This configuration creates nightly backups. The pfdb.dumpfile is overwritten each time. If you want to

keep the latest three backup dumps enhance the above backup.batscript 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 file.



53/104


Restore a Backup The RESTORE DATABASE command recovers a database from a dump file. Torestore a database backup on the same database server where it was created follow the instructionsbelow.

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:\msde2be

the installation folder of the targetSQL Server. All commands are to be run insidesqlcmd

.

First create a database user pf for PowerFactoryusage.

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 thepf user

USE pfdb

GO

sp_change_users_login AUTO_FIX, pf

GO

3.1.4 Vault (optional)

The Vaultis a shared directory where all PowerFactoryinstances can read and write files. TwoPow-erFactoryfeatures require a Vault:

Shared Result Files PowerFactorystores almost all data in the database. Result Filesare anexception. Result Filesare binary files containing the result of simulation calculation. Due toperformance reasons (these results can be arbitrarily large) they are not stored in the databasebut directly in files 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 finish, its worth to keep them at hand.

In a multi-user database scenario where two PowerFactoryusers USER1 and USER2 work onthe very same project, USER2 cannot access the Result Files created by USER1 because theyrestored on USER1s hard disk.



54/104


Result Files in a Vault directory can be accessed by all PowerFactoryusers working on the samemulti-user database (see figure3.1.8).

Project Archiving: since PowerFactoryversion 15.1 users can archive their projects. The projectsare exported into an Archive folder in the Vault directory and then deleted from the database.Users can restore them later. The Housekeeping configuration 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 file server where all PowerFactoryusers (i.e. the Windows usersrunning PowerFactory) have read and write access. The Vault directory path has to be configured inPowerFactory.








55/104


Figure 3.1.9: PowerFactoryConfiguration forSQL 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 specified directory must exist and the current Windows must have read and write access tothis directory.




Note: A Vault directory is required only in rare scenarios e.g. when PowerFactoryusers often run

long-running simulations and work on the very same shared project, or when using the projectarchiving 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 inPowerFactory

Using PowerFactoryin a multi-user environment requires some additional administrative managementwhich is subject of this section.

User accounts and credentials must be created and configured.



56/104


Users can be organized in User Groups.

In this section the termUseralways refers to a PowerFactoryuser (and not to physical database serveruser e.g. onOracle,SQL Server, or theWindowsusers).

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 figure3.1.10).

Figure 3.1.10: User AuthenticationDialogue

3.1.5.2 Administrator User and Password

Administrative actions have to be carried out as a special built-in PowerFactoryuser: theAdministratoruser. The default Administrator password is Administrator. In a multi-user environment it is stronglysuggested to change this password immediately after the installation:

Start PowerFactoryinAdministrator mode:

Open Windows Start menu and run Start All Progams DIgSILENT Software PowerFactory(Administrator)(see figure5.2.1on page87).

If no Data Manager window is opened: create a new one by clicking on the icon .

Double-click the Administrator.IntUserobject in the data manager.

A user dialogue pops up (see figure3.1.11).

Figure 3.1.11: Setting the Administrator Password



57/104


Click on the Change Passwordbutton.

Enter a new Password. Repeat the password in the Confirm Passwordfield.

PressOK to save the changes.

3.1.5.3 User Creation

The PowerFactoryAdministratoruser is able to create and modify PowerFactoryuser accounts in amulti-user database.

Start PowerFactoryinAdministrator mode:

Open Windows Start menu and run Start All Progams DIgSILENT Software PowerFactory(Administrator)(see figure5.2.1on page87).

If no data manager is opened: create a new one by clicking on the icon .

Edit the User Managerobject inside the Configurationfolder by double clicking it.

A dialogue is shown (c.f. figure3.1.12).

Figure 3.1.12: Create PowerFactoryUser

Click the buttonAdd User....

In theUserdialogue insert at least the fieldUser name.

ClickChange Passwordand fill out the New Passwordand Confirm Passwordfields.

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 functionrights to the new user.



58/104


Edit the Frodo.IntUserobject (figure3.1.13).

On theLicensepage of the dialogue enable the functions the user is allowed to use. Enable atleast theMulti User Databaseoption.

PressOK.

Figure 3.1.13: Configure PowerFactoryUser

3.1.6 Housekeeping (optional)

Over the course of time the database grows and is cluttered with old data that might have a generalnegative impact on the database performance. PowerFactoryprovides a Housekeeping job that can

be configured to be run as periodical background job e.g. every night.

Deletion of items older than a configurable 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 Configuration

The PowerFactoryAdministratoruser is able to configure the Housekeeping settings (see figure 3.1.14).

Please find the details in the PowerFactory User Manual.



59/104


Figure 3.1.14: Housekeeping Configuration

3.1.6.2 Scheduling Housekeeping

This is an optional installation step that can be carried out at a later date. Housekeeping is described inthe Program Administration chapter of thePowerFactoryUser Manual.

Housekeeping is executed via a Windows Scheduled Task from a computer with PowerFactoryin-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 specifies the maximum run duration of the housekeeping as eight hours. Ifthe housekeeping is scheduled to start at 11 p.m. and is still not finished at 7 a.m., it will exit aftercompleting its current action.

In the example above, 60specifies the sleep period, in seconds, after a housekeeping action. If therewere no sleep period the housekeeping would place a heavy workload on the system, possibly affectingother active users.

Housekeeping connects as a special administrative PowerFactoryuser called Housekeeper, which isautomatically created when housekeeping is run for the first 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 configuration isshown in figure3.1.15.



60/104

CHAPTER 3. ADVANCED INSTALLATION 3.2. APPLICATION SERVER

Figure 3.1.15: Configuring a scheduled task to run housekeeping

Program/script Insert the path to the PowerFactoryexecutable 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 configure this via the house-keeping maximum run duration parameter, but the scheduled task configuration can be used as a back-stop. When configuring the scheduled task, choose an appropriate operating system user to run thetask. 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 inparallel Windows sessions. A typical scenario for a PowerFactoryinstallation is shown in figure3.2.1.Several machines and components are involved:



61/104

3.2. APPLICATION SERVER CHAPTER 3. ADVANCED INSTALLATION

Many Workstations The actual PowerFactoryuser works locally on his Workstation. When the userstarts the application, a PowerFactoryprocess 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 PowerFactoryare running on this server.There might be several Application Server Computers organized in a Server Farm.

Database Server Manages the central PowerFactorydatabase. AllPowerFactoryinstances commu-nicate with it.

Vault File Server (Optional) provides a shared Vault directory (section3.1.4on page47).

License Server Part of a normalServer Versioninstallation (see section2.4on page18). The LicenseServerdoesnt have to run necessarily on a separate computer, it can be hosted on the ApplicationServer.

Figure 3.2.1: Application Server Environment

Installing PowerFactoryon an Application Server offers several advantages over a normal multi-userdatabase installation:

PowerFactoryhas to be configured only once on the Application Server computer, but can beused by potentially hundreds of Workstations.

A high-bandwidth network connection is necessarily required between PowerFactoryand a databaseserver. Bigger companies have their PowerFactoryusers distributed over several remote loca-tions with low-bandwidth network.

Figure3.2.1suggests that all components have to be installed on different machines. But its possibleto deploy several components on the same computer e.g. the Application Server machine can hostPowerFactory,License Server, and the Vault directory.

Note: PowerFactoryis executed in its entirety on the application server. It is important that the servercomplies with PowerFactorys computing requirements: RAM, CPU(s), hard disk space, etc.

This section describes how to configure PowerFactoryon application server for three Windows usersFrodo,Sam, andPippin. It is assumed that

PowerFactoryServer Version is already installed on the computer according to section2.4onpage18.



62/104

CHAPTER 3. ADVANCED INSTALLATION 3.2. APPLICATION SERVER

Additionally a multi-user database should be up and running as described and PowerFactoryisconfigured to use it section3.1on page35.

The PowerFactory installation directory (usuallyC:\Program Files\DIgSILENT\PowerFactory 15.1)contains

PowerFactorythe application binary PowerFactory.exealong with several DLL files

the configuration filePowerFactory.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 PowerFactoryrequires a separate workspace directory which will holdtemporary data and log files. The workspace directories are subfolder of a common workspace directorye.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 vaultdirectory is optional (see section3.1.4on page47). The workspaces directory must not benecessarily on a local hard disk. It can be on an network drive instead e.g. \\SERVER\PowerFactoryWorkspaces.

3.2.1 Workspace directories

Create a root directory for all Workspaces e.g.

D:\Data\PowerFactory Workspaces

Create a Workspace directory for eachWindowsuser:

D:\Data\PowerFactory Workspaces\Frodo

D:\Data\PowerFactory Workspaces\Sam

D:\Data\PowerFactory Workspaces\Pippin

Verify that eachWindowsuser has read and write access to his Workspace directory

(optional) Create a Vault directory e.g.



63/104

3.2. APPLICATION SERVER CHAPTER 3. ADVANCED INSTALLATION

D:\Data\PowerFactory Workspaces\vault

Verify that eachWindowsuser has read and write access to the Vault directory.

3.2.2 PowerFactoryConfiguration




Switch to theWorkspacepage

Insert the directory settings as described below (see figure3.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 Directoryon theDatabaseas described insection3.1.4on page47.



Windows eventually shows an User Access Control dialogue and asks for an Administrator users

credentials in order to save the configuration file into the PowerFactoryinstallation directory (see fig-ure4.2.1on page75). Select an Administrative Windows user from the list, insert the users password,and pressYes.



64/104

CHAPTER 3. ADVANCED INSTALLATION 3.3. OFFLINE MODE

3.3 Offline Mode

Since Version 15.0 PowerFactoryprovides the ability to work in Offline Mode when a network con-nection to the database server is unavailable. The required project data is cached to the users localmachine, 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: Offline Mode requiresMulti-user databaseand Floating Licensesmodule.

This section describes the installation and configuration of the Offline Proxy Service, a software com-ponent of PowerFactoryto be used with the Offline Mode database driver on Microsoft Server 2008R2. Figure3.3.1gives an overview over all components.

Figure 3.3.1: Offline Mode Components Overview

The installation procedure consists of the following steps:

1. First a PowerFactoryenvironment in normal (i.e. not-offline) mode has to be set up. It contains atleast a PowerFactoryinstallation, a License Server, and a multi-user database server (OracleorSQL Server) (see section3.3.1).

2. Installation of theOffline Proxy Serviceon an application server (see section3.3.2).

3.

installation manual 15.1 en

Documents