Proval LS Database & Client Software (Trial or Full) Installation Guide

Transcription

1 Proval LS Database & Client Software (Trial or Full) Installation Guide Prerequisites: Technical Requirements SDS ProVal is an independent application and does not require Microsoft Office to run. It is written using the Microsoft.NET Framework and is designed for use with Windows XP Professional. It can be installed directly onto a PC, or delivered via a remote services tier, such as Citrix or Windows Terminal Services. The hardware quoted below is for operating systems that are loaded native on the "Tin". It is almost impossible for us (SDS) to tell you what the equivalent Virtualised computer network environment would perform the same as the hardware listed below. In this light we expect that you the IT professional, knowing your own systems would be a better judge within your own environment. Licensing SDS ProVal is licensed on a named user basis. The Windows user profile will be used to create the licence key. This means a licensed Windows user can log onto any PC and use the software without restriction. It is not a concurrent licence model. Once the licensed number of users have logged in for the first time, no other users will be permitted. Requirements for the client PC Software The client PC is compatible with Windows XP Professional with Service Pack 2, Windows Vista or Windows 7. Microsoft.NET Framework v3.5sp1 is required for all operating systems. Page 1

2 Hardware In addition to the space required for the system components mentioned above, a further 120MB of disk space is required to install ProVal LS. Minimum Windows 7 Windows 8.1 System Memory 4GB 4GB CPU Cores 2 3 CPU Speed 3GHz 2GHz Graphics Memory Display Resolution 128MB 1280px x 1024px The application will work reliably albeit slowly on the above minimum specification. Recommended Windows 7 Windows 8.1 System Memory 4GB 4GB CPU Cores 2 4 CPU Speed 3GHz 2GHz Graphic Memory Display Resolution The application will work reliably and perform well on the above specification. Requirements for the application/database server The server is compatible with Microsoft Windows Server 2003 (any edition). Windows Server 2008 and Server 2008 R2 are also supported. Microsoft.NET Framework v3.5 SP1 is required for all operating systems. Assuming that no computers yet exist for ProVal LS the following will apply. If you have current systems then use the following as a guide and that you may have to beef up existing systems to cope with the extra load of ProVal LS. There is no real reason why both the application and the database could not be on the same server. Page 2

3 Application Server Hardware Requirements We recommend as a minimum: Core 2 Duo at 2.4 GHz CPU 1GB RAM plus 512MB per concurrent user 360MB free hard disk space for installation. Graphics performance of the server is not relevant to the end user and is not specified for this reason. Consider using quad-core or better. We recommend the use of a dedicated server where possible. Please note that x86 (32-bit) versions of Microsoft s operating systems will only support up to 4GB of RAM, resulting in a maximum of six concurrent users (approximately). If a server needs to support more than six concurrent users, it must have an x64 (64-bit) version of the operating system, and proportionally more RAM. Database Server Software Requirements The server is compatible with Microsoft SQL Server 2005, SQL Server 2008 and Microsoft SQL Server 2012 (any edition). The.BAK file we supply will currently be in MSSQL2005 format which can be restored to any of the aforementioned server types. Database Server Hardware Requirements Whilst we recognise you might already have a SQL server, as a guide we recommend as a minimum: Core 2 Duo at 2.4 GHz CPU 4GB RAM (This assumes that no other programs or databases are being used on the same server.) 1GB free hard disk space for installation. Of course as with all SQL servers the more hardware you give it the better performance you get. We recommend the use of a single server dedicated to SDS ProVal LS and SDS Sequel databases as this makes support easier. Page 3

4 Remote Support A remote connection via VPN, or other secure third party client, will be required in order to provide the best level of end user support and this is covered in our "Remote Support" document. Please contact SDS technical support if you require more detail. Introduction You are now going to download and install the two parts of SDS ProVal, which are the client and server software. You will need access to the internet as well as administrator access to both the server and client computers. A basic knowledge of SQL Server Management application and how to open a SQL script and edit a few lines will be helpful. Downloading the Database File Click on the link provided in the body to download your company s relevant database file. This file will be in a zipped form and will need to be extracted. Copy the file to a suitable place, typically C:\Program Files\Microsoft SQL Server\MSSQL.1\Backup\SDSProValWorking.bak Installation using the SQL script 1. Please make sure that the SQL installation is running in mixed mode. If you are unsure, from within SQL Management Studio Program right mouse click on the server name, go to the security selection in the tree, SQL Server and Windows Authentication Mode should be the selected radial button. 2. Special Note: All of our applications (ProVal LS & Sequel) use TCPip to connect to the SQL server please make sure that this protocol is turned on for your SQL server and you will need to know the listening port number if it is not the default If you are unsure of how to check this please call us, details are in the Make sure that the logged on user, used by the MS SQL server has Read & Write access to the folder where the backup files are located, we suggest using the server administrator login. 4. Open the SQL Server Management application and login to the correct instance as a suitable database administrator, ie. 'sa'. Make a note of the 'server/instancename' as the clients will need this to use the correct database when logging into the Page 4

5 application. 5. Go to File open and select the SDSProValWorking Installation Script.sql file attached to the or in your downloaded zip file. 6. Amend the folder locations on lines 16, 17, file names on lines 22 & 23 to suit your server environment if necessary. The backup folder location must be the same place that you saved the SDSProValWorking.bak. The script file will do the following:- i. Create the logins necessary for SDS ProVal, which are "SDS User" and "SDS Query". (Do NOT alter the passwords being set otherwise the program will not know how to talk to the database) ii. iii. An empty database will be created with the correct naming syntax. Restore the ed database into the empty database that has just been prepared. iv. Assign the correct roles to the logins created in i. 7. Execute the script. This completes the database installation as long as there were no errors. If you do get errors please check the folder and file adjustments that you made earlier and run the script again. Please make sure that the SQL installation is running in mixed mode. If you are unsure, from within SQL Management Studio Program right mouse click on the server name, go to the security selection in the tree, SQL Server and Windows Authentication Mode should be the selected radial button. Make sure that the logged on user, used by the MS SQL server has Read & Write access to the folder where the backup files are located. Go to File open and select the SDSProValWorking Installation Script.sql file from the database zip file Downloading the Client Software Click on the link provided in the body to download the client software and save the zip in a suitable temporary location (your desktop is a good place). Page 5

6 Installation of Client Software Note: 1. Extract the client ZIP file and you will have a 'setup.exe' & 'Setup SDS ProVal LS.msi'. 2. Run the setup.exe as an ADMINISTRATOR 3. Make the required selections and the program files will install into the correct folders. A shortcut will have been created for the Desktop as well as in the Shelton Development Services menu selection. 4. Run the application from the "installed folder" as an ADMINISTRATOR for the first time. This allows the.net platform to compile the program for your particular hardware. (do not use the short cut on the desktop the first time) Microsoft has made it awkward for the installation of unsigned applications such as ProVal LS so the above method will make sure that the install goes smoothly. The setup.exe will check the local environment for the presence of.net 3.51 &.NET 2 If the local computer environment does not have the.net 3.5 sp1 platform loaded it will offer to download it from MS. This might take a long time depending on your Internet access speed. It might be faster if you download the platform and install this for all clients before running the setup.exe The application won't run correctly until the database is installed. Running and testing the application Once the database is installed, start the SDS ProValLS application. The application will require inputting the 'SQL server name\instancename', then type in 'SDSProValWorking'. Timed Trial Database If you are using the "Timed Trial" database two users are pre-programmed into the database and they are: User: Password: Role UserA UserA (Administrators) UserB UserB (General Users) and the passwords match each login name respectively. Note: Passwords are case sensitive. Page 6

7 This User configuration is only valid for "Timed Trial" databases, for New Supply customers only UserA will exist. Customer Custom Built Database If you are using a database that has been sent to you as a New Supply, built especially for your organisation, then only the first user, UserA will be active and is set to the Administrator Role although UserA can create new users. Registry options The standard installation of SDS ProVal LS will write the user name and database server to the HKEY_Current_User/Software key. This is used to save the user re-entering these each time they run the application. If you would prefer not to use the registry, please modify the application shortcut as follows:../ SDSProValLS.exe [/Server=address] [/User=username] The /Server command line option allows you to change the default database server:- eg. server= eg. server=myserver.mydomain.local If the server is running on a non-standard port:- eg. "server=myserver,1513" If the server is on a non-default instance:- eg. "server= myserver \instancename" The /User command line option allows you to specify the default name with which to try to log in to ProValLS. Note that this is not the database login name, which will always be either "sds user" or "sds query" depending on the application's need to read or write from the database, but the username chosen by the user. Please do NOT change the user logins on the SQL server side as this will stop the program from working all together. These user settings are encoded in the client software and are not accessible by any user. In the shortcut the Target is the line to be altered for the command line method see example below: Page 7

8 A Typical example is: "C:\Program Files (x86)\shelton Development Services\SDS ProVal LS\SDSProValLS.exe" "server=localhost" "database=sdsprovalworking" "user=%domain%\%user%" Where the server = localhost, database=sdsprovalworking and the user is DomainName\UserName Please NOTE that the trial version has particular user names i.e. UserA that will not be part of your domain so will have to be manually typed in each time. This is intentional and will not be a problem when you get the full release version of ProValLS licensed to your organisation. Page 8