1. Installation Guide
  2. Upgrading Oracle Thesaurus Management System to Release 5.4.0
  3. Upgrade and Configure the Application Tier Technology Stack

Upgrade and Configure the Application Tier Technology Stack

This section describes how to upgrade Oracle Application Server, which includes the Oracle WebLogic Server, Oracle Fusion Middleware Infrastructure Software, Oracle Forms Server, and the Oracle Reports Server.

  • For releases 5.0.1, 5.0.2, 5.1, 5.1.1, 5.1.2, and 5.2.1, upgrade of the technology stack is not supported. Follow instructions in Install and Configure the Oracle Application Tier for installing a new application server.

  • For release 5.4.0, you can upgrade the application tier from releases 5.2.x and 5.3.x.

  • For the upgrade from releases 5.2.2, 5.2.3, and 5.3, upgrade the application tier technology stack from 12.2.1.3 to 12.2.1.4.

  • For the upgrade from releases 5.2.4 and 5.3.1, upgrade the application tier technology stack is not needed as it is already at version 12.2.1.4.

  • If upgrade from 12.2.1.2 to 12.2.1.3 was already done on the environment, then upgrading to 12.2.1.4 application tier technology stack is not supported and a fresh environment is needed.

For more information, see Oracle Fusion Middleware - Upgrade Common Tasks 12.2.1.4.0 and Upgrading Oracle Forms from a Previous 12c Release.

For more information, see:

Parent topic: Upgrading Oracle Thesaurus Management System to Release 5.4.0

Before You Start

Consider the following:

Parent topic: Upgrade and Configure the Application Tier Technology Stack

Identify a Single Account to Perform All Application Tier Installation Tasks

Install all application tier components using the same user account you had when you installed version 12.2.1.3.

The account must have administrator privileges on the server computer.

Parent topic: Before You Start

Gather Required Information to Upgrade the Application Tier Technology Stack

Have the following information ready.

Note:

A new ORACLE_HOME needs to be created, the 12.2.1.4 upgrade is an out-of-place upgrade.

The existing domains remain in the same place, FRDomain and OPADomain do not change their paths. The domain and component upgrade are in-place as the domain directory remains the same in the initial 12.2.1.3 ORACLE_HOME.

Note:

For OHS 12.2.1.3 or later on Windows, it is required to have both Microsoft Visual C++ 2010 Redistributable and Microsoft Visual C++ 2012 Redistributable installed. Otherwise, there will be errors when starting the ohs component and trying to access forms. For more information, see Oracle HTTP Server Start Failed With 'exit status = -1073741515' In New Installation of FMW 12.2.1.3 on Windows Server (Doc ID 2314112.1) on My Oracle Support.

These libraries may already be installed, In this case, there will be an error message when trying to install them.

Install the 12.2.1.4 Oracle WebLogic Server

  • Home directory path for FMW 12.2.1.4; for example: C:\Oracle12214\Middleware\Oracle_Home

  • Email address to receive the 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 FMW 12.2.1.4; for example: C:\ Oracle12214\Middleware\Oracle_Home

  • Email address to receive the 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 FMW 12.2.1.4; for example: C:\ Oracle12214\Middleware\Oracle_Home

Parent topic: Upgrade and Configure the Application Tier Technology Stack

Restart Computer and Stop All Servers

  1. Restart the computer before starting the upgrade to 12.2.1.4.
  2. Before starting the upgrade to 12.2.1.4, stop all servers and components.

    For FRDomian, make sure Admin Server, WLS_FORMS, WLS_REPORTS, OHS, report server instance, and Node Manager are stopped.

    For OPADomain, make sure Admin Server, managed server, and Node Manager are stopped.

Parent topic: Upgrade and Configure the Application Tier Technology Stack

Install Oracle Application Tier 12.2.1.4

Install Oracle WebLogic Server, Oracle Fusion Middleware Infrastructure Software, and Oracle Forms and Reports Server in the new 12.2.1.4 ORACLE_HOME.

  1. To install Oracle WebLogic Server, see Install Oracle WebLogic Server 12.2.1.4.
  2. To install Oracle Fusion Middleware Infrastructure Software, see Install the Oracle Fusion Middleware Infrastructure Software.
  3. To install Oracle Forms and Reports Server, see Install the Oracle Forms and Reports Servers.

Parent topic: Upgrade and Configure the Application Tier Technology Stack

Run Pre-Upgrade Readiness Check

To identify potential issues with the upgrade, Oracle recommends that you run a readiness check before you start the upgrade process. Be aware that the readiness check may not be able to discover all potential issues with your upgrade. An upgrade may still fail, even if the readiness check reports success.

The Upgrade Assistant readiness check performs a read-only, pre-upgrade review of your Fusion Middleware schemas and WebLogic domain configurations that are at a supported starting point. The review is a read-only operation.

The readiness check generates a formatted, time-stamped readiness report so you can address potential issues before you attempt the actual upgrade. If no issues are detected, you can begin the upgrade process. Oracle recommends that you read this report thoroughly before performing an upgrade.

Once the new 12.2.1.4 ORACLE_HOME is created and Oracle WebLogic Server, Oracle Fusion Middleware Infrastructure Software, and Oracle Forms and Reports Servers are installed, run a pre-upgrade readiness check. You must run this check separately for FRDomain and OPAdomain.

  1. Run the following command to start the pre-upgrade readiness check:

    <12.2.1.4_Oracle_Home>\oracle_common\upgrade\bin\ua.bat -readiness

    1. Select the Domain Based option and enter the domain location.

    2. Select the Include checks for all schemas and Include checks for all configurations check boxes.

  2. Enter the WebLogic domain directory where schemas and configurations will be checked. This will be the path to the domains directory from <12.2.1.3_Oracle_Home>. For example, C:\Oracle\Middleware\Oracle_Home\user_projects\domains\FRDomain.

  3. Check schemas and configuration in FRDomain.

    Schemas to be checked:

    • Oracle Platform Security Services – OPSS

    • Oracle Audit Services – IAU

    • Common Infrastructure Services – STB

    • Oracle WebLogic Server - WLS_RUNTIME

    Configuration to be checked:

    • System Components Infrastructure

    • Oracle HTTP Server

    • Oracle JRF

    • Common Infrastructure Services

    • Oracle Forms Services

    • Oracle Reports Services

  4. Check schemas and configuration in OPADomain.

    Schemas to be checked:

    • Oracle Platform Security Services – OPSS

    • Oracle Audit Services – IAU

    • Common Infrastructure Services – STB

    • Oracle WebLogic Server - WLS_RUNTIME

    Configuration to be checked:

    • System Components Infrastructure

    • Oracle HTTP Server

    • Oracle JRF

    • Common Infrastructure Services

    • Oracle Forms Services

  5. Enter the administrator database account credentials for checking the RCU OPSS schema. The account need to have DBA privileges (can be system account).

    Note:

    Click Connect to make sure the credentials you entered are valid.

  6. Enter the administrator database account credentials for checking account credentials for the RCU IAU and STB schemas. The account need to have DBA privileges (can be system account).

  7. In the Readiness Progress screen, check that all the components should have a green status – upgrade not necessary or ready for upgrade.

For OPADomain in the Readiness Progress screen all the components should have a green status – upgrade not necessary or ready for upgrade; except for Oracle Forms Services. The Oracle Forms Service component for OPADomain will be marked as Failure but this can be ignored as Oracle Forms Service is not a part of OPADomain.

Parent topic: Upgrade and Configure the Application Tier Technology Stack

Upgrade the Domain Schema

When upgrading the application technology stack from 12.2.1.3 to 12.2.1.4 version, the upgrade of the domain schema is not needed.

Parent topic: Upgrade and Configure the Application Tier Technology Stack

Run the Reconfiguration Wizard

Run the Reconfiguration Wizard For FRDomain

  1. Open a DOS prompt and run:

    <12.2.1.4_Oracle_Home>\oracle_common\common\bin\reconfig.cmd -log  <path_to_log_file>\FRDomain_log.txt -log_priority=ALL

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

Select Domain

  1. Select the FRDomain location; for example:

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

Database Configuration Type

  1. Select the RCU data check box under Specify AutoConfiguration Options Using.

  2. Make sure the RCU database is correct.

  3. Click Get RCU Configuration.

Component Datasources

  1. Select all RCUs.

  2. Click Next.

Advanced Configuration

  1. Select only the Topology check box in the Advanced Configuration in the Reconfiguration Wizard.

    Do not select the System Components check box. Those are automatically configured/upgraded by the Upgrade Assistant in the next steps.

Make a note of the FRDomain defaultCoherenceCluster port because for OPADomain a different port needs to be used. By default, it is 7574.

Note:

In the Configuration Summary, ignore the warning "CFGFWK-40326: Invalid coherence server address."

Run the Reconfiguration Wizard For OPADomain

  1. Open a DOS prompt and run:

    <12.2.1.4_Oracle_Home>\oracle_common\common\bin\reconfig.cmd -log  <path_to_log_file>\OPADomain_log.txt -log_priority=ALL

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

Select Domain

  1. Select the OPADomain location; for example:

    C:\Oracle\Middleware\Oracle_Home\user_projects\domains\OPADomain

Datasources

  1. Select the existing data sources.

Database Configuration Type

  1. Select the RCU data check box under Specify AutoConfiguration Options Using.

  2. Make sure the RCU database is correct.

  3. Click Get RCU Configuration.

Component Datasources

  1. Select all RCUs.

  2. Click Next.

Advanced Configuration

  1. Select all check boxes.

Default Coherence Cluster

  1. Use a different port number other than the one used for FRDomain. For example, 7575.

Domain Frontend Host

  1. Deselect the Configure Domain Frontend Host check box.

Parent topic: Upgrade and Configure the Application Tier Technology Stack

Upgrade the Forms Server

Start the upgrade assistant in the new 12.2.1.4 Oracle Home to upgrade the Forms installation.

  1. Run the following command:
    <12.2.1.4_Oracle_Home>\oracle_common\upgrade\bin\ua.bat
  2. Select the All Configurations Used by a Domain check box, and provide the FRDomain location.
  3. Upgrade the components in FRDomain:

    • System Components Infrastructure

    • Oracle HTTP Server

    • Oracle JRF

    • Oracle Forms Services

    • Oracle Reports Services

  4. In the Prerequisites screen, select all the check boxes.
  5. In the Examine screen, make sure all the checks have the status "ready for upgrade" or "upgrade not necessary".
  6. Click Upgrade.

Parent topic: Upgrade and Configure the Application Tier Technology Stack

Complete the Upgrade for FRDomain

Do the following:

Parent topic: Upgrade and Configure the Application Tier Technology Stack

Check EXTRA_JAVA_PROPERTIES for setDomainEnv.cmd

Check if setDomainEnv.cmd file from <FRDomain_Home>\bin contains Dforms.userid.encryption.enabled=true for EXTRA_JAVA_PROPERTIES. If it dose not contain, create the script setUserOverridesLate.cmd under <FRDomain_Home>\bin (this script is executed when startWeblogic.cmd is executed):

echo ""
echo "*****************************************************"
echo "** Executing setUserOverridesLate.cmd "
echo "*****************************************************"
rem specify additional java command line options for all servers
set EXTRA_JAVA_PROPERTIES =%EXTRA_JAVA_PROPERTIES% -Dforms.userid.encryption.enabled=true
echo "USER_MEM_ARGS=\"${USER_MEM_ARGS}\""
echo "EXTRA_JAVA_PROPERTIES=\"${EXTRA_JAVA_PROPERTIES}\""
echo ""
echo "*****************************************************"
echo "** End of setUserOverridesLate.cmd "
echo "*****************************************************"
echo ""

Parent topic: Complete the Upgrade for FRDomain

Run WLST to Provide Grant for Forms Application Keystore and Update OHS

  1. Start the FRDomain Node Manager.

    <FRDomain_Home>\bin\startNodeManager.cmd

  2. Start the FRDomain admin server.

    <FRDomain_Home>\bin\startWebLogic.cmd

  3. Run WLST.

    <12.2.1.4_ORACLE_HOME>\oracle_common\common\bin\wlst.cmd

  4. Connect to admin server.

    connect('adminserver_username','adminserver_password','t3://host_name:FRDomain_adminserver_port')

  5. Run the following WLST (online mode) commands to provide grants to the forms application or mbeans to access the Forms application keystore:
    grantPermission(codeBaseURL="file:${common.components.home}/../forms/provision/forms-config-mbeans.jar", permClass="oracle.security.jps.service.keystore.KeyStoreAccessPermission",permTarget="stripeName=formsapp,keystoreName=formsks,alias=*", permActions="*")
    grantPermission(codeBaseURL="file:${domain.home}/servers/${weblogic.Name}/tmp/_WL_user/formsapp_12.2.1/-", permClass="oracle.security.jps.service.keystore.KeyStoreAccessPermission", permTarget="stripeName=formsapp, keystoreName=formsks,alias=*",permActions="*")
  6. Run the following WLST (online mode) command for the OHS instance update:
    ohs_updateInstances()
  7. Exit WLST.
    exit()
  8. Stop the FRDomain admin server.

    <FRDomain_Home>\bin\stopWebLogic.cmd

  9. Stop the FRDomain Node Manager.

    <FRDomain_Home>\bin\stopNodeManager.cmd

Parent topic: Complete the Upgrade for FRDomain

Update OHS Instance Files

  1. Update the httpd.conf file to have only one Listen directive.

    Make sure the httpd.conf files have only one Listen directive for one specific port: Listen <machine_name>:<port_number>

    The httpd.conf files can be found under:

    • <FRDomain_Home>\config\fmwconfig\components\OHS\instances\ohs1\

    • <FRDomain_Home>\config\fmwconfig\components\OHS\ohs1\

  2. In the following ohs.plugins.nodemanager.properties files, replace '\' with '/' for the value of nm-wallet path to avoid "MALFORMED \UXXXX ENCODING" error when starting ohs1 instance:

    • <FRDomain_Home>\config\fmwconfig\components\OHS\ohs1\ohs.plugins.nodemanager.properties

    • <FRDomain_Home>\config\fmwconfig\components\OHS\instances\ohs1\ohs.plugins.nodemanager.properties

Parent topic: Complete the Upgrade for FRDomain

Start all components of FRDomain and OPADomain

To make sure the application technology stack upgrade was successful, start all components from FRDoamin (nodemanager, admin server, WLS_FORMS, WLS_REPORTS, and ohs1) and OPADomain (nodemanager, admin server, and managed server), except for the report server instance created for TMS 5.2.x/5.3 or OC 5.2.x.

Parent topic: Upgrade and Configure the Application Tier Technology Stack