3 Install and Configure the Oracle Application Tier

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:

3.1 Before You Start



3.1.1 Identify a Single Account to Perform All Application Tier Installation Tasks

  1. Install all application tier components using the same user account.

    The account must have administrator privileges on the server computer.

3.1.2 Get a CA Certificate for HTTPS

To support HTTPS:

  1. Request a certificate from a Certificate Authority (CA) vendor, such as Thawte, Entrust, or Verisign.

    1. Generate an encoded plain text certificate request file. See Section 3.11.1.1, "Create an Oracle Wallet and Generate a Certificate Request" for more information.

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

  2. 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.11.2, "Enable SSL Between a Browser and Oracle HTTP Server With Self Signing".

3.1.3 Permanent IP Address

  1. Make sure every computer on which either the Oracle Clinical Forms or Reports Server is installed has a permanent IP address.

3.2 Gather Required Information

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

Configure the FRDomain

  • Domain home path; for example:

    C:\Oracle\Middleware\user_projects\domains\FRDomain

  • Application location; for example:

    C:\Oracle\Middleware\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

3.3 Install Adobe Reader

If you have not already downloaded Adobe Reader, following instructions in Section 1.6.7, "Download Adobe Reader", do so now.

  1. Install Adobe Reader on the Reports Server and on client computers.

3.4 Install Oracle Java Development Kit

To install Oracle Java Development Kit (JDK):

  1. If you have not already done so, follow instructions in Section 1.6, "Download the Software".

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

    In addition, the directory name must have no more than 8 characters; for example, C:\app\java\jdk.

  3. Make a note of the directory in which you install JDK. You will need it when you install WebLogic Server.

3.5 Install Oracle WebLogic Server 12.2.1.2

  1. 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.2 Generic and Coherence and extract the WebLogic Server .zip file (fmw_12.2.1.2.0_wls_Disk1_1of1.zip) if you have not already done so.

  2. Log in as the user you selected in Section 3.1.1, "Identify a Single Account to Perform All Application Tier Installation Tasks".

  3. Install Oracle WebLogic Server using a Generic Package installer—This type of installer is a .jar file; fmw_12.2.1.2.0_wls.jar.

    For instructions, see Oracle® Fusion Middleware Installing and Configuring Oracle WebLogic Server and Coherence for Release 12.2.1.2, at http://docs.oracle.com/middleware/12212/lcm/WLSIG/GUID-E4241C14-42D3-4053-8F83-C748E059607A.htm#WLSIG125.

    The complete documentation set for Oracle WebLogic Server 12.2.1.2 is available at: http://docs.oracle.com/middleware/12212/wls/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, 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.2) and Oracle Forms and Reports 12c (12.2.1.2) Servers to invoke Data Capture API methods from custom clients.

Choose the "WebLogic Server" Install Type

  1. Select WebLogic Server.

    This is required in order to create a Node Manager.

Security Updates

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

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

3.6 Install the Oracle Fusion Middleware Infrastructure Software

  1. 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 (fmw_12.2.1.2.0_infrastructure_Disk1_1of1.zip) if you have not already done so.

  2. Log in as the user you selected in Section 3.1.1, "Identify a Single Account to Perform All Application Tier Installation Tasks".

  3. Install the Oracle Fusion Middleware Infrastructure Software using a Generic Package installer—This type of installer is a .jar file; fmw_12.2.1.2.0_infrastructure.jar.

    Note:

    Use the same install directory that you specified when you installed WebLogic Server in Section 3.5, "Install Oracle WebLogic Server 12.2.1.2".

    For instructions, see Oracle® Fusion Middleware Installing and Configuring Oracle WebLogic Server and Coherence for Release 12.2.1.2, at https://docs.oracle.com/middleware/12212/lcm/WLSIG/GUID-2ACC5AA7-8904-430B-B903-8F1EEA578B7A.htm#WLSIG-GUID-2ACC5AA7-8904-430B-B903-8F1EEA578B7A.

3.7 Install the Oracle Forms and Reports Servers

  1. 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.2) for Microsoft Windows (64-bit) and extract the .zip file (fmw_12.2.1.2.0_fr_win64_Disk1_1of1.zip) if you have not already done so.

  2. Log in as the user you selected in Section 3.1.1, "Identify a Single Account to Perform All Application Tier Installation Tasks".

  3. Install the Oracle Forms and Reports 12c (12.2.1.2) using a Generic Package installer—This type of installer is an .exe file; setup_fmw_12.2.1.2.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.5, "Install Oracle WebLogic Server 12.2.1.2".

    For instructions, see Oracle® Fusion Middleware Installing Oracle Forms and Reports for Release 12.2.1.2, at https://docs.oracle.com/middleware/12212/formsandreports/install-fnr/GUID-EBBA8709-F563-469C-9D2F-F308AF4E60C5.htm#FRINS256.

3.8 Install Oracle Database Client

In the application tier staging area:

  1. Extract the file win64_11gR2_client.zip.

  2. Run setup.exe.

  3. You can accept all default values in the installation wizard.

  4. When prompted for the type of installation, select Administrator.

3.9 Create the Repository Creation Utility

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.2, at https://docs.oracle.com/middleware/12212/formsandreports/install-fnr/GUID-EBBA8709-F563-469C-9D2F-F308AF4E60C5.htm#FRINS429. 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 Components

  1. Select the option Oracle Platform Security Services.

  2. Enter the prefix name for the domains in the following format:

    servernameFR

Schema Password

  1. Provide a schema password and make note of the schema name and password because they are required to configure the FRDomain.

3.10 Configure the FRDomain

For instructions, see Oracle® Fusion Middleware Installing Oracle Forms and Reports for Release 12.2.1.2, at https://docs.oracle.com/middleware/12212/formsandreports/install-fnr/GUID-EBBA8709-F563-469C-9D2F-F308AF4E60C5.htm#FRINS394.

Make sure you type FRDomain (case-sensitive) in the desired domain home path.

You can accept most default values, with the exception noted below.

Templates

  1. Select the check box for the following templates:

    • Oracle Reports Server - 12.2.1

    • Oracle Reports Bridge - 12.2.1

    • Oracle Reports Application - 12.2.1

    • Oracle Reports Tools - 12.2.1

    • Oracle HTTP Server - Collacated - 12.2.1.2.0

    • Oracle Forms - 12.2.1.2.0

    • Oracle Enterprise Manager - 12.2.1.2.0

Add Administrator Account

  1. Provide a password for the WebLogic user account and make note of this password because it is required to install Oracle Clinical.

Domain Mode and JDK

  1. Select the Production option under Domain Mode.

Database Configuration Type

  1. Provide the Repository Creation Utility schema name that you defined in Section 3.9, "Create the Repository Creation Utility" and add _STB to this name. For example, if the schema name you defined was OCRDCDEV, provide OCRDCDEV_STB.

  2. Provide the schema password that you defined in Section 3.9, "Create the Repository Creation Utility".

  3. Click Get RCU Configuration to continue.

Advanced Configuration

  1. Select all check boxes.

Administration Server

  1. Select the Enable SSL check box.

Node Manager

  1. Define the Node Manager username and password and make note of them because they are required to install Oracle Clinical.

Managed Servers

  1. Select the Enable SSL check box for all managed servers.

Assign Servers to Machines

  1. Move AdminServer from the Servers list to the Machines list.

System Components

  1. Click Add to add the OHS component.

    1. For System Component, specify ohs1.

    2. For the Component Type, select OHS.

OHS Server

  1. For Listen Address, specify the machine name, including the domain.

  2. Change the Listen Port value to 80.

  3. Change the SSL Listen Port value to 443.

Domain Frontend Host

  1. Copy the URL from the Plain field and paste it in the SSL field.

  2. In the SSL field, change http to https.

  3. Select the SSL as the default option.

Assign System Components

  1. Move ohs1 from the System Component list to the Machines list.

3.11 Enable SSL Between a Browser and Oracle HTTP Server

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:

3.11.1 Enable SSL Between a Browser and Oracle HTTP Server Using a Certificate Authority

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.

3.11.1.2 Obtain Trusted Certificate and User Certificate from Certificate Authority

Note:

Certificate signed using MD5 algorithm is no longer supported in Oracle HTTP Server (12.2.1.0.2). You must get the certificate signed using Secure Hashing Algorithm 2 (SHA-2).
  1. 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.

3.11.1.3 Add the User Certificate and Trusted Certificate to an Oracle Wallet

For information, see https://docs.oracle.com/middleware/12212/lcm/ASADM/GUID-2D2FEEFA-FF02-4ABA-B1A4-C7FCADCEE743.htm#GUID-70174F92-035D-4829-9DB8-8118964BFA9D

3.11.1.4 Edit the Oracle HTTP Server Configuration File

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.

  1. 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
    
  2. Open ssl.conf in a text editor.

  3. 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
    
  4. 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
    
  5. Make sure the port for SSL is 443.

    To change the port to 443, change the following lines:

    Listen existing port
    <VirtualHost *:existing port>
    

    to:

    Listen 443
    <VirtualHost *:443>
    
  6. Stop and start Oracle HTTP Server (OHS) to load the configuration change:

    1. To stop OHS:

      %ORACLE_HOME%\user\projects\domains\FRDomain\bin\stopComponent ohs1

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

  7. Test that you can connect from a browser to your virtual host in HTTPS URL:

    https://host.your_company_domain

3.11.2 Enable SSL Between a Browser and Oracle HTTP Server With Self Signing

For more information, see How To Configure SSL Between the Apache Web Server Proxy Plug-in And WebLogic Server Using Self Signed Wallets on My Oracle Support (Doc ID 1384737.1).

3.11.2.1 Edit the Oracle HTTP Server Configuration File

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.

  1. 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
    
  2. Open ssl.conf in a text editor.

  3. 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
    
  4. 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
    
  5. Make sure the port for SSL is 443.

    To change the port to 443, change the following lines:

    Listen existing port
    <VirtualHost *:existing port>
    

    to:

    Listen 443
    <VirtualHost *:443>
    
  6. Stop and start Oracle HTTP Server (OHS) to load the configuration change:

    1. To stop OHS:

      %ORACLE_HOME%\user\projects\domains\FRDomain\bin\stopComponent ohs1

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

  7. Test that you can connect from a browser to your virtual host in HTTPS URL:

    https://host.your_company_domain

3.12 Apply Patches on the Application Server

Apply the following patches:

  • Oracle Java Database Connectivity (patches 19028811 and 21043834)

  • Oracle Reports Developer patch 22334822

  • Oracle Forms patch 25143879

  • Oracle Clinical PDF Plug-In (patch 12733341)

  • Oracle Application Development Framework (ADF) bundle patch 12.2.1.2.170404 (patch 25495193). You must submit a Service Request (SR) for Oracle Clinical to request the password for this patch.

For instructions on applying a patch, see the corresponding Readme in My Oracle Support.

3.13 Modify the tnsnames.ora File on the Application Server

  1. Go to the following tnsnames.ora location on the application server:

    middleware_home\user_projects\domains\FRDomain\config\fmwconfig

  2. Make sure the tnsnames.ora file has an entry for each database that matches the database's service name.

  3. Copy the edited tnsnames.ora file from fr_home to 11g Client home (for example, to C:\app\gbuadmin\product\11.2.0\client_1\network\admin).

3.14 Configure Firewall on the Application Tier

If you have a firewall in your environment:

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

3.15 Test Connectivity to Databases for Forms and Reports Servers

The Oracle Thesaurus Management System database must be able to communicate with the application servers.

3.15.1 Test the Connection from the Application Servers to the Database

To ensure that you can connect to the database from each application server:

  1. Open a Microsoft DOS command window.

  2. Use SQL*Plus to verify that you can connect to the database:

    sqlplus system/password@dbname

3.15.2 Troubleshoot Network Connection Issues

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.

3.16 Restart the Computer

To ensure that all configuration changes for the Oracle Application Server are initialized:

  1. Restart the computer before you continue with the next task in the installation process.