PRECISION v16.0 MSSQL Database. Installation Guide. Page 1 of 45

Transcription

1 Installation Guide PRECISION v16.0 MSSQL Database Page 1 of 45

2 2015 Precision Software, a division of QAD Inc. Precision Software products are copyrighted and all rights are reserved by Precision Software, a division of QAD Inc. This document is copyrighted and all rights are reserved. No part of this docume nt may be reproduced, transmitted, adapted, translated or electronically stored without the prior written consent of Precision Software, a division of QAD Inc. PRECISION is a trademark of Precision Software, a division of QAD Inc.. Progress is a registered trademark of Progress Software Corporation. Page 2 of 45

3 Document Control Issue Control Issue Date Changes Made 1.0 April 2015 New document Cross Reference Change Summary Nr. Description Date (ymd) By whom 1.0 New Document Daniel Bratu Page 3 of 45

4 Contents Document Control... 3 Issue Control... 3 Cross Reference... 3 Change Summary... 3 Introduction... 6 Overview... 7 Server (Full) Install... 7 Client Install... 8 Pre-Requisites / Supported Platforms... 9 Progress OpenEdge... 9 ODBC Driver... 9 MS SQL Server... 9 PRECISION Remote Client Installation Requirements...10 PRECISION Network Client Installation Requirements...10 Quick Reference...11 Server (Full) Installation - with Remote Clients Only...11 Server (Full) Installation with Network Clients...12 Client Installation...13 Open Edge installation...14 PRECISION Remote Client...14 PRECISION Network Client...14 SQL Native Client 11 ODBC driver installation...15 PRECISION Remote Client...15 PRECISION Network Client...15 SQL Server Database Setup...16 PRECISION Dat abase Inst allation...18 Precision database can be installed before or after installing PRECISION v16.0 application Steps to be followed to install PRECISION database into an existing SQL Server instance when creating dev environment...18 Copy scripts to a local folder on SQL Server...18 Copy Bulk copy (*.bcp) files to a local folder on SQL Server...18 Open SQL Server Management Studio and connect to the SQL Server instance using an account/user that is member of the securityadmin or sysadmin...19 Run script: 01_CreateDb_PS_902.sql...19 Run script: 02_Tables_PS_902.sql...19 Run script: 03_Enable_xp_cmdshell.sql...19 Run script: 04_BulkImport_PS_902.sql...19 Run script: 05_AddUsers_MSSecurity_PS_902.sql when using MS SQL Security...20 Configuring the Dat aserver for SQL Server...21 Page 4 of 45

5 Install SQL Native Client 11 ODBC driver...21 Register PRECISION Data source...21 PRECISION Server (Full) Installation...29 Start the installation...29 Welcome screen...29 Company Name screen...30 PRECISION v16.0 location...31 PROGRESS OpenEdge details...32 SQL Server...33 SQL PRECISION PS_902 Database...35 PRECISION v16.0 Shortcut Location...36 Ready to Install Program...37 Restore of schema holder...38 Install complete...39 Post Installation...40 PRECISION Client Installation...42 Creating additional environments...45 Run installer to create a new environment...45 Create a new PRECISION MS SQL database...45 Page 5 of 45

6 Introduction This document is a guide to installing PRECISION v16.0 on an MSSQL Database platform. It is strongly advised that the installation is performed by a Precision installation specialist. They will require the services of an MSSQL DBA to complete the installation. If this is not being installed by a Precision installation specialist the installer should be technically competent in; - MSSQL Database Administration and Networking - Progress OpenEdge - MS Windows Administration The following should be noted Precision Software and QAD Support Centre reserve the right to charge for any consultation assistance given during the course of an installation by an unqualified installer". This document must be read in full before attempting the installation. Page 6 of 45

7 Overview This document includes instructions for Server and Client installs. Server (Full) Install When Windows Terminal Services / Citrix architecture is being utilized a Server Installation must be carried out on each server. The users running the PRECISION Windows UI will access the application from these servers using RDP or ICA clients. When configuring servers that will run PRECISION listeners (PRECISION SOA) a Server Install should be performed on each server. The following components will be installed on the server; - PRECISION Database Images - PRECISION Application objects - PRECISION required DLL s and OCX s - PRECISION Folder structure - PRECISION Program Group, Shortcuts and configuration files - PRECISION NetSetup Utility - PRECISION epage - Document Design Tool - PRECISION Viewer Proprietary PCL Document Viewer The following products must be installed on the server in advance; - OpenEdge Client Networking - OpenEdge MSSQL DataServer - SQL Server Native Client 11 ODBC Page 7 of 45

8 Client Install A client install would be required; 1) when Windows Terminal Services / Citrix is not being utilized to provide access to the PRECISION Windows UI 2) where additional servers will run PRECISION Listeners and a decision has been taken not to perform a full installation on these servers (the recommendation is a full application install on all servers) The client installation does not install the PRECISION Application objects and these must be accessed from the server using a shared network drive. Therefore there must be at least one Server Installation before a Client installation is attempted. It will install the following components: - PRECISION required DLL s and OCX s - PRECISION Client Folder structure - PRECISION Program Group, Shortcuts and configuration files - PRECISION epage - Document Design Tool - PRECISION Viewer Proprietary PCL Document Viewer The following products must be installed on the client; - OpenEdge Shared Network Client (netsetup from OpenEdge Server Installation) - SQL Server Native Client 11 ODBC driver Page 8 of 45

9 Pre-Requisites / Supported Platforms The PRECISION pre-installation checklist must have been completed and returned to the Precision project manager. The PRECISION Security Key must be available. Only case-insensitive collations are available for PRECISION v16.0 SQL Databases. Connection to the PRECISION SQL database is carried out using ODBC connections. SQL ODBC Native driver needs to be installed on the system. The ODBC System data source configuration should be carried out in advance of running PRECISION v16.0 application. If a previous version of PRECISION (PRECISION, TRA/X) is installed on the Server or Client the installation of PRECISION v16.0 will have an adverse effect on the existing implementation. The installation will move any Precision DLL, OCX or EXE files from the Windows\system32 folder to a backup folder within PRECISION v16.0 folder structure. It is recommended that clean servers are used for installation of PRECISION v16.0. It is possible to have multiple versions installed on one Server or Client however this will require manual configuration. Progress OpenEdge OpenEdge MS SQL DataServer OpenEdge Client Networking ODBC Driver SQL Server Native Client 11 ODBC MS SQL Server SQL Server 2012 service pack 2 Page 9 of 45

10 PRECISION Remote Client Installation Requirements This is where the users are running the PRECISION Windows UI via Windows Terminal Services or Citrix. This requires a Server Install only. Server/Client Product Operating System MS SQL Database Server SQL Server 2012 Any platform supported by MS SQL Server PRECISION Application Microsoft Terminal Server or Windows Server 2012 R2 Server Client Citrix XenServer RDP Client or ICA Client Any supported platform supported Notes: The following must be installed in advance of this installation; 1) Progress OpenEdge 11.4 MS SQL DataServer on PRECISION application server 2) Progress OpenEdge 11.4 Client Networking on PRECISION application server 3) Progress OpenEdge patch on application server 4) SQL Server Native Client 11 ODBC driver PRECISION Network Client Installation Requirements This is where the users are running the PRECISION Windows UI from their client machine. This requires at least one Server Install and client install on each client workstation that requires access. Server/Client Product Operating System MS SQL Database Server SQL Server 2012 Any platform supported by MS SQL Server PRECISION Application - Windows Server 2012 R2 Server Client - Windows 7 Windows 8 Windows Server 2008 R2 Windows Server 2012 R2 Notes: The following must be installed in advance of this installation; 1) Progress OpenEdge 11.4 MS SQL DataServer on PRECISION application server 2) Progress OpenEdge 11.4 Client Networking on PRECISION application server 3) Progress OpenEdge 11.4 Netsetup on the Client 4) Progress OpenEdge patch on application server and on the Client 5) SQL Server Native Client 11 ODBC driver Page 10 of 45

11 Quick Reference The details referenced in the tables below will be required during the installation. These tables can be used to record installation information for future reference and should be provided to the Precision Project Manager after an installation. There may be multiple Server (Full) Application or Client installations carried out. Server (Full) Installation - with Remote Clients Only Description Referred to in this document Used during installation PRECISION version v16.0 v16.0 number Location of installation D: media Progress OpenEdge C:\PRECISION\OpenEdge11.4 Location PRECISION Application C:\PRECISION\v16.0 Location PRECISION SQL PS_902mssqldev Database Name ODBC DSN Entry PS_902mssqldev SQL User Name PS_902DEV Local path on SQL Server C:\MSSQL\Data\PS_902\ to store PRECISION data files Local path on SQL Server to store PRECISION SQL C:\MSSQL\Data\PS_902\db.dev \ Database filenames for DEV environment Local path on SQL Server to store PRECISION bulk copy (bcp) files C:\MSSQL\Data\PS_902\bcp\ Page 11 of 45

12 Server (Full) Installation with Network Clients Description Referred to in this document Used during installation PRECISION version v16.0 v16.0 number Location of installation D: media Location on Server C:\PRECISION shared as PRECISION Mapped Network Drive S:\ mapped to \\server\precision Progress OpenEdge S:\OpenEdge11.4 Location PRECISION Application S:\v16.0 Location PRECISION SQL PS_902mssqldev Database Name ODBC DSN Entry PS_902mssqldev SQL User Name PS_902DEV Local path on SQL Server C:\MSSQL\Data\PS_902\ to store PRECISION data files Local path on SQL Server to store PRECISION SQL C:\MSSQL\Data\PS_902\db.dev \ Database filenames for DEV environment Local path on SQL Server to store PRECISION bulk copy (bcp) files C:\MSSQL\Data\PS_902\bcp\ Page 12 of 45

13 Client Installation Description Referred to in this document Used during installation Location of installation S:\v16.0\Netsetup media Progress OpenEdge S:\OpenEdge11.4 Location PRECISION Application S:\v16.0 Location PRECISION Client C:\PRECISION\v16.0 Location PRECISION SQL PS_902mssqldev Database Name ODBC DSN Entry PS_902mssqldev SQL User Name PS_902DEV Page 13 of 45

14 Open Edge installation PRECISION Remote Client Install the Open Edge MS SQL DataServer and the Client Networking products on the server: Insert the supplied Open Edge CD into the CD-ROM drive of the Server. From explorer/file manager locate and select the setup program on the CD-ROM root e.g. D:\setup.exe. (for Terminal Server install see section Installation on a Terminal Server) Enter your serial number and control strings. Follow the screen instructions and select a location for the installed products e.g. C:\OpenEdge11.4 Choose Complete installation type. PRECISION Network Client Install the Open Edge MS SQL DataServer and the Client Networking products on the server: Insert the supplied Open Edge CD into the CD-ROM drive of the Server. From explorer/file manager locate and select the setup program on the CD-ROM root e.g. D:\setup.exe. (for Terminal Server install see section Installation on a Terminal Server) Enter your serial number and control strings. Follow the screen instructions and select a location for the installed products e.g. S:\OpenEdge11.4 Choose Complete installation type. Install the NetSetup product on each of the Client Machines. Run the executable setup.exe to install the product. This executable can be located in the sub -folder netsetup of the main Openedge installation folder S:\OpenEdge11.4 on the server. If you require further information on this section then refer to the OpenEdge product installation guide and release notes. Page 14 of 45

15 SQL Native Client 11 ODBC driver installation PRECISION Remote Client Install SQL Native Client 11 ODBC driver on the server: Install the driver per the SQL Server version an patch To find it, search for SQL Server 20[XX] Service Pack [Y] Feature Pack o Where [XX] is the version [Y] is the service pack o Please download only from Microsoft Within the page from Microsoft, look for sqlncli.msi' Download the file for the supported platform (Windows 2012 R2 is only available as 64 bit platform): o X86 package for a 32 bit Windows OS o X64 package for a 64 bit Windows OS For example the SQL 2012 SP2 feature pack can be found using the link and it is required to download the package ENU\x64\sqlncli.msi PRECISION Network Client Install SQL Native Client 11 ODBC driver on the server and on each client machine: Install the driver per the SQL Server version an patch To find it, search for SQL Server 20[XX] Service Pack [Y] Feature Pack o Where [XX] is the version [Y] is the service pack o Please download only from Microsoft Within the page from Microsoft, look for Microsoft SQL Server 20[XX] Native Client Download the file for you platform: o X86 package for a 32 bit Windows OS o X64 package for a 64 bit Windows OS If you require further information on this section then refer to the OpenEdge product installation guide and release notes. Page 15 of 45

16 SQL Server Database Setup This must be performed by a qualified SQL Server DBA. PRECISION v16.0 database can be installed in a new or existing SQL Server instance that must meet following requirements: - SQL Server It is recommended to apply the latest patches available - Supported Database collations are case-insensitive collations - Server authentication o Select SQL Server and Windows Authentication mode - SQL Server Surface Area Configuration o Surface Area Configuration for Services and Connections Enable local and remote connections o Surface Area Configuration for Features Enable xp_cmdshell After running the script that requires this feature you can turn it OFF - xp_cmdshell option can be enabled by running a script provided if you don t have access to SQL Server Surface Area Configuration The scripts and files referenced in this section are available on the installation DVD and can be copied directly from the DVD in advance of the installation. They are also copied into the PRECISION folder structure as part of the installation. The following is an itinerary of the scripts and files provided; Create PRECISION SQL Database script file - 01_CreateDb_PS_902.sql Create PRECISION SQL Database tables script file - 02_Tables_PS_902.sql Enable xp_cmdshell option script file - 03_Enable_xp_cmdshell.sql Load PRECISION SQL Database content from bulk copy files - 04_BulkImport_PS_902.sql Create PRECISION SQL Database default logins if selected security is MSSQL security - 05_AddUsers_MSSecurity_PS_902.sql Add a new user/login for PRECISION SQL Database - AddNewUser_PS_902.sql Page 16 of 45

17 Export PRECISION SQL Database content into bulk copy files - BulkExport_PS_902.sql o Enable xp_cmdshell before running this script Backup PRECISION SQL Database script file - DbBackup_PS_902.sql Restore PRECISION SQL Database script file - DbRestore_PS_902.sql Restrict a user/login for accessing SQL Server if selected security is MSSQL security - DropUser_PS_902.sql Restrict a user/login for accessing PRECISION SQL Database when selected security is MSSQL security - RestrictUser_PS_902.sql Rebuild all indexes of PRECISION SQL Database - RebuildAllIndexes_PS_902.sql All these scripts contain tags which must be replaced if not already replaced before running. - Tags are replaced with values provided during the install for dev environment Page 17 of 45

18 PRECISION Database Installation Precision database can be installed before or after installing PRECISION v16.0 application. Create PRECISION Database before installing PRECISION v16.0 Scripts are located on DVD media at: PRECISION-v16.0-MSSQL\db\install\scripts: - template folder contains template script files that can be used to create a PRECISION PS_902 Database o All tags must be updated before running the scripts Initial data provided is available as copy bulk files available into Test data archive available at: PRECISION-v16.0-MSSQL\db\install\bcp\PS_902_test_bcp.zip - it contains bulk copy files to be used to create a test environment Create PRECISION Database after installing PRECISION v16.0 Scripts will be located after initial install at: C:\PRECISION\v16.0\db\dev\scripts. These scripts will have all tags replaced with values provided during the install for dev environment. Initial data provided is available as copy bulk files available into Test data archive available at: C:\PRECISION\v16.0\db\install\bcp\PS_902_test_bcp.zip - it contains bulk copy files to be used to create a test environment Steps to be followed to install PRECISION database into an existing SQL Server instance when creating dev environment Copy scripts to a local folder on SQL Server Copy all scripts from the DVD media (PRECISION-v16.0-MSSQL\db\install\scripts\template) or from PRECISION application server (C:\PRECISION\v16.0\db\dev\scripts) to C:\MSSQL\Data\PS_902\db.dev\scripts. If using scripts from DVD media, please replace all tags before running these scripts. Database name for the initial dev environment must be PS_902mssqldev. Copy Bulk copy (*.bcp) files to a local folder on SQL Server Copy archive PS_902_test_bcp.zip, containing bulk copy (*.bcp) files from the DVD media (PRECISION-v16.0-MSSQL\db\install\bcp) or from PRECISION application server (C:\PRECISION\v16.0\db\install\bcp) to C:\MSSQL\Data\PS_902\bcp and then unpack its content at C:\MSSQL\Data\PS_902\bcp Page 18 of 45

19 Open SQL Server Management Studio and connect to the SQL Server instance using an account/user that is member of the securityadmin or sysadmin Run script: 01_CreateDb_PS_902.sql This script will create PRECISION v16.0 SQL Database: PS_902mssqldev By default database files are: - PS_902mssql_Data o Initial size of 8GB o Auto growth File growth: 100MB Unrestricted growth - PS_902mssql_Log o Auto growth File growth: 100MB Unrestricted growth The Initial database size for the Test database is approximately 8GB. Run script: 02_Tables_PS_902.sql This script will create PRECISION v16.0 SQL Database tables & indexes and it will set login user: PS_902DEV as the owner of the database. Run script: 03_Enable_xp_cmdshell.sql Please run this script if xp_cmdshell option was not already enabled via SQL Server Surface Area Configuration. xp_cmdshell option is required by the next SQL script to load Bulk copy files provided. After running the next script this option can be disabled if required by security policies in place. Run script: 04_BulkImport_PS_902.sql This script will import data from bulk copy files provided into PRECISION v16.0 SQL Database tables. Update the script to import files provided for a Test or a Clean database as required. For dev environment please create a Test database. Before running this script please set import type as TEST or CLEAN. Page 19 of 45

20 Run script: 05_AddUsers_MSSecurity_PS_902.sql when using MS SQL Security This script should be run when using MS SQL security: all PRECISION users will have a login account on MS SQL Server. Page 20 of 45

21 Configuring the DataServer for SQL Server Install SQL Native Client 11 ODBC driver Install the driver per the SQL Server version and patch To find it, search for SQL Server 20[XX] Service Pack [Y] Feature Pack o Where [XX] is the version [Y] is the service pack o Please download only from Microsoft Within the page from Microsoft, look for Microsoft SQL Server 20[XX] Native Client Download the file for you platform: o X86 package for a 32 bit Windows OS o X64 package for a 64 bit Windows OS Register PRECISION Data source Precision Data source can be registered after PRECISION v16.0 database was created on SQL Server. This step should be repeated when creating a new PRECISION environment. Steps to register Precision Data source: Open 32 bit ODBC Data Source Administrator For a 64 bit Windows OS, open 32 bit version from: [Windows]\SysWOW64\odbcad32.exe Page 21 of 45

22 Select System DSN Create a new Data Source by choosing Add Page 22 of 45

23 Select SQL Server Native Client 11.0 driver Choose Finish Specify a name for your data source: PS_902mssqldev Description e.g.: PRECISION v16.0 MS SQL Dev Select the SQL Server name from the list or manually add it Choose Next Page 23 of 45

24 Select: With SQL Server authentication using a login ID and password entered by user Select Connect to SQL Server to obtain default settings for the additional configuration option User ID: PS_902DEV Password: ps_902dev Choose: Next Page 24 of 45

25 Change the default database to: PS_902mssqldev Choose Next Page 25 of 45

26 Uncheck Perform translation for character data Choose: Finish Choose: Test Data Source Page 26 of 45

27 You should receive: TESTS COMPLETED SUCCESSFULLY! Choose OK Choose OK to Page 27 of 45

28 Exit the ODBC Data Source Administration tool Page 28 of 45

29 PRECISION Server (Full) Installation Start the installation Windows Server 2012 R2 Install on a Remote Desktop Server - formerly Terminal Server- via Control Panel -> Install Application on Remote Desktop Server. The following provides a description of each screen that will be encountered during the installation, detailing the information required and its purpose; Welcome screen Page 29 of 45

30 Company Name screen User Name: prompts for user name. Company Name: prompts for your company name. This information is used to automatically configure the system parameter settings within PRECISION when the new installation is accessed for the first time. Install this application for: PRECISION v16.0 application must be installed ONLY for ALL USERS Page 30 of 45

31 PRECISION v16.0 location Destination Folder: prompts, for PRECISION v16.0 install folder. Default folder is C:\PRECISION\v16.0 Page 31 of 45

32 PROGRESS OpenEdge details DLC: prompts for PROGRESS OpenEdge 11.4 install folder. OpenEdge must be installed prior to PRECISION v16.0. Date Format: prompts for Date Format to be used by PRECISION v16.0 client application Page 32 of 45

33 SQL Server Environment name: default value is dev it cannot be changed. IMPORTANT NOTICE: If you want to create another environment with a different name please complete all requests for DEV environment because you will be using it as a template for creating any other environments. That means you don t have to create SQL PRECISION PS_902 Database for DEV environment at the end of installation. When the installation process is finished you can create another environment following the steps described in paragraph Creating additional environments. SQL Server name: prompts for the name of SQL Server used to store PRECISION v16.0 database. Note: For MS SQL Server 2012 Express Edition usually the name of the server is like <COMPUTER-NAME>\SQLEXPRESS SQL Server version: allow you to choose current version of SQL Server. Path on SQL Server to store PRECISION bulk copy (bcp) files: prompts for the local path on SQL Server where will be stored PRECISION bulk copy (bcp) files e.g. C:\MSSQL\Data\PS_902\bcp\; Page 33 of 45

34 Security: prompts for security model to be used for PRECISION v16.0 application. There are two choices; all users can log onto the MS SQL database with the same username and password or individual usernames and passwords are used when logging onto the database. PRECISION Security: The username and password entered during PRECISION login are validated against the user setup in PRECISION. The username and password used to connect to the MS SQL database is always the same and is the username and password specified in the next step of the install. The username must exist in MS SQL and have all required privileges to access PRECISION objects that exist in the MS SQL database. MS SQL Security: The username and password entered during login will be used to connect to the MS SQL Instance. If the username exists in the MS SQL Database and the connection is successful, a second validation will be performed with the same user and password against the PRECISION users. As before, the MS SQL user should have the required configuration to access PRECISION objects that exist in the MS SQL database. Page 34 of 45

35 SQL PRECISION PS_902 Database SQL Database name: prompts, for the name of PRECISION v16.0 SQL Database. The name should have this format: PS_902mssql<xxx>, where <xxx> = dev, prd is the environment name. This field is read-only. SQL Database filenames paths: Data: prompts, for the local path on SQL Server where to be stored PRECISION v16.0 SQL Database data file for DEV environment e.g. C:\MSSQL\Data\PS_902\db.dev\ Log: prompts for the local path on SQL Server where to be stored PRECISION SQL Database log file for DEV environment e.g. C:\MSSQL\Data\PS_902\db.dev\ Collation: prompts for the PRECISION SQL Database collation to be used. Only caseinsensitive collations are available for selection. SQL Server collation specifies the sort order to use for Unicode data types (nchar). A sort order defines the sequence in which characters are sorted, and the way characters are evaluated in comparison operations. Login owner name: prompts, for the PRECISION SQL Database login owner name e.g. PS_902DEV Login owner password: prompts, for the PRECISION SQL Database login owner password e.g. ps_902dev Page 35 of 45

36 PRECISION v16.0 Shortcut Location Program Folder: this screen shows the default location for the PRECISION v16.0 MS SQL shortcut, which will be located in Start > Programs > PRECISION v16.0 MS SQL. PRECISION v16.0 automatic installation also creates a PRECISION v16.0 shortcut on your desktop. Page 36 of 45

37 Ready to Install Program Choose Install to start installing PRECISION v16.0 MS SQL. Page 37 of 45

38 Restore of schema holder Installation restores schema holder from the backup provided. Press any key to continue. Page 38 of 45

39 Install complete Choose Finish to continue. Page 39 of 45

40 Post Installation Requirement: This step requires that PRECISION database installation is completed. The following users (with passwords) will be available after an install; qconfig qad traxglmgr traxgluser Precision demo Precision Precision The first time PRECISION is accessed after an install it will give an option to update the database with initial settings. The option to update the configuration should be accepted. This will tailor the database based on information entered during the install. If this update is not carried out the system will not function and you may not be able to access it. If you choose AUTOMATIC update, following screen will be presented: Page 40 of 45

41 If XML were set to be loaded when running PRECISION v16.0 for the first time the following screen will be presented; When Automatic update completed the following messages will be presented; Note: For a new PRECISION installation PRECISION Preview should be installed from C:\PRECISION\v16.0\windows\install\PRECISION Preview Page 41 of 45

42 PRECISION Client Installation Typically PRECISION v16.0 application is installed on a Terminal Server or Citrix server that will allow users to run PRECISION Windows UI from the server without installing any components on the client computers. If direct access from remote client computers is required then: o Install PRECISION v16.0 MSSQL on the server on a network drive that is mapped to a local share (e.g. S: = \\SERVER\PRECISION). o The same mapped drive letter used during the install (e.g. S:) should be mapped on the client computers to access and run PRECISION v16.0 MS SQL client application. To install PRECISION v16.0 MS SQL Network Client on a client computer, go to Start > All Programs (or Programs) > Accessories and then click Command Prompt. In the command window, type CD /D S:\v16.0\netsetup [Enter] to change the current directory to the Network Client installation. The Network Client installation script requires four parameters: PRECISION v16.0 MSSQL server location This is the location of the server installation, e.g. S:\v16.0 PRECISION v16.0 MSSQL Network Client location This is a local path where the script will install the client files required to run the application, e.g. C:\PRECISION\v16.0 Progress Open Edge client location This can be a local path for a full Progress installation (e.g. C:\PRECISION\PROGRESS) or a remote path for a PROGRESS Network Page 42 of 45

43 Shared installation (e.g. S:\PROGRESS). Progress OpenEdge client should be installed on the client computer prior to running the script. You can run the InstallNetworkClient.bat installation script without parameters to get a quick example. Run the script providing the four parameters explained above (example): Page 43 of 45

44 The script will install the required application files on the client computer and will also create a shortcut to run the PRECISION v16.0 MSSQL application, one for each environment installed on the server. Setup the DSN on the client computer, same as done on the server see Register PRECISION Data source. Failure to do so will result in an error message when running the PRECISION v16.0 MSSQL application on the client machine:. Page 44 of 45

45 Creating additional environments This section outlines the steps required to create a second installation of PRECISION i.e. additional databases. Run installer to create a new environment Go to Control Panel and choose to Add/Remove Programs or Programs and Features. Select PRECISION v16.0 MS SQL and choose Change. It will prompt to Uninstall PRECISION or to Create New Environment. Choose to Create New Environment and it will guide you through the install routine. You will be prompted for the name of the new environment (e.g. PROD, QA - no more than 4 characters) then screens presented at SQL Server & SQL PRECISION PS_902 Database must be filled. Installer then creates: o a second Progress Schema o scripts to be used to create new PRECISION v16.0 MS SQL Database o connection configuration files o client related folder structure o cust related folder structure o new shortcut on the desktop and start menu Create a new PRECISION MS SQL database Bulk copy files provided with the install can be used to create a new database. o Test (seeded) database - contains sample data e.g sample shipments, sample workflows, content (compliance & carrier), partners, and products. This database should be used for training, education and demo purposes. o Clean database - contains the minimal base data required to run the system (e,g. system values, UOM s, edit codes, device types, transport modes etc..). There are no shipments, rules, partners, products etc. in this database. This can be used to prepare a customer's system for go-live. Bulk copy files are available on install DVD in the [install folder]\db\install\bcp or at [PRECISION v16.0 MS SQL install folder]\db\install\bcp. Alternatively a database backup can be created from an existing PRECISION v16.0 database and this can be used to create a new PRECISION v16.0 database. In the second scenario when logging into PRECISION for the first time the system will not update the environments and system values with paths entered when creating the second environment, it will use the settings from the copied database. Follow Steps per PRECISION Database Installation to create new database and then register new PRECISION Data Source. Page 45 of 45