Laura 4.2 Application Installation Guide 4.2... · files whilst it is running. Some anti‐virus...

Application Installation Guide

Ref : Laura 4.2 Application Installation Guide Version: 4.2.11 Compiled by: LabLogic Date: 07 Aug 2015

Page 2 of 124

Laura Application Installation Guide

Contents Introduction .................................................................................................................................... 4 Database Options ............................................................................................................................ 5 Installation of the Application ........................................................................................................ 9

Laura install ................................................................................................................................................... 10 Welcome Dialog .............................................................................................................................. 11 Select Destination Location dialog .................................................................................................. 12 Select Components dialog ............................................................................................................... 13 Select Start Menu Folder dialog ...................................................................................................... 14 Ready to Install dialog ..................................................................................................................... 15 Copying files process ....................................................................................................................... 16 Setup Complete dialog .................................................................................................................... 17

Upgrading From Earlier Versions .................................................................................................. 18 Connecting a LabLogic USB instrument ........................................................................................ 19 Connecting the license dongle ...................................................................................................... 19 Launching the Laura application ................................................................................................... 20 Oracle Client/Server Install ........................................................................................................... 21

Oracle Server with no Laura tablespaces ...................................................................................................... 21 Networked Data Files for Files mode installation ......................................................................................... 23

MSSQL201x Server Client/Server Install ....................................................................................... 24 MS SQL Server with no Laura database ......................................................................................................... 25 Networked Data Files .................................................................................................................................... 26

Summary ‐ After the Install Of Laura ............................................................................................ 27 APPENDIX A: FILES THAT LAURA INSTALLS OR MODIFIES ON A CLIENT MACHINE ..................... 30 APPENDIX B: OPTIONAL SETUP PROGRAM PARAMETERS ........................................................... 44 APPENDIX C : LAURA ORACLE INSTALLATION GUIDE ................................................................... 46

Introduction................................................................................................................................................... 46 Overview ....................................................................................................................................................... 47 Quick Installation Instructions ....................................................................................................................... 48 Advanced Installation Instructions ................................................................................................................ 48

APPENDIX D: INSTALL MSSQL 2012 SERVER EXPRESS .................................................................. 57 Prerequisites ................................................................................................................................................. 57 Extracting Files .............................................................................................................................................. 57 SQL Server Installation Center ....................................................................................................................... 59 Setup Support Rules ...................................................................................................................................... 60 SQL Server Installation Center ....................................................................................................................... 61 Setup Support Rules ...................................................................................................................................... 62 License Terms ................................................................................................................................................ 63 Install Setup Files ........................................................................................................................................... 64 Feature Selection........................................................................................................................................... 65 Instance Configuration .................................................................................................................................. 66 Disk Space Requirements .............................................................................................................................. 67 Server Configuration ..................................................................................................................................... 68


Page 3 of 124


Database Engine Configuration ..................................................................................................................... 69 Error Reporting .............................................................................................................................................. 74 Installation Progress ...................................................................................................................................... 75 Completing Microsoft SQL Server 2012 Setup .............................................................................................. 76 Important ...................................................................................................................................................... 77

Start Laura ........................................................................................................................................ 84 Select Database ............................................................................................................................................. 84 No Database found ........................................................................................................................................ 85 Create Database ............................................................................................................................................ 86 Following successful database creation ........................................................................................................ 87

APPENDIX E: INSTALL MSSQL 2014 SERVER EXPRESS ................................................................... 88 Prerequisites ................................................................................................................................................. 88 Extracting Files .............................................................................................................................................. 89 Common pop up message ............................................................................................................................. 90 SQL Server Installation Center ....................................................................................................................... 91 Global Rules ................................................................................................................................................... 92 SQL Server Installation Center ....................................................................................................................... 95 Installation ..................................................................................................................................................... 96 License Terms ................................................................................................................................................ 97 Product Updates ............................................................................................................................................ 98 Install Rules ................................................................................................................................................... 99 Feature Selection......................................................................................................................................... 101 Instance Configuration ................................................................................................................................ 102 Server Configuration ................................................................................................................................... 103 Database Engine Configuration ................................................................................................................... 104 Installation Progress .................................................................................................................................... 108 Completing Microsoft SQL Server 2014 Setup ............................................................................................ 109 Important .................................................................................................................................................... 110

Start Laura ...................................................................................................................................... 118 Select Database ........................................................................................................................................... 118 No Database found ...................................................................................................................................... 119 Create Database .......................................................................................................................................... 120 Following successful database creation ...................................................................................................... 121

APPENDIX F: REG FILES ............................................................................................................... 122 Create a .Reg File with Notepad.exe ........................................................................................................... 122 Create a .Reg File with Registry Export ....................................................................................................... 122 Edit a .Reg File ............................................................................................................................................. 122 Syntax of .Reg Files ...................................................................................................................................... 122 Deleting Registry Keys and Values .............................................................................................................. 123 Run .Reg file ................................................................................................................................................. 124


Page 4 of 124


Introduction

This document provides information for installing Laura. It is strongly recommended that;

• You do not change the steps in this document, nor their order. Often a seemingly trivial change can make a large difference to the success of the installation. Should you encounter difficulties, it will be much easier for technical support staff to aid you if you have followed the guide exactly.

• If you do make any changes to the steps in the Guide (e.g. changes to scripts, object naming etc) carefully note down exactly what you do. If you encounter difficulties with the installation having not followed the guide exactly, technical support will expect to know precise details of changes you have made; if you fail to provide these details, you may be charged for technical support of your installation.

• You perform a full backup of the machine configuration before you begin; LabLogic do not accept

responsibility for loss of, or damage to, data on client or server. • You keep this document for reference after the installation of Laura. • You login to Windows as an Administrator to do the installation and initially start the application. Other user

accounts may not have sufficient privileges to install the dongle drivers, HPLC drivers, update the registry with your database selection and register the Debra link, if required.

• Laura 4.2 is installed on workstations/servers utilising the Windows XP, Windows Server 2003, Windows

Server 2008, Windows Vista, Windows 7 (32‐bit or 64‐bit) or Windows 8 (32‐bit or 64‐bit) operating systems. However, please not that the database you will use may further restrict the selected operating system e.g. MSSQL Express 2012 and later will not support older version of Windows.

• When connecting to a Waters Acquity system, install the Waters drivers, following the Waters documentation.

Ensure that the Acquity system is recognised by the Acquity Console program, before attempting to connect to the system through Laura.

• If using Oracle or MSSQL as the database, it is recommended that the database is prepared, ready for

connection, before running Laura for the first time. Please read and follow the relevant Appendix at the end of this guide.

• In order to diagnose instrument problems, you may be asked to configure Laura to record information to LOG

files whilst it is running. Some anti‐virus software has been found to scan these *.LOG files which can severely slow down the PC and potentially cause communication errors. To avoid this issue, we recommend that you exclude *.LOG files from the on‐access scan in your anti‐virus software.


Page 5 of 124


Database Options

All installations of Laura need a database. Laura has the facility to attach to an Oracle, MSSQL2012 or MSSQL2014 database.

There are 2 modes when creating the database. Laura supports the following database modes:

Database

This means that the following data is stored in the database:

• System Configuration

• Workstation Configuration

• User Security

• Audit Trail

• Electronic Signatures

• Document Management

• Measurements

• Evaluations

• Methods

• Report Templates

• Gradients

• Pump Calibration

This provides the following advantages over Files' mode:

• Controlled access to the data ‐ files cannot be accidentally or deliberately modified outside of Laura. All the security of your Oracle or MSSQL database protects your data.

• Security access is controlled on a per project basis instead of system wide. So you can specify which users can access which projects and what their security level is within each project.

• Closer links between Debra and Laura. With the link enabled you can simply open a Debra project from Laura and a corresponding project is seamlessly created for you ready for your HPLC batches.

• When used in conjunction with a client/server database the performance of the system is increased.

• Everything is stored in the database which simplifies your backup/restore strategy.

For all GLP environments LabLogic recommends using the Database mode.

Note: To run in Database mode, your license will need to include this option. If in doubt, contact LabLogic support.


Page 6 of 124


Files

This means that the following data is stored in the database:

• System Configuration

• Workstation Configuration

• User Security

• Audit Trail

• Electronic Signatures

• Document Management

And the following data is stored in files:

• Measurements

• Evaluations

• Methods

• Report Templates

• Gradients

• Pump Calibration

These files can be configured to be stored locally on each PC or on a networked drive. Each project has its own folder which contains its methods, measurements and evaluations. This was the only option in earlier versions of Laura 3.0 and 3.1 and is provided mainly for backward compatibility purposes.


Page 7 of 124


Next you need to decide which database you want to use with Laura. The following database options are currently available for use with Laura:

• Oracle Client/Server database (Oracle)

This database is a client/server database and is suitable for any number of networked PCs. You will require suitable licenses for using Oracle, which your company may already have in place. LabLogic is an Oracle Partner and can provide you with suitable licenses. These licenses are in addition to the Laura purchase price. Advice on installing Oracle for use with Laura is included in Appendix C on page 46.

• MS SQL Client/Server database (MSSQL2012, MSSQL2014 or MSSQL2008)

This database is a client/server database and is suitable for any number of networked PCs. You will require suitable licenses for using MSSQL, which your company may already have in place.

• MS Database Engine (MSSQL2012 Express, MSSQL2014 Express or MSSQL2008 Express)

This database is a cut down version of MS SQL Server. It has been restricted so that there is a noticeable performance drop if there are more than 5 concurrent users. The advantage over MSSQL is that there are no licensing costs. Advice on installing MSSQL2012Express is included in Appendix D on page 57 and for MSSQL2014Express is included in Appendix E on page 88.

For small (5 users) installs LabLogic recommends using either Oracle or one of the MSSQL options as your database. This choice is normally made by your sites Database Administrator.


Page 8 of 124


Depending on your decision on how you want to setup the database, see the following section of the installation guide as applicable.

• Single‐User Install If you want to run Laura as a standalone system on one PC, using MSSQL2012 EXPRESS, MSSQL2014 EXPRESS or MSSQL2008 EXPRESS.

• Multi‐User Install If you want to run Laura on a small number of PCs using MSSQL2012 EXPRESS, MSSQL2014 EXPRESS or MSSQL2008 Express as the database option. The application can also be shared.

• Client/Server Install If you want to run Laura on a larger number of PCs using Oracle, MSSQL2012, MSSQL2014 or MSSQL2008. The application can also be shared.

If you choose one method of installation and later change your mind, you will need to access Laura as a user who has rights to access the Tools | Options | Database tab and/or Folders tab to amend the database or data drive settings, as required.


Page 9 of 124


Installation of the Application

The process of installing the Laura application is identical for any option or setup. The Laura application install is available for download from your account on the www.Lablogic.com web page. If you need to be provided with a user account to access to download the Laura install, contact [email protected], giving details of the program you require, company name and any other pertinent details.

The product area will contain a number of files;

i) Software release notes.

ii) The Laura setup program.

iii) The latest User Guide.

Note: Do not insert the dongle prior to installing the software.


Page 10 of 124


Laura install

Locate your download of the setup file and run it ‘as administrator’ e.g. Laura4.2.11.127Setup. This will start the Laura setup program.

A number of command line parameters are available for the Setup program. These are detailed in Appendix B on page 44.

Note: It is essential to run the install ‘as administrator’. This means performing a right click on the setup program and selecting ‘run as administrator’.


Page 11 of 124


Install process

On each screen, press the Next button to move to the next page. Pressing the Cancel button will abort the installation. If the Back button is available, pressing it will take you back to the previous screen.

Welcome Dialog


Page 12 of 124


Select Destination Location dialog

Here you set the required location of the installation. The selected folder will be the destination for both the application files and data files.

Note: If the application and/or data are to be shared from a network drive, install Laura on the shared drive first. Each workstation will then need only a reduced local installation, selecting appropriate options from the Select Components page.

Single user setup

For a single user, local installation, the folder will be on a local drive and can be left with the default setting.

Multi user setup

Local application file As with the single user setup, the default settings are set to a standard location. Change this location if desired.

Shared network application file If you are sharing the program file, you will not need to select the Application files needed to run the application option from the Select Components page. Select other options as required.

Laura may be started from a shortcut to the shared network application file. Create the shortcut in the usual way. Even when running a network copy of the application, each workstation will need to be licensed appropriately.


Page 13 of 124


Select Components dialog

The install process will check the version of the relevant files for the selected areas and only replace files, if the currently installed version is older than the one that is integral to the installer. See Appendix A (page 28) for details of the files installed for each option. For a standard install, the default checkbox selections can be accepted.

The full list of options, and their default status, are;

Component Default checkbox status

Support files needed to run the application Selected

Application files to run ‘Laura’ single‐instrument PCs (default) Selected

Application files to run ‘Laura for GC’ ( for multi‐instrument PCs only)

Application files to run ‘Laura for MCA’ ( for multi‐instrument PCs only)

Application files to run ‘Laura for TLC’ ( for multi‐instrument PCs only)

Application files to run ‘Laura for HPLC’ ( for multi‐instrument PCs only)

Borland Database Engine (Paradox)

Microsoft SQL 2008 Native Client

Microsoft SQL 2012/2014 Native Client Selected

Drivers for using Sentinel dongles Selected

Drivers for using FTDI chipset based USB devices Selected

Example Measurement Files Selected

Utilities to diagnose dongle problems and database errors Selected

Shimadzu drivers for Nexera, Prominence and VP‐series

Demonstrates how to use the Laura‐Excel link Selected

Note1: For many systems you must be logged in as an Administrator for the Dongle drivers and Shimadzu drivers to be installed and registered correctly.

Note2: The Drivers for using FTDI chipset based USB devices option needs to be selected if the installation will be connecting to a LabLogic; B‐RAM model 5, Scan‐RAM, Flow‐RAM or Pearl interface.

Note3: The Shimadzu drivers are not installed by default. Before installing these drivers ensure that no other program needs them e.g. Xcalibur.

Note4: If the system is also intended to run any other program that uses the Borland Database Engine, do not install these drivers e.g TopCount.


Page 14 of 124


Select Start Menu Folder dialog

Here you can set or select the folder from which the program shortcut will be available when you select Start | Programs.


Page 15 of 124


Ready to Install dialog

This dialog gives you the final opportunity to check your selections before commencing with the install or cancel the installation.


Page 16 of 124


Copying files process

As the Laura install process copies files onto the pc, the dialog, similar to the following example, will show the progress of the installation. For information on the files that are copied etc, see Appendix A on page 30.


Page 17 of 124


Setup Complete dialog

After Laura has been installed press the Finish button to leave the setup program. If you want the setup to launch the program, ensure that you select the Launch application checkbox, before pressing the Finish button.

Please note that if you select the Launch application radio button, before you press the Finish button, ensure that the instruments are connected, turned on and that the appropriate drivers have been successfully installed. Furthermore, ensure that the dongle has been inserted and the drivers have been successfully installed.


Page 18 of 124


Upgrading From Earlier Versions

Upgrading Laura from earlier versions follows the same procedures as an installation. After selecting the equivalent settings as your original installation, the setup program will continue to replace the installed files with the latest versions. Should there be any changes to the database, Laura will execute the appropriate actions when Laura is run for the first time after the update. Any existing data should be unaffected by the changes made during this process unless a Software Release Note details a specific change.

Note: Please check the supplied Software Release Notes for changes made prior to starting the upgrade process. The Software Release Notes will help in fulfilling your Change Control process, if appropriate.

All installations need a basic database as a minimum. This means that users who are upgrading from Laura Lite will now have to select an appropriate database. If you are unsure of which choice to make, please contact LabLogic support.

Note: It is not possible at this time to automatically change the selected database mode from Files mode to Database mode or vice versa.


Page 19 of 124


Connecting a LabLogic USB instrument

For customers who will be attaching a; B‐RAM, Flow‐RAM, Scan‐RAM or Pearl Interface that uses a USB connector, the drivers will need to be installed prior to running Laura. Please note that the drivers will need installing on all workstations that connect to a LabLogic instrument that is connected to the workstation via a USB cable. If the Drivers for using FTDI chipset based USB devices option is selected on the Select Components page of the install, the drivers should be already installed ready for the individual instrument installation. Simply power up the instrument and plug in the USB cable. The system tray will indicate that a new instrument has been found and install the drivers. Wait until the process indicates that it is ready for use.

For workstations that will connect to multiple USB based instruments, all instruments need to be connected with drivers successfully installed prior to running Laura.

Connecting the license dongle

After installing the Laura software, insert the dongle into an available USB port before running Laura.

Note: For many systems you must have been logged in as an Administrator for the Dongle drivers to be installed and registered correctly.

On inserting the dongle, the pc will indicate that the drivers are being installed. It takes a couple of seconds for the dongle driver install to complete. A message will briefly appear around the System Tray stating the dongle drivers were installed successfully.

On startup, Laura will check to see if you have a valid dongle fitted or have entered a valid activation code.


Page 20 of 124


Launching the Laura application

Ensure you have already inserted the license dongle and that the LabLogic USB based instrument, if appropriate, is connected. The FTDI drivers for the LabLogic USB based instrument must be installed before running Laura. If you did not set the installation to launch the application file, or if you are launching Laura at a later time, you will need to click on Start | Programs | LabLogic | Laura.

Note: If you set the install to use a different location, you will need to follow your own set path.

On first using Laura, you will be prompted to create a database, presenting the Select Database dialog, where you select the required database.

Note: It is essential to run the program for the first time ‘as administrator’. This means performing a right click on the program and selecting ‘run as administrator’.

Important Note: Please download and read the relevant install guide for the database to be used, before attempting to connect to a database. This may avoid common errors.


Page 21 of 124


Oracle Client/Server Install

Your Oracle DBA or system manager will need to be involved in this process. Please ensure you have read and understood the Laura Oracle Installation Guide, Appendix C on page 46.

You should select the Client/Server database (Oracle – for larger installations) item in the Type drop down list and enter the required service name in the Server Name field. It is important to have the correct format for the Server Name entry, of the Oracle service to which you want to connect.

Make default for all users

This is generally a ‘set once’ option. With the introduction of Windows 7, security and access to folders changed. Selecting this checkbox makes it possible for all users, who log into Laura on the current pc, to connect to the selected database, by default.

You must be logged into the pc as an administrator, and run the Laura application as administrator, to be able to set this option.

Click the OK button to continue starting Laura.

Oracle Server with no Laura tablespaces

If Laura can attach to the Oracle database, but cannot find the named account then it will offer to create the necessary tablespaces for you with the following dialog.


Page 22 of 124


Pressing the Yes button will present a further dialog for completion.

The Data Mode can be set to either Database or Files. You MUST be licensed for Database mode in order to use it. With a valid license dongle attached, the field should automatically contain the relevant mode for your installation.

Database – with this option, the database is used for storing everything and gives enhanced security through per project security levels. You MUST be licensed for Database mode in order to use it.

Files – with this option, the database is used for storing security information, audit trail, electronic signatures and document management and files are used for storage of evaluations, gradients, methods, measurements, report templates and pump gradients.

You will need to enter a Server Database Folder. Note that this path will be the path from the Oracle server’s perspective, which will probably not be the same as the machine you’re using at the time.

Note: Pressing the button on the right of the Server Database Folder field will explore the local machine and not the server.

You will also need to enter the appropriate combination, as set by the DBA, for the Username and Password. Having made the required entries, Oracle will be able to create the tablespaces required by Laura.


Page 23 of 124


You can choose to let Laura create the tablespaces by clicking the Create button.

Alternatively you can use the Save SQL button to create the required SQL script. Having created and saved the script, start SQLPLUS as system/manager and execute the script file.

Once the tables have been successfully created, you will be ready to start using Laura.

Note: Please read the advice in the Introduction section on page 4.

Networked Data Files for Files mode installation

If you also want to store your data files on the network, sign into Laura as a user who has access to the Tools | Options menu option, selecting the Folders tab. Set the Default Data Folder field entry to the required area.

Note: If using a network path, Laura will perform better if you set the directory to a mapped network drive rather than using an UNC path.


Page 24 of 124


MSSQL201x Server Client/Server Install

Your MS SQL DBA or system manager will need to be involved in this process. This process may be followed for an MSSQL2012 or MSSQL2014 installation. Please ensure you have read and understood the recommended Laura MSSQL 2012 Express Installation Guide Appendix D on page 57, Laura MSSQL 2014 Express Installation Guide Appendix E on page 88.

You should select the appropriate Client/Server database (MSSQL201x – for most installations) item in the Type drop down list and enter the required server name in the Server Name field.

The Server Name field is expecting an entry in the format;

{server name}\{instance name}

e.g. WINDOWS7TEST\LAURADB

If the instance is omitted, as in the example dialog above, on pressing the OK button, the system will suggest the use of a default name.


Page 25 of 124


Make default for all users This is generally a ‘set once’ option. With the introduction of Windows 7, security and access to folders changed. Selecting this checkbox makes it possible for all users, who log into Laura on the current pc, to connect to the selected database, by default.

You must be logged into the pc as an administrator, and run the Laura application as administrator, to be able to set this option.

Once all fields are complete, click the OK button to continue starting Laura.

MS SQL Server with no Laura database

If Laura can attach to the MS SQL database, but cannot find the named account then it will offer to create the necessary database for you with the following dialog.

Pressing the Yes button will present a further dialog for completion.


Page 26 of 124


The Data Mode can be set to either Database or Files. You MUST be licensed for Database mode in order to use it. With a valid license dongle attached, the field should automatically contain the relevant mode for your installation.

Database – with this option, the database is used for storing everything and gives enhanced security through per project security levels. You MUST be licensed for Database mode in order to use it.

Files – with this option, the database is used for storing security information, audit trail, electronic signatures and document management and files are used for storage of evaluations, gradients, methods, measurements, report templates and pump gradients.

You will need to enter a Server Database Folder. Note that this path will be the path from the MS SQL server’s perspective, which will probably not be the same as the machine you’re using at the time.

Note: Pressing the button on the right of the Server Database Folder field will explore the local machine and not the server.

You will also need to enter the appropriate combination, as set by the DBA, for the Username and Password. Having made the required entries, MS SQL will be able to create the database required by Laura.

You can choose to let Laura create the tablespaces by clicking the Create button.

Alternatively you can use the Save SQL button to create the required SQL script. Having created and saved the script, start OSQL as SA and execute the script file.

Once the tables have been successfully created, you will be ready to start using Laura.

Note: Please read the advice in the Introduction section on page 4.

Networked Data Files

If you also want to store your data files on the network, sign into Laura as a user who has access to the Tools | Options menu option, selecting the Folders tab. Set the Default Data Folder field entry to the required area.

Note: If using a network path, Laura will perform better if you set the directory to a mapped network drive rather than using an UNC path.


Page 27 of 124


Summary ‐ After the Install Of Laura

Once you have installed Laura check the following points:

• If you have purchased Laura, make sure that the dongle (or security key) has been plugged into the USB port or printer (LPT) port (for older installations only) of your workstation. Laura will look for this to make sure you have a licensed version of the system ‐ if you experience any problems with this please contact your vendor.

• Ensure all the detectors and instruments to be controlled by Laura are attached, switched on and the drivers, if required, have been successfully installed.

• Start the Laura Package

• On the first connection of Laura, connect to the required database. If this is the first workstation to connect to the database the tablespaces will need to be created (unless created separately).

• On starting Laura (without a dongle) you will be presented with the dialog below, choose the I have been unable to contact my supplier… option if you want to evaluate Laura for 14 days, if you have an activation code click on I have contacted my supplier and this is the activation code and then type or paste the code in the box provided. Press the Continue button.

• If you are evaluating Laura for demonstration purposes, or are awaiting a license, you may use Laura for 14 days from the installation date. After the 14 days grace period, Laura will prevent any access to the software. In order to gain access to the software, you will need to acquire a license dongle.


Page 28 of 124


Note: During the grace period Laura will provide access to all areas of the software. When you start using the software with an acquired dongle/license only the licensed option will be available. If you need further advice on available licensed options please contact your vendor.

• On first starting up the software, Laura will first go through the Instrument Setup wizard that leads you through the necessary steps to configure the instrument attached to the Laura workstation. Please make sure that the instrument is on and follow the instructions on each dialog. You may leave this until later, if desired by clicking the Cancel button. The Instrument setup wizard is described in the Laura User Guide.

• On completion of the instrument detection, you will be presented with the Laura Login Dialog. The default user setup within the system is:

Login ID: A.USER

Note: there are no spaces in this name and there is a dot/period/full stop between "A" and "U"

Password: SECRET

Note: A password is only required if the installation is licensed for Passwords.

You may change the users' name and password within the Laura system, please consult your Laura User Guide for details.


Page 29 of 124


Windows security and folder access

With the introduction of Windows 7, security and access to folders changed. As you have installed Laura as an administrator, other users, who are not administrators, may not have read and write access to key folders used by Laura. It is important that users are given read and write access to these folders before they first log onto the pc and run Laura. The affected folders can be found on the Options dialog, which is accessed from the Tools | Options menu path. These settings are in addition to the optional checkbox on the Select Database dialog.

For all installations

Log Files Folder – on the System page.

Note: this field may be blank, which then defaults to storing the log files in the currently logged in users documents folder, to which they have automatic access.

Network Recovery Folder – on the Measurements page.

Folder – on the Database page.

Note: This entry is only relevant for an older Paradox installation.

Files mode installation

All entries on the Folders page.

Setting the access rights

1. Log. onto the pc as an administrator. 2. Open your Windows Explorer. 3. Navigate to the first folder relevant to your configuration. 4. Right‐click the folder and click Properties then select the Security tab. 5. Select a security group for which all Laura users are a member ‐ for example ‘Users’. 6. Select the Full Control box and click OK to save the changes. 7. Repeat steps 3 to 6 for each relevant folder.


Page 30 of 124


APPENDIX A: FILES THAT LAURA INSTALLS OR MODIFIES ON A CLIENT MACHINE

At the end of the installation process, the following changes will have been made to the client machine, for the selections made during the installation (page 13):

Support files needed to run the application

This option installs the support files and these are installed into the Laura folder. By default this is “C:\Program Files\Lablogic\Laura” – but it can be altered during the installation process. This will contain the Laura application and support files.

kl2dll32.dll Laura.chm LauraCOM.ocx NetCDF.dll VerifyKey.exe

Application files needed to run ‘Laura’ on single‐instrument PC’s (default)

The following files comprise the Laura application and its support files and these are installed into the Laura folder. By default this is “C:\Program Files\Lablogic\Laura” – but it can be altered during the installation process. This will contain the Laura application and support files.

Laura.exe DMS.dot Unins000.dat Unins000.exe Application files needed to run ‘Laura for GC’ (for multi‐instrument PC’s only)

The following file is installed into the Laura folder. By default this is “C:\Program Files\Lablogic\Laura” – but it can be altered during the installation process. This will contain an extra copy of the Laura application that would be used when multiple installs are required on one pc, attached to different instruments. This copy of the application would have a shortcut created for GC.

Laura1.exe

Application files needed to run ‘Laura for MCA’ (for multi‐instrument PC’s only)

The following file is installed into the Laura folder. By default this is “C:\Program Files\Lablogic\Laura” – but it can be altered during the installation process. This will contain an extra copy of the Laura application that would be used when multiple installs are required on one pc, attached to different instruments. This copy of the application would have a shortcut created for MCA.

Laura2.exe


Page 31 of 124


Application files needed to run ‘Laura for TLC’ (for multi‐instrument PC’s only)

The following file is installed into the Laura folder. By default this is “C:\Program Files\Lablogic\Laura” – but it can be altered during the installation process. This will contain an extra copy of the Laura application that would be used when multiple installs are required on one pc, attached to different instruments. This copy of the application would have a shortcut created for TLC.

Laura3.exe

Application files needed to run ‘Laura for HPLC’ (for multi‐instrument PC’s only)

The following file is installed into the Laura folder. By default this is “C:\Program Files\Lablogic\Laura” – but it can be altered during the installation process. This will contain an extra copy of the Laura application that would be used when multiple installs are required on one pc, attached to different instruments. This copy of the application would have a shortcut created for HPLC.

Laura4.exe

Borland Database Engine

This is included only for older systems and no longer generally used. The following Borland Database Engine and SQL Links files will have been installed into the “\Program Files\Common files\Borland Shared\BDE” folder:

bantam.dll bdeadmin.cnt bdeadmin.exe bdeadmin.hlp bdeadmin.toc blw32.dll ceeurope.btl charset.cvb europe.btl fareast.btl Idapi.cnf idapi32.dll idapinst.dll idasci32.dll idbat32.dll idda3532.dll iddbas32.dll iddr32.dll idodbc32.dll idpdx32.dll idqbe32.dll idr20009.dll idsql32.dll japan.btl other.btl


Page 32 of 124


SQL_DB2 (.CNF) SQL_DBv5 (.CNF) SQL_INF (.CNF) SQL_INF9 (.CNF) SQL_MSS (.CNF) SQL_ORA (.CNF) SQL_ORA8 (.CNF) SQL_SSC (.CNF) SQL_SYB (.CNF) sqldb2v5.dll sqldb232.dll sqlinf9.dll sqlinf32.dll sqllnk32.cnt sqllnk32.hlp sqllnk32.toc sqlmss32.dll sqlora8.dll sqlora32.dll sqlssc32.dll sqlsyb32.dll usa.btl The following file is used temporarily during the installation.

idapi32.cnf

Microsoft SQL 2008 Native Client

When using a networked MSSQL 2008 database, the local pc only needs the native client to be installed. This option will run and register the selected version of the sqlncli.msi file, leaving nothing on the local pc. (Generally you would not install both clients; 2008 and 2012/2014)

Microsoft SQL 2012/2014 Native Client

When using a networked MSSQL 2012 or MSSQL 2014database, the local pc only needs the native client to be installed. This option will run and register the selected version of the sqlncli.msi file, leaving nothing on the local pc. (Generally you would not install both clients; 2008 and 2012/2014)

Drivers for using Sentinel dongles

The following Sentinel driver files will have been installed into the “\Program Files\Common files\SafeNet Sentinel\Sentinel System Driver” folder:

Windows XP, Vista and Windows 7 and 8 (32‐bit)

Drv32InstLauncher.exe InstAndStartNTParService.exe Vista and Windows 7(32-bit)only InstAndStartNTParService.exe.manifest Vista and Windows 7(32-bit)only


Page 33 of 124


InstParLauncher.exe Vista and Windows 7(32-bit)only RemoveDriverTrail.exe RemoveDriverTrail.exe.manifest Vista and Windows 7(32-bit)only RemoveDriverTrailLauncher.exe SentinelDrv32Support.exe SentinelDrv32Support.exe.manifest Vista and Windows 7(32-bit)only SetupSysDriver.exe SetupSysDriver.exe.manifest Vista and Windows 7(32-bit)only sntnlusb.cat sntnlusb.inf sntnlusb.sys sysdriver.guid X86DIFxAPI.dll Window 7 and 8 (64‐bit)

DIFxAPI.dll Drv32InstLauncher.exe Drv32InstLauncher.exe.manifest Sentinel.chm Sentinel64.cat Sentinel64.sys SentinelDriverInstallSupport.exe SetupSysDriver.exe SetupSysDriver.exe.manifest Snti386.dll Sntusb64.cat SNTUSB64.inf Sntusb64.sys sysdriver.guid Drivers for using FTDI chipset based USB devices

By default these files are copied into the USB Drivers folder from “C:\Program Files\Lablogic\Laura” unless it was altered during the installation process.

amd64\ftbusui.dll amd64\ftcserco.dll amd64\ftd2xx64.dll amd64\ftd2xx.lib amd64\ftdibus.sys amd64\ftlang.dll amd64\ftser2k.sys amd64\ftserui2.dll i386\ftbusui.dll i386\ftcserco.dll i386\ftd2xx.dll i386\ftd2xx.lib i386\ftdibus.sys


Page 34 of 124


i386\ftlang.dll i386\ftser2k.sys i386\ftserui2.dll DPInst.exe DPInst.xml Ftd2xx.h Ftdibus.cat Ftdibus.inf Ftdiport.cat Ftdiport.inf

Example Measurement Files

By default these files are copied into the directory from “C:\Program Files\Lablogic\Laura” unless it was altered during the installation process.

Note: In a Database mode installation these files are only present before Laura is run. Once Laura is run the data is imported into the database and these files are deleted from the workstation that first ran Laura. Other workstations may still have the data available.

Data\Sample Data\032898.Measurement Data\Sample Data\091198.Measurement Data\Sample Data\101397A.Measurement Data\Sample Data\3D View.Measurement Data\Sample Data\500 cell.Evaluation Data\Sample Data\1000 cell.Evaluation Data\Sample Data\ABC2.Measurement Data\Sample Data\C-14 Spectrum.Spectrum Data\Sample Data\Cs-137 Spectrum.Spectrum Data\Sample Data\D6254_23.Measurement Data\Sample Data\Dual Label C14 Standard.Measurement Data\Sample Data\Dual Label H3 Standard.Measurement Data\Sample Data\EG1.Measurement Data\Sample Data\Example1.Measurement Data\Sample Data\Example2.Measurement Data\Sample Data\Example3.Measurement Data\Sample Data\Isol1.Measurement Data\Sample Data\Isol2.Measurement Data\Sample Data\Isol3.Measurement Data\Sample Data\Isol4.Measurement Data\Sample Data\Isol5.Measurement Data\Sample Data\Isol6.Measurement Data\Sample Data\Linearity Test.Evaluation Data\Sample Data\PETra GC Demo.Evaluation Data\Sample Data\PETra TLC Demo.Evaluation Data\Sample Data\Purity.Measurement Data\Sample Data\Run0025.Measurement Data\Sample Data\Run0045.Measurement Data\Sample Data\Serstab1.Measurement


Page 35 of 124


Data\Sample Data\Silica Autoradiograph.Measurement Data\Sample Data\SoFie NonStop Run 1.Evaluation Data\Sample Data\SoFie Stop Flow Run 1.Evaluation Data\Sample Data\Summary Demo.Measurement Data\Sample Data\TLC Calcs.Evaluation

Utilities to diagnose dongle problems and database errors

This directory contains utilities that may be required to read the information from the dongle or analyse Paradox tables. By default these files are copied into the folder from “C:\Program Files\Lablogic\Laura” unless it was altered during the installation process.

Diagnostics\DongleInfo.exe Diagnostics\kl2dll32.dll Diagnostics\Rebuild.exe Diagnostics\Tutil32.dll

Shimadzu drivers for Nexera, Prominence and VP‐series

The following files are installed for control of the Shimadzu HPLC system. By default these files are copied into the Shimadzu folder from “C:\Program Files\Lablogic\Laura” unless it was altered during the installation process. Please note that the Shimadzu drivers are not supported in Windows 8.

@CHKDT.LC Cbm2.ocx LCIpAddressList.dll Rsprot32.dll ShimLCCONFIG.dll ShimLCController.exe ShimLCMethod.dll ShimLCSetup.dll ShimLCStatus.ocx Spdmxa.ocx SWDEditU.dll SwdgraphU.dll SWDLCControl_DUALU.dll VIUtlu.dll Vsflex8u.ocx Vsstr8.ocx WSAProt32.dll One file is copied to the C:\Windows folder

CBMOCX.ini


Page 36 of 124


Demonstrates how to use the Laura‐Excel link

By default these files are copied into the Excel from “C:\Program Files\Lablogic\Laura” unless it was altered during the installation process.

Laura COM Excel Demonstration 2.xls Laura COM Excel Demonstration.xls

Files created for a Paradox database (Borland Database Engine), post installation

If you have selected to install the files to the default location, these files will be created in the “C:\Documents and Settings\All Users\Application Data\Laura\System\” folder or the hidden “C;ProgramData\Laura\System\” folder.

AcquityPlates.DB AcquityPlates.PX AcquityPlates.XG0 AcquityPlates.XG1 AcquityPlates.YG0 AcquityPlates.YG1 AlliancePlates.DB AlliancePlates.PX AlliancePlates.XG0 AlliancePlates.XG1 AlliancePlates.YG0 AlliancePlates.YG1 AuditReasons.DB AuditReasons.PX AuditReasons.XG0 AuditReasons.XG1 AuditReasons.XG2 AuditReasons.XG3 AuditReasons.XG4 AuditReasons.YG0 AuditReasons.YG1 AuditReasons.YG2 AuditReasons.YG3 AuditReasons.YG4 AuditX.DB AuditX.PX AuditX.XG0 AuditX.XG1 AuditX.YG0 AuditX.YG1 BatchHistory2.DB Database Mode Only BatchHistory2.MB Database Mode Only BatchHistory2.PX Database Mode Only BatchHistory2.XG0 Database Mode Only BatchHistory2.XG1 Database Mode Only BatchHistory2.XG2 Database Mode Only


Page 37 of 124


BatchHistory2.XG3 Database Mode Only BatchHistory2.XG4 Database Mode Only BatchHistory2.XG5 Database Mode Only BatchHistory2.YGO Database Mode Only BatchHistory2.YG1 Database Mode Only BatchHistory2.YG2 Database Mode Only BatchHistory2.YG3 Database Mode Only BatchHistory2.YG4 Database Mode Only BatchHistory2.YG5 Database Mode Only CellTypes.DB CellTypes.PX Chromatograms.DB Database Mode Only Chromatograms.MB Database Mode Only Chromatograms.PX Database Mode Only Chromatograms.XG0 Database Mode Only Chromatograms.XG1 Database Mode Only Chromatograms.XG2 Database Mode Only Chromatograms.XG3 Database Mode Only Chromatograms.XG4 Database Mode Only Chromatograms.XG5 Database Mode Only Chromatograms.XG6 Database Mode Only Chromatograms.YG0 Database Mode Only Chromatograms.YG1 Database Mode Only Chromatograms.YG2 Database Mode Only Chromatograms.YG3 Database Mode Only Chromatograms.YG4 Database Mode Only Chromatograms.YG5 Database Mode Only Chromatograms.YG6 Database Mode Only ColumnNames.DB ColumnNames.PX Components.DB Database Mode Only Components.MB Database Mode Only Components.PX Database Mode Only Components.XG0 Database Mode Only Components.XG1 Database Mode Only Components.XG2 Database Mode Only Components.XG3 Database Mode Only Components.XG4 Database Mode Only Components.XG5 Database Mode Only Components.XG6 Database Mode Only Components.YG0 Database Mode Only Components.YG1 Database Mode Only Components.YG2 Database Mode Only Components.YG3 Database Mode Only Components.YG4 Database Mode Only Components.YG5 Database Mode Only Components.YG6 Database Mode Only CustomFields.DB Database Mode Only CustomFields.PX Database Mode Only DMS.DB


Page 38 of 124


DMS.MB DMS.PX DMS.XG0 DMS.XG1 DMS.XG2 DMS.XG3 DMS.YG0 DMS.YG1 DMS.YG2 DMS.YG3 DPDEFAULTS.DB DPDEFAULTS.PX ESigOptions.DB ESigOptions.PX ESigs.DB ESigs.PX ESigs.XG0 ESigs.XG1 ESigs.XG2 ESigs.XG3 ESigs.XG4 ESigs.XG5 ESigs.XG6 ESigs.XG7 ESigs.YG0 ESigs.YG1 ESigs.YG2 ESigs.YG3 ESigs.YG4 ESigs.YG5 ESigs.YG6 ESigs.YG7 ESigTypes.DB ESigTypes.PX ESigTypes.XG0 ESigTypes.YG0 FileLocking.DB FileLocking.PX Folders.DB Folders.PX Gradient.DB Database Mode Only Gradient.MB Database Mode Only Gradient.PX Database Mode Only Gradient.XG0 Database Mode Only Gradient.XG1 Database Mode Only Gradient.XG2 Database Mode Only Gradient.XG3 Database Mode Only Gradient.XG4 Database Mode Only Gradient.XG5 Database Mode Only Gradient.XG6 Database Mode Only


Page 39 of 124


Gradient.YG0 Database Mode Only Gradient.YG1 Database Mode Only Gradient.YG2 Database Mode Only Gradient.YG3 Database Mode Only Gradient.YG4 Database Mode Only Gradient.YG5 Database Mode Only Gradient.YG6 Database Mode Only Instruments.DB Instruments.PX InstrumentStatus.DB InstrumentStatus.PX IPAResults.DB IPAResults.PX IPATestLimits.DB IPATestLimits.PX IPATestResults.DB IPATestResults.PX Isotopes.DB Isotopes.PX LSCFormats.DB LSCFormats.PX MCAConfig.DB MCAConfig.PX Meanings.DB Meanings.PX Method.DB Database Mode Only Method.MB Database Mode Only Method.PX Database Mode Only Method.XG0 Database Mode Only Method.XG1 Database Mode Only Method.XG2 Database Mode Only Method.XG3 Database Mode Only Method.XG4 Database Mode Only Method.XG5 Database Mode Only Method.XG6 Database Mode Only Method.YG0 Database Mode Only Method.YG1 Database Mode Only Method.YG2 Database Mode Only Method.YG3 Database Mode Only Method.YG4 Database Mode Only Method.YG5 Database Mode Only Method.YG6 Database Mode Only MethodComments.DB MethodComments.PX PDOXUSERS.NET Preferences.DB Preferences.PX Printers.DB Printers.PX Privilege.DB


Page 40 of 124


Privilege.PX Project.DB Database Mode Only Project.PX Database Mode Only Project.XG0 Database Mode Only Project.YG0 Database Mode Only Pump.DB Database Mode Only Pump.MB Database Mode Only Pump.PX Database Mode Only Pump.XG0 Database Mode Only Pump.XG1 Database Mode Only Pump.XG2 Database Mode Only Pump.XG3 Database Mode Only Pump.XG4 Database Mode Only Pump.XG5 Database Mode Only Pump.XG6 Database Mode Only Pump.YG0 Database Mode Only Pump.YG1 Database Mode Only Pump.YG2 Database Mode Only Pump.YG3 Database Mode Only Pump.YG4 Database Mode Only Pump.YG5 Database Mode Only Pump.YG6 Database Mode Only Quench.DB Database Mode Only Quench.MB Database Mode Only Quench.PX Database Mode Only Quench.XG0 Database Mode Only Quench.XG1 Database Mode Only Quench.XG2 Database Mode Only Quench.XG3 Database Mode Only Quench.XG4 Database Mode Only Quench.XG5 Database Mode Only Quench.XG6 Database Mode Only Quench.YG0 Database Mode Only Quench.YG1 Database Mode Only Quench.YG2 Database Mode Only Quench.YG3 Database Mode Only Quench.YG4 Database Mode Only Quench.YG5 Database Mode Only Quench.YG6 Database Mode Only Queue.DB Database Mode Only Queue.MB Database Mode Only Queue.PX Database Mode Only Queue.XG0 Database Mode Only Queue.XG1 Database Mode Only Queue.XG2 Database Mode Only Queue.XG3 Database Mode Only Queue.XG4 Database Mode Only Queue.XG5 Database Mode Only Queue.YG0 Database Mode Only Queue.YG1 Database Mode Only


Page 41 of 124


Queue.YG2 Database Mode Only Queue.YG3 Database Mode Only Queue.YG4 Database Mode Only Queue.YG5 Database Mode Only Reasons.DB Reasons.PX Report.DB Database Mode Only Report.MB Database Mode Only Report.PX Database Mode Only Report.XG0 Database Mode Only Report.XG1 Database Mode Only Report.XG2 Database Mode Only Report.XG3 Database Mode Only Report.XG4 Database Mode Only Report.XG5 Database Mode Only Report.XG6 Database Mode Only Report.YG0 Database Mode Only Report.YG1 Database Mode Only Report.YG2 Database Mode Only Report.YG3 Database Mode Only Report.YG4 Database Mode Only Report.YG5 Database Mode Only Report.YG6 Database Mode Only Samples.DB Database Mode Only Samples.MB Database Mode Only Samples.PX Database Mode Only Samples.XG0 Database Mode Only Samples.XG1 Database Mode Only Samples.XG2 Database Mode Only Samples.XG3 Database Mode Only Samples.XG4 Database Mode Only Samples.XG5 Database Mode Only Samples.XG6 Database Mode Only Samples.YG0 Database Mode Only Samples.YG1 Database Mode Only Samples.YG2 Database Mode Only Samples.YG3 Database Mode Only Samples.YG4 Database Mode Only Samples.YG5 Database Mode Only Samples.YG6 Database Mode Only ScanRamFlowRamCalibration.DB ScanRamFlowRamCalibration.PX ScanSpeeds.DB ScanSpeeds.PX SignatureReasons.DB SignatureReasons.PX Solvents.DB Solvents.PX StationaryPhase2.DB StationaryPhase2.PX


Page 42 of 124


StudUser.DB StudUser.PX SysPref.DB TableNext.DB TableNext.PX TableNext.XG0 TableNext.XG1 TableNext.YG0 TableNext.YG1 TTFKAL.DB TTFKAL.PX UserDefaults.DB UserDefaults.PX UserWorkstations.DB UserWorkstations.PX UserWorkstations.XG0 UserWorkstations.XG1 UserWorkstations.YG0 UserWorkstations.YG1 Usr.DB Usr.MB Usr.PX Usr.XG0 Usr.YG0 UsrActivity.DB Workstation.DB Workstation.PX WorkstationDefaults.DB WorkstationDefaults.PX WorkstationModules.DB WorkstationModules.PX

Registered files

The following files, found in the install folder for Laura 4, will be registered. The USB or Sentinel drivers are probably also registered, but we have no control over these installations.

All installations;

LauraCOM.ocx

Only when the Shimadzu drivers are installed;

Shimadzu\Rsprot32.dll Shimadzu\Cbm2.ocx Shimadzu\ShimLCStatus.ocx Shimadzu\Spdmxa.ocx Shimadzu\vsflex8u.ocx


Page 43 of 124


Shimadzu\vsstr8.ocx Shimadzu\WSAProt32.dll Only when an MSSQL native client is selected during the install;

Sqlncli.msi (the native client is registered, but the file is not saved)


Page 44 of 124


APPENDIX B: OPTIONAL SETUP PROGRAM PARAMETERS

The Setup program has a number of optional parameters that can be used during the installation. These may help with packaged installs used by a number of sites. It is likely that the parameters will only be used by System administrators / IT groups.

/SILENT, /VERYSILENT Instructs Setup to be silent or very silent. When Setup is silent the wizard and the background window are not displayed but the installation progress window is. When a setup is very silent this installation progress window is not displayed. Everything else is normal so for example error messages during installation are displayed.

If a restart is necessary and the '/NORESTART' command isn't used (see

below) and Setup is silent, it will display a Reboot now? message box. If it's very silent it will reboot without asking.

/SUPPRESSMSGBOXES Instructs Setup to suppress message boxes. Only has an effect when combined with '/SILENT' and '/VERYSILENT'.

The default response in situations where there is a choice is:

Yes in a 'Keep newer file?' situation. No in a 'File exists, confirm overwrite.' situation. Abort in Abort/Retry situations. Cancel in Retry/Cancel situations. Yes (=continue) in a DiskSpaceWarning/DirExists/DirDoesntExist/NoUninstallWarning/ExitSetupMessage/ConfirmUninstall situation. Yes (=restart) in a FinishedRestartMessage/UninstalledAndNeedsRestart situation.

5 message boxes are not suppressible:

The About Setup message box. The Exit Setup? message box. The FileNotInDir2 message box displayed when Setup requires a new disk to be inserted and the disk was not found. Any (error) message box displayed before Setup (or Uninstall) could read the command line parameters. Any message box displayed by [Code] support function MsgBox.

/LOG

Causes Setup to create a log file in the user's TEMP directory detailing file installation and [Run] actions taken during the installation process.


Page 45 of 124


This can be a helpful debugging aid. For example, if you suspect a file isn't being replaced when you believe it should be (or vice versa), the log file will tell you if the file was really skipped, and why.

The log file is created with a unique name based on the current date. (It will not overwrite or append to existing files.)

The information contained in the log file is technical in nature and therefore not intended to be understandable by end users. Nor is it designed to be machine‐parseable; the format of the file is subject to change without notice.

/LOG="filename"

Same as /LOG, except it allows you to specify a fixed path/filename to use for the log file. If a file with the specified name already exists it will be overwritten. If the file cannot be created, Setup will abort with an error message.

/NOCANCEL

Prevents the user from cancelling during the installation process, by disabling the Cancel button and ignoring clicks on the close button. Useful along with '/SILENT' or '/VERYSILENT'.

/DIR="x:\dirname"

Overrides the default directory name displayed on the Select Destination Location wizard page. A fully qualified pathname must be specified.

/GROUP="folder name"

Overrides the default folder name displayed on the Select Start Menu Folder wizard page. If the [Setup] section directive DisableProgramGroupPage was set to yes, this command line parameter is ignored.

/NOICONS

Instructs Setup to initially check the Don't create a Start Menu folder check box on the Select Start Menu Folder wizard page.

/COMPONENTS="comma separated list of component names"

Overrides the default components settings. Using this command line parameter causes Setup to automatically select a custom type.


Page 46 of 124


APPENDIX C : LAURA ORACLE INSTALLATION GUIDE

Introduction

This document provides information for installing the Oracle database for Laura. It is strongly recommended that:

• You call upon LabLogic’s experience and allow them to assist in the installation. LabLogic will be happy to help you this or any other installation of LabLogic software. Further, if you have any problems or queries regarding this document, contact LabLogic.

• You do not change the steps in this document, nor their order. Often a seemingly trivial change can make a large difference to the success of the installation. Should you encounter difficulties, it will be much easier for technical support staff to aid you if you have followed the guide exactly.

• If you do make any changes to the steps in the Guide (e.g. changes to scripts, object naming etc) carefully note down exactly what you do. If you encounter difficulties with the installation having not followed the guide exactly, LabLogic technical support will expect to know precise details of changes you have made; if you fail to provide these details, LabLogic will charge at the standard rate for technical support of your installation.

• You perform a full backup of the machine configuration before you begin; LabLogic do not accept responsibility for loss of, or damage to, data on client or server.

• You keep this document for reference after installation of Laura.

• Laura can use the same Oracle server as your Debra installation, but it needs its own schema. By default the user will be LAURA_SYSTEM and the tablespace LAURA_SYSTEM.


Page 47 of 124


Overview

Server

The steps below are performed once only, on the Oracle server. In order to carry out the server‐side installation, a high level of access to the Oracle database is required. It is recommended that this is discussed with the IT supervisor or DBA before the installation procedure begins.

• Create the Laura database on the Oracle server. • Create the Laura tablespace. • Create the Laura Oracle account (user). • Create the Laura tables.

Client

The steps below will need to be performed on each client on which you intend to run the Laura application.

• Verify that there is a working SQL*Net link from a client machine to the server. • Install the Oracle Client software on each PC

Location of Installation Files

The Oracle installation can be created after the installation of Laura by clicking the “Save SQL” button in Laura's “Create Database” dialog. Alternatively the script can be created sent to you on request to [email protected].


Page 48 of 124


Quick Installation Instructions

The simplest way to create the Oracle database is to allow Laura to create the database during initial setup.

Advanced Installation Instructions

Creation of the database

Creation and administration of an Oracle database is a very involved process, and one that LabLogic Systems do not formally support as far as Laura is concerned. If you are unsure of how to create an Oracle database, consult your Oracle documentation and/or your DBA.

However, the following guidelines for database parameters are offered:

• Character set (database creation): the character set of the database must be an ANSI character set. In particular, on some systems the default character set is US7ASCII—this will not work with Laura since Laura uses characters in the ANSI character set. A symptom of using the wrong character set is that Laura may display characters such as ‘µ’ incorrectly (eg. ‘?l‘ instead of ‘µl’). LabLogic has successfully used AL32UTF8 and WE8ISO8859PI.

Note: If you are considering a common Oracle database for any combination of Debra, Laura, Stacy, Jane and SeeScan tablespaces, it is important to note that the character set will also need to be common to all applications. Currently that will mean that the UTF8 family cannot be used and we advise an ANSI character set e.g. WE8ISO8859PI.

• MAXDATAFILES (database creation): if the database is to be used for Laura only, MAXDATAFILES should be at least 4 plus the number of datafiles you are specifying in the CREATE DATABASE command (to hold at least the system datafiles and one datafile for each of the initial Laura tablespaces). Increasing this value will allow for future expansion of the Laura database.

• SHARED_POOL_SIZE (instance start‐up): this should be set to as high a value as possible for optimum performance.

• Redo Log Files: you should have at least three redo log files.

• Rollback segments: if you wish Oracle to manage rollbacks, the Initialisation Parameter ‘Undo Management’ should be set to AUTO. Otherwise it should be set to MANUAL. If MANUAL is selected, the main consideration when determining the required number and size of rollback segments should be the number of users who will be using Laura concurrently. Also (if using MANUAL), once rollback segments have been established (by completing this installation), you will need to monitor them closely to find the optimum number and size.

• Other parameters (instance start‐up): you can affect a large gain in performance by tuning other parameters. Parameters you should pay particular attention to are DB_BLOCK_BUFFERS, SORT_AREA_SIZE and LOG_BUFFER

• Optimizer Mode: It has been noted in some situations that Optimizer Mode can affect the speed at which reports will be processed. It is recommended that this be set to ‘Choose’ mode. At the time of database creation, consideration should be given to how data backups will be performed. If you intend doing ‘hot’ backups, you will need to set up ARCHIVELOG mode for the database. If this is the case, then from a performance aspect it is of course much better to have your LOG_ARCHIVE_DEST (the destination for


Page 49 of 124


your archive log files) on a different physical disk from your data (which, in turn, should be on a physical disk other than the one your

Date post:	27-Jan-2021
Category:	Documents
Upload:	others
View:	0 times
Download:	0 times