Understand how your pre-upgrade environment will be affected by the upgrade.
When upgrading your existing SOA Suite 11g or 12c environment to SOA Suite and Business Process Management 12c (126.96.36.199), 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 (188.8.131.52) Oracle home binaries are upgraded "out of place" as the binaries are installed in a new directory.
The upgrade to 12c (184.108.40.206) 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 ( WebLogic Server and JRF) 12c (220.127.116.11) and the Oracle SOA Suite and Business Process Management 12c (18.104.22.168) distribution binaries in a new Oracle home. The upgrade of binaries is considered "out of place" as the existing binaries are not overwritten.
Schemas - Upgraded In Place
The schemas are upgraded "in place" which means that the Upgrade Assistant updates and overwrites the existing 11g or 12c 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 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 provide the location of the existing 11g or 12c SOA domain and this domain will be reconfigured to point to the new SOA 12c (22.214.171.124) home directory.
Domain Component Configuration - Upgraded In Place
After the reconfiguration of the existing SOA domain, the Upgrade Assistant is used again to upgrade any remaining domain component configurations that require an upgrade in the new SOA 12c (126.96.36.199) home directory.
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 in Planning an Upgrade of Oracle Fusion Middleware
Verify that your pre-upgrade environment is at a supported version before an upgrade.
You can upgrade to Oracle SOA Suite and Business Process Management 12c (188.8.131.52) from the following production starting points:
SOA Suite and Business Process Management 12c (12.1.3), 12c (184.108.40.206) and 12c (220.127.116.11)
SOA Suite 11g (18.104.22.168, 22.214.171.124)
Note:If you are running SOA 11g (126.96.36.199) or earlier, you must first upgrade to SOA 11g (188.8.131.52 or 184.108.40.206) 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 (220.127.116.11) upgrade documentation library.
Read and understand how all of the components within your pre-upgrade domain will interact with the upgraded 12c (18.104.22.168) components.
Before you begin the upgrade process from SOA Suite and BPM 11g to 12c (22.214.171.124) 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 Middleware12c (126.96.36.199). There are other restrictions on the components that can be upgraded to12c (188.8.131.52) and you need to be sure that you have reviewed this information carefully before you proceed with the upgrade.
Review the domain upgrade restrictions before starting the upgrade.
Some domains cannot be upgraded to 12c (184.108.40.206) 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 12c (220.127.116.11).
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 (18.104.22.168). If you want to include SOA Core Extension in your 12c (22.214.171.124) 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 to12c (126.96.36.199)
If your pre-upgrade domain includes the Cloud Adapters Pack, you cannot upgrade to 12c (188.8.131.52).
If your pre-upgrade domain includes Oracle Enterprise Repository (OER), you cannot upgrade to 12c (184.108.40.206).
Your actual topology may vary, but the topologies described in this guide can be used to upgrade similar SOA Suite component 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?
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:|
|Oracle SOA Suite and Business Process Management (BPM) 11g||Upgrading SOA Suite and Business Process Management from 11g|
|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 Oracle SOA Suite with Oracle Business Activity Monitoring from 11g|
|Oracle SOA Suite with Oracle Business Activity Monitoring (BAM) 12c||Upgrading Oracle SOA Suite with Business Activity Monitoring from a Previous 12c Release|
|Domain with Oracle Business Activity Monitoring 11g Only||You cannot upgrade a BAM-only domain, but you can Import/Export BAM objects to 12c.|
|Oracle Service Bus (OSB) 11g without SOA Suite
NOTE: Oracle Service Bus (OSB) 11g with SOA Suite will follow the standard upgrade procedures.
|Upgrading an Oracle Service Bus 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 — You must uninstall AIAFP 11g or SOA Core Extension to upgrade.|