OPERA v5 Hardware Sizing Guide

(v5.0.04, v5.5.0, v5.5.1)

MAY 2016
Disclaimer
The following is intended to outline our general product direction. It is intended for information
purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any
material, code, or functionality, and should not be relied upon in making purchasing decisions. The
development, release, and timing of any features or functionality described for Oracle’s products
remains at the sole discretion of Oracle.

OPERA V5 HARDWARE SIZING GUIDE

Table of Contents

Disclaimer 1

Purpose 4

Intended Audience 4

Sizing Methodology 4

Large installs (Over 140 connections) 4

Resiliency and Redundancy 5

Mitigating Business Risk - Risk vs. Cost 5

Supported Platforms 5

Determining existing server information 6

Opera Upgrades 6

Compatibility Chart 7

Hardware Sizing For Opera 9

Additional considerations 9

OPERA Single Server Sizing 10

Separate OPERA Application / Database Server Sizing 14

OXI PC / Server Sizing 17

Windows Server OXI HUB Queue Manager Sizing 18

Windows Server OWS, GDS, OAP Server Sizing 18

OPERA Interface PC and Workstation Hardware Sizing 19

Guidelines for Determining OPERA User Counts 21

1 | OPERA V5 HARDWARE SIZING GUIDE

Frequently Asked Questions 23

Virtualization, Terminal Services, Citrix Support 24

Hard Drive Configurations and Specifications 24

Storage Area Network Devices 24

Backup and Antivirus Information 25

Oracle Hospitality Network Requirements 27

Local Area Network (LAN) Requirements 27

Wide Area Network (WAN) Requirements 27

Introduction to Network Design 28

Local Area Network (Internal Network) 28

Demilitarized Zone (DMZ) 29

External Network 29

Overview of Required Network Communication Ports 30

Graphical View 32

OPERA Server and Application Components 33

Property Management System (PMS) Servers 33

OPERA Electronic Distribution Suite (OEDS) Servers 33

OEDS Servers with a direct connection to the internet 34

OEDS Servers without a direct connection to the internet 34

OPERA eXchange Interface (OXI) Components and Server(s) 34

OXI External System NOT Posting Into OPERA Network 37

OXI Variations Summary 37

2 | OPERA V5 HARDWARE SIZING GUIDE

 Property Level Interfaces 39

OPERA Client/Server Communications 40

Secure Socket Layer (SSL) and OPERA 40

Wireless Access Points and OPERA 42

User Accounts 43

Windows User Accounts 43

Active Directory 43

Active Directory Integration to OPERA 43

Credit Card Data Flow 44

Known Issues and Security Enhancements 44

Virtualization 45

OPERA Hardware Sizing Template 46

3 | OPERA V5 HARDWARE SIZING GUIDE

Purpose
This document is intended to provide an understanding and reference point to correctly sizing OPERA Property
Management System and its secondary applications.

This Sizing Guide is for current versions of OPERA, including v5.0.04 and v5.0.05 but the sizing recommendations
can be used for any version of OPERA v5.

Intended Audience
This document contains Oracle proprietary information for Oracle Employees and Customers.

Sizing Methodology
There are 3 primary components considered when sizing servers:

» CPU
» Memory
» Disks

Each component has factors that determine proper size. At a High level, CPU and Memory are driven by the
number of users and the type of processing. Disk configuration is driven by data size and the necessity for speed of
access (Reduced I/O contention).

The sizing guidelines published in this document are based on analysis of empirical data from many previous
installations as well as load testing results. The hardware specifications are based on available hardware at the
time of writing.

The number of connections is the sum of the number of workstations with the ability to connect to OPERA at one
time plus the number of external connection sources, i.e. third party software, interface workstations, etc.

Example and generic calculations for determining the user equivalent load of CRS interfaces, GDS and OWS are
included in this document and must be considered.

Server sizes are designed to support all OPERA modules in any configuration, as long as the numbers of
connections are not exceeded. Compatibility and performance of OPERA Hotel Servers with other products such as
Yield Management, Materials Management or Back office products has not been evaluated and should be
considered separately when specifying servers.

Large installs (Over 140 connections)

Larger installs classified as greater than 140 users will require a detailed analysis for proper sizing. Contact your
Oracle Hospitality Sales or Account Executive for help with large configurations, as there are many possibilities
based on customer preference.

4 | OPERA V5 HARDWARE SIZING GUIDE

Resiliency and Redundancy

Mitigating Business Risk - Risk vs. Cost

The amount of investment a hotel makes in Resiliency and Redundancy should be judged to equal the business risk
i.e. the larger the hotel, the greater the number of users and services should mean a greater investment in
Resiliency and Redundancy. This may mean an investment in:

» High quality, long standby time UPS with integrated Power Filters
» Best Practices for Backups and regular restore testing

Today’s servers are very powerful and give us the ability to handle very large numbers of connections. However, it
may be sensible from a business risk perspective to use one of the resilient configurations available rather than
putting both DB and Application services on a single server. If a hotel IT manager is unsure, they should get a
recommendation for Resiliency and Redundancy best practices from Oracle Hospitality.

OPERA Versions
This is a hardware sizing document for current versions of OPERA. All references to supported environments and
platforms are in reference to OPERA version 5.0.04 and 5.0.05. Please contact Oracle Hospitality for
recommendations on Hardware Sizing for other versions of OPERA.

Supported Platforms
As of this writing OPERA versions less than 5.0.04.03 are only certified on Windows 2008r2.

Windows Server 2012r2 is only certified for OPERA versions v5.0.04.03 and above including Database, Application
and Single Servers.

OXI, Property Interfaces and HTNG Interfaces are certified on Windows 7 as well as Windows 2008r2.

All references to “Windows 2008” in this document are to be understood as references to Windows 2008r2.
Windows 2008r1 is not considered to be a valid platform for OPERA installations.

All references to Windows 2008r2 in this document include Windows 2008r2 Standard or Enterprise Server
unless otherwise noted.

All references to Windows 7, 8 or 8.1 in this document include Windows 7, 8 or 8.1 Professional, Enterprise
or Ultimate unless otherwise noted. Both x32 and x64 are supported unless otherwise noted. NO Starter or
Home versions are supported.

5 | OPERA V5 HARDWARE SIZING GUIDE

All references to Windows 2012 in this document mean Windows 2012r2 Standard Server unless otherwise
noted.

Determining existing server information

If you are looking to upgrade your OPERA environment and need to determine if your current system is able to
handle the load, there are a few key pieces of information that Oracle Hospitality will need to effectively determine
sizing.

First we need your property information, including:

 Total Concurrent Users (number of OPERA users that will be in the system at once)

 Total Number of Properties

 Total number of Property Interfaces

 Total number of OXI Interfaces

 Total number of HTNG and other Interfaces

*To estimate concurrent users, a general guideline is 10% of the hotel room count.

Second, we need your current OPERA Server details, including:

 Operating System

 Number and speed of CPU

 Amount of RAM

 Speed and size of disks

 Array configuration and Drive Layout

Opera Upgrades
While the upgrade process is very straight forward, the hotel should ensure that there is a successful and valid
backup of the OPERA Application folder (D:\MICROS) and the Oracle database through the Oracle agent. Failure to
do so may result in total data loss should unexpected issues arise.

6 | OPERA V5 HARDWARE SIZING GUIDE

Compatibility Chart
*Please see all notes below the compatibility chart

*1 Also available for the following Epatches:

5.0.03.01 E32+

5.0.03.02 E23+

7 | OPERA V5 HARDWARE SIZING GUIDE

 5.0.03.03 E17+

*2 Also available for the following Epatches:

5.0.03.01 E26+

5.0.03.02 E16+

5.0.03.03 E08+

Oracle Database version 11.2.0.4 is also supported for OPERA versions 5.0.04+

*3 OPERA Advanced Reporting and Analytics/OPERA Sales and Catering Reporting and Analytics versions
are released as Sprints. Please ensure the latest Sprint Version available is applied. Both Applications
are built on Oracle Business Intelligence (OBI). OPERA Advanced Reporting and Analytics on OBI 11g is
compatible with OPERA from version 5.0.04.02 e5 and above. OPERA Sales and Catering Advanced
Reporting on OBI 11g is compatible with OPERA version 5.0.04.02 e20 and above.

NOTE: Neither OPERA Advanced Reporting and Analytics NOR OPERA Sales and Catering Reporting
and Analytics are compatible with OPERA Professional Premium and Standard Cloud Service.

OBI 11g works with Microsoft Internet Explorer 11. The latest security patch for the OBIEE tool can be
downloaded from oracle.com and should be applied.

The version matrix is checked by the OBI Install wizard.

*4 Oracle Application Server 10g has reached “Sustaining” Support in the lifecycle and it is therefore
recommended to upgrade to a Version of OPERA that supports Oracle WebLogic 11g. See the “Oracle
Fusion Middleware Lifecycle” Document available here for further information:
http://www.oracle.com/us/support/library/lifetime-support-middleware-069163.pdf

*5 As Microsoft is de-supporting IE 8,9, and 10 on January 12, 2016, it is highly recommended that clients
upgrade to IE 11 to avoid being exposed to potential security risks after that date. The minimum OPERA
Version supported to work with IE 11 is V5.0.04.01E-patch 21. Please see link
(https://support.microsoft.com/en-us/lifecycle#gp/Microsoft-Internet-Explorer) for the announcement from
Microsoft.

*6 As Microsoft terminated support for Windows 2000, 2003 Servers, it is highly recommended that clients
upgrade to the latest Servers to receive security updates and patches. Please see the link
(http://support.microsoft/com/en-
us/lifecycle/search/default.aspx?sort=PN&alpha=Windows%20server&Filter=FilterNO) for the
announcement from Microsoft.

*7 OPERA Professional Premium/Standard Cloud Service and OPERA Enterprise Premium/Standard Cloud
Service are now browser agnostic. This add support to any modern Operating System and Browser
(including Microsoft Internet Explorer 11 (Version 9.0.1.18.06 forward) and Microsoft Edge. For security
and compatibility purposes, please ensure to update both the operating system and browser to the latest
available versions.

8 | OPERA V5 HARDWARE SIZING GUIDE

*8 Supported from 5.0.04.03 Epatch 7 and higher. Edge Browser is not supported with OPERA 5. The Edge
Browser is supported with OPERA Cloud.

Hardware Sizing For Opera

This section detailed the minimum and recommended configurations to ensure that OPERA will perform optimally.
Between each of these configurations there are some standard requirements that need to be discussed. This will
ensure that there are no unexpected issues during and after installation or upgrade.
1. A dedicated server is required for most Oracle Hospitality products. Please contact your Sales Executive or
Account manager for further assistance or clarification.
2. The server cannot be used as a workstation.
3. The OPERA server should be housed in a secure area with limited access.
4. Printers should normally be connected to a print server or workstations and not the OPERA server. If they are
installed to the OPERA server performance may suffer.
5. Consideration should be given to using a separate workstation for support connectivity.

Additional considerations
» Concurrent Connections is the sum of the number of workstations with the ability to connect to OPERA at one
time plus the number of external connection sources, i.e. third party software, interfaces, Web Booking, etc...
» Servers are sized to support hot backups using 3rd party backup solutions that use an Oracle Agent.
» Raid level 5 not supported for drives containing database data files due to disk write performance impact. Using a
lesser number of drives than recommended can negatively impact I/O performance, regardless of the size of the
disks or the amount of space needed. Number of drives is more important than size for I/O distribution. It is not
intended that external disk storage be required for standard installations. Configurations for Database or Single
Server are based on SAS controllers and drives with < 5ms seek times. Recommended drive configurations are
Raid 10 (Also referred to as RAID 1+0).
» Application server sizing is based on 1 CPU core per 40 concurrent users and 64MB RAM per concurrent user.
» Raid levels 1, 5 or 10 are supported for Application servers. The OPERA Application Server is not I/O intensive
but requires disk space for storage of Night Audit reports and export files as well as temporary space used in
generating other reports. Disk space requirements may change in a multi-property environment or if multiple
Applications servers are present in the same environment.
» When using multiple applications servers a shared disk location for Night Audit reports and exports will need to be
available via UNC path. It is recommended that UNC locations are not on an OPERA Application server.
» For multiple Applications servers Oracle Hospitality recommends the implementation of Hardware Network Load
balancers. Please be advised that Oracle Hospitality does not configure hardware load balancers. It is possible
but not recommended to use a software based load balancer (e.g. Windows Network Load Balancing or DNS
round robin). It is recommended to properly size a single Application server rather than multiple Application
servers if the customer IT staff is not able to install, configure and manage a hardware load balancer.

9 | OPERA V5 HARDWARE SIZING GUIDE

 OPERA Single Server Sizing
 OPERA Single Server combines the Oracle Database and the OPERA Application onto one server
 All OPERA servers must be dedicated only to OPERA and can serve no other purpose

OPERA Single Server Specifications

Up to 20 Users (No more than 8 interfaces and 1 OXI interface on this hardware)
Windows 2008r2 Standard or Enterprise Windows 2008r2 Standard or Enterprise
Operating System
Windows 2012r2 Standard only for 5.0.04.03+ Windows 2012r2 Standard only for 5.0.04.03+

Minimum Recommended

CPU 4 Cores, 1.8 GHz or faster 4 Cores, 1.8 GHz or faster

Memory Minimum 16 GB 16 GB

4 Disks – 15k SAS drives, all disks in a single

2 Disks – 10k SAS drives, both drives in a RAID1
RAID1+0 array. Disks should be a minimum of
array. Disks should be a minimum of 146gb each.
300gb each.
Disk Minimum
Recommend 100gb C: drive and remainder of
Recommend 100gb C: drive and remainder of
available space assigned to D: drive (at least
available space assigned to D: drive (at least
100gb). OPERA software will be installed by
200gb). OPERA software will be installed by
default on D: drive.
default on D: drive.

NOTE: Hardware RAID controller is required in NOTE: Hardware RAID controller is required in
order to use RAID. Software RAID controller is not order to use RAID. Software RAID controller is not
supported. supported.

Enterprise level 4-8 port RS232 Serial expansion Enterprise level 4-8 port RS232 Serial expansion
Interface Ports card or Serial to IP device (built in surge protection card or Serial to IP device (built in surge protection
highly recommended) highly recommended)

Although Oracle Hospitality does not configure or Although Oracle Hospitality does not configure or
support customer backups, a backup location will support customer backups, a backup location will
be needed. A disk, tape or offsite (cloud) backup be needed. A disk, tape or offsite (cloud) backup
Backups
location will need to be configured by the customer location will need to be configured by the customer
IT staff to be able to fully backup the OPERA IT staff to be able to fully backup the OPERA
Database and Application files. Database and Application files.

Printer Networkable Laser printers with PostScript drivers are recommended.

10 | OPERA V5 HARDWARE SIZING GUIDE

 OPERA Single Server Specifications
Up to 40 Users (No more than 8 interfaces and 1 OXI interface on this hardware)
Windows 2008r2 Standard or Enterprise Windows 2008r2 Standard or Enterprise
Operating System
Windows 2012r2 Standard only for 5.0.04.03+ Windows 2012r2 Standard only for 5.0.04.03+

Minimum Recommended

CPU 4 Cores, 1.8 GHz or faster 4 Cores, 1.8 GHz or faster

Memory Minimum 16 GB 24 GB

8 Disks – 10k SAS drives, all disks in a single 8 Disks – 15k SAS drives, all disks in a single
RAID1+0 array. Disks should be a minimum of RAID1+0 array. Disks should be a minimum of
146gb each. 300gb each.
Disk Minimum
Recommend 100gb C: drive and remainder of Recommend 100gb C: drive and remainder of
available space assigned to D: drive (at least available space assigned to D: drive (at least
200gb). OPERA software will be installed by 200gb). OPERA software will be installed by
default on D: drive. default on D: drive.

NOTE: Hardware RAID controller is required in NOTE: Hardware RAID controller is required in
order to use RAID. Software RAID controller is order to use RAID. Software RAID controller is
not supported. not supported.

Enterprise level 4-8 port RS232 Serial expansion Enterprise level 4-8 port RS232 Serial expansion
Interface Ports card or Serial to IP device (built in surge card or Serial to IP device (built in surge
protection highly recommended) protection highly recommended)

Although Oracle Hospitality does not configure or Although Oracle Hospitality does not configure or
support customer backups, a backup location will support customer backups, a backup location will
be needed. A disk, tape or offsite (cloud) backup be needed. A disk, tape or offsite (cloud) backup
Backups
location will need to be configured by the location will need to be configured by the
customer IT staff to be able to fully backup the customer IT staff to be able to fully backup the
OPERA Database and Application files. OPERA Database and Application files.

Printer Networkable Laser printers with PostScript drivers are recommended.

11 | OPERA V5 HARDWARE SIZING GUIDE

 OPERA Single Server Specifications
Up to 80 Users (No more than 8 interfaces and 1 OXI interface on this hardware)
Windows 2008r2 Standard or Enterprise Windows 2008r2 Standard or Enterprise
Operating System
Windows 2012r2 Standard only for 5.0.04.03+ Windows 2012r2 Standard only for 5.0.04.03+

Minimum Recommended

CPU 2 x 4 Cores, 1.8 GHz or faster 2 x 4 Cores, 1.8 GHz or faster

Memory Minimum 24 GB 24 GB

8 Disks – 10k SAS drives, all disks in a single 8 Disks – 15k SAS drives, all disks in a single
RAID1+0 array. Disks should be a minimum of RAID1+0 array. Disks should be a minimum of
300gb each. 300gb each.
Disk Minimum
Recommend 100gb C: drive and remainder of Recommend 100gb C: drive and remainder of
available space assigned to D: drive (at least available space assigned to D: drive (at least
200gb). OPERA software will be installed by 300gb). OPERA software will be installed by
default on D: drive. default on D: drive.

NOTE: Hardware RAID controller is required in NOTE: Hardware RAID controller is required in
order to use RAID. Software RAID controller is order to use RAID. Software RAID controller is
not supported. not supported.

Enterprise level 4-8 port RS232 Serial expansion Enterprise level 4-8 port RS232 Serial expansion
Interface Ports card or Serial to IP device (built in surge card or Serial to IP device (built in surge
protection highly recommended) protection highly recommended)

Although Oracle Hospitality does not configure or Although Oracle Hospitality does not configure or
support customer backups, a backup location will support customer backups, a backup location will
be needed. A disk, tape or offsite (cloud) backup be needed. A disk, tape or offsite (cloud) backup
Backups
location will need to be configured by the location will need to be configured by the
customer IT staff to be able to fully backup the customer IT staff to be able to fully backup the
OPERA Database and Application files. OPERA Database and Application files.

Printer Networkable Laser printers with PostScript drivers are recommended.

12 | OPERA V5 HARDWARE SIZING GUIDE

 OPERA Single Server Specifications
Up to 140 Users (No more than 8 interfaces and 1 OXI interface on this hardware)
Windows 2008r2 Standard or Enterprise
Operating System
Windows 2012r2 Standard only for 5.0.04.03+

Recommended

CPU 2 x 4 Cores, 1.8 GHz or faster

Memory Minimum 32 GB

16 Disks – 15k SAS drives, all disks in a single

RAID1+0 array. Disks should be a minimum of
300gb each.
Disk Minimum
Recommend 100gb C: drive and remainder of
available space assigned to D: drive (at least
400gb). OPERA software will be installed by
default on D: drive.

NOTE: Hardware RAID controller is required in

order to use RAID. Software RAID controller is not
supported.

Separate Interface workstation or server

Interface Ports
recommended

Although Oracle Hospitality does not configure or

support customer backups, a backup location will
be needed. A disk, tape or offsite (cloud) backup
Backups
location will need to be configured by the customer
IT staff to be able to fully backup the OPERA
Database and Application files.

Printer Networkable Laser printers with PostScript drivers are recommended.

13 | OPERA V5 HARDWARE SIZING GUIDE

 Separate OPERA Application / Database Server Sizing
 All OPERA servers must be dedicated only to OPERA and can serve no other purpose.

Separate OPERA Application / Database Server Specifications

Up to 40 Users (No more than 8 interfaces and 1 OXI interface on this Application Server)
Windows 2008r2 Standard or Enterprise Windows 2008r2 Standard or Enterprise,
Operating System Windows 2012r2 Standard only for 5.0.04.03+
Windows 2012r2 Standard only for 5.0.04.03+

Application Server Database Server

CPU 4 Cores, 1.8 GHz or faster 4 Cores, 1.8 GHz or faster

Memory Minimum 8 GB 16 GB

6 Disks – 15k SAS drives, all disks in a single

2 Disks – 10k SAS drives, both drives in a RAID1
RAID1+0 array. Disks should be a minimum of
array. Disks should be a minimum of 146gb each.
146gb each.
Disk Minimum
Recommend 100gb C: drive and remainder of
Recommend 100gb C: drive and remainder of
available space assigned to D: drive (at least
available space assigned to D: drive (at least
100gb). OPERA software will be installed by
100gb). OPERA software will be installed by
default on D: drive.
default on D: drive.

NOTE: Hardware RAID controller is required in NOTE: Hardware RAID controller is required in
order to use RAID. Software RAID controller is order to use RAID. Software RAID controller is not
not supported. supported.

Enterprise level 4-8 port RS232 Serial expansion

Interface Ports card or Serial to IP device (built in surge N/A
protection highly recommended)

Although Oracle Hospitality does not configure or Although Oracle Hospitality does not configure or
support customer backups, a backup location will support customer backups, a backup location will
be needed. A disk, tape or offsite (cloud) backup be needed. A disk, tape or offsite (cloud) backup
Backups
location will need to be configured by the location will need to be configured by the customer
customer IT staff to be able to fully backup the IT staff to be able to fully backup the OPERA
OPERA Database and Application files. Database and Application files.

Printer Networkable Laser printers with PostScript drivers are recommended.

14 | OPERA V5 HARDWARE SIZING GUIDE

 Separate OPERA Application / Database Server Specifications
Up to 80 Users (No more than 8 interfaces and 1 OXI interface on this Application Server)
Windows 2008r2 Standard or Enterprise Windows 2008r2 Standard or Enterprise,
Operating System Windows 2012r2 Standard only for 5.0.04.03+
Windows 2012r2 Standard only for 5.0.04.03+

Application Server Database Server

CPU 4 Cores, 1.8 GHz or faster 4 Cores, 1.8 GHz or faster

Memory Minimum 16 GB 16 GB

6 Disks – 15k SAS drives, all disks in a single

2 Disks – 10k SAS drives, both drives in a RAID1
RAID1+0 array. Disks should be a minimum of
array. Disks should be a minimum of 300gb each.
300gb each.
Disk Minimum
Recommend 100gb C: drive and remainder of
Recommend 100gb C: drive and remainder of
available space assigned to D: drive (at least
available space assigned to D: drive (at least
100gb). OPERA software will be installed by
200gb). OPERA software will be installed by
default on D: drive.
default on D: drive.

NOTE: Hardware RAID controller is required in NOTE: Hardware RAID controller is required in
order to use RAID. Software RAID controller is order to use RAID. Software RAID controller is
not supported. not supported.

Enterprise level 4-8 port RS232 Serial expansion

Interface Ports card or Serial to IP device (built in surge N/A
protection highly recommended)

Although Oracle Hospitality does not configure or Although Oracle Hospitality does not configure or
support customer backups, a backup location will support customer backups, a backup location will
be needed. A disk, tape or offsite (cloud) backup be needed. A disk, tape or offsite (cloud) backup
Backups
location will need to be configured by the location will need to be configured by the
customer IT staff to be able to fully backup the customer IT staff to be able to fully backup the
OPERA Database and Application files. OPERA Database and Application files.

Printer Networkable Laser printers with PostScript drivers are recommended.

15 | OPERA V5 HARDWARE SIZING GUIDE

 Separate OPERA Application / Database Server Specifications
Up to 140 Users (No more than 8 interfaces and 1 OXI interface on this Application Server)
Windows 2008r2 Standard or Enterprise Windows 2008r2 Standard or Enterprise,
Operating System Windows 2012r2 Standard only for 5.0.04.03+
Windows 2012r2 Standard only for 5.0.04.03+

Application Server Database Server

CPU 6 Cores, 1.8 GHz or faster 2 x4 Cores, 1.8 GHz or faster

Memory Minimum 24 GB 16 GB

4 Disks – 10k SAS drives, all disks in a single 8 Disks – 15k SAS drives, all disks in a single
RAID1+0 array. Disks should be a minimum of RAID1+0 array. Disks should be a minimum of
300gb each. 300gb each.
Disk Minimum
Recommend 100gb C: drive and remainder of Recommend 100gb C: drive and remainder of
available space assigned to D: drive (at least available space assigned to D: drive (at least
200gb). OPERA software will be installed by 300gb). OPERA software will be installed by
default on D: drive. default on D: drive.

NOTE: Hardware RAID controller is required in NOTE: Hardware RAID controller is required in
order to use RAID. Software RAID controller is not order to use RAID. Software RAID controller is not
supported. supported.

Separate Interface workstation or server

Interface Ports N/A
recommended

Although Oracle Hospitality does not configure or Although Oracle Hospitality does not configure or
support customer backups, a backup location will support customer backups, a backup location will
be needed. A disk, tape or offsite (cloud) backup be needed. A disk, tape or offsite (cloud) backup
Backups
location will need to be configured by the customer location will need to be configured by the customer
IT staff to be able to fully backup the OPERA IT staff to be able to fully backup the OPERA
Database and Application files. Database and Application files.

Printer Networkable Laser printers with PostScript drivers are recommended.

16 | OPERA V5 HARDWARE SIZING GUIDE

OXI PC / Server Sizing
In most cases the OXI component of the application can reside on the application server however Oracle Hospitality
recommends that interfaces that require the ability to post into the OPERA network from the Internet be separated
from the OPERA network using a DMZ. Contact a qualified IT consultant for assistance with this configuration.

Windows 7 Pro x64, Windows 8 Pro x64

Operating System Windows 2008r2 Standard
Windows 2012r2 Standard only for 5.0.04.03+

OXI Server /Workstation

CPU 4 Cores, 1.8 GHz or faster

Memory Minimum 8 GB

Disk Minimum 1 Disk – at least 80gb free space available after

Operating System is installed

* OPERA OXI needs to be on a separate workstation or server in a DMZ if one or more of the following interfaces
are configured:

 Passkey

 SynXis 2 way

 Vistera / OPEN

 Hospitality

 Rainmaker

 Travelclick

 Any interface that receives data directly from the internet

* This list is not necessarily all inclusive

17 | OPERA V5 HARDWARE SIZING GUIDE

Windows Server OXI HUB Queue Manager Sizing
OXI HUB messages per day (Note1) < 75,000 75,000 – 200,000

OXI HUB messages per day (Note1) Up to 200,000

CPU 1 x Quad Core
Monitor Server Memory 8 GB
Drive Count x size 1 x 80 GB

Windows Server OWS, GDS, OAP Server Sizing

Services (Note 2) Sizing
CPU 1 x Quad Core
Per Major Distribution Channel, GDS Pegasus, GDS XML ,
OWS XML etc.. (1 server will support 50,000 messages per Memory 8 GB
hour)
Drive Count x size 1 x 80 GB
CPU 1 x Dual Core
Up to 2 low volume XML interfaces, (< 1000 messages per
Memory 8 GB
hour)
Drive Count x size 1 x 80 GB

Note 1: Estimating OXI messages per day. (Total number of Rooms / Avg stay length) * 2) * %Occupancy. Use of
statistics from existing central interfaces will provide a more accurate determination of the number of messages per
day.
Note 2: Estimating OWS messages. ((Annual bookings) * % annual bookings acquired from internet) * 1000
Availability requests per actual booking) = OWS messages per year.
OWS messages per year / 365 = OWS messages per day.
Typical internet traffic occurs in peaks. Assume that all the messages per day are actually processed within a 12
hour period.
OWS messages per day / 12 hours = Average OWS hourly message load.
Average OWS XML message size = 1.5 Kbytes

18 | OPERA V5 HARDWARE SIZING GUIDE

OPERA Interface PC and Workstation Hardware Sizing

Windows 7 Pro This formula can be used in determining the memory for an interface
Windows 8 Pro workstation or server.
OS Windows 8.1 Pro
80MB for each installed property interface, defined as Voicemail, Call
Interface Windows 2008r2
Accounting, Movies, etc.
Workstation
or Server CPU 2 Cores Add 40MB per additional PMS in case of Multi-Property setup.
Memory 4 GB Add 150MB for the IFC Controller.
Min. Free
20 GB
Disk
Minimum Recommended
Windows 7 Pro Windows 7 Pro See Note 5 for minimum OPERA versions
Windows 8 Pro Windows 8 Pro supported on each OS.
OS
Windows 8.1 Pro Windows 8.1 Pro
Windows 10 Pro Windows 10 Pro Windows 10 Pro or Enterprise must be x64.
CPU 2 Cores 2 Cores
User Memory 3 GB 4 GB Internet Explorer 7, 8, 9, 10 and 11 are supported.
Workstation For IE 10 and 11, OPERA must be a minimum
version 5.0.04.00/3
Min. Free
100 MB 200 MB The Edge Browser is not supported.
Disk

Note 1: Minimum workstation configuration supports one OPERA Session and a small application (< 5 MB memory usage).
Users who require multiple OPERA sessions or use other large applications may require more RAM and other resources.

Note 2: Bandwidth of 16kb (kilobits) per user minimum available to OPERA for WAN connections. WAN latency should be
below 80ms for a 1k packet (ping –l 1024) for optimal performance. If the WAN circuit is used to transport other software
like email, web browsing, etc. then it is highly recommended that QOS (Quality of Service) software or a dedicated circuit be
used to ensure that mission critical applications have priority use of the bandwidth.

Note 3: Workstations installed with personal firewall software and/or anti-virus clients could require additional memory.

Note 4: Both 32bit and 64bit workstations are supported unless otherwise noted. On 64bit workstations, the 32bit browser
must be used.

Note 5: OS Minimum Supported OPERA version

Windows 7 Pro 5.0.04.00
Windows 8 Pro 5.0.04.00/3
Windows 8.1 Pro 5.0.04.01/21, 5.0.04.02/12, 5.0.04.03/7
Windows 10 Pro x64 5.0.04.03/7

19 | OPERA V5 HARDWARE SIZING GUIDE

Guidelines for OPERA BI Sizing
OPERA Business Intelligence sizing will vary significantly on how the customer uses the product. Different combinations
and configuration of cubes, length of online historical data, length of future date modeling, and the configuration of OPERA
components can all impact the sizing for the BI data.
Disk space requirements can vary greatly so always err on the side of extra storage space.

Single property sizes: (See Note 1)

GB of Disk Space
GB of Disk Space Amount of extra CPU Cores
Required for
Required for OBI and Physical Memory
# of Rooms Block/Reservation
Cubes Required
Detail Data (optional)

(See Note 2) (See Note 2) (See Notes 3,4,6)

101 – 300 45 30 +1 CPU core

301 – 500 75 50 +1 CPU core
+2 CPU cores
501 – 1000 150 100
+1 GB RAM
+4 CPU cores
1001 – 2000 250 150
+2 GB RAM
+8 CPU cores
2001 – 3000 350 200
+4 GB RAM
+16 CPU cores
3001+ Custom (See Note 5) Custom (See Note 5)
+8 GB RAM

» Note 1: If there are multiple properties, then add 20% extra space for each property. (Example: A 4 multi
property OPERA installation with 1,200 rooms would need 250 + (250*(4*0.2)) = 450GB of space). If Codes and
Categories are standardized and strictly enforced, this value can be reduced to 10%.
» Note 2: The disk space requirements in the table include an additional 20% disk space allocation for larger than
standard database temp segment needs.
» Note 3: For installs larger than 1000 rooms, it is required to have a separate application server for running
OPERA BI.
» Note 4: For installs with 1000-3000 rooms, it is recommended to have a separate database server for running
OPERA BI. For installs with 3000+ rooms, it is required to have a separate database server for running OPERA
BI.
» Note 5: For custom sizing, the most accurate method for calculating needed disk space is to build sample test
cubes with customer production data. It would be preferred for this to be done before disk size requirements are
finalized.
» Note 6: For installs larger than 500 rooms, the extra physical memory will be needed for increasing the DB
parameter OLAP_PAGE_POOL_SIZE (manual memory settings) or PGA_AGGREGATE_TARGET (auto tuned
memory settings).

20 | OPERA V5 HARDWARE SIZING GUIDE

Guidelines for Determining OPERA User Counts
By far the best method for determining the correct site sizing is to get actual numbers from existing systems and
business input for changes that will occur once OPERA is deployed. Sometimes it is not possible to gather all
required information for a variety of reasons, new site, expansion, no previous comparable system, etc…

Here are some guidelines to follow to get an estimate of the hardware sizing. The numbers obtained with these
methods should be reviewed by MICROS and the Customer to ensure they understand what assumptions were
made and adjust as necessary.
1. Real users.
a. Each time a user launches a browser and logs into OPERA it counts as a User.
b. OPERA will launch Child sessions during normal use of the application. These sessions are
already included in the sizing.
c. As a rule of thumb, OPERA PMS user count averages at about 10% of the number of rooms.
Slightly higher for high end properties, and slightly lower for Express type hotels. PMS user
counts <5% or >20% of the number rooms may be fine, however they warrant a double check
with the customer to make sure they are accurate.
d. S&C and ORS user counts are very site dependent and will need to be gathered from the
customer.
2. Property interfaces
a. Count one equivalent OPERA user for 4 property interfaces in database sizing.
b. On IFC8 installations, count one equivalent OPERA user for 4 property interfaces in application
server sizing.
3. 2 way CRS interface
a. 6 Equivalent OPERA users per 1000 Rooms in database sizing.
2 methods used to establish this thumb rule. Note 1200 reservation msgs per day per user and
the 100 bookings per day per user are empirically derived from production sites and load testing
information. Since block messages can hold a large number of details, Block messages need
to be converted to equivalent reservation messages. A 10 day block with 20 rooms would
equate to 100 reservation msgs.
i. # Rooms * 7 Msgs per room per day
1200 msg per day per user = equivalent users.
ii. # Rooms * avg Stay Length * % occupancy
100 bookings per day per user = equivalent users.
b. Retention of up to 4 days of interface messages is included in the server disk sizing. If the
retention period for OXI messages is increased, additional disk space will be needed.
100 Rooms would require ~ 50MB per additional day of retention.
4. OPERA Electronic Distribution Systems (OEDS) ie.. GDS, OWS, ADS etc.
a. These interfaces can have a large effect on sizing since the actual load is generated by basically
uncontrolled end users. It is very important that the customer understand how peaks in load
from these interfaces can affect sizing / performance.

21 | OPERA V5 HARDWARE SIZING GUIDE

 b. In the past, the calculation of 250 messages = 1 OPERA user was used. Different versions of
OPERA and different rate configurations affect the cost of a OWS message so this number is
subject to changes in each customer location. Generally, take the cost (measured in logical
reads) of 1 general availability lookup message (X) and use the following formula to determine
the number of messages/hour that equal 1 OPERA user;
i. 1,200,000 / X = Messages per hour
c. If other means are not available to measure / estimate the message rate from these interfaces,
Use the following formula;
Typical electronic traffic occurs in peaks. Empirical analysis indicates that 80% of all traffic
occurs in 6 hours. For calculation purposes assume all traffic occurs in 6 hours.

(Bookings per day from interface * Look to book ratio for the interface) / 6 = average peak
messages per hour.
Est. Look to book ratios. OWS 1000, GDS 200.

22 | OPERA V5 HARDWARE SIZING GUIDE

Frequently Asked Questions
Below is a series of commonly asked questions that may help you. If you find a question that is not answered here,
please contact your Sales executive or Account Manager for assistance.

Q. What does the hardware team need to determine if a server is sufficient for OPERA?

A. Please reference the Hardware Sizing Spreadsheet. Any additional information that could be a contributing factor
should also be presented for review.

Q. What operating systems are supported for OPERA Servers?

A. Windows 2008r2 Standard or Enterprise for OPERA version v5.0.04 and above.

Windows Server 2012r2 is only certified for OPERA versions 5.0.04.03 and above.

Q. What operating systems are supported for Property Interfaces?

A:

 Windows 7 Pro, Business or Enterprise (32 or 64bit)

 Windows 8 Pro, Business or Enterprise (32 or 64bit)

 Windows 8.1 Pro, Business or Enterprise (32 or 64bit)

 Windows 2008R2 Standard or Enterprise

Q. How big should the operating system (C:) partition be?

A. Our recommendation is at least 100GB but this value is dynamic as hardware and software requirements change.

Q. What naming convention can I use for the server?

A. OPERA server names should be between 3 and 15 characters, without an underscore, space or any other
special characters. A dash (-) is acceptable but not recommended. The server name should begin with a letter and
NOT a number or any other special character. Our recommendation is to use a standard format that includes in
order the first 4 characters of the hotel name, operating system, function, and number. For example: Hotel MICROS
would be MICRPMSW2K8SS. You can amend this guideline to suit your needs as this is only offered as a
suggestion.

Q. Will Oracle Hospitality install the Operating System?

A. Yes, but only with the purchase of OPERA Server Hardware from Oracle, the server would arrive on site pre-
configured with the operating system and OPERA installed. [WHERE AVAILABLE]

23 | OPERA V5 HARDWARE SIZING GUIDE

Q. What can I not use in naming the server?

A. In order to avoid technical difficulties, do NOT use the following expressions as Computer name: OPERA,
ORACLE, Server, LocalHost, Expressions containing an underscore ( _ ), spaces, or other special characters.

Virtualization, Terminal Services, Citrix Support

Q. Are any virtualization products supported?

A. Oracle will not support the actual VM environment although OPERA Application, Database and Single Servers
can be installed in VM environments. Oracle RAC (Real Application Cluster) is not supported on any VM platform.
Oracle does not provide sizing recommendations for VM environments.

See the Support statement for Virtualization here.

Q. Do you support Terminal Services or Citrix Implementations?

A. Oracle has no technical expertise on the implementation or configuration of Terminal Services or Citrix.
Customers wishing to use these products do so at their own risk.

Q. How can we get assistance if we have a technical issue with OPERA in these environments?

A. Our Support teams will make every effort to troubleshoot any issue as long as the issue is clearly related to the
OPERA Property Management System. Oracle Support will request that you seek assistance from your third party
provider if the issue is not directly reproducible or known in a non VM, TS or Citrix environment.

Hard Drive Configurations and Specifications

Q. If the recommendation for disk drives is 8 drives, can I use 4 larger drives instead?

A. No, OPERA is an I/O intensive application that requires writing to multiple disk spindles to spread the workload
and maintain performance.

Q. What drive configurations are supported?

A. Any server or workstation that houses mission critical data should be configured using hardware Redundant Array
of Independent Disks (RAID) Level 1 or 1+0. This is a requirement for Database and Single Servers. In addition
RAID1, RAID1+0 and RAID 5 can be used for Application Servers, OXI, and OEDS servers.

Storage Area Network Devices

Q. Can I have the Oracle Datafiles on a SAN?

24 | OPERA V5 HARDWARE SIZING GUIDE

A. Yes, however the datafiles must reside on SAS drives configured in a RAID 1+0 array.

Q. What Storage Area Network (SAN) devices are supported?

A. Depending on sizing requirements, Only Direct Attached and Fiber SAN’s are currently supported with 15K SAS
drives. iSCSI is not supported.

Q. Are Network Area Storage (NAS) devices supported?

A. No. NAS Devices are not supported for OPERA Databases.

Backup and Antivirus Information

Q. What backup solutions are supported?

A. Oracle does not provide support for any customer backups. Third party products such as Symantec Backup Exec
can be used to perform hot backups, with the use of an Oracle agent, but are not supported by Oracle. Please ask
your Oracle Account Manager for the document “OPERA Backup Specifications” for more information.

Q. What exceptions need to be added to any Antivirus software for OPERA Servers?

A. Please exclude the following folders:

» C:\Oracle\Oradata
» D:\Oracle\Oradata
» D:\Oracle\Admin
» File types: .ARC, .CTL, .DBF, .ORA and .RDO

Q. What folders need to be backed up to restore OPERA?

A. Please ask you Oracle Account Manager for the document “OPERA Backup Specifications” for more information.

Q. What folders need to be backed up to restore Property Interfaces?

A. The XML information used by the interface program are stored in C:\ or D:\Fidelio.If you have SDC then additional
folders may be present such as C:\ or D:\Elevon or SDC which needs to be backed up to restore credit cards.

Q. Does Oracle recommend that the OPERA server be placed on a domain?

25 | OPERA V5 HARDWARE SIZING GUIDE

A. Absolutely. The OPERA application does not require a domain for versions 5.0.04.02 and prior however printing
and workstation / user authentication issues will be greatly reduced in a domain environment.

Additionally, OPERA is LDAP aware and can be tied into the domain environment as well.

For OPERA versions 5.0.04.03 and 5.0.05+ a domain is necessary due to SSL requirements.

Q. I don’t have a domain controller in place right now. What if I add one later?

A. For OPERA versions 5.0.04.02 and prior - No problem. OPERA only points to the NETBIOS name of the
server. If a server has been joined to the domain, the workstations will still only point to the server’s name. As an
example, if your server name is PMSSERVER.MICROS.US.INT, users would only point to PMSSERVER.
For OPERA versions 5.0.04.03 and 5.0.05+ - Once the mandatory SSL certificate request is generated there is
no way to change it and any change in the server name or domain would require the entire Opera Installation to be
removed and re-installed.

Q. Can the OPERA Server function as a domain controller?

A. No, due to PCI compliance, this is not a recommended or supported configuration.

Q. What ports does OPERA use?

A. Please refer to the section entitled “Overview of Required Network Communication Ports” later in this document.

Q. Does OPERA support SSL on port 443?

A. Yes, In order to comply with both requirement 8.4 of the PCI-DSS and requirement 3.3 of the PADSS, user
access credentials are required to be obfuscated (encrypted) when stored or in transit within the internal network.
For its OPERA Enterprise Solution products, (OPERA), the PA-DSS Implementation Guides state that in order to
comply with PCI-DSS requirement 8.4 and PA-DSS requirement 3.3, OPERA must be deployed with Secure Socket
Layer (SSLv3) certificates installed on certain OPERA servers.

Q. What print drivers do I need?

A. If the printers are to be installed on the OPERA servers then only PostScript drivers are approved. All other
devices can use PCL or PostScript.

Q. Does Opera recommend the use of USB printers?

A. No, Oracle only recommends networkable printers.

26 | OPERA V5 HARDWARE SIZING GUIDE

Oracle Hospitality Network Requirements
In general most LANs will meet or exceed these requirements. If there is any doubt that these standards cannot be
met then please consult with your qualified network technician for assistance.

Local Area Network (LAN) Requirements

All OPERA Servers and secondary applications, such as the interface workstation, should be connected to the same
network switch with a minimum of 100Mb speed. 1000Mb (Gigabit) speed is preferred.

In more complex environments utilizing technologies such as Oracle RAC, 1000Mbit is mandatory.

If NIC teaming is implemented on the servers, each team member should be connected at the same speed.

OPERA Workstations on the LAN should be connected with at least 100Mbit.

Network printers on the LAN should be connected with at least 10Mbit.

In general LANs, because of their nature, will meet all other networking requirements.

Wide Area Network (WAN) Requirements

Each OPERA user connected over the WAN will require between 16 and 20 Kbit bandwidth per user.

Each OPERA Interface connected over the WAN will require between 5 and 10 Kbit bandwidth per user connection.

The absolute WAN latency for a 1 Kilobyte packet should be below 150 ms and the average WAN latency should be
below 80 ms for optimal performance. This means bandwidth dedicated to the OPERA Application. If the WAN
circuit is used to transport other software, like email, internet connection, etc. then it is highly recommended that
QOS (Quality Of Service) software or a dedicated circuit be used to ensure that mission critical applications have
priority use of the bandwidth. The latency can be easily tested with the command

ping –n 1000 –l 1024 IPADDRESS

Which will give output like

Ping statistics for 192.168.0.104:

Packets: Sent = 1000, Received = 1000, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 3ms, Maximum = 80ms, Average = 14ms
The maximum value must not exceed 150ms, the average value must be 80ms or less.

There should normally be no lost packets.

27 | OPERA V5 HARDWARE SIZING GUIDE

Lost packets can cause performance issues and possibly disconnects from the application. There are network retry
parameters in use by Oracle Forms to account for lost packets in the connection between the client workstation and
the application server however each retry could cause the perception of an application performance issue. We don’t
have any hard numbers on how many lost packets are acceptable. The issue is more complicated than that due to
latency. Lost packets increase the average latency due to the retries. As long as that average latency remains in
an acceptable range, the application will still be ok. If that average latency for burst periods becomes too high, then
users will suffer.

In practice the latency requirement imposes a minimum bandwidth of 250Kbit in both directions. Fortunately modern
technology allows that to be easily exceeded.

Introduction to Network Design

One way to categorize the different types of computer network designs is by their scope or scale. For historical
reasons, the networking industry refers to nearly every type of design as some kind of area network. Common
examples of area network types are:
» LAN - Local Area Network
» WLAN - Wireless Local Area Network
» WAN - Wide Area Network
» MAN - Metropolitan Area Network
» SAN - Storage Area Network, System Area Network, Server Area Network, or sometimes Small Area Network
» CAN - Campus Area Network, Controller Area Network, or sometimes Cluster Area Network
LAN and WAN were the original categories of area networks, while the others have gradually emerged over many
years of technology evolution. We will only be covering those networks that are pertinent to OPERA.

Local Area Network (Internal Network)

A local area network (LAN) supplies networking capability to a group of computers in close proximity to each other
such as in an office building, a school, or a home. A LAN is useful for sharing resources like files, printers, games or
other applications. A LAN in turn often connects to other LANs, and to the Internet or other WAN.

Most local area networks are built with relatively inexpensive hardware such as Ethernet cables, network adapters,
and hubs. Wireless LAN and other more advanced LAN hardware options also exist.

28 | OPERA V5 HARDWARE SIZING GUIDE

Demilitarized Zone (DMZ)
In a DMZ configuration, most computers on the LAN run behind a firewall connected to a public network like the
Internet. One or more computers also run outside the firewall, in the DMZ. Those computers on the outside intercept
traffic and broker requests for the rest of the LAN, adding an extra layer of protection for computers behind the
firewall.

Traditional DMZs allow computers behind the firewall to initiate requests outbound to the DMZ. Computers in the
DMZ in turn respond, forward or re-issue requests out to the Internet or other public network, as proxy servers do.
(Many DMZ implementations, in fact, simply utilize a proxy server or servers as the computers within the DMZ.) The
LAN firewall, though, prevents computers in the DMZ from initiating inbound requests.

DMZ is a commonly-touted feature of home broadband routers. However, in most instances these features are not
true DMZs. Broadband routers often implement a DMZ simply through additional firewall rules, meaning that
incoming requests reach the firewall directly. In a true DMZ, incoming requests must first pass through a DMZ
computer before reaching the firewall.

External Network
A WAN spans a large geographic area, such as a state, province or country. WANs often connect multiple smaller
networks, such as local area networks (LANs) or metro area networks (MANs).

The world's most popular WAN is the Internet. Some segments of the Internet, like VPN-based extranets, are also
WANs in themselves. Finally, many WANs are corporate or research networks that utilize leased lines.

High-Level Network Diagram

General Networking Environment with OEDS \ OXI

Credit
OXI Ports
Cards Demilitarized Zone (DMZ) 80
20
PBX 21
OEDS / OXI PC 443
Network or Server 445
Printer
VSS
HP Compaq

HP Compaq
RS232 or TCP/IP

Voice Mail
HP
ProLiant
ML350
Client
Workstation
Dual Port 15k
Serial SCSI
146GB

UID
Dual Port 15k
Serial SCSI
146GB
Dual Port 15k
Serial SCSI
146GB

Clean
Tape

DVD-Drive

POS
Drive Ready
Dual Port 15k
Serial SCSI
146GB

G5
Dual Port 15k
Serial SCSI
146GB

HP StorageWorks Ultrium 920

Dual Port 15k
Serial SCSI
146GB

Ethernet

Door Lock OPERA Application / Internet

Database Server HP Compaq

Client Firewall NAT-Able

Minibar Workstation Router External Network (WAN)

Opera eXchange Interface needs to be on a separate PC or server in a

Internet DMZ environment if one of the following interfaces are configured:
Network
Printer
Passkey
Call Acc. SynXis 2 way
HP Compaq
Vistera / Open
Hospitality
Client Genares
Workstation
Rainmaker
Travelclick (pre Opera version 5.0.02.00)
Local Area Network (LAN)
Please note: This list is not inclusive and should apply to any interface that
receives any data directly from the internet.

29 | OPERA V5 HARDWARE SIZING GUIDE

Overview of Required Network Communication Ports

Port Configurable Alway s Required

Protocol Used for / Comments Serv ers
Number (Yes or No) (Yes or No)

20 / 21 N N TC P Standard FTP Ports ALL

22 N N TC P/UDP Standard Secure Shell (SSH) Port ALL

23 N N TC P Standard Telnet Port ALL

Default SMTP Port / Is required on DB

Y (DB Servers)
server
25 N TC P DB
N (Other Servers) to mail server configured in OPERA

Default HTTP Port / C an be changed

APP
(OappC fgEd)

Workstations to Application Server DB

Interface Servers (IFC 8) to Application

IFC
Servers
80 Y Y TC P
Database Servers to Application Servers OXI

Database Servers to internet IP addresses

when using certain options (e.g. Address
Doctor)
C ertain OXI interfaces also need this port

Default HTTPS Port / C an be

APP
changed(OappC fgEd)

Workstations to Application Server DB

Interface Servers (IFC 8) to Application

IFC
Servers
443 Y N TC P
Database Servers to Application Servers OXI

Database Servers to internet IP addresses

when using certain options (e.g. Address
Doctor)
C ertain OXI interfaces also need this port

30 | OPERA V5 HARDWARE SIZING GUIDE

 Port Configurable Always Required
Protocol Used for / Comments Servers
Number (Yes or No) (Yes or No)
*1 Microsoft File Sharing / Active Directory /
Y (App Server ) APP
445 N TC P / UDP Share Port
N Between Application and File Server FILE

Y (DB Servers) Default Oracle Listener Port *2 DB

N (Other Servers) Application Servers to DB Servers APP

1521 Y TCP Old Interface Servers (IFC7) to DB Servers IFC

Certain OXI Servers to DB Servers OXI
Other Servers that require an Oracle Client / SQLNet
OTH
connection to the DB

*2
Commonly used alternative Oracle Listener Port
1526 Y N TCP DB
Other commonly used ports are 1522, 1571, 1581

Oracle Connection Manager Default Port

1630 Y N TCP In some rather rare scenarios it is needed to configure DB
OCM on the DB Servers

From DB Servers to Application Servers (QAS Servers) APP

3389 N N TCP Microsoft Remote Desktop Port ALL

APP

This Port is commonly used as an alternative HTTP Port DB

4400 Y Y TCP
(see 80) IFC
OXI

Y (IFC8 Servers) The Default Port used for connections from IFC8 to the
5001 Y TCP IFC
N (Other Servers) IFC8 Controller.

5002 to Y (IFC8 Servers) Communication Ports between IFC8 and Third Party
Y TCP IFC
5020 N (Other Servers) Systems *3

1. Only needed when a UNC configuration is used for e.g. the export folder. Between Application Server and
File Server.

2. Only the initial communication takes place on this port. The connection will be handed over using a
different port above 1024. In case your Firewall does not support SQLNet, ports above 1024 will need to be
opened.

3. In most cases the IFC8 Server is tcp/ip server and the third party vendor is tcp/ip client => OPERA decides
the ports used. In rare cases the third party vendor is tcp/ip server and OPERA is tcp/ip client => the
vendor decides the ports used.

31 | OPERA V5 HARDWARE SIZING GUIDE

Graphical View

32 | OPERA V5 HARDWARE SIZING GUIDE

OPERA Server and Application Components
The OPERA Enterprise Suite has a number of different components that interact in a variety of possible
configurations.

Property Management System (PMS) Servers

Due to the scalability of the OPERA Property Management System, the database and application server
components can be configured in a number of different ways. Generally these will be based upon the volume of
transactions that will be processed on a daily basis. Our most common installation combines the Oracle Database
and Application Server components onto one server class machine (Single Server). In cases where the server
resource load is expected to be high, the OPERA PMS solution can span from a single server solution to an Oracle
Real Application Cluster, known as RAC. For more details about these configurations, please contact your sales or
account executive.

OPERA Electronic Distribution Suite (OEDS) Servers

Depending on your implementation needs, Oracle Hospitality offers a variety of products under the name OPERA
Electronic Distribution Suite (OEDS). OEDS components include many individual services and processes that may
or may not be installed or required depending on configuration and property requirements. These commonly could
include OWS, HTNG, ADS, GDS, Kiosk, or Gaming interfaces. The general behavior for all components in the suite
is similar.

At a basic level OEDS may be installed in one of two possible configurations. The first requires that the OEDS
Server be placed in a DMZ. This is necessary if the server must receive data directly from the internet. Alternately, if
there are no requirements to receive as previously mentioned then the servers should be located within the bounds
of the corporate firewall.

OXI / OEDS in a DMZ Environment

Opera eXchange Interface, as long as it does not receive information

from the internet, can either be installed directly to the server hosting
the OPERA application.

OEDS Server still needs to be in a DMZ environment

Demilitarized Zone

OEDS Server

HP Compaq

Local Area Network (LAN) External Network (WAN)

HP
ProLiant
ML350
Dual Port 15k
Serial SCSI
146GB

UID
Dual Port 15k
Serial SCSI

Internet
146GB
Dual Port 15k
Serial SCSI
146GB

Clean
Tape

DVD-Drive
Drive Ready
Dual Port 15k
Serial SCSI
146GB

G5
Dual Port 15k
Serial SCSI
146GB

HP StorageWorks Ultrium 920

NAT-
Dual Port 15k
Serial SCSI
146GB

Able External OEDS /

Application / OXI Firewall Router OXI Resource
Server

Traffic allowed ONLY between OXI / OEDS device will need to be

OEDS server(s) and required configured with a Network External port open to allow
equipment on the Internal Address Translation able firewall / SSL traffic between OEDS
Network. Ports open on the router to allow access to each server and required outside IP
External firewall should respective network segment. Addresses. Ports open on the
generally be closed here unless Internal firewall should
specifically required. There are other ways to generally be closed here unless
configure a DMZ environment specifically required.
All other traffic is rejected. so please consult your network
specialist for a custom All other traffic is rejected.
configuration

33 | OPERA V5 HARDWARE SIZING GUIDE

OEDS Servers with a direct connection to the internet
The above diagram shows the recommended location of the OEDS server(s) for all interfaces that require the ability
to post into the OPERA network from the Internet. Oracle Hospitality recommends the server be located in a DMZ.
There are a few different ways to configure a DMZ so please talk with your qualified network technician on the
configuration that works for your environment.

Additionally, the internal firewall should be SQL*Net enabled to handle the Oracle database links and should allow
ONLY SQL*Net traffic between the OEDS server(s) and the OPERA database(s). If the firewall is not SQL*Net
aware, then the firewall will need to close all ports below 1024 and should allow all other ports for communication
between the OEDS server(s) and the OPERA database(s). All other traffic should be rejected.

Oracle Hospitality will assume that the customer has put such a network in place to protect against unwanted
access from the Internet to the internal corporate network.

Oracle Hospitality will NOT take any responsibility for security issues that may rise after installation of any OPERA
component. It is the responsibility of the customer to ensure that there is a secure network in place. The above
diagram is only for reference purposes.

OEDS Servers without a direct connection to the internet

OEDS server(s) for all interfaces that do not require the ability to post from the internet into the properties LAN do
not need to be housed in a DMZ.

In this case, Oracle Hospitality recommends OEDS be installed on a standalone machine (due to resource
requirements) except in select circumstances. The properties firewall should be configured to block ALL incoming
traffic from the public internet.

Oracle Hospitality will NOT take any responsibility for security issues that may rise after installation of any OPERA
component. It is the client’s responsibility to have a secure network in place. The above diagram is only for
reference purposes.

OPERA eXchange Interface (OXI) Components and Server(s)

OXI interfaces are designed to be flexible and as such may be configured in a number of different fashions. The
components used for message exchange and processing are:
» OPERA Application HTTP Server
» Accepts incoming traffic from the external system.
» OXI Processor (Windows NT Service)
» Processes messages as the point of communication between OPERA's HTTP server and the OPERA API.
» Posts outgoing messages to the external system.

34 | OPERA V5 HARDWARE SIZING GUIDE

It is not required that the OXI Processor and OPERA Application HTTP Server be installed on the same machine
though so such a configuration is often the case. However, incoming messages MUST be able to reach the HTTP
Server and outgoing messages MUST be able to reach the external system. The communication flow between
OPERA and the external system will be one of the following:
» Push/Push – Both systems push messages to other system when messages are available. External system
sends messages for OXI to OPERA’s HTTP server and OXI sends messages to external system’s HTTP server.
» Push/Pull – External system pushes messages to OPERA when messages are available and polls OPERA’s
HTTP server for availability of messages (OR) OPERA pushes messages to external system when messages are
available and polls external system’s HTTP server for availability of messages.
» Pull/Pull – Both systems poll the other system for messages and pull them when available (No implementations
currently exist).
In each of these cases, it is important to evaluate which system initiates connectivity under different circumstances
and where each system resides. For example, in the case of a Push/Pull interface where OPERA will initiate all
messages and connect to an external system located in an offsite datacenter, it is important to keep in mind that
communications will pass over the public internet and should be encrypted with an SSL certificate installed on the
external system side. No incoming ports are required through the firewall for this interface.

OXI may be installed in one of two possible configurations (including accompanying firewall configurations).
Depending on the requirements of the OXI interface itself, it may or may not be required that the external system
have the ability to post into the DMZ. In many cases, the external system does not in fact post INTO the property.
Communication is instead initiated from the property and all messages are pulled FROM the vendor.

35 | OPERA V5 HARDWARE SIZING GUIDE

OXI External System Posting INTO OPERA Network

OXI / OEDS in a DMZ Environment

Opera eXchange Interface needs to
be on a separate PC or server in a DMZ
environment if one of the following
interfaces are configured:

Passkey
SynXis 2 way
Vistera / Open
Hospitality
Genares
Rainmaker
Demilitarized Zone
Travelclick (pre Opera version
5.0.02.00) OEDS / OXI PC or Server

Please note: This list is not inclusive HP Compaq HP Compaq

and should apply to any interface that

receives any data directly from the
internet.
Local Area Network (LAN) External Network (WAN)
OXI Ports include:
20, 21, 80, 443, 445
HP
ProLiant
ML350
Dual Port 15k
Serial SCSI
146GB

UID
Dual Port 15k
Serial SCSI

Internet
146GB
Dual Port 15k
Serial SCSI
146GB

Clean
Tape

DVD-Drive
Drive Ready
Dual Port 15k
Serial SCSI
146GB

G5
Dual Port 15k
Serial SCSI
146GB

HP StorageWorks Ultrium 920

NAT-
Dual Port 15k
Serial SCSI
146GB

Able External OEDS /

Application / Firewall Router OXI Resource
Database Server

Traffic allowed ONLY between OXI / OEDS device will need to be External port open to allow
OEDS server(s) and required configured with a Network SSL traffic between OEDS
equipment on the Internal Address Translation able firewall / server and required outside IP
Network. Ports open on the router to allow access to each Addresses. Ports open on the
External firewall should respective network segment. Internal firewall should
generally be closed here unless generally be closed here unless
specifically required. There are other ways to specifically required.
configure a DMZ environment
All other traffic is rejected. so please consult your network All other traffic is rejected.
specialist for a custom
configuration

The above diagram shows the recommended location of the OXI server(s) for all OXI interfaces that require the
ability to post into the OPERA network from the Internet. Oracle Hospitality recommends the server be located
between an external and internal firewall (a DMZ). The external firewall (shown on the right) controls access from
the Internet through a dedicated port by using the external IP address. The internal firewall (shown on the left)
controls access from the OXI PC to the OPERA database(s) by using the internal IP address. The internal firewall
should be SQL*Net enabled to handle the Oracle database links and should allow ONLY SQL*Net traffic between
the OXI Server and the OPERA database(s). If the firewall is not SQL*Net aware, then the firewall will need to close
all ports below 1024 and should allow all other ports for communication between the OXI server and the OPERA
database(s) All other traffic should be rejected.

Servers located within the DMZ should have 2 NICs (network interface cards), one with a public (external) IP
address and one with the local LAN IP address. The server may also have just 1 NIC provided the proper network
routing to handle this is in place.

Oracle Hospitality will assume that the customer has put such a network in place to protect against unwanted
access from the Internet to the hotel’s LAN.

Oracle Hospitality will NOT take any responsibility for security issues that may rise after installation of any OPERA
component. It is the client’s responsibility to have a secure network in place. The above diagram is only for
reference purposes.

36 | OPERA V5 HARDWARE SIZING GUIDE

OXI External System NOT Posting Into OPERA Network
Like OEDS, there are two possible configurations exist for those OXI interfaces where the external system is NOT
posting into the network containing the OPERA system.

First, the communication between the external system and OPERA may exist entirely on the internal network:

The second possible configuration for those OXI interfaces where the external system is NOT posting into the
OPERA network is one where the external system exists on the external network (i.e., across the public internet). In
this case, OXI will initiate communication and pull messages from the external system. A DMZ is not required in this
case as incoming traffic is not present and ALL incoming ports should be blocked from the internet. The outgoing
port to the external system from the OPERA server must be open.

The above two diagrams show the recommended location of the OXI server(s) for all OXI interfaces that DO NOT
require the ability to post into the OPERA network from the Internet. In these cases, if traffic volume requires it, OXI
may be installed on a standalone machine or may be installed on an OPERA Application or Single Server.

In this case, Oracle Hospitality recommends OXI be installed on the OPERA Application Server whenever possible.
If the network traffic or concurrent user count requires it, a separate server may be installed. The external firewall
should be configured to block ALL incoming traffic from the public internet.

Oracle Hospitality will assume that the customer has put such a network in place to protect against unwanted
access from the Internet to the hotel’s LAN.

Oracle Hospitality will NOT take any responsibility for security issues that may rise after installation of any OPERA
component. It is the client’s responsibility to have a secure network in place. The above diagram is only for
reference purposes.

OXI Variations Summary

The variation in OXI configurations is summarized in the table below. This should not be considered a complete or
definitive listing as custom configurations are always possible. Oracle Hospitality recommends reviewing your
configuration with a qualified networking resource to ensure your configuration is as secure as possible.

OXI Communication External Server On-Site or on External Server Off-Site

Flow Internal Network (External Network)
SSL/DMZ SSL/DMZ SSL/DMZ SSL/DMZ
Push/Push for OPERA for External for OPERA for External
No No Yes Yes

SSL/DMZ SSL/DMZ SSL/DMZ SSL/DMZ

Push/Pull OPERA
for OPERA for External for OPERA for External
Initiating Calls
No No No Yes

SSL/DMZ SSL/DMZ SSL/DMZ SSL/DMZ

37 | OPERA V5 HARDWARE SIZING GUIDE

 Push/Pull External for OPERA for External for OPERA for External
System Initiating Calls No No Yes No

SSL/DMZ SSL/DMZ SSL/DMZ SSL/DMZ

Pull/Pull for OPERA for External for OPERA for External
No No Yes Yes

For those scenarios in the table above where SSL/DMZ is required for OPERA, Oracle Hospitality strongly
recommends a network implementation similar to that in the above diagram labeled OXI External System Posting
INTO Property. For those scenarios where SSL/DMZ is not required for OPERA, a DMZ may still be required for
another system such as OEDS, but not for OXI. In such a case, a network implementation similar to that in the
above diagrams labled OXI External System NOT Posting INTO Property is acceptable.

38 | OPERA V5 HARDWARE SIZING GUIDE

Property Level Interfaces
OPERA supports thousands of property level interfaces. In many cases these require a physical connection (via
COM port) to a machine running the OPERA Interface Controller software (an Interface PC) that handles translation
between the physical connection and the OPERA Application Server. To allow for multiple COM port connections to
a single machine, a multiport serial card is often used to expand the COM port capacity of the Interface PC. In other
cases, the physical connection may be via TCP/IP to the same Controller. An Interface PC is generally limited to
eight Interfaces as this is where the expanded COM port capacity is usually exhausted.

In some cases, it is possible to connect COM ports from a different machine to an interface PC running the Interface
Controller. In such a configuration, port 5001 is generally configured from TCP/IP transmission from the machine
hosting the COM port to the machine hosing the Interface Controller. For TCP/IP interfaces using the IFC PC as the
TCP/IP server, ports 5002 through 5020 are usually configured. If the equipment on the interface side will be the
TCP/IP server, then please check with your vendor.

All equipment relating to Property Level Interfaces should be a member of the Internal Network, should NOT be
located in the DMZ, and should not be accessible from the internet.

Internal
Network

OPERA Application
Server

Property Level
l
Interface PC TC
ri a P/
Se IP
or or
IP Se
P/ r ia
TC l

Credit
PBX VSS Voice Mail
Cards

Call
POS Door Lock Minibar Internet
Accounting

39 | OPERA V5 HARDWARE SIZING GUIDE

OPERA Client/Server Communications
Traffic between an OPERA client machine and the OPERA Application server is broken into two types.

» Type-1 traffic is a forms applet that communicates with the forms setvlet using a pure Oracle proprietary message
format and hard-coded DES3 encryption. This includes everything that is communicated via the OPERA UI (i.e.,
most of the traffic to/from the server).
» Type-2 traffic is everything else and is exactly what would generally be expected from an HTTP call to any
website. Implementing an SSL certificate ensures this stream of information is encrypted prior to transmission.

Once an SSL certificate has been installed on an App Server, Type-2 traffic will be directed over the SSL port
(typically 443). Type-1 traffic will continue to be directed over the non-SSL port. Type-1 traffic continues to be
directed over the non-SSL enabled port for two reasons:

Type-1 messages are already encrypted. Adding an HTTPS layer would be unnecessary overhead

Type-1 messages are small but very frequent. This means there are numerous roundtrips. Adding HTTPS doubles
the number of roundtrips on the network and significantly increases application response times. In scenarios with
higher latency or high traffic volume, this results in significant performance degradation.

Due to this architecture, OPERA still requires two ports to operate (defaults are 80 and 443). If a firewall will be in
place to filter activity, its configuration must allow for communication of both ports between client and application
server.

Secure Socket Layer (SSL) and OPERA

Beginning with version 4.0.xx.xx, the OPERA application server supports the implementation of an SSL certificate.

For OPERA versions 4.0 – 5.0.04.02 - Oracle Hospitality strongly recommends OPERA be implemented with an
SSL certificate in place. A proper SSL Implementation will force all un-encrypted user traffic to proceed over the
SSL encrypted port so that a user is not able to bypass the secure certificate for sign-on. User's that direct their
browser to a un-encrypted (HTTP) URL will be redirected to an encrypted (HTTPS) URL. This will protect all traffic
that is not already encrypted by the Oracle forms applet. As mentioned in the previous section, Client/Server
communications will use two ports for transmission, one that will be encrypted using the SSL certificate and one that
will not (because this traffic is already encrypted).

Delivering non-encrypted traffic over the same port that delivers SSL encrypted traffic in a non-encrypted fashion is
not an option – this is not possible in Apache (the Web Server component of Oracle Application Server). So delivery
of traffic that is both encrypted and unencrypted from the Web server point of view requires two ports minimum.

It is technically possible to redirect the non-encrypted traffic through the SSL tunnel in the Apache or Oracle
configuration. However, this would double-encrypt those components that are already encrypted, increase server
roundtrips, and increase application response times. Micros neither recommends nor supports this configuration.

40 | OPERA V5 HARDWARE SIZING GUIDE

For OPERA versions 5.0.04.03 and 5.0.05+ - SSL is now a requirement and self-signed certificates are no longer
supported. The below items list the requirements for SSL:

not supported.

-signed certificates are not supported. If the client has

their own internal certificate authority this is supported however they must be able to provide ALL corresponding CA
Certs that were used to sign the certificate. A chain certificate will not work in this case for the CA Certs, and
individual certificate is needed for each certificate in the chain.

responsible for converting the certificate to X.509 format if the Certificate Authority cannot issue in the X.509 Format.

- Note: This is due to Certificate Authorities no longer signing certificates with these domain names. If the
customer has their own internal Certificate Authority and they are able to sign certificates with .LOCAL or
.INTERNAL domain names then an exception can be granted. However once the certificate request is
generated there is no way to change it and the Opera Installation must be removed and re-instaled. This
will be billable time if the customer wants to proceed with a .LOCAL or .INTERNAL domain and finds they
are unable to sign the certificate.

quest. Properties should not attempt

to “make up” a domain as this will cause delays in obtaining a certificate.

Fully Qualified Domain name.

41 | OPERA V5 HARDWARE SIZING GUIDE

Wireless Access Points and OPERA
Oracle Hospitality recommends that OPERA not be run wirelessly unless specific operational processes and
application components require it. Examples where this may be desirable include a self-service kiosk or a handheld
check-in device. In such a circumstance, Oracle Hospitality strongly recommends that the accompanying OEDS
server be located in its own DMZ separate from any other external access servers (OEDS or OXI) that may also
exist in a DMZ facing the internet.

Wireless devices should be configured to require strong encryption mechanisms such as AES and all firmware
should be updated to support strong encryption for both authentication and transmission. WEP should not be used.
The wireless network itself should be an internal network insofar as that is possible. Guest wireless access should
not occur on this network.

Internal
Internal DMZ Wireless
Network Network

Wireless
OEDS Server(s) Access
OPERA
Server(s) 2 NICs for:
Point
Internal IP Address
External IP Address
Firewall Firewall

Traffic allowed ONLY Wireless-facing port

between OEDS open to allow
server(s) and required encrypted traffic
equipment on the between OEDS
Internal Network. server and wireless
Ports open on the access point. Ports
wireless-facing firewall open on the Internal
should generally be firewall should
closed here unless generally be closed
specifically required. here unless
specifically required.
All other traffic is
rejected. All other traffic is
rejected.

42 | OPERA V5 HARDWARE SIZING GUIDE

User Accounts
User accounts for the OPERA Application are handled in a secure manner and will be reviewed during the OPERA
configuration that occurs as part of the implementation and training process. User accounts in the Windows and
network environment must be managed by an external process. Oracle Hospitality recommends against the use of
generic user accounts for any level of system access and instead recommends that unique Operating System or
network credentials be established for each individual and that these credentials include the use of strong
passwords. Strong passwords should include the following rules:

» Passwords must expire at most every 90 days

» Passwords must be at least 7 characters in length
» Passwords must include at least one each of alphabetic and numeric characters

At all times when user credentials will be transmitted against any internal or external network, they must be
encrypted. To facilitate this, Oracle Hospitality strongly recommends implementing OPERA with an SSL certificate
in place on the Application Server.

Windows User Accounts

The Windows operating system provides the capability to create and manage unique credentials for each user that
requires access. Managing credentials at the operating system level can be somewhat cumbersome as credentials
from one machine do not transfer to another machine. If a user will access two computers, then that user would
require an account on each machine.

Active Directory
An Active Directory installation can facilitate management of user access credentials. Active Directory allows the
creation of a domain environment to which each computer on the network can be assigned. Domain level user
accounts then have the ability to log into any machine connected to the domain provided the machine allows these
logins.

Active Directory Integration to OPERA

OPERA provides the ability to integrate with an Active Directory installation via the Lightweight Directory Access
Protocol (LDAP) to allow users to use the same login credentials at the operating system and network level and at
the OPERA Application level. This simplifies the management of user credentials by allowing credentials for the
operating system, network resources, and the OPERA Application to be managed in a single location.

43 | OPERA V5 HARDWARE SIZING GUIDE

Credit Card Data Flow
The flow of credit card data through the OPERA system is relatively straightforward. From the point of entry (i.e.,
client workstation), information is transmitted to the database server which then makes the posting to the credit card
gateway.

At the workstation, UI is received via

an Oracle Forms stream. Credit card
is swiped or manually entered.

PMS Client OPERA PMS

Workstation

The OPERA Application Server serves user PAN

interface to the web browser on the PMS Expiration
Track Data (if swiped)
workstation via two layers. UI activity is via an
Transmission is an Oracle
encrypted Oracle Forms stream. External activity Forms stream.
(e.g., reports) is via HTTP or HTTPS call (HTTPS
is recommended).
OPERA
PMS Server Application Server

PAN
Expiration
Track Data (if swiped)
Transmission is an The OPERA database and the OPERA Credit
SQL*Net connection Card driver reside within the database
architecture. Internally, an XML message is
The OPERA database server runs created and transmitted directly from the
on a Windows OS with an Oracle OPERA Database database to the URL specified in configuration.
Server
Database.
For long-term storage, PAN and expiration date
may be stored in an encrypted table. Track data
OPERA Databae is NEVER stored.
and Credit Card
Driver
PAN
Expiration
Track Data (if swiped)
Transmission is via
HTTPS (SSL v3) to an Offsite gateway or could be either
HTTP or HTTPS to an Onsite gateway.

Onsite or
Credit Card
Offsite Gateway

Known Issues and Security Enhancements

A current listing of all identified security-related issues with the OPERA product suite can be obtained from the
Micros Information Security Website at: http://www.micros.com/ServicesAndSupport/InformationSecurity

44 | OPERA V5 HARDWARE SIZING GUIDE

Virtualization
Support for Virtual Environments

Oracle has not certified any of its products on any VMware or other virtualization environment. Oracle Support will
assist customers running Oracle products in virtual environments in the following manner: Oracle will only provide
support for issues that either are known to occur on the native OS, or can be demonstrated not to be as a result of
running in a VM (virtual machine).

If a problem is a known Oracle issue, Oracle support will recommend the appropriate solution on the native OS. If
that solution does not work in the VM environment, the customer will be referred to the VM vendor for support. When
the customer can demonstrate that the Oracle solution does not work when running on the native OS, Oracle will
resume support, including logging a bug with Oracle Development for investigation if required.

If the problem is determined not to be a known Oracle issue, we will refer the customer to the VM vendor for
support. When the customer can demonstrate that the issue occurs when running on the native OS, Oracle will
resume support, including logging a bug with Oracle Development for investigation if required.

NOTE: Oracle has not certified any of its products on VMware or any virtual environment.

NOTE: Oracle RAC (Real Application Cluster) can NOT be installed in any virtualized environment.

45 | OPERA V5 HARDWARE SIZING GUIDE

OPERA Hardware Sizing Template

An editable version is available by request.

46 | OPERA V5 HARDWARE SIZING GUIDE

 Oracle Corporation, World Headquarters Worldwide Inquiries
500 Oracle Parkway Phone: +1.650.506.7000
Redwood Shores, CA 94065, USA Fax: +1.650.506.7200

CONNECT W ITH US

blogs.oracle.com/oracle Copyright © 2015, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only, and the
contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other
warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or
facebook.com/oracle fitness for a particular purpose. We specifically disclaim any liability with respect to this document, and no contractual obligations are
formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means,
twitter.com/oracle electronic or mechanical, for any purpose, without our prior written permission.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
oracle.com
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and
are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are
trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.0115

OPERA v5 Hardware Sizing Guide

Version 1.4
May 2016
Author: Larry Baird
Contributing Authors: Bryan Clarke