The Integration blog covers the latest in product updates, best practices, customer stories, and more.
-
Integration
May 2, 2019
Moving SOA to Oracle Cloud Infrastructure
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.
- Prepare OCI to run PaaS: There are some prerequisites that need to be completed which I talk about in Getting ready to Run SOA on Oracle Cloud Infrastructure with Terraform
- Provision the new SOACS environment on OCI.
- Migrate your Weblogic configurations: A great option for this which I'll talk about in a bit more detail below is Myst, by Rubicon Red.
- Deploy your composites into the new environment
- Test your new deployments
- Switch over your routing to the new services
- Decommission your old environment on OCI-C
Weblogic configurations can be quite extensive with SOA installations, from JCA Adapters, to JMS Queues etc. Reconfiguring a new Weblogic instance can be quite involved.
To make this process easier, Rubicon Red, an Oracle Platinum Partner, provides Myst, which is a cloud platform dedicated to managing SOA Configurations throughout the lifecycle.
Oracle customers can get a free trial at https://www.myst.cloud/
Once you sign up for the platform, you can quickly use it to connect to your existing SOA Suite Cloud Service instance and discover all of your configurations. Using Myst, you can then connect to your new environment and re-configure it to match your existing environment. Of course if you need to change some of the details due to deltas in your new environment, you can do that as well.
Myst will also help you maintain your configurations and catch any sort of configuration drift.
There may be ways to work with WLST and other mechanisms to automate this yourself, but Myst provides a great platform to manage both SOACS and SOA Suite on-premises instances.
If you are running SOA Cloud Service on OCI-C, now is the time to move to OCI. If you are not yet running SOA Cloud Service 12.2.1.3 or above, then now is the time to upgrade and if that means moving to OCI, then you can solve both within one project and Myst will help make this a smoother transition.