Documentation for POS Intellect 5.4. Documentation for other versions of Intellect is available too.
The MixForward utility settings are stored in the mixforward.exe.xml file that must be located in the same folder as the MixForward.exe executable file for utility’s correct operation. The configuration file can be edited using the text editor (for instance, Notepad).
The configuration file allows setting up the following processes:
- connecting to POS-terminal;
- processing the data transfer protocol from the POS-terminal;
- logging the routing process;
- forwarding data to the IP-address and port of POS-server;
- receiving titles from multicast titles broadcast.
The table describes the configuration elements of MixForward.
Element name | Element description | Element content | Element attribute | Attribute description | Value range |
InputPortType | POS-terminal data transfer protocol | Protocol name | - | - | RS232 – data transfer via COM-port UDP – data transfer using UDP TCP – data transfer using TCP/IP TCPCLIENT - data transfer using TCP/IP from remote Server |
ServerPort | Local port number, if InputPortType is TCP or UDP | Whole positive numbers | - | - | From 0 to 65535 |
MultiCast | Enables the function of receiving multicast messages | - | - | - | True – function of multicast messages receiving is enabled False – function of multicast messages receiving is disabled |
MultiCastIP | Address to which multicast messages from external POS program will be sent in case of the UDP interface is selected in InputPortType parameter | - | - | - | IP address to which the multicast messages sending is performed |
ProtocolName | Current data transfer protocol from the POS-terminal | Protocol name | - | - | Depends on the number of plug-ins linked to MixForward |
LogFileMaxSize | Maximum log file size, bytes | Whole positive numbers | - | - | - |
LogInput | Enables or disables the received data log | - | - | - | true - the log is enabled false - the log is disabled |
PingTime | The period of test package sending in seconds | - | - | - | Up to 60 seconds |
RS232_settings | COM-port settings if InputPortType is RS-232 | -
| PortName | Available COM-port name | Depends on the number of available ports |
BaudRate | Supported bit rate, bit/s | Depends on the number of supported bit rates | |||
RtsEnable | Enable RTS option | 0 – do not use RTS control signal 1 – use RTS control signal | |||
DtrEnable | Enable DTR option | 0 – do not use DTR control signal 1 – use DTR control signal | |||
MSMQ_settings | MSMQ settings if InputPortType is MSMQ | ReconnectTimeout | The time after which an attempt is made to restore connection, if messages are not received | Up to 60 seconds | |
NoTimeFilter | Enables or disables messages filtering by time | true - messages are filtered by time | |||
DeleteMessages | Enables or disables message deletion after they are read | true - messages are deleted | |||
Queue Path | Path to the queue | - | |||
Terminal | Number of the terminal that is inserted for the specified queue | - | |||
forwards | Sets the correspondence between the routing id and POS-server IP-address/port | - | ip | POS-server IP-address | Depends on the POS-server network settings |
port | POS-server port | Depends on the POS-terminal object settings | |||
id | Routing id | Depends on the routing id value in the data package. If the id=”*”, then data from all POS-terminals is redirected to the POS-server | |||
Note
If the events come in from several objects, the correspondence between the routing id and POS-server IP-address/port should be set for each of these objects. See the example below.
Important!