Versions Compared

Old Version 1

changes.mady.by.user Ekaterina Marchenko

Saved on

compared with

New Version Current

changes.mady.by.user Ekaterina Marchenko

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

MenuBoard Setup for Single Restaurant

Executing MenuboardCreate.sql

...

Script

In the base powered by MS SQL server, tables and procedures are created with the use of the MenuboardCreate_1.0.7.sql script. Do not forget to specify the name of your base: USE [DB_name], ef.gex., USE [rk7]. The script can be executed in the SQL Server Management Studio environment. Execute the script on the current RK7 database, used by the restaurant directories/reports server!Note: the option of upgrading reference or report server.

Note

At the moment, it is impossible to upgrade from version 1.0.7.0+ to 1.0.9.0+

...

so far

...

. The possible solution is

...

to delete  SQL tables with

...

the "MB_"

...

prefix and then recreate them using the MenuBoardCreate 1.0.9.0.sql

...

script, available at

...

FTP:ftp://ftp.ucs.ru/rk7/INSTALL/RK7_MenuBoard/MenuBoard 1.0.9/.

...

Please, note that the previous plugin configurations will be lost.

Configuring and Launching Common Server

...

Get Download the distribution package (kit from FTP ftp://ftp.ucs.ru/rk7/other/UCS_CS/CSSetup.exe)  and install Common Server.

The address and port, requested when installing the Common Server, should be available on the PCs running the Feature Server. Later, you will be able to change the server port in its INI file (— CS_Service.ini in the Common Server installation folder).

Configuring and

...

Launching High-Level Feature Server

FS_High_Level.exe

...

or high-level Feature Server

...

Required is required for the plugin operation at the manager station.

The server working directory is FS_high_level (located in the archive level. It is located in the MenuboardFS_1.0.7.2.zip)zip archive.

In this folder, edit the files edit  FS_high_level.ini and MSSQL_FS.udl udl, and only after that launch the FS_high_level.exe file.

1.3.1. Edit the FS_high_level.ini file.

Example of FS_high_level.ini file sample:

Code Block
[FS_CONNECTION]
url = http://127.0.0.1:8890/soap/IStructuresInfo
urlSSL =

...

 
start_port = 8890

...


DB_Connect_Count = 2
[CS_CONNECTION]

...


url = http://192.168.1.1:7007/soap/UCSCommonWS

...


urlSSL =

FS_high_level.ini parameters description:

[FS_CONNECTION] section, parameter  URL or URLSSL — URLSSL parameter — here, you specify the high-level Feature Server address, which will beregistered be registered at the Common Server depending on the selected connection type.

[FS_CONNECTION] section, parameter  start_port —  parameter — here, you specify the port, which will be used for the Feature Server operation.

[CS_CONNECTION] section, parameter  URL or URLSSL — URLSSL parameter — here, you specify the Common Server address.

If the Feature Server is installed on another PC as compared to the Common Server, this address should be visible to for the Common Server.

...

Editing MSSQL_FS.udl

...

In the MSSQL_FS.udl file, you configure the connection to the RK7 capture r_keeper 7 database for the SQL Server.

Double-click or use Notepad to open this file and set the following parameters:

Code Block
User ID=(user_name); Password=(password); Initial Catalog=(database); Data Source=(server_IP_address), (server_port)\(server_name)

...

You can To find these parameters at the manager station under , go to Service  - > Data  export -Export > External  DB settingsDatabase Configurations.1.3.3. 
 Note
FS_high_level.exe should be launched only after FS_high_level.ini and MSSQL_FS.udl have been edited!
...
Configuring and 
...
Launching Low
...
-Level Feature Server
...
The server working directory is of FS_Low_Level.exe is FS_low_level (located in the archive level. It is located in the MenuboardFS_1.0.7.2.zip)zip archive.
...
Editing FS_low_level.
...
ini
Example of FS_low_level.ini file sample:
 Code Block
[FS_CONNECTION]
...

url =
...
  http://127.0.0.1:8891/soap/IStructuresInfo
urlSSL =
...
 
start_port = 8891
...

FSGuid={7BF6D21E-1D1D-4DB2-A877-DB047028B212}
...

[CS_CONNECTION]
...

RemoteURL = http://192.168.1.1:7007/soap/UCSCommonWS
...

RemoteURLSSL =
...
 
LocalURL = http://192.168.1.1:7007/soap/UCSCommonWS
...

LocalURLSSL =
...
 
[XMLInt]
...

RefServAddress = 127.0.0.1:18881
...

CashServAddress = 127.0.0.1:17771
...

CashServPassword=
...

RestaurantCode=39
...

StationCode = 1
...

ImageForMissing = image_for_missing.png
FS_low_level.ini parameters description:
...
url=http://127.0.0.1:8891/soap/IStructuresInfo (or URLSSL) — URLSSL — the address, which will be used for the selected Feature Server registration at the local Common Server.
...
If the Feature Server is installed on another PC as compared to the Common Server, this address should be visible to for the Common Server.
FSGuid — the unique identifier of the selected server intended for client requests.
...
RemoteURL=http://192.168.1.1:7007/soap/UCSCommonWS (or RemoteURLSSL) — the address of  or RemoteURLSSL — the Common Server address at the head office, where the low-level server will connect to in order to retrieve settings ( if the high-level and low-level servers are running on different PCs).
LocalURL=http://192.168.1.1:7007/soap/UCSCommonWS (or LocalURLSSL) — the address of  or LocalURLSSL — the Common Server address at the local restaurant, where the selected Feature Server should register. For a single restaurant with one CS, it matches the previous RemoteURL.
Example: the PC, where the MenuBoard application is launched, can have no access beyond the restaurant network. MenuBoard requests the settings from the local CS via LocalURL, where the LowFS is functioning, and the . The LowFS, in turn, requests the settings from the remote CS via RemoteURL, where the High_FS is running. Technically, if such access separation is not required, LocalURL and RemoteURL can be identical, i.e. you can use a single general common CS.
[XMLInt] section
RefServAddress=127.0.0.1:18881 — here, you 18881 — specify the "address:port of the directories reference server XML interface" (you . You can check the XML interface functionality with the untility available on FTP: utility from FTP: ftp://ftp.ucs.ru/rk7/ForDealers/XMLInterface/); . Find the port is the same as in 1.6.2. in the reference server properties at the manager station. Starting from version 7.5.3.214, you can specify the cash server address:port for this parameter instead of the address and port of the directories/reference or reports server.
CashServAddress=127.0.0.1:17771 — here, you specify the "address:port of the cash server XML interface" (you . You can check the XML interface functionality with the untility available on untility from FTP: ftp://ftp.ucs.ru/rk7/ForDealers/XMLInterface/); . Find the port is the same as in 1.6.1in the cash server properties at the manager station.
RestaurantCode=39 — here, you specify the code of the restaurant (the "Code" for which FS should retrieve settings from the head office and the cash server. It is the Code property from the RK7 r_keeper 7 manager station; , not to be confused with the full code), for which FS will have to retrieve settings from the head office and the cash server.. 
StationCode=1 — here, you specify the code of the station (the "Code" property from the RK7 manager station ), for which you will retrieve the list of dishes, prices, current business period, etc. via the XML interface. Find the value in the Code property from the r_keeper 7 manager station. 
ImageForMissing=image_for_missing.png — here, you specify the inage image that will be used for dishes with missing images. The file should be located in the folder containing dish pictures, specified at the manager station (see 1.6.3).
Now, you can launch 1.4.2. Launch FS_Low_Level.exe.
 Note
Before the server startup, make sure that the 
...
reference server and the cash server have been launched
...
.
Manager Station Settings
...
  1. Copy the plugin to the manager station
...
  1. :
    • In the manager station 
...
    • folder, create 
...
    • the plugins folder and unzip the MenuboardPlugin_1.0.Х.zip archive 
...
    •  there, keeping the file structure.
  2. In the menuboard_settings.ini file, under the [CS_CONNECTION] section, specify the Common Server address 
...
  1.  for the 
...
  1. WSDL parameter, 
...
  1. f.
...
  1. ex.: WSDL=http://192.168.1.1:7007/soap/UCSCommonWS.
    menuboard_settings.ini should be located in the plugins\menuboard_settings
...
  1.  folder, while menuboard_settings.
...
  1. dll — in the plugins
...
  1.  folder.
...
  1. Add the XML interface to the 
...
  1.  Devices 
...
  1.  tab for the cash server, and specify the port
...
  1. . 
...
  1.  Then, link this interface to the logical interface.
     Note
    It is recommended to create the new interface for MenuBoard as a copy of the pre-installed XML interface in the 
...
  1.  Service 
...
  1.  > Interfaces 
...
  1. reference.
...
  1. To imply the changes
...
  1. , 
...
  1.  restart the cash server!
...
  1. Image Added
  1. Specify the port for the 
...
  1. reference server XML interface.
...

  1. Image Added
  2. Specify the path to the images folder in 
...
  1. r_keeper 7 parameters in Options > Parameters > Installation > Large images path. Place the dish images 
...
  1. in the .png
...
  1.  format and the image_for_missing.png file 
...
  1.  for those dishes without an image 
...
  1.  into this folder.
...
  1. Enable the following parameter: 
...
  1.  Options > Parameters > Options usage 
...
  1. > Self-
...
1.6.5. Create business periods (Settings – Head office – Business periods). Configure the use of business periods.
...
  1. Service/Web Orders.
  2. Go to Options > Head office > Business periods and create business periods. Configure the business periods usage and, if necessary, time intervals in the Order > Periods reference.
    Image Added
    Image Added
     Note
    Prior to performing the following operations, make sure that the Common Server and both Feature Servers
...
  1. , HIGH and LOW
...
  1. , have been launched
...
  1. .

  2. Go to Extensions > MenuBoard configuration, and configure the required 
...
  1.  MenuBoard display variants in the plugin.
...
  1. Create a new setting by right-clicking the plugin configuration tree and selecting Add setting.
    On the 
...
  1. Basic Properties tab, in the created setting properties, specify the coordinates of the desktop point, from which the screens with dishes will be drawn. 
    By default, the setting is created with a single screen. You can create additional screens
...
  1. : right-click the configuration tree 
...
  1. and select Add screen
...
  1. . For each screen, coordinates, height, and width should be set. Each screen corresponds to a separate monitor connected to the video card.
...
  1. Configure the use of these variants for restaurants according to business periods 
...
  1. in Extensions 
...
  1. > MenuBoard using
...
  1. .
     Info
    For detailed information about the MenuBoard configuration via the plugin, see the user manual:ftp://ftp.ucs.ru/books/menuboard_RK7_user_manual.pdf
...

Configuring and 
...
Launching MenuBoard (AIR application)
MenuBoard is an Adobe AIR application. Therefore, before the launch, you need to install Active-X components for Windows.
Unzip the contents of the MenuboardApp_1.0.7.6.zip archive and edit the Settings.xml file:Important! 
 Note
In the paths, use the forward slash — 
...
 /
...
.

 Code Block
<Application>
...
<Settings   
...


<Settings
WSDLServer = "http://192.168.1.1:7007/wsdl/UCSCommonWS"
...

ServiceName = "UCSCommonWSservice"
...

ServicePort = "UCSCommonWSPort"
...

FSGuid = "{7BF6D21E-1D1D-4DB2-A877-DB047028B212}"
...

RequestInterval = "10000"
AssetsDirectory = "D:/UCS/RK7_MenuBoard/MenuboardApp/assets/"
>
...


</Settings>
...

<Log
...

Enable = "0"
...

Size = "25000000"
...

Name = "log"
Dir = "D:/UCS/RK7_MenuBoard/MenuboardApp/Log"
>
...

</Log>
...

</Application>
WSDLServer — the path to the local Common Server. The Common Server address should be available from your PC.
AssetsDirectory — the path to the folder containing design files. Usually, it is as follows: "[the folder, where the archive contents have been unzipped]/assets/".
RequestInterval — the frequency of the settings update request, ms.
FSGuid — GUID of the required FS_low_level (could , might have been empty in early versions).
Launch MenuBoard.exe.
...
Design Files Synchronization Logic
  1. If everything is launched on the same local computer, the path in settings.xml should be as follows: [path to the plugins folder]/menuboard_settings/assets/.
    In this case, when you select an image 
...
  1. or a video 
...
  1.  for advertisement and gallery design at the manager station, these files are automatically copied to the Advert subfolder.
  2. If the menuboardapp MenuBoard app is located on another PC, you should check the following:
    ...
      • The path to the assets folder in settings.xml
    ...
    ...
      • The assets
    ...
      •  folder should contain the 
    ...
      • Advert, Dish, Interface
    ...
      •  folders and their contents should correspond to the same folders 
    ...
      • in /plugins/menuboard_settings/assets/ for the manager station at the 
    ...
      • reference server
    ...

      • Then, create a directory according to 
    ...
      • the Path to the images folder
    ...
      •  parameter at the manager station, keeping the folder structure, and copy the dish pictures there without changing their names.
    2. Alternatively, the path in settings.xml can be random in both cases; the . The main requirement is that the folder should contain 3 subfolders (— Advert, Dish, Interface ), — the contents of which correspond to the following: [path to the plugins folder]/menuboard_settings/assets/.
    3. If the Menuboardapp MenuBoard app is launched on a remote PC, design files should be synchronized either individually (, considering the folder arrangement logic mentioned above), or with the use of the Synchronizer utility (available via from FTP: ftp://ftp.ucs.ru/rk7/INSTALL/RK7_XMLSecondScreen/Synchronizer.rar). Configuration Find the configuration description is provided in ReadMe.txt in the archive.
    ...
    Recommendations on 
    ...
    Image Formats Use
    • If you need a transparent background for dish images, use .png, if not — use .jpg;
    • Do not use .bmp, it may cause problems during the visualization and loading, since the files of such type are usually quite large;
    • Dish The dish image size is ~1280 on the larger side. This is because such images can be used for advertising purposes;
    • The main background size is 1920x1080;
    • Videos should have .flv (vp6) format, 1920x1080; high . High bitrate is not recommended.
    MenuBoard operation principles for multiple restaurants
    ...
    menu_board_n4.pngImage Added
     Note
    The implementation of MenuBoard operation in chain restaurants is possible only for RKeeper version 7.5.3.ХХХ and higher.
    At the head office, the Common Server and FS_High_Level.exe should be installed and always launched. Moreover, you should correctly configure the MenuBoard usage variants for restaurants according to business periods.
    ...
    Upon the MenuBoard (menuboard.exe) launch:- the 
    • The application requests the display data from the local Common Server
    ...
    • , specified in settings.xml
    ...
    • , and 
    ...
    • the latter redirects the request to FS_low_level
    ...
    ...
    • FS_low_level, based on the settings from the 
    ...
    • .ini file and the current business period, forwards the request for settings 
    ...
    •  to the head office Common Server
    ...
    ...
    • The head office Common Server forwards the request to FS_high_level
    ...
    ...
    • FS_high_level selects the design matching the specified restaurant and business period, and returns the result to the head office Common Server;
    ...
    • The head office Common Server returns the obtained result to FS_low_level
    ...
    ...
    • FS_low_level complements the received setting with current prices and dish images, acquired via the XML interface, and transmits the response to the local Common Server
    ...
    ...
    • The local Common Server returns the relevant design setting to the MenuBoard, which displays it on the panel
    ...
    • After the interval specified in settings.xml
    ...
    • , the chain of actions repeats, since the settings might have changed.
    After each request, FS_low_level saves the settings received from the head office along with the data acquired via the XML interface. Therefore, if the communication between it and the head office Common Server is interrupted, FS_low_level will provide the AIR application with cahed cached data.
    If graphical design files change at the head office, a synchronization of the "assets" you should synchronize the assets folder at the head office and at every restaurant is required.Note: in 
     Note
    In the case of making all settings on a single PC
    ...
    , there can be one Common Server, but the Feature Server ports should not match.
    RK7 r_keeper 7 should be configured for online sales data collection for the purpose of discount calculation.