Go to documentation repository
Page History
The MixForward utility is configured using the mixforward.exe.xml configuration file. The configuration file should be is located in the same directory with the the MixForward.exe executable file. You can edit the configuration file using any text editor.
| Note | ||
|---|---|---|
| ||
When you update POS PSIM, the mixforward.exe.xml configuration file is overwritten and all settings are returned to default values. |
The configuration file allows you to set up the following processes:
- Connecting
- Connection to a POS terminal or third-party software.
- Processing of the data transfer protocol from the
- a POS -
- terminal. Logging the
- Maintaining routing process
- LOG files.
- Forwarding data to the IP -
- address and port of POS -
- server.
- Receiving the packages with titles
- captions from multicast titles
- captions broadcast.
The table describes the configuration elements of MixForward utility.
Element name | Element description | Element attribute | Attribute description | Value range | ||
InputPortType | POS-terminal Used data transfer protocol | - | interface from a POS terminal | NA | NA- | RS232 UDP TCP TCPCLIENT MSMQ PLUGIN WEBSERVICE JMS |
ServerPort | Local port number, if InputPortType is TCP or UDP | - | Number of a local port processed by the utility if UDP interface is selected in InputPortType | NA | NA- | From 0 to 65535 |
MultiCast | Enables the function of receiving multicast messages if the messages if UDP interface is selected in the InputPortType | -NA | - | NA | true—reception of True – function of multicast messages receiving is enabledFalse – function of false—reception of multicast messages receiving is disabled | |
| MultiCastIP | Address to which multicast messages from external POS program will be sent in case of the are sent if UDP interface is selected in InputPortType parameter | -NA- | NA | IP address to which the multicast messages sending is performedare sent | ||
ProtocolName | Name of the used data transfer protocol | -NA- | NA | -NA | ||
LogFileMaxSize | Maximum log file size, size of LOG files in bytes | -NA- | NA | -NA | ||
| LogInput | Enables or disables the log of received data log | -NA | - | NA | true—log of received data is enabled false—log of received data true - the log is enabled false - the log is disabled | |
| PingTime | The period of forwarding of a test package sending in seconds | -NA- | NA | Up to 60 seconds | ||
| PrivateLog | Enables or disables the creation of its own detailed log by the plugin (for debugging only!) | -NA | Not available for all plugins | true - the true—the plugin will keep its detailed log false - the plugin will not false—the plugin won't keep its detailed log | ||
RS232_settings | A group of elements. Specifies the settings of COM - port settings if InputPortType is RS-232 inteface is selected in InputPortType | PortName | Available Name of an available COM - port name | Depends on the number of available COM ports | ||
BaudRate | Supported bit data transfer rate , in bit/s | Depends on the number of supported bit data transfer rates | ||||
RtsEnable | Enable RTS option0 | – do not use RTS 0—RTS control signal 1 – use RTS isn't used 1—RTS control signal is used | ||||
DtrEnable | Enable DTR option0 | – do not use DTR 0—DTR control signal 1 – use DTR isn't used 1—DTR control signal is used | ||||
MSMQ_settings | A group of elements. Specifies the settings of 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 true—messages are filtered by time | ||||
| DeleteMessages | Enables or disables message deletion after they are read | true - messages true—messages are deleted | ||||
| Queue.Path | Path to the queue | -NA | ||||
| Queue.Terminal | Number of the terminal that is inserted for the specified queue | -NA | ||||
| JMS_settings | A group of elements. Sets Specifies the settings of JMS settings if InputPortType is JMS | UrlUrl | -URL address- | NA | ||
| Login | Login | -NA | ||||
| Password | Password | NA | ||||
| HttpStreaming Settings | A group of elements. Specifies the settings of transferring XML files via HTTP protocol | HttpStreaming use | Enables or disables the mode of transferring XML files via HTTP protocol | true—the mode of transferring XML files via HTTP protocol is enabled false—the mode of transferring XML files via HTTP protocol is disabled | ||
| ip | IP address of the POS server | Depends on the network settings of the POS server | ||||
| port | Port of the POS server | Depends on the settings of the POS-terminal object | ||||
| TcpClients_Settings | A group of elements. Specifies the settings of TCPCLIENT settings if InputPortType is TCPCLIENT | IpAddress | Connection address | -NA | ||
| Port | Connection port | -NA | ||||
| Message | Command to send (optional) | -NA | ||||
| Interval | Command sending interval ("Message") in Interval of sending the Message command in ms (optional) | -NA | ||||
| IdTerminal | Terminal id for the node, to be specified in the forwards section (optional) | -NA | ||||
forwards | A group of elements. Sets the correspondence between the routing id and POS - server IP - address/port | ip | POS-server IP - address of POS server | Depends on the POS-server network settings of POS server | ||
port | Port of POS - server port | Depends on the settings of 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 | ||||
| PluginSettings | A group of elements. Specifies Likothe settings of the Liko, SecurOS and LogisticsSystemPlugin plugin settings and LogisticsSystemPlugin plugins if InputPortType is PLUGIN For details, see Configuring data receiving reception from plug-ins - | NA | -NA- | NA |
| Info | ||
|---|---|---|
| ||
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.several POS terminals send data, the number of established connections is equal to the number of recipient addresses and for each POS terminal it is required to determine whether the routing ID matches the IP address and port of the POS server. |
Example of several POS terminals sending events:
| Note | ||
|---|---|---|
| ||
| If the routing id of a package has no match in the utility configuration file, and the id=”*” is not setisn't specified, the package is deleted. |
Overview
Content Tools