2.3 - Installing the moveon management module - SQL version



Similar documents
for Networks Installation Guide for the application on the server July 2014 (GUIDE 2) Lucid Rapid Version 6.05-N and later

for Networks Installation Guide for the application on a server September 2015 (GUIDE 2) Memory Booster version 1.3-N and later

for Networks Installation Guide for the application on the server August 2014 (GUIDE 2) Lucid Exact Version 1.7-N and later

Migrating helpdesk to a new server

Installing The SysAidTM Server Locally

Installation / Migration Guide for Windows 2000/2003 Servers

MICROSTRATEGY 9.3 Supplement Files Setup Transaction Services for Dashboard and App Developers

Training module 2 Installing VMware View

Windows 98 Workstation Install

Virtual Office Remote Installation Guide

Setting up a database for multi-user access

Installation Instruction STATISTICA Enterprise Small Business

Linking Access to SQL Server

STATISTICA VERSION 9 STATISTICA ENTERPRISE INSTALLATION INSTRUCTIONS FOR USE WITH TERMINAL SERVER

STATISTICA VERSION 12 STATISTICA ENTERPRISE SMALL BUSINESS INSTALLATION INSTRUCTIONS

SPECIALIST PRACTICE MANAGER

Active Directory Integration for Greentree

MS SQL Server Database Management

Installation Instruction STATISTICA Enterprise Server

Jolly Server Getting Started Guide

PaperClip Audit System Installation Guide

Migrating MSDE to Microsoft SQL 2008 R2 Express

How To Upgrade Your Microsoft SQL Server for Accounting CS Version

Table of Contents SQL Server Option

Voyager Reporting System (VRS) Installation Guide. Revised 5/09/06

Installing Cobra 4.7

Linko Software Express Edition Typical Installation Guide

Install SQL Server 2014 Express Edition

MS SQL Express installation and usage with PHMI projects

Prerequisites Guide. Version 4.0, Rev. 1

STATISTICA VERSION 10 STATISTICA ENTERPRISE SERVER INSTALLATION INSTRUCTIONS

Aradial Installation Guide

Suite. How to Use GrandMaster Suite. Exporting with ODBC

ilaw Installation Procedure

SyncThru Database Migration

Moving a Romexis Database to an Existing SQL Instance

SonicWALL CDP 5.0 Microsoft Exchange User Mailbox Backup and Restore

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

3 Setting up Databases on a Microsoft SQL 7.0 Server

Windows administration for Adash Software

Querying Databases Using the DB Query and JDBC Query Nodes

How to use SURA in three simple steps:

Matisse Installation Guide for MS Windows. 10th Edition

Upgrading to Document Manager 2.7

Getting Started with ODM

InformationNOW SQL 2005 Database Backup and Restoration

Server Installation, Administration and Integration Guide

Setting Up ALERE with Client/Server Data

Installing SQL Express. For CribMaster 9.2 and Later

LockView 4.2 CompX Database & Network Configuration & Installation Manual

Installation of MSSQL Server 2005 Express Edition and Q-Monitor 3.x.x

Installing the Microsoft Network Driver Interface

Converting InfoPlus.21 Data to a Microsoft SQL Server 2000 Database

Installing LearningBay Enterprise Part 2

PaperClip32. Installation Guide. for Workgroup and Enterprise Editions. Document Revision 2.1 1

INTRODUCTION: SQL SERVER ACCESS / LOGIN ACCOUNT INFO:

Case Closed Installation and Setup

Analyzer 2.0. Installation Guide. Contents

Tool Tip. SyAM Management Utilities and Non-Admin Domain Users

Symantec Backup Exec 12.5 for Windows Servers. Quick Installation Guide

Using SSH Secure Shell Client for FTP

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

LockView CompX Database & Network Configuration & Installation Manual

aims sql server installation guide

QUANTIFY INSTALLATION GUIDE

Creating IBM Cognos Controller Databases using Microsoft SQL Server

2. Installation Instructions - Windows (Download)

National Fire Incident Reporting System (NFIRS 5.0) NFIRS Data Entry/Validation Tool Users Guide

RFMS, INC. Reference Library Documentation. Version 10 Conversion Manual. Microsoft SQL

Installation Troubleshooting Guide

SC-T35/SC-T45/SC-T46/SC-T47 ViewSonic Device Manager User Guide

VERITAS Backup Exec 9.1 for Windows Servers Quick Installation Guide

ProSystem fx Document

CS WinOMS Practice Management Software Server Migration Help Guide

How to Backup and FTP your SQL database using E2.

SQL Express to SQL Server Database Migration MonitorIT v10.5

Symantec Backup Exec TM 11d for Windows Servers. Quick Installation Guide

Falcon Install Guide

Installation of MSSQL Server 2008 Express Edition and Q-Monitor 3.x.x

WhatsUp Gold v16.1 Installation and Configuration Guide

IceWarp Server Windows Installation Guide

Creating client-server setup with multiple clients

Reconfiguring VMware vsphere Update Manager

Table of Contents. 2 Getting Started Guide

Server & Workstation Installation of Client Profiles for Windows (WAN Edition)

COMBOGARDPRO. 39E Electronic Combination Lock SOFTWARE INSTALLATION INSTRUCTIONS

UPS WorldShip Install on a Workgroup Remote

Getting Started with Attunity CloudBeam for Azure SQL Data Warehouse BYOL

ATD NEWS SOFTWARE NETWORKING / DATABASE FAQs... 2 Database Issues:... 2 Q: What are the system requirements for installing MSDE server?...

PeopleTools v8.52 Crystal Reports and nvision for Windows 7 Workstation Installation Guide

1 Download & Installation Usernames and... Passwords

User Management Tool 1.5

Global Image Management System For epad-vision. User Manual Version 1.10

E-Notebook SQL 12.0 Desktop Database Migration and Upgrade Guide. E-Notebook SQL 12.0 Desktop Database Migration and Upgrade Guide

GIGATRAK CLIENT INSTALL HANDHELD TERMINAL

System Manager Installation Guide

Transcription:

2.3 - Installing the moveon management module - SQL version The moveon management module consists of two elements: the moveon client and the moveon database. The moveon client contains all the program forms, lists, functions, etc. The moveon database contains all the data relating to your institution to be managed in moveon (e.g. students, partner institutions, contacts, etc.). The moveon client is an MS Access application (file: moveon.mdb). The moveon database can be an SQL database or an MS Access application (file: moveon_data.mdb). This section describes how to install the SQL version of moveon and also how to migrate from an MS Access version of moveon to an SQL version. In both cases the moveon-sql program (file: moveon_sql.mdb) provided by QS QS unisolution enables you to carry out the installation/migration of moveon. 1- Creating the "moveon" directory on a file server (installation) This section is only applicable if you are installing moveon. Start by creating a "moveon" folder on a file server. This folder must be accessible from and have the same access path from all the workstations using moveon (e.g. "M:"). Within this "moveon" folder you should also create a folder "documents" to store all the MS Word documents used for mail merge with moveon. 2- Creating the SQL database You should create a "moveon" SQL database together with a user who can access the database via ODBC with create/ edit/delete rights for the tables and the data. The size of the database should not generally exceed 20 MB. The SQL version of moveon is compatible with the following databases: MySQL, PostgreSQL, Oracle, MS-SQL Server. The minimal version required for these databases is described in section 2.2. The encoding used for the database must be UTF-8. If you choose to use MS SQL Server, please refer to the point 10 of this section. 3- Extracting the installation files to the file server Installing moveon from the CD-ROM, without data transfer This section is only applicable if you are installing moveon and QS QS unisolution did not transfer your institution s data to moveon. In this case the installation file "moveon_install_3xx.zip" is supplied on an installation CD-ROM. Extract the files from the zip folder to the "moveon" directory on your file server (e.g. "M:"). Installing moveon with data transfer This section is only applicable if you are installing moveon and QS QS unisolution transferred your institution s data to moveon. In this case do not use the installation CD-ROM; QS QS unisolution supplies the installation pack as a zip file called "moveon_install3xx.zip". Extract the files from the zip folder to the "moveon" directory on your file server (e.g. "M:"). Contents of the installation file This section is only applicable if you are installing moveon. The installation file contains the following files: - the moveon client: "moveon.mdb" - the moveon database: "moveon_data.mdb" - the moveon icon: "moveon.ico" - the moveon update icon: "moveon_update.ico" - the batch file for updates: "moveon_update.bat", and - the software for migration to an SQL database: "moveon_sql.mdb" Fig. 1: Contents of the installation zip file 2.3 - Installing the moveon management module - SQL version page 1

Migrating moveon from an MS Access database to an SQL database This section is only applicable if you subsequently migrate moveon from an MS Access version to an SQL version. In this case QS QS unisolution supplies you with a file called "moveon_sql3xx.zip", which contains the file "moveon_sql.mdb". Extract this file to the "moveon" directory on your file server (e.g. "M:"). 4- Creating SQL database tables and migrating data Installing and configuring the ODBC driver on the workstation from which the installation / migration will be performed. The ODBC driver corresponding to the chosen SQL database is required on the workstation from which the installation or migration will be performed. The ODBC driver allows the moveon-sql program to connect to the SQL database. Please refer to section 2.9 for details of how to install and configure the appropriate ODBC driver. Check that the connection to the database is working correctly by using the connection test function in the configuration of the ODBC driver. Starting the installation/migration program The moveon-sql program allows you to create SQL database tables and to migrate earlier data if necessary. To start the moveon-sql program, run the "moveon_sql.mdb" file from a workstation on which MS Access is installed. In stage 1 select the language in which moveon will be used and then click Next. Fig. 2: moveon-sql - Language selection In stage 2 the following two options appear: "First installation without import" and "Installation with import or migration MS Access -> SQL". Select the appropriate option and then click Next. page 2 2.3 - Installing the moveon management module - SQL version

Fig. 3: moveon-sql - Installation/migration type selection Installation without data transfer In this case, in stage 3 specify the data for connecting to the SQL database and then click Next. Fig. 4: moveon-sql - Installation without data transfer Installation with data transfer or migration from MS Access to SQL In this case, in stage 3 specify the data for connecting to the SQL database and the path for accessing the database (moveon_data.mdb) containing the data to be transferred/migrated, then click Next. 2.3 - Installing the moveon management module - SQL version page 3

Fig. 5: moveon-sql - Installation with data transfer Executing the installation/migration The actual installation/migration takes place in stage 4. Various tasks are carried out automatically. The successful completion of each task is indicated by a green OK symbol. This stage may take several minutes. Once the installation/ migration has been completed, you can close the moveon-sql program. To avoid using two databases in parallel, make sure that future users cannot access the moveon_data.mdb file. Fig. 6: moveon-sql - Executing the installation/migration 5- Initial configuration of the moveon management module page 4 2.3 - Installing the moveon management module - SQL version

Before the moveon client can be installed on each workstation it must be configured with the data for connecting to the SQL database. To do this, start the "moveon.mdb" file from the server's "moveon" directory. MS Access must be installed on the computer you are using to do this. Choosing the language of moveon In the first window select the language in which moveon will be used and then click Next. Fig. 7: moveon - Language selection Linking the moveon client to the moveon database In the next window you should specify the data for connecting to the moveon database. Select "SQL database" followed by the database type (Oracle, MySQL, PostgreSQL, SQL Server). Then specify the connection data (DSN, server, etc.) corresponding to your "moveon" SQL database. Now click Next. The connection to the tables is made automatically. This process may take several minutes. Fig. 8: moveon - Connecting to the database Once the connection has been made to all tables, the login window appears. This shows that the installation has been completed successfully. You can now close moveon by clicking the Close button in the top right of the window. 6- Installing moveon 3.0 Structure of the moveon personal folder Each user should have a moveon personal folder. This can either be a folder on the local disk (e.g. C:\Program Files \moveon) or a personal folder on a server (e.g. U:\moveon), particularly where a terminal server is used. The moveon personal folder contains the following elements: 2.3 - Installing the moveon management module - SQL version page 5

- the moveon client: "moveon.mdb" - the moveon icon: "moveon.ico" - the moveon update icon: "moveon_update.ico" The moveon personal folder has to be accessible for every user via the same access path (e.g. C:\Program Files \moveon or U:\moveon). This personal folder and its contents can be created automatically via a batch file (see below). Installing and configuring the ODBC driver on the workstations The ODBC driver corresponding to the SQL database used must be installed on each workstation on which moveon is to be used. Please refer to section 2.9 for details of how to install and configure the appropriate ODBC client. Creating an installation and update batch file The batch file "moveon_update.bat", which is one of the installation files supplied, is used for creating the moveon personal folders and then for copying the files required for moveon, in particular the moveon client (moveon.mdb), into these folders. It will also be used to update the client on each workstation when the client is updated on the server. The contents of the batch file supplied by QS unisolution are shown below. Its contents, and in particular the access paths for the various files and folders, should be adapted to the specific requirements of your institution. Fig. 9: Installation and update batch file The batch file creates the "moveon" personal folder and then copies the "moveon.mdb", "moveon.ico" and "moveon_update.ico" files locally. Creating shortcuts for starting moveon and for updates Each user should have the following two shortcuts on his/her desktop: - the "moveon" shortcut, allowing the user to open the moveon client saved in his or her personal folder, and - the "moveon update" shortcut, allowing the user to update his or her personal version of the moveon client by copying the client from the server Fig. 10: moveon shortcuts on the user's desktop page 6 2.3 - Installing the moveon management module - SQL version

Before creating these shortcuts, run the "moveon_update.bat" file from one of the workstations in order to copy the "moveon.mdb", "moveon.ico" and "moveon_update.ico" files locally. Then create the two shortcuts as follows: - The "moveon" shortcut points to the "moveon.mdb" file in the local directory (e.g. C:\Program Files\moveon \moveon.mdb). It uses the "moveon.ico" icon in the local directory (e.g. C:\Program Files\moveon\moveon.ico). - The "moveon update" shortcut points to the "moveon_update.bat" file on the server (e.g. M:\moveon_update.bat). It uses the "moveon_update.ico" icon in the local directory (e.g. C:\Program Files\moveon\moveon_update.ico). Once you have created these shortcuts, simply copy them to the "moveon" directory on the server. Copying the two shortcuts to each user's desktop and local installation To install moveon on each workstation, simply copy the two shortcuts created above onto the user's worktop. Then click the "moveon update" shortcut to carry out the installation. moveon can now be started by clicking the "moveon" shortcut. You must have administration rights to create the local "moveon" directory. 7- Verifying the requirements on each workstation Please refer to section 2.2 to verify that all requirements are met for each workstation. 8- Testing moveon on each workstation Now you can use the desktop shortcut to check that moveon is working correctly on each workstation. The first window which will open when you start moveon is the login window. A user account for the administrator is created by default in moveon. This user has access to the software functions and configuration. The access codes for the administrator are as follows: - User name: admin - Password: moveon Enter the access codes and click Next. This will take you to the main menu of moveon. Fig. 11: moveon - Login window 9- Specific case: using a terminal server If moveon is hosted on a terminal server, MS Access only needs to be installed on the terminal server. Make sure that any other tools needed for using moveon are also available on the terminal server: MS Word and MS Excel, printers, and directories for saving MS Word mail merge documents. 10- Specific case: using a MS SQL Server database Here is a summary of the installation steps to install moveon with a MS SQL Server: - Create a user in MS SQL Server with the "dbcreator" role 2.3 - Installing the moveon management module - SQL version page 7

- Log in into SQL Enterprise Manager (or SQL Server Management Studio) as the newly created user and create the moveon database - Create an ODBC connection with the latest Driver (if you use MS SQL Server 2005, please use the SQL Native Client as an ODBC Driver) and connect with the newly created user using Server Authentication - Run the the moveon SQL program. To do so, please refer to the point 4 of this section. After having created the database and after the moveon-sql program has run successfully, the database can be connected with the MS SQL Server authentication or the Windows Authentication. For Server Authentication: - The same user used for the moveon SQL can be used for accessing moveon from the clients - Or create new user, assign the user to moveon database with appropriate read and write rights - Create on each client an ODBC connection using the latest ODBC Driver (if you use MS SQL Server 2005, please use the SQL Native Client as an ODBC Driver) and choose Server Authentication - In moveon, enter the necessary information under the choice "SQL Server with Server Authentication" and leave the tables owner empty For Windows Authentication: - Create the Windows authenticated users and assign them into moveon database with appropriate read and write rights - Create on each client an ODBC connection using the latest ODBC Driver (if you use MS SQL Server 2005, please use the SQL Native Client as an ODBC Driver) and choose Windows Authentication - In moveon, enter the necessary information under the choice "SQL Server with Windows Authentication" page 8 2.3 - Installing the moveon management module - SQL version