ALOHA POS SYSTEMS

Revolution HARDWARE & SOFTWARE REQUIREMENTS

  • .NET Framework 4.0 or greater installed on every POS Server in locations that will be using the Revolution service.
  • All POS Operating systems must be Microsoft Windows 7 or greater with most recent patches applied.
  • An Aloha Lab server configured exactly as a typical restaurant is configured that can be made accessible to the Revolution Technical team for testing.
  • On every firewall / router, full inbound access to tcp port 4503
  • On every firewall / router, whitelist (or not blacklist) tokenex.com and tokenex.net
  • On every firewall / router, full outbound access via tcp, http & https protocols to rrtusa.net.
  • On every firewall / router, full outbound access via tcp, http & https protocols to tokenex.com & tokenex.net.
  • On every POS server, the Z: drive cannot be mapped; Aloha Connect interface uses it on an ad hoc basis.
  • An administrative account on each server with full access to the directory structures for each POS terminal.

ALOHA SOFTWARE REQUIREMENTS

  • Licenses for at least one Radiant Interface Terminal and one Radiant interface terminal server. Contact local reseller for an installation quote.
  • Fully licensed to use the Aloha Connect program (not CLOUD Connect), if client is not currently an Aloha Connect licensed customer.

ALOHA / REVOLUTION CONFIGURATION REQUIREMENTS

  • Job Code, Employee, Labor Group, Interface Server Terminal (virtual, in Aloha), Interface Terminal (virtual, in Aloha).
  • Exception Modifier Group ID, Instructions Modifier ID, FOH COM enabled.

MISCELLANEOUS

  • RECOMMENDED FOR CALL CENTER SERVICES:  An unlimited long distance package on the primary line called for takeout if anticipated call volume is expected to be high. Call forwarding capabilities on the primary line called for takeout
  • RECOMMENDED: Teamviewer, Logmein, or similar remote desktop connection service technical assistance when troubleshooting issues.

INSTALLATION INSTRUCTIONS

Server Preparation

Set up a few system environmental variables on the server if they are not there already under windows system properties / advanced.

  • IBERDIR – location of aloha folder on server (normally d:\alohaqs or d:\bootdrv\alohaqs)
  • LOCALDIR – location of aloha folder on server (normally d:\alohaqs or d:\bootdrv\alohaqs)
  • TERM – this is the three-digit number of the interface server in Aloha (e.g. 051)
  • MASTERCAPABLE – False
  • TERMSTR – TERM

Verify that the Z: Drive is not in use or reserved

Open port 4503 outbound for rrtusa.net

Revolution Service Installation

  • Enter the following license code as a new line in the raddacct.lic file in the AlohaQS BIN directory.

4;2O49393B5>4@4L2<45421N1R1?2F4U2V500Q2U215K2L1R5I5Q1V5I5D1P3X394R1N434@1V2J

  • Make a directory c:\program files\RRT
  • Copy the files located in the DropBox folder (provided separately by your Revolution Client Services team) into the new Revolution folder.
  • From within the Aloha Location Service Starter folder, run install_locationservicestarter.bat
  • If you encounter any exceptions, the install will roll back. Please contact Revolution if this occurs.
  • If successful, press any key to close the install log window.
  • In Services:
    • Configure the Revolution Service to run under an account that has access to the file system of all terminals capable of being Master Terminal (usually the administrative account of that terminal)
    • Configure service to start automatically. If successful, press any key to close the install log window.
  • START SERVICE

Aloha Configuration

  • JOB CODE: Create job code for RRT Takeout.
    • Rev Center=ToGo or Takeout
    • Check ignore labor schedules/Exclude from labor scheduling.
    • Functions – Team Get Check selected, Limit to Labor Group “ToGo or Takeout”.
      If not there, see below:
  • EMPLOYEE: Create a new employee with name of something like RRT TAKEOUT and assign it the new RRT takeout job and give normal server permissions (access levels=Server).
  • LABOR GROUP: Create labor group (maintenance/labor/labor groups) for the job codes that handle takeout orders (including the new RRT takeout job code).  
    • No need to worry about sales categories, but you can select them all if desired.
    • Configure the takeout job codes to enable team get check and assign to the new labor group (maintenance/labor/job codes – functions tab).  Do not check assume ownership.
  • TERMINALS:
    • Create interface server terminal (maintenance/hardware/terminals).  
      • Recommend a high terminal number
      • For default and voucher printer, choose the printer that corresponds with the terminal where the takeout person works.
      • Revenue center is takeout.  Terminal type is Radiant.  Check the Interface Server box.  No need to worry about any other fields or tabs.
  • TERMINALS:
    • Create interface terminal (maintenance/hardware/terminals).  
      • Recommend using a terminal number one higher than the interface server
      • For default and voucher printer, choose the printer that corresponds with the terminal where the takeout person works.
      • Revenue center is takeout.
      • Terminal type is Radiant.  Check the Interface Terminal box.  DO NOT check the Radiant Interface Terminal box.
      • For Interface Host, select the newly created Interface Server terminal.  No need to worry about any other fields or tabs.
  • EXCEPTION MODIFIER GROUP: If no exception modifier group exists, create one and assign to all submenus that contain items that can be ordered through the call center
    • ID must match RRT rest mgr
  • INSTRUCTIONS MODIFIER: Create new menu item to be used for transmitting messages to guest check (e.g. special instructions, guest phone, car make/model, etc)
    • Check “Ask For Description”
    • Add to sales category
    • Add to exception modifier group referenced above
  • SYSTEM: Enable FOH com (Maintenance/store settings/system/interfaces tab)
    • USE FOH COM
  • REFRESH: Save all and refresh