X

News, tips and technical guidance to help you run Oracle E-Business Suite on Oracle Cloud.

EBS to OCI Manual Migration Documents Available

Terri Noyes, and Robert Farrington

We are pleased to announce the availability of two documents that can be used as the basis for you to develop your own manual procedures for migrating Oracle E-Business Suite (EBS) on-premises Linux environments to Oracle Cloud Infrastructure (OCI), just for those situations when Oracle E-Business Suite Cloud Manager cannot be used.

Examples of cases that may require a manual migration method include when:

  • There is no direct connectivity between your on-premises and Cloud environments.
  • Your database is extremely large and you do not want to transfer it over the network.
  • You wish to preserve an on-premises application tier configuration that is not yet supported by Cloud Manager.

 

Where Can I Get the Documents?

The two documents are available on My Oracle Support:

The procedures provided in thse documents comply with our reference document, Standards Used by the Oracle E-Business Suite Cloud Manager for Provisioning Oracle E-Business Suite on Oracle Cloud Infrastructure (MOS Note 2656874.1).

What Are the High Level Migration Steps?

When following either of the above documents, you will perform these high level steps to move your EBS Release 12.2 environment from on-premises to OCI and VM DB Systems:

  1. Prepare the on-premises Oracle E-Business Suite application tier.
  2. Create a database instance on an Oracle Cloud Infrastructure VM DB System.
  3. Clone and configure an EBS database tier on the VM DB System instance.
  4. Create a Compute Cloud instance to host the EBS application tier.
  5. Configure the EBS application tier on the Compute Cloud Service instance.
  6. Deploy and configure an OCI load balancer (optional).
  7. If not using a load balancer, configure Transport Layer Security (TLS) and web entry point access.
  8. Configure secure access for an Oracle WebLogic Server admin port.
  9. Configure forms and concurrent processing for Oracle RAC (if applicable).
  10. Apply latest Quarterly Database Bundle Patch (optional but recommended).

What's Supported in a Manual Migration?

The above two documents are supported as written. We encourage you to adapt these documents as the basis for your own efforts, to take advantage of the standards and best practices they promote. However, be aware that Oracle is unable to provide direct support for your custom procedures. Consequently, when implementing your own procedures you should always undertake trial runs to ensure that the migrated environment meets your operational requirements.

Oracle will support the resulting EBS on OCI environments provided they meet the respective requirements listed in:

What If the On-Premises Source is Non-Linux?

If you are currently running EBS on an on-premises platform other than Linux, you will want to review articles from our platform engineering team such as the latest, EBS 12.2 Cross Platform Migration to OCI with 19c Now Certified.

For the full list of documents applicable to platform migration use cases, refer to Section 4.3.2 Migrating Oracle E-Business Suite from a Non-Linux Platform On-Premises to Linux in Getting Started with Oracle E-Business Suite on Oracle Cloud Infrastructure (MOS Note 2517025.1).

How Can I Ensure Adequate Performance?

When migrating your EBS system from on-premises to OCI, it is essential to ensure that operational performance will continue to meet your requirements. We recommend that before you migrate your production environment, you first migrate a test environment where you can conduct benchmark tests to simulate expected workloads and verify performance. For more information, see Performance Best Practices for Oracle E-Business Suite on Oracle Cloud Infrastructure and On-Premises (MOS Note 2528000.1).

References

Related Articles

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.