Oracle SOA Suite - Version 220.127.116.11.0 and later Information in this document applies to any platform.
The purpose of this document is to provide a complete summary view of the upgrade process to SOA 12c including tips / tricks that we pick up along the way. Please scroll to the bottom of the document for specific product notes and known issues.
Note: As more customers go through the upgrade process we will learn more and update this document accordingly. It is not guaranteed to cover the specifics of your situation.
Note: If you have configured a custom trust keystore in EM 11g, please review <Document 1961846.1> before proceeding with the upgrade as there is a known OWSM issue you can avoid.
Note: If you are trying to upgrade a domain that was originally created using T2P (cloning) prior to 18.104.22.168 then you must do the following:
- Upgrade the original source domain to 22.214.171.124
- Recreate the cloned domain from the 126.96.36.199 source
- Upgrade the cloned domain to 12.1.3
Note: Any modifications made to the configuration of OOTB SOA Data Sources will be reset by the upgrade tools so make note of what changes were made in 11g so they can be manually re-applied after the upgrade.
Note: Before upgrading take a moment to check your config.xml soa-infra and UMS related deployments. If they have sub-deployments listed in the 11g config.xml you can anticipate post upgrade errors during server startup that will require manual intervention. For soa-infra we know that the sub-deployment '/integration/services/CompositeMetadataService' will need to be removed post upgrade and for UMS it is recommended to follow the instructions in <Document 2016656.1>.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!