Introduction
Starting from r_keeper version 7.5.X, the cash server support for DOS is terminated.
By default, MIDSERV.EXE is the cash server executable file.
The default cash server configuration file is RKEEPER.INI.
To download a distribution kit, go to ftp://ftp.ucs.ru/rk7/versions/
Copy the RKEEPER.INI file from the \bin\win\ini\ folder to the working \bin\win\ folder, where MIDSERV.EXE is located.
When installing the software via an installer, the server with its configuration file can be found in the following folder: [installation path\instance name\Rk7MidServer].
Licensing
Important:
The cash server should be licensed. The license is linked to the full object code (9 digits) and the key code.
Before licensing a server, create it at the manager station in the «Service – Stations and devices» reference.
Note:
As an example, find a description of the cash server licensing procedure for the object (restaurant) with a full code 199990039. It is implied that an object with the code 199990039 has already been created at l.ucs.ru, and it has an active master license for the «r_keeper 7 Stations» software.
At the manager station, perform the following:
- Specify the corporate code (Options – Parameters – Installation – Enterprise Code – Integer).
- Specify the restaurant code (restaurant property «CODE») in accordance with the object credentials from l.ucs.ru.
- Select a protection key (Licensing - Common –> Protection key –> Actual number).
- Generate a licensing request (right-click the cash server icon –> Actions).
- Generate a license at l.ucs.ru and insert it in the «Licensing - Cash Stations –> License key» field.
- Save the changes.
Launch!
Important: before you launch the cash server, create it under the "Service – Stations and devices" directory at the manager station and perform the licensing.
Before the server is launched, perform the following:
- Create the server at the manager station under the "Service – Stations and devices" directory, assign a unique network ID to it, e.g. MIDSRV3001, set the status to "Active" and save the changes.
- License the server.
- In RKeeper.ini, specify the following parameters under the [Config] section:
- RefServer = RK7SRV ;; the name of the directories server, where the given cash server connects to (= Server parameter in RK7SRV.INI).
- Client = MIDSRV3001 ;; the cash server network ID according to item 1.
- Launch the server.
Important: the first launch should always be performed as an application (with the /desktop parameter). Also, make sure to perform the launch as administrator.
Both cash server and the directories server can be launched as a service. For this purpose, use the /install parameter.
After the server is launched as an application (midserv.exe /desktop), the systray will display the following icon: .
Launching multiple servers
Important: each cash server created at the manager station has its own catalog with the working database work.udb (the catalog path should be specified in the BasePath parameter), and its own ini file with a unique server name.
If you are planning to launch multiple cash servers, the following variants are possible:
Variant A — launching multiple servers with different ini-files from the same \bin\win folder.
A.1. Launching as an application:
midserv.exe /ininame:rkeeper1.ini /desktop — launching the 1st server
midserv.exe /ininame:rkeeper2.ini /desktop — launching the 2nd server
A.2. Installing a service:
midserv.exe /ininame:rkeeper1.ini /install — service installation for the 1st server
midserv.exe /ininame:rkeeper2.ini /srvname:midserver2 /install — service installation for the 2nd server Do not forget to set a new name for the service!
In each ini-file, you should specify a unique log file name for each server (ERRORLOG = midsrv.stk)
Variant B — laucnhing each server from a separate folder (copy of \bin\win).
B.1. Launching as an application:
c:\rk7\bin\win\midserv.exe /ininame:rkeeper.ini /desktop — launching the 1st server
c:\rk7\bin\win2\midserv.exe /ininame:rkeeper2.ini /desktop — launching the 2nd server
B.2. Installing a service:
c:\rk7\bin\win\midserv.exe /install — service installation for the 1st server
c:\rk7\bin\win2\midserv.exe /srvname:midserver2 /install — service installation for the 2nd server Do not forget to set a new name for the service!
Cash server INI-file description
[Config] — main section
In case of a cash desk server, this section should contain the cash desk parameters (see [Config] for a cash station).
CashServer = MIDSERVER — cash server network name
Client = MIDSERVER — same as above (for compatibility purposes); cash server network name
RefServer = RK7SRV — directories server network name
BasePath = ..\..\MIDBASE — working database path
Important: if multiple cash servers are used, each of them should have a unique folder, the name of which has to be specified in the corresponding INI file.
RECREATEBASE = 0 — if "1" is set, the working database is re-created at every launch; if "-1" is set, it will not be re-created even if the version changes.
ArchivePath = (BasePath + ‘Archive\’) — path to the bill archive
InterfacePath — path to interface DLLs
TwoFilesMode = 0 — if "1" is set, 2 files per collection are created, and then switched. It enhances the reliability, but also increases the file saving time. If you have a permanent access to the directories server, "1" does not make sense.
ShortTimeout = 20000 — the maximum time (ms), during which a network operation can be performed for a single item
LongTimeout = 100000 — the maximum time (ms), during which a network operation can be performed for a collection
StartLang = .\midserv.rus — cash server initial language, used to display errors that occur before the directories are loaded ("Unable to connect to the server", etc.); after the loading, the language will be taken from the "Language preferences" parameter group.
KeepModules = 0 — keep the module list loaded in the memory. Relevant for cash desk + server only. By default, it is "0" for the cash desk + server combination, and "1" for a simple cash server. If you are planning to connect cash stations via network to the cash desk + server combination, set "1".
FileSyncPath= (BasePath + 'Incoming\') — the path to the folder, from which synchronization files should be taken
ERRORLOG = midsrv.stk — error log
ErrorLogSize = 1048576 — error log size
AlwaysZOnCommonClose = 0 — whether the Z-report should be printed when the general shift is closed, even if there were no sales
DebugMessages = () — a comma-separated list of debug message codes
WarningDiskFree=209715200 — the maximum free disk space threshold, at which the message about an insufficient free disk space should be output
PollEvents=0 — whether the list of occurred directory changes should be periodically requested from the top-level server instead of synchronizing by events. For the directories server to store those changes in its .ini file, enable the parameter EventCachePath
PollRepeatTime=60 — the periodicity (s) of requesting the list of changes at Pollevents=1
For the purpose of solving the issue with paybindings.uni duplication, the following settings are provided:
NoUdbPacketMode — disable the batch mode when writing into work.udb. Implemented in 7.5.5.095, 7.5.6.037, 7.5.7.011
NoReuseUNI — disable the reuse of UNI, which have been released during the order calculation. Implemented in 7.5.5.095, 7.5.6.037, 7.5.7.011
ExceptOnCheckUNI — disable the software interruptions and write the events in a log (error 2220)
[NewBaseGenerators] — a section containing initial values of sequences (generators) for the new database
Important: this section is used during the creation of a new database only.
You can specify the initial values for the following sequences (generators):
OpLogGen = 0 — the internal number of an entry in the operations log (OperationLog table)
SendFile = 0 — the initial file number during the archivation of a file sent to the directories server (if the number is already used, the parameter value will be incremented)
VisitGen = 1000 — 2 least significant bytes of the internal visit number (2 most significant bytes are taken from the date)
CheckGen = 100000 — the number of the bill (CheckNum field)
CashInOutGen = 0 — the internal number (UNI field) of the deposit/withdrawal documents, the internal invoice number
InvoiceGen = 0 — the number of the invoice (InvoiceNum field)
KDSDishIDGen = 1 — the dish line identifier for KDS (KDSIdent field)
OrderSessGen = 1 — the global package identifier (UniqueID field)
PrintNumberGen = 0 — the printed bill number, if no fiscal printer or fiscal memory is used, and the "CommonPrintNumber" parameter is set to "True"
CommonShiftNumber = N — the number, from which the shift numbering should begin. This parameter is relevant, when you need to re-create a cash server, but the shift numbering should be continued. Tested for 7.5.4.174.
[NETKERN]
Protocols=TCPSOC.dll;localnet.dll
[TCPSOC]
PORT=2350 ;; the port for incoming connections
[TCPDNS]
;;An optional parameter; however, the connection will be faster, if it is set; the same is true for the cash desk
;;Sometimes necessary, if broadcast messages fail to pass, or the communication with the top-level server is performed via Internet
TEST_RK7SRV=127.0.0.1:3639
[UPDATE] — server update section
NoUpdate = "1";; Do not update this module and its dependent objects (dll, etc.).
Data synchronization
In the properties of a cash server at a manager station, there are parameters controlling data synchronization (top-down and bottom-up).
- Automatic update— update this application automatically
2. Online sales data — transmit the online sales data on level upper
3. Closed shifts data — transmit the closed shift sales data one level upper
4. Directories — update the directories data at this server
5. Module DBs — update application databases (required for updating clients one level lower)
Now, the options "Automatic update" and "Module DBs", as well as "Closed shifts data" and "Online sales data" are made dependent (i.e., if one parameter is missing, the other is missing as well, and vice versa). In future versions, they will probably work separately. The old "Online" ("Synchronization") flag has been kept, but it disables all kinds of synchronization at a time, even if new flags are set.
If you need to disable the online transmission of bills, but keep the data upload after the general shift is closed, there are three ways:
- Global: disable the "Online data collection" parameter.
- For the cash server: set the interval of sending online data at 00:00.
- For the reports server: set the interval of downloading online data at 00:00.
Important: starting from version 7.4.21.27, the "Test connection" property has been added to the cash server properties; it controls the output of the message informing of communication interruption between the cash server and the high-level server. By default, this check is disabled.
Features of configuring a server at a cash desk
- In DOS, launch the doscs.exe program.
- The rkeeper.ini settings see here: Config — main section
- In the PROTOCOLS parameter under the [NETKERN] section, specify the localnet.dll (except for the protocol to be used for the directories server communication)
- When configuring stations and devices at the manager station, you should specify identical (!) network names for the stations group and the separate station.
- For the purpose of using Preload at the stations connecting to doscs, set KeepModules=1