Back to Olo.com

Quick Glance: Aloha Best Practices & Requirements


Updated

Audience:

Technical Teams, Account Managers, and Product Development.

Description:

This article lists a quick glance at the requirements & best practices for our Integrated > Aloha POS Solution. This is intended to be a living article in which updates are expected as technology changes and as new learnings occur. We do not claim that this is comprehensive or final for every environment, rather, it is a standard list that applies in most scenarios. (R)denotes a requirement / (BP) denotes a best practice. Additionally, there are links to relevant documents within this list.

System

(R) Aloha Connect and 1 EIT specific to Olo must be enabled on your Aloha Security Key License.

(R) 4GB+ RAM to support the OS, Aloha POS, additional programs and Olo with 5Gb+ of free disk space.

(BP) Olo recommends a PCI Compliant OS and balance with other software program specifications).

Firewall

(R) Allow outbound HTTP(S) connections to api.olo.com on port 443.

(R) Allow outbound TCP connections to our hostnames posX.olo.com on port 9292.

(R) These connections are long-running and must be allowed to run indefinitely.

(R) Whitelist the following FQDN host names and ports:

                           api.olo.com (port 443)
                           pos1.olo.com (port 9292)
                           pos2.olo.com (port 9292)
                           pos3.olo.com (port 9292)
                           pos4.olo.com (port 9292)
                           pos5.olo.com (port 9292)

Configuration and Versions

(R) Aloha POS 6.7.38.138 or higher.

(BP) Configuration Center for multiple stores.

(R) Standardized database with consistent record ID's across stores.

(R) OloUpdate Service needs administrative privileges to run local updates (N/A for Aloha 15.1+).

(R) OloAlohaService has administrative privileges for launching Iber and local registration on boot up.

(BP) OloAlohaService needs R/W access to bootdrv on FOH terminals to pull debouts for troubleshooting (N/A for Aloha 15.1+).

(BP) User that Cltsvr is using and should be set to not allow local login in the Local Policy.

(BP) Ctlsvr should not be logging on with Localsystem in standard scenarios (discuss with TAM).

(R) Unique Interface Server, Interface Terminal records configured in Aloha POS.

(R) Interface Employee must be setup within Aloha with an Olo relative Job Code, Access Level.

(R) ATO > Maintenance > System Parameters configured to not start FOH / not be Master Capable.

(R) Any application that launches iber(qs) on the BOH should have launch command disabled.

(R) With ATG enabled, edit ATG\Bin\AlohaTransactionGateway.exe.config to include the  "SkipLogOut" values (ATG 14.1.361+).

(BP) For integrated catering,use bulk items in the POS database on a catering menu to avoid maximum check item count in Aloha POS.

 



Last updated 11/17/17

Didn't find what you need?

Submit a request to our Help Team and someone will
get back to you shortly.

Submit a request

Copyright © 2017 Olo. All rights are reserved.