installation guide oracle hospitality simphony · step 2 - access the iis manager console 7-13 step...

Oracle® Hospitality SimphonyInstallation Guide

Release 18.1E83238-05February 2019

Oracle Hospitality Simphony Installation Guide, Release 18.1

E83238-05

Copyright © Oracle and/or its affiliates. All rights reserved.

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.Reverse engineering, disassembly, or decompilation of this software, unless required by law forinteroperability, is prohibited.

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 installed on the hardware, and/or documentation, delivered to U.S. Government end users are"commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of theprograms, including any operating system, integrated software, any programs installed on the hardware,and/or documentation, shall be subject to license terms and license restrictions applicable to the programs.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 Xeon 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, Opteron,the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced MicroDevices. UNIX is a registered trademark 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 not beresponsible 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.

Contents

Preface

1 Getting Started

Installation Process 1-1

2 Deployment Scenarios Using R&A version 9.0 and Later

3 Deployment Scenarios Using R&A version 8.5.1

4 Pre-Installation Tasks

Browser Security 4-4

Property Network Considerations 4-4

Installing Microsoft Windows Communication Foundation Features 4-5

Pre-install Reporting and Analytics Installation Requirements 4-10

Installing Microsoft Internet Information Services (IIS) 4-10

Installing Oracle Database 11g or 12c 4-15

Database User Passwords 4-17

Increasing Database Process Count 4-17

5 Simphony Installation Tasks

Before Installing Simphony 5-2

Assigning Multi-Factor Authentication EMC Access Privileges 5-3

Multi-Factor Authentication for EMC Access 5-5

MFA Configuration During the Installation of Simphony 5-6

Accessing the Simphony EMC Using Multi-Factor Authentication 5-7

Configuring the SMTP and Backup SMTP Servers in the EMC 5-8

Configuring and Resetting Email Addresses 5-9

Setting the Max Allowed Failed Logins for EMC Access 5-10

iii

Forgotten EMC Password Recovery 5-11

Configuring Access Privileges for Resetting a Password 5-13

Resetting Passwords from the Simphony Web Portal 5-14

Simphony Installation for an All-in-One Server 5-17

6 Installing Simphony on Multiple Servers

Installing Simphony Database Components on Microsoft SQL Server 6-2

Installing Simphony Application Components on One or More Servers 6-3

7 Upgrading from a Previous Release

Upgrading to the Simphony 18.1 Release 7-2

Upgrades with Separate Transaction and Security Database Servers (when addinga new database server) 7-3

Upgrades without Separate Transaction and Security Database Servers 7-7

Upgrades with Existing Separated Transaction and Security Database Servers 7-8

Upgrading Prior to the Simphony 18.1 Release 7-10

Post-Upgrade Tasks 7-11

Post-Upgrade Steps for CAPS on IIS for Simphony 2.9 Users 7-12

Step 1 - Close and Post All Transactions 7-13

Step 2 - Access the IIS Manager Console 7-13

Step 3 - Rename the IIS Folder 7-15

Step 4 - Enable an Option and Configure CAPS 7-17

Step 5 - Stop IIS 7-18

Step 6 - Move the DbSettings.xml to the Newly Defined IIS CAPS Path 7-18

Step 7- Start IIS 7-19

Step 8 - Verify Log Creation, Database Tables, and Delete the Old Directory 7-19

8 Post-Installation Tasks

Updating Simphony License Counts 8-2

Updating Property Administrator and Database Logon Credentials 8-3

Configuring Different Credentials for Each Property 8-4

Configuring the Same Credentials for All Properties in the Enterprise 8-5

Updating the Property EMC Client 8-5

Verifying the Installation 8-6

Configuring Recycle Settings for the IIS Application Pool 8-7

After the Simphony Installation 8-9

If You Installed the Blank Database 8-10

If You Installed the Sample Database 8-11

Post Install Steps for Engagement on Load Balanced Simphony Servers 8-12

iv

Setting the Start-Of-Day Sequencer Machine and the App Server Time Zone 8-17

Connecting Reporting and Analytics to Simphony 8-18

Enabling Communication Between the Enterprise and Workstations 8-20

Binding SSL Certificates to Internet Information Services 8-21

9 Uninstalling Simphony

Uninstalling Simphony 9-1

10

Troubleshooting

Insufficient System Privileges 10-1

Cannot Connect to the Database Server During the Simphony Installation 10-1

EMC Fails to Launch 10-2

11

List of Simphony Components and Services

12

List of Simphony Database Configuration Fields

13

Appendix A: Sample Script for Creating Oracle Tablespaces

14

Appendix B: Post-Installation Best Practices

Creating Database Backups 14-1

Changing the Application Server’s Name 14-1

Changing the Database Server Name 14-3

v

Preface

Audience

This installation guide is intended for installers, programmers, technical support teams,product specialists, and others who are responsible for setting up Oracle HospitalitySimphony version 18.1.

Customer Support

To contact Oracle Customer Support, access My Oracle Support at the following URL:

https://support.oracle.com

When 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 all associated log files

• Screen shots of each step you take

Documentation

Oracle Hospitality product documentation is available on the Oracle Help Center at http://docs.oracle.com/en/industries/hospitality/.

Revision History

Date Description of Change

July 2018 Initial publication

Updates to Chapter 7 for post-upgrade stepsfor CAPS on IIS

August 2018 Updates to Chapter 4’s Installing MicrosoftInternet Information Services (IIS) section

December 2018 Updates to the Pre-Installation Tasks sectionin reference to Oracle Payment Interface (OPI)driver requirements.

February 2019 Updated the applicable Simphony versions forupgrading in the Upgrading to the Simphony18.2 Release topic.

Preface

vi

https://support.oracle.com

http://docs.oracle.com/en/industries/hospitality/

1Getting Started

This guide provides instructions on how to install, upgrade, and configure Simphonyversion 18.1.

You must install Reporting and Analytics (R&A) separately from Simphony using theBack Office R&A installation application. For upgrades from versions prior toSimphony 2.9, users must upgrade to Reporting and Analytics version 8.5. 1 Patch 3prior to installing or upgrading to Simphony version 2.9. Simphony version 18.1 iscompatible with both R&A versions 8.5.1 Patch 3 and 9.0 Patch 8.

For Simphony Cloud Services users, refer to the Simphony Cloud Services Post-Installation or Upgrade Guide for more information about the required steps to takeafter performing an installation or upgrade.

• Installation Process


• Deployment Scenarios Using R&A version 9.0 and Later

• Deployment Scenarios Using R&A version 8.5.1

Installation Process1. Select the appropriate deployment scenario.

Prior to installation and configuration, you need to determine which deploymentscenario meets your requirements. Depending on the version of Reporting andAnalytics (R&A) you use, support for these deployment scenarios differ from eachother:



2. Install the database server application.

You need to install one of the following database platforms prior to installingSimphony application components:

• Oracle Database 11g

• Oracle Database 12c

• Microsoft SQL Server 2008 R2

• Microsoft SQL Server 2012 R2

3. Upgrade or install Simphony.

You can run the Simphony version 18.1 installation application to upgradeSimphony, to perform a clean installation, or to install and add application servers. Upgrading from a Previous Release and List of Simphony Components andServices contains more installation information.

4. Configure post-installation settings.

1-1

The post-installation configuration ensures that the application components andthe database are configured correctly.

5. Verify the installation.

Perform the verification step to ensure that the Simphony application and thedatabase applications are set correctly.

6. Troubleshooting.

Follow the instructions in this section to resolve common problems you mightencounter when installing Simphony version 3.0.

• Getting Started



Chapter 1Installation Process

1-2

2Deployment Scenarios Using R&A version9.0 and Later

Installing Application Components and Databases on Two Servers

You can install the Simphony and R&A databases along with the Simphonycomponents on one server and the R&A components on another server.

Figure 2-1 Example of Application and DB Components on Different Servers

Installing Both Application Components and Databases on Separate Servers

You can install the Simphony and R&A components and each application’s databaseon separate servers.

Figure 2-2 Example of Application and DB Components on Separate Servers

2-1

• Getting Started



Chapter 2

2-2

3Deployment Scenarios Using R&A version8.5.1

Installing All-In-One

With an all-in-one installation, you install the Simphony and Reporting and Analyticsdatabases and the Simphony and Reporting and Analytics components on one server.If using an all-in-one installation scenario, Oracle Hospitality recommends that youinstall the Simphony application on a separate partition from where the MicrosoftWindows operating system resides.

Figure 3-1 Example of an All-In-One Installation

Installing Application Components and Databases on Separate Servers

You can install the Simphony and Reporting and Analytics components on onephysical or virtual server and install the databases on a separate server.

Figure 3-2 Example of Application Components and Databases on SeparateServers

3-1

Installing Application Components and Databases on Different Servers

You can install the Simphony and Reporting and Analytics components on twoseparate servers and install the databases on a third server.

Figure 3-3 Example of Application and Database Components on DifferentServers

Installing Both Application Components and Databases on Separate Servers

You can install the Simphony and Reporting and Analytics components and eachdatabase on separate servers.

Figure 3-4 Example of Application and Database Components on SeparateServers

• Getting Started



Chapter 3

3-2

4Pre-Installation Tasks

There are several pre-installation tasks that must be performed on the Simphonyapplication server. After completing the steps in this chapter, refer to the followingtable for database platform installation instructions.

Table 4-1 Pre-Installation Tasks for Simphony Version 18.1

Pre-Installation Task Instructions

Configure Log File rollover options (IIS) For instructions on configuring Log file rolloveroptions, refer to the Microsoft TechNet Libraryat https://technet.microsoft.com/en-us/

Install .NET 4.6.1 Framework Run the .NET 4.6.1 Framework setup in theInstallation Media\Prerequisites\DotNetFramework461 folder, followingthe on-screen instructions.

Turn on Data Execution Prevention (DEP) For instructions on turning on Data ExecutionPrevention on the server, refer to the MicrosoftTechNet Library at https://technet.microsoft.com/en-us/.

Disable Anti Denial-Of-Service (Dos) Attacks If you are installing Simphony with MicrosoftSQL Server as the database platform, you needto add the SynAttackProtect registry key to thecomputer that is running Microsoft SQL Server.

For instructions on disabling DOS attacks, referto the Microsoft TechNet Library at https://technet.microsoft.com/en-us/.

Install a TLS 1.2 compliant Certificate Install a TLS 1.2 compliant Certificate on theSimphony application server issued byCertification Authority

The Simphony Security Guide contains moreinformation in Chapter 1, specifically theWorkstation Authorization section, aboutsecurity certificates.

Remove anti-virus software from all servers Simphony can silently fail to install due to anti-virus software. Remove anti-virus software fromall servers before installing Simphony. You canreinstall the anti-virus software after Simphonyapplications and databases are installed.

4-1

https://technet.microsoft.com/en-us/





Table 4-1 (Cont.) Pre-Installation Tasks for Simphony Version 18.1


Install a database platform on the databaseserver

Simphony version 18.1 supports the followingdatabase platforms:• Oracle Database 11g Enterprise Edition• Oracle Database 12c Enterprise Edition• Microsoft SQL Server 2008 R2 Enterprise

Edition• Microsoft SQL Server 2012 R2 Enterprise

EditionFor instructions on installing and setting up theOracle Database, see Installing OracleDatabase 11g or 12c.

For instructions on installing Microsoft SQLServer, refer to the Microsoft TechNet Library at https://technet.microsoft.com/en-us/.

You can also install Simphony on a MicrosoftSQL Server 2008 or 2012 R2 Failover Cluster.For instructions on installing a Microsoft SQLServer 2008 or 2012 R2 Failover Cluster, referto the Microsoft TechNet Library at https://technet.microsoft.com/en-us/.

*For Oracle Database users only; GrantPUBLIC access for the DBMS_LOB andDBMS_SCHEDULER on the database server

The Simphony installer requires access toexecute certain Oracle database packages forwhich public privileges are not granted. Thismakes it necessary to request that temporarypublic access be granted for the installation torun successfully, after which the public grantcan be revoked and a specific schema grant becreated instead.

Prior to performing a new install, using OracleSQL Developer, execute the following requests:

• GRANT EXECUTE ON DBMS_LOB TOPUBLIC

• GRANT EXECUTE ONDBMS_SCHEDULER TO PUBLIC

Prior to performing an upgrade, using OracleSQL Developer, execute the following request:• GRANT EXECUTE ON

DBMS_SCHEDULER TO PUBLIC

Refer to the Oracle Database Security Guide https://docs.oracle.com/en/database/oracle/oracle-database/12.2/dbseg/index.html for moreinformation.

Chapter 4

4-2


https://technet.microsoft.com/en-us

https://technet.microsoft.com/en-us

https://docs.oracle.com/en/database/oracle/oracle-database/12.2/dbseg/index.html


Table 4-1 (Cont.) Pre-Installation Tasks for Simphony Version 18.1


*For Microsoft SQL Server users only;Manually create the folders to store theMicrosoft SQL Server database files

For Simphony sites utilizing Microsoft SQLServer, upon performing upgrades fromSimphony version 2.9.2 or later, and want tophysically separate their Transaction(MCRSPOS) and Security (MCRSCACHE)databases, you need to manually create adatabase destination folder on the newdatabase server prior to the upgrade. Whateverdatabase installation path is entered into theRemote Database Location field, needs toalready exist on the destination databaseserver. For example, create a C:\MICROS\Data or D:\MICROS\Data folder on thenew database server, and then enter the newlycreated folder's path in the Remote DatabaseLocation field. This path is used to create thenew Security and Transaction databases.https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/view-or-change-the-default-locations-for-data-and-log-files?view=sql-server-2017 contains more information aboutsetting default database locations for MicrosoftSQL Server users.

*For Oracle Payment Interface (OPI) driverusers only

If you are using the Oracle Payment Interface(OPI) driver, OPI version 6.1 is supported,although there are known issues relating to tipsand tip adjustment functionality. Oraclerecommends that before performing aSimphony installation or upgrade, you need toinstall or upgrade to OPI version 6.2 includingthe latest patch.

See My Oracle Support (MOS) at https://support.oracle.com/ to access the latest OPIPayment drivers.

• Browser Security

• Property Network Considerations

• Installing Microsoft Windows Communication Foundation Features

• Pre-install Reporting and Analytics Installation Requirements

• Installing Microsoft Internet Information Services (IIS)

• Installing Oracle Database 11g or 12c

• Database User Passwords

• Increasing Database Process Count





Chapter 4

4-3

https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/view-or-change-the-default-locations-for-data-and-log-files?view=sql-server-2017





https://support.oracle.com/

https://support.oracle.com/


Related Topics



• Appendix A: Sample Script for Creating Oracle Tablespaces

Browser SecuritySimphony requires the use of a web browser for some parts of the application such asthe Simphony Web Portal. You should configure the security settings for your webbrowser to disable features that are not required or that could cause securityvulnerabilities. Below is a list of some of the more commonly used browsers along witha link to the documentation that describes the security settings of each browser.

Internet Explorer

http://windows.microsoft.com/en-us/internet-explorer/ie-security-privacy-settings

Mozilla Firefox

https://support.mozilla.org/en-US/products/firefox/privacy-and-security

Google Chrome

https://support.google.com/chrome/?hl=en#topic=7437824

• Pre-Installation Tasks





Related Topics




Property Network ConsiderationsPrior to installing Reporting and Analytics or Simphony, property networks usingOracle RAC or Load Balancing environments must be operational.

If you are using a Load Balancing server and plan to use the Simphony EngagementCloud Service, select LoadBalancer for the required CA Certificate Location field.

If you define a Service Host Secure Port number other than the default of 443, youneed to enable that port on the Load Balancing server.



Chapter 4Browser Security

4-4

http://windows.microsoft.com/en-us/internet-explorer/ie-security-privacy-settings

https://support.mozilla.org/en-US/products/firefox/privacy-and-security%20

https://support.google.com/chrome/?hl=en#topic=7437824




Related Topics




Installing Microsoft Windows Communication FoundationFeatures

Microsoft Windows Communication Foundation (WCF) configuration only needs to beperformed on servers where the Simphony Web Portal (Import/Export) and API areinstalled.

For more information about the Server Manager - Add Roles and Features Wizard,refer to the Microsoft TechNet Library at https://technet.microsoft.com/en-us/.

From the Simphony application server (running Microsoft Windows Server 2012 R2)perform these steps:

1. Access the Control Panel, click Programs, and then beneath Programs andFeatures, click Turn Windows features on and off.

2. The Server Manager Dashboard loads and subsequently, the Add Roles andFeatures Wizard.

3. Access the Server Manager and select 2 Add roles and features.

Figure 4-1 Server Manager – Dashboard — Adding Roles and Features

Chapter 4Installing Microsoft Windows Communication Foundation Features

4-5


4. Click Next.

Figure 4-2 Server Manager — Before You Begin Screen

5. Select Role-based or feature-based installation, and then click Next.

Figure 4-3 Server Manager — Select Installation Type Screen


4-6

6. Select the Select a server from the server pool option.

7. Select the server you are configuring, and then click Next.

Figure 4-4 Server Manager – Select Destination Server Screen

8. Click Next.

Figure 4-5 Server Manager – Select Server Roles Screen


4-7

9. Expand .NET Framework 3.5 Features and ensure that HTTP Activation andNon-HTTP Activation are selected.

Figure 4-6 Server Manager — Select Features Screen

10. Expand .NET Framework 4.5 Features, enable WCF Services, and then ensurethat HTTP Activation and TCP Activation are selected.

Figure 4-7 Server Manager — Select Features Screen


4-8

11. Confirm the selections, click Install, and once completed, click Close.

Figure 4-8 Server Manager — Confirm Installation Selections Screen

12. When finished, navigate to Administrative Tools, then select IIS Manager.

a. If you are performing an upgrade to Simphony release 18.1 from an earlierversion, the ImportExportAppPool is renamed to SimphonyAppPool.

b. For fresh Simphony 18.1 installations, several Application Pools including theSimphonyAppPool are created for you.

Locate the following Application Pools, click on each one individually, right-click, and then select Recycle.

• ImportExportAPIPool

• Simphony2Pool

• SimphonyAppPool

13. Perform an Internet Information Services (IIS) reset.


Related Topics








4-9


Pre-install Reporting and Analytics InstallationRequirements

Beginning with the Simphony version 2.9 release or later, users must install Reportingand Analytics (R&A) separately from Simphony using the Back Office R&A installationapplication. For upgrades from versions prior to Simphony 2.9, users must upgrade toReporting and Analytics version 8.5.1 Patch 3 prior to installing or upgrading toSimphony version 2.9. Simphony versions 2.10 and 18.1 are compatible with bothR&A versions 8.5.1 Patch 3 and 9.0 Patch 8.

Install Reporting and Analytics version 8.5.1 and Enterprise Back Office with OracleHospitality Simphony contain more information about installing reports for Simphony.






Related Topics




Installing Microsoft Internet Information Services (IIS)For more information about the Server Manager - Add Roles and Features Wizard,refer to the Microsoft TechNet Library at https://technet.microsoft.com/en-us/.

From the Simphony application server (running Microsoft Windows Server 2012 R2)perform the following steps:

1. Using the Server Manager, select 2 Add roles and features.

Chapter 4Pre-install Reporting and Analytics Installation Requirements

4-10

https://docs.oracle.com/cd/E66143_01/doc.850/e66674.pdf

https://docs.oracle.com/cd/E71871_01/doc.90/e74935/c_roadmap_simphony.htm#SimphonyScenario-D6F04A6F

https://docs.oracle.com/cd/E71871_01/doc.90/e74935/c_roadmap_simphony.htm#SimphonyScenario-D6F04A6F


Figure 4-9 Server Manager – Adding Roles and Features

2. Select Role-based or feature-based installation, and then click Next.

3. Choose Select a server from the server pool.

4. Select the server you are configuring, and then click Next.

Figure 4-10 Server Manager – Select Server

5. Expand the Web Server role service.

Chapter 4Installing Microsoft Internet Information Services (IIS)

4-11

Figure 4-11 Server Manager – Web Server Role Services

6. Expand the Web Server options and select the following Common HTTPFeatures:

• Default Document

• HTTP Errors

• Static Content

From a system security standpoint, the Directory Browsing role service should notbe enabled.

7. Select the following Health and Diagnostics options:

• HTTP Logging

• Request Monitor

8. Select the Performance option Static Content Compression.

9. Select the Security option Request Filtering.


4-12

Figure 4-12 Server Manager – Performance and Security Role Services

10. Select and expand Application Development, and then select the followingoptions:

• .NET Extensibility 4.5

• ASP

• ASP .NET 4.5

• ISAPI Extensions

• ISAPI Filters


4-13

Figure 4-13 Server Manager – Application Development Role Services

11. Select and expand Management Tools, and then select the following options:

• IIS Management Console

• IIS Management Scripts and Tools

12. Select IIS 6 Management Compatibility, and then select the following options:

• IIS 6 Metabase Compatibility

• IIS 6 Management Console

• IIS 6 Scripting Tools

• IIS 6 WMI Compatibility


4-14

Figure 4-14 Server Manager – Management Tools

13. Click Next as needed, and then click Install.


Related Topics








Installing Oracle Database 11g or 12cTo download and install the Oracle Database, refer to the Oracle Technology Network(OTN) website at http://www.oracle.com/technetwork/database/enterprise-edition/downloads/index.html.

For Oracle Database 12c users, Oracle Hospitality does not currently supportPluggable database options.

For Oracle Database users, ensure that the Use Unicode character set option isenabled during your database installation.

Chapter 4Installing Oracle Database 11g or 12c

4-15

http://www.oracle.com/technetwork/database/enterprise-edition/downloads/index.html

http://www.oracle.com/technetwork/database/enterprise-edition/downloads/index.html

Figure 4-15 Database Configuration Options - Character Sets - Use UnicodeOption

Creating Oracle Database Tablespaces

If you are using an Oracle database, ensure that you have the Simphony databaseTablespaces created on your sever.

Create the following Oracle database Tablespaces on the database server or servers:

• MCRSPOS

• MCRSCACHE

See Appendix A – Sample Script for Creating Oracle Tablespaces for a sample scriptto create the database Tablespaces. The Platform Guide for Microsoft Windows andthe Administrator's Reference for Linux and UNIX-Based Operating Systems containsmore information about creating database Tablespaces.

Increasing Database Process Count

Run the ALTER SYSTEM SET processes=300 SCOPE=SPFILE; command on theOracle Database and restart the Oracle Database Service. If you are using the OracleLinux operating system, run the shutdown immediate; command and then run theSTARTUP pfile=init.ora; command to restart the service. The Administrator'sReference for Linux and UNIX-Based Operating Systems contains more informationabout restarting the Oracle Database Service.

If you are using a Microsoft Windows Server, restart the OracleServiceSIMPHONYservice using the Windows Services dialog. The Platform Guide for Microsoft Windowscontains more information about restarting the Oracle Database Service on MicrosoftWindows Servers.



Chapter 4Installing Oracle Database 11g or 12c

4-16




Related Topics




Database User PasswordsWhen performing a database installation, specifically Oracle Database users,passwords must adhere to the following rules:

• Cannot start with a number (for example, 1QasHello)

• Cannot start with a special character (for example, #abc)

• Must have at least 8 characters

• Must have at least one upper case letter

• Must have at least one number

• Cannot use a dictionary word, although two dictionary words together may pass

• Must have at least one supported special character

• Can only use database supported special characters, which include theunderscore (_), dollar sign ($), and pound symbol (#) characters. The followingcharacters are not recognized and should not be used for Oracle Database userpasswords: ! @ % ^ & *

For example, Hello3&there is not valid because Hello and there are separateddictionary words by symbols/numbers, but Hellothere$1 is valid.






Related Topics




Increasing Database Process CountRun the ALTER SYSTEM SET processes=300 SCOPE=SPFILE; command on the OracleDatabase and restart the Oracle Database Service. If you are using the Oracle Linuxoperating system, run the shutdown immediate; command and then run the STARTUPpfile=init.ora; command to restart the service.

Chapter 4Database User Passwords

4-17

The Administrator's Reference for Linux and UNIX-Based Operating Systems containsmore information about restarting the Oracle Database Service. If you are using aMicrosoft Windows Server, restart the OracleServiceSIMPHONY service using theWindows Services dialog.

The Platform Guide for Microsoft Windows contains more information about restartingthe Oracle Database Service on Microsoft Windows Servers.

Chapter 4Increasing Database Process Count

4-18

5Simphony Installation Tasks

This chapter provides a list of tasks that you must perform for each of the installationscenarios.

• Before Installing Simphony

• Assigning Multi-Factor Authentication EMC Access PrivilegesTo access and configure Multi-Factor Authentication (MFA) security for other userson your system, you need to be assigned the correct privileges in the EMC.

• Multi-Factor Authentication for EMC Access

• MFA Configuration During the Installation of SimphonyWhen running the Simphony installation application, you are prompted to configureMFA. Your choices are:

• Accessing the Simphony EMC Using Multi-Factor AuthenticationTo utilize Multi-Factor Authentication (MFA) on your Simphony system, you needto add and register your email address. Follow the steps outlined below:

• Configuring the SMTP and Backup SMTP Servers in the EMCSMTP and Backup SMTP server settings are configured and saved at theEnterprise level. To configure the SMTP servers:

• Configuring and Resetting Email AddressesAfter enabling Multi-Factor Authentication (MFA), each user that accesses theEMC or Simphony Web Portal (SWP) must register their email address. Thesystem prompts each EMC user to do so. This enables users to receive the one-time password (OTP) via email to complete the EMC login process. To enroll auser’s email address using the EMC:

• Setting the Max Allowed Failed Logins for EMC AccessMFA adheres to the following EMC account lock out setting:

• Forgotten EMC Password Recovery

• Configuring Access Privileges for Resetting a Password

• Resetting Passwords from the Simphony Web Portal

• Simphony Installation for an All-in-One ServerThe All-in-One server installation scenario is only supported for those usingReporting and Analytics version 8.5.1 Patch 3.




Related Topics


5-1









• List of Simphony Components and Services

• List of Simphony Database Configuration Fields

Before Installing SimphonyIf you are installing Simphony with an Oracle Database, ensure that the Simphony andSimphonyXDB instances are running. To show the status of the Simphony andSimphonyXDB instances, run the lsnrctl STATUS command from a commandprompt on the database server.

During a fresh Simphony installation, the Sample Database should not be utilized in aproduction environment. Rather, you should install the Blank Database.

See Verifying the Installation for initial application logon information after the Simphonyinstallation is complete.

• Simphony Installation Tasks



Related Topics



Chapter 5Before Installing Simphony

5-2










Assigning Multi-Factor Authentication EMC AccessPrivileges

To access and configure Multi-Factor Authentication (MFA) security for other users onyour system, you need to be assigned the correct privileges in the EMC.

1. Select the Enterprise level, click Configuration, and then click Roles.

2. Click the EMC Modules EMC Modules tab and scroll to the Personnel section.

3. Select the checkboxes for the Employees (Enterprise) access privileges for eachof the following columns:

• View

• Edit

• Add

• Delete

4. Click Save.

Chapter 5Assigning Multi-Factor Authentication EMC Access Privileges

5-3

Figure 5-1 MFA Access Privilege Roles Configuration

5. Click the Actions tab, scroll through the Action column until you reach the Securitysection, select the Can Change Others’ Passwords and Email Addresses andSecurity Questions checkbox, and then click Save.

6. Ensure that all users requiring MFA configuration permissions are assigned a Rolethat have these access privileges enabled.

Figure 5-2 MFA Access Privilege Roles Configuration

Related Topics






Chapter 5Assigning Multi-Factor Authentication EMC Access Privileges

5-4


Multi-Factor Authentication for EMC AccessSimphony Multi-factor Authentication (MFA) is enabled by default in order to complywith Payment Card Industry (PCI) standards.

You can configure MFA in Simphony to provide users a one-time password (OTP)through email in two ways. They are:

1. During the installation of the Simphony software.

2. After the installation of the Simphony software, using the Simphony EMC.

MFA Configuration Prerequisites

To utilize this functionality, the following requirements must be met:

• For MFA implementation, you must install and make network accessible, twoseparate Simple Mail Transfer Protocol (SMTP) email servers (each to bedesignated as either a Primary or Backup server). This allows users to receivetheir OTP via email each time they attempt to log onto the EMC. An SMTP Backupserver is required to provide EMC access redundancy in the event that the PrimarySMTP server fails for any reason.

Since Enterprise Back Office applications also require an SMTP email server, youcould assign that email server as either a Primary or Secondary server for yourSimphony EMC MFA logon purposes.

• Each employee using the EMC or Simphony Web Portal (SWP) must have a validemail address configured in their employee record.

The Oracle Hospitality Simphony PA-DSS Implementation Guide contains PaymentCard Industry information about Multi-Factor Authentication.




Related Topics





• Configuring and Resetting Email AddressesAfter enabling Multi-Factor Authentication (MFA), each user that accesses theEMC or Simphony Web Portal (SWP) must register their email address. The

Chapter 5Multi-Factor Authentication for EMC Access

5-5

system prompts each EMC user to do so. This enables users to receive the one-time password (OTP) via email to complete the EMC login process. To enroll auser’s email address using the EMC:







MFA Configuration During the Installation of SimphonyWhen running the Simphony installation application, you are prompted to configureMFA. Your choices are:

1. Deselect the Email One-Time Password checkbox and click Next to bypass thispart of the installation until after Simphony has been installed. Bear in mind thatwhen you deselect the Email One-Time Password checkbox, you receive amessage that indicates your system is not in compliance with PCI standards.

2. If you choose to configure MFA at this time, the configuration instructions are thesame as outlined here: Configuring the SMTP and Backup SMTP Servers in theEMC

It is important to note that if you are performing a Simphony Standard CloudService installation, MFA configuration that is completed during the installation ofSimphony is duplicated for each enterprise. After Simphony has been installed,you can go back and make edits in the EMC for individual enterprises (ororganizations) that might have differing SMTP servers or settings from each other.

Chapter 5MFA Configuration During the Installation of Simphony

5-6

Figure 5-3 Enabling Multi-Factor Authentication

Related Topics







Accessing the Simphony EMC Using Multi-FactorAuthentication

To utilize Multi-Factor Authentication (MFA) on your Simphony system, you need toadd and register your email address. Follow the steps outlined below:

1. When first attempting to log onto the Simphony EMC, when prompted, enter youruser name in the User Name field, and your email address in the Email Addressfield.

2. Re-enter your email address in the Confirm Email Address field and clickRegister. This email address is utilized to send you a one-time password (OTP).Your registered email address is written to your employee record in the newlyadded Email field.

3. Access the email account you registered in step 1 and open the email containingthe OTP.

Chapter 5Accessing the Simphony EMC Using Multi-Factor Authentication

5-7

4. Enter the password in the One-Time Password field and click Enter.

OTP passwords are only valid for five minutes, so enter your OTP password in atimely fashion. If the 5 minute threshold is exceeded, you are required to re-loginto the EMC to generate another OTP. OTPs are valid for one single entry for theindividual attempting to log onto the EMC at that time. After entering a valid OTP,the EMC opens.

Related Topics







Configuring the SMTP and Backup SMTP Servers in theEMC

SMTP and Backup SMTP server settings are configured and saved at the Enterpriselevel. To configure the SMTP servers:

1. Select the Enterprise level, click Setup, click Enterprise Parameters, and thenclick the Login tab.

2. Within the Multi-Factor Authentication section, enable the Email One-TimePassword option.

Figure 5-4 EMC Enterprise Parameters Login Tab

3. From the Email Configuration section, select the Primary SMTP Server subtaband enter the required settings in the fields listed below:

a. Server: Enter either the IP address or the name of the Primary SMTP server.Click the Select button to choose an email provider, and then click OK. Whenyou select an email provider, the Server field auto-populates with an SMTP

Chapter 5Configuring the SMTP and Backup SMTP Servers in the EMC

5-8

server name that includes the selected email provider’s naming convention.For example, SMTP.EMAIL.COM.

b. Port: Enter a port number or utilize the defaults.

c. SSL: Select to enable a secure connection using HTTPS.

d. User Name: Enter a user name for access to the Primary SMTP server.

e. Password: Enter a password for access to the Primary SMTP server and re-enter it in the Confirm password field for verification.

f. Source Email: Enter your source email address. This email address is usedas the sender of all OTP emails.

g. (Optional) Name: Enter an alternate (alias) name for the Source Emailsender.

4. Click the Backup SMTP Server subtab and enter the IP address or server nameof the Backup SMTP server.

5. Enter information in the fields as listed above for the SMTP Backup server.

6. Click Save.

7. On the Primary SMTP Server tab, click the Send Test Email button to confirmthe SMTP server’s configuration and that the OTP email is received. Repeat thisstep on the Backup SMTP Server tab to confirm the functionality.

Related Topics







Configuring and Resetting Email AddressesAfter enabling Multi-Factor Authentication (MFA), each user that accesses the EMC orSimphony Web Portal (SWP) must register their email address. The system promptseach EMC user to do so. This enables users to receive the one-time password (OTP)via email to complete the EMC login process. To enroll a user’s email address usingthe EMC:

1. Select the Enterprise level, click Configuration, and then click EmployeeMaintenance.

2. Search for the employee record that requires editing.

3. Click the Email button and enter the user’s email address in the Email Addressfield. Re-enter the email address in the Confirm Email Address field and clickRegister.

Chapter 5Configuring and Resetting Email Addresses

5-9

Figure 5-5 Employee Email Address Configuration

4. If a user’s email address changes, click the Email button and enter the user’sCurrent Email Address (that is already registered on the system), new EmailAddress, and then re-enter the address in the Confirm Email Address field andclick Register.

5. Depending on your Employee Role privilege settings in reference to accessing theEmployee Maintenance module, you could also enter or edit the Email field foryourself or others.

Related Topics







Setting the Max Allowed Failed Logins for EMC AccessMFA adheres to the following EMC account lock out setting:

1. Select the Enterprise, click Setup, click Enterprise Parameters, and then clickthe Login tab.

2. From the Options section, set the value for the Maximum Allowed Failed Loginsfield.

After reaching the failed login threshold (based on entering an invalid EMC user orOTP password), users are notified that their login was rejected by the system andthat their account is currently locked out.

Chapter 5Setting the Max Allowed Failed Logins for EMC Access

5-10

Related Topics







Forgotten EMC Password RecoveryStaff members occasionally forget their password to access the EMC or SimphonyWeb Portal (SWP). You can reset your password or, in some cases, assist others inresetting their password (if you are privileged to do so). This is accomplished byreceiving a temporary, One-Time Password (OTP) via email, which then allows you tolog on and reset your password. To further enhance security, you are prompted by thesystem to choose three security questions from a drop-down list. You must then enterthe answers (known only to you) to each of the security questions.

OTPs are valid for one single entry for the individual attempting to log on to the EMCat that time. One-Time Passwords are only valid for five minutes after they aregenerated by the system.

Prerequisites

To use this functionality, the following requirements must be met:

• You must install and make network accessible, two separate Simple Mail TransferProtocol (SMTP) email servers (each to be designated as either a Primary orBackup server). This is required so that One-Time Passwords can be emailed toemployees as needed.

• To use the Can’t Sign In? link, each employee using the EMC must have a validemail address configured in their employee record

If you are locked out of the EMC, you can reset your own password (if you have thenecessary access privileges assigned to your account).

Chapter 5Forgotten EMC Password Recovery

5-11

Figure 5-6 EMC Login Can’t Sign In?




Related Topics








Chapter 5Forgotten EMC Password Recovery

5-12





Configuring Access Privileges for Resetting a PasswordTo access and reset passwords for other users, you need to be assigned theappropriate privileges in the EMC.

1. Select the Enterprise level , click Configuration, and then click Roles.

2. Click the EMC Modules tab and scroll to the Personnel section.

3. Select the options for the Employees (Enterprise) access privileges for each ofthe following columns:

• View

• Edit

• Add

• Delete

Figure 5-7 Roles for EMC Modules

4. Click Save.

5. Click the Actions tab, and then scroll through the Action column until you reachthe Security section.

6. Select the Can Change Others’ Passwords and Email Addresses and SecurityQuestions check box to enable the option, and then click Save.

Chapter 5Configuring Access Privileges for Resetting a Password

5-13

Figure 5-8 Roles Actions Security Settings

7. Ensure that all users requiring Multi-Factor Authentication (MFA) configurationpermissions are assigned a role that have these access privileges enabled.

Related Topics







Resetting Passwords from the Simphony Web PortalYou can reset passwords and configure your security questions from the SimphonyWeb Portal (SWP) page. To change your password:

1. Open the Simphony Web Portal URL. When prompted, enter your User Name,and then click the Can’t Sign In? link. You are provided with a One TimePassword (OTP) via email.

Chapter 5Resetting Passwords from the Simphony Web Portal

5-14

Figure 5-9 Simphony Web Portal Logon Screen’s Can’t Sign In? Link

The following prerequisites are validated.

2. When prompted, enter your User Name and registered Email Address.

Figure 5-10 Request One Time Password Screen

3. The system validates the information you entered, and shows a details pagewhere you must correctly answer your security questions as configured in thesystem. Upon entering your validated logon and security question responses, anOTP token is sent to your email account, and you are redirected to the ForgotPassword page. You are prompted to enter your OTP and your new password,and to confirm it by entering these credentials again.

4. When you click the Can’t Sign In? link from the EMC Log in screen, the systemredirects you to the Request One Time Password (OTP) page of the SWP in abrowser. To log in, enter the following information, and then click Next:

• Username


5-15

• Email Address

From the SWP, you can change your password and update your securityquestions. The following image shows the default User Profile screen. You canaccess the User Profile screen from the SWP page by clicking the User Profilelink on the toolbar.

Figure 5-11 Simphony Web Portal (SWP) User Profile Screen

Note:

If you do not meet the following prerequisites, you must request to havea privileged supervisor initiate recovering your password:

• You do not have a valid email address configured within youremployee record

• You have not configured your security questions and answers

Related Topics








5-16

Simphony Installation for an All-in-One ServerThe All-in-One server installation scenario is only supported for those using Reportingand Analytics version 8.5.1 Patch 3.

1. Log in and download the Simphony version 18.1 installation application from theOracle Technology Network (OTN) website at https://edelivery.oracle.com/.

2. Run the Setup file, and then click Next to continue the installation.

3. Select Application and Database Components, and then click Next. List ofSimphony Components and Services contains more information.

Figure 5-12 Simphony Installation Application

4. Select all of the components, and then click Next. The Simphony Data RequestProcessing Service is installed by default, and is utilized for Import/Export tasks.

Chapter 5Simphony Installation for an All-in-One Server

5-17

https://edelivery.oracle.com/

Figure 5-13 Simphony Install Component Selections

5. Select all of the components that are to be enabled by default, and then click Next.

Figure 5-14 Simphony Install Components to Enable by Default


5-18

6. If are not using a Load Balancing server and are utilizing the Import/Export featureor plan to use the Simphony Engagement Cloud Service:

a. Select IIS for the Certificate Location field.

b. To add a new certificate, select New, click Select, enter or select thecertificate location, and then enter the Password for the certificate.

c. To add an existing certificate, select Existing, and then select the certificatefrom the drop-down list.

d. Enter the port number in the Service Host Secure Port field.

If you define a Service Host Secure Port number other than the default of 443,you need to configure the IIS Bindings of each Application Pool to the newport. For information on adding IIS Bindings, refer to the Microsoft TechNetLibrary at https://technet.microsoft.com/en-us/ for more information.

7. Enter the IP address of the server for the Service Host Name (computer name) inthe Https IP Address field. If the server is using a Domain Name System (DNS)or Host file mapping, you can enter the name of the server instead of the IPaddress. To install Simphony on a named instance of Microsoft SQL Server, enterthe Server Host Name as ServerName\InstanceName.

Figure 5-15 Simphony Install Certificate Information

8. Click Next.

9. If you are using a Load Balancing server and are utilizing the Import/ExportService or plan to use the Simphony Engagement Cloud Service, selectLoadBalancer for the Certificate Location field.

10. Enter the port number in the Service Host Secure Port field.


5-19


• If you define a Service Host Secure Port number other than the default of 443,you need to enable that port on the Load Balancer server.

• If you define a Service Host Secure Port number other than the default of 443,you also need to configure the IIS Bindings of each Application Pool to thenew port. For information on adding IIS Bindings, refer to the MicrosoftTechNet Library at https://technet.microsoft.com/en-us/ for more information.

• You can define any free port number for the Service Host Port. If you define aport number other than the default 443, you must manually change the portnumber when you install subsequent services.

• If you plan to install Reporting and Analytics on the same server as Simphony,do not assign port number 8081 for the Service Host Port. This is the defaultport number assigned to the Red Hat JBoss server for Back Office Reports.

a. Select IIS in the Certificate Location field.


c. To add an existing certificate, select Existing, and then select the certificatefrom the drop-down list.

11. Click Next.

Figure 5-16 Service Host and Default Gateway Addresses

12. Enter the Service Host Name and Service Host Port number as well as theDefault Gateway IP and Default Net Mask IP addresses

13. Click Next.


5-20


14. Select the database platform type of either Microsoft SQL Server or OracleDatabase, and then click Next:a. If you are using an Oracle Database, select Oracle.

For All-in-One installation scenarios, the installation application installs anOracle 12c client (even if you are using Oracle Database 11g as a platform). Ifyou are using Oracle Database 12c, the installer does not install an Oracle 12cclient.

b. Click OK to install the 12c client if prompted to do so.

c. If you are using a Microsoft SQL Server database, select MS-SQL.

15. Enter or select the location to install Simphony, and then click Next twice.

Oracle Hospitality recommends that you install the Simphony application on aseparate partition from where the Microsoft Windows or Oracle Linux operatingsystem resides (usually the C:\ drive).

16. To install Simphony with a blank database:

a. Select Blank Database.

b. Enter a strong Username and Password to comply with Payment CardIndustry (PCI) security guidelines. The credentials that you enter here areused to create the Simphony super user to access the EMC.

c. Confirm the password, and then click Next.

17. To install Simphony with a sample database, select Sample Database, click Next,and then click Yes to continue with the installation.

DO NOT use the Sample Database for production systems. It is meant fordemonstration purposes only.

18. If you selected Oracle as the database platform type:

a. Enter the information to create the transaction database, and then click Next. List of Simphony Database Configuration Fields contains more information onthe database setup options.

b. Enter the login credentials for the default sys user, and then click OK.

c. Enter the information to create the security database, and then click Next.

Oracle Hospitality recommends separating the Transaction and Securitydatabases onto to different servers for additional security.

19. If you selected MS-SQL as the database platform type:

a. Enter or select the location to create the transaction database data files, andthen click Next. List of Simphony Database Configuration Fields containsmore information on the database setup options.

b. Enter the information to configure the transaction database, and then clickNext.

c. Enter the login credentials for the sa user, and then click OK.

d. Enter or select the location to create the security DB data files, and then clickNext.

Oracle Hospitality recommends separating the Transaction and Securitydatabases onto to different servers for additional security.

20. Enter the following information that is used to connect to the existing securitydatabase, and then click Next.


5-21

a. Server Name - Enter the name of the database server.

b. Service Name - Oracle Database users - Enter the name of the service (TNSalias).

c. Instance Name - Microsoft SQL Server users - Enter the Microsoft SQLServer’s database name (usually contains the database server’s name).

d. Username - Enter your security database access user name.

e. Password - Enter your security database access password.

f. Database Port - Enter the port number used to access the security databaseserver, and click Next.

Figure 5-17 Security Database Connection Information

21. Enter the following information to connect to the reporting database.

a. Server Name - Enter the name of the reporting database server.



d. Username - Enter (or verify) your reporting database access user name.

e. Password - Enter your reporting database access password.

f. Database Port - Enter the port number used to access the reportingdatabase.

g. Username - Enter (or verify) your reporting database access user name.


5-22

h. Password - Enter your reporting database access password, and click Next.

Figure 5-18 Simphony Install Reporting Database Connection

22. You have the option to configure Multi-Factor Authentication (MFA) if you alreadyhave your SMTP email servers setup and validated. Refer to MFA ConfigurationDuring the Installation of Simphony for instructions about configuring MFAduring the installation process.

23. Click Confirm.

24. After the installation completes, click Finish to exit the Simphony setup.

25. Click Yes to restart the computer.

26. Proceed to Post-Installation Tasks to continue.

Related Topics








5-23

6Installing Simphony on Multiple Servers

In a multi-server installation, you install the Simphony application and databasecomponents on one or more separate servers.

The following table outlines the process for installing Simphony on multiple servers,depending on the database platform that you are using:

Table 6-1 Overview of Installing Simphony on Multiple Servers

Database Type Description Instructions

Oracle Database When installing Simphony with anOracle database, you can installSimphony database components onseparate database servers from aremote machine while installingSimphony on the application servers.

For properties using separate serversfor the Simphony application anddatabases, install an Oracle 12cClient on all application servers sothat it can connect to the remotedatabase server.

1. Create Simphony DatabaseTablespaces. See CreatingOracle Database Tablespaces.

2. Install the Simphony applicationcomponents. See InstallingSimphony ApplicationComponents on One or MoreServers.

3. Run the Simphony installationapplication to install the Oracle12c Client on all Simphonyapplication servers.

Microsoft SQLServer

When installing Simphony withMicrosoft SQL Server, you cannotinstall the databases from a remotemachine; you must run the Simphonydatabase setup on the local databaseservers and install the databasecomponents.

1. Install the Simphony databasecomponents on the databaseservers. See Installing SimphonyDatabase Components onMicrosoft SQL Server.

2. Install the Simphony applicationcomponents. See InstallingSimphony ApplicationComponents on One or MoreServers.

• Installing Simphony Database Components on Microsoft SQL Server

• Installing Simphony Application Components on One or More Servers

Related Topics




6-1

Installing Simphony Database Components on MicrosoftSQL Server

1. Follow all pre-installation tasks for the site. Pre-Installation Tasks contains moreinformation.

2. Run the Setup file, and then click Next to continue the installation.

3. Select Database Components Only, and then click Next.

4. Select MS-SQL as the database platform type, and then click Next.

5. Enter or select the location to install Simphony, and then click Next twice.

Oracle recommends that you install the Simphony application on a separatepartition from where the Microsoft Windows operating system resides.

6. To install Simphony with a blank database:

a. Select Blank Database.

b. Enter a strong Username and Password to comply with Payment CardIndustry (PCI) security guidelines.

The credentials that you enter here are used to create the Simphony superuser to access the EMC.

c. Confirm the password, and then click Next.

7. To install Simphony with a sample database, select Sample Database, click Next,and then click Yes to continue with the installation.

Do not install the sample database to be used for an actual food and beverage orretail environment.

8. Enter or select the location to create the transaction database data files, and thenclick Next. List of Simphony Database Configuration Fields contains moreinformation on the database setup options.

9. Enter the information to configure the transaction database, and then click Next.

10. Enter the credentials for the SA user, and then click OK.

11. Enter or select the location to create the security DB data files, and then clickNext.

12. Enter the information to configure the security database, and then click Next.

13. Click Confirm.

14. After the installation completes, click Finish to exit the Simphony setup.


Related Topics

• Installing Simphony on Multiple Servers


Chapter 6Installing Simphony Database Components on Microsoft SQL Server

6-2

Installing Simphony Application Components on One orMore Servers

1. Ensure that the application and database server or servers are set up asdescribed in Installing Simphony on Multiple Servers.

2. Select Application Components Only, and then click Next.

3. Select all components, and then click Next. List of Simphony Components andServices contains more information.

4. If you are installing all Simphony application components on a single server, selectall the services, and then click Next.

5. If you are installing Simphony application components on more than one server:

a. On the primary application server, select all services, and then click Next.

b. On all other application servers, deselect Sequencer Service, and then clickNext.

6. Follow the instructions in Simphony Installation to complete the installation. Whenconfiguring the databases, enter the Server Host Name or IP address, ServiceHost Name, and logon credentials for the Simphony database servers.


Related Topics



Chapter 6Installing Simphony Application Components on One or More Servers

6-3

7Upgrading from a Previous Release

Upgrading Reporting and Analytics (R&A)

R&A version 9.0

Prior to upgrading to Simphony version 2.9 or later (including Simphony 18.1),upgrade the R&A application server to version 9.0 Patch 8 using the Back Officeinstallation application. The Oracle Hospitality Enterprise Back Office InstallationGuide Release 9.0 contains more information about upgrading Reporting andAnalytics.

R&A version 8.5.1

Prior to upgrading to Simphony version 2.9 or later (including Simphony 18.1),upgrade the R&A application server to version 8.5.1 Patch 3 using the Back Officeinstallation application. The Oracle Hospitality Reporting and Analytics DeploymentGuide Release 8.5 contains more information about upgrading Reporting andAnalytics.

• Upgrading to the Simphony 18.1 ReleaseSimphony version 18.1 performs an upgrade from Simphony version 2.9 or later.To enhance your system’s security, during the installation, the Simphonyinstallation application enables you to physically separate the Transaction(MCRSPOS) database from the Security (MCRSCACHE) database (onto anotherdatabase server), and then proceed with the upgrade. Oracle Hospitality stronglyrecommends to store these databases on separate database servers. Thefollowing sections review three possible upgrade scenarios:

• Upgrades with Separate Transaction and Security Database Servers (whenadding a new database server)This section provides upgrade instructions to enhance your site’s system security.This includes adding a new physical database server to house the site’s securitydatabase. If the site uses multiple Simphony application servers, upgrade theinitial application server to version 18.1. After upgrading subsequent applicationservers, ensure that on each application server, that the security database servername matches the dataSource entry for the CACHE host name located in theapplication server’s DBSettings.xml. This file is located on the initial Simphonyapplication server that was upgraded. For example:

• Upgrades without Separate Transaction and Security Database ServersThis section provides upgrade instructions for site’s that want to maintain theirTransaction and Security databases on the same database server. To initiate thistype of upgrade, perform the following steps:

• Upgrades with Existing Separated Transaction and Security Database ServersThis section provides upgrade instructions for site’s that already have separateTransaction and Security database servers. To initiate this type of upgrade,perform the following steps:

• Upgrading Prior to the Simphony 18.1 Release

• Post-Upgrade Tasks

7-1

• Post-Upgrade Steps for CAPS on IIS for Simphony 2.9 Users

Related Topics

• Upgrading to the Simphony 18.1 ReleaseSimphony version 18.1 performs an upgrade from Simphony version 2.9 or later.To enhance your system’s security, during the installation, the Simphonyinstallation application enables you to physically separate the Transaction(MCRSPOS) database from the Security (MCRSCACHE) database (onto anotherdatabase server), and then proceed with the upgrade. Oracle Hospitality stronglyrecommends to store these databases on separate database servers. Thefollowing sections review three possible upgrade scenarios:

• Upgrades with Separate Transaction and Security Database Servers (whenadding a new database server)This section provides upgrade instructions to enhance your site’s system security.This includes adding a new physical database server to house the site’s securitydatabase. If the site uses multiple Simphony application servers, upgrade theinitial application server to version 18.1. After upgrading subsequent applicationservers, ensure that on each application server, that the security database servername matches the dataSource entry for the CACHE host name located in theapplication server’s DBSettings.xml. This file is located on the initial Simphonyapplication server that was upgraded. For example:

• Upgrades without Separate Transaction and Security Database ServersThis section provides upgrade instructions for site’s that want to maintain theirTransaction and Security databases on the same database server. To initiate thistype of upgrade, perform the following steps:

• Upgrades with Existing Separated Transaction and Security Database ServersThis section provides upgrade instructions for site’s that already have separateTransaction and Security database servers. To initiate this type of upgrade,perform the following steps:

• Upgrading Prior to the Simphony 18.1 Release

Upgrading to the Simphony 18.1 ReleaseSimphony version 18.1 performs an upgrade from Simphony version 2.9 or later. Toenhance your system’s security, during the installation, the Simphony installationapplication enables you to physically separate the Transaction (MCRSPOS) databasefrom the Security (MCRSCACHE) database (onto another database server), and thenproceed with the upgrade. Oracle Hospitality strongly recommends to store thesedatabases on separate database servers. The following sections review three possibleupgrade scenarios:

• Upgrades with Separate Transaction and Security Database Servers (whenadding a new database server)

• Upgrades without Separate Transaction and Security Database Servers

• Upgrades with Existing Separated Transaction and Security Database Servers

1. Ensure that the Simphony application and database servers meet therequirements listed in Pre-Installation Tasks.

2. Log in and download the Simphony version 18.1 installation application from theOracle Technology Network (OTN) website at https://edelivery.oracle.com/.

3. Run the Setup and click Next.

Chapter 7Upgrading to the Simphony 18.1 Release

7-2

https://edelivery.oracle.com

If you have the application and the database on separate servers, run theinstallation application on the application server.

4. Enter the logon credentials for a database administrator, and then click OK.

• If you are using an Oracle database, enter the credentials for the SYS user.

• If you are using Microsoft SQL Server, enter the credentials for the SA user.

Beginning with the Simphony 2.10 release or later, you can now upgradeapplication components on servers with or without downloading CAL Packages.This flexibility helps to speed up the upgrade process on properties utilizingmultiple application servers.

Figure 7-1 Simphony Components Installation Options

Related Topics

• Upgrading from a Previous Release

Upgrades with Separate Transaction and Security DatabaseServers (when adding a new database server)

This section provides upgrade instructions to enhance your site’s system security. Thisincludes adding a new physical database server to house the site’s security database.If the site uses multiple Simphony application servers, upgrade the initial applicationserver to version 18.1. After upgrading subsequent application servers, ensure that oneach application server, that the security database server name matches thedataSource entry for the CACHE host name located in the application server’s

Chapter 7Upgrades with Separate Transaction and Security Database Servers (when adding a new database server)

7-3

DBSettings.xml. This file is located on the initial Simphony application server that wasupgraded. For example:

alias="Cache"

dbType="<TYPE> "

dataSource="<SERVERNAME>"

To initiate this type of upgrade:

1. Perform steps 1-5 as shown in Upgrading Prior to the Simphony 18.1 Release

2. Certificate Location - Throughout the Simphony 18.1 upgrade process, theSimphony installation application checks for the entry of a valid Service HostName. The following parameters review the installation application’s Service HostName validation behavior:

a. If Microsoft Internet Information Services (IIS) is selected for the CertificateLocation field, note that the Service Host Name (to be entered on the nextinstallation screen) is based on the installed secure certificate's CommonName (CN) field.

b. Certificate - To add a new certificate, select New, click Select, enter or selectthe certificate location, and then enter the Password for the certificate.

c. To utilize an existing certificate, select Existing, and then select the installedcertificate from the drop-down list.

d. If you are using a Load Balancer server and utilizing the Import/Export Serviceor plan to use the Oracle Hospitality Simphony Engagement Cloud Service,select LoadBalancer for the Certificate Location field. Note that the ServiceHost Name (to be entered on the next installation screen) is based on the FullQualified Domain Name (FQDN) of your application server.

e. Https IP Address - Enter the application server’s IP address.

f. Service Host Secure Port - If you enter a port number other than the defaultof 443, you need to enable that port on the Load Balancer server and thenclick Next.

3. When using IIS, enter (or verify) the Service Host Name (for the Simphonyapplication server). If the Service Host Name does not match the installed secureCertificate’s CN text, a warning message dialog appears.

a. Do not ignore the message, select No, and then correct the invalid ServiceHost Name.

b. Enter the Default Gateway IP address and Default Net Mask in theircorresponding fields, and then click Next.

4. When using LoadBalancer, enter (or verify) the Service Host Name (for theSimphony application server). If the Service Host Name does not match the FQDNof your computer, a warning message dialog appears.



5. Enter the following information that is used to connect to the security database:

a. Server Name - Enter the name of the security database server.


7-4





f. Database Port - Enter the port number used to access the security databaseserver, and then click Next.

6. Enter your security database administrator Username and Password logoncredentials, and then click OK and Next. If the security database server name andlogon credentials entered in step 3, matches the server name where theTransaction database is stored, the installation application prompts and affordsusers the opportunity to separate the databases onto different database servers.Since you want the two databases separated, click Yes.

7. Enter the following information that is used to connect to the secondary databaseserver and then click Next:

a. Server Name - Enter the name of the secondary database server. This nameshould match the dataSource entry for the CACHE host name located in theapplication server’s DBSettings.xml. For example:

alias="Cache"

dbType="<TYPE> "

dataSource="<SERVERNAME>"


c. Instance Name - Microsoft SQL Server users - Enter the Microsoft SQLServer’s database name (usually contains the database server’s name). Perthe Pre-Installation Tasks, for Microsoft SQL Server users, theimplementation consultant must go to the secondary database server andmanually create the folders specified in the Remote Database Location field.Alternatively, the implementation consultant can enter the location ofpreviously existing files on the secondary database server. Click Next.



f. Confirm Password - Re-enter your security database access password.

g. Database Name - Enter the name of the security database.

h. Database Port - Enter the port number used to access the security database.

i. Remote Database Location - Enter the path and folder names where theSecurity database is to be created.


7-5

Figure 7-2 New Security Database Information


• If you are using an Oracle Database, enter the credentials for the SYS user.

• If you are using a Microsoft SQL Server database, enter the credentials for theSA user.

9. Enter the following information to connect to the reporting database:









10. Enter a database administrator’s logon credentials, click OK, and then click Next.



11. Click Confirm. The installation application creates a new user and securitydatabase on the secondary database server and drops them from the originaldatabase server. When the upgrade is complete, click Finish.


7-6

Related Topics


Upgrades without Separate Transaction and SecurityDatabase Servers

This section provides upgrade instructions for site’s that want to maintain theirTransaction and Security databases on the same database server. To initiate this typeof upgrade, perform the following steps:

1. Perform steps 1-5 as shown in Upgrading Prior to the Simphony 18.1 Release.











4. When using LoadBalancer, enter (or verify) the Service Host Name (for theSimphony application server). If the Service Host Name does not match the FQDNof your computer, a warning message dialog appears.



Chapter 7Upgrades without Separate Transaction and Security Database Servers

7-7

5. Enter (or verify) the Service Host Name for the Simphony application server,Default Gateway IP address, and Default Net Mask in their corresponding fields,and then click Next.

6. Enter the following information that is used to connect to the existing securitydatabase, and then click Next:




















Related Topics


Upgrades with Existing Separated Transaction and SecurityDatabase Servers

This section provides upgrade instructions for site’s that already have separateTransaction and Security database servers. To initiate this type of upgrade, performthe following steps:

Chapter 7Upgrades with Existing Separated Transaction and Security Database Servers

7-8

1. Perform steps 1-5 as shown in Upgrading Prior to the Simphony 18.1 Release.











4. When using LoadBalancer, enter (or verify) the Service Host Name (for theSimphony application server).

a. If the Service Host Name does not match the FQDN of your computer, awarning message dialog appears.

b. Do not ignore the message, select No, and then correct the invalid ServiceHost Name.

5. Enter the Default Gateway IP address and Default Net Mask in theircorresponding fields, and then click Next.

6. Enter the following information that is used to connect to the existing securitydatabase, and then click Next:





Chapter 7Upgrades with Existing Separated Transaction and Security Database Servers

7-9
















Related Topics


Upgrading Prior to the Simphony 18.1 Release1. Ensure that the Simphony application and database servers meet the

requirements listed in Chapter 2 under Pre-Installation Tasks.

2. Log in and download the Simphony 18.1 release installation application from theOracle Technology Network (OTN) website at https://edelivery.oracle.com.

3. Run the Setup and click Next. If you have the application and the database onseparate servers, run the installation application on the application server.


• If you are using an Oracle database, enter the credentials for the sys user.

• If you are using Microsoft SQL Server, enter the credentials for the sa user.

5. Select Update Application Components on this machine, and then click Next.

6. If you are using a Load Balancer server and utilizing the Import/Export Service orplan to use the Oracle Hospitality Simphony Engagement Cloud Service, selectLoadBalancer for the Certificate Location field. If you define a Service HostSecure Port number other than the default of 443, you need to enable that port onthe Load Balancer server.

Chapter 7Upgrading Prior to the Simphony 18.1 Release

7-10

https://edelivery.oracle.com

7. If you are not using a Load Balancer server and are installing the Import/ExportService or plan to use the Engagement Cloud Service:

a. Select IIS for the Certificate Location field.



d. Enter the Service Host Secure Port.

If you define a Service Host Secure Port number other than the default of443, you need to configure the IIS Bindings of each Application Pool to thenew port. For information on adding IIS Bindings, refer to the MicrosoftTechNet Library at https://technet.microsoft.com/en-us/ for more information.

8. If you are connected to Reporting and Analytics, enter the passwords for theMMSQL and CEDB database users, and then click Next.

9. If you have Reporting and Analytics installed and want to connect to it, click Yeswhen prompted, enter the information to connect to the reporting database, andthen click Next.

10. Click Next, and then click Confirm to begin the upgrade.

11. Click Yes to restart the server.

Related Topics


Post-Upgrade TasksThe following table lists the tasks you must perform after upgrading to Simphonyversion 18.1 from an earlier release.

Table 7-1 Post-Upgrade Tasks for Simphony Version 18.1

Post-Upgrade Task Instructions

*For Oracle Database users only; Update theTransction DB Schema and revoke PUBLICaccess on the DBMS_SCHEDULER

The Simphony installer requires access toexecute certain Oracle database packages forwhich public privileges are not granted. Onceyour upgrade is complete, the public accessgrant should be revoked and a specificdatabase schema grant can be created.

After performing an upgrade, using OracleSQL Developer, execute the followingrequests:

• GRANT EXECUTE ONDBMS_SCHEDULER TO<TRANSACTIONSCHEMA>

• REVOKE ACCESS ONDBMS_SCHEDULER FROM PUBLIC

Refer to the Oracle Database SecurityGuidehttps://docs.oracle.com/en/database/oracle/oracle-database/12.2/dbseg/index.htmlfor more information.

Chapter 7Post-Upgrade Tasks

7-11




Table 7-1 (Cont.) Post-Upgrade Tasks for Simphony Version 18.1

Post-Upgrade Task Instructions

Update the Property’s Admin and DatabaseCredentials

See Updating Property Administrator andDatabase Logon Credentials for details andinstructions.

Update the Simphony License Counts See Updating Simphony License Counts forinstructions.

Update all Check and Posting Service (CAPS)clients prior to updating workstations with thelatest CAL Packages

See Check and Posting Service (CAPS) in theOracle Hospitality Simphony ConfigurationGuide.

Update or verify your CAL Packages andschedule their deployment to your workstationclients

See Client Application Loader (CAL) in theOracle Hospitality Simphony ConfigurationGuide for more information about configuringand deploying CAL Packages.

Related Topics

• Step 1 - Close and Post All Transactions

• Step 2 - Access the IIS Manager Console

• Step 3 - Rename the IIS Folder

• Step 4 - Enable an Option and Configure CAPS

• Step 5 - Stop IIS

• Step 6 - Move the DbSettings.xml to the Newly Defined IIS CAPS Path

• Step 7- Start IIS

• Step 8 - Verify Log Creation, Database Tables, and Delete the Old Directory

Post-Upgrade Steps for CAPS on IIS for Simphony 2.9Users

This section only applies if you are upgrading from the Simphony 2.9 General Release(GR) and are using either an Oracle or Microsoft SQL Server database platform, andare upgrading to Simphony version 2.10 or 18.1.

Note:

No additional post-upgrade steps are necessary for CAPS on MicrosoftInternet Information Services (IIS) if you upgrade from Simphony versionslater than Simphony 2.9 GR (for example, Simphony versions 2.9.3, and 2.10or later).




Chapter 7Post-Upgrade Steps for CAPS on IIS for Simphony 2.9 Users

7-12






Related Topics









Step 1 - Close and Post All TransactionsEnsure that all transactions are closed and posted to the Enterprise prior to performingthe Simphony upgrade.

Related Topics



Step 2 - Access the IIS Manager Console1. From the desktop of each server running CAPS on IIS, select Start, Control

Panel, Administrative Tools, and then select Internet Information Services(IIS) Manager.

2. From the IIS Connections column, expand the Sites folder and right-click the sitecreated for IIS CAPS and select Remove. The name of the IIS CAPS site shouldbe the same as the ServiceHostName. For example, if your service host name isMyIISCapsSvcHost, your site name should be added using the exact same text.


7-13

Figure 7-3 IIS CAPS Site

3. From the IIS Connections column, click Application Pools.

Figure 7-4 Simphony Application Pools

4. Right-click on the application pool created for IIS CAPS and select Remove. Thename of the IIS CAPS pool should be the ServiceHostName Pool. For example, if


7-14

your service host name is MyIISCapsSvcHost, your IIS CAPS application poolname should be MyIISCapsSvcHostPool.

Figure 7-5 IIS CAPS Application Pool

Related Topics



Step 3 - Rename the IIS Folder1. Rename the Simphony version 2.9 IIS CAPS folder.

2. Verify the installed folder path by navigating to the [Drive]:\MICROS\Simphony2\Tools\CAPSConfigurator\CAPSConfigurator.exe.configfile and open it with a text editor such as Microsoft Notepad.


7-15

Figure 7-6 CAPSConfigurator.exe.config IIS CAPS Directory InstallationFolder Path

3. Note that the default Simphony version 2.9 IIS CAPS folder location is: [Drive]:\Simphony2\IISCAPS. Rename the IISCAPS folder to IISCAP_Backup. Thisstep ensures that you maintain a backup of the old folder.

Figure 7-7 Default IIS CAPS Folder Installation Path


7-16

Related Topics



Step 4 - Enable an Option and Configure CAPS1. Access EMC and navigate to the Enterprise level, click the Configuration tab, and

then click Roles.

2. Click your assigned Role and toggle to Form view.

3. Click the Operations tab, and then click the Miscellaneous subtab.

4. In the Miscellaneous Options section, enable option 10065 - Download Software,Install and Authenticate Clients and Service Hosts Using CAL, and then clickSave.

5. Log on to the CAPS Configurator Tool (using the CAPSConfigurator.exe), andfreshly configure CAPS with the default configuration settings by clicking theConfigure CAPS button.


7-17

Figure 7-8 CAPS Configurator Tool

6. Upon successful installation, verify the new directory created under [Drive]:\Simphony2\EgatewayService\IISCAPSServiceHost path.

Related Topics



Step 5 - Stop IISTo stop IIS:

1. Run the command window with administrator privileges.

2. Enter the iisreset /stop command, and then press Enter.

Related Topics



Step 6 - Move the DbSettings.xml to the Newly Defined IIS CAPS Path1. Copy the DbSettings.xml file from the old path (review Step 3 - Rename the IIS

Folder and verify the default CAPS IIS installation path), and then using MicrosoftWindows Explorer, navigate to that path. For example, [Drive]:\Simphony2\IISCAP_Backup\IISCAPS\DbSettings.xml.

2. Paste the DbSettings.xml file to the new path: [Drive]:\Simphony2\EgatewayService\IISCAPSServiceHost.

3. Edit the DbSettings.xml file to update the CAPS database password; this meansto delete the previously existing password value on epw (encrypted format) andenter the password again with pwd (ClearText). For example:


7-18

<root><dbalias="CPServiceDb" dbType="sqlserver" dataSource="xxxx" catalog="xxxxxxx" uid="xxxxxxxxx" pwd=”CAPSDBPassword” port="1433" /></root>

Related Topics



Step 7- Start IISTo start IIS:

1. Run the command window with administrator privileges.

2. Enter the iisreset /start command, and then press Enter.

Related Topics



Step 8 - Verify Log Creation, Database Tables, and Delete the OldDirectory

1. Verify that logs are created here: [Drive]:\Simphony2\EgatewayService\IISCAPSServiceHost\EgatewayLog.

2. Verify that the tables are upgraded on the existing transaction database.

3. Delete the Simphony version 2.9 CAPS directory, for example the IISCAP_Backupdirectory (review Step 3 - Rename the IIS Folder.

Related Topics




7-19

8Post-Installation Tasks

Perform all post-installation tasks to ensure that the application components and thedatabase are configured correctly.

• Updating Simphony License Counts

• Updating Property Administrator and Database Logon Credentials

• Updating the Property EMC Client

• Verifying the Installation

• Configuring Recycle Settings for the IIS Application Pool

• After the Simphony InstallationDepending on if you installed the Blank or Sample database, click the correct linkbelow to see how to access and log onto the Enterprise Management Console(EMC)

• Post Install Steps for Engagement on Load Balanced Simphony ServersIf you are a Simphony Standard or Premium Cloud Service user (not a stand-alone, on-premise installation), and you utilize load balancing for your system, tocompletely configure Engagement, perform the following steps:

• Setting the Start-Of-Day Sequencer Machine and the App Server Time Zone

• Connecting Reporting and Analytics to Simphony

• Enabling Communication Between the Enterprise and Workstations

• Binding SSL Certificates to Internet Information ServicesWith the release of Simphony 2.9 or later, you must have a valid securityCertificate installed on the Simphony application server. This is the samecertificate that is identified and linked to Internet Information Services (IIS) duringthe Simphony software installation process. After a successful installation of theSimphony application, you must perform the following steps to Bind the SSLCertificate to the IIS website.






Related Topics



8-1

• If You Installed the Blank DatabaseIf you installed the Blank Database, then you can either configure the system fromscratch, or import an alternate Simphony database.

• If You Installed the Sample DatabaseThe Sample Database should not be utilized in a production environment. Rather,you should install the Blank Database, and then either configure the system fromscratch, or import an alternate Simphony database.





Updating Simphony License CountsTo edit the system’s license counts:

1. In the EMC, select the Enterprise level, click Setup, and then click EnterpriseParameters.

2. Click the License Configuration tab.

3. Click Configure adjacent to Workstations Client License Count.

4. To add a new license count, selectI would like to set the license count to X,making the new license count X.

5. To append licenses to an existing license count, select I would like to add X tothe current license count, making the new license count X.

6. Enter the number of client licenses purchased.

7. (Optional) Enter additional details regarding the purchased license in EnterReference Information for the License Count Change, and then click OK.

8. Repeat Steps 3 through 7 for Transaction Service Client License Count, andKDS Client License Count.

9. Click Save, and then click Yes to agree to the license.

10. To perform a side by side comparison of the number of purchased licensesagainst the number of configured clients, click View adjacent to the Properties,Revenue Centers, Concessions Terminals, Workstation Client License Count,Transaction Services Client License Count, or KDS Client License Count labels.


Chapter 8Updating Simphony License Counts

8-2







Related Topics

• Post-Installation Tasks






Updating Property Administrator and Database LogonCredentials

When logging on to the EMC for the first time after installing or upgrading to Simphonyversion 18.1, a message indicates that the property credentials are not compliant withthe Simphony standards. To keep the properties safe from security risks, you need toupdate the Admin and Database credentials, which Simphony uses to create andmaintain the workstation databases. Simphony offers the options of configuringsecurity credentials for each property separately or using the same credentials for allproperties in the Enterprise. Simphony requires that you update the system anddatabase administrator credentials every 90 days. If you do not update the credentials,EMC shows the Database Credentials Non-Compliance message each time you logon until you meet the compliance.

• To configure credentials for each non-compliant property separately, see Configuring Different Credentials for Each Property.

Chapter 8Updating Property Administrator and Database Logon Credentials

8-3

• To configure the same credentials for all non-compliant properties in theEnterprise, see Configuring the Same Credentials for All Properties in theEnterprise.

• Configuring Different Credentials for Each Property

• Configuring the Same Credentials for All Properties in the Enterprise






Related Topics









Configuring Different Credentials for Each Property1. In the EMC, select the Enterprise level, click Setup, and then click Properties.

2. In table view, scroll to the right until you see the Admin Credentials and theDatabase Credentials columns. If a property is not compliant, the AdminCredentials and the Database Credentials columns are highlighted in red.

3. Click either the Admin Credentials or the Database Credentials column of thenon-compliant property, and go to the Property Parameters module.

Chapter 8Updating Property Administrator and Database Logon Credentials

8-4

4. Click the Security tab, and then enter the User Security Credentials. Simphonyuses these credentials to authenticate the workstations.

The Install User Security Username must have at least two characters and mustnot contain a company name, product name, common words, or Structured QueryLanguage (SQL) keywords (for example, Micros, Oracle, abcd, 1234, and so on).

The Install User Security Password must have a minimum of eight charactersand adhere to the Oracle Database standards.

5. Enter the Current Password of the Admin User.

6. Enter a new strong password for the Admin User. Database User Passwordscontains more information about password requirements.

7. Repeat Steps 5 and 6 for the Database User, and then click Save.

8. Repeat Steps 3 through 7 for all non-compliant properties.

Configuring the Same Credentials for All Properties in the Enterprise1. In the EMC, select the Enterprise level, click Setup, and then click Enterprise

Parameters.

2. Click the Security tab, and then select Use Same Credentials for All Properties.

3. Select the property whose credentials you want to use, and then enter the NewInstall User Security Password.

4. Re-enter the new security password in the Confirm User Security Passwordfield, and then click Save.

Updating the Property EMC ClientThe Enterprise Management Console (EMC) is the primary configuration application inSimphony. A shortcut for accessing EMC is installed on the application server duringthe installation.

Self-hosted customers also need to follow these steps to configure Remote EMCclients. Remote EMC clients allow users to access the EMC from other computers onthe network.

The Oracle Hospitality Simphony Manager User Guide, specifically the Simphony WebPortal (SWP) section contains instructions about accessing the SWP and updatingyour EMC Client for your property.






Related Topics


Chapter 8Updating the Property EMC Client

8-5








Verifying the Installation1. Open the EMC from the shortcut on the desktop or Start menu.

2. Enter the Application Server Host Name:

• If you are launching EMC locally from the server, enter localhost for theApplication Server Host Name.

• If you are accessing the EMC remotely, enter the Server Host Name or IPaddress of the Simphony application server.

3. If you installed the blank database, enter the logon credentials for the Simphonysuper user that you created when installing Simphony.

4. If you installed the sample database:

a. Log on to the EMC with:

• User: micros

• Password: micros

b. Click OK when prompted to update the password.

c. Enter a new strong password (per PCI DSS 8.2.3 / PA-DSS 3.1.6 standards)for the Simphony super user, and then click Accept.

If you are using an Oracle database, refer to the Oracle Database SecurityGuide for more information about configuring password protection.

d. Click OK when prompted to update the user name.

e. Enter a new user name for the EMC super user, and then click Accept.

5. Click Login.

Chapter 8Verifying the Installation

8-6

6. Click OK for the EMC Database Credentials Non-Compliance message.

If you can launch and see the EMC and the Simphony Gateway is up and running,Simphony is successfully installed.








Related Topics







Configuring Recycle Settings for the IIS Application PoolIf you configure the application pool to recycle at a scheduled time using the IISManager, consider configuring the following recycle settings for the IIS ApplicationPools:

• Ensure that the specific times you define do not coincide with your Start-of-Day(SOD) or periods of peak sales activity.

• Set the Memory Based Maximums to less than half of the available servermemory.

• Set the Simphony2 App Pool Pipeline mode to Classic.

Chapter 8Configuring Recycle Settings for the IIS Application Pool

8-7

• Set the Disable Overlapped Recycle setting to True for the Simphony2 AppPool.

In addition to the Simphony2 App Pool, the following IIS App Pools are also installed:

• ImportExportAPIPool: For the Import Export Service.

• SimphonyAppPool: For the Simphony Web Portal.

• WCCPool: For the Engagement feature.

These App Pool’s Pipeline mode settings can remain on their default settings.

For instructions on configuring an application pool to recycle at a scheduled time, referto the Microsoft TechNet Library at https://technet.microsoft.com/en-us/.






Related Topics









Chapter 8Configuring Recycle Settings for the IIS Application Pool

8-8


After the Simphony InstallationDepending on if you installed the Blank or Sample database, click the correct linkbelow to see how to access and log onto the Enterprise Management Console (EMC)

• If You Installed the Blank Database

• If You Installed the Sample Database








Related Topics









Chapter 8After the Simphony Installation

8-9

If You Installed the Blank DatabaseIf you installed the Blank Database, then you can either configure the system fromscratch, or import an alternate Simphony database.

1. Open the EMC from the shortcut on the desktop or Start menu.


• If you are launching EMC locally from the server, enter localhost for theApplication Server Host Name.

• If you are accessing the EMC remotely, enter the Server Host Name or IPaddress of the Simphony application server.

3. Enter the logon credentials for the Simphony super user that you created in Step15 of Simphony Installation Tasks.

4. Click Login.










Related Topics






8-10



If You Installed the Sample DatabaseThe Sample Database should not be utilized in a production environment. Rather, youshould install the Blank Database, and then either configure the system from scratch,or import an alternate Simphony database.

1. Open the EMC from the shortcut on the desktop or Start menu.


a. If you are launching EMC locally from the server, enter localhost for theapplication Server Host Name.

b. If you are accessing the EMC remotely, enter the Server Host Name or IPaddress of the Simphony application server.

3. Log on to the EMC with:

• Username = micros

• Password = micros

4. Click OK when prompted to update the password.

5. Enter a new strong password (per PCI DSS 8.2.3 / PA-DSS 3.1.6 standards) forthe Simphony super user, and then click Accept. If you are using an OracleDatabase, refer to the Oracle Database Security Guide for more information aboutconfiguring password protection.

6. Click OK when prompted to update the username.

7. Enter a new username for the EMC super user, and then click Accept.

8. Click Login.










8-11


Related Topics







Post Install Steps for Engagement on Load BalancedSimphony Servers

If you are a Simphony Standard or Premium Cloud Service user (not a stand-alone,on-premise installation), and you utilize load balancing for your system, to completelyconfigure Engagement, perform the following steps:

1. From the Simphony application server, access the Server Manager, and select theInternet Information Services(IIS) Manager from the Tools menu.

2. Expand the Simphony2 Web Site.

3. Right-click on API, and then click Explore.

Figure 8-1 IIS Simphony2 Web Site- API Application

4. Open the API Web.config file using a text editor.

Chapter 8Post Install Steps for Engagement on Load Balanced Simphony Servers

8-12

5. Edit the AllowHttpForwarding key and set the value to true.

For example: <add key=”AllowHttpForwarding” value=”true” />

6. Save and close the API Web.config file.

7. From the expanded Simphony2 Web Site, right-click on WCC, and then clickExplore.

Figure 8-2 IIS Simphony2 Web Site- WCC Application

8. Open the WCC Web.config file using a text editor.



10. Save and close the WCC Web.config file.

11. From the expanded Simphony2 Web Site, right-click on WS, and then clickExplore.


8-13

Figure 8-3 IIS Simphony2 Web Site- WS Application

12. Open the WS Web.config file using a text editor.



14. Delete the highlighted endpoint text as shown in Figure 4.

Figure 8-4 WS Web.config file

15. Save and close the WS Web.config file.

16. From the expanded Simphony2 Web Site, right-click on EngagementApp, andthen click Explore.


8-14

Figure 8-5 IIS Simphony2 Web Site- EngagementApp Application

17. Open the EngagementApp Web.config file using a text editor.

18. Search the “HostURI” key and set the value to the load balancer host name- fullyqualified domain name (FQDN).

For example: <add key=”HostURI” value=”https://LoadBalancerHostName” />

Figure 8-6 IIS Simphony2 Web Site- EngagementApp Web.config

19. Save and close the EngagementApp Web.config file.

20. From the expanded Simphony2 Web Site, right-click on EngagementAPI, andthen click Explore.


8-15

Figure 8-7 IIS Simphony2 Web Site- EngagementAPI Application

21. Open the EngagementAPI Web.config file using a text editor.

22. Delete the highlighted endpoint text as shown in Figure 8.

Figure 8-8 IIS Simphony2 Web Site- EngagementAPI Web.config

23. Save and close the EngagementAPI Web.config file.







• Binding SSL Certificates to Internet Information ServicesWith the release of Simphony 2.9 or later, you must have a valid securityCertificate installed on the Simphony application server. This is the samecertificate that is identified and linked to Internet Information Services (IIS) duringthe Simphony software installation process. After a successful installation of the


8-16

Simphony application, you must perform the following steps to Bind the SSLCertificate to the IIS website.

Related Topics







Setting the Start-Of-Day Sequencer Machine and the AppServer Time Zone

1. In the EMC, select the Enterprise level, click the Setup tab, and thenclickEnterprise Parameters.

2. Click the Miscellaneous tab, and then enter the Windows machine name for SODSequencer Machine Name.

3. Select the App Server Time Zone.

If you are deploying Simphony on multiple servers, the date, time, and the timezone settings of each app server and database server must correspond.Additionally, the servers’ time zone must correspond with the App Server TimeZone setting in the EMC.

You can synchronize the time settings between the servers by configuring one ofthe servers to be a Network Time Protocol (NTP) server and then point the rest ofthe servers to the NTP server. For information on setting up a Network TimeProtocol server, refer to the Microsoft TechNet Library at https://technet.microsoft.com/en-us/.

4. Click Save.

5. If you installed Simphony on multiple application servers, disable the MicrosSequencer Service on all servers other than the SOD Sequencer Machine.

In the event the application server that is running the Micros Sequencer Servicehas performance issues, start the Micros Sequencer Service on another Simphonyapplication server if the main application server is going to be down for multipledays.




Chapter 8Setting the Start-Of-Day Sequencer Machine and the App Server Time Zone

8-17







Related Topics







Connecting Reporting and Analytics to SimphonyWith the release of Simphony version 2.10 or later, if you utilize Reporting andAnalytics (R&A) version 9.0 Patch 8 or later, the steps outlined below are no longerrequired. Core Simphony reports are now available to set up by default from within theR&A application. If you are utilizing R&A version 8.5.1, the following steps are stillapplicable. Before you connect to R&A, you need to have:

• At least one property in the Enterprise. The Oracle Hospitality SimphonyConfiguration Guide contains more information about adding properties to theEnterprise.

• Organizations and report locations created in R&A for your properties in theEnterprise. See the Hospitality Enterprise Back Office Installation Guide for moreinformation about the prerequisite configurations that are required when creatingOrganizations and report locations.

To identify the location of Reporting and Analytics on the system, perform the followingsteps:

1. In the EMC, select the Enterprise level, click the Setup tab, click EnterpriseParameters, and then click the Reporting and Analytics tab.

Chapter 8Connecting Reporting and Analytics to Simphony

8-18

2. In the Reporting and Analytics Machine Name field, enter the name of thecomputer that is running the MICROS Portal Service.

3. Select the Enterprise level, click the Setup tab, and then click Properties.

4. Double-click a property to open it.

5. Select theReport Location for the property.

6. If the Report Location is not available in the drop-down list:

a. Click New, and then create a Report Location.

b. Complete each field (required) as described below:

• Name: Enter the property name.

• Location Reference: Enter the Property ID. This must be unique.

• Time Zone: Select the time zone from the drop-down list that matches theproperty’s time zone.

• Simphony Labor Logon: Enter a unique user name.

• Simphony Labor Password: Enter a unique password.

7. Click OK, and then click Save.

Figure 8-9 Report Location Configuration

8. Repeat Steps 4 through 7 for all properties in the Enterprise.






Chapter 8Connecting Reporting and Analytics to Simphony

8-19



Related Topics







Enabling Communication Between the Enterprise andWorkstations

To allow the workstations in the property to communicate with the Enterprise, youmust add Firewall exceptions for the following services on your Simphony applicationservers using either the default ports or the ports you assign when installing Simphonyversion 18.1:

• Internet Information Services (IIS): By default uses Transmission Control Protocol(TCP) port 8080 or port 443 for HTTPS connections.

• Client Application Loader (CAL): By default uses TCP port 7300 and UserDatagram Protocol (UDP) ports 7300 through 7302.

• Oracle Hospitality Labor Management: By default uses TCP port 81.

You may need to open extra ports for additional Simphony features. Contact your localsupport representative or Oracle Hospitality Support Services for assistance.

For instructions on opening a port in Windows Firewall, refer to the Microsoft TechNetLibrary at https://technet.microsoft.com/en-us/library.






Chapter 8Enabling Communication Between the Enterprise and Workstations

8-20

https://technet.microsoft.com/en-us/library

Related Topics









Binding SSL Certificates to Internet Information ServicesWith the release of Simphony 2.9 or later, you must have a valid security Certificateinstalled on the Simphony application server. This is the same certificate that isidentified and linked to Internet Information Services (IIS) during the Simphonysoftware installation process. After a successful installation of the Simphonyapplication, you must perform the following steps to Bind the SSL Certificate to the IISwebsite.

1. Click Start, and then click Control Panel.

2. If you are using Windows Server 2008 R2, click System and Security, and thenclick Administrative Tools.

3. In the Administrative Tools window, double- click Internet Information Services(IIS) Manager.

4. Under Connections, Sites, select the site to be secured with the SSL Certificate.

5. From the Actions menu (on the right), click on Bindings...

6. This opens the Site Bindings window.

7. In the Site Bindings window, click Add...

8. This opens the Edit Site Binding window.

9. From the Type drop-down list, select https.

10. Enter the IP address. It should be the IP address of the site or select AllUnassigned.

Chapter 8Binding SSL Certificates to Internet Information Services

8-21

11. Enter the port number in the Port field. The port over which traffic is secured bySSL, is usually 443. The SSL Certificate field should specify the installedcertificate.

12. Click OK.








Related Topics







Chapter 8Binding SSL Certificates to Internet Information Services

8-22

9Uninstalling Simphony

• Uninstalling Simphony

Related Topics


Uninstalling SimphonyUninstalling only removes the Simphony application. To completely remove Simphonyfrom the servers, you must manually delete the Simphony database components fromthe database after uninstalling the application.

1. Run the Simphony version 18.1 Installation application, and click Next.

If you have the application and the database on separate servers, run theinstallation application on the application server.

2. Enter the credentials for a database administrator, and then click OK.

• If you are using an Oracle database, enter the credentials for the sys user.

• If you are using Microsoft SQL Server, enter the credentials for the sa.

3. Select Uninstall Simphony, and then click Next.

4. Click Confirm.

Related Topics


9-1

10Troubleshooting

This chapter describes common problems you might encounter when installingSimphony version 18.1 and explains how to solve them.

• Insufficient System Privileges

• Cannot Connect to the Database Server During the Simphony Installation

• EMC Fails to Launch




Insufficient System PrivilegesThe Insufficient System Privileges message appears when the prerequisite, InternetInformation Services (IIS), has not been installed.

Installing Microsoft Internet Information Services (IIS) 7 contains instructions to installMicrosoft IIS.

• Troubleshooting



Cannot Connect to the Database Server During theSimphony Installation

The Simphony installation application may not connect to the database server due tothe following reasons:

• Windows Firewall is running

• Simphony and SimphonyXDB instances are not running

Adding Simphony to the Windows Firewall Exceptions

The Windows Firewall, that is enabled by default on your operating system couldprevent the Simphony installation application from connecting to the database server.You must set up an exception rule on your firewall setting for the Simphony server andthe database server to continue with the installation. For instructions on seting upexception rules in Windows Firewall, refer to the Microsoft TechNet Library at https://technet.microsoft.com/en-us/library.

10-1



Installing Simphony on Separate Servers

If you are using a separate database server, you must set up an incoming rule to allowconnections from Simphony, depending on your database platform, using either thedefault port or the port you assign during Installation. By default, the Oracle databaseserver uses port 1521 and Microsoft SQL Server uses port 1443. For instructions onopening a port in Windows Firewall, refer to the Microsoft TechNet Library at https://technet.microsoft.com/en-us/library.

Starting the Oracle Listener

If the Oracle Listener is not running, Simphony services cannot start. Ensure that theOracle Listener is running.

• If you are using Oracle Linux, run the command $ lsnrctl status. If the Listeneris running, you will see the listener configuration settings and the servicessummary.

• If you are using Microsoft Windows, make sure that the Oracle TNS Listenerservice (for example, OracleOraDb11g_home1TNSListener) is set to Startedin the Windows Services utility.

If the Oracle Listener is not running, you need to manually restart the Listener usingthe Linux command = lsnrctl start. The Platform Guide for Microsoft Windowsand the Administrator's Reference for Linux and UNIX-Based Operating Systemscontain more information about manually starting Oracle services.

• Troubleshooting



EMC Fails to LaunchSimphony can fail to install completely because of anti-virus software. Remove anti-virus software from all servers and reinstall Simphony. You can reinstall the anti-virussoftware after Simphony applications and databases are installed.

• Troubleshooting



Chapter 10EMC Fails to Launch

10-2



11List of Simphony Components andServices

You can install the following components and services by running the Simphonyinstallation application.

Table 11-1 List of Application and Database Services

Component Description

Data Transfer Service Moves point of sale (POS) definitions and journal data toReporting and Analytics. This is typically installed on eachSimphony application server.

Direct Posting Service Posts sales data to the Simphony Reports database. Thisis typically installed on each Simphony application server.

EMC Client Contains all files necessary to run the EnterpriseManagement Console (EMC).

Open Source This is typically installed on each Simphony applicationserver.

Sequencer Service Responsible for running the Start of Day Autosequences.This is typically installed on each Simphony applicationserver, but is only enabled on one server.

Tools Installs the tools required for import/export, encryption,and so on. This is typically installed on each Simphonyapplication server.

Data Request Processing Service Installs the Import Export Web API and the WebApplication Data Request Processing Service. This istypically installed on each Simphony application server.

The Web Application Data Request Processing Serviceprocesses Simphony Data Import/ Export requests andscheduled Import/ Export requests.


Related Topics







11-1








Related Topics




Chapter 11

11-2

12List of Simphony Database ConfigurationFields

The following table describes the fields that appear on the Simphony installationapplication when configuring the Simphony databases.

Table 12-1 List of Database Configuration Fields

Field Description

Service Name If you are using an Oracle database, enter a service name onwhich to install the Simphony database.

Instance Name If you created a named instanced to install Simphony onMicrosoft SQL Server, enter the instance name.

Username Enter a strong username for the database.

Password Enter a strong password for the user defined in the Usernamefield to use to connect to the database.

Database Name Enter a name for the database if you want to use a name otherthan the default. This field only appears if you select MicrosoftSQL as your database type.

Database Port To use a port other than the default, enter the port number touse to connect to the database.


Related Topics









12-1






Chapter 12

12-2

13Appendix A: Sample Script for CreatingOracle Tablespaces

DECLARE

cursor mcrspos_tablespace_check is select tablespace_name from dba_tablespaces where tablespace_name = 'MCRSPOS';v_tablespace varchar2(40);v_path VARCHAR2(100);sql_stmt VARCHAR2(10000);

BEGIN

open mcrspos_tablespace_check;fetch mcrspos_tablespace_check into v_tablespace; if mcrspos_tablespace_check%NOTFOUND then SELECT substr(file_name, 1,((INSTR(file_name,'\', -1, 1)))) into v_path from dba_data_files where rownum < 2; sql_stmt := 'CREATE TABLESPACE MCRSPOS LOGGING DATAFILE '||''''|| v_path||'mcrspos01.dbf'||''''||' SIZE 512M AUTOEXTEND ON NEXT 128M MAXSIZE UNLIMITED EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO'; execute immediate sql_stmt; end if;close mcrspos_tablespace_check;END;/

DECLARE

cursor MCRSCACHE_tablespace_check is select tablespace_name from dba_tablespaces where tablespace_name = 'MCRSCACHE';v_tablespace varchar2(40);v_path VARCHAR2(100);sql_stmt VARCHAR2(10000);

BEGIN

open MCRSCACHE_tablespace_check;fetch MCRSCACHE_tablespace_check into v_tablespace; if MCRSCACHE_tablespace_check%NOTFOUND then SELECT substr(file_name, 1,((INSTR(file_name,'\', -1, 1)))) into v_path from dba_data_files where rownum < 2;

13-1

sql_stmt := 'CREATE TABLESPACE MCRSCACHE LOGGING DATAFILE '||''''|| v_path||'MCRSCACHE01.dbf'||''''||' SIZE 128M AUTOEXTEND ON NEXT 128M MAXSIZE UNLIMITED EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO'; execute immediate sql_stmt; end if;close MCRSCACHE_tablespace_check;END;/

Related Topics









Chapter 13

13-2

14Appendix B: Post-Installation BestPractices

• Creating Database Backups

• Changing the Application Server’s Name

• Changing the Database Server Name



Related Topics


Creating Database BackupsCreate backups of the Simphony database periodically to ensure that you do notencounter potential data loss due to unforeseen circumstances.

The Database Backup and Recovery User Guide contains more information aboutcreating database backups using the Oracle Recovery Manager. For instructions oncreating database backups in Microsoft SQL Server, refer to the Microsoft DocsLibrary at https://docs.microsoft.com/en-us/ for more information.

• Appendix B: Post-Installation Best Practices


Related Topics


Changing the Application Server’s NameIf you change the Server Host Name of your Simphony application server, completethe following updates on the application server.

1. Find and replace the default ServerName in the following host files with the newServerName. The default ServerName is associated with the IP addresslocalhost.

Table 14-1 Host Files

Path and Filename Variable

C:\Windows\System32\drivers\etc\hosts

HostIPAddress ServerName

The HostIPAddress is typically set tolocalhost.

14-1

https://docs.microsoft.com/en-us/sql/relational-databases/backup-restore/back-up-and-restore-of-sql-server-databases

Table 14-1 (Cont.) Host Files


C:\Windows\System32\drivers\etc\lmhosts

HostIPAddress ServerName

The HostIPAddress is typically set tolocalhost.

2. If you are using an Oracle database, find and replace the default ServerName inthe following Oracle files with the new ServerName.

Table 14-2 Oracle Database Files


[Drive]:\Oracle\product\version\dbhome_1\ NETWORK\ADMIN\listener.ora

HOST=ServerName

[Drive]:\Oracle\product\version\dbhome_1\ NETWORK\ADMIN\tnsnames.ora

HOST=ServerName

3. If the DNS is enabled on the network, find and replace the default ServerName inthe following Simphony and Reporting and Analytics files with the newServerName. If DNS is not enabled, enter the server’s IP address.

Table 14-3 Simphony Services and Reporting and Analytics Files


[Drive]:\Micros\Simphony2\EgatewayService\DbSettings.xml

Set the ServerName for all dataSourceentries.

[Drive]:\Micros\Simphony2\EgatewayService\Web.config

Set the ServerName in the <appsettings>elements for:• SimphonyCAL DiscoveryURL• BatchServiceURL• EGatewayURL• BatchServiceURL_1x• KdsCheckAndPosting• ServiceHost

[Drive]:\Micros\Simphony2\DirectPostingService\DirectPostingService.exe.config

Set the ServerName on theEGatewayURL line.

[Drive]:\Micros\Simphony2\SequencerService\SequencerService.exe.config

Set the ServerName on the EGatewayUrlline.

[Drive]:\Micros\Simphony2\DataTransferService\ mmserver\postingServer.properties

Set the ServerName on all URL lines.

Chapter 14Changing the Application Server’s Name

14-2

Table 14-3 (Cont.) Simphony Services and Reporting and Analytics Files


[Drive]:\Micros\MyMicros\myPortal\microsConfig.properties

Set the ServerName on all db.server*lines.

[Drive]:\Micros\MyMicros\infoDelivery\Db.xml

Set the ServerName on all db.server*lines.

4. Restart IIS and the MyMicros Portal service (or restart the computer for newinstalls).

5. If you are using Microsoft Windows 32 (Win32) devices:

a. Find and replace the default ServerName in the following file:

Table 14-4 Simphony Install


[Drive]:\Micros\Install\SimphonyInstall.xml

Set the ServerName on all<ServerName> and <SvcHostName>

b. In the EMC, select the Enterprise level, click Setup, and then click CALPackages.

c. Click the Package Contents tab, and then select the appropriate ServiceHost.

d. Click Win32 under the Platforms header.

e. Click Reload Package From Disk to upload the Win32 CAL package to thedatabase.

f. When prompted for the CAL package location, enter [Drive]:\Micros\Simphony2\EgatewayService\CAL\Win32\Packages\ServiceHost2.0, and then click OK.

Related Topics




Changing the Database Server NameChanging an Oracle Database Server’s Name

Refer to http://docs.oracle.com for more information about renaming your OracleDatabase server.

Changing a Microsoft SQL Server’s Computer Name

Refer to https://msdn.microsoft.com/en-us/library for more information about renamingyour Microsoft SQL Server computer.

Chapter 14Changing the Database Server Name

14-3

https://docs.oracle.com/middleware/1212/core/ASADM/host.htm#ASADM313

https://msdn.microsoft.com/en-us/library/ms143799.aspx



Related Topics


Chapter 14Changing the Database Server Name

14-4

installation guide oracle hospitality simphony · step 2 - access the iis manager console 7-13 step...

Documents