1.1. ITV is a video registration system for hospitality and trade.
1.2. RK7 uses ITV interface to send data to ITV system.
1.3. RK7 ITV interface is protected with restaurant-level license.
1.4. The integration utilizes intellct.dll functions (there are Windows and Dos versions).
1.5. intellct.dll is updated with preload.exe (regular RK7 update).
1.6. There are 2 possible mechanisms of data transfer: using files or TCP socket.
2.1. Add 'ITV POS Intellect interface' driver to each cash server (if necessary).
2.2. Set driver properties as follows.
2.2.1. "VideoPath" — path (folder) to save files, if file exchange way chosen (XML) in ITV POS Intellect usiing ITV File Scanner.
2.2.2. "NCR_FORWARD IP" - IP address of NCR_FORWARD.exe (ITV module, that redirects data to POS Intellect system), if socket exchange way chosen.
2.2.3. "NCR_FORWARD Port" - port of NCR_FORWARD.exe (corresponding to 2.2.2.); set "0" to disable data flow to NCR_FORWARD.
2.2.4. "Use Alt сharset" - if set Yes, alternative language of RK7 will be used.
2.2.5. "ActualTime" - time to live for NCR_FORWARD data flow (for connection lose or queue issues), seconds, after this time data marked not actual and not to be sent. This pr
2.2.6. "Log file name" - log with this name will be put to cash server folder.
2.2.7. You have to set or "VideoPath" or "NCR_FORWARD" properties, not both methods at the same time.
2.2.8. "VideoPath" is priority to "NCR_FORWARD IP". If "VideoPath" set to smth not empty, system will ignore "NCR_FORWARD IP".
2.3. Set logical interface (see 4.1.2.) to be linked to necessary driver(s).
2.4. After above actions ITV licensing appear in restaurant(s) properties "License information" with "ITV POS Intellect" name, where you have to put corresponding sub-license (see below and in).
2.5. Create separate printing purpose for ITV interface.
2.6. In section "Printer assignments" of restaurant properties set "ITV POS Intellect" interface for previously created purpose (you may use preset "XML reports" purpose, but this is not good for printing scheme reassignments).
2.6.1. You might do assignments on station level instead of reataurant if necessary (to the interface 105 ITV POS intellect).
2.7. Data for "POS Intellect" is formed by means of standard XML printing through layouts.
2.7.1. There are 2 preset layouts at least: "66 ITV POS Intellect" for receipt and "67 ITV POS Intellect" for service document.
2.7.2. Prepare some well-formed xml layouts that your ITV POS version is able to parse.
2.7.3. You may create your own layouts of mentioned or other document types and assign them to ITV. Take care of strict format and supported function numbers.
2.8. Add layouts to printing schemes not as usually.
2.8.1. You must assign your "XML layout"(s) to valid views of the same document type (not add separate views).
2.8.2. Set created above "XML printer class" purpose for them.
2.8.3. Do not change main layout printer assignments ("Main printer class" and "Back printer class").
2.8.4. Do XML printer and layout assignments to ITV interface only for those layouts prepared for ITV (with strict structure).
2.8.5. Make sure to assign this xml layout to all views of the same document type (if you have alternative printing choise set = several layouts of the same document type in 1 printing scheme).
2.8.6. Do mentioned assignments for all necessary (and active) schemes.
2.8.7. Do not set ITV printer purpose for any non-XML layouts (never set that to "Main printer class" or "Back printer class").
2.9. Add ITV layout view to service scheme.
2.9.1. Create new view and set "ITV POS Intellect" interface to its "XML printer" property, and choose your service document ITV layout in "Layout", "transfer layout" and "deletion layout" properties.
2.9.2. Do not assign any printer in "Printer" and "Backup printer" properties of this view.
2.9.3. Do this for all restaurants (if necessary).
3.1. Set "ITV file scaner" to take files from given folder in case of file mode set.
3.2. Set "NCR_FORWARD" to listen given port in case of socket mode set.