Salesware System Architecture and Specifications

Salesware System Architecture and Specifications Version 4.3 Siriusware, Inc. 302 Camino de la Placita Taos, NM 87571 575.751.0633 www.siriusware.com/docs www.siriusware.com/training google.siriusware.com

Copyright Copyright 2014 Siriusware, Incorporated. All rights reserved. NOTICE: All information contained herein is the property of Siriusware, Incorporated. No part of this publication (whether in hardcopy or electronic form) may be reproduced or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written consent of Siriusware, Incorporated. The software, which includes information contained in any databases, described in this document is furnished under a license agreement and may be used or copied only in accordance with the terms of that agreement. This publication and the information herein is furnished AS IS, is subject to change without notice, and should not be construed as a commitment by Siriusware, Incorporated. Siriusware, Incorporated assumes no responsibility or liability for any errors or inaccuracies, makes no warranty of any kind (express, implied, or statutory) with respect to this publication, and expressly disclaims any and all warranties of merchantability, fitness for particular purposes, and non-infringement of third party rights.

Salesware System Architecture and Specifications Introduction... 3 Block diagrams showing typical Salesware configurations... 3 Overall Salesware architecture... 3 ProtoBase architecture... 4 E-Commerce architecture... 6 Web pages hosted externally... 7 Web pages hosted internally... 8 Rentals architecture... 9 Food Service architecture...10 Scan access architecture...11 Axess Gates architecture...12 Mobile Sales architecture...13 Typical WAN architecture...14 Network configuration... 15 Domain...15 Workgroup...15 Salesware system specifications... 16 Windows XP end of life...16 Using virtual servers...17 32-bit vs. 64-bit...18 Recommended standard salespoint configurations... 19 Middleware... 20 Number of SalesEZ application instances...22 1

Database server... 22 SQL Server Express Edition...25 Web (E-Commerce)... 25 Rentals... 28 Food and beverage FileSync server... 30 Folio Charge... 31 Mobile Sales... 32 Reserved Seating... 34 2

Introduction Salesware features a fully modular, configurable, scalable, fault-tolerant and distributed architecture. This document describes that architecture and presents its specifications. The document is organized as follows: The first section provides block diagrams that show typical Salesware configurations. Note: Salesware supports four Charge Card systems: ProtoBase, DirectNET, Ingenico and Tender Retail. (DirectNET and Tender Retail are not supported for E-Commerce applications.) Siriusware Inc. documentation discusses how to interface with these systems and how to use them from the Salesware product. For information regarding the hardware requirements and specifications for Charge Card systems, please consult the documentation provided by Southern DataComm, Inc. (ProtoBase), DirectNET, Inc., Ingenico and Tender Retail. Note: For information concerning Siriusware Hardware compatibility, please see the Hardware Compatibility List document. Block diagrams showing typical Salesware configurations This section presents typical Salesware configurations. Overall Salesware architecture The following diagram presents the overall Salesware architecture. 3

ProtoBase architecture The overall Salesware architecture diagram shows how a credit card processor can be integrated into the Salesware architecture. The majority of clients incorporate the ProtoBase system. The following diagram shows how the ProtoBase system is configured. Hardware requirements for the ProtoBase PC are available from the http://www.protobase.com web site. 4

Note: Although we use the term, ProtoBase Server, ProtoBase does not require server grade hardware or operating system. Windows 7, both 32 or 64 bit works and Siriusware Inc. recommends 2GByte of RAM and at minimum a Celeron processor and 80 GByte hard drive. ProtoBase requires that their server be a dedicated computer and is not shared with any Siriusware Inc. applications. 5

E-Commerce architecture The E-Commerce module environment includes one or more web servers, a Sales Host computer and an SMTP server. Two web servers are recommended if you are hosting the E-Commerce pages internally or externally (e.g., with a web hosting company). See Web pages hosted externally and Web pages hosted internally. If hosting the pages internally, then you have ww.dll on one web server and the E-Commerce pages installed on the additional server. If hosting the pages externally, then you have ww.dll and wwservice installed on one web server and the E-Commerce pages installed on the other web server (e.g., at your web hosting company). In either scenario, the server that is running ww.dll needs to have access to ProtoBase and to the SiriusSQL database. The server that is running the pages needs to have access to an SMTP server and, if hosted externally, to the ww.dll server. The Sales Host computer needs to have access to ProtoBase, the middleware server and an SMTP server. The computer where ww.dll (and wwservice, if the pages are hosted externally) is installed requires either Windows Server 2008 or Windows Server 2012, Microsoft.NET Framework version 4.0, Internet Information Services (IIS version 7) and ASP.NET 4.0. The computer where the E-Commerce pages are installed also requires either Windows Server 2008 or Windows Server 2012, Microsoft.NET Framework version 4.0, Internet Information Services (IIS version 7) and ASP.NET 4.0. This computer also needs to have an SSL certificate in place so that the E-Commerce pages can be run under https when running live. Note: ASP.NET 4.0 is not automatically installed; you must install this yourself in conjunction with the installation of Windows Server 2008 or Windows Server 2012. Note: Siriusware Inc. strongly recommends that your web server not be a member of a Windows domain. Being a domain member is a potential security risk and changes the way authentication is handled. This change in authentication could make the E-Commerce pages not function correctly without additional configuration. For optimum performance, the computer where Sales Host utility is installed needs to be a separate computer from the SQL Server, the middleware server and the web server. Note: a second web server (ww.dll) is required of you plan on using Print At Home Tickets module. 6

When running E-Commerce module, it is important to purchase a Processor License for Microsoft SQL Server. This is a Microsoft requirement for web-based access of SQL Server and not doing this violates your license agreement with Microsoft. Siriusware Inc. supports ProtoBase, VersaPay (Orbital), Payment Express (AUS/NZ clients) and OCV (AUS/NZ clients) for E-Commerce transactions, not DirectNet or Tender Retail. Web pages hosted externally The diagram below shows how E-Commerce web pages can be hosted externally. 7

Web pages hosted internally The diagram below shows how E-Commerce web pages can be hosted internally. Note: An SMTP server can be hosted externally even when the pages are hosted internally, though this configuration is not shown in this diagram. 8

Rentals architecture The Rentals module environment includes Self-Entry stations, Rental TechStations, salespoints and either a web/rental server or separate web and rental servers. For most installations, a combined web/rental server is sufficient. The following diagram shows separate web and rental servers. 9

Food Service architecture The following diagram shows a Table Service Food and Beverage module installation that implements a FileSync server. The FileSync server is used to ensure that operations aren t interrupted in the event that the connection is lost to the database server. (Quick Service Food and Beverage module does not implement a FileSync server, because all sales are finalized immediately.) 10

Scan access architecture The following diagram shows a typical scan access (ScanMan module) hardware configuration. 11

Axess Gates architecture The following diagram shows a typical Axess Gates hardware configuration: 12

Mobile Sales architecture The following diagram shows a typical Mobile Sales configuration. 13

Typical WAN architecture The following diagram shows the recommended configuration for connecting a remote Salesware site to the data center over a WAN connection. Note: that Siriusware Inc. recommends a minimum 256 Kbps connection and use of a remote desktop connection to run SysManager and ReportManager from the remote site. If SysManager and ReportManager are used directly on a salespoint at the remote site, Siriusware Inc. recommends a minimum 1 Mbps connection. If a slower connection is used, performance may be poor. It is possible to connect a small number of salespoints to the data center over a 56K dial-up connection, but performance may be extremely slow and the process of downloading updates or rebuilding local data at a salespoint could take many hours. Note: Salesware also supports WAN configurations where multiple Salesware sites are connected over a WAN. Each site has its own data center (SQL Server database), but ticket and pass validation can occur between sites. These configurations are described in the Salesware Validation document. 14

Network configuration Siriusware Inc. recommends a network domain if you are managing more than ten computers on your network. A domain setup offers easier control of your security and users. In addition, it works with SQL Server Reporting Services for custom reports and facilitate PCI compliance. Here are sever key points of utilizing a Domain versus Workgroup network configuration. Domain Pros Offers centralized control of users and security on network Easier to control sharing and accessibility across your network Shared log-in and passwords across network Easier to maintain PCI compliance Cons Requires an IT savvy person and domain controller. Workgroup Pros Easy to set up No additional cost to configure Cons Requires security management at each individual PC that gets more labor intensive as the network grows Potential PCI issues (too open of a network) Does not work with Reporting Services on SQL Server 2008 or newer. Anonymous connections not allowed. Sharing printers and network resources can get complicated 15

Less stable environment due to the aforementioned reasons Salesware system specifications The following sections present recommended Salesware system specifications. Refer to the diagrams in the first section of this document for information regarding configurations. Networking is required; this can be via an Ethernet or a wireless connection. Siriusware s policy is not to support operating systems not supported by Microsoft. These are the reasons why we don t: Microsoft is no longer providing security updates, so it is risky for anyone to use a non-supported operating system. Clients are not in compliance with PCI if they use non-supported operating systems. It may be impossible for us to resolve issues with an operating system we cannot get support on. Third party products our software uses may not work. Currently, Windows 95, Windows 98, Windows Me, Windows NT and Windows XP are not supported. Note: E-Commerce module is not supported on non-server operating systems. E-Commerce module must be deployed on Windows Server 2008 or Windows Server 2012. The requirements for management stations running SysManager or ReportManager are the same as those for standard salespoints, except less disk space is required. Note: Failover clustering using Microsoft clustering software is in use by several Siriusware clients. Clustering is transparent to the applications and users of the database. Windows XP end of life Beginning on April 9, 2014, Microsoft will no longer support or provide security patches for the Windows XP operating system. PCI compliance requires that you ensure all payment system components are protected from known security vulnerabilities. If you are running Siriusware applications on Windows XP computers, it will become extremely difficult for you to ensure your system is protected against emerging security threats and remain compliant with PCI. 16

Important notes: Use of a supported operating system is outlined in PCI DSS Requirement 6.1, which requires that the merchant (you) ensure that all system components and software are protected from known vulnerabilities by regularly applying vendor-supplied security patches. Since Microsoft will not provide these after April 8, 2014 for Windows XP, it is difficult for you to meet this requirement if you use Windows XP for your Siriusware system. Your simplest course of action is to stop using the Windows XP operating system for Siriusware applications. For more information, consult a PCI Qualified Security Assessor or see https://www.pcisecuritystandards.org/faq/ and search for article #1130. Additionally, use of a computer operating system that is not regularly updated with security patches could put your site at risk. It is also Siriusware's policy to only support Windows operating systems that are currently supported by Microsoft. After April 8, 2014, Siriusware will no longer support Windows XP. This means that future versions of the Siriusware product may not operate on Windows XP. Also, if incompatibility issues are found that are operating system related, Siriusware may not be able to resolve them. To ensure the longest product lifecycle possible, Siriusware Inc. recommends upgrading to a recently released operating system such as Windows 7 or Windows 8. If you have questions concerning replacement hardware compatibility or wish to inquire about obtaining replacement computer hardware through Siriusware, our Hardware Specialist is happy to assist you. Using virtual servers Microsoft Virtual Server or VMware allows several virtual servers to run on a single, powerful server. Although Siriusware Inc. does not officially support virtual servers, several clients have incorporated virtual servers into their network infrastructure. The hardware requirements for all Siriusware servers must be met when configuring your virtual servers. If you have qualified IT staff that can configure, support and diagnose issues with virtual servers, Siriusware has no problem with it. However, as with all network issues, Siriusware Technical Support staff is not able to help diagnose and resolve issues with virtual servers. Please be sure you have the inhouse expertise before considering using virtual servers. 17

32-bit vs. 64-bit Most processors for sale today are x64 (64-bit). You have the choice of running 32-bit or 64-bit operating systems and database server software on these processors. The minimum and recommended specifications provided in this section call for a 32-bit operating system and 32-bit version of SQL Server. Clients who choose to use 64-bit operating systems and/or a 64-bit version of SQL Server consults Microsoft specifications and adjust accordingly. Note: Salesware is not supported on IA-64 ( true 64-bit) processors from Intel. 18

Recommended standard salespoint configurations In addition to the requirements shown in the table, one or two empty PCI slots are useful for future expansion, but not a necessity. A CD-ROM drive, as well as an uninterruptable power supply (UPS) keeps power up for at least fifteen minutes and are highly recommended. Parallel, serial and USB ports are required as necessary to support peripherals specific to a salespoint. Module Component Minimum The minimum hardware requirements correspond to the minimum OS; other OSes require higher than minimum. Recommended Operating system Vista or windows 7 Windows 7 or Windows 8 Processor 2 GHz or faster Windows 7 2 GHz or faster Standard salespoint Free space on hard drive 40 GByte 1 160 GByte RAM 4 GByte or more Windows 7 or 8 4 GByte or more Video 1024x768, 24-bit video/monitor resolution 1280x1024 (or better) 24-bit video/monitor resolution Network 10/100 Mbit Ethernet 100/1000 Mbit Ethernet 1 For management stations running SysManager or ReportManager, 100 MByte is the minimum requirement and 1 GByte is recommended. 19

Middleware Each hardware installation is different; there is not a single generic answer for all hardware installations. This section is intended to give a few basic guidelines. For twenty salespoints or less, the middleware can be run on the database server. Be sure to include any SysManager or ReportManager stations as salespoints in this calculation. For more than twenty salespoints, a separate middleware server is used. That server adheres to the following requirements. In addition, a common strategy to increase middleware response is to partition middleware components across multiple servers. Example: SalesEZ application can be deployed on one server while BookEZ application is deployed on another. Using this approach, each server adheres to the following requirements. Module Component Requirements Operating system Windows Server 2012 / 2008/ 2003 Pool/SalesEZ or Pool/BookEZ Processor Memory Free Disk Space Multi-core / 1 core per 20 connections 4 GByte 20 GByte Display 1024 x 768 Network Notes 100/1000 Mbit Ethernet Middleware computers ideally are located on the same very fast network as the SQL Server. 20

Note: If you use ScanMan and/or GateKeeper modules, a separate Pool/SalesEZ application is used for those devices so they do not compete for CPU time with regular salespoints. For larger installations, we feel that having roughly twenty connections per CPU core are the maximum saturation. Some clients have a higher ratio, but to find the magic number requires knowing what kind of transactions a typical. For instance, extensive use of Max4Sale capability forces you to keep a lower ratio. You may be able to increase this number with experimentation, but be aware that the risk is slowing down the response times of your salespoints. Note: for the purpose of calculating the number of connections, you must add SalesEZ and BookEZ connections together. Therefore, a single salespoint with bookings enabled connecting to a single middleware server counts as two connections. Example: There is an installation of forty-five salespoints and five GateKeeper instances. Eighteen of the salespoints also do bookings. For this install, you have at least three (or better yet four) cores doing the work. One instance of Pool/SalesEZ application using two or three CPU cores for the forty-five salespoints, a second instance of Pool/ SalesEZ application using one CPU core for the five GateKeeper instances and a third instance of Pool Service running BookEZ application using a single CPU core for the fifteen Bookings stations. With these numbers, it works out that you could run all of these on a single Quad-core box. If you were using virtual computers, we suggest having one VM with three cores running the two Pool/SalesEZ application installs and a second VM with a single core running Pool/BookEZ application. If there were ten GateKeeper instances instead of five, we suggest placing Pool/SalesEZ instance on its own computer with its own single core. Example: Multisite installation: Three sites with ten salespoints each with no bookings. On the surface, it might appear that a single core might be able to handle the load. Thirty per core is above our recommendation, but, plausible in some cases. However, with three sites, we would recommend that each site be given its own Pool/SalesEZ application on its own core. The reasons are for troubleshooting. If one site is having trouble, but the other two sites are fine, it is easier to isolate issues when the sites are not sharing a single Pool/SalesEZ application installation. Important: Siriusware Inc. recommends that your Middleware server be placed on a battery backup system (UPS) capable of lasting at least forty-five minutes. This ensures that your operation continues to run smoothly when you experience power issues. 21

Number of SalesEZ application instances The default number of SalesEZ application instances that start up running under Pool Management is three. We consider this the normal minimum number. The optimal number is, according to some research, the number of CPU cores plus one. So, for a quadcore computer, the optimal number is five SalesEZ instances. This number comes with some conditions though. It assumes that Pool/SalesEZ application is the only application running on that computer. So, if you have both Pool/BookEZ and Pool/SalesEZ applications running on the same computer, that number is no longer valid. In that case, we would suggest leaving the default at three instances. Database server Database server hardware is selected based on the number of salespoints that are supported. If more than seventy-five salespoints are supported, special consulting services is used to determine the exact configuration for the network. In general, SQL Server must be dedicated to Salesware applications only and not used by other applications. Siriusware Inc. supports SQL Server 2012 and SQL Server 2008. For less than twenty salespoints, the middleware can be run on the database server. A backup strategy with the necessary hardware to support it are required. A battery backup system (UPS) capable of lasting at least forty-five minutes helps prevent a variety of potential database corruption problems. A DVD is highly recommended. Keeping your data on a separate drive system from your operating system helps to improve the speed of the database server. The minimum and recommended requirements call for SQL Server 2008 Standard Edition, 32-bit (and therefore a 32-bit operating system). Please consult Microsoft SQL Server requirements if using a different version, including the following links: Note: Version 4.3 of the software requires either SQL 2008 or SQL 2012. http://msdn.microsoft.com/en-us/library/bb545450.aspx (SQL Server 2008 and SQL Server 2012) 22

Number of salespoints 2 Component Minimum The minimum hardware requirements correspond to the minimum OS; other OSes require higher than minimum. Recommended Operating system Windows Server 2003 Windows Server 2012 with 64bit SQL Server 2014 Less than 20 salespoints Processor Dual core or better Multi-core (4+) Free space on hard drive 100 GBytes per year of data. Ten years is the recommended length of time to plan for, so you have 1000 GByte of free space. Also, you have a separate drive system for holding backups with enough space for several full backups and differentials. Thus, if you have a 25 GByte database, you would need approximately 100 GByte of free space for backups. Most installations therefore require two separate drives systems, each with at least 100 GByte free. Approximately 40 GByte is normally required for the operating system. RAM 4 GByte 8+ GByte Video 1024 x 768 1280/1024 or larger Network 10 Mbit Ethernet 100\1000 Mbit Ethernet Operating system Windows Server 2003 Windows Server 2012 with 64bit SQL Server 2014 Processor Dual-core or better Multi-core 2 The numbers provided are for Classic salespoints. For sites that implement the E-Commerce module, you adjust your calculations to accommodate for the Sales Host utility. A good rule-of-thumb is that a Sales Host is equivalent to 1 5 Classic salespoints, depending on your application and load. 23

20-49 salespoints Free space on hard drive 100 GByte per year of data. Ten years is the recommended length of time to plan for, so you have 1000 GByte of free space. 1000 GByte is recommended. Also, you have a separate drive system for holding backups with enough space for several full backups and differentials. Thus, if you have a 25 GByte database, you would need approximately 100 GByte of free space for backups. Most installations therefore require two separate drives systems, each with at least 100 GByte free. Approximately 40 GByte is normally required for the operating system. RAM 4 GByte 8-32 GByte Video 1024 x 768 1280 / 1024 or larger Network 10 Mbit Ethernet 100/1000 Mbit Ethernet Operating system 32Bit Windows Server 2008 or newer with 32bit SQL Server 2005 Windows Server 2012 with 64bit SQL Server 2014 Processor Quad Core or better Multi-core (8+ i.e., i7 or better) 50-75 salespoints 3 Free space on hard drive 100 GByte per year of data. Ten years is the recommended length of time to plan for, so you have 1000 GByte of free space. 1000 GByte is recommended. Also, you have a separate drive system for holding backups with enough space for several full backups and differentials. Thus, if you have a 25 GByte database, you would need approximately 100 GByte of free space for backups. Most installations therefore require two separate drives systems, each with at least 100 GByte free. Approximately 40 GByte is normally required for the operating system. RAM 4 GByte 8-32 GByte 3 With larger venues (over fifty salespoints), the specifications are increased. The server is an enterprise solution with a two-channel RAID controller and a RAID 1/5 split, dual-processors and 4 GByte RAM. High-speed drives (15K RPM) are recommended. 24

Video 1024 x 768 1280/1024 or larger Network 10 Mbit Ethernet 100/1000 Mbit Ethernet SQL Server Express Edition As of July 1, 2012, Siriusware Inc. no longer supports using SQL Express as the primary Siriusware database. We recommend that clients using SQL Express make plans to purchase and upgrade to a supported version of SQL (SQL 2008 or SQL 2012 Standard or Enterprise versions). Unless you already own a supported version, you purchase SQL 2012, Microsoft s latest version. As of July 1, 2012, issues related to the use of SQL Express are not covered by your support contract. In the past, we felt that small installations that do not use E-Commerce or Access Control modules could effectively use SQL Express. However, due to the evolution of our product and the catastrophic failure that can occur if the database size limit of SQL Express is reached, we have made the decision to no longer support SQL Express. If your site reaches the database size limit (10GByte for SQL Express 2008), your system abruptly stops functioning causing severe operational issues. Additionally, new reports are now written using Microsoft Reporting Services using functionality that SQL Express does not fully support. Eventually, all reports will use Microsoft Reporting Services. Web (E-Commerce) For web servers, a minimum 256K Internet connection is required; a 1.5 Mbit or greater connection is recommended. A UPS is recommended. Important: These specifications are for an average volume of web transactions. For higher volume sites please contact Siriusware Client Services to determine your specific needs. Also, a second web server (ww.dll) is required of you plan on using Print At Home Tickets module. 25

Server Component Minimum The minimum hardware requirements correspond to the minimum OS; other OSes require higher than minimum. Recommended Operating system Vista, Windows 7 Windows Server 2012 Processor 1 GHz or faster Windows 7 2 GHz or faster Sales Host Free space on hard drive 20 GByte 160 GByte RAM 2 GByte or more Windows 7 4 GByte or more 4 Video 1024x768, 24-bit color 1280x1024 Network 10/100 Mbit Ethernet 100/1000 Mbit Ethernet Database 500 MBytes to 1 GByte per year 500 MBytes to 1 GByte per year Bandwidth 3Mbps up /down 3Mbps up /down Middleware Quad Core Quad core or better Operating system Windows Server 2008 Windows Server 2012 Processor 1 quad core 1 quad core 4 Print At Home Tickets module requires large amounts of memory. High-volume clients must consider using up to 4 GByte. 26

Server Component Minimum The minimum hardware requirements correspond to the minimum OS; other OSes require higher than minimum. Recommended Web Server (running E- Commerce Pages + ww.dll, web pages hosted internally) Free space on hard drive 100 GByte 160 GByte+ RAM 8 GByte or more 16 GByte or more Video 1024x768 1280x1024 Network 100/1000 Mbit Ethernet 100/ 1000 Mbit Ethernet Operating system Windows Server 2008 Windows Server 2012 Web Server (running wwservice + ww.dll, web pages hosted externally) Processor 1 quad core 1 quad core Free space on hard drive 100 GByte 160 GByte + RAM 16 GByte or more 16 GByte or more Video 1024x768 1280x1024 Network 100/1000 Mbit Ethernet 100/1000 Mbit Ethernet 27

Rentals A UPS is recommended. Station Component Minimum The minimum hardware requirements correspond to the minimum OS; other OSes require higher than minimum. Recommended Operating system Windows 7 Windows 7 or 8 Self-Entry Station and Rental Tech Station Processor 1 GHz or faster Windows 7 2 GHz or faster Free space on hard drive 20 GByte 160 GByte RAM 2 GByte Windows 7 4 GByte or more Video 1024x768, 24-bit color 5 1024x768, 24-bit color Network 100 Mbit Ethernet 100/1000 Mbit Ethernet Operating system Windows Server 2008 Windows Server 2008 or 2012 64 bit Processor 2 GHz or faster 2 GHz or faster, multicore CPU Free space on hard drive 50 GByte 160 GByte 5 A resolution of 800x600, 16-bit color, can be used for Self-Entry Stations if scrolling isn t required and the number of controls displayed is not too great. 28

Station Component Minimum The minimum hardware requirements correspond to the minimum OS; other OSes require higher than minimum. Recommended Separate Rental Server (for more than 25 connections) RAM 4 GByte 4 GByte or more Video 1024x768, 24-bit color 1280x1024, 24-bit color Network 100Mbit Ethernet 100/1000 Mbit Ethernet Web Server and combined Web/Rental Server Operating system Windows 2008 Windows 2012 Server Processor 2 GHz or higher 3 GHz or higher, multiple CPU Cores Free space on hard drive 50 GByte 160 GByte RAM 4 GByte or more 4 GByte or more Video SVGA XGA Network 100 Mbit Ethernet 100/1000 Mbit Ethernet 29

Food and beverage FileSync server Food and beverage sites utilize numerous salespoints based on the standard specifications. However, FileSync application is often implemented to ensure that operations continue in the event of a loss of connectivity to the database server. The following specification is for the FileSync server, which may also be used as a salespoint if needed. FileSync application is used only for Table Service Food and Beverage module (not Quick Service Food and Beverage module). Component Minimum The minimum hardware requirements correspond to the minimum OS; other OSes require higher than minimum. Recommended Operating system Windows Server 2008 Windows Server 2008 or 2012 Processor 2 GHz or faster 2 GHz or faster, multiple core CPU Free space on hard drive 50 GByte 160 GByte RAM 4 GByte 4 GByte or more Video 1024x768 1280x1024 Network 100 Mbit Ethernet 100/1000 Mbit Ethernet 30

Folio Charge Folio Charge module is deployed on a standalone workstation with the following requirements. Component Minimum The minimum hardware requirements correspond to the minimum OS; other OSes require higher than minimum. Recommended Operating system Windows 7 Windows 7 or 8 Processor 1 GHz or faster Windows 7 2 GHz or faster Free space on hard drive 20 GByte 160 GByte RAM 2 GByte Windows 7 4 GByte or more Video 1024x768 1280x1024 Network 100 Mbit Ethernet 100/1000 Mbit Ethernet 31

Mobile Sales Salesware Service application, utilized with Mobile Sales module, is installed on a separate server with the following requirements Station Component Minimum The minimum hardware requirements correspond to the minimum OS; other OSes require higher than minimum. Recommended Operating system Windows Server 2008 Windows 2012 Server Salesware Service Processor 1 GHz or faster 2 GHz or multiple core Free space on hard drive 20 GByte 160 GByte RAM 2 GByte 4 GByte or more Video 1024x768 1280x1040 Network 100 Mbit Ethernet 100/1000 Mbit Ethernet Operating system Windows 7 Windows 7 or Windows 8 Processor Windows 7 1 GHz or faster Windows7 2 GHz or faster Mobile Sales Host Free space on hard drive 20 GByte 160 GByte RAM 4 GByte or more 4 GByte or more 32

Station Component Minimum The minimum hardware requirements correspond to the minimum OS; other OSes require higher than minimum. Recommended Video 800x600, 16-bit color 1280x1040 Network 10/100 Mbit Ethernet 100/1000 Mbit Ethernet Database 500 MBytes to 1 GByte per year 500 MBytes to 1 GByte per year Bandwidth 3Mbps up /down 3Mbps up /down Middleware Quad Core Quad core or better 33

Reserved Seating Station Component Minimum The minimum hardware requirements correspond to the minimum OS; other OSes require higher than minimum. Recommended Operating system Windows Server 2008 Windows 2008 or 2012 Server Salesware Service Processor 1 GHz or faster 2 GHz or multiple core Free space on hard drive 20 GByte 160 GByte RAM 2 GByte 4 GByte or more Video 1024x768 1280x1040 Network 100 Mbit Ethernet 100/1000 Mbit Ethernet 34