View a markdown version of this page

Migrating Oracle SOA Suite 12c to AWS - Deploying Oracle SOA Suite 12c on AWS
Migrating the web and application tierMigrating the Oracle MDS repository

This whitepaper is for historical reference only. Some content might be outdated and some links might not be available.

Migrating Oracle SOA Suite 12c to AWS

When migrating Oracle SOA Suite 12c to AWS, consider the architecture described in this whitepaper, perform a trial migration and validate it, then iterate one or two times before migrating to production. Review the migration approach to ensure the least amount of downtime for the business during the production cutover. Before starting the migration, you must create an Amazon Virtual Private Cloud (Amazon VPC) with the required subnets on AWS. You must also set up network connectivity from on-premises to AWS using a VPN connection or AWS Direct Connect.

The following sections describe the process to migrate the various Oracle SOA Suite 12c components to AWS.

Migrating the web and application tier

You can migrate the Oracle SOA Suite 12c Web and Application tier components to AWS using the following approaches.

VM or server level migration

You can migrate or clone the entire virtual machine (VM) or server hosting the Oracle SOA Suite 12c components using tools such as AWS Application Migration Service (AWS MGN), the next generation of CloudEndure Migration. The following steps provide an overview of the migration process:

  1. Use AWS MGN (or a similar tool) to migrate the servers or VMs from the on-premises deployment. AWS MGN ensures the data is synchronized in real time and minimizes the cutover window.

  2. Use Amazon EFS as the shared storage mounted on the application tier nodes. Reconfigure Oracle WebLogic Server to use Amazon EFS for shared data such as the artifacts for Oracle Fusion Middleware, including Oracle home, Domain Home, Application Home, JTA Transaction Logs, and JMS Store for persisting the JMS messages.

  3. Migrate the Oracle Metadata Services (MDS) Repository as described in the Migrating the Oracle MDS repository section of this document.

  4. Update the metadata data source in WebLogic with the new database connection information of the Oracle Metadata Services (MDS) Repository.

  5. Open the WebLogic Administration Console to verify that the Domain, cluster, and managed servers are configured correctly.

  6. Configure the Web servers and ELB (Network Load Balancer and Application Load Balancer).

  7. Start the servers and test.

Migration using Oracle Fusion Middleware utilities

The second option is to migrate the Oracle SOA Suite 12c components using the built-in Oracle Fusion Middleware utilities such as copy binary/copy config, and paste binary/paste config. The following steps provide a high-level overview of migration. For more details, refer to Overview of Procedures for Moving from a Source to a Target Environment on the Oracle Help Center.

  1. Launch the EC2 instances with Oracle Linux or a certified operating system for hosting the Oracle SOA Suite 12c components.

    1. Apply the required prerequisite patches for Oracle SOA Suite 12c, including the security patches.

    2. Create an Amazon EBS-backed Linux Amazon Machine Image (AMI) and preserve the copy for future use.

  2. Install a new Oracle Home. You can also copy the Oracle Home binaries from the existing on-premises instance.

  3. Use Copy binary and Copy Config commands on each application node to back up Oracle SOA Suite.

  4. Back up the web servers on each node.

  5. Back up the files on the on-premises NFS drive shared between the application tier nodes.

  6. Copy the backup of the Oracle SOA Suite files and the Web Servers to the respective instances on AWS.

  7. Restore the Oracle SOA Suite components using the paste library and paste config commands on the application tier nodes on AWS.

  8. Complete the Fusion Middleware steps for Moving from a Test to a Production Environment. The RCU step is not required if you have already migrated the Oracle MDS Repository (refer to the Migrating the Oracle MDS Repository section later in this document).

  9. Restore the Web Server backup on AWS.

  10. Mount the Amazon EFS share on the application tier nodes and copy the shared data from on-premises.

  11. Migrate the Oracle MDS Repository. (Refer to the Migrating the Oracle MDS repository section of this document.)

  12. Update the metadata data source in WebLogic with the new database connection information of the MDS Repository.

  13. Open the WebLogic Administration Console to verify that the domain, cluster, and managed servers are configured correctly.

  14. Configure the Web servers and ELB (Network Load Balancer and Application Load Balancer).

  15. Start the servers and test.

Migration using new installation and configuration

  1. Launch the EC2 instances with Oracle Linux or a certified operating system for hosting the Oracle SOA Suite 12c components.

    1. Apply the required prerequisite patches for Oracle SOA Suite 12c, including the security patches.

    2. Create an Amazon EBS-backed Linux AMI and preserve the copy for future use.

  2. Migrate the Oracle MDS Repository. (Refer to the Migrating the Oracle MDS repository section of this document.)

  3. Install the Oracle Home.

  4. Mount the Amazon EFS share on the application tier nodes.

  5. Install Oracle SOA Suite 12c software on a single node.

  6. Configure an Oracle SOA Suite domain for each component (Oracle SOA, OSB, Oracle BPM, Oracle BAM, and Oracle ADF).

  7. Horizontally scale out to multiple nodes as per the requirements and complete the domain configuration.

  8. Configure data sources and JMS connection pools in WebLogic Server.

  9. Install the Web server and configure it (you can copy the configuration files from on-premises).

  10. Configure the Web servers and ELB (Network Load Balancer and Application Load Balancer).

  11. Start the servers and test.

Migrating the Oracle MDS repository

The steps for MDS Repository migration differ depending upon your database configuration.

For databases on Amazon EC2

For initial data migration, copy the regular Oracle Recovery Manager (Oracle RMAN) backup files along with archive log files for recovery. Then, use AWS Database Migration Service (AWS DMS) to synchronize the databases using change data capture (CDC). Refer to Migrate an on-premises Oracle database to Oracle on Amazon EC2 for prescriptive guidance.

For databases on Amazon RDS

For initial migration, copy the export dump files taken from the on-premises database to restore on Amazon RDS using the import tools. Then, use AWS DMS to synchronize the databases using change data capture (CDC). Refer to Migrate an on-premises Oracle database to Amazon RDS for Oracle for prescriptive guidance.