Many customers are running their workloads on Oracle Cloud Infrastructure Classic (OCI-C), but the new Oracle Cloud Infrastructure (OCI) offers compelling benefits that customers should consider moving their workloads to the “gen 2 cloud“.  Additionally if the customer is not yet running SOA 12.2.1.3 or above, now is an ideal time to make the move.

A SOA implementation is typically large and serves mission critical requirements.  This means that a “side-by-side” migration is the best approach.  At a high-level the process is as follows:

• Discover/map the existing OCI-C deployment.  Oracle provides a set of tools to help in migrating workloads to OCI.  You can learn more about this at Upgrade to Oracle Cloud Infrastructure.
• Branch your SOA projects: SOA projects can be deployed into a new environment and they will be upgraded on the deployment.  However, a better approach is to branch your version control and upgrade the projects in JDeveloper.  You can then validate the project to catch any potential issues. Read the complete article here.

PaaS Partner Community

For regular information on Oracle PaaS become a member in the PaaS (Integration & Process) Partner Community please register here.

Blog Twitter LinkedIn Facebook Wiki

Technorati Tags: SOA Community,Oracle SOA,Oracle BPM,OPN,Jürgen Kress