Setup of Reference Server

Introduction

The main server of r_keeper 7 system, or a root server, is the Reference server. It is launched first at system setup.

The Reference server executable file is REFSRV.EXE, the default config file name is RK7SRV.INI.

When RK7 is being installed from the distribution kit (the archive is at ftp in ftp.ucs.ru/versions folder), the RK7SRV.INI file needs to be copied from the \bin\win\ini\ folder into the \bin\win\ wording folder containing REFSRV.EXE.

If the software is being installed via the installer, the server with config file is located in [installation path\instance name\Rk7Reference] folder.

Licensing

If you need to view the reports, the Reference server should be licensed. License is associated with a full object code, a key code, and hardware components of the machine where the server is installed.

To license the Reference server:

1. Specify the corporation code in the parameters.

   Click here to see more information on the corporation code

   1. Specify the Corporation Code from the licensing system into the Enterprise Code parameter. To do that, go to Settings > Parameters > Installation and enter the number into the Integer field. 
      
   2. The Object code from the license system should be specified in the restaurant properties.
      To do that, go to Service > Stations and Devices and select the required restaurant.
      
   3. Enter your object code in the Code field.
   4. Confirm and save the changes.

2. Go to Settings > OLAP reports > Reporting servers.
3. Select the Reference server, expand the «License information» properties group.
4. Select the protection key. The key can be either virtual or physical. The Guardant driver is necessary for licensing with the physical keys.
   Starting from version 7.06.05.399, a virtual protection key is used by default. If you want to use a virtual key, it should be generated:
   1. Select the required reference server and field in the Handles restaurant field in the Basic section
   2. Save the changes
   3. In the License information section left-click on the Protection Key Actual Number field.
   4. Press the button to generate the key code and click OK.
      
      
      
      
   5. The key code will appear in the Protection Key Actual Number field.
      

5. Generate a license request. Right-click on the server > Actions > Generate License Request.

6. Generate the requested license in the license system. The objects shall have a master license with RKeeper 7 Reporting server software type.

7. Enter it into the License key field.

8. Save changes.

Reference server licensing with virtual key

Fill in the Handles restaurant field (mandatory). This must be a restaurant other than the Head office.

If your r_keeper version is below 7.06.05.399, specify the following parameter in rk7srv.ini before virtual key generation:

[REFSERVER]
UseNetChecking=1

And restart the Reference server.

Launch 

Before the server is launched, perform the following:

1. Modify RK7SRV.ini file: in the [Refserver] section, specify the server name (Server) and add the UseSql parameter if not any:

Server = RK7SRV_3001 ; Reference server network ID

UseSql = 0           ; since there is no connection to external database yet

See more details on other rk7srv.ini file parameters below.

2. Run the server.

This application can be launched either as a separate service, or as an application.

The first launch shall always be performed as an application. To do that, create the refsrv.exe shortcut and insert the /desktop parameter in the Target field.

Also, make sure to perform the launch as administrator.

After the server is launched as an application, the icon will appear in Wndows task bar.

Depending on the task being performed, the server icon can be of three colors:

• green - normal server operation;
• yellow - data processing (loading, editing, cubes re-calculation, etc.), the server is loaded;
• red - the server is stopped.

Double-click on the icon to open the Server information window.

To install the server as a service, just double-click the Refsrv.exe file, and follow dialog instructions, or launch the server with /install parameter. After the service is installed, it needs to be launched.

Note that r_keeper 7 services should be launched from the account with administrator rights.

Using of password policy

Starting with versions 7.7.0 and 7.6.5.483 the new Use password policy parameter is added.

This parameter may be set in 2 places:

• in the refsrv.ini file of the reference server
• in the manager station. In this case the setting from the INI file prevails over the value in the manager station.

To turn this parameter on in the INI file, add the [CONFIG] section and specify the UsePasswordPolicy=1 parameter as shown bellow:

[CONFIG]
UsePasswordPolicy=1

Setup of connection to external DB

To make it possible to view OLAP reports in the manager station, set up a connection to external SQL DB, as described in the Setup of connection to MS SQL article.

To configure interactive reports, see the Setup of interactive reports plugin article.

Reports are generated based on the data collected from the cash server only after common shift is closed at the cash station.

Reference server settings description

To translate reference data:

1. In [REFSERVER] section, enter primary and alternative language file names.

[REFSERVER]

MainLang=.\RefSrv.DEU ; primary language

AltLang=.\ RefSrv.PLK ; alternative language

To translate primary language:

UpgradeTranslateRussian=0 ; 0 - translation from English, 1-translation from Russian

To translate alternative language:

UpgradeAltTranslateRussian=0 ; 0 - translation from English, 1-translation from Russian

2. UPGRADE.DEU2. Using Langer.exe program (can be downloaded from FTP), translate the files from /base folder.

UPGRADEDEV.DEU
These files are created automatically after you perform paragraph 1 and update the program.

Attention! To restore default settings for different drivers, do the following:

Go to base\drvlocalize and run Defparam.exe by selecting defparams.rus from the list (for versions below 7.5.2.269, see readme.txt in the same folder).

Default driver settings will be specified. This is particularly important for universal foscal register drivers.