Table of Contents

1. General mechanism


1.1. General rules

1.1.1. RK7 applications are protected with PC hardware, corporation and restaurant code, Guardant key, time -depended sub-license key.

1.1.2. Report server and cash server can’t function without Guardant protection key (and valid sub-license code in case of midserv.exe).

1.1.3. Sub-License is generated for every cash server (and report server only if you need repot functions work: data gathering and manager station connection are protected).

1.1.4. You generate new license for every cash server and prolong it after it expires (if necessary and if license is not unlimited).

1.1.5. Every master-license request should be approved in UCS Moscow office licensing manager (exception: SOS-codes).

1.1.6. You should create license request (on UCS site or in LicenseManager) at least 2 days before installation.

1.1.7. Also you should send to licensing responsible person information about Guardant keys, Corporation and restaurant and hardware: what keys (key numbers) will be used in each particular restaurant. This info also should be sent at least 2 days before installation. There is a standard Excel form, which is more preferable.

Note: if you create license request and don’t send required information in e-mail to UCS, this license request will be ‘refused’.

1.1.8. If you need new license urgently and have no time to wait until we approve your request (for example, it is weekend, or in some really urgent cases), you can generate license yourself using SOS code. The difference between SOS-code and “usual license” is that SOS-code is generated only for 1 month and does not need approving from our side. There is also a limitation on number of SOS-codes that can be created on our site. If you exceed the limit, you won’t be able to create more SOS-codes.

1.1.9. There is two-level licensing, it has: Master level (UCS head office approves) and Sub level (Dealer generates them). In software you use ONLY sub-license. Master license exists only in licensing system.
1.1.10. Cash server license protects number of cash stations connected to that cash server. Report server license protects number of manager stations connected to that report server.
1.1.11. Only Cash server and Report server licenses in RK7 system are linked with Gurdant key number. This key must be plugged in that computer where you run corresponding server (not station!).

1.2. Change of existing license

1.2.1. Existing license should be changed in case:

* Number of cash stations changed.

* Guardant USB key was changed (for example, after it was broken or lost).

* Hardware on computer (where reference server is installed) was changed.

Note:Re-installing operation system on computer (where refserver is installed) in general case doesn’t affect license, so you don’t need to re-generate license.

1.2.2. You have to change both master license (change station quantity, extend validity period) and sub-license or sub-license only (change Gurdant key, change Reference server PC hardware).
1.2.3. If you want to change Master license, you must use NEW request option always.
 

1.3. “History” of licensing in RK7

* Version 7.0.20.10 and higher – licensing of midservers was added
* Version 7.1.XX.XX and higher – ability to clear old license in database, if enterprise or restaurant code is changed.
* Version 7.1.7.0. and higher – ability to re-generate license request code without selecting type of request (just command “Generate license request” for midserver).
* Starting from May 2009 – License manager utility with ability for dealers to generate master licenses (unlimited) and inside them generate licenses for particular period of time.
* From October 2009 – site http://support.ucs.ru:8080/rkeeper-license/rk7lic/login.jsp with control of sub-licenses.
* 2013 - l.ucs.ru site started
 

1.4. Main license sources

There are 3 main license sources, where you can create license requests and generate licenses (sorted by date of creation):
1. Site1: http://support.ucs.ru:8080/rkeeper-license/
2. License Manager (can be downloaded from FTP: /dealers/rk7/ForDealers/lm/)
3. Site2: http://support.ucs.ru:8080/rkeeper-license/rk7lic/login.jsp
Differences in abilities are shown in table below:
 
 
1
2
3
1
Search by:
 
 
 
 
corporations
+
+
-
 
objects (=restaurants)
+
+
+
 
requests
+
+
-
2
Create new:
 
 
 
 
corporation
+
+
-
 
object (=restaurant)
+
+
-
 
request
+
+
+
3
New request for:
 
 
 
 
master license
+
+
-
 
change dealer
+
+
-
 
change station count
+
+
-
4
Generate SOS-code
+
+
+
5
Generate sub-license:
 
 
 
 
new sub-license
-
+
+
 
prolong sub-license
-
+
+
 
change key
-
+
+
 
change hardware
-
+
+
6
Edit dealer info
+
+
-
7
Edit corporation / restaurant info
+
+
-
8
Delete new requests
+
+
-
9
View licensing history:
 
 
 
 
approved master licenses
+
+
-
 
generated SOS-codes
+
+
-
 
generated sub-licenses
-
+
-
 
Note: abbreviations ‘Site1’, ‘LM’ and ‘Site2’ will be used below.
 
 
* Browser ‘Mozilla Firefox’ is the most preferable for both sites.
* Utility LM.jar requires Java 5 and higher, installed on computer.
 
 

1.5. Viewing dealer info

1.5.1. Site1

* Press on button ‘Home’ (in the left top part of window).
* Number of generated SOS-codes is displayed in corresponding section.
* Also you can edit dealer’s and employee’s contact information.
Note: if you want to receive information about soon license expiration, add email in field ‘Dealer contact information’ (Attention! Dealer, not employee).

1.5.2. Utility LM.jar

* Press on button ‘Home’ (in the left top part of window).
* Number of generated SOS-codes is displayed in corresponding section and also in tab ‘SOS-codes’.
* Also you can edit dealer’s and employee’s contact information.
Note: if you want to receive information about soon license expiration, add email in field ‘Dealer contact information’ (Attention! Dealer, not employee).
 

1.5.3. Site2

There is no ability to edit dealer info.



2. Request code for generating licenses


2.1. Description

Every license is generated on base of request code. Request code is taken from manager station and contains information about:
* corporation code
* restaurant code
* USB key number
* hardware info
Note: information about hardware is taken from computer, where refserver is installed, so if you change motherboard or hard-drive, license should be regenerated.

2.2. Direct connection

On manager station:
1) Service --- Stations and devices --- Properties of midserver --- License information section
2) Choose USB key number (more information – in installation manual)
3) Press ‘Save’ to save changes
4) Right-click on midserver in the list:
* in ‘current’ versions: Actions --- Generate license request

Note: license request is the same for new license, prolongation license or hardware change. It differs only in case you change key and generate license request code for another key.
* in ‘stable’ versions: Licensing --- First activation / License change
Note:
* if you create midserver from zero, you should choose ‘First activation / License Change’
* if you want to prolong license, you should choose ‘First activation / License Change’
* if you changed key, you should choose ‘Protection key changed’  )))
* if you changed hardware on computer, where refserver was installed, you should choose ‘System Configuration Changed’

2.3. Curtail connection

2.3.1. When using local report servers as reference source for cash servers you have to generate extended key codes on cash servers.
2.3.2. Start doscs.exe or midserv.exe with "/listKeys" parameter once (in order not to wait for key check on each start).
2.3.3. Find lines begin with "5242" in midsrv.stk.
2.3.4. Those lines should look like:

16.05 17:49:11
5242:listKeys: key 2 of 2, (244B6D4B-608922955-ZYATMWKI)

2.3.5. Take those codes in brackets to manager station "Protection Key Actual Number" property (use "..." button to insert the code).
2.3.6. Generate license request as usually.


3. Master licenses and sub-licenses


3.1. General information

Master-license contains several sub-licenses inside.
All summary sub-licenses inside master-license can not exceed:
* date of master-license expiration
* total station count in master license
 
So you can generate several sub-licenses inside master license for different terms, for example:
Master license 17.10.2009 - 31.12.2009
sub-license 1
sub-license 2
sub-license 3
17.10.2009 - 17.11.2009
17.11.2009 - 31.11.2009
31.11.2009 - 31.12.2009
 
Also you can generate different sub-licenses for several keys inside master-license (summary amount of stations in sub-licenses = 5 + 3 + 2 = 10, this amount can not exceed total amount of stations in master-license):
Master license for 10 stations
sub-license 1
sub-license 2
sub-license 3
midserver 1
midserver 2
midserver 3
key1
key2
key3
5 stations
3 stations
2 stations
 
Sub-licenses for ShowRoom for several employees are also generated for summary amount of stations in master-license (3 + 1 + 1 = 5);
Master license for ShowRoom for 3 employees (summary 5 stations)
sub-license 1
sub-license 2
sub-license 3
Employee1
Employee2
Employee3
midserver 1
midserver 2
midserver 3
key1
key2
key3
3 stations
1 station
1 station
 

3.2. How to create request for master-license

Approximate sequence of actions (more detailed – please see below in p.5 - Working with requests)
1) Create new object (=restaurant) or find already existing, add new license request for it.
2) In request for this object fill:
* Reason = Master license
* Period of licensing
* Station count
3) Press button “Apply” to save request.


4. Search


4.1. On Site1

Choose search details on left panel and click ‘Search’
Search can be made by:
* corporations (by name or by code)
* restaurants (by name or by code)
* license requests (by date, request ID, object name or object code. Also you can filter by request status – new, generated, approved, etc)
 
Search results are shown in central part of the screen.
If you make search by requests, they can be colored in:
* green (new request)
* yellow (approved request)
* white (approved request or approved master-license)
* red refused request)
 
If you make double-click on request, you will see its properties.

Already approved requests will have mark

inside it (# XXXX on the right – number of request on site)
 

Refused requests will have mark

inside (# XXXX on the right – number of request on site)
 

Approved requests for master license has value ‘MASTER LICENSE’ in property ‘Activation code’

4.2. in LM.jar

Search can be made by:
* corporations (by name or by code)
* restaurants (by name or by code)
* license requests (by date, request ID, object name or object code. Also you can filter by request status – new, generated, approved, etc)
 
Search by requests are divided in tabs (by request reasons – new license, generate SOS-code, etc)

Requests can be colored in:
* green (new request)
* white (approved request or approved master-license)
* red refused request)

4.3. On Site2

Enter part of name or code and press on corresponding button.

Navigation on site is made via buttons ‘Forward’ and ‘Backward’ of your browser.

If restaurant has already approved master-license, it has white square in column ‘Master-license’:


5. Working with master-license requests


5.1. New master-license request for new corporation and new object (=restaurant)

5.1.1. Site1

1) Press on button ‘Create license request’ in the upper part of the screen.
2) Choose mode: “New object and new corporation” and press ‘>’
3) In next window fill information about corporation (address, contact phones, name, etc).
4) In next window fill information about object (=restaurant) and press ‘>’
Note:
* names of restaurant and corporation should be the same as in xls-file, that you send to Gulnur.
* if you create ShowRoom, put tick in property ‘ShowRoom’
* usually fields ‘Object name’ and ‘Legal name’ are the same.
5) In next window fill information about request:
* put tick in property ‘Generate new code for corporation’
* put tick in property ‘Generate new code for object’
* reason = ‘Master license’
* choose station count
* choose period
6) Press ‘Apply’ to save request. After we approve this request, you’ll be able to generate sub-licenses inside this master-license.

5.1.2. Utility LM.jar

1) Press button ‘New request’ in the main window of utility.
2) Choose mode: ‘New object and new corporation’ and press ‘Next’
3) In next window fill information about corporation (address, contact phones, name, etc).
4) In next window fill information about object (=restaurant) and press ‘Next’
Note:
* names of restaurant and corporation should be the same as in xls-file, that you send to Gulnur.
* if you create ShowRoom, put tick in property ‘ShowRoom’
* usually fields ‘Object name’ and ‘Legal name’ are the same.
5) In next window fill information about request:
* put tick in property ‘Generate new code for corporation’
* put tick in property ‘Generate new code for object’
* reason = ‘Master license’
* choose station count
* choose period
6) Press ‘Apply’ to save request. After we approve this request, you’ll be able to generate sub-licenses inside this master-license.

5.1.3. Site2

There is no ability to create new corporation and new object.

5.2. New master-license request for new restaurant in already existing corporation

5.2.1. Site1

1) Make search by corporations and find necessary corporation (by name or by code). Choose it in central part of the screen (with search results) and press button ‘Add license request’.
2) In next window fill information about object (=restaurant) and press ‘>’
Note:
* names of restaurant should be the same as in xls-file, that you send to Gulnur.
* if you create ShowRoom, put tick in property ‘ShowRoom’
* usually fields ‘Object name’ and ‘Legal name’ are the same.
3) In next window fill information about request:
* put tick in property ‘Generate new code for object’
* reason = ‘Master license’
* choose station count
* choose period
4) Press ‘Apply’ to save request. After we approve this request, you’ll be able to generate sub-licenses inside this master-license.

5.2.2. Utility LM.jar

1) Make search by corporations and find necessary corporation (by name or by code). Choose it in search results, make a right-click on it and choose ‘New request’.
2) In next window fill information about object (=restaurant) and press ‘Next’
Note:
* names of restaurant should be the same as in xls-file, that you send to Gulnur.
* if you create ShowRoom, put tick in property ‘ShowRoom’
* usually fields ‘Object name’ and ‘Legal name’ are the same.
3) In next window fill information about request:
* put tick in property ‘Generate new code for object’
* reason = ‘Master license’
* choose station count
* choose period
4) Press ‘Finish’ to save request. After we approve this request, you’ll be able to generate sub-licenses inside this master-license.
 

5.2.3. Site2

There is no ability to create new object (=restaurant).
 

5.3. New master-license request for already existing restaurant and corporation

5.3.1. Site 1

1) Make search by objects (=restaurants) and find necessary object (by name or by code). Choose it in central part of the screen (with search results) and press button ‘Add license request’.
2) In next window fill information about request:
* reason = ‘Master license’
* choose station count
* choose period
3) Press ‘Apply’ to save request. After we approve this request, you’ll be able to generate sub-licenses inside this master-license.

5.3.2. Utility LM.jar

1) Make search by objects (=restaurants) and find necessary object (by name or by code). Choose it in search results, make a right-click on it and choose ‘New request’.
2) In next window fill information about request:
* reason = ‘Master license’
* choose station count
* choose period
3) Press ‘Finish’ to save request. After we approve this request, you’ll be able to generate sub-licenses inside this master-license.
 

5.3.3. Site 2

There is no ability to create new request for master-license.


5.4. How to generate SOS-code for already existing object (=restaurant)

In urgent cases, when there is no time to wait until UCS Moscow approves your request, you can generate SOS-code for 1 month for existing restaurant.

5.4.1. Site1

1) Make search by objects (=restaurants) and find necessary object (by name or by code). Choose it in central part of the screen (with search results) and press button ‘Add license request’.
2) In next window fill information about request:
* reason = ‘Generate SOS-code’
* choose station count
* choose period
* fill field ‘Request code’ (also see p2. -  Request code for generating licenses)
3) Press ‘Apply’ to save request.
4) Choose search by request. Find this request, make a double-click to open and press on button ‘Generate’. Copy-paste info from field ‘Activation code’ to manager station.
 

5.4.2. Utility LM.jar

1) Make search by objects (=restaurants) and find necessary object (by name or by code). Choose it in search results, make a right-click on it and choose ‘New request’.
2) In next window fill information about request:
* reason = ‘Generate SOS-code’
* choose station count
* choose period
* fill field ‘Request code’ (also see p.2 -  Request code for generating licenses)
3) Press ‘Finish’ to save request
4) In main window of LM.jar choose ‘Requests’ à ‘Search’, switch to tab ‘Generate SOS-code’, make a double-click on your request and press button ‘Generate’. Copy-paste info from field ‘Activation code’ to manager station.

5.4.3. Site2

1) Make search by name or code and find necessary object (=restaurant).

2) Press on square button ‘Generate SOS’ in last column

3) In next window fill information about request:
* station count
* request code (also see Request code for generating licenses)
4) Press on button ‘Generate code’


6. Sub-licenses inside master-license


6.1. New sub-license inside approved master license

Before trying to generate sub-license, make sure that UCS Moscow has already approved your license request (please see p.4 - Search).

6.1.1. Site1

It does not have ability to work with sub-licenses.

6.1.2. Utility LM.jar

 
1) Make search by objects (=restaurants)
2) Make a right-click on necessary object in search results and choose ‘Properties’
3) On tab ‘Active licenses’ make a right-click on “R-Keeper 7 Stations in the list” and choose ‘Add license’

4) In next window fill information about request:
* Reason = ‘New license’ (chosen by default)
* choose station count
* choose period
* fill field ‘Request code’ (also see Request code for generating licenses)
5) Press on button ‘Generate’
6) Copy-paste info from field ‘Activation code’ to manager station

6.1.3. Site2

1) Make search by code or by name

2) Press on white square button in column ‘Master-license’:

3) Press on button ‘New license’
4) In next window fill information about request:
* choose station count
* choose period
* fill field ‘Request code’ (also see Request code for generating licenses)
5) Press on button ‘Generate code’

6.2. Prolong sub-license

Prolongation of sub-licenses is used, when sub-license’s term has expired and you want to prolong it.
Note: it can be prolonged on term not greater than expiration date of master-license.
If you master-license itself has expired, please see 7 Prolong master license

6.2.1. Site1

It does not have ability to work with sub-licenses.

6.2.2. Utility LM.jar

1) Make search by objects (=restaurants)
2) Make a right-click on necessary object in search results and choose ‘Properties’

3) On tab ‘Active licenses’ make a right-click on “R-Keeper 7 Stations in the list” and choose ‘Renew’

4) In next window fill information about request:
* Reason = ‘Prolongation license’ (chosen by default)
* choose period
* ‘Request code’ will be filled automatically (also see Request code for generating licenses)
5) Press on button ‘Generate’
6) Copy-paste info from field ‘Activation code’ to manager station
 

6.2.3. Site2

1) Make search by code or by name
2) Press on white square button in column ‘Master-license’

3) In next window you’ll see table of all generated sub-licenses. Choose necessary sub-license and press button

4) In next window fill information about request:
* choose station count
* choose period
* fill field ‘Request code’ (also see Request code for generating licenses)
5) Press on button ‘Generate code’

6.3. Sub-license for hardware change

* Information about hardware (of computer, where refserver is installed) is used in generating request codes. If you change motherboard or hard-drive, license should be re-generated.
* Re-installing Windows usually does not affect license.

6.3.1. Site1

It does not have ability to work with sub-licenses.

6.3.2. Utility LM.jar

1) Make search by objects (=restaurants)
2) Make a right-click on necessary object in search results and choose ‘Properties’
3) On tab ‘Active licenses’ make a right-click on “R-Keeper 7 Stations in the list” and choose ‘Change hardware’

4) In next window fill information about request:
* Reason = ‘Change hardware’ (chosen by default)
* fill field ‘Request code’ (also see Request code for generating licenses)
5) Press on button ‘Generate’
6) Copy-paste info from field ‘Activation code’ to manager station

6.3.3. Site2

1) Make search by code or by name
2) Press on white square button in column ‘Master-license’

3) In next window you’ll see table of all generated sub-licenses. Choose necessary sub-license and press button

4) In next window fill field ‘Request code’ (also see Request code for generating licenses)
5) Press on button ‘Generate code’

6.4. Sub-license for key change

General rules:
* If key in restaurant was broken or you want to change key for any other reason, you should make new request on key change.
* At the same time you should obligatory write technician, that there was a key change in particular restaurant.
* Key change requires 1 free SOS-code (so if you have 10 of 10 SOS-codes generated, you should write us and ask to delete SOS-code). This ‘key change’ license is generated only for 1 month (as usual SOS-code).
* Obligatory ask Gulnur to annul license for ‘old’ key.
* After license for ‘old’ key is annulated, generate new sub-license with reason = ‘New license’ (also see - 6.1. New sub-license inside approved master license)
 

6.4.1. Site1

It does not have ability to work with sub-licenses.

6.4.2. Utility LM.jar

1) Make search by objects (=restaurants)
2) Make a right-click on necessary object in search results and choose ‘Properties’
3) On tab ‘Active licenses’ make a right-click on “R-Keeper 7 Stations in the list” and choose ‘Change key’

4) In next window fill information about request:
* Reason = ‘Change key’ (chosen by default)
* fill field ‘Request code’ (also see Request code for generating licenses)
5) Press on button ‘Generate’
6) Copy-paste info from field ‘Activation code’ to manager station

6.4.3. Site2

1) Make search by code or by name
2) Press on white square button in column ‘Master-license’

3) In next window you’ll see table of all generated sub-licenses. Choose necessary sub-license and press button

4) In next window fill field ‘Request code’ (also see Request code for generating licenses)
5) Press on button ‘Generate code’

6.5. Sub-license for station count change

There are 2 different situations with station count changes:
1) changing ‘global’ station count in master license, that is given for the whole restaurant
See p.8 Change station count in restaurant for more information.
2) changing station count for particular midserver in sub-license for this midserver.
See below:
 

6.5.1. Site1

It does not have ability to work with sub-licenses.
 

6.5.2. Utility LM.jar

1) Make search by objects (=restaurants)
2) Make a right-click on necessary object in search results and choose ‘Properties’

3) On tab ‘Active licenses’ make a right-click on “R-Keeper 7 Stations in the list” and choose ‘Change station count’

4) In next window fill information about request:
* Reason = ‘Change station count’ (chosen by default)
* choose new station count
* ‘Request code’ will be filled automatically (also see Request code for generating licenses)
5) Press on button ‘Generate’
6) Copy-paste info from field ‘Activation code’ to manager station


7. Prolong master license


If your master-license has expired, you should create new request for new master license.
For more info please see - 5.3 New master-license request for already existing restaurant and corporation

8. Change station count in restaurant


General rules:
1) obligatory send to Gulnur (gulnur@ucs.ru) information about changed station count (in standard xls-file), so that she’ll add it in our restaurants database. Otherwise your license request will be ‘refused’.
2) Create new request for new master-license (please see - 5.3 New master-license request for already existing restaurant and corporation)
In this new request in property ‘Station count’ choose new number of stations.
Note: if station count is decreased, old key should be returned.

9. Change dealer code


1) When user first logs in on manager station as RK7 XXX (where XXX is dealer code) in new database, he becomes ‘maintaining’ dealer of this database. So that dealers from other countries can not open this database.
Example: if rk7.udb was created by COUNTRY1 dealer and after that dealer from COUNTRY2 takes the same database and runs manager station on his side, he’ll not be able to log into manager station, using COUNTRY2 dealer ID and password. Error message, that dealer with COUNTRY2 code can not maintain COUNTRY1 database, will be shown.
2) You should create request for dealer change.
3) After we generate dealer change code, you can log in to manager station with this code and it will change ‘maintaining’ dealer of database:
RK7 XXX YYYYYYYYYYYYYYYYY, where
        XXX – dealer code,
        YYYYYYYYYYYYYYYYY – code of dealer changing (that we generate).

9.1. Site1

1) Make search for necessary restaurant (by name or by code)
2) Select it in search result areas and press button ‘Add license request’
3) In new request fill reason = ‘Change dealer’ (no more information is needed).
4) Press ‘Apply’
 

9.2. Utility LM.jar

1) Press on button ‘Objects’. Make search for necessary restaurant (by name or by code)
2) Select it in search result areas, make a right-click on it and select ‘New license request’
3) In new request fill reason = ‘Change dealer’ (no more information is needed).
4) Press ‘Finish’
 

9.3. Site2

There is ability to change dealer code.


10. Difficult situations


10.1. Key in the restaurant was broken

You should create request for key change
Please see: 6.4. Sub-license for key change
 

10.2. License is needed urgently

If you don’t have time to wait several days until we approve your request, you can generate SOS-code.
Please see 5.4. How to generate SOS-code for already existing object (=restaurant)
 

10.3. We want to decrease number of stations in restaurant

If you want to decrease station count in restaurant, old key should be returned.
Please see: 8 Change station count in restaurant
 

10.4. We want to increase number of stations in restaurant

License should be re-generated.
Please see: 8 Change station count in restaurant

10.5. New restaurant worked on SOS-code, now ‘normal’ license is needed

You should create new master-license request..
Please see: 5.3 New master-license request for already existing restaurant and corporation

10.6. Master-license has expired

You should create new request for new master-license.
Please see: 7 Prolong master license

10.7. How to clear all information about license in rk7.udb

Starting from version 7.1.XXX you have ability to clear old license for your midserver.
Just change corporation code or restaurant code and agree with message, that old license will be cleared.
Note: if you clear license on midserver, you are able to generate only ‘New license / License Change’ in ‘stable’ RK7 versions.

10.8. We bought extra PDA and want to use it in restaurant

PDA is treated as cash station in RK7, so you should re-generate license (station count increased).
Additional information:
* 8 Change station count in restaurant
* 11.2. PDA


11. Licensing of additional modules (software) and interfaces


11.1. Webmonitoring

11.1.1. General rules

* web-monitoring license is needed only in ‘current’ versions of RK7 (starting from version 7.1.5.0.)
* you do not need license in ‘stable’ versions of RK7
* there is no request code for web-monitoring, we just generate license on base of corporation and restaurant codes
* key number is not used in web

11.1.2. Making request (only on Site1 and in utility LM.jar)

Process of creating request is like for usual master-license:
* make search by restaurant
* add license request for it
* Software name = ‘RKeeper 7 Web Monitoring’
* Reason = ‘New license’
* no other information is needed (leave station count 1 by default, do not fill request code)
* copy-paste info from field ‘Activation code’ on manager station (see below)
 

11.1.3. Saving activation code on manager station

On manager station received license key for web-monitoring is entered in properties of restaurant:

Service --- Stations and devices --- Properties of restaurant --- License information

11.2. PDA

11.2.1. MobileWaiter7

Read information here: http://support.ucs.ru/node/5067

11.2.2. Obsolete version (KDSTerm)

11.2.2.1. Every PDA has its unique ID and connects to midserver like usual cash station (pocket station). While trying to connect to midserver, PDA sends its ID to RK7, and RK7 launches cash station for this ID (via settings in rkloader.ini) and transfers graphic to this PDA, so that on PDA screen you see cash station interface.
11.2.2.2. In License Manager create new Master License for PDA. Create New subLicense inside and as a Request Code enter Request Code you used for usual Cash Stations (Cash server Guardat key is used). Enter License Code in Licensing - Pocket Devices. Make sure that you Cash Server license supports additional stations (because every PDA is treated as cash station and formula is – Total Cash Stations on Cash Server = Cash Stations + PDA Stations).
ATTENTION! It was made for version 7.1.20.0 and later. Make sure, that you loaded latest KDSTerm.exe on your PDA.

11.3. Reservation system

1) License for reservation system is based on USB key number, which is plugged into your computer. So you can move this system from computer to computer, if you unplug the key from "old" computer and plug it to "new".

2) If you re-install Windows or change hardware of computer, it will not affect license of reservation system, because it is based only on USB key.
3) If several keys are plugged, remove all of them except one key, on which you want to base your license for reservation system. After reservation system key is generated by LUpdater.exe, you can plug back to computer all USB keys.
 
Run file LUpdater.exe, press button Read. Field Key will be filled with generated key.
 

Send this key to technician. Your email should contain:
1) restaurant name (in this case, when you are only testing reservation system, please write, that it is your ShowRoom).
2) key, which was generated by LUpdater.exe.
 
After license will be generated, Gulnur will send it to you.
You add license code in the field of LUpdater.exe (in the bottom, on screenshot it is line with zeros - 00000000000000000) and press the button Write.
 
Note: don’t be afraid, that key in field “Key” is changing. Only 2 first digits change (they stand for current date), other digits remain the same.
 

11.5. SaveOrder XML interface

11.5.1. This license protects only Save order related xml interface (cash server) querries.

11.5.2. You have to put license code to the restaurant properties.