PLA 3.0. Installation Guide

Transcription

1 PLA 3.0 Installation Guide

2 PLA Installation Guide COPYRIGHT 2015 by Stegmann Systems GmbH, Rodgau, Germany. All rights reserved. CONTACT Stegmann Systems GmbH Raiffeisenstr. 2 // C1, C Rodgau Germany Phone: Fax: support@bioassay.de 2

3 Table of Contents TABLE OF CONTENTS Copyright... 2 Contact... 2 Table of Contents... 3 Welcome... 7 Installation Guide... 8 Installing PLA System Requirements (Local Installation)... 8 System Requirements (Terminal Server Installation)... 8 System Requirements (SQL Server)... 9 Preparing the System... 9 Installation... 9 Network Protection Key Server Installation HASP Keys Prerequisites Installation of the HASP Driver Allow Access From Remote Clients Configure Access (Server Side) Configure Access (Client Side) HASP Software Protection Keys Hardlock Keys Prerequisites Installation of the Hardlock Driver Configure Access (Client Side)

4 PLA Installation Guide Hardware Keys on Virtual Machines Local Protection Key Installation Managing Software Protection Keys Installation of a Software Key Create New Protection Key Apply License File Update of an existing Software Key Create Update Key Request Apply License File Transfer of a Software Key Prerequisites Collect and Save Information Create License Transfer File Apply License File Deployment Scenarios Concepts Databases Database Connections Trial Version Licenses Seat License Concurrent Use License License Key Global Properties

5 Table of Contents User Specific Properties Database Policies Used Paths Scenarios General Standalone Environment (Seat License) Multi User Environment (Seat License) Multi User Environment (Concurrent Use License) Terminal Server Environment Managing License Keys License Information Software Protection Key Serial Number License Keys Download Add Rollout Adjust Global Properties Properties Manage Databases Create Databases Preparation (MS-SQL Only) Initialization MS-SQL SQLite

6 PLA Installation Guide Manage Database Connections Import Database Connections Export Database Connections Distributing Database Connection

7 Welcome WELCOME Welcome to the PLA 3.0 Installation Guide. This handbook is primarily intended for system administrators. This guide describes the deployment scenarios for PLA 3.0, the installation of PLA 3.0 and the license server as well as extended preferences for the usage of PLA 3.0. It is supposed to help system administrators to adjust PLA 3.0 to company guidelines. 7

8 PLA Installation Guide INSTALLATION GUIDE INSTALLING PLA 3.0 SYSTEM REQUIREMENTS (LOCAL INSTALLATION) Item Minimum Recommended Operating System Windows 7, Windows 8, Windows 8.1 Processor Single-core, 2 GHz Quad-core, 2,4 GHz or faster Memory 2 GB RAM 4 GB RAM Hard disk 500 MB of available space 1 GB of available space, or more Graphics display Graphics display with 1024 x 768 resolution Minimum Color 16 Bit Depth Software installation Software activation Storage space for a about 25 MB local database Storage space per assay Graphics display with 1280 x 1024 or higher resolution Internet connection or CD drive USB 2.0 port or remote license server about 1 MB including audit trail, depending on complexity and number of changes SYSTEM REQUIREMENTS (TERMINAL SERVER INSTALLATION) Item Minimum Recommended Operating System Windows Server 2003, Windows Server 2008, Windows Server 2008R2, Windows Server 2012, Windows Server 2012R2 Hard disk 500 MB of available space 1 GB of available space, or more 8

9 Installation Guide SYSTEM REQUIREMENTS (SQL SERVER) Item Minimum Recommended Version Microsoft SQL Server 2005, Microsoft SQL Server 2008 Processor *) Single-core, 2 GHz Quad-core, 2,4 GHz or faster Memory *) 2 GB RAM 4 GB RAM Hard disk 500 MB of available space 1 GB of available space, or more Storage space per database about 25 MB Storage space per assay about 1 MB including audit trail, depending on complexity and number of changes *) Based on Microsoft recommendations. PREPARING THE SYSTEM Ensure there is enough free disc space on the system. Adobe Reader will be required for viewing and printing reports on the system. This free software is available at INSTALLATION Start the setup as administrator and follow the instructions. In case there was a previous version of PLA 3.0 installed on this system, it will be recognized by the setup. Previously installed PLA 3.0 versions will be removed by the installation program. Important: After completing the PLA 3.0 setup, you also need to run the PLA 3.0 application as administrator once, to finalize the installation. Extended Adjustments can be made after the installation and are covered in the following chapters. 9

10 PLA Installation Guide NETWORK PROTECTION KEY SERVER INSTALLATION Besides local Protection Keys, PLA 3.0 supports using Protection Keys via local networks. These Network Protection Keys are multi user licenses and allow authenticating a certain amount of running PLA instances. These instances only count if the Protection Key with a valid Activation Key is used to authenticate PLA License Keys, to enable a fully functional PLA 3.0 instance. HASP KEYS HASP keys are available as a hardware or a software protection key and have advanced methods to configure the client-server access. PREREQUISITES The license server needs to be accessible for the PLA workstations via your local network. The Sentinel License Manager Service requires certain ports to be opened on the Protection Key server and on any client that needs to access the Protection Key server. Incoming and outgoing network traffic for TCP Port 1947 and UDP Port 1947 need to be allowed between the PLA License Server and the PLA Workstations. IPv4 sockets are always opened (Sentinel License Manager currently does not work without IPv4 installed). IPv6 sockets are opened if IPv6 is available. These sockets need to be opened if you want to access the Admin Control Center locally on the server, too. INSTALLATION OF THE HASP DRIVER To install a HASP Network Key, you have to install the HASP driver using the haspdinst.exe from the PLA 3.0 installation CD via the command line using the parameter -i. 10

11 Installation Guide The Sentinel LDK driver installs a service named Sentinel Local License Manager that needs to run on the PLA License Server to allow the PLA Workstations to use the Protection Key. ALLOW ACCESS FROM REMOTE CLIENTS Connect the Network HASP Hardware Key or install a HASP Software Key and open the Web Admin Control Center in your browser at :1947. When selecting Sentinel Keys, a list of all available HASP Keys is displayed. These HASP Keys are either locally connected to your computer or shared by other computers using the local network. 11

12 PLA Installation Guide To use the HASP Key via the local network, click Configuration and select the tab Access from Remote Clients. Allow Access from Remote Clients has to be activated to allow other computers to authenticate their PLA 3.0 licenses using the HASP Key. When saving these properties using Submit, it may take several minutes to activate them. Afterwards the HASP Key is available in the local network and can be used by PLA 3.0 instances. CONFIGURE ACCESS (SERVER SIDE) The HASP license server can allow only specific clients to be able to receive licenses from the license server. The Access Restrictions textbox allows setting additional restrictions. The PLA 3.0 access to HASP Keys can be restricted. The entries are made line by line and the first lines are prioritized. Entries are: allow=<ip> or <Hostname> or all deny=<ip> or <Hostname> or all At the end of the list the entry allow=all will be appended if it is not yet part of the list. When saving these properties using Submit, it may take several minutes to activate them. CONFIGURE ACCESS (CLIENT SIDE) If there are multiple license server in a network it is possible to configure PLA 3.0 to use a specific license server or to prioritize certain license servers over others. These access restrictions can be enabled in the pla.properties file (see chapter Adjust Global Properties and chapter Used Paths). The selection of the HASP Key Servers can be influenced by the following properties (see chapter Properties in Global Properties): 12

13 Installation Guide com.stegmannsystems.edp.license.hasptargethostnames It is possible to specify one or more hostnames of HASP Key Servers by dividing them with semicolons. First listed hostnames are prioritized. com.stegmannsystems.edp.license.hasptargetips It is possible to specify one or more IP addresses of HASP Key Servers by dividing them with semicolons. First listed IP addresses are prioritized. Using both properties at the same time is possible. The list with hostnames is used first, followed by the list of IP addresses. com.stegmannsystems.edp.license.providers This property allows setting which type of Protection Key Server is addressed. Hasp only uses HASP Key Servers. Hardlock only uses Hardlock Key Servers. If not configured HASP license servers have a higher priority than Hardlock license servers. HASP SOFTWARE PROTECTION KEYS How to setup and manage software protection keys is covered in the chapter Managing Software Protection Keys. The steps described in the Create New Protection Key subchapter of Managing Software Protection Keys need to be applied on the PLA License Server, because the protection key has to be created for the PLA License Server. HARDLOCK KEYS Hardlock keys are only available as a hardware and have a reduced set of methods to configure the client-server access. 13

14 PLA Installation Guide PREREQUISITES The license server needs to be accessible for the PLA workstations via your local network. The Hardlock Monitor requires certain ports to be opened on the Protection Key server and on any client that needs to access the Protection Key server. Incoming and outgoing network traffic for UDP Port 3047 needs to be allowed between the PLA License Server and the PLA Workstations. INSTALLATION OF THE HARDLOCK DRIVER To install the Hardlock Key Server software, administrative rights are required. Start the aksmon32_setup.exe and install the Aladdin Monitor software. This software monitors sessions on the Network Hardlock Key and manages the Hardlock Server services. Start Aladdin Monitor with administrative rights. 14

15 Installation Guide Select Hardlock in the Services menu and afterwards install the HL- Server Service. The installation was completed if the following message is displayed. Start the Hardlock Server Service which is located in the Services sub menu Hardlock. The hostname of the computer is now displayed in the Navigator in the folder Hardlock. If it is not displayed, please reload the list via Reload in the File menu. Now connect the Network Hardlock Key with the computer. The Navigator now displays the sub item 9307 below the hostname. If the sub item is not displayed, please reload again. Selecting the sub item 9307 displays a list, containing all currently connected PLA 3.0 instances. 15

16 PLA Installation Guide CONFIGURE ACCESS (CLIENT SIDE) The access on Network Hardlock Key Servers can be restricted through setting the environment variable HLS_IPADDR to one or more IP addresses or hostnames. Values are separated with commas. The computer will only search these addresses for Network Hardlock Key Servers. Annotation: This environment variable affects all programs using a Hardlock Key Server. Thus adjust the environment variable so it includes all addresses of all Network Hardlock Key Servers required by this computer. If there are Hardlock and HASP license server in your network it is possible to prioritize or enable only a certain type of license server via a property in the pla.properties file (see chapter Adjust Global Properties and chapter Used Paths). com.stegmannsystems.edp.license.providers 16

17 Installation Guide HARDWARE KEYS ON VIRTUAL MACHINES When using Hardware Keys on virtual machines, we recommend connecting the Network Hardware Key with the virtual machine via a network USB device. Depending on your virtualization environment, it may be possible to connect the Network Hardware Key with a physical USB port of the host. The installation of the Protection Key Server software depends on the type of the Protection Key, but is identical with the one on a physical machine. For further information, please read the HASP Key or Hardlock Key section of this chapter. LOCAL PROTECTION KEY INSTALLATION The drivers for the protection keys are part of the PLA 3.0 setup and will be installed automatically. It is also possible to install them manually using the HASPUserSetup.exe from the PLA 3.0 installation CD. When using a hardware protection key you need to connect it to the workstation. If you are using a software protection key please follow the instructions in subchapter Installation of a Software Key in the Managing Software Protection Keys chapter. MANAGING SOFTWARE PROTECTION KEYS Software protection keys use the HASP license server system and the base configuration is similar to HASP license server with a hardware protection key. However the installation and management of the software key on the license server requires a few more steps described in the following chapters. 17

18 PLA Installation Guide INSTALLATION OF A SOFTWARE KEY A Software Key is always bound to the computer it has been created on and cannot be used on any other computer to verify Activation or License Keys. If you need to move your PLA License Server to a different computer you need to perform a Software Key license transfer process. Information on the transfer of Software Keys is available in the chapter Transfer of a Software Key. An active internet connection is not required during the process, you can send the containing the resulting Update receipt file (.C2V) using a different computer which has an active internet connection. CREATE NEW PROTECTION KEY Start the RUS_MATRG.exe to create a protection key or apply a license file. 18

19 Installation Guide To create a new protection key, select Installation of new protection key within the Collect Status Information tab of the Stegmann Systems Software Key Management application and press the Collect Information button. This option is disabled if you have already installed a protection key on the computer. When the required information has been successfully collected, an update receipt file (.C2V) will be generated. Save the generated update receipt file to your computer. 19

20 PLA Installation Guide Send the update receipt file (.C2V) that has been generated as written in the Create New Protection Key chapter to support@stegmannsystems.com. APPLY LICENSE FILE When you have sent an with the generated update receipt file to support@stegmannsystems.com, you will receive a reply from the Stegmann Systems customer service with an attached license file (.V2C). Save the license file to the computer the protection key has been created with. To apply a license file, start the RUS_MATRG.exe, switch to the Apply License File tab of the Stegmann Systems Software Key Management application and Select the license file (.V2C) you have received from the Stegmann Systems customer service. 20

21 Installation Guide After selecting the license file, proceed by clicking the Apply Update button. 21

22 PLA Installation Guide When the license file has been successfully applied, you have successfully installed the PLA Software Key. You now can activate the Software Key using the PLA License Manager. Further information on the PLA License Manager is available in the Managing Licenses chapter of the PLA Installation Guide. UPDATE OF AN EXISTING SOFTWARE KEY CREATE UPDATE KEY REQUEST 22

23 Installation Guide Start the RUS_MATRG.exe to create an update key request or apply a license file. To create an update key request, select Update of existing protection key within the Collect Status Information tab of the Stegmann Systems Software Key Management application and press the Collect Information button. 23

24 PLA Installation Guide Now select the protection key you need to get updated and press OK. When the required information has been successfully collected, an update receipt file (.C2V) will be generated. Save the generated update receipt file to your computer. Send the update receipt file (.C2V) that has been generated as written in the Create Update Key Request chapter to support@stegmannsystems.com. APPLY LICENSE FILE When you have sent an with the generated update receipt file to support@stegmannsystems.com, you will receive a reply from the Stegmann Systems customer service with an attached license file (.V2C). Save the license file to the computer the update key request has been created with. To apply a license file, start the RUS_MATRG.exe, switch to the Apply License File tab of the Stegmann Systems Software Key Management application select the license file (.V2C). You can only ap- 24

25 Installation Guide ply the license file to the computer the update key request has been created with. After selecting the license file, proceed by clicking the Apply Update button. 25

26 PLA Installation Guide When the license file has been successfully applied, you have successfully updated the PLA Software Key. You now can activate the Software Key using the PLA License Manager. Further information on the PLA License Manager is available in the Managing Licenses chapter of the PLA Installation Guide. TRANSFER OF A SOFTWARE KEY In case you need to replace your PLA License Server or PLA Workstation, the transfer of a Software Key process needs to be applied because the Software Key is bound to the computer it has been created with. In addition, the requirements listed below have to be met. It is recommended to close all PLA applications during the transfer of the Software Key. To transfer a license key meet the requirements and follow the steps listed in this chapter. PREREQUISITES When a Software Key needs to be transferred to a new PLA Workstation or License Server, the following requirements apply: Standalone environment: Target computer needs to be prepared as mentioned in Local Protection Key Installation. Multi user environment and terminal server environment: Target server has to meet the prerequisites for HASP server installation and HASP driver needs to be installed. Source computer and target computer need to be in the same network 26

27 Installation Guide Incoming and outgoing network traffic for TCP Port 1947 and UDP Port 1947 needs to be allowed between source and target computer A way to transfer files between target and source computer COLLECT AND SAVE INFORMATION Start the RUS_MATRG.exe on the target computer and open the Transfer License tab to transfer a Software Key. The target computer is the computer the license will be transferred to. 27

28 PLA Installation Guide In the Transfer License tab, click the button of the Collect information about the recipient computer area to choose a destination for the recipient information file (.ID). After choosing a destination file for the recipient information file (.ID), press the Collect and Save Information button to create the file. 28

29 Installation Guide When the file has been successfully created, make the file, or a copy of the file, available for the source computer of the license transfer process. The source computer of the license transfer process is the computer that is currently holding the Software Key. CREATE LICENSE TRANSFER FILE Start the RUS_MATRG.exe on the source computer and open the Transfer License tab to transfer a Software Key. The source computer is the computer the license will be transferred from. 29

30 PLA Installation Guide Use the button next to the Read the recipient information file from input field of the Transfer License tab and select the recipient information file that has been created as written in the Collect and Save Information chapter. 30

31 Installation Guide Use the button next to the Generate the license transfer file to input field of the Transfer License tab to choose a destination for the license transfer file (.H2H). After choosing a destination for license transfer file (.H2H), press the Generate License Transfer File button to create the file. Confirm that you do want to transfer the selected license key to a different computer using the Yes button of the dialog. 31

32 PLA Installation Guide When the file has been successfully created, make the file, or a copy of the file, available for the target computer of the license transfer process. The target computer of the license transfer process is the computer the Software Key needs to be transferred to. 32

33 Installation Guide The source computer now has lost the Software Key. As long as the Software Key has not been transferred to the target computer, it cannot be used to enable License Keys of a PLA installation. APPLY LICENSE FILE Switch back to the RUS_MATRG.exe on the target computer and open the Apply License File tab to transfer the Software Key. The target computer is the computer the license will be transferred to. 33

34 PLA Installation Guide Use the button of the Apply License File tab to choose the license transfer file (.H2H) that has been created as written in the Create License Transfer File chapter. After choosing the license transfer file (.H2H), the Apply License File tab will show you a summary of the license transfer process. Press the Apply Update button to transfer the license to the target computer. When the license file has been successfully transferred, you have installed the PLA Software Key on the target computer. The Soft- 34

35 Installation Guide ware Key in combination with an Activation Key can be used again to enable License Keys of a PLA installation. DEPLOYMENT SCENARIOS CONCEPTS DATABASES PLA 3.0 supports databases with Client-Server model as well as local ones or local databases shared via network connections. This allows running a workstation completely autarkic, as well as working with one database in a multi user environment. DATABASE CONNECTIONS Database connections are automatically generated when creating a database in PLA 3.0. They contain connection data like path, address, username and the encrypted password to access a database. They are saved in a folder and are importable and exportable. Attention: Database connection files are no databases, but shortcuts to a database. TRIAL VERSION If you want to evaluate PLA 3.0, feel free to do so. Installing PLA 3.0 automatically gives you a 14 day trial license. If you need more time testing PLA 3.0, please contact the Stegmann Systems customer support using the contact information supplied in the Contact chapter of this book. While testing, all features of a PLA 3.0 license are available but PDF reports are tagged and cannot be printed. The functionality of the validation package is not available. 35

36 PLA Installation Guide LICENSES There are two different licensing models available for PLA 3.0: SEAT LICENSE A seat license is bound to a specific computer system. PLA 3.0 can be used by all users of this computer, but only one user at a time. It is not permitted to make use of several instances of PLA 3.0 by different users at once (e.g. via Remote Desktop). A Protection Key device needs to be connected to each computer system to enable the usage of a seat license. CONCURRENT USE LICENSE 36

37 Installation Guide A network hardware key is attached to a license server which keeps track of the licenses currently in use and the maximum of allowed licenses. The concurrent use license allows the installation of PLA 3.0 on any number of computer systems within your site. At startup PLA 3.0 contacts the license server to obtain a license. LICENSE KEY The licensing of PLA 3.0 is dual. This means there is a licensing via physical or software protection key and license keys in addition, which can only be activated in combination with the matching protection key. Stegmann Systems runs a server where the license keys for the protection keys are stored and can be downloaded if an internet connection is available and the protection key is connected. It is possible to activate your license without an active internet connection by manually adding license keys. GLOBAL PROPERTIES Some properties in PLA 3.0 affect the whole system. Global properties are the used license keys, the restrictions for using network hardware keys, the list of available databases and properties to search for news and updates. These properties are mandatory for all users of the system. Important: To prevent users from changing system wide settings, remove the write permission for the corresponding user group from the pla.properties file. The path to the pla.properties file is available in the subchapter Used Paths. USER SPECIFIC PROPERTIES The user specific properties hold the default paths for actions, proxy settings and further UI properties. Frequently used paths can be 37

38 PLA Installation Guide defined as default paths for fast access on folders and documents by every user, to simplify the handling of PLA 3.0. DATABASE POLICIES The database policies define settings for password rules, electronic signatures and reasons for changes. Database policies can differ from database to database. It is possible for policies to be highly restrictive on the production database, while the test database has only policies of limited extend to avoid making tests unnecessarily complex. USED PATHS Global Properties Windows 7, 8.x, 2008, 2012: C:\ProgramData\Stegmann Systems\PLA 3.0\pla.properties Windows XP: C:\Documents and Settings\All Users\Application Data\Stegmann Systems\PLA 3.0\pla.properties Override Path of Properties- Files Database Connections Windows 7, 8.x, 2008, 2012: C:\ProgramData\Stegmann Systems\PLA 3.0\plaredirect.properties Windows XP: C:\Documents and Settings\All Users\Application Data\Stegmann Systems\PLA 3.0\plaredirect.properties Windows 7, 8.x, 2008, 2012: C:\ProgramData\Stegmann Systems\PLA 3.0\DBConnections Windows XP: C:\Documents and Settings\All Users\Application Data\Stegmann Systems\PLA 3.0\ DBConnections 38

39 Installation Guide Standard Component Packages Additional Component Packages User Specific Properties Windows 7, 8.x, 2008, 2012: C:\Program Files (x86)\stegmann Systems\PLA 3.0\packages Windows XP: C:\Programme\Stegmann Systems\PLA 3.0\packages Windows 7, 8.x, 2008, 2012: C:\Program Files (x86)\common Files\Stegmann Systems\PLA 3.0\packages Windows XP: C:\Programme\Common Files\Stegmann Systems\PLA 3.0\packages Windows 7, 8.x, 2008, 2012: C:\Users\USERNAME\AppData\Local\Stegma nn Systems\PLA 3.0\config\.metadata\.plugins\org.eclipse.cor e.runtime\.settings\com.stegmannsystems.lim s.core.prefs Windows XP: C:\Documents and Settings\USERNAME\Local Settings\Application Data\Stegmann Systems\PLA 3.0\config\.metadata\.plugins\org.eclipse.core.r untime\.settings\com.stegmannsystems.lims.c ore.prefs 39

40 PLA Installation Guide Custom Database Connections Windows 7, 8.x, 2008, 2012: C:\Users\USERNAME\AppData\Local\Stegmann Systems\PLA 3.0\DBConnections Windows XP: C:\Documents and Settings\USERNAME\Local Settings\Application Data\Stegmann Systems\PLA 3.0\DBConnections SCENARIOS GENERAL For terminal server and virtual environments the usage of a network hardware key is mandatory. Apart from that, seat licenses, as well as concurrent use licenses which are distributed by a license server are available for PLA 3.0 installations. The selection of the database system should be based on how many users will be using PLA 3.0 simultaneously. You can find additional information in the Databases chapter. There are several deployment scenarios for PLA 3.0. In the following are four most frequently used scenarios sketched and described. STANDALONE ENVIRONMENT (SEAT LICENSE) PLA 3.0 is installed on a workstation and is using a SQLite file based database. A locally attached hardware key is used for authentication. This solution is only for very small environments or for the duration of the trial period. Important: The customer is responsible for backing up the database file on a regular basis. 40

41 Installation Guide MULTI USER ENVIRONMENT (SEAT LICENSE) PLA 3.0 is installed on a workstation and is using a MS-SQL database in collaboration with other users. A locally attached hardware key is used for authentication. MULTI USER ENVIRONMENT (CONCURRENT USE LICENSE) 41

42 PLA Installation Guide PLA 3.0 is installed on a workstation and is using a MS-SQL database in collaboration with other users. PLA 3.0 accesses a license server which has a network hardware key attached to it to acquire a license. TERMINAL SERVER ENVIRONMENT PLA 3.0 is installed on a virtual machine running on a terminal server and is using a MS-SQL database in collaboration with other users. PLA 3.0 accesses a license server which has a network hardware key attached to it to acquire a license. The virtual machine is accessed by a terminal client. 42

43 Installation Guide MANAGING LICENSE KEYS License Keys can be added via License Management. To access the License Manager, use the Tools button in the login screen of PLA 3.0 or the Help menu of PLA 3.0. LICENSE INFORMATION Here you see the current license state. When you have a valid Activation Key, you can validate PLA 3.0 License Keys. The state of a PLA 43

44 PLA Installation Guide license changes to valid, if it has been validated successfully. When using PLA in trial mode, the remaining days are displayed. SOFTWARE PROTECTION KEY SERIAL NUMBER The Protection Key Serial Number that is used in combination with the Activation Key, to authenticate your PLA 3.0 License Keys. LICENSE KEYS DOWNLOAD Stegmann Systems keeps the License Keys for every Protection Key Serial Number on a server. Via Download you are able to download all licenses purchased for the currently displayed Protection Key, simplifying the activation of your licenses. ADD If your computer has no access to the internet, License Keys can be added manually. It is possible to enter the License Key manually, via CRTL + V or via Paste From Clipboard button. Annotation: Before PLA 3.0 or the PLA 3.0 Validation Package can be licensed, a valid Activation Key has to be entered, because the Pro- 44

45 Installation Guide tection Key and its Activation Key is required to verify the validity of your License Keys. If you encounter problems at login, please check your licenses. If a Protection Key with a different Serial Number is used, you have to enter the corresponding Activation Key and License Keys. ROLLOUT The Activation and License Keys are saved in the pla.properties file. See chapter Adjust Global Properties and chapter Used Paths for further information on the pla.properties file. The License Keys can be distributed by copying the file to the corresponding folder. This process might require administrative rights. ADJUST GLOBAL PROPERTIES Device-specific adjustments can be made via global properties. All instances of PLA 3.0 have to be closed. These adjustments are specified in the pla.properties file. This file can be opened with a text editor program of your choice. You might need administrative rights to make changes to the global properties. PROPERTIES To use these properties, please enter the key and the according value into one line, divided by an equal sign. Key Value Description com.stegmannsystems. edp.internet.access <Number of the Option> Access to the internet for searching Messages and Updates. 45

46 PLA Installation Guide Key Value Description 1 = auto search 2 = manual search 3 = no search com.stegmannsystems. edp.system.disabledat abasemanagement com.stegmannsystems. edp.system.executeiq NotAllowed true or false Locking the database in the login screen true or false Locking the Installation Qualification in the login screen com.stegmannsystems. edp.system.availabled atabase_0 com.stegmannsystems. edp.system.availabled atabase_1 com.stegmannsystems. edp.system.availabled atabase_2 com.stegmannsystems. edp.system.availabled atabase_3 com.stegmannsystems. <GUID of the database connection. It is located in the connection profiles. See chapter Used Paths for further information on where to find database connections. Restricting the available database profiles. Only specified database profiles are displayed in the login screen. 46

47 Installation Guide Key Value Description edp.system.availabled atabase_4 com.stegmannsystems. edp.system.availabled atabase_5 com.stegmannsystems. edp.system.availabled atabase_6 com.stegmannsystems. edp.system.availabled atabase_7 com.stegmannsystems. edp.system.availabled atabase_8 com.stegmannsystems. edp.system.availabled atabase_9 com.stegmannsystems. edp.system.reportprint Delay com.stegmannsystems. edp.license.keys <Time in seconds> (List of license keys separated via semicolons) Printing jobs are delayed by this time List of license keys com.stegmannsystems. (List separated Restricts the 47

48 PLA Installation Guide Key Value Description edp.license.providers via semicolons: valid values: hasp and hardlock ) license servers for the system. com.stegmannsystems. edp.license.hasptarget Hostnames com.stegmannsystems. edp.license.hasptarget IPs If this property is not available: hasp;hardlock (List of hostnames separated via semicolons) Working example: "WJKA03" Non-working example: "WJKA03.rssys tem.de" (List of IPaddresses separated via semicolons) Restricts the license servers for the system via hostnames. Restricts the license servers for the system via IP. Example: " " 48

49 Installation Guide OVERRIDE PATH FOR PROPERTIES FILES By usage of the file pla-redirect.properties the path where the system is reading and writing the pla.properties and other *.properties files can be overridden. For example all nodes in a network running PLA can use the same pla.properties file in one network share. Using this option can reduce the operating expenses to maintain multiple properties files on different nodes. Key Value Description com.stegmannsystems. edp.system.properties Path An (UNC-) path which can be accessed by the system. Overrides the path where the system reads and writes properties-files. Example: Z:\\Share\\S ettings\\ MANAGE DATABASES For information about configuring database properties, see the Administrator s Guide. CREATE DATABASES PLA 3.0 supports two different types of database systems, covering different scopes of use. MS-SQL is recommended for multi user environments. SQLite databases are file based databases, suited for local usage or for small groups if they are shared via the local network. 49

50 PLA Installation Guide PREPARATION (MS-SQL ONLY) A MS-SQL-Server 2005 or higher is required to create a PLA 3.0 database. An empty database is required, which will be initialized by PLA 3.0. A MS-SQL user or domain user with db_owner permission is required. After initializing the database using PLA 3.0, all PLA 3.0 accounts only need db_datareader and db_datawriter permissions to use the database. INITIALIZATION When starting PLA fort the first time after the installation, a dialog to create a new database connection opens. This dialog is also reachable via the login screen using the sub item Database Management in the Tools menu. 50

51 Installation Guide Choose the Standard Mode and continue using Next. MS-SQL 51

52 PLA Installation Guide To initialize a MS-SQL database, select Connect to existing database and ensure that Microsoft SQL Server is your active selection in the Type drop down menu. 52

53 Installation Guide Choose the server that holds the new database using the Server name drop down and enter the username and password of the MS- SQL account with db_owner permissions. If the desired server is not part of the list you can also type in the name or IP address of the server using your keyboard. Then choose the database which should be initialized using the Database name drop down. Proceed using the Next button. 53

54 PLA Installation Guide Verify the connection details and finish the setup. You will get the following dialog: 54

55 Installation Guide PLA will test the database and open the database templates dialog if the database has not been initialized before. 55

56 PLA Installation Guide Select a template for the database. Default Database (empty) contains predefined roles, but no documents. Default Database with Demo Data contains predefined roles and example documents. Confirm your choice and wait till the database has been initialized. Initializing an empty database will take approximately 1 minute, a database with Demo Data 5 minutes. 56

57 Installation Guide The dialog Create an Administrative Account will open when the database has been initialized. Enter an account name and password for the administrative account. Important: Keep a copy of the account information in a safe place, because the initial administrator cannot be recovered. Confirm the dialog and close the Database Management if this is not the first database connection on this system. The new database is now ready to use. SQLITE 57

58 PLA Installation Guide To initialize a SQLite database, select Create new database and SQLite in the Standard Mode of the Database Connection Management. 58

59 Installation Guide Change the database file and description, if necessary. 59

60 PLA Installation Guide Select a template for the database. Default Database (empty) contains predefined roles, but no documents. Default Database with Demo Data contains predefined roles and example documents. 60

61 Installation Guide Enter an account name and password for the administrative account. Important: Keep a copy of the account information in a safe place, because the initial administrator cannot be recovered. Confirm the dialog using Next. 61

62 PLA Installation Guide Verify your settings and confirm your choice using the Finish button. Initializing an empty database will take approximately 1 minute, a database with Demo Data 5 minutes. 62

63 Installation Guide When the database has been initialized, you can confirm the information dialog. Close the Database Management if this is not the first database of this system. The database is now ready to use. MANAGE DATABASE CONNECTIONS To manage database connections, open the Database Management in the Tools menu of the login screen. 63

64 PLA Installation Guide IMPORT DATABASE CONNECTIONS It is possible to import a database connection that has been exported using PLA 3.0. To do so, add a new database in Standard Mode. 64

65 Installation Guide Use the button next to Import database connection to select a.dbconnection file which has previously been exported using PLA

66 PLA Installation Guide Verify the settings of the database profile you want to import. 66

67 Installation Guide When the import is done, an information dialog will be shown. After confirming this dialog, the database connection is ready to use. EXPORT DATABASE CONNECTIONS You can export created database connections to make them available to other PLA Installations. Select Database Management choose the database connection to be exported and select Export. You can now edit file name and Path. If the process was finished successfully you will receive the following message. 67

68 PLA Installation Guide The database connection was saved as.dbconnection-file. DISTRIBUTING DATABASE CONNECTION Previously exported database connection profiles can be distributed by copying the.dbconnection-file to either the folder for userspecific or common connection profiles. See Chapter Used Paths for information about the file paths. 68