Opera Install Binder

Oracle Hospitality
OPERA 5.0.5.xx Single Server

Installation
Release 1.0
October 2015
Note: The following is intended to outline our general
product direction. It is intended for information purposes

only, and may not be incorporated into any contract. It is not
a commitment to deliver any material, code, or functionality,
and should not be relied upon in making purchasing
decisions. The development, release, and timing of any
features or functionality described for Oracles products
remains at the sole discretion of Oracle.
Contents
Contents ............................................................................................................................. ii
Record of changes ............................................................................................................ 1
Single Server Installation ................................................................................................. 2
Single Server Installation Steps .............................................................................................2
Record of changes
Date
Document
Version
Description
Author
March 2015
1.0
Initial document, replacement for

1473 - Opera v5.0.x NT- Single
Server Install
Richard Schulze
October 2015
1.1
New format, miscellaneous
Richard Schulze
Please sent comments on this document to richard.schulze@oracle.com
Record of changes 1
Single Server Installation Steps
Single Server Installation

Single Server Installation Steps
OPERA Single Server media will no longer be provided as separate installation media.
In order to install a single server environment, the OPERA database software should be
installed, followed by the installation of the OPERA 11g Forms Application server.
Please follow the steps in documents OPERA 5.0.5.xx Database Server Installation and
OPERA 5.0.5.xx Forms 11g Application Server Installation.
Because the 11g Forms Application server needs a valid connection to the OPERA
database during the installation, it is important that the database installation gets
completed first.
Please note that it takes a considerable amount of time for the database and middleware
stacks to startup completely. Please allow for enough time for all components to
completely come up before accessing the application.
2 Confidential Oracle Internal
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores, CA 94065
U.S.A.
Worldwide Inquiries:
Phone: +1.650.506.7000
Fax: +1.650.506.7200
oracle.com
Copyright 2015, Oracle. All rights reserved.
All rights reserved. This document is provided for information purposes only, and the contents hereof are subject to change without notice. This document is not warranted to
be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or
fitness for a particular purpose. We specifically disclaim any liability with respect to this document, and no contractual obligations are formed either directly or indirectly by
this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written
permission.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of
SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered
trademark of The Open Group.
Oracle Hospitality
OPERA 5.0.5.xx Database Server
Installation
Release 1.0
October 2015

Contents
Contents ............................................................................................................................. ii
Introduction ....................................................................................................................... 2
Intended Audience ............................................................................................................ 2
Prerequisites ..................................................................................................................... 2
Disk Layout ........................................................................................................................ 3
Changes required to a standard Windows installation ................................................. 4
Disable Windows DEP ...........................................................................................................4
Disable IPv6 .............................................................................................................................4
Disable User Account Control (UAC). .................................................................................5
Modify the Elevation Prompt Behavior (only if UAC has not been disabled) ........5
Modify Admin Approval Mode (only if UAC has not been disabled).....................6
Disabling the Windows Firewall ..........................................................................................7
Reboot the server.....................................................................................................................9
OPERA 5 Database Server Installation ......................................................................... 10
Post Installation Steps ................................................................................................... 16
Installation logs ..................................................................................................................... 16
Initopera.ora changes ........................................................................................................... 16
Database backups.................................................................................................................. 16
Enabling archivelog mode ................................................................................................... 17
Record of changes
Date
Document
Version
Description
Author
March 2015
1.0
Initial document, replacement for

1472 - Opera v5.0.x NTDatabase Server Install
Richard Schulze
October 2015
1.1
New format, miscellaneous
Richard Schulze
Record of changes 1
Disable Windows DEP
Introduction
With the release of the media for Service Pack 5.0.05.00 of OPERA, the Oracle database
version on the media has been upgraded to 11.2.0.4.18.
For existing installations, the use of Oracle 11.2.0.4.18 is not mandatory for the use of
OPERA 5.0.05.00. Please consult the OPERA Supported Platforms document for
Platform / OPERA version requirements.
This document describes how to install an OPERA database server using the provided
installation media.
The installation has been documented on a Microsoft Windows Server 2008 R2 Standard
operating system.
OPERA Single Server media will no longer be provided as separate installation
media. In order to install a single server environment, please follow the document
OPERA 5.0.5.xx Single Server Installation.
Intended Audience
This document is intended for Oracle staff that is familiar with the Windows Server 2008
R2 OS, OPERA components, Oracle RDBMS and network environments, charged to
install OPERA database servers on SP 5.0.05.00 or higher.
Prerequisites
Obtain the latest OPERA 11g Database Server installation media and copy or extract it to
the root of the target machines D: drive. Do not run the installation from a dvd / usb
drive or from a network location.
It is assumed that the Windows Server 2008 R2 software has been correctly installed.
The document 1535 - Recommended Windows 2008R2 Configuration Changes for
OPERA servers that can be found on the MICROS members website contains
recommended changes to the Operating System after the initial installation.
Although some changes in that document are optional, the ones listed in the next
paragraph have to be made before the installation is attempted.
Disable Windows DEP
Disk Layout
The following is the required disk layout for an OPERA 5 database installation on
Windows platforms.
It is HIGHLY recommended that RAID 1 or RAID 0+1 be used for all drives containing
OPERA database files.
The Opera 5 standard database installation requires anywhere from one to seven logical
drives (C, D, G-K), depending on what is available. The E drive is assumed to be the CDROM. There are six installation options based on how the disk drives and drive letters
are laid out. The following are the minimum required sizing for installation only, this is
not production sizing. The following is the amount of free space the drives should have
before installing Opera.
Installation options:
1. C(4GB), D(4GB), G(4GB), H(4GB), I(4GB), J(4GB), K(4GB)
2. C(4GB), D(4GB), G(4GB), H(8GB), I(8GB)
3. C(4GB), D(8GB), G(8GB), H(8GB)
4. C(4GB), D(12GB), G(12GB)
5. C(4GB), D(24GB)
6. C(28GB)
NOTE: If these minimum sizing requirements are not provided the installation will not
proceed.
Disk Layout 3
Disable Windows DEP
Changes required to a standard Windows

installation
Disable Windows DEP
Open a new elevated command prompt (Run as administrator) and type the following
command:
bcdedit.exe /set {current} nx AlwaysOff
Disable IPv6
IPv6 is not supported on OPERA servers. In order to disable it, open an elevated
command prompt (Run as administrator) and type the following command:
reg add hklm\system\currentcontrolset\services\tcpip6\parameters /v
DisabledComponents /t REG_DWORD /d 2
Confirm if you are prompted to overwrite the current value.
Disable User Account Control (UAC).

If possible disable UAC during the installation by running the following command from
an elevated command prompt (Run as administrator):
C:\Windows\System32\cmd.exe /k %windir%\System32\reg.exe ADD
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v
EnableLUA /t REG_DWORD /d 0 /f
If UAC cannot be disabled during the installation, at a minimum the following has
to be performed:
Modify the Elevation Prompt Behavior (only if UAC has not been disabled)
The elevation prompt behavior for administrators needs to be changed to "Elevate
without prompting":
Open a command prompt and type secpol.msc to launch the Security Policy Console
management utility. From the Local Security Settings console tree, click Local Policies,
and then Security Options.
Scroll down to and double-click User Account Control: Behavior of the elevation prompt
for administrators.
Changes required to a standard Windows installation 5
From the drop-down menu, select: "Elevate without prompting (tasks requesting
elevation will automatically run as elevated without prompting the administrator)".
Click OK to confirm the changes.
Modify Admin Approval Mode (only if UAC has not been disabled)
Scroll down to and double-click User Account Control: Run all administrators in Admin
Approval Mode.
Select Disabled.
Disabling the Windows Firewall

Windows 2008 has firewall safety settings for different profiles. The firewall needs to be
disabled for each profile individually.
In order to verify if the Firewall is enable, go to Start > Control Panel > Check Firewall
Status
If the Firewall is enabled, select Turn Windows Firewall on or off.
Turn it off for all profiles.
It may still be enabled for the other profiles (see below).
In order to change the firewall settings for all profiles, right click my computer and select
Manage. On the Server management page, scroll to the Configuration > Windows
Firewall with Advanced Security.
Select the Windows Firewall Properties link and turn the firewall off for each profile by
clicking on the different tabs.
Reboot the server.
The result is shown below.
Reboot the server.

At this point, the server needs to be rebooted.
Reboot the server.
OPERA 5 Database Server Installation
Navigate into the DVD2 folder and launch OperaInstallation.EXE.
The wizard will collect some installation variables. Click Next.
Acknowledge the actions the wizard will take. Click Next.
Reboot the server.
Enter the credentials for the SYS and SYSTEM users that you want to use.
Enter the credentials for the SYSMAN and DBSNMP users that you want to use.
OPERA 5 Database Server Installation 11
Reboot the server.
Enter the credentials for the OPERA, OXI and OXIHUB users that you want to
use.
The media will look for the D Drive by Default and if the D Drive does not have
enough disk space the media will show below additional screens.
Reboot the server.
If the User selected Drive is low on Disk space, the wizard will prompt with the
below screen giving the ability for the user to Ignore the disk space. Use
caution when selecting Ignore as there is a great possibility that the installer will
fail during installation.
The wizard will give the option to cancel the installation at this time. This
additional screen will popup if the user selected Ignore for Disk space warning.
Reboot the server.
Disk drive layout. Carefully review the selected drives for installation and that
they are the desired layout for this installation. Click Next if correct. Click
Cancel if changes to the drive layout are required.
The installation will commence.
When the database software installation is finished, the data files are being
extracted.
Reboot the server.
After a while, the DBConsole will be configured. The message regarding the
email address can be ignored.
The installation finishes.
Installation logs
Post Installation Steps

Review the following notes to customize the database parameters and then reboot the
database server.
Installation logs
Installation logs are located in the system tmp directory, if there is no tmp directory it
will write to the temp directory. Right click my computer, properties, advanced tab,
environment variables to find the tmp location. Example:
c:\temp\opera40\DatabaseInstall.log and CopyDBfiles_Install.log.
Initopera.ora changes
Even standard installations require some manual steps to be completed. The person
installing the database server should adjust the size of the SGA as needed (initopera.ora).
To adjust the size of the SGA, edit the d:\oracle\admin\opera\pfile\initopera.ora file.
Go to the end of the file. Select the memory configuration that fits the new environment
by uncommenting (i.e remove # in front of shared_pool_size and db_cache_size) the
two parameter values associated with the size of installation and commenting out
(i.e.insert # in front of shared_pool_size and db_cache_size) the two parameter values
associated with 20 Concurrent users. The database must be restarted to pick up the
new values.
Database backups
After the initial installation there are no backups configured for the OPERA database.
Please make sure that an adequate backup strategy is put in place before the site starts
configuring the application. In order to take hot backups, the database needs to be put in
archivelog mode.
Enabling archivelog mode
Enabling archivelog mode

After the installation completes, the database is not in ARCHIVELOG MODE.
Enable archive log mode:
Shut down the database.
Check the parameters in the initopera.ora file. They should look like the below:
###########################################
# Archive
###########################################
log_archive_dest_1='LOCATION=d:\oracle\admin\opera\archive mandatory REOPEN=120'
log_archive_format=ARC%S_%R.%T
Mount the database in sqlplus.
Enable archive logging and open the database.
Post Installation Steps 17
Oracle Corporation
World Headquarters
500 Oracle Parkway
U.S.A.
Phone: +1.650.506.7000
Fax: +1.650.506.7200
oracle.com
permission.
Oracle Hospitality
OPERA 5.0.5.xx Forms 11g
Application Server Installation
Release 2.0
October 2015

Contents
Contents ............................................................................................................................. ii
Introduction ....................................................................................................................... 2
Intended Audience ............................................................................................................ 2
Prerequisites ..................................................................................................................... 2
Certificates and Java keystores ...................................................................................... 3
Changes required to a standard Windows installation ................................................. 3
Disable Windows DEP ...........................................................................................................3
Disable IPv6 .............................................................................................................................4
Disable User Account Control (UAC). .................................................................................4
Modify the Elevation Prompt Behavior (only if UAC has not been disabled) ........5
Modify Admin Approval Mode (only if UAC has not been disabled).....................6
Disabling the Windows Firewall ..........................................................................................6
Microsoft Visual C++ 2008 Redistributable .........................................................................9
Reboot the server.....................................................................................................................9
OPERA 5 Forms 11g Application Server Installation .................................................. 10
Important Note regarding re-using certificates in a clustered installation ............... 22
External Certificates .............................................................................................................. 22
Internal Certificates ............................................................................................................... 22
Compile stationary RDF files ......................................................................................... 23
Checklist for 10g to 11g OPERA Application Server migration ................................. 24
Support for National Character Sets ............................................................................. 25
Keystores and wallets on an 11g OPERA Application Server ................................... 26
Pre-Creating Certificate Requests for 11g OPERA 5 Application Servers................ 27
Creating the Certificate Request ......................................................................................... 27
Using the Certificate during the Application Server Installation ................................... 28
Updating an 11g OPERA application server with new certificates ............................ 30
Additional Information .................................................................................................... 34
Record of changes
Date
Document
Version
Description
Author
October 2014
1.0
Initial document
Richard Schulze
January 2015
1.1
Changes for localhost
Richard Schulze
February 2015
1.2
MS VC++ 2008 addition,

miscellaneous
Richard Schulze
July 2015
1.3
Migration steps, miscellaneous
Johan Gartzell /
Richard Schulze
October 2015
2.0
New format, document

consolidation, miscellaneous
Johan Gartzell /
Richard Schulze
Record of changes 1
Disable Windows DEP
Introduction
With the release of Service Pack 5.0.04.03 of OPERA, the introduction of Oracle 11g
Forms and Reports 11.1.2.2 is necessary.
This document describes how to install an OPERA application server using the provided
installation media. The media can be obtained through your Regional Office. The
installation has been documented on a Microsoft Windows Server 2008 R2 Standard
operating system.
The installation wizard will prompt for a password to be provided for WebLogic
administrative accounts.
Valid passwords are 8 to 30 characters long, must begin with an alphabetic character,
use only alphanumeric, underscore (_), dollar ($) or pound (#) characters. It should
contain at least one numeric, underscore (_), dollar ($), or pound (#) character.
Intended Audience
This document is intended for Oracle staff that is familiar with the Windows Server 2008
R2 OS, OPERA components, Oracle WebLogic Server and network environments,
charged to install OPERA application servers on SP 5.0.05.00 or higher.
Prerequisites
Obtain the latest OPERA 11g Application Server installation media and copy or extract it
to the root of the target machines D: drive. Do not run the installation from a dvd / usb
drive or from a network location.
It is assumed that the Windows Server 2008 R2 software has been correctly installed.
The document 1535 - Recommended Windows 2008R2 Configuration Changes for
OPERA servers that can be found on the MICROS members website contains
recommended changes to the Operating System after the initial installation.
Although some changes in that document are optional, the ones listed in the next
paragraph have to be made before the installation is attempted.
ATTENTION: In contrary to the 10g application server installation, a connection to a
database is needed when the 11g application server is being installed in order to
correctly create the datasources.
Disable Windows DEP
Certificates and Java keystores

During the installation the wizard will create a certificate request and halt. At that point,
a valid certificate needs to be obtained so it can be imported in the keystore.
Because in some instances it can take a substantial amount of time to obtain a certificate
from a Certificate Authority, it is possible to create the certificate requests in advance.
Please follow the steps further in this document under the title Pre-Creating Certificate
Requests for 11g OPERA 5 Application Servers in order to create the request and apply
the certificates.
For more information regarding certificates, keystores and keytool commands, please
have a look at the document titled Keytool Self Study and the below url.
http://docs.oracle.com/javase/6/docs/technotes/tools/solaris/keytool.html
Changes required to a standard Windows

installation
Disable Windows DEP
Open a new elevated command prompt (Run as administrator) and type the following
command:
bcdedit.exe /set {current} nx AlwaysOff
Certificates and Java keystores 3
Disable IPv6
Disable IPv6
IPv6 is not supported on OPERA servers. In order to disable it, open an elevated
command prompt (Run as administrator) and type the following command:
reg add hklm\system\currentcontrolset\services\tcpip6\parameters /v
DisabledComponents /t REG_DWORD /d 2
Confirm if you are prompted to overwrite the current value.

If possible disable UAC during the installation by running the following command from
an elevated command prompt (Run as administrator):
C:\Windows\System32\cmd.exe /k %windir%\System32\reg.exe ADD
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v
EnableLUA /t REG_DWORD /d 0 /f
If UAC cannot be disabled during the installation, at a minimum the following has
to be performed:
Modify the Elevation Prompt Behavior (only if UAC has not been disabled)
The elevation prompt behavior for administrators needs to be changed to "Elevate
without prompting":
Scroll down to and double-click User Account Control: Behavior of the elevation prompt
for administrators.
From the drop-down menu, select: "Elevate without prompting (tasks requesting
elevation will automatically run as elevated without prompting the administrator)".
Click OK to confirm the changes.
Modify Admin Approval Mode (only if UAC has not been disabled)
Scroll down to and double-click User Account Control: Run all administrators in Admin
Approval Mode.
Select Disabled.

Windows 2008 has firewall safety settings for different profiles. The firewall needs to be
disabled for each profile individually.
In order to verify if the Firewall is enable, go to Start > Control Panel > Check Firewall
Status
If the Firewall is enabled, select Turn Windows Firewall on or off.
Turn it off for all profiles.
It may still be enabled for the other profiles (see below).
In order to change the firewall settings for all profiles, right click my computer and select
Manage. On the Server management page, scroll to the Configuration > Windows
Firewall with Advanced Security.
Select the Windows Firewall Properties link and turn the firewall off for each profile by
clicking on the different tabs.
Microsoft Visual C++ 2008 Redistributable
The result is shown below.
Microsoft Visual C++ 2008 Redistributable

The Microsoft Visual C++ 2008 Redistributable Package (x64) contains runtime
components of Visual C++ Libraries required to run 64-bit applications developed with
Visual C++ on a computer that does not have Visual C++ 2008 installed.
The OPERA installation wizard will install the Microsoft Visual C++ 2008 Redistributable
Package (x64) on the OPERA Application Server. You do not have to install this package
manually.
Reboot the server.

At this point, the server needs to be rebooted.
Reboot the server.
OPERA 5 Forms 11g Application Server

Installation
Navigate into the media folder and launch OPERAV5_FRM11G_Setup.EXE.
The wizard will collect some installation variables. Click Next.
Select the drive you want to install OPERA on.
Reboot the server.
The wizard will close and launch the actual installation wizard. Select Next.
Select the number of database nodes. The wizard can correctly handle up to
three database nodes. Select Next.
OPERA 5 Forms 11g Application Server Installation 11
Reboot the server.
Depending on the number pf database nodes you selected, this screen will allow
you the name for up to three database servers. Select Next.
Enter the Database name and the Service name. They often are, but do not have
to be identical. The database name can be found by querying the (g)v$database
view. The service name can be found by querying the (g)v$services view. Also
enter the listener port number and select Next.
Reboot the server.
Enter the OPERA schema credentials and select Next.
ATTENTION: In contrary to the 10g application server installation, a valid

connection to a database is needed when the 11g application server is being
installed in order to correctly create the datasources.
Enter the hostname that the wizard should create a certificate request for. This
can be the FQDN hostname, but also could be a different name if load balancers
etc. are being used. The wizard defaults to the FQDN of the server.
ATTENTION: It is very important that the correct name is being used. If you
are not 100% certain, please consult your Regional Office.
Reboot the server.
Enter the additional information.
Select if the application server will be a stand-alone application server or part of

a server farm. When selecting stand-alone, the WebLogic administrative console
can only be accessed from the desktop of the server. This increases security in a
non-datacenter environment. When Server Farm Member is selected, the
administrative console can be accessed from remote systems. This increases
manageability, but assumes a secured environment such as a datacenter. If not
sure, select stand-alone server.
Reboot the server.
Enter a password for the WebLogic administrative accounts. Make sure that the
password adheres to the below rules:
Valid passwords are 8 to 30 characters long, must begin with an alphabetic
character, use only alphanumeric, underscore (_), dollar ($) or pound (#)
characters. It should contain at least one numeric, underscore (_), dollar ($), or
pound (#) character.
When you have created the keystore and certificate requests in advance, please
make sure that this is the same password that was used when creating the
keystore, still adhering to the above password rules.
The wizard will first install the JDK 1.7
WebLogic server is being installed.
Reboot the server.
Oracle Forms and Reports is being installed.
Oracle Forms and Reports is being configured. No progress is being shown.
When the following screen appears, you need to obtain certificates that will
allow for a valid SSL configuration. The wizard will create a key store called
V5MACHINE.jks in D:\MICROS\opera\security.
Afterwards this key store will be converted into an Oracle wallet as being used
by OPERA (in D:\MICROS\wallets).
Reboot the server.
If you created the certificate requests in advance and already obtained the
certificates, please follow the steps further in this document under the title
Creating Certificate Requests for 11g OPERA 5 Application Servers in order to
apply the certificates.
The installation wizard has created a certificate request for the machine you are
installing on. It is called %HOSTNAME%.csr. Use this request to obtain the
certificate. Remember to also obtain any root / chain certificates etc. that might
be needed.
ATTENTION: It is important to import the correct (chain/root) certificates at

this point. Please contact your Regional Office if you need more information
regarding certificates.
Important Note regarding re-using certificates in a clustered install
When you want to re-use certificates in a clustered installation, please read the
section further in the document under Important Note regarding re-using
certificates in a clustered install
When the certificate(s) is(are) received, copy it(them) into the security folder.
Note that in this example we also have copied our root certificate ftDEV.cer.
Reboot the server.
The contents of KeyToolImport_example.txt are displayed below:
set java_home=D:\ORA\JDK
cd /d %JAVA_HOME%\jre\lib\security
#########################################################################
### Please make sure to replace thepassword with the correct password ###
#########################################################################
%java_home%\jre\bin\keytool -importcert -file
D:\micros\opera\security\ftdev.cer -alias ftdev -keystore
D:\micros\opera\security\V5MACHINE.jks -storepass thepassword -storetype
JKS -noprompt
D:\micros\opera\security\ftdev.cer -alias ftdev -keystore cacerts storepass thepassword -storetype JKS -noprompt
D:\micros\opera\security\%COMPUTERNAME%.cer -alias V5MACHINE -keystore
D:\micros\opera\security\V5MACHINE.jks -storepass thepassword -storetype
JKS -noprompt
D:\micros\opera\security\%COMPUTERNAME%.cer -alias V5MACHINE -keystore
cacerts -storepass thepassword -storetype JKS noprompt
The first 2 keytool commands import the root certificate ftdev.cer into the
V5MACHINE and cacerts keystores. For these commands, and any additional
root/chain certificates, you change the name of the file and the name of the alias.
The next two commands import the certificates for the hostname you entered
into the wizard earlier into the V5MACHINE and cacerts keystores. For these
commands you can change the file name if needed, but it is important that the
alias is not renamed and thus stays V5MACHINE.
Reboot the server.
KeyToolImport_example.txt can be opened in Notepad and edited to fit the

situation. You can open a DOS window and copy/paste the commands after
editing KeyToolImport_example.txt.
We see that both the server certificate and the root certificate are added to
V5MACHINE and cacerts key stores. Now you can close the command window
and click OK. Close the warning text document when the certificates have been
imported.
Reboot the server.
As this is an important step in the installation process and the installation will
need to be deleted and redone if the correct certificates have not been imported,
there is another warning. Click OK.
The configuration process will continue.
Some patches will be applied.
Reboot the server.
OPERA Applications are deployed to the managed servers.
The wizard will also install an 11g client into :\ORA\1120client
Select Next
External Certificates
The server will reboot when clicking OK.
Important Note regarding re-using

certificates in a clustered installation
External Certificates
In an environment where multiple application servers are being load balanced, it may be
desirable to share the certificates from the initial application server install with the nth
servers. To perform this, the first application server installation must be completed.
Upon subsequent server installations when the below prompt is received the following
should be done:
Rename D:\micros\opera\security to D:\micros\opera\security_orig

Copy D:\micros\opera\security from APP1 to APPn
Follow KeyToolImport_example.txt but only import the certificate chain into cacerts
Click OK
Internal Certificates
External certificates are not a requirement for the application server install since this
layer isnt customer facing like the OAM/WT server. In this case the certificate should be
issued using the computer name and the security directory should not be shared across
systems.
Compile stationary RDF files

Any customized RDFs created against a 10g OPERA application server will need to be
recompiled on the 11g OPERA application server after the RDF files have been copied
from the 10g application server to the 11g application server.
The recompile steps can be manually carried out using Oracle Reports Builder on the 11g
Application server, or by utilizing the below sample script. This script can be used to
compile any and all RDFs located in the Customizable_reports location on the 11g
Application server.
Save the below sample script into a batch file and place in the customizable_reports
folder on the 11g application server. It is important to modify the path to RUNTIMES
folder as required in the below script.
*****************************************************************
:: Get username/password/database
setlocal
set /p USER="Input Username: "
set /p PASS="Input Password: "
set /p DB="Input Database: "
:: Set REPORTS_PATH to point to rep_gen.pll in the runtimes folder modify if runtime on C: Drive.
set REPORTS_PATH=D:\micros\opera\production\runtimes
:: Search current directory for RDF files and convert to REP file
FORFILES /m *.rdf /c "CMD /C rwconverter %USER%/%PASS%@%DB% STYPE=RDFFILE
SOURCE=@file DTYPE=REPFILE BATCH=YES OVERWRITE=YES"
*****************************************************************
Executing the batch file from the customizable_reports location will launch the batch
compile procedure where the connection string for the OPERA type schema will need to
be entered. Once connection details have been entered the following is seen as the batch
compile procedure is executed
A log file named reports.log is created in the customizable_reports folder.
Compile stationary RDF files 23
Checklist for 10g to 11g OPERA Application

Server migration
During a 10g to 11g application server migration certain types of files would need to be
migrated to the new 11g OPERA application server(s).
Some of the main areas to consider when migrating relevant data from 10g to 11g
Application server(s) are listed below.
Resort GIF files and customized image files located in

\micros\opera\production\runtimes
Images used in resort and room configuration located in

\micros\opera\production\images
File export and EOD reports located in \micros\opera\export or in UNC

location
Customized stationary located in

\micros\opera\production\customizable_reports
(These need to be recompiled as per previous section.)
Customized screen painter files (*_SP.PLL) located in

\micros\opera\production\runtimes
(These need to be recompiled as per previous section.)
Support for National Character Sets

Support for Unicode national characters in PDF output is available, but not enabled by
default. In order for Unicode characters to be properly rendered in PDF report output,
the following configuration changes are required.
File name: UIFONT.ALI
Location:
D:\ORA\operainstance\config\FRComponent\frcommon\guicommon\tk\admin
This file contains a section related to PDF output. Using the Microsoft Unicode Arial font
Oracle Report Service will be capable of outputting all character sets within the PDF
format.
The PDF:Subset section of the file should contain one or more references to the font
file(s) to be used. Opera forms and reports are coded to use Arial Unicode MS the
entries below cover the various styles of output for this font and the actual Unicode font
file to be used for each.
Sample content:
Note: The Arial Unicode TTF file must exist in the %windir%\fonts folder of the
Application Server.
For more information, please consult the below documents:
https://docs.oracle.com/cd/E17904_01/bi.1111/b32121/pbr_font.htm#RSPUB0009
https://docs.oracle.com/cd/E21764_01/bi.1111/b32121/pbr_pdf002.htm#RSPUB23407
https://docs.oracle.com/cd/E21764_01/bi.1111/b32121/pbr_font003.htm#RSPUB23181
Support for National Character Sets 25
Keystores and wallets on an 11g OPERA

Application Server
The OPERA 11g Application Server makes use of some JAVA keystores and Oracle
wallets and each of the files involved has a specific role.
The files involved are:
1)
\micros\wallets\ewallet.p12 (and cwallet.sso)
2)
\micros\opera\security\V5MACHINE.jks
3)
%JAVA_HOME%\jre\lib\security\cacerts
#1 is the identity store for the OHS (Apache) server. It should always include the
server cert for the web server and the CA certs used to sign that certificate. With a selfsigned cert, the server cert and the CA cert are the same. The installation wizard
generates this file by converting the #2 file.
#2 is the identity store for the WLS server. The managed servers use a certificate out
of this keystore (accessed by alias) to act as the server cert for the WLS SSL ports. Details
of the config are available via the WLS admin console. This file is basically the same as
#1 but used by a different server component.
#3 is the trust store for the JDK. Any program running via the JDK will (by default)
use the CA certs in this file as a trusted CA list. So things like the WLST scripting tool
will use it to decide if the SSL connection it is making is trusted or not. Since we use SSL
for deploying applications to WLS managed servers, the CA used to sign the WLS server
cert (#2) must be in here as a trusted certificate. Any outbound calls from java
applications running in the managed servers on the machine will do the same.
A couple other points:
There is no harm in installing additional CA certs that are expected to be trusted

in any of the files. Sometimes this is unnecessary but no harm done. The only
required ones are ones used for connections out of components using that file.
The way JKS files work is that when you first create a client certificate (-genkey)
in a JKS keystore, the certifcate will exist inside as a self-signed certificate. This is
expected. The next steps are to export the certificate signing request, get it
signed, and then import it back in overwriting the self-signed cert with a CA
signed certificate. If you intend to use self-signed, then the export/import part
are skipped.
More information can be found at the below locations:

http://docs.oracle.com/cd/E29597_01/fusionapps.1111/e14496/securing.htm#CHDJG
HCD
http://docs.oracle.com/middleware/1212/webtier/HSADM/getstart.htm#HSADM860
Creating the Certificate Request
Pre-Creating Certificate Requests for 11g

OPERA 5 Application Servers
During the installation of an 11g OPERA 5 Application Server, the installation wizard
expects the installation staff to present a valid certificate for the server.
Because it can take a certain amount of time to receive a certificate from a Certification
Authority after creating the certificate request, this document describes the steps that can
be taken in order to create the certificate ahead of the Application Server installation
process.
It is assumed that the person creating the certificate requests knows the hostnames that
the requests are to be for and all other attributes. It also is assumed that all necessary
root certificate etc. will be delivered when the certificate is being delivered, ahead of the
Application Server installation process.
Attributes that are to be provided during the certificate request creation are listed below:
Certificate Request Hostname (CN)
Organization (O)
Locality / City (L)
State / Province (ST)
Two letter Country Abbreviation (C )
When creating the certificate request, a keystore file will get created that during the
actual installation is copied to the application server. It is important that the password
that is provided during the creation of the certificate request is the same as the
WebLogic Administrative Password that will be used during the application server
installation.
Valid passwords are 8 to 30 characters long, must begin with an alphabetic character,
use only alphanumeric, underscore (_), dollar ($) or pound (#) characters. It should
contain at least one numeric, underscore (_), dollar ($), or pound (#) character.
Creating the Certificate Request

You can use any machine that has JDK 7 u60 x64 or higher installed to create the
certificate request, including existing 11g application servers. Certificate Requests
created using JDK 8 are not supported.
Caution: When using an existing application server, make sure to not create the
keystore files in the D:\micros\opera\security folder as to not overwrite existing
keystore files.
Pre-Creating Certificate Requests for 11g OPERA 5 Application Servers 27
Using the Certificate during the Application Server Installation
Open a command prompt and type the below commands (adapt to your environment
where needed). Make sure that the password adheres to the rules described in the
previous paragraph.
Caution: Only change the entries that are bolded in the below command. It is
important that the alias name of V5MACHINE is preserved.
"C:\Program Files\Java\jdk1.7.0_79\jre\bin\keytool.exe" -genkey -keyalg
RSA -dname "CN=THEHOSTNAME.domain.com, O=MYCOMPANY, C=US, ST=Florida,
L=Naples" -alias V5MACHINE -keypass typeapassword15 -keystore
D:\giveaname.jks -storepass typeapassword15 -validity 1461 -keysize 2048
"C:\Program Files\Java\jdk1.7.0_79\jre\bin\keytool.exe" -certreq -v alias V5MACHINE -file D:\giveaname.csr -keypass typeapassword15 storepass typeapassword15 -keystore D:\giveaname.jks
Submit the certificate request to your CA.

Once all certificates have been received, install the application server as described earlier
in this document.
Note: Even though you already have the certificates, you will still need to complete the
attributes screens.
At a certain stage, the wizard will create a new certificate request, show the below screen
and pause. It is at this point that we will perform the below steps in order to use the
certificates that we received from our CA. Do NOT click on OK until the following steps
are completed.
Navigate to D:\MICROS\opera\security and delete the files called

V5MACHINE.csr, V5MACHINE.jks and %HOSTNAME%.csr (e.g.
FR11WPWD.csr).
Optionally delete the files ftDEV.cer and ftdevca2.crt in the same directory.
Copy the jks file that was created when the certificate request was made (e.g.
FR11WPWD.jks) to D:\MICROS\opera\security and rename it to
V5MACHINE.jks.
Copy the certificate and all additional chain certificates required to

D:\MICROS\opera\security.
Import the certificates. You can consult example commands in

KeyToolImport_example.txt. The output should look similar to the below. In
the below example, the ftdev.cer is the root certificate.
If the output of the importcert command of the actual server certificate (3rd
command in the above screenshot) does not return with Certificate reply was
installed in keystore, the certificate was not correctly added to the keystore and
the application server installation will not complete correctly. You will need to
find out why this is happening and correct the installation.
In case you do see the correct output, complete the application server
installation as usual.
Pre-Creating Certificate Requests for 11g OPERA 5 Application Servers 29
Updating an 11g OPERA application server

with new certificates
There are several methods to update the keystores and wallets with new certificates. The
below documents recreating the wallets and keystores as a way of using new certificates.
There are several other ways in which Weblogic administrators can replace the
certificates and there is a good amount of Oracle documentation available on MOS and
other sources in order to assist.
Note that he keystore that is created when the certificate request is being created and
the certificate that is obtained from that certificate request are a pair. You cannot
create the keystore and create a certificate request / obtain the certificate separately,
even if the same hostname is being used.
Take backups of and move the files in the below folders away:
o
D:\MICROS\wallets
D:\MICROS\opera\security
Create a copy of the file cacerts in D:\ORA\JDK\jre\lib\security
Create the new certificate request:
In a CMD window type the below and validate the output/response:

Caution: Only change the entries that are bolded in the below command. It is
important that the alias name of V5MACHINE is preserved.
D:\ora\JDK\jre\bin\keytool.exe -genkey -keyalg RSA -dname
"CN=TESTV505WIZ.ft.micros.com, O=Micros, C=US, ST=Florida, L=Naples" alias V5MACHINE -keypass mypasswd71 -keystore
D:\MICROS\opera\security\V5MACHINE.jks -storepass mypasswd71 -validity
1461 -keysize 2048
D:\ora\JDK\jre\bin\keytool.exe -certreq -v -alias V5MACHINE -file
D:\MICROS\opera\security\TESTV505WIZ.csr -keypass mypasswd71 -storepass
mypasswd71 -keystore D:\MICROS\opera\security\V5MACHINE.jks
Submit the certificate request to your CA.
Once you receive the certificate and root certificate(s), continue with the below
steps.
Navigate to D:\ORA\JDK\jre\lib\security and copy the file cacerts_ORG to

cacerts (Note that this is NOT The backup of the cacerts file that you created
earlier, but rather a backup file created by the installation wizard during the
initial installation)
Open a CMD window, type the below and validate the output/response:
D:\ora\JDK\jre\bin\keytool.exe -storepasswd -new mypasswd71 -keystore

D:\ora\JDK\jre\lib\security\cacerts -storepass changeit
D:\ora\JDK\jre\bin\keytool.exe -delete -keystore
D:\ora\JDK\jre\lib\security\cacerts -alias ttelesecglobalrootclass2ca
-storepass mypasswd71 -noprompt
D:\ora\JDK\jre\bin\keytool.exe -delete -keystore
D:\ora\JDK\jre\lib\security\cacerts -alias ttelesecglobalrootclass3ca
-storepass mypasswd71 -noprompt
Copy the certificate and root certificate(s) to D:\MICROS\opera\security
Updating an 11g OPERA application server with new certificates 31
Import the root certificate(s) and certificate by opening a CMD window and
typing the below (ftdevca2.crt is the root certificate in this example). Validate the
output/response.
set java_home=D:\ORA\JDK
cd /d %JAVA_HOME%\jre\lib\security
D:\micros\opera\security\ftdevca2.crt -alias ftdev -keystore
D:\micros\opera\security\V5MACHINE.jks -storepass mypasswd71 storetype JKS -noprompt
D:\micros\opera\security\ftdevca2.crt -alias ftdev -keystore cacerts
-storepass mypasswd71 -storetype JKS -noprompt
D:\micros\opera\security\TESTV505WIZ.cer -alias V5MACHINE -keystore
D:\micros\opera\security\V5MACHINE.jks -storepass mypasswd71 storetype JKS -noprompt
D:\micros\opera\security\TESTV505WIZ.cer -alias V5MACHINE -keystore
cacerts -storepass mypasswd71 -storetype JKS -noprompt
If the output of the importcert command of the actual server certificate (3rd
command in the below screenshot) does not return with Certificate reply was
installed in keystore, the certificate was not correctly added to the keystore.
Likely the wrong files were being used in that case.
Now that the root and server certificates have been installed in the keystore, we
need to recreate the Oracle wallet. Open a CMD window, type the below and
validate the output/response:
set JAVA_HOME=D:\ora\JDK
D:\ora\mwfr\oracle_common\bin\orapki.BAT wallet create -wallet
D:\micros\opera\security -pwd mypasswd71 -auto_login
D:\ora\mwfr\oracle_common\bin\orapki.BAT wallet jks_to_pkcs12 -wallet
D:\MICROS\opera\security -pwd mypasswd71 -keystore
D:/micros/opera/security/V5MACHINE.jks -jkspwd mypasswd71
Update the security on the wallet files. Open a CMD window, type the below and
validate the output/response:
echo 'Y'|CACLS D:\micros\opera\security\cwallet.sso /E /T /C /G
"Everyone":F
Updating an 11g OPERA application server with new certificates 33
Move cwallet.sso and ewallet.p12 from D:\MICROS\opera\security to

D:\MICROS\wallets
Import any additional certificates that are needed into the Oracle wallet using the
Oracle Wallet Manager GUI.
Reboot the server.
NOTE: In order to obtain more information regarding commands being used in this
document, please read the below documentation:
http://docs.oracle.com/javase/6/docs/technotes/tools/solaris/keytool.html
Additional Information
The following are the main components that are installed by the wizard (x64 version):
JDK 7u60
Oracle WebLogic Server 10.3.6
Oracle Forms and Reports 11.1.2.2
Oracle HTTP Server 12.1.3.0.0
OPERA 5.0.04.03 E00007 / OPERA 5.0.05.00 E00005
Note that Oracle Forms and Reports installs an older version of OHS. The OPERA
installation wizard disables this HTTP Server.
The software gets installed in directories under :\ORA. The OperaDomain is located
at :\ORA\user_projects\domains\OperaDomain and the OperaInstance is in
:\ORA\operainstance
The installation of OHS 12c creates an additional OperaOHSDomain domain under
:\ORA\user_projects\domains\OperaOHSDomain, containing many of the
configuration files for the HTTP Server.
The application server contains some of the configuration files that we are used to from
the OPERA Oracle 10g IAS application servers.
The files within D:\micros\opera\operaias stay pretty much the same, with the addition
of opera.cfg and opera_wl.conf
Formswweb.cfg is now located in
:\ORA\user_projects\domains\OperaDomain\config\fmwconfig\servers\WLS_FO
RMS\applications\formsapp_11.1.2\config
httpd.conf is located in
D:\ORA\user_projects\domains\OperaOHSDomain\config\fmwconfig\component
s\OHS\ohs1. Another copy of the httpd.conf is created by the system in
:\ORA\user_projects\domains\OperaOHSDomain\config\fmwconfig\components\
OHS\instances\ohs1Note there is also an httpd.conf file in
:\ORA\operainstance\config\OHS\ohs1 that is NOT being used by the OPERA
Application Server.
tnsnames/sqlnet.ora are located in :\ORA\operainstance\config

The weblogic console can be accesses by:
http//localhost:7041/console or https// localhost:7042/console
The reports server configuration files are in
:\ORA\operainstance\config\ReportsServerComponent\repSERVERNAMESCHEM
ANAME
The reports server(s) are controlled by opmn.
Additional Information 35
Oracle Corporation
World Headquarters
500 Oracle Parkway
U.S.A.
Phone: +1.650.506.7000
Fax: +1.650.506.7200
oracle.com
permission.

Opera Install Binder

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Opera Install Binder

Загружено:

Авторское право:

Доступные форматы

Oracle Hospitality

OPERA 5.0.5.xx Single Server

Note: The following is intended to outline our general

product direction. It is intended for information purposes

Initial document, replacement for

New format, miscellaneous

Please sent comments on this document to richard.schulze@oracle.com

Single Server Installation Steps

Single Server Installation

2 Confidential Oracle Internal

Note: The following is intended to outline our general

product direction. It is intended for information purposes

Initial document, replacement for

New format, miscellaneous

Please sent comments on this document to richard.schulze@oracle.com

Disable Windows DEP

2 Confidential Oracle Internal

Disable Windows DEP

Disable Windows DEP

Changes required to a standard Windows

Confirm if you are prompted to overwrite the current value.

4 Confidential Oracle Internal

Disable User Account Control (UAC).

Disable User Account Control (UAC).

Changes required to a standard Windows installation 5

Disable User Account Control (UAC).

Click OK to confirm the changes.

6 Confidential Oracle Internal

Disabling the Windows Firewall

Disabling the Windows Firewall

Changes required to a standard Windows installation 7

Disabling the Windows Firewall

It may still be enabled for the other profiles (see below).

8 Confidential Oracle Internal

Reboot the server.

The result is shown below.

Reboot the server.

Changes required to a standard Windows installation 9

Reboot the server.

OPERA 5 Database Server Installation

Navigate into the DVD2 folder and launch OperaInstallation.EXE.

The wizard will collect some installation variables. Click Next.

Acknowledge the actions the wizard will take. Click Next.

10 Confidential Oracle Internal

Reboot the server.

OPERA 5 Database Server Installation 11

Reboot the server.

12 Confidential Oracle Internal

Reboot the server.

OPERA 5 Database Server Installation 13

Reboot the server.

The installation will commence.

14 Confidential Oracle Internal

Reboot the server.

The installation finishes.

OPERA 5 Database Server Installation 15

Post Installation Steps

16 Confidential Oracle Internal

Enabling archivelog mode

Enabling archivelog mode

Shut down the database.

Mount the database in sqlplus.

Enable archive logging and open the database.

Post Installation Steps 17