Transcription

Oracle MICROS SimphonyServer Sizing GuideRelease 19.2F32383-02May 2021

Oracle MICROS Simphony Server Sizing Guide, Release 19.2F32383-02Copyright 2010, 2021, Oracle and/or its affiliates.This software and related documentation are provided under a license agreement containing restrictions onuse and disclosure and are protected by intellectual property laws. Except as expressly permitted in yourlicense agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license,transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverseengineering, disassembly, or decompilation of this software, unless required by law for interoperability, isprohibited.The information contained herein is subject to change without notice and is not warranted to be error-free. Ifyou find any errors, please report them to us in writing.If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it onbehalf of the U.S. Government, then the following notice is applicable:U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software,any programs embedded, installed or activated on delivered hardware, and modifications of such programs)and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Governmentend users are "commercial computer software" or "commercial computer software documentation" pursuantto the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such,the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works,and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programsembedded, installed or activated on delivered hardware, and modifications of such programs), ii) Oraclecomputer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in thelicense contained in the applicable contract. The terms governing the U.S. Government’s use of Oracle cloudservices are defined by the applicable contract for such services. No other rights are granted to the U.S.Government.This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applications thatmay create a risk of personal injury. If you use this software or hardware in dangerous applications, then youshall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure itssafe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of thissoftware or hardware in dangerous applications.Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks oftheir respective owners.Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks areused under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc,and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registeredtrademark of The Open Group.This software or hardware and documentation may provide access to or information about content, products,and services from third parties. Oracle Corporation and its affiliates are not responsible for and expresslydisclaim all warranties of any kind with respect to third-party content, products, and services unless otherwiseset forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will notbe responsible for any loss, costs, or damages incurred due to your access to or use of third-party content,products, or services, except as set forth in an applicable agreement between you and Oracle.

ContentsPreface1Simphony Server SizingPurpose1-1Server Sizing Methodology1-1A Note on Virtualization1-1Disk Capacity Sizing1-2Database Objects used for Simphony2341-2Local Disk and RAID ConfigurationsStorage Area Networks2-1Operating System Version Options2-2Database OptionsMicrosoft SQL Server3-1Which Version of Database Should be Used?3-1Oracle Database3-1Server Replication and Clustering3-2Oracle Real Application Cluster (RAC)3-2Network Load BalancingLarge Configurations (50 Workstations)4-1Reporting Application Servers4-1Simphony Server SpecificationsConfigurations Larger than 5000 Workstations4-14-3Database Server Size4-3Database Server Quantity4-4Application Server Sizing4-4Application Server Quantity4-5iii

Additional Assistance4-5iv

PrefacePurposeThis document is designed to offer guidance on the topics involved in sizing a serverfor an Oracle MICROS Simphony version 19.2 system, as well as provide minimumspecifications for hardware purchases. The server configurations published in thisdocument are based on analysis of data collected in lab and production environmentsand designed to offer the best possible performance.Due to the fact that many environments have nuances specific to them, theseguidelines should be used as a starting point when selecting server hardware. Once asystem has gone live in the production environment, it may be necessary to modify theserver configuration to account for customer specific requirements and conditions.AudienceThis document is intended for users of Simphony.Customer SupportTo contact Oracle Customer Support, access My Oracle Support at the following URL:https://support.oracle.comWhen contacting Customer Support, please provide the following: Product version and program/module name Functional and technical description of the problem (include business impact) Detailed step-by-step instructions to re-create Exact error message received and any associated log files Screenshots of each step you takeDocumentationOracle Food and Beverage product documentation is available on the Oracle HelpCenter at /.Acronyms and AbbreviationsThe following acronyms and abbreviations are used throughout this document:Table 1Acronyms and AbbreviationsAcronymFull TextCPUCentral Processing UnitIISInternet Information Servicev

PrefaceTable 1(Cont.) Acronyms and AbbreviationsAcronymFull TextNLBNetwork Load BalancingRAIDRedundant Array of Inexpensive DisksRAMRandom Access MemorySANStorage Area NetworkCAPSCheck and Posting ServiceDTSData Transfer ServiceDPSDirect Posting ServiceRevision HistoryTable 2Revision HistoryDateDescription of ChangeOctober 2020Initial publication.May 2021Minor update to version references.vi

1Simphony Server SizingReview the Simphony Server Sizing information outlined below:PurposeThis document is designed to offer guidance on the topics involved in sizing aserver for the most recent Simphony version system as well as provide minimumspecifications for hardware purchases. The server configurations published in thisdocument are based on analysis of data collected in lab and production environmentsand designed to offer the best possible performance.Due to the fact that many environments have nuances specific to them, theseguidelines should be used as a starting point when selecting server hardware. Once asystem has gone live in the production environment, it may be necessary to modify theserver configuration to account for customer specific requirements and conditions.Server Sizing MethodologyThere are three main components to servers: Central Processing Unit (CPU) Random Access Memory (RAM) StorageEach component has factors that determine proper sizing. At a high level, CPU andmemory are driven by the number of users and the type of processing, for example,transaction processing versus report generation. Disk configuration is driven by dataretention length, system configuration (revenue centers, menu items, and employees),resiliency and necessity for speed of access. Long-term storage of such data belongsin a warehouse such as Reporting and Analytics. Ideally, memory on a databaseserver should be sized to keep index objects and/or table objects in the buffer cache.This reduces IO latency and reduces the wait for reads.In addition to the physical attributes of the server, it is necessary to select the correctversions of database and operating system software. At a minimum, the versionschosen for these items must be able to support the hardware that is going to bepurchased.A Note on VirtualizationAll recommendations put forth herein regarding the resource requirements forhardware when sizing a Simphony platform are applicable to Virtualized environmentsas well as physical ones when current Virtualization technologies such as OracleVirtualbox are used. Current technologies incur no real overhead cost, and thereforedo not require separate consideration when choosing resource requirements.1-1

Chapter 1Disk Capacity SizingDisk Capacity SizingThe amount of disk space necessary for a system is driven by the amount of historicaldata, backups, and database log files retained on the drives. There are two areas thataccount for the majority of the database growth: Check details used for online transaction access (Transaction Data) Simphony Reporting and Analytics dataBy default, the system automatically purges checks and their associated details thatare used for online check access after six (6) weeks from the transaction database.The Simphony Reporting and Analytics data accumulates for as long as desired. Thereporting database contains check detail, totals, and electronic journal information.The following values can be used as a guideline to determine how much space adatabase uses. It should be noted that testing used for these figures was based onfast transactions averaging 10 line items per check. Sites with multiple rounds or largecheck sizes experience more database growth.Database Objects used for SimphonyThe reporting database grows at rate of approximately 20 MB per 1000 checks. Thosenumbers are approximate values and may vary depending on individual setup andconfiguration.The following databases/schemas/tablespaces* are used in a Simphony environment.Table 1-1Simphony TablespacesDatabase/Schema NamePurposeAutoExtendMax SizeInitial SizeGrowthExpectation**TransactionTRANSACTION staging DBDBYesUnlimited128MB*** Medium**SECURITYDBSecurity ration of YesUsers andOrganizations(Reporting &Analytics)Unlimited128MBNegligibleLOCATION AC Historical dataYesTIVITY DBDB (Reporting uration of Yesthe PortalWebsite(Reporting &Analytics)Unlimited128MBNegligibleRTARTA agent DB(Reporting &Analytics)Unlimited128MBNegligibleYes1-2

Chapter 1Disk Capacity SizingWhen working with Oracle Database, the schema is the name of the logical placewhere tables are stored, the tablespace is the definition of the physical file that is givensize parameters.** Names of these databases (schemas) are chosen during installation. There is nostandard naming convention.*** The size of the TRANSACTIONDB remains relatively consistent as oldertransactions are purged; adding workstations or revenue centers typically causes thesize to grow to a new consistent level.1-3

2Local Disk and RAID ConfigurationsFrom an application perspective, Simphony does not require any type of RedundantArray of Inexpensive Disks (RAID) configuration. In fact, the application is oblivious tothe physical configuration of the disks. However, some form of redundancy such asRAID is strongly recommended for local storage on Database servers.Depending on the performance and disaster recovery requirements for a customer,there are a wide number of possible hard drive configurations available. Users shouldconsult a current reference, for example https://en.wikipedia.org/wiki/RAID, and theirstorage manufacturer’s recommendations before selecting a configuration.RAID may allow for hardware redundancy and performance enhancements dependingon what solution is chosen. Some of the solutions are more costly than others. Inevery situation, it is recommended that the RAID controller have a battery backedread/write cache.Note:For high volume deployments, it might be necessary to utilize a storagesystem or two RAID controllers, so that the loads for transaction databasesare being separated from the reporting databases. If magnetic hard drivesare used, it is that only SAS type hard disks with 10k or 15k rpm shouldbe used; SATA type hard disks are currently not considered sufficient.Alternatively, some or all of the local storage can be retained on SolidState drives (SSD); these are significantly more expensive, but provide muchhigher I/O speeds.Storage Area NetworksSome large scale customers may wish to implement a Storage Area Network (SAN)instead of using local hard drives. SANs are typically used with database servers tohouse the data files and logs.This option, while more costly than local drives, becomes necessary as soon ashigh availability (HA) and database redundancy options are considered (such asOracle RAC). A SAN also allows customers to have an option to put the data on aninfrastructure that can be shared amongst other servers and can be expanded moreeasily than if the data were stored on local drives.Simphony Customers that wish to use a SAN are required to configure their serverhardware according to the size recommendations that are provided. Oracle Hospitalityis not responsible for installing and setting up an on premise SAN.2-1

Chapter 2Operating System Version OptionsOperating System Version OptionsSimphony versions 19.2 and later are supported on either Microsoft Windows Server2012 R2 or Microsoft Windows Server 2016. The specific Edition of Microsoft WindowsServer selected depends on several factors. For more details on Microsoft WindowsServer edition differences, refer to this Microsoft webpage.A Simphony database server is supported using the Oracle Linux operating system.See the Oracle Food and Beverage Compatibility Matrix for more information onsupported database versions.2-2

3Database OptionsThe Oracle Food and Beverage Compatibility Matrix and Oracle MICROS SimphonyRelease Notes provide more information on supported databases.Oracle Hospitality recommends the use of Oracle Database 18c.Customers upgrading from 9700 HMS to Simphony who are running earlier versionsof either Microsoft SQL Server or Oracle Database must upgrade to a currentlysupported database platform.Microsoft SQL ServerBeginning with Simphony versions 19.2 and later, Microsoft SQL Server is no longersupported as a database platform for the Simphony Enterprise application server. It isstill supported for CAPS clients.Which Version of Database Should be Used?The server configuration tables that appear later in this guide include a minimumversion of Oracle Database that needs to be used in order to make use of thehardware resources recommended for the server. A more recent version (up to themaximum listed above) may be used whenever desired. Also, when selecting adatabase platform and version, make certain not to waste hardware resources byselecting a version that cannot utilize all of the server’s memory or CPU capabilities.Oracle DatabaseCommon practices for the Oracle Database platform:1.B-tree indexes are useful for queries that are highly selective, highly filtered on thecolumn(s) that are indexed.2.Do not use Oracle bitmap queries on Simphony or Reporting & Analytics. Bitmapqueries are designed for nightly batch-loaded systems, not for either real-timeoperational systems or for real-time reporting.3.Collect statistics each night.4.Rebuild indexes monthly or perhaps even weekly.5.As with any database, perform capacity planning based not on expected oraverage load, but on the once-a-year peak time.6.It is crucial to keep your data correctly purged; failure to do so can slowly turn anoperational transaction system into a multi-year historical reporting database.3-1

Chapter 3Server Replication and ClusteringServer Replication and ClusteringIn addition to building servers that have hardware redundancy solutions for individualcomponents, it may be desirable to also have multiple servers of the same type. Forinstance, in the event of a complete server failure (not just a hard drive), the systemcan readily function on a backup server.Oracle Real Application Cluster (RAC)Oracle RAC is available for customers who have experience implementing andmanaging Oracle RAC configurations. It is expected that the customer is able to installand configure the Oracle RAC and provide on-going management of the database ifthis configuration is used.The Simphony installation media is not Oracle RAC aware.3-2

4Network Load BalancingIn previous Oracle Hospitality POS products, solutions like Double Take and Legatowere used to provide fault tolerance if the application server were to suffer a completefailure. These products are not supported for use with Simphony. Instead, networkclustering and load balancing solutions can be used to achieve a degree of resiliencythrough redundancy, in addition to their primary function of improved throughput. Thereare two primary means to implement this solution.The Microsoft Windows Server software contains a feature called Network LoadBalancing (NLB) which may be used to cluster the application servers together. Thisoption does not require any additional licensing costs.Hardware solutions can also be used to handle this functionality. These solutions aremore expensive than implementing the Microsoft Windows based solution, but canprovide a higher degree of flexibility and configuration options.Network load balancing detects server failure and balances the load on the remainingconfigured application servers. Network load balancing does not detect failure ofservices (including IIS).Large Configurations (50 Workstations)Configurations larger than 50 workstations are not supported on a shared server. Thistype of configuration must be split across a minimum of two servers, with applicationand database on dedicated servers. Additional servers may be added as necessary forresiliency purposes.Reporting Application ServersImplementing a dedicated reporting server or an additional application server shouldbe considered when the number of users simultaneously running reports exceeds11. By moving the Simphony Reports web server to different hardware than thetransaction application servers, it is possible to isolate reporting activities fromnegatively impacting transaction performance.See the Oracle Hospitality Enterprise Back Office Server Sizing Guide for moreinformation regarding Reporting Application Servers.Simphony Server SpecificationsKeep the following in mind when reviewing the specification tables: Not Applicable (N/A) indicates that the option is not available SANs could be used instead of HDD for 500 workstations or more. Requiredstorage space depends on the size, number of checks, and how long you storethem.4-1

Chapter 4Reporting Application ServersTable 4-1ServerType/LevelServer CountsServer Countsup to 50WSup to 200WS201–500WS501–1000WS1001–2000 WS2001–4000 WS4001 WSSimphony SharedServer1N/AN/AN/AN/AN/AN/ASimphony AppServerLevel 1N/A12N/AN/AN/AN/ASimphony DBServerLevel 1N/A12N/AN/AN/AN/ASimphony AppServerLevel 2N/A112N/AN/AN/ASimphony DBServerLevel 2N/A112N/AN/AN/ASimphony AppServerLevel 3N/A112234Simphony DBServerLevel 3N/A112222Table 4-2ServerType/LevelSimphonySharedServer*Server SpecificationsServer SpecificationsCPURAMHDDDataRedoCRS4 cores32 GB100 GB(OS)N/AN/AN/AN/AN/AN/A500 GB100 GB24 GB200 GB(App)500 GB(DB)500 GB(Redo Log)SimphonyApp ServerLevel 14 coresSimphonyDB ServerLevel 116 cores16 GB100 GB(OS)200 GB(App)48 GBN/A4-2

Chapter 4Configurations Larger than 5000 WorkstationsTable 4-2(Cont.) Server SpecificationsServer SimphonyApp ServerLevel 24 cores32 GB100 GB(OS)N/AN/AN/ASimphonyDB ServerLevel 216 cores64 GBN/A1 TB100 GB24 GBSimphonyApp ServerLevel 38 cores64 GB100 GB(OS)N/AN/AN/ASimphonyDB ServerLevel 332 cores2 TB200 GB24 GB200 GB(App)200 GB(App)128 GBN/ANote:*All-In-One systems do not support Suites Management, Simphony VenueManagement, Gift and Loyalty, or Simphony ServiceHost, as all of theserequire a MS SQL Database. A maximum of one property is recommendedwhen using a Shared Server.For more information on R&A Server Sizing, see the Oracle HospitalityEnterprise Back Office Server Sizing Guide.Configurations Larger than 5000 WorkstationsThe sizing requirements for a system with more than 5000 workstations are moredifficult to accurately recommend. The following guidelines should be understood:Database Server SizeWhen enterprises become larger than 5000 workstations, it is hard to predict just howmuch CPU, RAM and disk space is required. In many of these enterprises, there isa wide variance in the quantity of menu items, employees, and content stored in thedatabase. Additionally, the volume of checks coming in and the average size of thosechecks vary greatly; only general guidance can be provided.Minimally, a Dual Quad Core CPU based server is recommended as a baseline forreally large systems. Depending upon how much farther over 5000 workstations thesystem is going to go, consideration should be given up front to purchasing serverhardware with the ability to add up to four CPUs, even if only two are purchasedinitially. The option to add CPUs can be exercised over time, as the load dictates.4-3

Chapter 4Configurations Larger than 5000 WorkstationsWhen it comes to RAM, beginning with a minimum of 64 GB and having room to growis prudent. At a relatively low cost, it is possible to procure servers today that arecapable of expanding to hundreds of gigabytes. The amount of RAM consumed bythe database grows as an enterprise grows. Careful monitoring needs to take place toensure that the database servers do not become memory starved. Customers shouldbe prepared to add RAM as the system grows over time.Disk space usage grows as new properties are brought on line and more transactionsstart flowing in. Expect to see the transaction database grow and plateau as aresult of each property coming on line. When a property comes online, there isnew configuration data stored in the database. By default, check storage is disabledin Simphony. When the check storage option is enabled, up to 30 days worth oftransaction data can be stored.The Simphony reporting database also continues to grow based on the same rulesthat apply to smaller systems. For large reporting systems that keep multiple years ofhistorical transactional data — which can grow up to 10-20TB of disk space — it maybe advisable for customers to persist their Simphony data on a SAN, where additionalresources can be added when needed. Installing the Simphony database files ontolocal hard drives limits the systems growth potential.Database Server QuantityThe Oracle HA database solution for fault tolerance and load balancing is calledthe Real Application Cluster (RAC). This technology is used by the Oracle hostingcenter today. One of the advantages of RAC is that it provides load balancing. RACprocesses database requests against the database and there is no down time asa passive instance is brought on line if the primary server fails. If the load on thedatabase servers increases over time, more servers can be added to the cluster togain computing power.Application Server SizingApplication servers do not typically consume a large amount of server resources in theSimphony platform. Database servers are where most of the I/O and CPU/RAM usageoccurs. That being said, application servers still need to be configured with the properresources to handle the workload, primarily through IIS and various other Simphonyweb services. Oracle Hospitality recommends that customers operate all of the webservices which are capable of being load balanced on every application server andto place a load balancer (either a software load balancer or a hardware device) infront of the application servers to distribute the load. It is also possible to dedicateindividual servers to do some, or even individual jobs needed by the application. Forexample, a single server, or even multiple servers that only run the Direct PostingService. Servers that run only the EGateway service and no other services. Thisall depends on the requirements of the enterprise and how the customer wants todistribute the application load. The inherent extensibility and both the horizontal andvertical scalability of the architecture allow infinite combinations of services to meet theneeds of an enterprise only limited by the hardware available (both real and virtual).As for disk sizing, the only growth items on an application server are the log files whenit comes to the Simphony application. The Simphony application itself is not very I/Ointensive on the disk side of the hardware. The size of the enterprise does not impactthe disk usage to the point where different recommendations must be made for largercustomers.4-4

Chapter 4Configurations Larger than 5000 WorkstationsRAM is a crucial resource. RAM requirements for large enterprises are where theapplication servers can greatly vary, based primarily upon the number of menu itemsand employees configured in the system. The application server caches data for useby the EMC and Database Download Handlers. The cached data is used to speedup the performance of the system in those applications. Other processes such as theposting handler, Data Transfer Service (DTS) and Direct Posting Service (DPS) alsorequire RAM.Since application servers are load balanced, it is possible for a request for any of theprocesses to come to an application server, it is necessary to load the servers withenough RAM to handle everything on all of the servers; or as mentioned above, to splitthe application servers even further into even more specialized servers that handlespecific tasks within the enterprise. When deciding upon how much memory to put intoan application server, it is important to consider what the operating system is actuallycapable of supporting.Application Server QuantityThe application server count recommendation is driven by the total number of servicesthat connect to the enterprise. It is recommended that the total number of applicationservers be equivalent to the total number of services divided by 2000.The following services need to be counted when making this determination: Simphony Clients Check and Posting Service (CAPS) Kitchen Display System (KDS) Controller ServicesTechnically, the EMC and reporting user counts also impact server performance.Unless those counts are very high, there is no need to factor them into the equation. Ifthere is concern over the impact that these items may have on the system, then theyshould be counted like the services when making the recommendation for applicationservers.For example, if a system has 3000 Simphony clients, 1000 properties (with one CAPSand one KDS per property), and 12 EMC users, then the total number of items is 5012.Using the value of 2000 as the break point, the customer requires three applicationservers to handle the load. An additional application server – which brings the total tofour servers – is recommended to provide resilience in the event a server fails.Additional AssistanceFor additional assistance with large configurations, please liaise with your OracleHospitality Account Manager, and share the following information: Number of Workstations by Types (WS5a, WS6, Workstation 2015, Tablets, etc.) Total Number of Properties Total Number of Revenue Centers Total Number of Employees Total Number of Employees running reports Total Number of Menu Items Average Checks per Day (indicating peak business throughput)4-5

Simphony Server Sizing. Review the Simphony Server Sizing information outlined below: Purpose. This document is designed to offer guidance on the topics involved in sizing a server for the most recent Simphony version system as well as provide minimum specifications for hardware purchases. The server configurations published in this