This chapter describes how to install Oracle Application Server, which includes the Oracle Fusion Middleware Infrastructure Software, Oracle Forms Server and the Oracle Reports Server, and Oracle WebLogic Server.
This chapter includes:
Section 3.5, "Install the Oracle Fusion Middleware Infrastructure Software"
Section 3.9, "Enable SSL Between a Browser and Oracle HTTP Server"
Section 3.10, "Modify the tnsnames.ora File on the Application Server"
Section 3.12, "Test Connectivity to Databases for Forms and Reports Servers"
Install all application tier components using the same user account.
The account must have administrator privileges on the server computer.
To support HTTPS:
Request a certificate from a Certificate Authority (CA) vendor, such as Thawte, Entrust, or Verisign.
Generate an encoded plain text certificate request file. See Section 3.9.1.1, "Create an Oracle Wallet and Generate a Certificate Request" for more information.
Email the certificate request file to the CA vendor.
The vendor will sign the file, and send you a Trusted Certificate and a User Certificate. Allow some time for the certificates to be issued.
Import the certificate into the Oracle Wallet for the Oracle Application Server.
Note:
If your intention is to install an environment that will never be taken into production, you can skip this step and create a self-signed demo certificate for testing purposes; see Section 3.9.2, "Enable SSL Between a Browser and Oracle HTTP Server With Self Signing".Have the following information ready.
Install the Oracle WebLogic Server
Home directory path; for example:
C:\Oracle\Middleware\Oracle_Home
Email address to receive security updates specific to your installation
My Oracle Support password if you wish to receive the security updates through My Oracle Support
Install the Oracle Fusion Middleware Infrastructure Software
Home directory path; for example:
C:\Oracle\Middleware\Oracle_Home
Email address to receive security updates specific to your installation
My Oracle Support password if you wish to receive the security updates through My Oracle Support
Install the Oracle Forms and Reports Servers
Home directory path; for example:
C:\Oracle\Middleware\Oracle_Home
Create the Repository Creation Utility
Database details:
Server.Domain; for example:
servername.your_company.com
Port number
Database service name
Database administrator username and password
RCU Schema password
Domain home path; for example:
C:\Oracle\Middleware\Oracle_Home\user_projects\domains\FRDomain
Application location; for example:
C:\Oracle\Middleware\Oracle_Home\user_projects\applications\FRDomain
WebLogic Domain administration username and password
RCU Database connection:
DBMS/ Service name
Server.Domain; for example:
servername.your_company.com
Port number
Schema owner name and password
Node Manager credentials: Username and password
Oracle HTTP Server details:
Administrator host's IP address
Administrator port number
Listen address
Listen port number
SSL listen port number
Server name
To install Oracle Java Development Kit (JDK):
If you have not already done so, follow instructions in Section 1.6, "Download the Software".
Follow instructions in the release notes to apply the patch.
Note:
Do not use the default download location. By default, the download directory is C:\Program Files\java\jdk. "Program Files" includes a space, which can cause problems. Oracle recommends specifying a directory with no spaces in the name. Also, we recommend not to include the JDK version in the directory name (for example, C:\app\jdk18016) in order to have the directory name valid if JDK needs to be upgraded in the future.In addition, the directory name must have no more than 8 characters; for example, C:\app\java\jdk.
Make a note of the directory in which you install JDK. You will need it when you install WebLogic Server.
In the staging area where you downloaded the media pack (see Section 1.6, "Download the Software"), locate the directory where you downloaded Oracle WebLogic Server 12.2.1.4 Generic and Coherence and extract the WebLogic Server .zip file (V983364-01.zip) if you have not already done so.
Log in as the user you selected in Section 3.1.1, "Identify a Single Account to Perform All Application Tier Installation Tasks".
Install Oracle WebLogic Server using a Generic Package installer—This type of installer is a .jar file; fmw_12.2.1.4.0_wls.jar.
For instructions, see Oracle® Fusion Middleware Installing and Configuring Oracle WebLogic Server and Coherence for Release 12.2.1.4, at https://docs.oracle.com/en/middleware/lifecycle/12.2.1.4/wlsig/installing-oracle-weblogic-server-and-coherence-software.html#GUID-E4241C14-42D3-4053-8F83-C748E059607A
.
The complete documentation set for Oracle WebLogic Server 12.2.1.4 is available at: https://docs.oracle.com/en/middleware/fusion-middleware/weblogic-server/12.2.1.4/index.html
.
You can accept most default values, with the exceptions noted below.
Note:
You can change the default value of the middleware_home directory, which is C:\Oracle\Middleware\Oracle_Home, if you want, but some code examples in this guide use that value to make it easier to copy and paste, so remember to change these if you change the value.You must NOT change the names for any of the middleware home's subdirectories, including wlserver
and oracle_common
.
Note:
Make sure you have installed Visual C++ in Microsoft Visual Studio 2012 (x64 distributed). This is required for Oracle WebLogic Server 12c (12.2.1.4) and Oracle Forms and Reports 12c (12.2.1.4) Servers to invoke Data Capture API methods from custom clients.Choose the "WebLogic Server" Install Type
Select WebLogic Server.
This is required in order to create a Node Manager.
Note:
Even if you accept this option, you should check My Oracle Support for quarterly Oracle Critical Patch Update (CPU) security patches certified for use with Oracle Clinical and/or Oracle Thesaurus Management System.Specify whether you want to register the product installation with My Oracle Support.
If you register, Oracle Support emails you immediately of any security updates that are specific to your installation.
Follow instructions on the screen to register or to reject the option.
Note:
Continue to click Next until you are finished. After the Installation Summary, the processing may take a few minutes. You can deselect the Automatically Launch Configuration Wizard check box and click Finish to complete the 12c WebLogic Server installation.In the staging area where you downloaded the media pack (see Section 1.6, "Download the Software"), locate the directory where you downloaded the Oracle Fusion Middleware Infrastructure Software and extract the .zip file (V983368-01.zip) if you have not already done so.
Log in as the user you selected in Section 3.1.1, "Identify a Single Account to Perform All Application Tier Installation Tasks".
Install the Oracle Fusion Middleware Infrastructure Software using a Generic Package installer—This type of installer is a .jar file; fmw_12.2.1.4.0_infrastructure.jar.
Note:
Use the same install directory that you specified when you installed WebLogic Server in Section 3.4, "Install Oracle WebLogic Server 12.2.1.4".Select "Fusion Middleware Infrastructure" as the installation type.
For instructions, see Oracle® Fusion Middleware Installing and Configuring the Oracle Fusion Middleware Infrastructure for Release 12.2.1.4, at https://docs.oracle.com/en/middleware/fusion-middleware/12.2.1.4/infin/installing-infrastructure-software.html#GUID-943F11B4-DD9E-4631-8F5F-80B3ADC06F26
.
In the staging area where you downloaded the media pack (see Section 1.6, "Download the Software"), locate the directory where you downloaded Oracle Forms and Reports 12c (12.2.1.4) for Microsoft Windows (64-bit) and extract the .zip file (V983393-01.zip) if you have not already done so.
Log in as the user you selected in Section 3.1.1, "Identify a Single Account to Perform All Application Tier Installation Tasks".
Install the Oracle Forms and Reports 12c (12.2.1.4) using a Generic Package installer—This type of installer is an .exe file; setup_fmw_12.2.1.4.0_fr_win64.exe.
When asked, to choose an installation type, select Forms and Reports Deployment.
Note:
Use the same install directory that you specified when you installed WebLogic Server in Section 3.4, "Install Oracle WebLogic Server 12.2.1.4".For instructions, see Oracle® Fusion Middleware Installing Oracle Forms and Reports for Release 12.2.1.4 at https://docs.oracle.com/en/middleware/developer-tools/forms/12.2.1.4/install-fnr/installing-and-configuring-oracle-forms1.html#GUID-EBBA8709-F563-469C-9D2F-F308AF4E60C5
.
For this task, you need the following database server details:
Host name
Port
Service name
Password for the SYS account
For instructions, see Oracle® Fusion Middleware Installing Oracle Forms and Reports for Release 12.2.1.4 at https://docs.oracle.com/en/middleware/developer-tools/forms/12.2.1.4/install-fnr/installing-and-configuring-oracle-forms1.html#GUID-26210D99-290E-446D-B972-A81EA5C90CF9
. In this link, read the first step as "Run FMW_HOME/oracle_common/bin/rcu.bat."
You can accept most default values, with the exception noted below.
Select the option Oracle Platform Security Services.
Enter the prefix name for the domains in the following format:
servernameFR
Provide a schema password and make note of the schema name and password because they are required to configure the FRDomain.
For instructions, see Oracle® Fusion Middleware Installing Oracle Forms and Reports for Release 12.2.1.4 at https://docs.oracle.com/en/middleware/developer-tools/forms/12.2.1.4/install-fnr/installing-and-configuring-oracle-forms1.html#GUID-E3EC8981-780D-4D15-AA01-1FF91CDDCF59
.
Note:
Ignore the warning "CFGFWK-40326" that appears in the Configuration Summary screen as it is not related to the Oracle Forms and Report configuration.Make sure you type FRDomain
(case-sensitive) in the desired domain home path.
When configuring the FRDomain, it is recommended to use the default port 7001 for Admin Server and 9001 or 9002 for managed servers (WLS_FORMS and WLS_REPORTS).
You can accept most default values, with the exception noted below.
After completing the FRDomain configuration, follow instructions in Section 3.8.1, "Run ohs_updateInstances".
Select the check box for the following templates:
Oracle Forms [forms]
Oracle Reports Application [reports]
Oracle Enterprise Manager [em]
Oracle HTTP Server (Collocated) [ohs]
Oracle Reports Tools [ReportsToolsComponent]
Oracle Reports Server [ReportsServerComponent]
Oracle Reports Bridge [ReportsBridgeComponent]
Oracle JRF [oracle_common]
WebLogic Coherence Cluster Extension [wlserver]
Provide a password for the WebLogic user account and make note of this password because it is required to install Oracle Thesaurus Management System and/or Oracle Clinical.
Select the Production option under Domain Mode.
Provide the Repository Creation Utility schema name that you defined in Section 3.7, "Create the Repository Creation Utility" and add _STB to this name. For example, if the schema name you defined was OCRDCDEV, provide OCRDCDEV_STB.
Provide the schema password that you defined in Section 3.7, "Create the Repository Creation Utility".
Click Get RCU Configuration to continue.
Select all check boxes.
Select the Enable SSL check box.
Define the Node Manager username and password and make note of them because they are required to install Oracle Thesaurus Management System and/or Oracle Clinical.
Select the Enable SSL check box for all managed servers.
Move AdminServer from the Servers list to the Machines list.
Click Add to add the OHS component.
For System Component, specify ohs1.
For the Component Type, select OHS.
Note:
It is recommended to use the standard HTTP/HTTPS ports 80 or 443. If you plan to use other ports, these need to be modified accordingly during the installation process.For Listen Address, specify the machine name, including the domain.
Change the Listen Port value to 80.
Change the SSL Listen Port value to 443.
Copy the URL from the Plain field and paste it in the SSL field.
In the SSL field, change http to https, and add the SSL port if the non-standard port 443 is used.
Select the SSL as the default option.
Move ohs1 from the System Component list to the Machines list.
Perform the following steps:
Start the Node Manager.
$ORACLE_HOME\user_projects\domains\FRDomain\bin\startNodeManager.cmd
Start the admin server.
$ORACLE_HOME\user_projects\domains\FRDomain\bin\startWebLogic.cmd
Run WLST.
$ORACLE_HOME\oracle_common\common\bin\wlst.cmd
Connect to admin server.
connect('adminserver_username','adminserver_password','t3://host_name:FRDomain_adminserver_port')
For example:
('weblogic','weblogic1','t3:localhost:7001')
Run the following command:
ohs_updateInstances()
Create the following SSL (HTTP Secure Socket Layer) configuration: from users' browsers, HTTPS to Oracle HTTP Server (Web proxy), then HTTP to Oracle WebLogic Server.
Follow instructions in one of the following sections:
Section 3.9.1, "Enable SSL Between a Browser and Oracle HTTP Server Using a Certificate Authority"
Section 3.9.2, "Enable SSL Between a Browser and Oracle HTTP Server With Self Signing"—This may be useful if you want to set up HTTPS with a demo certificate for internal testing purposes.
The following basic steps are required:
An Oracle Wallet is a container that stores your credentials, such as certificates, trusted certificates, certificate requests, and private keys.
The Oracle Thesaurus Management System Installer automatically enables traffic from Oracle HTTP Server to Oracle WebLogic Server.
Note:
Do all steps in this section with the same user account you have used in the previous steps in this chapter. You must have administrator privileges on the machine.To create an Oracle Wallet:
Create an Oracle Wallet: https://docs.oracle.com/en/middleware/lifecycle/12.2.1.4/asadm/managing-keystores-wallets-and-certificates.html#GUID-DA49F413-AB8F-46E6-924C-EC4CD8F96AC1
Generate a Certificate Request: https://docs.oracle.com/en/middleware/lifecycle/12.2.1.4/asadm/managing-keystores-wallets-and-certificates.html#GUID-70174F92-035D-4829-9DB8-8118964BFA9D
Note:
Certificate signed using MD5 algorithm is no longer supported in Oracle HTTP Server (12.2.1.4). You must get the certificate signed using Secure Hashing Algorithm 2 (SHA-2).Obtain the certificates from the Certificate Authority as described in Section 3.1.2, "Get a CA Certificate for HTTPS".
Depending on the Certificate Authority, you will need to send either the certificate request file generated in the previous section or you will need to copy and paste the text in that file.
For information, see https://docs.oracle.com/en/middleware/lifecycle/12.2.1.4/asadm/managing-keystores-wallets-and-certificates.html#GUID-70174F92-035D-4829-9DB8-8118964BFA9D
WebLogic Server installation creates a default, unsigned SSL wallet file for OHS. Its location is specified in the configuration file (ssl.conf) loaded at startup from the oracle_instance\config\OHS\ohs1 directory.
Make a backup copy of ssl.conf, which is located where Fusion Middleware is installed in %ORACLE_HOME%:
%ORACLE_HOME%\user_projects\domains\FRDomain\config\fmwconfig\components\OHS\ohs1 %ORACLE_HOME%\user_projects\domains\FRDomain\config\fmwconfig\components\OHS\instances\ohs1
Open ssl.conf in a text editor.
Find the string #Path to the wallet
and comment out the default location that follows it.
SSLWallet ${ORACLE_INSTANCE}/config/${COMPONENT_TYPE}/${COMPONENT_NAME}/keystores/default
Replace the above string (in bold) with the path to the directory you created:
SSLWallet %ORACLE_HOME%\user_projects\domains\FRDomain\config\fmwconfig\components\OHS\ohs1\keystores
Stop and start Oracle HTTP Server (OHS) to load the configuration change:
To stop OHS:
%ORACLE_HOME%\user_projects\domains\FRDomain\bin\stopComponent ohs1
To start OHS:
%ORACLE_HOME%\user_projects\domains\FRDomain\bin\startComponent ohs1
Note:
ohs1 is the name of OHS component provided while configuring FRDomain.%ORACLE_HOME% is the location of installed FMW.
Test that you can connect from a browser to your virtual host in HTTPS URL:
https://host.your_company_domain
For more information, see How to create a Self Signed Certificate to enable SSL between the Browser and HTTP Server in Oracle Clinical 5.2 (Document ID 2473240.1) on My Oracle Support.
WebLogic Server installation creates a default, unsigned SSL wallet file for OHS. Its location is specified in the configuration file (ssl.conf) loaded at startup from the oracle_instance\config\OHS\ohs1 directory.
Make a backup copy of ssl.conf, which is located where Fusion Middleware is installed in %ORACLE_HOME%:
%ORACLE_HOME%\user_projects\domains\FRDomain\config\fmwconfig\components\OHS \ohs1 %ORACLE_HOME%\user_projects\domains\FRDomain\config\fmwconfig\components\OHS\instances\ohs1
Open ssl.conf in a text editor.
Find the string #Path to the wallet
and comment out the default location that follows it.
SSLWallet ${ORACLE_INSTANCE}/config/${COMPONENT_TYPE}/${COMPONENT_NAME}/keystores/default
Replace the above string (in bold) with the path to the directory you created:
SSLWallet %ORACLE_HOME%\user_projects\domains\FRDomain\config\fmwconfig\components\OHS\ohs1\keystores
Stop and start Oracle HTTP Server (OHS) to load the configuration change:
To stop OHS:
%ORACLE_HOME%\user_projects\domains\FRDomain\bin\stopComponent ohs1
To start OHS:
%ORACLE_HOME%\user_projects\domains\FRDomain\bin\startComponent ohs1
Note:
ohs1 is the name of OHS component provided while configuring FRDomain.%ORACLE_HOME% is the location of installed FMW.
Test that you can connect from a browser to your virtual host in HTTPS URL:
https://host.your_company_domain
Go to the following tnsnames.ora location on the application server:
%ORACLE_HOME%\user_projects\domains\FRDomain\config\fmwconfig
Make sure the tnsnames.ora file has an entry for each database that matches the database's service name.
Copy the edited tnsnames.ora file from FRDomain_Home to %ORACLE_HOME%\network\admin (for example, to C:\Oracle\Middleware\Oracle_Home\network\admin).
If you have a firewall in your environment:
Open the following ports:
HTTP: 80 (or listen from httpd.conf)
HTTPS: 443 (or listen from ssl.conf)
RDC Onsite: 7221
Oracle Forms: 9001
Oracle Reports: 9002
Forms Admin Server: 7001
OPADomain Admin Server: 7101
The Oracle Thesaurus Management System database must be able to communicate with the application servers.
To ensure that you can connect to the database from each application server:
Open a Microsoft DOS command window.
Use SQL*Plus to verify that you can connect to the database:
sqlplus system/
password@dbname
If the system returns a connection error, you must resolve this problem before continuing with the installation of Oracle Thesaurus Management System.
Possible causes of errors include:
The computer is not physically connected to the network.
One of the databases does not exist.
The network protocol software is not loaded on the computer. Try a remote login to check.
The database or SQL*Net listener process is not started on the server.
An incorrect connect string (service name), user ID, or password was entered.
The tnsnames.ora file is not present in the correct directory or does not contain the correct entries.
To ensure that all configuration changes for the Oracle Application Server are initialized:
Restart the computer before you continue with the next task in the installation process.