Page History

This way of interacting with the XML interface is not recommended due to lack of authorization.

The XML interface works

via the iTCPXML.dll driver. When working with the XML interface via rk7xml.dll, in addition to the settings described above, you must manually add the interface to the

cash server:

1. Go to

1. Service > Stations and Devices
2. Select a required restaurant and go to

1. its cash server
2. On the

1. Drivers tab, add the XML Interface For Windows driver
2. Write the port in the Port parameter
   Image Added
3. Bind the added interface to a logical interface in the

1. Service > Interfaces

1. reference.
   By default, the system

1. already

1. has a pre-installed XML interface with code 104. For each external application, you can make a copy of this interface and

1. bind it with the driver on the

1. cash server

1. 
   Image Added
2. After binding the interface, restart the cash server. Check that the interface is loaded in the cash server properties
3. Start the cash server with the /desktop parameter and open its interface by double-clicking on its tray icon.
   The loaded interface should be visible on the Interfaces tab
4. Functions are called via RK7XML.dll, an interface module:
   
   1. CallRK7XMLRPC

1. 1. function
      

1. 1. Parameters:
      • AddressName

1. 1. • — address:port
      • Request

1. 1. • — XML ​​request
      • RequestSize

1. 1. • — XML ​​request length
      • ResultFile

1. 1. • — the name of the file where the result is written
      • ErrorBuf

1. 1. • — the place where connection errors are written
      • ErrorBufSize — ErrorBuf size
   2. CallRK7XMLRPCToStream function

1. 1. — similar to the function above, but its result is written to the IStream stream
      

1. 1. Parameters:
      • AddressName

1. 1. •  — address:port
      • Request

1. 1. • — XML ​​request
      • RequestSize

1. 1. •  — XML ​​request size
      • ResultStream

1. 1. • — IStream

1. 1. • — the stream where the result is transferred
      • ErrorBuf

1. 1. • — the place where connection errors are written
      • ErrorBufSize — ErrorBuf size
   2. The SetUseTempFileLimit function sets the file size limit if the result return time exceeds the threshold.

1. 1. The default value is 1000000ms
   2. GetDLLVersion function

1. 1. — returns the DLL version
   2. SetCryptKey function

1. 1. — sets the encryption key. It can be different for different cash servers, it is specified in the properties of the XML interface.

The current protocol version 2 assumes control over the execution of commands by the server. In the previous version, it was impossible to know if the last request is completed

in case there was a disconnect after the request started processing.

For this purpose, now there are new functions — GetLastXMLResult and GetLastXMLResultToStream

. If the response could not be sent after the request was completed, it is stored on the server until a special request is made when calling these functions or until the next request. If the response was successfully sent, it is not stored on the server. In any case, you can always find out the number of the last executed request for a particular ConnectName.

ConnectName

— an arbitrary Null-terminated string, a connection identifier
RequestNum

— a sequential number of the request, maintained for each connection identifier separately. You must pass 0, otherwise the passed request number will be used.

function CallRK7XMLRPC2(AddressName: PChar; ConnectName:PChar;

Parameters description:

• 127.0.0.1:1122

• — IP address and port to which the XML interface is configured in r_keeper 7
• xmlquery.xml

• — file name with XML request
• response.xml

• — the name of the file where the response should be written
• /pass:password

• — the password set in the XML interface in r_keeper 7

After execution, the utility will save the response from the r_keeper 7 XML interface to the response.xml file. To check the functionality and correctness of the settings, you can use the following query, which should be saved to the xmlquery.xml file:

<?xml version="1.0" encoding="UTF-8"?>

1. Service > Stations and Devices
2. Select a required restaurant and go to

1. its cash server
2. In the

1. cash server properties, in the HTTP Server section, specify the HTTP Log path and check the Log HTTP query and response checkbox:
   Image Added

1. Service > Stations and Devices
2. Select a required restaurant and go to

1. its cash server
2. On the

1. Drivers tab, select one of the XML Interface For Windows drivers
2. Expand the Options section and fill in the OutputDir parameter
   Image Added

Be sure to restart the cash server after the changes have been made.

Requests will be paired

— INxxxxx.XML and

OUTxxxxx.XML.

Additionally, you can enable the NoLogginQueries parameter

— it is responsible for disabling logging of the queries specified in the parameter. Specify the required requests in the field.