Post-Installation or Upgrade Guide - Oracle · 4 Updating Property Administrator and Database Logon Credentials Configuring Different Credentials for Each Property 4-1 Configuring

Oracle® Hospitality SimphonyPost-Installation or Upgrade Guide

Release 18.2F12086-04December 2019

Oracle Hospitality Simphony Post-Installation or Upgrade Guide, Release 18.2

F12086-04

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 Upgrading Simphony

Upgrading to Simphony Release 18.2 1-1

Simphony Upgrade Procedures 1-2

Upgrades When Adding a New Database Server 1-3

Upgrades without Separate Transaction and Security Database Servers 1-6

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

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

Step 1 - Close and Post All Transactions 1-10

Step 2 - Access the IIS Manager Console 1-10

Step 3 - Rename the IIS Folder 1-12

Step 4 - Enable an Option and Configure CAPS 1-13

Step 5 - Stop IIS 1-14

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

Step 7- Start IIS 1-15

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

2 Post-Installation Tasks

Updating the Property EMC Client 2-1

Updating Check and Posting Service Clients 2-1

Updating CAL Packages 2-1

Enabling Communication Between the Enterprise and Workstations 2-1

3 EMC Access Security

Accessing the Simphony EMC Using Multi-Factor Authentication 3-1

Configuring the SMTP and Backup SMTP Servers in the EMC 3-1

Configuring and Resetting Email Addresses 3-3

Forgotten EMC Password Recovery 3-3

Configuring Access Privileges for Resetting a Password 3-5

iii

Resetting Passwords from the Simphony Web Portal 3-6

Setting the Max Allowed Failed Logins for EMC Access 3-8

4 Updating Property Administrator and Database Logon Credentials

Configuring Different Credentials for Each Property 4-1

Configuring the Same Credentials for All Properties in the Enterprise 4-2

iv

Preface

This guide is for Simphony Cloud Services users and provides post-installation stepsto perform after a fresh installation or upgrade to the Simphony 18.2 release.Beginning with the Simphony 2.9 release or later, users must install Reporting andAnalytics (R&A) separately from Simphony using the Back Office R&A installationapplication. For upgrades from releases prior to Simphony 2.9, users must upgrade toReporting and Analytics release 8.5.1 Patch 3 before installing or upgrading toSimphony release 2.9. Simphony release 18.2 is compatible with R&A releases 8.5.1Patch 3 (for all-in-one installations), 9.0 Patch 8, and 9.1.

Audience

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

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

The Simphony Installation Guide contains more information about performinginstallations and upgrades to Simphony.

Product documentation is available on the Oracle Help Center at https://docs.oracle.com/en/industries/food-beverage/pos.html.

Revision History

Date Description of Change

December 2018 Initial publication

v

https://support.oracle.com

https://docs.oracle.com/en/industries/food-beverage/pos.html

https://docs.oracle.com/en/industries/food-beverage/pos.html

Date Description of Change

May 2019 • Removed the following sections fromChapter 2:

– Updating Simphony License Counts– Post Install Steps for Engagement on

Load Balanced Simphony Servers• Added Chapter 3: EMC Access Security• Updated the Upgrading to Simphony

Release 18.2 topic.

December 2019 Updated the Upgrading to Simphony Release18.2 topic by including the workaround to addtheSQLNET.INBOUND_CONNECT_TIMEOUT=120 parameter.

Preface

vi

1Upgrading Simphony

The information on this page provides instructions on how to perform an upgrade toyour Simphony system.

• Upgrading to Simphony Release 18.2

• Simphony Upgrade Procedures

• Upgrades When Adding a New Database Server

• Upgrades without Separate Transaction and Security Database Servers

• Upgrades with Existing Separated Transaction and Security Database Servers

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

Upgrading to Simphony Release 18.2Simphony version 18.2 performs an upgrade from Simphony version 2.9 or later. Toenhance your system’s security, during upgrades, 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 strongly recommends storing these databases onseparate database servers. The following sections review three possible upgradescenarios:

• Upgrades When Adding a New Database Server

• Upgrades without Separate Transaction and Security Database Servers

• Upgrades with Existing Separated Transaction and Security Database Servers

When upgrading in certain environments, you may experience the error ORA-25408,which is an Oracle Client related issue outside of Simphony. This condition is causedby environmental network timeouts being reached. To work around this issue, add theparameter SQLNET.INBOUND_CONNECT_TIMEOUT=120 to the Sqlnet.ora file on thedatabase server.

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

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

3. Run the Setup, and then click Next.

If the application and the database are on separate servers, run the installationapplication 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.

1-1

http://www.oracle.com/pls/topic/lookup?ctx=F10429-01&id=Pre-InstallationTasks-86CE214D

https://edelivery.oracle.com

Beginning with the Simphony 2.10 release and later, you can upgrade applicationcomponents on servers with or without downloading CAL Packages to theSimphony database. This flexibility can speed up the upgrade process onproperties using multiple application servers.

Figure 1-1 Simphony Components Installation Options

Simphony Upgrade Procedures1. Ensure that the Simphony application and database servers meet the

requirements listed in the Oracle Hospitality Simphony Installation Guide,specifically the Pre-Installation Tasks section.

2. Log in and download the Simphony 18.2 release installation application from theOracle Technology Network (OTN) Web site 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 using 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 1Simphony Upgrade Procedures

1-2

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.

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 use an existing certificate, select Existing, and then select the installedcertificate from the drop-down list.

d. Enter the Service Host Secure Port.

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. To add IIS Bindings, refer to Binding Secure Server Certificates to IISand the Microsoft TechNet Library at https://technet.microsoft.com/en-us/ formore information.

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

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

10. Click Yes to restart the server.

Upgrades When Adding a New Database ServerThis section provides upgrade instructions to enhance your system security by addinga new database server to house the security database. If you are using multipleSimphony application servers, upgrade the initial application server to Simphonyrelease 18.2. After upgrading subsequent application servers, ensure that on eachapplication server the security database server name matches the dataSource entryfor the CACHE host name located in the application server’s DBSettings.xml. This fileis located on the initial Simphony application server that was upgraded. For example:

alias="Cache"

dbType="<TYPE> "

dataSource="<SERVERNAME>"

To initiate this type of upgrade:

1. Perform Steps 1 through 5 in Simphony Upgrade Procedures.

2. Certificate Location: Throughout the Simphony 18.2 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.


Chapter 1Upgrades When Adding a New Database Server

1-3

http://www.oracle.com/pls/topic/lookup?ctx=F10429-01&id=BindingSSLCertificatesToInternetInf-A2BF8396

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

d. If you are using a Load Balancer server and using the Import/Export Service orplan 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.

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 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 match the server name where the Transactiondatabase is stored, the installation application prompts and affords users theopportunity to separate the databases onto different database servers. Becauseyou 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 name

should match the dataSource entry for the CACHE host name located in theapplication server’s DBSettings.xml. For example:

alias="Cache"

dbType="<TYPE> "


1-4



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, you must go to thesecondary database server and manually create the folders specified in theRemote Database Location field. Alternatively, you 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.

Figure 1-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:

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


1-5

http://www.oracle.com/pls/topic/lookup?ctx=F10429-01&id=Pre-InstallationTasks-86CE214D



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 reporting database.

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

h. Password: Enter your reporting database access password, and then clickNext.

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.

Upgrades without Separate Transaction and SecurityDatabase Servers

This section provides upgrade instructions for sites 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 through 5 as in Simphony Upgrade Procedures.

2. Certificate Location: Throughout the Simphony 18.2 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:


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



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

Chapter 1Upgrades without Separate Transaction and Security Database Servers

1-6

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.




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 (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:

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





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


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 reporting database.

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

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


Chapter 1Upgrades without Separate Transaction and Security Database Servers

1-7




Upgrades with Existing Separated Transaction and SecurityDatabase Servers

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

1. Perform steps 1-5 as shown in Simphony Upgrade Procedures.

2. Certificate Location - Throughout the Simphony 18.2 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:


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.


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.


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


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.

Chapter 1Upgrades with Existing Separated Transaction and Security Database Servers

1-8

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:

a. Server Name - Enter the name of the security 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 then click Next.


a. Server Name - Enter the name of the reporting 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 (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.

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





Chapter 1Upgrades with Existing Separated Transaction and Security Database Servers

1-9

Note:

If multiple Simphony application servers are utilized, upgrade the initialapplication server to Simphony release 18.2. After upgrading subsequentapplication servers, ensure that on each application server the securitydatabase server name matches the dataSource entry for the CACHEhost name located in the application server’s DBSettings.xml. This file islocated on the initial Simphony application server that was upgraded. Forexample:

alias="Cache"

dbType="<TYPE"


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 releases 2.10, 18.1, or 18.2.

No additional post-upgrade steps are necessary for CAPS on Microsoft InternetInformation Services (IIS) if you upgrade from Simphony releases later than Simphony2.9 GR (for example, Simphony 2.10, 18.1, or 18.2).

• 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

Step 1 - Close and Post All TransactionsEnsure that all transactions for the property are closed and posted to the Enterpriseprior to performing the Simphony upgrade.

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 should

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

1-10

be the same as the ServiceHostName. For example, if your service host name isMyIISCapsSvcHost, your site name should be added using the exact same text.

Figure 1-3 IIS CAPS Site

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

Figure 1-4 Simphony Application Pools


1-11

4. Right-click the application pool created for IIS CAPS and select Remove. Thename of the IIS CAPS pool should be the ServiceHostName Pool. For example, ifyour service host name is MyIISCapsSvcHost, your IIS CAPS application poolname should be MyIISCapsSvcHostPool.

Figure 1-5 IIS CAPS Application Pool

Step 3 - Rename the IIS Folder1. Rename the Simphony release 2.9 (or later) 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.

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


1-12

3. Note that the default Simphony release 2.9 (or later) IIS CAPS folder location is:[Drive]:\Simphony2\IISCAPS. Rename the IISCAPS folder toIISCAP_Backup. This step ensures that you maintain a backup of the old folder.

Figure 1-7 Default IIS CAPS Folder Installation Path

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 switch to Form view.

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

4. In the Miscellaneous Options section, enable 10065 - Download Software, Installand Authenticate Clients and Service Hosts Using CAL, and then click Save.

5. If you are configuring CAPS on IIS at the Simphony application server, you canaccess the CAPS Configurator Tool using this path: [Drive]:\MICROS\Simphony2\Tools\CAPSConfigurator\ CAPSConfigurator.exe. If you areinstalling CAPS on IIS on a remote workstation or virtual machine, install CAL onthat device, and through CAL, deploy a package called CAPSOnIIS to the device.When the software is on the device, navigate to [Drive]:\MICROS\Simphony\CAPSOnIIS\Tools\CAPSConfigurator\ and double-click theCAPSConfigurator.exe file.

6. Log on to the CAPS Configurator Tool, and freshly configure CAPS with thedefault configuration settings by clicking the Configure CAPS button.


1-13

Figure 1-8 CAPS Configurator Tool

7. Upon successful installation, verify that the new directory is created along the[Drive]:\Simphony2\EgatewayService\IISCAPSServiceHost path.

Step 5 - Stop IISTo stop IIS:

1. Run the command window with administrator privileges.

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

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 in 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:

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


1-14

Step 7- Start IISTo start IIS:

1. Run the command window with administrator privileges.

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

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 release 2.9 CAPS directory (for example, theIISCAP_Backup directory). See Step 3 - Rename the IIS Folder for details.


1-15

2Post-Installation Tasks

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

• Updating the Property EMC Client

• Updating Check and Posting Service Clients

• Updating CAL Packages

• Enabling Communication Between the Enterprise and Workstations

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 enable 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.

Updating Check and Posting Service ClientsUpdate all Check and Posting Service (CAPS) clients prior to updating workstationswith the latest CAL Packages. The Simphony Client Deployment Guide contains moreinformation about configuring and deploying CAL Packages.

Updating CAL PackagesOracle Hospitality recommends that you consider updating your POS clients using thelatest available CAL Packages. To accomplish this, verify the CAL Package contentsand then configure and execute a CAL Package Deployment Schedule. The SimphonyClient Deployment Guide contains more information about configuring and deployingCAL Packages.

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 Simphonyrelease 18.2:

2-1

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

• 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 2Enabling Communication Between the Enterprise and Workstations

2-2

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

3EMC Access Security

Enterprise Management Console (EMC) access security has been enhanced with thesupport of Multi-Factor Authentication (MFA). This chapter reviews enablingconfiguring the system’s EMC security settings including information about configuringemployee passwords and email addresses.

• Accessing the Simphony EMC Using Multi-Factor Authentication

• Configuring the SMTP and Backup SMTP Servers in the EMC

• Configuring and Resetting Email Addresses

• Forgotten EMC Password Recovery

• Setting the Max Allowed Failed Logins for EMC Access

Accessing the Simphony EMC Using Multi-FactorAuthentication

To use Multi-Factor Authentication (MFA) on your Simphony system, you need to addand register your email address.

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

2. Re-enter your email address in the Confirm Email Address field, and then clickRegister.

This email address is used to send you a one-time password (OTP). Yourregistered email address is written to your employee record in the newly addedEmail field.

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

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

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

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:

3-1

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 3-1 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 (IPv4 Address) or the name of the PrimarySMTP server. Click the Select button to choose an email provider, and thenclick OK. When you select an email provider, the Server field auto-populateswith an SMTP server name that includes the selected email provider’s namingconvention (for example, SMTP.EMAIL.COM).

b. Port: Enter a port number or use 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.

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

3-2

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.

Figure 3-2 Employee Email Address Configuration

4. If a user’s email address changes:

a. Click the Email button.

b. Enter the user’s Current Email Address (that is already registered on thesystem), new Email Address, and then re-enter the address in the ConfirmEmail Address field.

c. Click Register.

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

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 in

Chapter 3Configuring and Resetting Email Addresses

3-3

resetting 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).

Figure 3-3 EMC Login Can’t Sign In?

• Configuring Access Privileges for Resetting a Password

• Resetting Passwords from the Simphony Web Portal

Chapter 3Forgotten EMC Password Recovery

3-4

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 3-4 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.


3-5

Figure 3-5 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.

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.

Figure 3-6 Simphony Web Portal Logon Screen’s Can’t Sign In? Link


3-6

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

Figure 3-7 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

• 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.


3-7

Figure 3-8 Simphony Web Portal (SWP) User Profile Screen

If you do not meet the following prerequisites, you must request to have aprivileged supervisor initiate recovery of your password:

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

• You have not configured your security questions and answers

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

1. Select the Enterprise, click Setup, and then click Enterprise Parameters.

2. Click the Login tab.

3. In the Options section, enter 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 3Setting the Max Allowed Failed Logins for EMC Access

3-8

4Updating Property Administrator andDatabase Logon Credentials

When logging on to the EMC for the first time after installing or upgrading to Simphonyrelease 18.2, 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.

• 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

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.

4. Click the Security tab, and then enter the User Security Credentials. Simphonyrelease 18.2 uses 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.

Review the Simphony Installation Guide specifically, the Database UserPasswords section which contains more information about passwordrequirements.

4-1

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.

If you are using Simphony release 2.9.1 or later (including the Simphony 18.2release), the steps outlined above have changed in reference to allowing you touse your EMC logon credentials to perform downloads, upgrades, andauthentications using the Client Application Loader (CAL) on service hosts andworkstations.

See the Oracle Hospitality Simphony Configuration Guide, specifically, theEmployees and Privileges chapter, for more information about configuringemployees and their access privileges.

To allow users to use their EMC logon credentials to access and update servicehosts and workstations:

• Access the EMC and select the Enterprise level, Configuration tab, and thenclick Roles.

• Select the Operations tab, click the Miscellaneous tab, and then within theMiscellaneous Options section, enable the 10065 – Download Software,Install and Authenticate Clients and Service Hosts Using CAL option.

• Click Save.

• Repeat these steps for each employee role you wish to assign this privilege.

Configuring the Same Credentials for All Properties in theEnterprise

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

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.

Chapter 4Configuring the Same Credentials for All Properties in the Enterprise

4-2

Documents

Post-Installation or Upgrade Guide - Oracle · 4 Updating Property Administrator and Database Logon Credentials Configuring Different Credentials for Each Property 4-1 Configuring