Home > System Administration > Set Up and Installation > Upgrading The Database

Upgrading The Database

Introduction

Prerequisite

Prepare POS for Upgrade

Updating the SQL Database

Upgrading the Application Server

Preparing Files for Client Upgrade

Apply the Licence

Starting up of the Remaining Services

How do the Back Office Clients Upgrade?

How do the POS Clients Upgrade?

Introduction

These processes can be applied where customers are using the BE System in a centralised architecture.

Prerequisite

Since version 5.16, a new licensing methodology has been applied, resulting that a new license key needs to be applied. Before attempting the upgrade, please ensure that you have a valid license which can be obtained via your account manager. Failing to obtain the new license means the TILLINCOMING service will fail to start.

You will need the SQL Scripts and Executables including any available patches of the version you wish to install, prior to the upgrade. See Where Do I Get The Programs From? for further details. You also need any other DB SQL upgrade scripts of previous releases which is described below. This can be obtained from the ftp server.

Historical transactions must be processed prior to upgrading.

Prepare POS for Upgrade

It is recommended that you prepare the POSUPDATEFOLDER or the folder specified in System Settings with the latest POS EXE’s and perform a “notify upgrade” to the tills at least 2 days prior to the upgrade. This is to ensure that the POS has the required files prior to the server upgrade. The new files will then be stored in the upgrade folder on the POS waiting to be used. When the FILEVERSIONS table is updated at Database level, the POS will then be notified and move the new files from the upgrade folder to the root of the DRSApps folder. This process reduces the network work load and speeds up the upgrade process. To know which files needs to be placed in this folder please check the following section. The notify upgrade can be initiated via the Till Control.

Updating the SQL Database

Upgrades must be applied in numeric order, for example, you can not upgrade from 5.21 straight to 5.23. This means that if you have 5.21, you need to upgrade the database using 5.22 upgrade database script then the 5.23 script. To ensure that the database upgrade script is processed correctly you need to stop all BE services prior to the database upgrade.

There are two ways to upgrade the database:

a. Use the UpgradeDatabase.exe (C:\drsapps\) program to upgrade the database. When you run the program it will ask for the file containing the SQL modifications. It will process each command in the file. Each statement, and any errors which occur, are logged to the screen. If there are errors you can copy this log to an email to send to support. The system will remember the last modification made. If you tried to process the same file again, it would be rejected.

Figure: Example Upgrade Database Screen

b. Run the provided SQL upgrade script using SQL Query Analyser. Select the BE database you want to upgrade, insert the SQL script into Query Analyser and press Execute. The Messages window may show you whether errors have occurred but these can be ignored.

Figure: Example SQL Query

Now that the DB has been upgraded to the latest version of BE, we need to clear down the FILEVERSIONS table. Failing to clear down the FILEVERSIONS table, the MainMenu.exe will fail to run. The clear down of the FILEVERSIONS table has to be done using SQL Query. Start a new SQL Query and execute the following command: TRUNCATE TABLE FILEVERSION.

The database has now been prepared and you can continue with the application server upgrade.

Upgrading the Application Server

a. Log on to Application Server:  

b. Stop ALL BE related services that are running if not already done prior to the upgrade of the Database. This will stop all communication from the stores to the database so it is advised to undertake this task outside shop operating hours.

c. Create a backup copy of all exe files in your \drsapps folder.

d. Copy the new exe files to your \drsapps folder and start the services for MerchantCentralServer.

To inform the clients (POS/ BOS) that the new application version is ready to be used and to enable the client to download those files you need to do the following. Run Main Menu and login. From the Command Prompt, Run C:\drsapps\MerchantEOD.exe FILEVERSIONS. This command will update a table in the database called FILEVERSIONS. This table contains a record for each valid executable in your \drsapps folder and sets the acceptable version number.

Preparing Files for Client Upgrade

As a prerequisite you need to ensure that the BE folders have the correct executables.

a. Copy all POS executables to the folder \drsapps\posupdatefiles or to the folder specified in System settings.

For POS with non BOS related tasks

DBISAMViewer.exe

DRSLicence.dll

DRSUpdater.exe

DynaPOSTouch.exe

MerchantLocalServer.exe

MerchantPOS.exe

For POS with BOS related tasks

DBISAMViewer.exe

DRSLicence.dll

DRSUpdater.exe

DynaPOSTouch.exe

MerchantLocalServer.exe

MerchantPOS.exe

RequestReportAccounts.exe

RequestReportBanking.exe

RequestReportEOD.exe

RequestReportExtra.exe

RequestReportInventory.exe

RequestReportItems.exe

RequestReportItems2.exe

RequestReportLoyalty.exe

RequestReportUsers.exe

b. Copy all BOS executables to the folder \drsapps\updatefiles or to the folder specified in System settings.

AlertService.exe

B2BService.exe

BackOfficeeClockIn.exe

BookingInterface.exe

CommsProfile.exe

DataEntryBasic.exe

DataEntryInventory.exe

DataEntryItems.exe.EXE

DBISAMViewer.exe

DRSBatchRun.exe

DRSLicence.dll

DRSUpdater.exe

DynaPOSTouch.exe

ImportItemData.exe

LanguageMaint.exe

LoyaltyService.exe

MainMenu.exe

MerchantEOD.exe

MerchantInterfaceProcess.exe

MerchantLocalServer.exe

MerchantPOS.exe

MerchantReportManager.exe

MerchantStats.exe

ReplMaint.exe

ReportAccounts.exe

ReportBanking.exe

ReportEOD.exe

ReportExtra.exe

ReportInventory.exe

ReportItems.exe

ReportItems2.exe

ReportLoyalty.exe

ReportUsers.exe

ReportVariant.exe

RequestReportAccounts.exe

RequestReportBanking.exe

RequestReportEOD.exe

RequestReportExtra.exe

RequestReportInventory.exe

RequestReportItems.exe

RequestReportItems2.exe

RequestReportLoyalty.exe

RequestReportUsers.exe

RequestReportVariant.exe

TillIncomimg.exe

UpgradeDatabase.exe

Those two update file folders are defined in the Systems Settings - Directories tab and tell the clients (BOS or POS) where to download the new version from.

Apply the Licence

Before applying the licence, please ensure that you have the correct licence library file in the root of the DRSapps folder. You can check this by viewing the properties of the DRSlicence.dll and check the version. The version of this DLL should be the same as the version you are upgrading to. Log on to the main menu if not already. From the start run command execute command “C:\DRSAPPS\DATAENTRYBASIC.EXE DRSLICENCE” or select BE Licence from the menu.

Initially you will see the existing licence code as shown below. To apply the new licence double click on the existing record.

Figure: Example BE Screen

The code should not have changed unless you have migrated to a new sever. If you have changed server, please ensure that you provide the correct MAC address when applying for the licence.  

The licence type should always be “Enterprise” unless specified when receiving the licence. Enter the correct number of POS and Stores or the licence will fail. Also ensure that you have expansion flexibility when applying for the licence by applying a licence for more POS and Stores than you currently have. Please be moderate! Enter the licence key received and press OK. If all data is correct the licence should be accepted.

Figure: Example BE Licence Screen

Starting up of the Remaining Services

Now that you have applied the new licence start the remaining services. These are MERCHANT INCOMING TRANSACTION HANDLER and MERCHANT STATISTICS UPDATER and the MERCHANT ALERT SERVICE if used. If your current setup violates the licence key the MERCHANT INCOMING TRANSACTION HANDLER will not start. You can check the Windows Event Viewer for the reason. This could be either too many active POS or Stores for the licence or incorrect MAC.

How do the Back Office Clients Upgrade?

Once a Back Office application is started and the client program version does not match the entry in FILEVERSIONS, the client will attempt to load the correct copy of the program. The first thing it will do is check the upgrade directory.

The upgrade directory is a subdirectory underneath the \drsapps directory where the executables are run from, for example c:\drsapps\updatefiles.

If there is a new file there it will attempt to use it. If there is no file, it will ask the server for the new version and download it into the updatefiles directory.

The client program will then run DRSUpdater.exe and immediately shutdown. DRSUpdater.exe will then wait for a short period of time for the original program to close down.

It will then copy the file from the upgrade directory to the executable directory. It will then start the original program again.

Example:

The executables are stored in c:\drsapps

The update files are stored in c:\drsapps\updatefiles

The user runs DataEntryBasic.exe LOCATION but there is a new version available.

The client program will run c:\drsapps\DRSUpdater.exe and then shutdown.

DRSUpdater.exe will copy c:\drsapps\upgrade\DataEntryBasic.exe to c:\merchant\DataEntryBasic.exe

DRSUpdater.exe will run c:\drsapps\DataEntryBasic.exe LOCATION and then close itself down

You can check the version by Pressing Help – About. The About screen tells you which version you are running.

Figure: Example About Screen

How do the POS Clients Upgrade

Same as for Back Office programs DynaPOSTouch will follow the same process. POS will check the \drsapps\posupgrade folder for new programs unless a notify upgrade has been initiated prior to the application server upgrade it will look in the upgrade folder on the POS itself. For POS upgrades it is recommended to reload the POS from Till Control to jumpstart the download of the new version as mentioned above.

Figure: Example Till Control Screen

Whether the upgrade was successful can be checked in Till Control.

Figure: Example Till Control Screen Showing POS Version

OR on the bottom right of the POS itself.

Figure: POS Version

Converted from CHM to HTML with chm2web Pro 2.85 (unicode)