1 Introduction to Oracle SOA Suite and Business Process Management Upgrade
- Understanding the Oracle SOA Suite and Business Process Management Upgrade to 12c
- Understanding the Starting Points for a SOA Suite 12c (12.2.1) Upgrade
- Understanding the Interoperability and Compatibility Restrictions Before You Upgrade
- Understanding SOA Domain Upgrade Restrictions
- Understanding the Standard SOA Upgrade Topologies
- Understanding the SOA Suite and BPM Upgrade Process Flow
- Understanding the SOA Suite and BPM Upgrade Procedures
- Understanding How to Use this Guide for Your Upgrade
There are different upgrade paths depending on what is in your pre-upgrade environment. This guide covers all of the supported upgrade paths, so it is important that you understand which procedures to follow.
1.1 Understanding the Oracle SOA Suite and Business Process Management Upgrade to 12c
When upgrading your SOA Suite 11g environment to SOA Suite and Business Process Management 12c (12.2.1), you should understand how your pre-upgrade environment will be affected by the upgrade. For example, schemas and domain directory upgrades are performed "in place" which updates the existing 11g files during the upgrade. The 12c (12.2.1) Oracle Home binaries are upgraded "out of place" as the binaries are installed in a new directory.
The upgrade to 12c (12.2.1) includes the midtier and the schemas. You cannot perform a midtier-only or schema-only upgrade.
The list below describes how the upgrade is performed for the following Infrastructure and SOA Suite components:
-
Oracle WebLogic Server, JRF and SOA Oracle Home Binaries - Upgraded Out of Place
You will install the Oracle Infrastructure 12c (12.2.1) (which includes WebLogic Server and JRF) and SOA Suite and Business Process Management 12c (12.2.1) distribution binaries in a new Oracle home. The upgrade of binaries is considered "out of place" as the 11g binaries are not overwritten.
-
Schemas - Upgraded In Place
The 11g schemas are upgraded to 12c "in place" which means that the Upgrade Assistant updates and overwrites the schemas during the upgrade process. The servers must be down during this process.
-
Instances - Migrated during the schema upgrade
The upgrade of active and closed instances from 11g to 12c happens automatically as part of the schema upgrade. You can manage the upgrade using administration scripts.
-
Domain Directory Reconfiguration - Upgraded In Place
The existing SOA domain is upgraded "in place". During the upgrade you will identify the location of the 11g SOA domain and the 11g domain will be reconfigured to point to the new SOA 12c (12.2.1) home directory.
-
Domain Component Configuration - Upgraded In Place
After the reconfiguration of the 11g SOA domain, the Upgrade Assistant is used again to upgrade any remaining domain component configurations that require an upgrade in the new SOA 12c (12.2.1) home directory.
Note:
Oracle recommends that you perform your domain upgrades in place. However, if an out-of-place domain upgrade is required, see "Performing an Out-of-Place Domain Directory Upgrade".
1.2 Understanding the Starting Points for a SOA Suite 12c (12.2.1) Upgrade
You can upgrade to Oracle SOA Suite and Business Process Management 12c (12.2.1) from the following production 11g starting points:
-
SOA Suite and Business Process Management 12c (12.1.3)
-
SOA Suite 11g (11.1.1.9, 11.1.1.7, and 11.1.1.6)
-
SOA Suite 11g (11.1.1.5) or earlier - Not Supported
If you are running SOA 11g (11.1.1.5) or earlier, you must first upgrade to SOA 11g (11.1.1.6 or 11.1.1.7) before you can upgrade. For more information, see Oracle® Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter Portal, and ADF in the Oracle Fusion Middleware 11g (11.1.1.7) upgrade documentation library.
1.3 Understanding the Interoperability and Compatibility Restrictions Before You Upgrade
Before you begin the upgrade process from SOA Suite and BPM 11g to 12c, you must read and understand how all of the components within your 11g domain will be impacted by the upgrade. Understanding Interoperability and Compatibility provides a detailed matrix of which components can and cannot be upgraded together. In general, you cannot upgrade a domain that contains components that are not yet available in Oracle Fusion Middleware 12c (12.2.1). There are other restrictions on the components that can be upgraded to 12c (12.2.1) and you need to be sure that you have reviewed this information carefully before you proceed with the upgrade.
1.4 Understanding SOA Domain Upgrade Restrictions
Some domains cannot be upgraded to 12c (12.2.1) because of known limitations and configuration changes from previous Fusion Middleware releases. Review the following to ensure your domains are not impacted by these restrictions. Domains that are impacted by these restrictions cannot be upgraded.
DO NOT ATTEMPT TO UPGRADE A DOMAIN THAT IS UNSUPPORTED.
-
Domains that include SOA Core Extension cannot be upgraded in–place to 12.2.1.
If your pre-upgrade environment contains SOA Core Extension, then you cannot upgrade to this release of Oracle Fusion Middleware. An upgrade of SOA Core Extension is not supported in 12c (12.2.1). If you want to include SOA Core Extension in your 12.2.1 domain, you will have to manually migrate the files. Contact Oracle Support for more information.
-
Domains that include the Cloud Adapters Pack should not be upgraded to 12.2.1
If your 12.1.3 domain includes the Cloud Adapters Pack, you cannot upgrade to 12.2.1.
- Domains that include Oracle Enterprise Repository cannot be upgraded to 12.2.1
If your 12.1.3 domain include Oracle Enterprise Repository (OER), you cannot upgrade to 12.2.1.
1.5 Understanding the Standard SOA Upgrade Topologies
This upgrade documentation provides detailed instructions for upgrading two typical SOA Suite configurations. These topologies are referred to as the Oracle Fusion Middleware 12c standard upgrade topologies. Specifically, for the purposes of this guide, a standard installation topology consists of a WebLogic Server domain that contains an Administration Server and a cluster containing two Managed Servers or a standalone domain.
A standalone domain is a container for system components, such as Oracle HTTP Server. It has a directory structure similar to an Oracle WebLogic Server domain, but it does not contain an Administration Server or Managed Servers. It can contain one or more instances of system components of the same type, such as Oracle HTTP Server, or a mix of system component types. For more information on the standalone topology, see What Is a Standalone Domain?
Your actual topology may vary, but the topologies described in this guide provide an example that can be used as a guide to upgrade similar SOA Suite component topologies. For more information on the standard topologies and building an enterprise deployment, see Planning an Installation of Oracle Fusion Middleware.
For more information on setting up the 12c SOA Suite topologies, see:
1.6 Understanding the SOA Suite and BPM Upgrade Process Flow
This section describes the high-level steps for upgrading the Oracle Fusion Middleware SOA Suite:
1.7 Understanding the SOA Suite and BPM Upgrade Procedures
Table 1-1 Task Descriptions for Upgrading Oracle SOA Suite
| Description | More Information |
|---|---|
|
Review the Oracle Fusion Middleware 12c Concepts Guide and the Planning an Upgrade Guide before you begin the upgrade. These guides provide important information about upgrading to Fusion Middleware12c. You should understand the new 12c terminology changes and new requirements. |
See Understanding Oracle Fusion Middleware |
|
Perform ALL applicable pre-upgrade tasks for the Oracle Fusion Middleware environment such as creating a complete backup, reassociating file-based security stores, and verifying system requirements. |
|
|
Perform all of the required pre-upgrade tasks for the components you are upgrading. |
For all required pre-upgrade tasks, see the Oracle Fusion Middleaware 12c Pre-Upgrade Checklist. For SOA-specific pre-upgrade tasks, see Performing SOA-Specific Pre-Upgrade Tasks For SOA domains that include Oracle BAM, see Performing the Pre-Upgrade Tasks for Oracle BAM When upgrading Oracle Service Bus (with or without Oracle SOA), see Performing Pre-Upgrade Tasks for Oracle Service Bus (OSB) |
|
You must install Fusion Middleware Infrastructure 12c (12.2.1) in a NEW Oracle home on the same host as the 11g production deployment before you begin the upgrade. In 12c, Oracle home is used to describe the 11g Middleware home. |
See Installing and Configuring the Oracle Fusion Middleware Infrastructure NOTE: Install but do not use the Configuration Wizard to configure the domain. You will use the Reconfiguration Wizard during the upgrade. |
|
Install SOA Suite and Business Process Management 12c (12.2.1) and any integrated SOA-integrated distributions (Oracle HTTP Server, Oracle Service Bus, etc) in your newly created Oracle home. |
See Installing Oracle SOA Suite and Business Process Management 12c NOTE: You must install the Fusion Middleware 12c (12.2.1) distributions for each SOA-integrated product you are upgrading. For example, if you are upgrading a SOA 11g environment with Oracle Service Bus, you must acquire the Oracle Service Bus 12c (12.2.1) distribution as well as the Oracle SOA Suite and BPM 12c (12.2.1) distribution. A complete list of distributions is provided in Planning an Installation of Oracle Fusion Middleware. |
|
Shut down the 11g Environment (stop all Administration and Managed Servers) |
|
|
Launch the 12c (12.2.1) Repository Creation Utility (RCU) and create the new required 12c schemas. |
See Creating the Required SOA Schemas Before You Upgrade from 11g |
|
Run the Upgrade Assistant to upgrade the 11g database schemas and to upgrade all active (in flight) instance data to 12c (12.2.1). |
See Upgrading Schemas with the Upgrade Assistant NOTE: The upgrade of active instance data is started automatically when running the Upgrade Assistant. Once the data is successfully upgraded to the new 12.2.1 environment, you can close the Upgrade Assistant. The closed instances will continue to upgrade through a background process. For more information, see Administering and Monitoring the Upgrade of SOA Instances . |
|
You can manage and administer the ongoing upgrade of closed instances using the administration SQL scripts or Oracle Fusion Middleware Enterprise Manager Control. |
See Administering and Monitoring the Upgrade of SOA Instances . |
|
NOTE: If the 11g SOA domain that you are upgrading includes Oracle Business Activity Monitoring (BAM), you must complete all of the BAM-specific pre-upgrade tasks before you run the Reconfiguration Wizard. If you do not complete these steps before you attempt to run the Reconfiguration Wizard, then the upgrade will fail. |
See Upgrading SOA with Oracle Business Activity Monitoring (Oracle BAM) NOTE: Business Activity Monitoring (BAM) has been completely redesigned in 12c, and requires additional steps before reconfiguring the domain and after the upgrade. |
|
Run the Reconfiguration Wizard to reconfigure the domain and node manager. |
See Reconfiguring the Domain Using the Reconfiguration Wizard |
|
Run the Upgrade Assistant (again) to upgrade domain configurations. |
See Upgrading the Domain Component Configurations Using the Upgrade Assistant |
|
Perform the required post-upgrade configuration tasks (if needed). |
|
|
Start the Administration and Managed Servers and node manager. |
|
|
Make sure that all of the upgraded components are working as expected. |
1.8 Understanding How to Use this Guide for Your Upgrade
There are different upgrade paths depending on what is in your pre-upgrade environment. This guide covers all of the supported upgrade paths, so it is important that you understand which procedures to follow.
The following table describes the procedures you will use based on your pre-upgrade environment. If your pre-upgrade environment includes other Oracle Fusion Middleware components, such as OracleWebCenter, you must refer to the component-specific upgrade guide for more information. For a complete list of upgrade guides available for this release, see Oracle Fusion Middleware 12c Upgrade Documentation .
| If your pre-upgrade environment includes... | Refer to these upgrade procedures: |
|---|---|
| Required for All Upgrades:
All upgrades must first complete the required pre-upgrade tasks for Oracle Fusion Middleware AND the component-specific upgrade tasks documented for each upgrade path. Failure to complete the pre-upgrade tasks may result in a failed upgrade. |
Oracle Fusion Middleware Pre-Upgrade Checklist |
| Oracle SOA Suite and Business Process Management (BPM) 11g | Upgrading to SOA Suite and Business Process Management 12c (12.2.1) |
| Oracle SOA Suite and Business Process Management (BPM) 12c | Upgrading Oracle SOA Suite and Business Process Management from a Previous 12c Release |
| Clustered SOA and BPM Environment | Upgrading a Clustered SOA Environment |
| Oracle SOA Suite with Oracle Business Activity Monitoring (BAM) 11g | Upgrading SOA with Oracle Business Activity Monitoring (Oracle BAM) |
| Oracle SOA Suite with Oracle Business Activity Monitoring (BAM) 12c | Upgrading Oracle SOA Suite with Business Activity Monitoring (BAM) 12c from a Previous 12c Release |
| Domain with Oracle Business Activity Monitoring 11g Only | Not Supported — You cannot upgrade a BAM-only domain, but you can Import/Export BAM objects to 12c.
Exporting All Oracle BAM 11g Artifacts from the Existing Domain |
| Oracle Service Bus (OSB) 11g with SOA Suite | Upgrading Oracle Service Bus |
| Oracle Service Bus (OSB) 11g without SOA Suite | Upgrading an OSB Domain (Without SOA) |
| Oracle User Messaging Service 11g or 12c | Performing pre-Upgrade Tasks for User Messaging Service (UMS) |
| SOA Domain with AIAFP 11g or SOA Core Extension 12c | Not Supported |