Migrate Oracle SOA Cloud Service

Migrate Oracle SOA Cloud Service application to a new or existing Oracle SOA Suite on Marketplace instance in Oracle Cloud Infrastructure.

Caution

Avoid entering confidential information when assigning descriptions, tags, or friendly names to cloud resources through the Oracle Cloud Infrastructure Console, API, or CLI.

Plan the Migration

Ensure that you complete the prerequisites to set up and use Classic Migration Service. See Before You Begin. Additionally, complete the following tasks before you migrate Oracle SOA Cloud Service applications to Oracle Cloud Infrastructure.

In the Oracle SOA Cloud Service console in the source environment, click an instance name to view instance details, and then note the service type, version, and number of nodes, which is information you need to plan the migration.

  • Service Type: Oracle SOA Cloud Service includes three service types: Business Activity Monitoring, Managed File Transfer (MFT) Cluster, and SOA with SB & B2B Cluster. Classic Migration Service supports the migration of Oracle SOA Cloud Service applications that have either the MFT Cluster or SOA with SB & B2B Cluster service type. You cannot use Classic Migration Service to migrate Oracle SOA Cloud Service applications that have the Business Activity Monitoring service type.
  • Public or private subnet: Choose whether you want the target instance to be created in a public or private subnet. When the target instance is in a public subnet, you can send network traffic over the internet.

    When the target instance is in a private subnet, network traffic does not go over the internet. Private access can be from hosts within the virtual cloud network (VCN) or an on-premises network.

  • New or existing target instance: Choose whether you want to use Classic Migration Service to migrate an application to an existing target instance or create a target instance in Oracle Cloud Infrastructure.

    If you are using Classic Migration Service to create a target instance and migrate an application, then Classic Migration Service creates the target instance in a public subnet. It does not create the target instance in a private subnet.

    Note

    To migrate an application to a private subnet using Classic Migration Service, you must create Oracle SOA Suite on Marketplace in a private subnet and then use Classic Migration Service to migrate the application to the existing target instance.
  • Version: Ensure that Oracle SOA Cloud Service is at a supported version in the source environment.

    If the application is not at a supported version, then upgrade the application to a supported version and then use Classic Migration Service to migrate the application.

    The following table lists the versions of the source and target instance that Classic Migration Service supports. If you want to migrate applications to an existing target instance, then use this information to create a target Oracle SOA Suite on Marketplace instance.

    Source Type Supported Versions in Source Environment Existing Target Version New Target Version
    Oracle SOA Cloud Service with SB & B2B Cluster
    • 12.2.1.2
    • 12.2.1.3
    • 12.2.1.4
    12.2.1.4

    Release version: 12.2.1.4

    Package version: 20.4.2

    Oracle SOA Cloud Service with MFT cluster

    Release version: 12.2.1.4

    Package versions:

    Release version: 12.2.1.4

    Package version: 20.4.2

    Classic Migration Service supports only 12.2.1.4 version with package version 20.3.3 in the target environment. If the application is at a supported version, such as 12.2.1.3 in the source environment, then Classic Migration Service automatically upgrades it to version 12.2.1.4 as part of the migration process.

  • Metadata: Classic Migration Service supports migration of the following metadata for Oracle SOA Cloud Service with SB & B2B Cluster:

    • LDAP data: LDAP data includes the Oracle WebLogic Server specified user, group, enterprise role, and security policies (predefined Oracle WebLogic configurations and configurations that users have added to internal LDAP). If you are migrating to an existing target instance, then any existing LDAP configuration data on the target instance is overwritten.
    • OWSM policies: If you are migrating to an existing target instance, then any existing custom OWSM policies on the target instance are overwritten.
    • Common resource configurations:
      • Custom JDBC system resources
      • Foreign JNDI providers
      • File stores
      • JDBC stores
      • JMS servers
      • JMS system resources or JMS modules
      • Resource adapters

      When you are migrating to an existing target instance and the resource already exists, Classic Migration Service does not import that resource.

    • Oracle Enterprise Scheduler metadata: Classic Migration Service migrates the metadata for the EssNativeHostingApp and ESSAPP applications. The metadata includes job definitions, schedules, and job requests. If you are migrating to an existing target instance, then any existing Oracle Enterprise Scheduler metadata on the target instance is overwritten.
      Note

      • Classic Migration Service migrates job requests to the target instance but does not submit the job requests immediately. Classic Migration Service generates a script that you must run when the target SOA instance is ready for production use. The script includes only the job requests that have non-recurring schedules. You must migrate job requests with a recurring schedule, manually. See Complete Post-Migration Tasks for instructions to run this script.

      • Using Classic Migration Service to migrate Oracle Enterprise Scheduler metadata does not migrate shared artifacts, if any exist. Instead, you must migrate this information, manually. See Application Export Commands for information about exporting the shared artifacts and Import Application Metadata for information about importing the metadata.
    • B2B metadata: If you are migrating to an existing target instance, then any existing B2B metadata on the target instance is overwritten.
    • Oracle Service Bus (OSB) project data: If you are migrating to an existing target instance, then any existing Oracle Service Bus project data on the target instance is overwritten.
    • SOA composite application data: Includes SOA projects, applications, partitions, SOA infrastructure metadata, and token configuration.

      If you are migrating to an existing target instance, then any existing data on the target instance is overwritten, with the exception of the default partition, which is named partition. The default partition is not overwritten, but the composites contained in the default partition are overwritten.

    Classic Migration Service supports the migration of following metadata for Oracle SOA Cloud Service with MFT cluster:

    • Oracle Web Services Manager (OWSM) policies: If you are migrating to an existing target instance, then any existing custom OWSM policies on the target instance are overwritten.
    • MFT configuration data (including keystores and keys): If you are migrating to an existing target instance, then any existing data on the target instance is overwritten.
    • LDAP data: LDAP data includes the Oracle WebLogic Server-specified user, group, and enterprise role and security policies (predefined Oracle WebLogic configurations and configurations that users have added to internal LDAP). If you are migrating to an existing target instance, then any existing LDAP configuration data on the target instance is overwritten.
    • Oracle Platform Security Services data: Credentials store, Oracle Platform Security Services policies, and keystores. Credentials store includes Credential Store Framework keys.

      While migrating Oracle SOA Cloud Service with MFT cluster, Classic Migration Service migrates the credentials but does not migrate Oracle Platform Security Services policies and keystores. After migrating an application, you must manually migrate Oracle Platform Security Services policies and keystores.

      If you are migrating Oracle Platform Security Services credentials to an existing target instance, then any existing data on the target instance is overwritten.

      If you are migrating to an existing instance in Oracle Cloud Infrastructure, then migrate Oracle Platform Security Services policies and keystores to the existing target instance before migrating the application. If you are migrating to a new instance, then you can migrate the Oracle Platform Security Services policies and keystores after migrating the application.

    If the source environment contains Oracle Platform Security Services data, then Classic Migration Service does not migrate the data. After migrating an application, you must manually migrate Oracle Platform Security Services data.

  • Nodes: Determine the number of nodes that the Oracle SOA Cloud Service application contains in the source environment.

    If you are using Classic Migration Service to automatically create an instance in the target environment and migrate an application, then Classic Migration Service detects the number of nodes that are available in the source application and automatically creates an instance with the same number of nodes in the target environment.

    If you are migrating a multi-node Oracle SOA Cloud Service application to an existing target instance, then ensure that the target instance also has multiple nodes. The following table provides details about the required mapping between the node types of the source and target instances.

    Node Type of Source Instance Node Type of Target Instance
    Single Single
    Multi-node Multi-node
    Multi-node with Oracle Traffic Director Multi-node with Oracle Cloud Infrastructure Load Balancing service, if your target instance is Oracle SOA Suite on Marketplace
    Multi-node with Oracle Traffic Director Multi-node with Oracle Traffic Director, if your target instance is Oracle SOA Cloud Service

    If an application contains a single node, then ensure that you can SSH to that node. If an application contains multiple nodes, then ensure that the SSH ports to the managed servers and the Oracle WebLogic Administration Server are open.

  • Database: If you are using Classic Migration Service to automatically create a database instance in the target environment and migrate an application, then Classic Migration Service creates an Oracle Cloud Infrastructure database instance. If you are using Classic Migration Service to migrate an application to an existing Oracle SOA Suite on Marketplace instance in the target instance, then you can associate an existing Oracle Cloud Infrastructure database or an Oracle Autonomous Transaction Processing database instance with the target instance. For information about creating a database, see Create an Oracle Database for Oracle SOA Suite on Marketplace. To configure the existing target database, see Configure the Database.
  • Licensing: When you migrate an application to Oracle SOA Suite on Marketplace, Classic Migration Service discovers the licensing type of the source instance and creates the target instance with the same licensing type. If the B2B adapter is enabled on the source instance, then Classic Migration Service creates the target instance with a paid license even when you have BYOL in the source environment.

Next: After planning a migration, provide information about the source environment to create a Classic Migration Service source.

Prepare the Target Environment

Prepare to migrate to a new Oracle SOA Suite on Marketplace instance

In Oracle Cloud Infrastructure, identify a compartment where you want to migrate an application. The compartment must contain a VCN and at least one subnet. To create a compartment, see Design the Oracle Cloud Infrastructure Network.

Prepare to migrate to an existing Oracle SOA Suite on Marketplace target instance

Before you migrate an Oracle SOA Cloud Service Classic instance to an Oracle Cloud Infrastructure region, you must create the required infrastructure and database resources.

  1. Identify an existing Oracle SOA Suite on Marketplace instance in Oracle Cloud Infrastructure or create an instance to host the application that you want to migrate. To create an Oracle SOA Suite on Marketplace instance, see Provision an Oracle SOA Suite on Marketplace Instance.
  2. Identify the number of nodes in the source instance. The target instance must have the same number of nodes as the source instance.
  3. The existing target instance must be connected to a database in Oracle Cloud Infrastructure. Ensure that the database and the instance are in the same subnet in Oracle Cloud Infrastructure. For details about creating a database that is associated with an Oracle SOA Suite on Marketplace instance in the target environment, see Create an Oracle Database for Oracle SOA Suite on Marketplace.
  4. Ensure that the target instance is available and is in the running state when you migrate the application.
  5. Complete all the steps mentioned in Before You Migrate Using the Application Migration Service.