Professional Documents
Culture Documents
Aloha v6.4
Table of Contents
About Aloha v6.4..................................................................................................................... 3
Preparing to Install Aloha v6.4 ............................................................................................. 4
Updating the Operating System........................................................................................... 6
Configuring the Aloha Network ............................................................................................ 8
Installing Aloha v6.4 on the BOH File Server.......................................................................... 9
Activating Remote File Storage ......................................................................................... 19
Installing Aloha v6.4 on a FOH Terminal .............................................................................. 21
Page 1
Copyright 2008, Radiant Systems, Inc. The information contained in this publication is confidential and
proprietary. No part of this document may be reproduced, disclosed to others, transmitted, stored in a
retrieval system, or translated into any language, in any form, by any means, without written permission of
Radiant Systems, Inc.
Radiant Systems, Inc. is not responsible for any technical inaccuracies or typographical errors contained in
this publication. Changes are periodically made to the information herein; these changes will be incorporated in new editions of this publication. Any reference to gender in this document is not meant to be discriminatory. The software described in this document is provided under a license agreement. The software
may be used or copied only in accordance with the terms of that agreement.
Radiant Systems, Inc., 2008. All Rights Reserved. ALOHA is a U.S. Registered Trademark of Radiant
Systems, Inc. Microsoft, and Windows are registered trademarks of Microsoft, Inc.
Page 2
Other References
Due to the general complexity of the working environment of the Aloha system, you must adapt the information in this document to address all aspects of your specific installation, taking differences into account.
You must also address any third-party software in use in your installation, such as external applications
exchanging financial or other information with the Aloha system.
Page 3
Aloha_64x_CD1.iso
Aloha_6x_CD2.iso
An image file is also available for the Aloha Resource Toolkit CD, file name DocCDv64.iso.
2. Identify, locate, and download or copy all update files needed, prior to starting.
The tables in this document list the files you will need, and their sources.
3. Perform operating system updates on all Aloha network computers, including file servers,
administrator workstations, and terminals. Refer to Updating the Operating System on page 6.
4. Configure the Aloha network as outlined in the appropriate RKS document. Refer to Configuring the Aloha Network on page 8.
a. Set the workgroup name on the file server and all terminals in the network to the same workgroup name. Radiant typically uses IBERTECH for the workgroup name, but this name is
arbitrary as long as it is consistent throughout the Aloha network.
b. Change the computer name on the Aloha BOH file server to ALOHABOH. This is arbitrary, so a different name can be used, if desired.
c. Change the computer name for each FOH terminal to TERMx, where x is a unique number
for the terminal, such as TERM1, TERM2, and TERM3 for a three-terminal system.
d. Set the IP address and the subnet mask for the BOH file server and each terminal in the network.
e. Set the LANA number to 0 (zero) for each network adapter used in the Aloha network.
f. Enable NetBIOS over TCP/IP on the file server and all terminals in the network.
g. Disable DHCP media sense on the file server and all terminals in the network.
h. Disable Use Simple File Sharing on the file server and all terminals in the network.
i. Create the BOOTDRV share and set permissions so that each specific user, as required in the
Data Security Handbook, has full control access. You can name the folder you are sharing any
name you want, but the Share Name must be BOOTDRV, as the FOH executable creates a
mapped network drive to Z:\BOOTDRV every time it starts.
j. Set the color palette to 256 colors or higher.
k. Configure the time zone and daylight savings options on the BOH file server and every terminal in the network.
Page 4
l.
Configure a Windows user account, such as AlohaSvr, specifically for the purpose of registering Aloha Windows services, on the BOH file server and all terminals in the network. Once
created, register the three primary Windows services associated with the Aloha system, Control Server (CtlSvr.exe), EDC Server (EDCSvr.exe), and Remote File Storage Server
(RFSSvr.exe), if applicable, using this user account and a unique, complex password. The user
must have administrative rights and have full control access to the BOOTDRV share on the
network.
5. Install the Aloha software on the BOH file server using the Aloha installation CDs. Refer to
Installing Aloha v6.4 on the BOH File Server on page 9.
6. You may need to adjust the login account for the Aloha-related services, such as CtlSvr.exe,
EDCSvr.exe, and RFSSvr.exe.
7. Install the Aloha software on each FOH terminal. Refer to Installing Aloha v6.4 on a FOH Terminal on page 21.
Page 5
MDAC 2.6*
MS Jet 4.0 SP 3*
.NET 2.0 framework or higher*
Visual C++ 2005 Runtime Redistributable Package*
Page 6
You can obtain the required updates and add-ons, as appropriate for your operating system, per the following:
Update Requirement
Available From
If not already installed, obtain this update to the Windows Installer directly
from Microsoft at:
http://www.microsoft.com/downloads/
Windows Installer v3.1 must be present on the BOH file server and each FOH
terminal before you install Aloha, as this is a prerequisite for .Net v2.0 and
later.
128-bit encryption librar- If 128-bit encryption is not already is use, you can install directly from the first
ies, as part of Internet
Aloha installation CD, available in the \Misc\Msie6_00.SP1 directory. The
Explorer updates
Windows 2000 High-Encryption Add-on is available from http://
www.microsoft.com for this operating system, as an alternative to installing or
upgrading Internet Explorer.
When you initiate the Aloha installation on the BOH file server, if these comMDAC 2.6
ponents are not installed on the system, a message appears indicating such
Microsoft Jet 4.0 SP 8
and they are installed for you using files located on the first installation CD;
.NET Framework v2.0
however, you must install .Net Framework v2.0 on the FOH terminals, as the
Visual C++ 2005 Runtime terminal installation program will not do this for you.
Redistributable Package
Page 7
Operating System
Windows 2000
Windows XP
Windows XP Embedded
Once the operating system is set up according to the guidelines in the appropriate RKS document, and you
can view the network, you can install the Aloha software on the BOH file server and the FOH terminals.
Page 8
3. Click Yes to allow the system to install these components on the system for you. The license terms
for Microsoft Visual C++ may appear.
Figure 2
Page 9
4. Click Yes to agree to the terms and continue with the installation. The Setup Aloha POS dialog box
appears.
5. Select Aloha TableService or Aloha QuickService. The Setup Aloha dialog box appears.
Clicking Cancel at any time during the installation process aborts the installation
of Aloha TableService and QuickService.
Page 10
6. Select Typical Install or Custom Install. The Aloha Configuration screen appears with the
default values for the product selected.
7. Accept the source path to the Aloha installation files. Setup automatically detects the drive from
which you are installing Aloha and sets this path for you; however, you can edit this and supply
another source path, if desired.
8. Change the destination path to a secure location, such as a secondary directory beneath the root
(C:\Bootdrv\Aloha).Using this convention, you can share the Bootdrv folder without sharing the
entire root drive. Include the drive letter and file name, according to the system.
Path to Calibrate Dir shows the path to the previously installed calibration program used for the
Front-of-House (FOH) touch screens. This is not applicable if touch screens requiring calibration
are not utilized, or the server is not used as a terminal.
9. Enter the server name, if applicable. Setup automatically detects the server name, and lists it (usually as ALOHABOH); however, you can edit this and supply another server name.
10. Enter the number of terminals. The number you enter here must match the number of terminals
designated as order entry terminals.
11. Leave the default value TERM in the TermStr text box, unless otherwise advised.
12. Enter the terminal ID, if applicable. A value entered here is relevant only if you will use the server
as a FOH terminal and you select Run Front-of-House and Back-of-House on the same PC.
Redundant mode is required; therefore, the Redundant Mode check box is selected and cannot
be changed.
13. Select Install Aloha EDC to install Aloha EDC along with the core product you selected.
Page 11
14. Select Run CTLSVR.EXE as a service to run the Control program as a service.
If you do not select Run CTLSVR.EXE and/or Run EDCSVR.EXE, they will run in server
mode rather than as a service. In server mode, the service starts when you start the user interface
and exits shortly after closing the user interface. In service mode, CTLSVR and EDCSVR are
always running.
15. Select Run EDCSVR.EXE as a service to run the EDC program as a service.
16. Optional: Select Install for demonstration purposes only to install Aloha TableService or Aloha
QuickService for the purposes of demonstration.
17. Click Next to continue. The CTLSVR and EDCSVR Services Properties dialog box appears.
Figure 6
Figure 7
Page 12
20. If you have more than nine terminals on your network, click Enable RFS and the RFSSVR Service Property dialog box appears. Continue with the next step; otherwise, click Do not Enable
RFS and a prompt to enter the security key IDs appears. Continue with step 24.
Although the Aloha system prompts you to enable Remote File Storage during installation, we
recommend you do this only if you have more than nine terminals and are reinstalling Aloha on a
BOH file server connected to a network on which RFS has previously run. If you have not used
RFS on your Aloha network prior to this installation, you should, as a best practice, bring the network into full operation prior to enabling RFS. Refer to Activating Remote File Storage on
page 19.
Figure 8
Figure 9
This service is specific to the MenuLink back office product. Do not enable this service unless
specifically told to do so. If you are told to enable this service, select to run it as a specific user
using the same network account user name and password used in step 19.
23. Select Do not enable AlohaDbuSvc. The installation continues and does the following:
a. Confirms the version of the operating system, and determines the hard drive letter and path.
b. Checks for a minimum MDAC version of 2.6 (prerequisite to continuing).
Page 13
24. Enter the security key information (sent with your security key) in the appropriate text boxes. A
0 is always the number zero, and a 1 is always the number one.
If there is a problem with the security key and you cannot complete the installation, contact your
support department.
Page 14
25. If you are performing a Typical installation for TableService or QuickService, steps 26 through
36 do not pertain to your installation. Please continue with step 37. If you are performing a Custom installation for TableService or QuickService, the General dialog box appears to allow you to
select an alternate interface theme.
Do not make a selection on this screen, as these graphic themes are no longer supported. An alternative for using these themes is to use the Enhanced Graphical Interface (EGI). After completing
the installation, access Aloha Manager > Store Settings > User Interface group > POS tab and
select the Graphic Theme you wish to use.
Page 15
Be very careful not to select a graphic theme, as this cannot be altered at a later time.
26. Click Next to continue. The Database Configuration dialog box appears.
On new installs,
you are given the
option to install
sample data, or real
data. Sample data is
the default.
27. Most Aloha installations will not use a relational database, but if you plan to use one, select the
appropriate relational database option from the External Relational Database group box.
If you select any of the MS SQL Server options (MS SQL Server 6.5, MS SQL Server 7.0, MS
SQL Server 2000, or MSDE), the Computer Name and Path To Database options are enabled
and the computer name is initialized with the name of the local machine. If you plan to use another
machine, you need to change the computer name. If SQL Server or MSDE is already installed on
the local machine, the path to the database will also be initialized to the path found in the Registry
for MS SQL Server/MSDE; otherwise, enter this path - normally C:\MSSQL7\DATA, or the same
path on a different drive. If you select MS Access, the system installs the Microsoft Access relational database engine (but not the user interface).
28. Select a sample database, or select Real Data to install real data from Data*.zip and BMP*.zip
files. You must provide the Data*.zip and BMP*.zip files in place of the sample data from the
installation CD. If you have an existing database, these options are not available. Setup alerts you
that is has detected an existing database and will not overwrite it.
29. If you selected Real Data, continue with the next step; otherwise, go to step 37.
Page 16
30. Click the Data Zip File Browse button (Figure 12). The Select Data .Zip File for Alohas Data
Directory dialog box appears.
Figure 13 Specify path and file name for locating data files
31. Select the path to the data zip file from the Look in drop-down list.
32. Click Open. The path to the Data*.zip file appears in the Data Zip File text box (Figure 12).
33. Click the Bmp Zip File Browse button. The Select Bmp. Zip File for Alohas BMP Directory dialog box appears.
Figure 14 Specify path and file name for locating .bmp files
34. Select the path to the BMP*.zip file from the Look in drop-down list.
35. Click Open. The path to the BMP*.zip file appears in the Bmp Zip File text box (Figure 12).
36. Click Finish to continue.
If you selected MSDE in step 28, and the computer specified in Computer Name is the local
computer, the install program will determine whether MSDE is already installed. If MSDE is not
already installed, you will receive a prompt for the location to which it should be installed, with
default values specified. Click OK and the install program will install MSDE for you.
Page 17
Sets all environment variables. (RKS Document #6613, 6614, and 6615)
Copies \Windows\System files from \Aloha\Setup to \Windows\System32 directory.
Verifies that AlohaSec.exe is not running, to configure the security key.
Installs the HASP driver. (RKS Document #6223, and 6224)
Creates Aloha program launch icons.
Prompts you to reboot the computer.
Page 18
Page 19
The next data refresh activates RFS across the Aloha network. The Aloha system registers RFSSvr.exe as a
Windows service, and starts the service, on computers running Windows NT-based operating systems. For
other operating systems, Aloha configures RFSSvr.exe to run as a server, requiring a restart to activate the
server.
If, at any time, you wish to stop using RFS, simply repeat this procedure, clearing all check boxes in Maintenance > Store Settings > System > RFS tab that enable the feature. The next data refresh restores the
Aloha system to operation without RFS.
Page 20
Page 21
Page 22