1 Preparing for the Oracle Fusion Middleware Infrastructure Upgrade

The topics in this section provide a high-level overview of the steps you should perform to prepare for an upgrade.

1.1 Understanding the Starting Points for an Oracle Fusion Middleware Infrastructure Upgrade

The primary focus of the upgrade procedures in this guide is to upgrade an existing Application Server 11g domain and the Oracle Fusion Middleware component configurations in that domain to Oracle Fusion Middleware Infrastructure 12c (12.2.1).

You can upgrade to this version of Oracle Fusion Middleware Infrastructure from the following supported starting points:

  • Oracle Fusion Middleware Application Developer 11g (11.1.1.6. 11.1.1.7, 11.1.1.8, 11.1.1.9)

  • Oracle Fusion Middleware Infrastructure 12c (12.1.2 and 12.1.3).

Note:

If you are upgrading Oracle HTTP Server instances associated with an existing Application Developer 11g domain or instructions for upgrading a standalone Oracle HTTP Server, see Upgrading Oracle HTTP Server.

1.1.1 About Oracle Fusion Middleware Infrastructure 12c

Oracle Fusion Middleware Infrastructure distribution, which is available as part of the Oracle Fusion Middleware 12c (12.2.1) release, provides a set of technologies and components similar to those provided by the Oracle WebLogic Server and Application Developer installers in 11g.

For more information about Oracle Fusion Middleware Infrastructure, see About Oracle Application Server Infrastructure 12c in Understanding Interoperability and Compatibility.

1.1.2 Key Differences Between Application Developer 11g and Infrastructure 12c

Oracle Fusion Middleware Infrastructure 12c is similar to the 11g Application Developer installation, except for few differences listed in this section.

  • Infrastructure 12c Includes Oracle WebLogic Server
    The Application Developer 11g installation required two separate installations (Oracle WebLogic Server and then Application Developer to add the Oracle JRF libraries and components). In Oracle Fusion Middleware 12c, a fresh installation requires only the Oracle Fusion Middleware Infrastructure distribution, which contains both Oracle WebLogic Server and the required Java Required Files (JRF) technologies.
  • Database Schema Requirement for Infrastructure 12c
    Unlike the Application Developer 11g installation, the Infrastructure 12c installation requires you to create a set of required schemas in a supported database. In particular, you must use the 12c Repository Creation Utility (RCU) to create the required database schemas before you can configure the Oracle Fusion Middleware Infrastructure 12 c software.
  • Using an OID-based Policy Store
    If you are using an Oracle Internet Directory (OID)-based policy store in 11g, use the 12c Repository Creation Utility (RCU) to create the new 12c OPSS schema. In the Upgrade Assistant, select the OPSS schema; the Upgrade Assistant upgrades the OID-based policy store. You do not need to reassociate an OID-based policy store before upgrade.
  • Infrastructure 12c Domains Can Include Oracle HTTP Server
    In Oracle Fusion Middleware 11g, Oracle HTTP Server instances are typically configured in a separate Oracle instance directory outside the 11g Middleware home. However, in Oracle Fusion Middleware 12c, Oracle HTTP Server instances can be configured a part of an Oracle WebLogic Server domain, using the Oracle Fusion Middleware Configuration Wizard.

1.1.2.1 Infrastructure 12c Includes Oracle WebLogic Server

The Application Developer 11g installation required two separate installations (Oracle WebLogic Server and then Application Developer to add the Oracle JRF libraries and components). In Oracle Fusion Middleware 12c, a fresh installation requires only the Oracle Fusion Middleware Infrastructure distribution, which contains both Oracle WebLogic Server and the required Java Required Files (JRF) technologies.

Note that the upgrade procedure does not require the configuration of a new Oracle Fusion Middleware 12c domain. Instead, you use the Reconfiguration Wizard to upgrade the domain. For more information, see Understanding and Obtaining the Upgrade and Configuration Tools in Planning an Upgrade of Oracle Fusion Middleware.

1.1.2.2 Database Schema Requirement for Infrastructure 12c

Unlike the Application Developer 11g installation, the Infrastructure 12c installation requires you to create a set of required schemas in a supported database. In particular, you must use the 12c Repository Creation Utility (RCU) to create the required database schemas before you can configure the Oracle Fusion Middleware Infrastructure 12 c software.

Depending upon your requirements, you must install one or more of the following database schemas before you can upgrade to Oracle Fusion Middleware Infrastructure 12c:

  • The Service Table (STB) schema is a new schema required for all Oracle Fusion Middleware Infrastructure 12c installations. This schema enables a new 12c feature called Cross-Component Wiring. For more information, see Cross-Component Wiring in Administering Oracle Fusion Middleware. You must install this schema before upgrading to 12c.

  • The OPSS schema, which provides a database-based policy store for Oracle Platform Security Services.

    Table 1-1 provides an overview of the policy stores used in 11g and how to upgrade them.

    Table 1-1 Overview of Upgrading the Oracle Fusion Middleware 11g Policy Store

    If you are using... Then perform the following action: More Information

    Oracle Internet Directory (OID)-based policy store in 11g

    • Before the upgrade, use the 12c Repository Creation Utility (RCU) to create the new 12c OPSS schema.

    • In the Upgrade Assistant, select the OPSS schema; the Upgrade Assistant upgrades the OID-based policy store.

      Note:

      The 12c OPSS database schema is required only so you can reference the 12c schema during the reconfiguration of the domain. Your domain will continue to use the OID-based policy store after the upgrade.

    Database-based policy store and the OPSS schema

    Use the Upgrade Assistant to upgrade the existing 11g OPSS schema.

  • The IAU schema, which is used for the OPSS auditing capabilities.

    You might be required to create the IAU 12cschema, depending on whether or not you are using an Audit Data Store in 11g and the type of Audit Data Store you are using. For more information, see Table 1-2.

    Table 1-2 Overview of Upgrading the Oracle Fusion Middleware 11g Audit Store

    If you are using... Then perform the following action: More Information

    File- based audit store in 11g

    • Before the upgrade, create a new 12c IAU schema.

    Database-based audit store and the IAU 11g schema

    • Use the Upgrade Assistant to upgrade the existing 11g IAU schema, and then reference the upgraded 11g schema during the domain reconfiguration.

1.1.2.3 Using an OID-based Policy Store

If you are using an Oracle Internet Directory (OID)-based policy store in 11g, use the 12c Repository Creation Utility (RCU) to create the new 12c OPSS schema. In the Upgrade Assistant, select the OPSS schema; the Upgrade Assistant upgrades the OID-based policy store. You do not need to reassociate an OID-based policy store before upgrade.

Note:

The 12c OPSS database schema is required only so you can reference the 12c schema during the reconfiguration of the domain. Your domain will continue to use the OID-based policy store after the upgrade.

1.1.2.4 Infrastructure 12c Domains Can Include Oracle HTTP Server

In Oracle Fusion Middleware 11g, Oracle HTTP Server instances are typically configured in a separate Oracle instance directory outside the 11g Middleware home. However, in Oracle Fusion Middleware 12c, Oracle HTTP Server instances can be configured a part of an Oracle WebLogic Server domain, using the Oracle Fusion Middleware Configuration Wizard.

Oracle HTTP Server 11g instances are managed using the Oracle Process Manager and Notification Server (OPMN) management software. Optionally, the Oracle HTTP Server 11g instances can be "associated with" the WebLogic domain.

When configured as part of an Oracle Fusion Middleware Infrastructure domain, Oracle HTTP Server instances can be managed using Oracle Enterprise Manager Fusion Middleware Control and the Oracle WebLogic Scripting Tool (WLST). In Oracle Fusion Middleware 12c, the Node Manager agent is responsible for delegating and executing management requests to OHS instances.

For more information about the changes to the ways system components, such as Oracle HTTP Server, are configured and managed in Oracle Fusion Middleware 12c, as well as other key changes for Oracle Fusion Middleware 12c, see Understanding the Additional New Features for Oracle Fusion Middleware 12c.

For more information on upgrade the Oracle HTTP Server, see Upgrading Oracle HTTP Server.

1.2 Upgrading Security Store

Before upgrading the OPSS security store, it is important to back up the security store so that it can be recovered in case the upgrade fails.

For details about backing up the security store, see Backing Up and Recovering the OPSS Security Store.

The upgrade procedure varies depending on the type of security store you start from. The security store to be upgraded can be file-based, OID-based, or DB-based. Note that the procedures vary depending upon the type of source audit data store (file-based or DB-based).

1.3 Understanding the Standard Upgrade Topologies for Infrastructure

There are two upgrade topologies: Standard infrastructure upgrade topology and Infrastructure upgrade topology with Oracle HTTP Server.

Using the Oracle Fusion Middleware Application Developer 11g software, you can create a variety of production topologies to suit the needs of your applications, your organization, and your application users.

As a result, it is difficult to provide exact upgrade instructions for every possible Application Developer 11g installation. To solve this problem, this upgrade documentation provides detailed instructions for upgrading two typical Application Developer configurations. These typical topologies are referred to as the Oracle Fusion Middleware 12c standard upgrade topologies.

Specifically, for the purposes of this guide, it is assumed that you have used Oracle WebLogic Server and the Application Developer 11g software to configure a domain that contains a cluster of two managed servers, both of which are configured to support Oracle JRF and the deployment of Oracle ADF applications.

Your actual topology may vary, but the topologies described here provide an example that can be used as a guide to upgrade other similar Application Developer topologies.

This guide explains how to upgrade the following two specific upgrade topologies step-by-step:

1.3.1 Fusion Middleware Infrastructure Standard Upgrade Topology

Figure 1-1 shows the Oracle Fusion Middleware 11g Application Developer standard upgrade topology and the resulting Oracle Fusion Middleware 12c Infrastructure topology as it appears after you complete the upgrade procedures in this guide.

Figure 1-1 Infrastructure Upgrade Topology

Description of Figure 1-1 follows
Description of "Figure 1-1 Infrastructure Upgrade Topology"

All elements in this topology illustration are described in Table 1-3.

Table 1-3 Description of the Elements in the Infrastructure Standard Upgrade Topology

Element Description and Links to Additional Documentation

11g Application Developer Topology

This is the label for the left side of Figure 1-1. It shows a typical single-host topology created using the Oracle Fusion Middleware 11g Application Developer installer.

It consists of a single domain that contains a cluster of two managed servers and the Administration Server. It also has an optional file-based store or database with schemas.

This document describes, step-by-step, how to upgrade this topology to an equivalent topology created using the Oracle Fusion Middleware 12c Infrastructure distribution.

12c Infrastructure Standard Installation Topology

This is the label for the right side of the figure. It shows a typical single-host topology created using the Oracle Fusion Middleware 12c Infrastructure distribution.

Like the Application Developer 11g topology, it also consists of a single domain that contains a cluster of two managed servers and the Administration Server.

APPHOST

Standard term used in Oracle documentation referring to the machine that is hosting the application tier.

DBHOST

Standard term used in Oracle documentation referring to the machine that is hosting the database.

Note that for Application Developer 11g, a database is optional; for Oracle Fusion Middleware 12c, a database is required. For more information, see Database Schema Requirement for Infrastructure 12c.

File-Based Store

An XML, file-based security store. In 11g, you could use a file-base security store or a database-based security store.

However, in 12c, the file-based store is deprecated, and you must use the Oracle Platform Security Services (OPSS) schema in a supported database. The Reconfiguration Wizard automates the process of reassociating file-based stores to DB-based stores.

Database with Schemas

Represents a supported database, where the Oracle Fusion Middleware schemas have been created using the Repository Creation Utility (RCU).

WebLogic Domain

A logically related group of Java components (in this case, the administration Server, Managed Servers, and other related software components).

For more information, see What is an Oracle WebLogic Server Domain in Understanding Oracle Fusion Middleware.

Administration Server

The central control entity of a domain which maintains the domain's configuration objects and distributes configuration changes to Managed Servers.

For more information, see What is the Administration Server in Understanding Oracle Fusion Middleware.

Enterprise Manager

Oracle Enterprise Manager Fusion Middleware Control. This is the main tool that can be used to manage your domain.

For more information, see Oracle Enterprise Manager Fusion Middleware Control in Understanding Oracle Fusion Middleware.

Cluster

A collection of multiple WebLogic Server instances running simultaneously and working together.

For more information, see Understanding Managed Servers and Managed Server Clusters in Understanding Oracle Fusion Middleware.

Machine

Logical representation of the computer that hosts one or more WebLogic Server instances (servers). Machines are also the logical glue between WebLogic Managed Servers and the Node Manager; in order to start or stop a Managed Server with Node Manager, the Managed Server must be associated with a machine.

Managed Server

Host for your applications, application components, Web services, and their associated resources.

For more information, see Understanding Managed Servers and Managed Server Clusters in Understanding Oracle Fusion Middleware.

Oracle JRF

Oracle JRF (Java Required Files) consists of those components not included in the Oracle WebLogic Server installation and that provide common functionality for Oracle business applications and application frameworks.

JRF consists of several independently developed libraries and applications that are deployed into a common location. The components that are considered part of Java Required Files include Oracle Application Development Framework shared libraries and ODL logging handlers.

Infrastructure

Oracle Fusion Middleware 12c term (similar to Oracle JRF) that refers to the collection of services that include the following:

  • Metadata repository (MDS)

    This contains metadata for Oracle Fusion Middleware components, such as the Oracle Application Developer Framework.

    For more information, see What is the Metadata Repository in Understanding Oracle Fusion Middleware.

  • Oracle Application Developer Framework (ADF)

  • Oracle Web Services Manager (OWSM)

The Application Developer 11g topology is similar to the Oracle Fusion Middleware Infrastructure 12c topology, except for the differences described in Key Differences Between Application Developer 11g and Infrastructure 12c.

1.3.2 Fusion Middleware Infrastructure Standard Upgrade Topology with Oracle HTTP Server

Figure 1-2 shows the Oracle Fusion Middleware 11g Application Developer standard upgrade topology with Oracle HTTP Server and the resulting Oracle Fusion Middleware 12c Infrastructure topology as it appears after you complete the upgrade procedures in this guide.

Figure 1-2 Infrastructure Standard Upgrade Topology with Oracle HTTP Server

Description of Figure 1-2 follows
Description of "Figure 1-2 Infrastructure Standard Upgrade Topology with Oracle HTTP Server"

Most of the elements in this topology illustration are described in Table 1-3.

Additional elements and those different from Figure 1-1 are described in Table 1-4.

Table 1-4 Description of the Elements in the Infrastructure Standard Upgrade Topology with Oracle HTTP Server

Element Description and Links to Additional Documentation

11g Application Developer Topology with Oracle HTTP Server

This is the label for the left side of Figure 1-2. It shows a typical single-host topology created using the Oracle Fusion Middleware 11g Application Developer installer.

It consists of a single domain that contains a cluster of two managed servers and the Administration Server. It also has an optional file-based store or database with schemas.

Figure 1-2 also shows an Oracle HTTP Server instance as part of the 11g domain.

This document describes, step-by-step, how to upgrade this topology to an equivalent topology created using the Oracle Fusion Middleware 12c Infrastructure distribution.

12c Infrastructure Standard Installation Topology with Oracle HTTP Server

This is the label for the right side of the figure. It shows a typical single-host topology created using the Oracle Fusion Middleware 12c Infrastructure distribution.

Like the Application Developer 11g topology, it also consists of a single domain that contains a cluster of two managed servers and the Administration Server.

Figure 1-2 also shows an Oracle HTTP Server instance as part of the 12c domain.

Oracle HTTP Server associated with the domain

An Oracle HTTP Server 11g instance that has been configured to be associated with the Oracle WebLogic Server domain. In Oracle Fusion Middleware 11g, system component instance, such as Oracle HTTP Server, are configured with an Oracle Universal Installer-based configuration wizard and are managed using Oracle Process Manager and Notification Server.

Oracle HTTP Server

Unlike the Oracle HTTP Server 11g instance in the left side of the diagram, the Oracle HTTP Server 12c instance shown in the 12c topology is configured as part of the domain using the Oracle Fusion Middleware Configuration Wizard. It is managed using Oracle Enterprise Manager Fusion Middleware Control, the Oracle WebLogic Scripting Tool (WLST), and the Oracle WebLogic Server Node Manager software.

Note:

There are changes to way Oracle HTTP Server instances are created and managed in an Oracle Fusion Middleware 12c Oracle WebLogic Server domain. For more information, see Infrastructure 12c Domains Can Include Oracle HTTP Server.

1.4 Understanding the Additional New Features for Oracle Fusion Middleware 12c

Before you begin the upgrade to Oracle Fusion Middleware Infrastructure 12c, review the new features and changes available in Oracle Fusion Middleware 12c.

In particular, refer to the following sections in Understanding Oracle Fusion Middleware:

1.5 Flow Chart and Task Roadmaps for Upgrading to Oracle Fusion Middleware Infrastructure

The sections in this topic describe the high-level steps for upgrading the Oracle Fusion Middleware standard upgrade topology.

1.5.1 Flow Chart for Upgrading the Infrastructure Standard Upgrade Topologies

This topic contains a flow chart showing the high-level process flow for upgrading the standard infrastructure topologies.

Figure 1-3 Flow Chart of the Infrastructure Upgrade Steps

img/GUID-3F4F3E50-6784-445E-A2A8-CD73A3004915-default.png

1.5.2 Task Roadmap for Upgrading the Infrastructure Standard Upgrade Topologies

This topic describes the high-level tasks that must be completed to upgrade to Fusion Middleware Infrastructure 12c.

Table 1-5 Oracle Fusion Middleware Infrastructure Upgrade Roadmap

Task Description More Information

Review the new 12c concepts and perform common upgrade tasks.

Before planning your upgrade, you must review the 12c concepts, and common upgrade tasks.

Planning an Upgrade of Oracle Fusion Middleware

Understanding the Starting Points for an Oracle Fusion Middleware Infrastructure Upgrade

Understanding the Standard Upgrade Topologies for Infrastructure.

Execute a compete backup of your existing 11g environment.

The backup is important because the upgrade process will reconfigure your existing domain directories.

Completing the Pre-Upgrade Tasks for Infrastructure (Required)

Install Infrastructure 12.2.1 in a new Oracle Home.

Install Oracle Fusion Middleware Infrastructure 12c in a new Oracle Home on the host where you installed Oracle Fusion Middleware Application Developer 11g.

If the 11g environment includes Oracle HTTP Server instances that are associated with the domain, then Install Oracle HTTP Server 12c in the same Oracle home as the Infrastructure.

Installing Oracle Fusion Middleware Infrastructure on APPHOST.

Installing Oracle HTTP Server.

Shut down the 11g environment.

Stop the Administration Server and all the Managed Servers.

Stopping Servers and Processes.

Run the Upgrade Assistant to upgrade the database schemas.

Run the Upgrade Assistant to upgrade your existing 11g schemas to 12c.

  

Run Repository Creation Utility (RCU) to create the 12c schemas. (For 11g to 12c upgrades only.)

Unlike Oracle Fusion Middleware 11g, you cannot configure an Oracle Fusion Middleware 12c domain without installing the required schemas in a supported database.

Creating the Required Schemas Before You Upgrade.

Run the Reconfiguration Wizard to reconfigure the 11g domain and Node Manager (if needed).

After upgrading the 11g schemas, you must run the Reconfiguration Wizard to reconfigure your existing 11g domain and Node Manager.

Using the Reconfiguration Wizard to Reconfigure the Domain

Run the Upgrade Assistant to upgrade domain configurations.

Use the Upgrade Assistant to upgrade any WebLogic component configurations.

 Using the Upgrade Assistant to Upgrade Component Configurations

Perform the required post-upgrade tasks.

Perform the required post-upgrade tasks like verifying the upgrade and deployed applications.

Tasks to Perform After Upgrade

1.6 About Upgrading Oracle HTTP Server

This guide explains how to upgrade Oracle HTTP Server 11g instances that have been configured so they are "associated with" an Oracle WebLogic Server domain. The upgrade is performed as you are upgrading the domain to which the Oracle HTTP Server has been associated.

To upgrade a standalone Oracle HTTP Server instance (one that is not associated with an 11g domain) refer to Upgrading Oracle HTTP Server.

1.7 Upgrading Custom Applications Using Oracle JDeveloper 12c

If you have deployed custom applications to an Oracle Fusion Middleware Application Developer 11g domain, then the application deployments should function as they did in Oracle Fusion Middleware 11g after the upgrade procedure is complete. However, if you want to take advantage of new Oracle Application Development Framework (Oracle ADF) 12c features, download and install Oracle JDeveloper 12c.

For more information, see Installing Oracle JDeveloper.

To test your 11g applications in preparation for an upgrade to Oracle Fusion Middleware Infrastructure 12c, open your existing Oracle JDeveloper 11g projects in Oracle JDeveloper 12c. Oracle JDeveloper migrates the projects to 12c . You can then test your applications with the embedded application server that is available from within Oracle JDeveloper. After you have reviewed and optionally modified your applications in Oracle JDeveloper 12c, upgrade the Application Developer 11g domain to Oracle Fusion Middleware Infrastructure 12c and redeploy the applications.

For more information about migrating your applications, see Migrating From a Previous Version to Oracle JDeveloper in Installing Oracle JDeveloper.