Back to Blog

Oracle Cloud Infrastructure: Classic to Gen2 with Myst

Alistair Palmer

Simplify the migration from OCI Classic to OCI

Introducing support for an Oracle Cloud Infrastructure Provider inside MyST to make migrating to OCI simple.

DECLARATIVE PLATFORM DESIGN

Design your OCI Platform

Provide your Oracle Cloud Credentials and select the Region. Let Myst take care of the rest. Myst asks you to provide the following metadata:

  1. A logical name for your Oracle Cloud Infrastructure provider
  2. Region
  3. Tenancy OCID
  4. User OCID
  5. Populate 1 or more Key Pairs
Model the Oracle Cloud Infrastructure metadata to accelerate OCI Gen2 provisioning

Further, Myst also provides an out of the box SOA Cloud Service template. This will help to standardize your SOA Cloud Service instances as well as accelerating provisioning an OCI based SOA Cloud Service.

PROVISION OCI FOR SOA CLOUD SERVICE

Upgrade your Classic SOA Cloud Service to OCI

Don't rely on scripts and manual changes. With Myst you can quickly provision OCI compute, network, database and storage all from the one blueprint. Myst also provisions SOA Cloud Service on the newly provisioned cloud infrastructure. Here is a brief list of everything that is created under the covers:

  1. Compartments
  2. VCN
  3. Internet and NAT Gateway
  4. Route tables
  5. Subnets
  6. Security lists and firewall rules
  7. Compute Instance
  8. Database Instance

Learn move about the high level process and some of the key considerations such as migrating your configuration, or upgrading and redeploying SOA composites on the Oracle Blog at https://blogs.oracle.com/integration/moving-soa-to-oci

Photo by Alistair MacRobert on Unsplash

Share on social media: 

More from our Blog

Myst Studio 6.6.0-rc11

Release pipeline bug fixes. Support for WebCenter Enterprise Capture. Improved support for Vanilla WebLogic. Misc regressions and improvements.

Read Story

Myst Studio 6.6.0-rc10

Added support for ODI 12.1.3 provisioning and deployments and support for SOA/OSB/ESS 12.1.3 provisioning (RCU) on Amazon RDS databases.

Read Story

Myst Studio 6.6.0-rc9

Fixed a regression caused by 6.6.0-rc7 where jsonpayload was only passed when a job parameter was defined. In 6.6.0-rc6 and earlier, no job parameter was required.

Read Story

Connect with the myst community on our slack channel.

Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa.
We will never share your email address with third parties.
Join Community