1. General information

1.1. RK7 uses network protocols to communicate between applications.

1.2. If default port is occupied by some other application, the system tries to use other free port. For some protocol types application won't start until free port set.

1.3. This manual is not about once-only export-import (files) operations described in .

1.4. You may use not only network communication between servers, but file exchage also.

2. Protocols

2.1. NetBios

2.2. IP

2.3. TCP


2.4.1. This is the main RK7 internal connection protocol that works over TCP.

2.4.2. In application .ini file you have section [TCPSOC] to set up this protocol working parameters.

3. Ports

3.1. Reference and report servers

3.1.1. 5160UDP is a default network name multicast port that is used in order to make other applications find the server by name over network.

3.2. Cash server

3.2.1. Most interfaces ports you have to set in RK7 manager station, others - in rkeeper.ini.

4. Addresses

4.1. There are some IP addresses that you are able to use in case of the same OS: loopback or localhost.

5. Files and folders

5.1. Reference and report server

5.1.1. Exchange folders are inside \BASE\ folder (which is set in server .ini file) or \BIN\WIN\BaseData\ (default  for report server - may be changed in server .ini).

5.1.2. There are 2 folder inside: \backups\ and \filesync\ involved in file exchanges. \filesync\  folder is the main one: you may find \incoming\ folder inside where the system puts accumulative data (shift.udb databases) before pumping them into accumulative DB. In case of file transfer or data exchange errors you have to put shifts to \incoming\ folder manually in order they been pumped (with overwriting if exist) to accumulative DB. In case of manual reference transfer you take them prepared (after running 'Сервис->Синхронизация->Сохранить справочники') from '\BASE\filesync\outgoing\database\' folder and put (transfer) to cash server '\MIDBASE\' folder .

5.2. Cash server

5.2.1. Exchange folders are inside \MIDBASE\ folder (default - may be changed in server .ini).

5.2.2. After closing shift, accumulative data being put to \MIDBASE\ForSend\ folder. You have to copy all 'shifts' from \ForSend\ to report server(s) in case of file exchange (see

5.2.3. If you sync references using file transfer, stop cash server before overwriting files and folders in \MIDBASE\. After starting cash server will get updated reference data.

5.3. Cash station

5.3.1. Cash station itself does not store reference or accumulative data (exception - currently open order).

6. Manager station settings

6.1. For data downflow

6.1.1. Data downflow is the references data transmission process (from reference server to cash station).

6.2. For data upflow

6.2.1. Data upflow is the accumulative data transmission process (from cash station to report server), attended by data gathering.

6.3. For connection test

6.3.1. If you want to show error message on cash station (on order payment), enable "monitor connection" parameter in [Synchronization] section of cash server properties.

6.3.2. In case of 6.3.1 you will get an error message on reference (report) server - cash server connection loose shown below.

7. Data gathering processes

7.1. Data gathering is a process of checking and saving data to accumulative databases.

7.2. Real time data gathering described .

8. Remarks

8.1. If you are sure about no changes in your static IP network, you'd better use [TCPDNS] links.

8.2. If you suffer from data exchange errors.