1. Migrating to the Cloud and Side-by-Side Upgrade in the Cloud for Oracle SOA Suite on Marketplace, Oracle SOA Cloud Service, and Oracle MFT Cloud Service
  2. Introduction to Migration and Upgrade for Oracle SOA Suite on Marketplace, Oracle SOA Cloud Service, and Oracle Managed File Transfer Cloud Service

1 Introduction to Migration and Upgrade for Oracle SOA Suite on Marketplace, Oracle SOA Cloud Service, and Oracle Managed File Transfer Cloud Service

SOA Suite on Marketplace, SOA Cloud Service, and MFT Cloud Service support manual migration from on-premises to the cloud and side-by-side upgrade from one version to another (or an older instance to a newer instance in the same version) in the cloud.

Notes:

  • The steps in this guide describe migration to the following target environments:
    • SOA Suite on Marketplace 12.2.1.4
    • SOA Cloud Service 12.2.1.3 (SOA+OSB+B2B+ESS topology) or later
    • MFT Cloud Service 12.2.1.3 or later
  • You can perform migration/side-by-side upgrade even if there is no version upgrade. For example, you can migrate from a subscription account to a universal credits account.

Topics:

Prerequisites for Migration and Side-by-Side Upgrade

Before migration or side-by-side upgrade, ensure the following:

  • For SOA Suite on Marketplace, the source on-premises version for migration to the cloud is 11.1.1.7 or later. The source version for side-by-side upgrade in the cloud is 12.2.1.4, as Oracle SOA Suite on Marketplace supports only 12.2.1.4.

  • For SOA Cloud Service and MFT Cloud Service, the source on-premises version for migration to the cloud is 11.1.1.7 or later. The source version for side-by-side upgrade in the cloud is 12.1.3 or later.

  • For SOA Cloud Service and MFT Cloud Service, it is assumed that disaster recovery is not configured for the source environment. Note that appropriate changes have to be made to the instructions if disaster recovery is configured.

  • For SOA Suite on Marketplace and SOA Cloud Service, it is assumed that the production environment has a load balancer. Otherwise, the steps have to be modified and adapted accordingly.

Understand Migration and Side-by-Side Upgrade for Oracle SOA Suite on Marketplace

The tasks that you’ll perform for migrating on-premises Oracle SOA Suite applications to the cloud are same as the tasks that you’ll perform for side-by-side upgrade in the cloud. The approach for migration and the side-by-side upgrade is the same — you’ll provision a new Oracle SOA Suite on Marketplace instance, migrate or re-create configurations from the old source environment, and then transition to the newly provisioned cloud instance.

Note:

Oracle SOA Suite on Marketplace allows you to create a separate instance for each service type (SOA with SB & B2B Cluster, MFT Cluster, and BAM Cluster).

Keep in mind the following differences between a migration to the cloud and a side-by-side upgrade in the cloud:

Migration Side-by-Side Upgrade

The source version of your on-premises Oracle SOA Suite application must be 11.1.1.7 or later.

Oracle SOA Suite on Marketplace supports only 12.2.1.4. For example, you can migrate projects and artifacts from an older 12.2.1.4 instance to a newer 12.2.1.4 instance.

Your on-premises Oracle SOA Suite application may use internal Lightweight Directory Access Protocol (LDAP), third party, or Oracle IDM.

Oracle SOA Suite on Marketplace uses internal LDAP.

Your on-premises Oracle SOA Suite application may use Oracle Traffic Director (OTD), Oracle HTTP Server (OHS), or a third party load balancer.

Oracle SOA Suite on Marketplace uses the Oracle Cloud Infrastructure load balancer.

Your on-premises Oracle SOA Suite application may use Java Keystore (JKS) or Keystore Services (KSS).

Oracle SOA Suite on Marketplace uses KSS.

You cannot copy security information directly between an on-premises Oracle SOA Suite application and Oracle SOA Suite on Marketplace during the migration. You have to first export the security information from your on-premises Oracle SOA Suite application to a local file, and then copy the file and import it to the target environment.

You can directly copy and import security information between the source and the target Oracle SOA Suite on Marketplace instances.

For the tasks you will need to complete to migrate an on-premises Oracle SOA Suite application to Oracle SOA Suite on Marketplace or perform a side-by-side upgrade, see Migration/Side-by-Side Upgrade for Oracle SOA Suite on Marketplace.

Understand Migration and Side-by-Side Upgrade for Oracle SOA Cloud Service

The tasks that you’ll perform for migrating on-premises Oracle SOA Suite applications to the cloud are same as the tasks that you’ll perform for side-by-side upgrade in the cloud. The approach for migration and the side-by-side upgrade is the same — you’ll provision a new cloud instance of Oracle SOA Cloud Service, migrate or re-create configurations from the old source environment, and then transition to the newly provisioned cloud instance.

Note:

Oracle SOA Cloud Service allows you to create a separate instance for each service type (SOA with SB & B2B Cluster, MFT Cluster, and BAM Cluster).

Keep in mind the following differences between a migration to the cloud and a side-by-side upgrade in the cloud:

Oracle SOA Cloud Service

Migration Side-by-Side Upgrade

The source version of your on-premises Oracle SOA Suite application must be 11.1.1.7 or later.

The source version of the Oracle SOA Cloud Service instance that you want to upgrade must be 12.1.3 or later.

Your on-premises Oracle SOA Suite application may use internal Lightweight Directory Access Protocol (LDAP), third party, or Oracle IDM.

Oracle SOA Cloud Service uses internal LDAP.

Your on-premises Oracle SOA Suite application may use Oracle Traffic Director (OTD), Oracle HTTP Server (OHS), or a third party load balancer.

Oracle SOA Cloud Service uses OTD.

Your on-premises Oracle SOA Suite application may use Java Keystore (JKS) or Keystore Services (KSS).

Oracle SOA Cloud Service uses KSS.

You cannot copy security information directly between an on-premises Oracle SOA Suite application and Oracle SOA Cloud Service during the migration. You have to first export the security information from your on-premises Oracle SOA Suite application to a local file, and then copy the file and import it to the target environment.

You can directly copy and import security information between the source and the target Oracle SOA Cloud Service instances.

For the tasks you will need to complete to migrate an on-premises Oracle SOA Suite application to Oracle SOA Cloud Service or perform a side-by-side upgrade, see Migration/Side-by-Side Upgrade for SOA Cloud Service.

Understand Migration and Side-by-Side Upgrade for MFT Cloud Service

The tasks that you’ll perform for migrating on-premises MFT applications to the cloud are same as the tasks that you’ll perform for side-by-side upgrade in the cloud for MFT Cloud Service. The approach for migration and the side-by-side upgrade is the same — you’ll provision a new cloud instance of MFT Cloud Service, migrate or recreate configurations from the old source environment and then transition to the newly provisioned cloud instance.

However, you have to keep in mind the following differences between migration to the cloud and side-by-side upgrade in the cloud:

Migration Side-by-Side Upgrade

The source version of your on-premises MFT application must be 11.1.1.7 or later.

The source version of the cloud MFT instance that you want to upgrade must be 12.1.3 or later.

Your on-premises MFT application may use internal Lightweight Directory Access Protocol (LDAP), third party, or Oracle IDM.

MFT Cloud Service uses internal LDAP.

Your on-premises MFT application may use Oracle Traffic Director (OTD) or a third party load balancer.

MFT Cloud Service uses OTD.

You cannot copy security information directly between an on-premises MFT application and MFT Cloud Service during the migration. You have to first export the security information from your on-premises MFT application to a local file, and then copy the file and import it to the target environment.

You can directly copy and import security information between the source and the target MFT Cloud Service instances.
For the tasks you will need to complete to migrate an on-premises Oracle SOA Suite application to MFT Cloud Service or perform a side-by-side upgrade, see Migration/Side-by-Side Upgrade for MFT Cloud Service.