text
stringlengths 65
20k
|
|---|
Element Description Name Enter a name for the source (for this example, oicmigrationamsdemo is entered).This is not the name for your new migrated instance.Description Enter an optional description.Compartment Select the compartment to use for migration.By default, the compartment that you selected prior to clicking Create Source is displayed.Chapter 3 Step 4: Migrate Integrations and Processes 3-9Element Description Source Type Select Oracle Cloud Infrastructure - Classic to migrate an Oracle Integration Classic instance.Account Enter your Oracle Integration Classic account.This is the unique portion following the hyphen in Compute-xxxxxxxxx .This is the name associated with your Oracle Cloud Infrastructure Classic Compute service entitlement and is typically a nine digit number.If you use a traditional account for Oracle Integration Classic, enter the identity domain ID.Region Select the region in which the Oracle Integration Classic instance to migrate is located.Service Administrator Username Enter the service administrator username for the Oracle Integration Classic instance.This user must be assigned the INTEGRATIONCLOUD_ENTITLEMENT_ADMI NISTRATOR role.Service Administrator Password Enter the service administrator password for this username.After creation, the source is displayed in the Sources section (for this example, named oicmigrationamsdemo ).You are now ready to create a migration. |
This is not the name for your new migrated instance.Description Enter an optional description.Compartment Select the compartment to use for migration.By default, the compartment that you selected prior to clicking Create Source is displayed.Chapter 3 Step 4: Migrate Integrations and Processes 3-9Element Description Source Type Select Oracle Cloud Infrastructure - Classic to migrate an Oracle Integration Classic instance.Account Enter your Oracle Integration Classic account.This is the unique portion following the hyphen in Compute-xxxxxxxxx .This is the name associated with your Oracle Cloud Infrastructure Classic Compute service entitlement and is typically a nine digit number.If you use a traditional account for Oracle Integration Classic, enter the identity domain ID.Region Select the region in which the Oracle Integration Classic instance to migrate is located.Service Administrator Username Enter the service administrator username for the Oracle Integration Classic instance.This user must be assigned the INTEGRATIONCLOUD_ENTITLEMENT_ADMI NISTRATOR role.Service Administrator Password Enter the service administrator password for this username.After creation, the source is displayed in the Sources section (for this example, named oicmigrationamsdemo ).You are now ready to create a migration.Chapter 3 Step 4: Migrate Integrations and Processes 3-10 Create a Migration When you create an Oracle Integration Classic migration, all applications (instances) available for you to migrate are discovered. |
Description Enter an optional description.Compartment Select the compartment to use for migration.By default, the compartment that you selected prior to clicking Create Source is displayed.Chapter 3 Step 4: Migrate Integrations and Processes 3-9Element Description Source Type Select Oracle Cloud Infrastructure - Classic to migrate an Oracle Integration Classic instance.Account Enter your Oracle Integration Classic account.This is the unique portion following the hyphen in Compute-xxxxxxxxx .This is the name associated with your Oracle Cloud Infrastructure Classic Compute service entitlement and is typically a nine digit number.If you use a traditional account for Oracle Integration Classic, enter the identity domain ID.Region Select the region in which the Oracle Integration Classic instance to migrate is located.Service Administrator Username Enter the service administrator username for the Oracle Integration Classic instance.This user must be assigned the INTEGRATIONCLOUD_ENTITLEMENT_ADMI NISTRATOR role.Service Administrator Password Enter the service administrator password for this username.After creation, the source is displayed in the Sources section (for this example, named oicmigrationamsdemo ).You are now ready to create a migration.Chapter 3 Step 4: Migrate Integrations and Processes 3-10 Create a Migration When you create an Oracle Integration Classic migration, all applications (instances) available for you to migrate are discovered.1.In the Name column, click the source to migrate (for this example, named oicmigrationamsdemo ). |
Compartment Select the compartment to use for migration.By default, the compartment that you selected prior to clicking Create Source is displayed.Chapter 3 Step 4: Migrate Integrations and Processes 3-9Element Description Source Type Select Oracle Cloud Infrastructure - Classic to migrate an Oracle Integration Classic instance.Account Enter your Oracle Integration Classic account.This is the unique portion following the hyphen in Compute-xxxxxxxxx .This is the name associated with your Oracle Cloud Infrastructure Classic Compute service entitlement and is typically a nine digit number.If you use a traditional account for Oracle Integration Classic, enter the identity domain ID.Region Select the region in which the Oracle Integration Classic instance to migrate is located.Service Administrator Username Enter the service administrator username for the Oracle Integration Classic instance.This user must be assigned the INTEGRATIONCLOUD_ENTITLEMENT_ADMI NISTRATOR role.Service Administrator Password Enter the service administrator password for this username.After creation, the source is displayed in the Sources section (for this example, named oicmigrationamsdemo ).You are now ready to create a migration.Chapter 3 Step 4: Migrate Integrations and Processes 3-10 Create a Migration When you create an Oracle Integration Classic migration, all applications (instances) available for you to migrate are discovered.1.In the Name column, click the source to migrate (for this example, named oicmigrationamsdemo ).2.Wait for the page to refresh, then scroll down to view all the applications (instances) associated with this tenancy. |
By default, the compartment that you selected prior to clicking Create Source is displayed.Chapter 3 Step 4: Migrate Integrations and Processes 3-9Element Description Source Type Select Oracle Cloud Infrastructure - Classic to migrate an Oracle Integration Classic instance.Account Enter your Oracle Integration Classic account.This is the unique portion following the hyphen in Compute-xxxxxxxxx .This is the name associated with your Oracle Cloud Infrastructure Classic Compute service entitlement and is typically a nine digit number.If you use a traditional account for Oracle Integration Classic, enter the identity domain ID.Region Select the region in which the Oracle Integration Classic instance to migrate is located.Service Administrator Username Enter the service administrator username for the Oracle Integration Classic instance.This user must be assigned the INTEGRATIONCLOUD_ENTITLEMENT_ADMI NISTRATOR role.Service Administrator Password Enter the service administrator password for this username.After creation, the source is displayed in the Sources section (for this example, named oicmigrationamsdemo ).You are now ready to create a migration.Chapter 3 Step 4: Migrate Integrations and Processes 3-10 Create a Migration When you create an Oracle Integration Classic migration, all applications (instances) available for you to migrate are discovered.1.In the Name column, click the source to migrate (for this example, named oicmigrationamsdemo ).2.Wait for the page to refresh, then scroll down to view all the applications (instances) associated with this tenancy.Oracle Integration Classic applications are identified as OIC in the Type column. |
Account Enter your Oracle Integration Classic account.This is the unique portion following the hyphen in Compute-xxxxxxxxx .This is the name associated with your Oracle Cloud Infrastructure Classic Compute service entitlement and is typically a nine digit number.If you use a traditional account for Oracle Integration Classic, enter the identity domain ID.Region Select the region in which the Oracle Integration Classic instance to migrate is located.Service Administrator Username Enter the service administrator username for the Oracle Integration Classic instance.This user must be assigned the INTEGRATIONCLOUD_ENTITLEMENT_ADMI NISTRATOR role.Service Administrator Password Enter the service administrator password for this username.After creation, the source is displayed in the Sources section (for this example, named oicmigrationamsdemo ).You are now ready to create a migration.Chapter 3 Step 4: Migrate Integrations and Processes 3-10 Create a Migration When you create an Oracle Integration Classic migration, all applications (instances) available for you to migrate are discovered.1.In the Name column, click the source to migrate (for this example, named oicmigrationamsdemo ).2.Wait for the page to refresh, then scroll down to view all the applications (instances) associated with this tenancy.Oracle Integration Classic applications are identified as OIC in the Type column.3.Identity the Oracle Integration Classic application (instance) to migrate. |
This is the unique portion following the hyphen in Compute-xxxxxxxxx .This is the name associated with your Oracle Cloud Infrastructure Classic Compute service entitlement and is typically a nine digit number.If you use a traditional account for Oracle Integration Classic, enter the identity domain ID.Region Select the region in which the Oracle Integration Classic instance to migrate is located.Service Administrator Username Enter the service administrator username for the Oracle Integration Classic instance.This user must be assigned the INTEGRATIONCLOUD_ENTITLEMENT_ADMI NISTRATOR role.Service Administrator Password Enter the service administrator password for this username.After creation, the source is displayed in the Sources section (for this example, named oicmigrationamsdemo ).You are now ready to create a migration.Chapter 3 Step 4: Migrate Integrations and Processes 3-10 Create a Migration When you create an Oracle Integration Classic migration, all applications (instances) available for you to migrate are discovered.1.In the Name column, click the source to migrate (for this example, named oicmigrationamsdemo ).2.Wait for the page to refresh, then scroll down to view all the applications (instances) associated with this tenancy.Oracle Integration Classic applications are identified as OIC in the Type column.3.Identity the Oracle Integration Classic application (instance) to migrate.4.Go to the far right section of the row for this application and click . |
This is the name associated with your Oracle Cloud Infrastructure Classic Compute service entitlement and is typically a nine digit number.If you use a traditional account for Oracle Integration Classic, enter the identity domain ID.Region Select the region in which the Oracle Integration Classic instance to migrate is located.Service Administrator Username Enter the service administrator username for the Oracle Integration Classic instance.This user must be assigned the INTEGRATIONCLOUD_ENTITLEMENT_ADMI NISTRATOR role.Service Administrator Password Enter the service administrator password for this username.After creation, the source is displayed in the Sources section (for this example, named oicmigrationamsdemo ).You are now ready to create a migration.Chapter 3 Step 4: Migrate Integrations and Processes 3-10 Create a Migration When you create an Oracle Integration Classic migration, all applications (instances) available for you to migrate are discovered.1.In the Name column, click the source to migrate (for this example, named oicmigrationamsdemo ).2.Wait for the page to refresh, then scroll down to view all the applications (instances) associated with this tenancy.Oracle Integration Classic applications are identified as OIC in the Type column.3.Identity the Oracle Integration Classic application (instance) to migrate.4.Go to the far right section of the row for this application and click .5.Select Create Migration . |
If you use a traditional account for Oracle Integration Classic, enter the identity domain ID.Region Select the region in which the Oracle Integration Classic instance to migrate is located.Service Administrator Username Enter the service administrator username for the Oracle Integration Classic instance.This user must be assigned the INTEGRATIONCLOUD_ENTITLEMENT_ADMI NISTRATOR role.Service Administrator Password Enter the service administrator password for this username.After creation, the source is displayed in the Sources section (for this example, named oicmigrationamsdemo ).You are now ready to create a migration.Chapter 3 Step 4: Migrate Integrations and Processes 3-10 Create a Migration When you create an Oracle Integration Classic migration, all applications (instances) available for you to migrate are discovered.1.In the Name column, click the source to migrate (for this example, named oicmigrationamsdemo ).2.Wait for the page to refresh, then scroll down to view all the applications (instances) associated with this tenancy.Oracle Integration Classic applications are identified as OIC in the Type column.3.Identity the Oracle Integration Classic application (instance) to migrate.4.Go to the far right section of the row for this application and click .5.Select Create Migration .6.Enter the following details, and click Create to begin the migration discovery. |
Region Select the region in which the Oracle Integration Classic instance to migrate is located.Service Administrator Username Enter the service administrator username for the Oracle Integration Classic instance.This user must be assigned the INTEGRATIONCLOUD_ENTITLEMENT_ADMI NISTRATOR role.Service Administrator Password Enter the service administrator password for this username.After creation, the source is displayed in the Sources section (for this example, named oicmigrationamsdemo ).You are now ready to create a migration.Chapter 3 Step 4: Migrate Integrations and Processes 3-10 Create a Migration When you create an Oracle Integration Classic migration, all applications (instances) available for you to migrate are discovered.1.In the Name column, click the source to migrate (for this example, named oicmigrationamsdemo ).2.Wait for the page to refresh, then scroll down to view all the applications (instances) associated with this tenancy.Oracle Integration Classic applications are identified as OIC in the Type column.3.Identity the Oracle Integration Classic application (instance) to migrate.4.Go to the far right section of the row for this application and click .5.Select Create Migration .6.Enter the following details, and click Create to begin the migration discovery.Several fields are automatically populated with details. |
Service Administrator Username Enter the service administrator username for the Oracle Integration Classic instance.This user must be assigned the INTEGRATIONCLOUD_ENTITLEMENT_ADMI NISTRATOR role.Service Administrator Password Enter the service administrator password for this username.After creation, the source is displayed in the Sources section (for this example, named oicmigrationamsdemo ).You are now ready to create a migration.Chapter 3 Step 4: Migrate Integrations and Processes 3-10 Create a Migration When you create an Oracle Integration Classic migration, all applications (instances) available for you to migrate are discovered.1.In the Name column, click the source to migrate (for this example, named oicmigrationamsdemo ).2.Wait for the page to refresh, then scroll down to view all the applications (instances) associated with this tenancy.Oracle Integration Classic applications are identified as OIC in the Type column.3.Identity the Oracle Integration Classic application (instance) to migrate.4.Go to the far right section of the row for this application and click .5.Select Create Migration .6.Enter the following details, and click Create to begin the migration discovery.Several fields are automatically populated with details.Element Description Migration Name Accept the default name, which is appended with a timestamp, or enter a different name. |
This user must be assigned the INTEGRATIONCLOUD_ENTITLEMENT_ADMI NISTRATOR role.Service Administrator Password Enter the service administrator password for this username.After creation, the source is displayed in the Sources section (for this example, named oicmigrationamsdemo ).You are now ready to create a migration.Chapter 3 Step 4: Migrate Integrations and Processes 3-10 Create a Migration When you create an Oracle Integration Classic migration, all applications (instances) available for you to migrate are discovered.1.In the Name column, click the source to migrate (for this example, named oicmigrationamsdemo ).2.Wait for the page to refresh, then scroll down to view all the applications (instances) associated with this tenancy.Oracle Integration Classic applications are identified as OIC in the Type column.3.Identity the Oracle Integration Classic application (instance) to migrate.4.Go to the far right section of the row for this application and click .5.Select Create Migration .6.Enter the following details, and click Create to begin the migration discovery.Several fields are automatically populated with details.Element Description Migration Name Accept the default name, which is appended with a timestamp, or enter a different name.Description Enter an optional description.Chapter 3 Step 4: Migrate Integrations and Processes 3-11Element Description Source Displays the name of the selected source migration. |
Service Administrator Password Enter the service administrator password for this username.After creation, the source is displayed in the Sources section (for this example, named oicmigrationamsdemo ).You are now ready to create a migration.Chapter 3 Step 4: Migrate Integrations and Processes 3-10 Create a Migration When you create an Oracle Integration Classic migration, all applications (instances) available for you to migrate are discovered.1.In the Name column, click the source to migrate (for this example, named oicmigrationamsdemo ).2.Wait for the page to refresh, then scroll down to view all the applications (instances) associated with this tenancy.Oracle Integration Classic applications are identified as OIC in the Type column.3.Identity the Oracle Integration Classic application (instance) to migrate.4.Go to the far right section of the row for this application and click .5.Select Create Migration .6.Enter the following details, and click Create to begin the migration discovery.Several fields are automatically populated with details.Element Description Migration Name Accept the default name, which is appended with a timestamp, or enter a different name.Description Enter an optional description.Chapter 3 Step 4: Migrate Integrations and Processes 3-11Element Description Source Displays the name of the selected source migration.Application Displays the name of the selected application. |
After creation, the source is displayed in the Sources section (for this example, named oicmigrationamsdemo ).You are now ready to create a migration.Chapter 3 Step 4: Migrate Integrations and Processes 3-10 Create a Migration When you create an Oracle Integration Classic migration, all applications (instances) available for you to migrate are discovered.1.In the Name column, click the source to migrate (for this example, named oicmigrationamsdemo ).2.Wait for the page to refresh, then scroll down to view all the applications (instances) associated with this tenancy.Oracle Integration Classic applications are identified as OIC in the Type column.3.Identity the Oracle Integration Classic application (instance) to migrate.4.Go to the far right section of the row for this application and click .5.Select Create Migration .6.Enter the following details, and click Create to begin the migration discovery.Several fields are automatically populated with details.Element Description Migration Name Accept the default name, which is appended with a timestamp, or enter a different name.Description Enter an optional description.Chapter 3 Step 4: Migrate Integrations and Processes 3-11Element Description Source Displays the name of the selected source migration.Application Displays the name of the selected application.Service Instance Username Enter the administrator username of the application to migrate. |
You are now ready to create a migration.Chapter 3 Step 4: Migrate Integrations and Processes 3-10 Create a Migration When you create an Oracle Integration Classic migration, all applications (instances) available for you to migrate are discovered.1.In the Name column, click the source to migrate (for this example, named oicmigrationamsdemo ).2.Wait for the page to refresh, then scroll down to view all the applications (instances) associated with this tenancy.Oracle Integration Classic applications are identified as OIC in the Type column.3.Identity the Oracle Integration Classic application (instance) to migrate.4.Go to the far right section of the row for this application and click .5.Select Create Migration .6.Enter the following details, and click Create to begin the migration discovery.Several fields are automatically populated with details.Element Description Migration Name Accept the default name, which is appended with a timestamp, or enter a different name.Description Enter an optional description.Chapter 3 Step 4: Migrate Integrations and Processes 3-11Element Description Source Displays the name of the selected source migration.Application Displays the name of the selected application.Service Instance Username Enter the administrator username of the application to migrate.This user must have the ServiceAdministrator role. |
Chapter 3 Step 4: Migrate Integrations and Processes 3-10 Create a Migration When you create an Oracle Integration Classic migration, all applications (instances) available for you to migrate are discovered.1.In the Name column, click the source to migrate (for this example, named oicmigrationamsdemo ).2.Wait for the page to refresh, then scroll down to view all the applications (instances) associated with this tenancy.Oracle Integration Classic applications are identified as OIC in the Type column.3.Identity the Oracle Integration Classic application (instance) to migrate.4.Go to the far right section of the row for this application and click .5.Select Create Migration .6.Enter the following details, and click Create to begin the migration discovery.Several fields are automatically populated with details.Element Description Migration Name Accept the default name, which is appended with a timestamp, or enter a different name.Description Enter an optional description.Chapter 3 Step 4: Migrate Integrations and Processes 3-11Element Description Source Displays the name of the selected source migration.Application Displays the name of the selected application.Service Instance Username Enter the administrator username of the application to migrate.This user must have the ServiceAdministrator role.Service Instance Password Enter the instance administrator password. |
1.In the Name column, click the source to migrate (for this example, named oicmigrationamsdemo ).2.Wait for the page to refresh, then scroll down to view all the applications (instances) associated with this tenancy.Oracle Integration Classic applications are identified as OIC in the Type column.3.Identity the Oracle Integration Classic application (instance) to migrate.4.Go to the far right section of the row for this application and click .5.Select Create Migration .6.Enter the following details, and click Create to begin the migration discovery.Several fields are automatically populated with details.Element Description Migration Name Accept the default name, which is appended with a timestamp, or enter a different name.Description Enter an optional description.Chapter 3 Step 4: Migrate Integrations and Processes 3-11Element Description Source Displays the name of the selected source migration.Application Displays the name of the selected application.Service Instance Username Enter the administrator username of the application to migrate.This user must have the ServiceAdministrator role.Service Instance Password Enter the instance administrator password.Target Instance Type Select the type of target instance in Oracle Cloud Infrastructure. |
2.Wait for the page to refresh, then scroll down to view all the applications (instances) associated with this tenancy.Oracle Integration Classic applications are identified as OIC in the Type column.3.Identity the Oracle Integration Classic application (instance) to migrate.4.Go to the far right section of the row for this application and click .5.Select Create Migration .6.Enter the following details, and click Create to begin the migration discovery.Several fields are automatically populated with details.Element Description Migration Name Accept the default name, which is appended with a timestamp, or enter a different name.Description Enter an optional description.Chapter 3 Step 4: Migrate Integrations and Processes 3-11Element Description Source Displays the name of the selected source migration.Application Displays the name of the selected application.Service Instance Username Enter the administrator username of the application to migrate.This user must have the ServiceAdministrator role.Service Instance Password Enter the instance administrator password.Target Instance Type Select the type of target instance in Oracle Cloud Infrastructure.The availability of this feature depends on your Oracle Cloud Infrastructure home region and your subscription. |
Oracle Integration Classic applications are identified as OIC in the Type column.3.Identity the Oracle Integration Classic application (instance) to migrate.4.Go to the far right section of the row for this application and click .5.Select Create Migration .6.Enter the following details, and click Create to begin the migration discovery.Several fields are automatically populated with details.Element Description Migration Name Accept the default name, which is appended with a timestamp, or enter a different name.Description Enter an optional description.Chapter 3 Step 4: Migrate Integrations and Processes 3-11Element Description Source Displays the name of the selected source migration.Application Displays the name of the selected application.Service Instance Username Enter the administrator username of the application to migrate.This user must have the ServiceAdministrator role.Service Instance Password Enter the instance administrator password.Target Instance Type Select the type of target instance in Oracle Cloud Infrastructure.The availability of this feature depends on your Oracle Cloud Infrastructure home region and your subscription.For Oracle Integration Classic, select Oracle Integration - Generation 2 . |
3.Identity the Oracle Integration Classic application (instance) to migrate.4.Go to the far right section of the row for this application and click .5.Select Create Migration .6.Enter the following details, and click Create to begin the migration discovery.Several fields are automatically populated with details.Element Description Migration Name Accept the default name, which is appended with a timestamp, or enter a different name.Description Enter an optional description.Chapter 3 Step 4: Migrate Integrations and Processes 3-11Element Description Source Displays the name of the selected source migration.Application Displays the name of the selected application.Service Instance Username Enter the administrator username of the application to migrate.This user must have the ServiceAdministrator role.Service Instance Password Enter the instance administrator password.Target Instance Type Select the type of target instance in Oracle Cloud Infrastructure.The availability of this feature depends on your Oracle Cloud Infrastructure home region and your subscription.For Oracle Integration Classic, select Oracle Integration - Generation 2 .The page shows a progress bar that indicates the status of the discovery process to gather details about the instance to migrate. |
4.Go to the far right section of the row for this application and click .5.Select Create Migration .6.Enter the following details, and click Create to begin the migration discovery.Several fields are automatically populated with details.Element Description Migration Name Accept the default name, which is appended with a timestamp, or enter a different name.Description Enter an optional description.Chapter 3 Step 4: Migrate Integrations and Processes 3-11Element Description Source Displays the name of the selected source migration.Application Displays the name of the selected application.Service Instance Username Enter the administrator username of the application to migrate.This user must have the ServiceAdministrator role.Service Instance Password Enter the instance administrator password.Target Instance Type Select the type of target instance in Oracle Cloud Infrastructure.The availability of this feature depends on your Oracle Cloud Infrastructure home region and your subscription.For Oracle Integration Classic, select Oracle Integration - Generation 2 .The page shows a progress bar that indicates the status of the discovery process to gather details about the instance to migrate.Once your migration discovery completes, the status is displayed as Succeeded . |
5.Select Create Migration .6.Enter the following details, and click Create to begin the migration discovery.Several fields are automatically populated with details.Element Description Migration Name Accept the default name, which is appended with a timestamp, or enter a different name.Description Enter an optional description.Chapter 3 Step 4: Migrate Integrations and Processes 3-11Element Description Source Displays the name of the selected source migration.Application Displays the name of the selected application.Service Instance Username Enter the administrator username of the application to migrate.This user must have the ServiceAdministrator role.Service Instance Password Enter the instance administrator password.Target Instance Type Select the type of target instance in Oracle Cloud Infrastructure.The availability of this feature depends on your Oracle Cloud Infrastructure home region and your subscription.For Oracle Integration Classic, select Oracle Integration - Generation 2 .The page shows a progress bar that indicates the status of the discovery process to gather details about the instance to migrate.Once your migration discovery completes, the status is displayed as Succeeded .7.You are now ready to create a configuration in which you provide details about the new target instance to create. |
6.Enter the following details, and click Create to begin the migration discovery.Several fields are automatically populated with details.Element Description Migration Name Accept the default name, which is appended with a timestamp, or enter a different name.Description Enter an optional description.Chapter 3 Step 4: Migrate Integrations and Processes 3-11Element Description Source Displays the name of the selected source migration.Application Displays the name of the selected application.Service Instance Username Enter the administrator username of the application to migrate.This user must have the ServiceAdministrator role.Service Instance Password Enter the instance administrator password.Target Instance Type Select the type of target instance in Oracle Cloud Infrastructure.The availability of this feature depends on your Oracle Cloud Infrastructure home region and your subscription.For Oracle Integration Classic, select Oracle Integration - Generation 2 .The page shows a progress bar that indicates the status of the discovery process to gather details about the instance to migrate.Once your migration discovery completes, the status is displayed as Succeeded .7.You are now ready to create a configuration in which you provide details about the new target instance to create.Configure the Migration Target Instance Once discovery completes, you create a configuration that describes the new Oracle Integration Generation 2 target instance to create in Oracle Cloud Infrastructure. |
Several fields are automatically populated with details.Element Description Migration Name Accept the default name, which is appended with a timestamp, or enter a different name.Description Enter an optional description.Chapter 3 Step 4: Migrate Integrations and Processes 3-11Element Description Source Displays the name of the selected source migration.Application Displays the name of the selected application.Service Instance Username Enter the administrator username of the application to migrate.This user must have the ServiceAdministrator role.Service Instance Password Enter the instance administrator password.Target Instance Type Select the type of target instance in Oracle Cloud Infrastructure.The availability of this feature depends on your Oracle Cloud Infrastructure home region and your subscription.For Oracle Integration Classic, select Oracle Integration - Generation 2 .The page shows a progress bar that indicates the status of the discovery process to gather details about the instance to migrate.Once your migration discovery completes, the status is displayed as Succeeded .7.You are now ready to create a configuration in which you provide details about the new target instance to create.Configure the Migration Target Instance Once discovery completes, you create a configuration that describes the new Oracle Integration Generation 2 target instance to create in Oracle Cloud Infrastructure.This configuration automatically creates an object storage bucket and new instance. |
Element Description Migration Name Accept the default name, which is appended with a timestamp, or enter a different name.Description Enter an optional description.Chapter 3 Step 4: Migrate Integrations and Processes 3-11Element Description Source Displays the name of the selected source migration.Application Displays the name of the selected application.Service Instance Username Enter the administrator username of the application to migrate.This user must have the ServiceAdministrator role.Service Instance Password Enter the instance administrator password.Target Instance Type Select the type of target instance in Oracle Cloud Infrastructure.The availability of this feature depends on your Oracle Cloud Infrastructure home region and your subscription.For Oracle Integration Classic, select Oracle Integration - Generation 2 .The page shows a progress bar that indicates the status of the discovery process to gather details about the instance to migrate.Once your migration discovery completes, the status is displayed as Succeeded .7.You are now ready to create a configuration in which you provide details about the new target instance to create.Configure the Migration Target Instance Once discovery completes, you create a configuration that describes the new Oracle Integration Generation 2 target instance to create in Oracle Cloud Infrastructure.This configuration automatically creates an object storage bucket and new instance.1.Click Configure to provide target instance details. |
Description Enter an optional description.Chapter 3 Step 4: Migrate Integrations and Processes 3-11Element Description Source Displays the name of the selected source migration.Application Displays the name of the selected application.Service Instance Username Enter the administrator username of the application to migrate.This user must have the ServiceAdministrator role.Service Instance Password Enter the instance administrator password.Target Instance Type Select the type of target instance in Oracle Cloud Infrastructure.The availability of this feature depends on your Oracle Cloud Infrastructure home region and your subscription.For Oracle Integration Classic, select Oracle Integration - Generation 2 .The page shows a progress bar that indicates the status of the discovery process to gather details about the instance to migrate.Once your migration discovery completes, the status is displayed as Succeeded .7.You are now ready to create a configuration in which you provide details about the new target instance to create.Configure the Migration Target Instance Once discovery completes, you create a configuration that describes the new Oracle Integration Generation 2 target instance to create in Oracle Cloud Infrastructure.This configuration automatically creates an object storage bucket and new instance.1.Click Configure to provide target instance details.Chapter 3 Step 4: Migrate Integrations and Processes 3-122.Review the overview page and click Configure . |
Application Displays the name of the selected application.Service Instance Username Enter the administrator username of the application to migrate.This user must have the ServiceAdministrator role.Service Instance Password Enter the instance administrator password.Target Instance Type Select the type of target instance in Oracle Cloud Infrastructure.The availability of this feature depends on your Oracle Cloud Infrastructure home region and your subscription.For Oracle Integration Classic, select Oracle Integration - Generation 2 .The page shows a progress bar that indicates the status of the discovery process to gather details about the instance to migrate.Once your migration discovery completes, the status is displayed as Succeeded .7.You are now ready to create a configuration in which you provide details about the new target instance to create.Configure the Migration Target Instance Once discovery completes, you create a configuration that describes the new Oracle Integration Generation 2 target instance to create in Oracle Cloud Infrastructure.This configuration automatically creates an object storage bucket and new instance.1.Click Configure to provide target instance details.Chapter 3 Step 4: Migrate Integrations and Processes 3-122.Review the overview page and click Configure .The Configure Target Oracle Integration Instance dialog is displayed. |
Service Instance Username Enter the administrator username of the application to migrate.This user must have the ServiceAdministrator role.Service Instance Password Enter the instance administrator password.Target Instance Type Select the type of target instance in Oracle Cloud Infrastructure.The availability of this feature depends on your Oracle Cloud Infrastructure home region and your subscription.For Oracle Integration Classic, select Oracle Integration - Generation 2 .The page shows a progress bar that indicates the status of the discovery process to gather details about the instance to migrate.Once your migration discovery completes, the status is displayed as Succeeded .7.You are now ready to create a configuration in which you provide details about the new target instance to create.Configure the Migration Target Instance Once discovery completes, you create a configuration that describes the new Oracle Integration Generation 2 target instance to create in Oracle Cloud Infrastructure.This configuration automatically creates an object storage bucket and new instance.1.Click Configure to provide target instance details.Chapter 3 Step 4: Migrate Integrations and Processes 3-122.Review the overview page and click Configure .The Configure Target Oracle Integration Instance dialog is displayed.3.Enter the following details, then click Configure . |
This user must have the ServiceAdministrator role.Service Instance Password Enter the instance administrator password.Target Instance Type Select the type of target instance in Oracle Cloud Infrastructure.The availability of this feature depends on your Oracle Cloud Infrastructure home region and your subscription.For Oracle Integration Classic, select Oracle Integration - Generation 2 .The page shows a progress bar that indicates the status of the discovery process to gather details about the instance to migrate.Once your migration discovery completes, the status is displayed as Succeeded .7.You are now ready to create a configuration in which you provide details about the new target instance to create.Configure the Migration Target Instance Once discovery completes, you create a configuration that describes the new Oracle Integration Generation 2 target instance to create in Oracle Cloud Infrastructure.This configuration automatically creates an object storage bucket and new instance.1.Click Configure to provide target instance details.Chapter 3 Step 4: Migrate Integrations and Processes 3-122.Review the overview page and click Configure .The Configure Target Oracle Integration Instance dialog is displayed.3.Enter the following details, then click Configure .Element Description Instance Name Enter a name for the new instance that is unique within your tenancy. |
Service Instance Password Enter the instance administrator password.Target Instance Type Select the type of target instance in Oracle Cloud Infrastructure.The availability of this feature depends on your Oracle Cloud Infrastructure home region and your subscription.For Oracle Integration Classic, select Oracle Integration - Generation 2 .The page shows a progress bar that indicates the status of the discovery process to gather details about the instance to migrate.Once your migration discovery completes, the status is displayed as Succeeded .7.You are now ready to create a configuration in which you provide details about the new target instance to create.Configure the Migration Target Instance Once discovery completes, you create a configuration that describes the new Oracle Integration Generation 2 target instance to create in Oracle Cloud Infrastructure.This configuration automatically creates an object storage bucket and new instance.1.Click Configure to provide target instance details.Chapter 3 Step 4: Migrate Integrations and Processes 3-122.Review the overview page and click Configure .The Configure Target Oracle Integration Instance dialog is displayed.3.Enter the following details, then click Configure .Element Description Instance Name Enter a name for the new instance that is unique within your tenancy.Description Enter an optional description to help identify the new service instance. |
Target Instance Type Select the type of target instance in Oracle Cloud Infrastructure.The availability of this feature depends on your Oracle Cloud Infrastructure home region and your subscription.For Oracle Integration Classic, select Oracle Integration - Generation 2 .The page shows a progress bar that indicates the status of the discovery process to gather details about the instance to migrate.Once your migration discovery completes, the status is displayed as Succeeded .7.You are now ready to create a configuration in which you provide details about the new target instance to create.Configure the Migration Target Instance Once discovery completes, you create a configuration that describes the new Oracle Integration Generation 2 target instance to create in Oracle Cloud Infrastructure.This configuration automatically creates an object storage bucket and new instance.1.Click Configure to provide target instance details.Chapter 3 Step 4: Migrate Integrations and Processes 3-122.Review the overview page and click Configure .The Configure Target Oracle Integration Instance dialog is displayed.3.Enter the following details, then click Configure .Element Description Instance Name Enter a name for the new instance that is unique within your tenancy.Description Enter an optional description to help identify the new service instance.Bring Your Own License Select the checkbox to bring your own license option (BYOL) to the new instance if your organization already owns an Oracle Fusion Middleware software license for Oracle Integration Classic. |
The availability of this feature depends on your Oracle Cloud Infrastructure home region and your subscription.For Oracle Integration Classic, select Oracle Integration - Generation 2 .The page shows a progress bar that indicates the status of the discovery process to gather details about the instance to migrate.Once your migration discovery completes, the status is displayed as Succeeded .7.You are now ready to create a configuration in which you provide details about the new target instance to create.Configure the Migration Target Instance Once discovery completes, you create a configuration that describes the new Oracle Integration Generation 2 target instance to create in Oracle Cloud Infrastructure.This configuration automatically creates an object storage bucket and new instance.1.Click Configure to provide target instance details.Chapter 3 Step 4: Migrate Integrations and Processes 3-122.Review the overview page and click Configure .The Configure Target Oracle Integration Instance dialog is displayed.3.Enter the following details, then click Configure .Element Description Instance Name Enter a name for the new instance that is unique within your tenancy.Description Enter an optional description to help identify the new service instance.Bring Your Own License Select the checkbox to bring your own license option (BYOL) to the new instance if your organization already owns an Oracle Fusion Middleware software license for Oracle Integration Classic.Otherwise, leave the checkbox unselected to subscribe to a new Oracle Integration software license. |
For Oracle Integration Classic, select Oracle Integration - Generation 2 .The page shows a progress bar that indicates the status of the discovery process to gather details about the instance to migrate.Once your migration discovery completes, the status is displayed as Succeeded .7.You are now ready to create a configuration in which you provide details about the new target instance to create.Configure the Migration Target Instance Once discovery completes, you create a configuration that describes the new Oracle Integration Generation 2 target instance to create in Oracle Cloud Infrastructure.This configuration automatically creates an object storage bucket and new instance.1.Click Configure to provide target instance details.Chapter 3 Step 4: Migrate Integrations and Processes 3-122.Review the overview page and click Configure .The Configure Target Oracle Integration Instance dialog is displayed.3.Enter the following details, then click Configure .Element Description Instance Name Enter a name for the new instance that is unique within your tenancy.Description Enter an optional description to help identify the new service instance.Bring Your Own License Select the checkbox to bring your own license option (BYOL) to the new instance if your organization already owns an Oracle Fusion Middleware software license for Oracle Integration Classic.Otherwise, leave the checkbox unselected to subscribe to a new Oracle Integration software license.Number of Message Packs The maximum number of message packs for an instance is based on your license type. |
The page shows a progress bar that indicates the status of the discovery process to gather details about the instance to migrate.Once your migration discovery completes, the status is displayed as Succeeded .7.You are now ready to create a configuration in which you provide details about the new target instance to create.Configure the Migration Target Instance Once discovery completes, you create a configuration that describes the new Oracle Integration Generation 2 target instance to create in Oracle Cloud Infrastructure.This configuration automatically creates an object storage bucket and new instance.1.Click Configure to provide target instance details.Chapter 3 Step 4: Migrate Integrations and Processes 3-122.Review the overview page and click Configure .The Configure Target Oracle Integration Instance dialog is displayed.3.Enter the following details, then click Configure .Element Description Instance Name Enter a name for the new instance that is unique within your tenancy.Description Enter an optional description to help identify the new service instance.Bring Your Own License Select the checkbox to bring your own license option (BYOL) to the new instance if your organization already owns an Oracle Fusion Middleware software license for Oracle Integration Classic.Otherwise, leave the checkbox unselected to subscribe to a new Oracle Integration software license.Number of Message Packs The maximum number of message packs for an instance is based on your license type.For BYOL, the instance can have between 1 and 3 message packs. |
Once your migration discovery completes, the status is displayed as Succeeded .7.You are now ready to create a configuration in which you provide details about the new target instance to create.Configure the Migration Target Instance Once discovery completes, you create a configuration that describes the new Oracle Integration Generation 2 target instance to create in Oracle Cloud Infrastructure.This configuration automatically creates an object storage bucket and new instance.1.Click Configure to provide target instance details.Chapter 3 Step 4: Migrate Integrations and Processes 3-122.Review the overview page and click Configure .The Configure Target Oracle Integration Instance dialog is displayed.3.Enter the following details, then click Configure .Element Description Instance Name Enter a name for the new instance that is unique within your tenancy.Description Enter an optional description to help identify the new service instance.Bring Your Own License Select the checkbox to bring your own license option (BYOL) to the new instance if your organization already owns an Oracle Fusion Middleware software license for Oracle Integration Classic.Otherwise, leave the checkbox unselected to subscribe to a new Oracle Integration software license.Number of Message Packs The maximum number of message packs for an instance is based on your license type.For BYOL, the instance can have between 1 and 3 message packs.Each message pack adds 20K messages per hour to your instance. |
7.You are now ready to create a configuration in which you provide details about the new target instance to create.Configure the Migration Target Instance Once discovery completes, you create a configuration that describes the new Oracle Integration Generation 2 target instance to create in Oracle Cloud Infrastructure.This configuration automatically creates an object storage bucket and new instance.1.Click Configure to provide target instance details.Chapter 3 Step 4: Migrate Integrations and Processes 3-122.Review the overview page and click Configure .The Configure Target Oracle Integration Instance dialog is displayed.3.Enter the following details, then click Configure .Element Description Instance Name Enter a name for the new instance that is unique within your tenancy.Description Enter an optional description to help identify the new service instance.Bring Your Own License Select the checkbox to bring your own license option (BYOL) to the new instance if your organization already owns an Oracle Fusion Middleware software license for Oracle Integration Classic.Otherwise, leave the checkbox unselected to subscribe to a new Oracle Integration software license.Number of Message Packs The maximum number of message packs for an instance is based on your license type.For BYOL, the instance can have between 1 and 3 message packs.Each message pack adds 20K messages per hour to your instance.If you don't have a BYOL license type, the instance can have between 1 to 12 message packs. |
Configure the Migration Target Instance Once discovery completes, you create a configuration that describes the new Oracle Integration Generation 2 target instance to create in Oracle Cloud Infrastructure.This configuration automatically creates an object storage bucket and new instance.1.Click Configure to provide target instance details.Chapter 3 Step 4: Migrate Integrations and Processes 3-122.Review the overview page and click Configure .The Configure Target Oracle Integration Instance dialog is displayed.3.Enter the following details, then click Configure .Element Description Instance Name Enter a name for the new instance that is unique within your tenancy.Description Enter an optional description to help identify the new service instance.Bring Your Own License Select the checkbox to bring your own license option (BYOL) to the new instance if your organization already owns an Oracle Fusion Middleware software license for Oracle Integration Classic.Otherwise, leave the checkbox unselected to subscribe to a new Oracle Integration software license.Number of Message Packs The maximum number of message packs for an instance is based on your license type.For BYOL, the instance can have between 1 and 3 message packs.Each message pack adds 20K messages per hour to your instance.If you don't have a BYOL license type, the instance can have between 1 to 12 message packs.Each message pack adds 5K messages per hour to your instance. |
This configuration automatically creates an object storage bucket and new instance.1.Click Configure to provide target instance details.Chapter 3 Step 4: Migrate Integrations and Processes 3-122.Review the overview page and click Configure .The Configure Target Oracle Integration Instance dialog is displayed.3.Enter the following details, then click Configure .Element Description Instance Name Enter a name for the new instance that is unique within your tenancy.Description Enter an optional description to help identify the new service instance.Bring Your Own License Select the checkbox to bring your own license option (BYOL) to the new instance if your organization already owns an Oracle Fusion Middleware software license for Oracle Integration Classic.Otherwise, leave the checkbox unselected to subscribe to a new Oracle Integration software license.Number of Message Packs The maximum number of message packs for an instance is based on your license type.For BYOL, the instance can have between 1 and 3 message packs.Each message pack adds 20K messages per hour to your instance.If you don't have a BYOL license type, the instance can have between 1 to 12 message packs.Each message pack adds 5K messages per hour to your instance.Notification Email Enter an email address at which to be notified of migration status. |
1.Click Configure to provide target instance details.Chapter 3 Step 4: Migrate Integrations and Processes 3-122.Review the overview page and click Configure .The Configure Target Oracle Integration Instance dialog is displayed.3.Enter the following details, then click Configure .Element Description Instance Name Enter a name for the new instance that is unique within your tenancy.Description Enter an optional description to help identify the new service instance.Bring Your Own License Select the checkbox to bring your own license option (BYOL) to the new instance if your organization already owns an Oracle Fusion Middleware software license for Oracle Integration Classic.Otherwise, leave the checkbox unselected to subscribe to a new Oracle Integration software license.Number of Message Packs The maximum number of message packs for an instance is based on your license type.For BYOL, the instance can have between 1 and 3 message packs.Each message pack adds 20K messages per hour to your instance.If you don't have a BYOL license type, the instance can have between 1 to 12 message packs.Each message pack adds 5K messages per hour to your instance.Notification Email Enter an email address at which to be notified of migration status.IDCS Username Enter the PaaS username for the account. |
Chapter 3 Step 4: Migrate Integrations and Processes 3-122.Review the overview page and click Configure .The Configure Target Oracle Integration Instance dialog is displayed.3.Enter the following details, then click Configure .Element Description Instance Name Enter a name for the new instance that is unique within your tenancy.Description Enter an optional description to help identify the new service instance.Bring Your Own License Select the checkbox to bring your own license option (BYOL) to the new instance if your organization already owns an Oracle Fusion Middleware software license for Oracle Integration Classic.Otherwise, leave the checkbox unselected to subscribe to a new Oracle Integration software license.Number of Message Packs The maximum number of message packs for an instance is based on your license type.For BYOL, the instance can have between 1 and 3 message packs.Each message pack adds 20K messages per hour to your instance.If you don't have a BYOL license type, the instance can have between 1 to 12 message packs.Each message pack adds 5K messages per hour to your instance.Notification Email Enter an email address at which to be notified of migration status.IDCS Username Enter the PaaS username for the account.Ensure that account is assigned the following service entitlement: AUTONOMOUS_INTEGRATION: CLOUD_ENTITLEMENT_ADMINISTRATOR (Autonomous Integration Cloud entitlement administrator role) IDCS Password Enter the password for the PaaS username.Chapter 3 Step 4: Migrate Integrations and Processes 3-13Start the Migration Once scheduled, you can start the migration and execute the configuration. |
The Configure Target Oracle Integration Instance dialog is displayed.3.Enter the following details, then click Configure .Element Description Instance Name Enter a name for the new instance that is unique within your tenancy.Description Enter an optional description to help identify the new service instance.Bring Your Own License Select the checkbox to bring your own license option (BYOL) to the new instance if your organization already owns an Oracle Fusion Middleware software license for Oracle Integration Classic.Otherwise, leave the checkbox unselected to subscribe to a new Oracle Integration software license.Number of Message Packs The maximum number of message packs for an instance is based on your license type.For BYOL, the instance can have between 1 and 3 message packs.Each message pack adds 20K messages per hour to your instance.If you don't have a BYOL license type, the instance can have between 1 to 12 message packs.Each message pack adds 5K messages per hour to your instance.Notification Email Enter an email address at which to be notified of migration status.IDCS Username Enter the PaaS username for the account.Ensure that account is assigned the following service entitlement: AUTONOMOUS_INTEGRATION: CLOUD_ENTITLEMENT_ADMINISTRATOR (Autonomous Integration Cloud entitlement administrator role) IDCS Password Enter the password for the PaaS username.Chapter 3 Step 4: Migrate Integrations and Processes 3-13Start the Migration Once scheduled, you can start the migration and execute the configuration.The Application Migration Service creates a new Oracle Integration Generation 2 instance in Oracle Cloud Infrastructure into which your design-time metadata is imported. |
3.Enter the following details, then click Configure .Element Description Instance Name Enter a name for the new instance that is unique within your tenancy.Description Enter an optional description to help identify the new service instance.Bring Your Own License Select the checkbox to bring your own license option (BYOL) to the new instance if your organization already owns an Oracle Fusion Middleware software license for Oracle Integration Classic.Otherwise, leave the checkbox unselected to subscribe to a new Oracle Integration software license.Number of Message Packs The maximum number of message packs for an instance is based on your license type.For BYOL, the instance can have between 1 and 3 message packs.Each message pack adds 20K messages per hour to your instance.If you don't have a BYOL license type, the instance can have between 1 to 12 message packs.Each message pack adds 5K messages per hour to your instance.Notification Email Enter an email address at which to be notified of migration status.IDCS Username Enter the PaaS username for the account.Ensure that account is assigned the following service entitlement: AUTONOMOUS_INTEGRATION: CLOUD_ENTITLEMENT_ADMINISTRATOR (Autonomous Integration Cloud entitlement administrator role) IDCS Password Enter the password for the PaaS username.Chapter 3 Step 4: Migrate Integrations and Processes 3-13Start the Migration Once scheduled, you can start the migration and execute the configuration.The Application Migration Service creates a new Oracle Integration Generation 2 instance in Oracle Cloud Infrastructure into which your design-time metadata is imported.1.Review your configuration details, then click Save or click Save and Run to run the migration now. |
Element Description Instance Name Enter a name for the new instance that is unique within your tenancy.Description Enter an optional description to help identify the new service instance.Bring Your Own License Select the checkbox to bring your own license option (BYOL) to the new instance if your organization already owns an Oracle Fusion Middleware software license for Oracle Integration Classic.Otherwise, leave the checkbox unselected to subscribe to a new Oracle Integration software license.Number of Message Packs The maximum number of message packs for an instance is based on your license type.For BYOL, the instance can have between 1 and 3 message packs.Each message pack adds 20K messages per hour to your instance.If you don't have a BYOL license type, the instance can have between 1 to 12 message packs.Each message pack adds 5K messages per hour to your instance.Notification Email Enter an email address at which to be notified of migration status.IDCS Username Enter the PaaS username for the account.Ensure that account is assigned the following service entitlement: AUTONOMOUS_INTEGRATION: CLOUD_ENTITLEMENT_ADMINISTRATOR (Autonomous Integration Cloud entitlement administrator role) IDCS Password Enter the password for the PaaS username.Chapter 3 Step 4: Migrate Integrations and Processes 3-13Start the Migration Once scheduled, you can start the migration and execute the configuration.The Application Migration Service creates a new Oracle Integration Generation 2 instance in Oracle Cloud Infrastructure into which your design-time metadata is imported.1.Review your configuration details, then click Save or click Save and Run to run the migration now.This starts the migration to create a new Oracle Integration Classic Generation 2 instance. |
Description Enter an optional description to help identify the new service instance.Bring Your Own License Select the checkbox to bring your own license option (BYOL) to the new instance if your organization already owns an Oracle Fusion Middleware software license for Oracle Integration Classic.Otherwise, leave the checkbox unselected to subscribe to a new Oracle Integration software license.Number of Message Packs The maximum number of message packs for an instance is based on your license type.For BYOL, the instance can have between 1 and 3 message packs.Each message pack adds 20K messages per hour to your instance.If you don't have a BYOL license type, the instance can have between 1 to 12 message packs.Each message pack adds 5K messages per hour to your instance.Notification Email Enter an email address at which to be notified of migration status.IDCS Username Enter the PaaS username for the account.Ensure that account is assigned the following service entitlement: AUTONOMOUS_INTEGRATION: CLOUD_ENTITLEMENT_ADMINISTRATOR (Autonomous Integration Cloud entitlement administrator role) IDCS Password Enter the password for the PaaS username.Chapter 3 Step 4: Migrate Integrations and Processes 3-13Start the Migration Once scheduled, you can start the migration and execute the configuration.The Application Migration Service creates a new Oracle Integration Generation 2 instance in Oracle Cloud Infrastructure into which your design-time metadata is imported.1.Review your configuration details, then click Save or click Save and Run to run the migration now.This starts the migration to create a new Oracle Integration Classic Generation 2 instance.During this process, the design-time metadata of the instance is exported and imported into the new instance. |
Bring Your Own License Select the checkbox to bring your own license option (BYOL) to the new instance if your organization already owns an Oracle Fusion Middleware software license for Oracle Integration Classic.Otherwise, leave the checkbox unselected to subscribe to a new Oracle Integration software license.Number of Message Packs The maximum number of message packs for an instance is based on your license type.For BYOL, the instance can have between 1 and 3 message packs.Each message pack adds 20K messages per hour to your instance.If you don't have a BYOL license type, the instance can have between 1 to 12 message packs.Each message pack adds 5K messages per hour to your instance.Notification Email Enter an email address at which to be notified of migration status.IDCS Username Enter the PaaS username for the account.Ensure that account is assigned the following service entitlement: AUTONOMOUS_INTEGRATION: CLOUD_ENTITLEMENT_ADMINISTRATOR (Autonomous Integration Cloud entitlement administrator role) IDCS Password Enter the password for the PaaS username.Chapter 3 Step 4: Migrate Integrations and Processes 3-13Start the Migration Once scheduled, you can start the migration and execute the configuration.The Application Migration Service creates a new Oracle Integration Generation 2 instance in Oracle Cloud Infrastructure into which your design-time metadata is imported.1.Review your configuration details, then click Save or click Save and Run to run the migration now.This starts the migration to create a new Oracle Integration Classic Generation 2 instance.During this process, the design-time metadata of the instance is exported and imported into the new instance.2.Click Start when prompted to start the migration. |
Otherwise, leave the checkbox unselected to subscribe to a new Oracle Integration software license.Number of Message Packs The maximum number of message packs for an instance is based on your license type.For BYOL, the instance can have between 1 and 3 message packs.Each message pack adds 20K messages per hour to your instance.If you don't have a BYOL license type, the instance can have between 1 to 12 message packs.Each message pack adds 5K messages per hour to your instance.Notification Email Enter an email address at which to be notified of migration status.IDCS Username Enter the PaaS username for the account.Ensure that account is assigned the following service entitlement: AUTONOMOUS_INTEGRATION: CLOUD_ENTITLEMENT_ADMINISTRATOR (Autonomous Integration Cloud entitlement administrator role) IDCS Password Enter the password for the PaaS username.Chapter 3 Step 4: Migrate Integrations and Processes 3-13Start the Migration Once scheduled, you can start the migration and execute the configuration.The Application Migration Service creates a new Oracle Integration Generation 2 instance in Oracle Cloud Infrastructure into which your design-time metadata is imported.1.Review your configuration details, then click Save or click Save and Run to run the migration now.This starts the migration to create a new Oracle Integration Classic Generation 2 instance.During this process, the design-time metadata of the instance is exported and imported into the new instance.2.Click Start when prompted to start the migration.3.Follow the progress of migration in the Percent Complete column. |
Number of Message Packs The maximum number of message packs for an instance is based on your license type.For BYOL, the instance can have between 1 and 3 message packs.Each message pack adds 20K messages per hour to your instance.If you don't have a BYOL license type, the instance can have between 1 to 12 message packs.Each message pack adds 5K messages per hour to your instance.Notification Email Enter an email address at which to be notified of migration status.IDCS Username Enter the PaaS username for the account.Ensure that account is assigned the following service entitlement: AUTONOMOUS_INTEGRATION: CLOUD_ENTITLEMENT_ADMINISTRATOR (Autonomous Integration Cloud entitlement administrator role) IDCS Password Enter the password for the PaaS username.Chapter 3 Step 4: Migrate Integrations and Processes 3-13Start the Migration Once scheduled, you can start the migration and execute the configuration.The Application Migration Service creates a new Oracle Integration Generation 2 instance in Oracle Cloud Infrastructure into which your design-time metadata is imported.1.Review your configuration details, then click Save or click Save and Run to run the migration now.This starts the migration to create a new Oracle Integration Classic Generation 2 instance.During this process, the design-time metadata of the instance is exported and imported into the new instance.2.Click Start when prompted to start the migration.3.Follow the progress of migration in the Percent Complete column.Chapter 3 Step 4: Migrate Integrations and Processes 3-14 4.Click Migrate Application to view in-progress details about the entire migration process, including: Creating an archive location in the object storage bucket for the design-time metadata. |
For BYOL, the instance can have between 1 and 3 message packs.Each message pack adds 20K messages per hour to your instance.If you don't have a BYOL license type, the instance can have between 1 to 12 message packs.Each message pack adds 5K messages per hour to your instance.Notification Email Enter an email address at which to be notified of migration status.IDCS Username Enter the PaaS username for the account.Ensure that account is assigned the following service entitlement: AUTONOMOUS_INTEGRATION: CLOUD_ENTITLEMENT_ADMINISTRATOR (Autonomous Integration Cloud entitlement administrator role) IDCS Password Enter the password for the PaaS username.Chapter 3 Step 4: Migrate Integrations and Processes 3-13Start the Migration Once scheduled, you can start the migration and execute the configuration.The Application Migration Service creates a new Oracle Integration Generation 2 instance in Oracle Cloud Infrastructure into which your design-time metadata is imported.1.Review your configuration details, then click Save or click Save and Run to run the migration now.This starts the migration to create a new Oracle Integration Classic Generation 2 instance.During this process, the design-time metadata of the instance is exported and imported into the new instance.2.Click Start when prompted to start the migration.3.Follow the progress of migration in the Percent Complete column.Chapter 3 Step 4: Migrate Integrations and Processes 3-14 4.Click Migrate Application to view in-progress details about the entire migration process, including: Creating an archive location in the object storage bucket for the design-time metadata.Exporting the design-time metadata of the instance to the archive location. |
Each message pack adds 20K messages per hour to your instance.If you don't have a BYOL license type, the instance can have between 1 to 12 message packs.Each message pack adds 5K messages per hour to your instance.Notification Email Enter an email address at which to be notified of migration status.IDCS Username Enter the PaaS username for the account.Ensure that account is assigned the following service entitlement: AUTONOMOUS_INTEGRATION: CLOUD_ENTITLEMENT_ADMINISTRATOR (Autonomous Integration Cloud entitlement administrator role) IDCS Password Enter the password for the PaaS username.Chapter 3 Step 4: Migrate Integrations and Processes 3-13Start the Migration Once scheduled, you can start the migration and execute the configuration.The Application Migration Service creates a new Oracle Integration Generation 2 instance in Oracle Cloud Infrastructure into which your design-time metadata is imported.1.Review your configuration details, then click Save or click Save and Run to run the migration now.This starts the migration to create a new Oracle Integration Classic Generation 2 instance.During this process, the design-time metadata of the instance is exported and imported into the new instance.2.Click Start when prompted to start the migration.3.Follow the progress of migration in the Percent Complete column.Chapter 3 Step 4: Migrate Integrations and Processes 3-14 4.Click Migrate Application to view in-progress details about the entire migration process, including: Creating an archive location in the object storage bucket for the design-time metadata.Exporting the design-time metadata of the instance to the archive location.Creating a new Oracle Integration Generation 2 instance. |
If you don't have a BYOL license type, the instance can have between 1 to 12 message packs.Each message pack adds 5K messages per hour to your instance.Notification Email Enter an email address at which to be notified of migration status.IDCS Username Enter the PaaS username for the account.Ensure that account is assigned the following service entitlement: AUTONOMOUS_INTEGRATION: CLOUD_ENTITLEMENT_ADMINISTRATOR (Autonomous Integration Cloud entitlement administrator role) IDCS Password Enter the password for the PaaS username.Chapter 3 Step 4: Migrate Integrations and Processes 3-13Start the Migration Once scheduled, you can start the migration and execute the configuration.The Application Migration Service creates a new Oracle Integration Generation 2 instance in Oracle Cloud Infrastructure into which your design-time metadata is imported.1.Review your configuration details, then click Save or click Save and Run to run the migration now.This starts the migration to create a new Oracle Integration Classic Generation 2 instance.During this process, the design-time metadata of the instance is exported and imported into the new instance.2.Click Start when prompted to start the migration.3.Follow the progress of migration in the Percent Complete column.Chapter 3 Step 4: Migrate Integrations and Processes 3-14 4.Click Migrate Application to view in-progress details about the entire migration process, including: Creating an archive location in the object storage bucket for the design-time metadata.Exporting the design-time metadata of the instance to the archive location.Creating a new Oracle Integration Generation 2 instance.Importing the design-time metadata archive from the object storage bucket into the new instance. |
Each message pack adds 5K messages per hour to your instance.Notification Email Enter an email address at which to be notified of migration status.IDCS Username Enter the PaaS username for the account.Ensure that account is assigned the following service entitlement: AUTONOMOUS_INTEGRATION: CLOUD_ENTITLEMENT_ADMINISTRATOR (Autonomous Integration Cloud entitlement administrator role) IDCS Password Enter the password for the PaaS username.Chapter 3 Step 4: Migrate Integrations and Processes 3-13Start the Migration Once scheduled, you can start the migration and execute the configuration.The Application Migration Service creates a new Oracle Integration Generation 2 instance in Oracle Cloud Infrastructure into which your design-time metadata is imported.1.Review your configuration details, then click Save or click Save and Run to run the migration now.This starts the migration to create a new Oracle Integration Classic Generation 2 instance.During this process, the design-time metadata of the instance is exported and imported into the new instance.2.Click Start when prompted to start the migration.3.Follow the progress of migration in the Percent Complete column.Chapter 3 Step 4: Migrate Integrations and Processes 3-14 4.Click Migrate Application to view in-progress details about the entire migration process, including: Creating an archive location in the object storage bucket for the design-time metadata.Exporting the design-time metadata of the instance to the archive location.Creating a new Oracle Integration Generation 2 instance.Importing the design-time metadata archive from the object storage bucket into the new instance.Deleting the archive from the object storage bucket when the import completes. |
Notification Email Enter an email address at which to be notified of migration status.IDCS Username Enter the PaaS username for the account.Ensure that account is assigned the following service entitlement: AUTONOMOUS_INTEGRATION: CLOUD_ENTITLEMENT_ADMINISTRATOR (Autonomous Integration Cloud entitlement administrator role) IDCS Password Enter the password for the PaaS username.Chapter 3 Step 4: Migrate Integrations and Processes 3-13Start the Migration Once scheduled, you can start the migration and execute the configuration.The Application Migration Service creates a new Oracle Integration Generation 2 instance in Oracle Cloud Infrastructure into which your design-time metadata is imported.1.Review your configuration details, then click Save or click Save and Run to run the migration now.This starts the migration to create a new Oracle Integration Classic Generation 2 instance.During this process, the design-time metadata of the instance is exported and imported into the new instance.2.Click Start when prompted to start the migration.3.Follow the progress of migration in the Percent Complete column.Chapter 3 Step 4: Migrate Integrations and Processes 3-14 4.Click Migrate Application to view in-progress details about the entire migration process, including: Creating an archive location in the object storage bucket for the design-time metadata.Exporting the design-time metadata of the instance to the archive location.Creating a new Oracle Integration Generation 2 instance.Importing the design-time metadata archive from the object storage bucket into the new instance.Deleting the archive from the object storage bucket when the import completes.5.If successful, Succeeded is displayed in the status column. |
IDCS Username Enter the PaaS username for the account.Ensure that account is assigned the following service entitlement: AUTONOMOUS_INTEGRATION: CLOUD_ENTITLEMENT_ADMINISTRATOR (Autonomous Integration Cloud entitlement administrator role) IDCS Password Enter the password for the PaaS username.Chapter 3 Step 4: Migrate Integrations and Processes 3-13Start the Migration Once scheduled, you can start the migration and execute the configuration.The Application Migration Service creates a new Oracle Integration Generation 2 instance in Oracle Cloud Infrastructure into which your design-time metadata is imported.1.Review your configuration details, then click Save or click Save and Run to run the migration now.This starts the migration to create a new Oracle Integration Classic Generation 2 instance.During this process, the design-time metadata of the instance is exported and imported into the new instance.2.Click Start when prompted to start the migration.3.Follow the progress of migration in the Percent Complete column.Chapter 3 Step 4: Migrate Integrations and Processes 3-14 4.Click Migrate Application to view in-progress details about the entire migration process, including: Creating an archive location in the object storage bucket for the design-time metadata.Exporting the design-time metadata of the instance to the archive location.Creating a new Oracle Integration Generation 2 instance.Importing the design-time metadata archive from the object storage bucket into the new instance.Deleting the archive from the object storage bucket when the import completes.5.If successful, Succeeded is displayed in the status column.a.Access your new instance by clicking the link shown at the top of the page: Application "instance_name " migrated successfully Access the Instance at Oracle Integration b.Go to the Integrations page to activate the migrated instance. |
Ensure that account is assigned the following service entitlement: AUTONOMOUS_INTEGRATION: CLOUD_ENTITLEMENT_ADMINISTRATOR (Autonomous Integration Cloud entitlement administrator role) IDCS Password Enter the password for the PaaS username.Chapter 3 Step 4: Migrate Integrations and Processes 3-13Start the Migration Once scheduled, you can start the migration and execute the configuration.The Application Migration Service creates a new Oracle Integration Generation 2 instance in Oracle Cloud Infrastructure into which your design-time metadata is imported.1.Review your configuration details, then click Save or click Save and Run to run the migration now.This starts the migration to create a new Oracle Integration Classic Generation 2 instance.During this process, the design-time metadata of the instance is exported and imported into the new instance.2.Click Start when prompted to start the migration.3.Follow the progress of migration in the Percent Complete column.Chapter 3 Step 4: Migrate Integrations and Processes 3-14 4.Click Migrate Application to view in-progress details about the entire migration process, including: Creating an archive location in the object storage bucket for the design-time metadata.Exporting the design-time metadata of the instance to the archive location.Creating a new Oracle Integration Generation 2 instance.Importing the design-time metadata archive from the object storage bucket into the new instance.Deleting the archive from the object storage bucket when the import completes.5.If successful, Succeeded is displayed in the status column.a.Access your new instance by clicking the link shown at the top of the page: Application "instance_name " migrated successfully Access the Instance at Oracle Integration b.Go to the Integrations page to activate the migrated instance.See Verify Your Environment and Activate Your Integrations . |
The Application Migration Service creates a new Oracle Integration Generation 2 instance in Oracle Cloud Infrastructure into which your design-time metadata is imported.1.Review your configuration details, then click Save or click Save and Run to run the migration now.This starts the migration to create a new Oracle Integration Classic Generation 2 instance.During this process, the design-time metadata of the instance is exported and imported into the new instance.2.Click Start when prompted to start the migration.3.Follow the progress of migration in the Percent Complete column.Chapter 3 Step 4: Migrate Integrations and Processes 3-14 4.Click Migrate Application to view in-progress details about the entire migration process, including: Creating an archive location in the object storage bucket for the design-time metadata.Exporting the design-time metadata of the instance to the archive location.Creating a new Oracle Integration Generation 2 instance.Importing the design-time metadata archive from the object storage bucket into the new instance.Deleting the archive from the object storage bucket when the import completes.5.If successful, Succeeded is displayed in the status column.a.Access your new instance by clicking the link shown at the top of the page: Application "instance_name " migrated successfully Access the Instance at Oracle Integration b.Go to the Integrations page to activate the migrated instance.See Verify Your Environment and Activate Your Integrations .6.If unsuccessful, Failed is displayed in the status column. |
1.Review your configuration details, then click Save or click Save and Run to run the migration now.This starts the migration to create a new Oracle Integration Classic Generation 2 instance.During this process, the design-time metadata of the instance is exported and imported into the new instance.2.Click Start when prompted to start the migration.3.Follow the progress of migration in the Percent Complete column.Chapter 3 Step 4: Migrate Integrations and Processes 3-14 4.Click Migrate Application to view in-progress details about the entire migration process, including: Creating an archive location in the object storage bucket for the design-time metadata.Exporting the design-time metadata of the instance to the archive location.Creating a new Oracle Integration Generation 2 instance.Importing the design-time metadata archive from the object storage bucket into the new instance.Deleting the archive from the object storage bucket when the import completes.5.If successful, Succeeded is displayed in the status column.a.Access your new instance by clicking the link shown at the top of the page: Application "instance_name " migrated successfully Access the Instance at Oracle Integration b.Go to the Integrations page to activate the migrated instance.See Verify Your Environment and Activate Your Integrations .6.If unsuccessful, Failed is displayed in the status column.The logs provide details about what failed. |
This starts the migration to create a new Oracle Integration Classic Generation 2 instance.During this process, the design-time metadata of the instance is exported and imported into the new instance.2.Click Start when prompted to start the migration.3.Follow the progress of migration in the Percent Complete column.Chapter 3 Step 4: Migrate Integrations and Processes 3-14 4.Click Migrate Application to view in-progress details about the entire migration process, including: Creating an archive location in the object storage bucket for the design-time metadata.Exporting the design-time metadata of the instance to the archive location.Creating a new Oracle Integration Generation 2 instance.Importing the design-time metadata archive from the object storage bucket into the new instance.Deleting the archive from the object storage bucket when the import completes.5.If successful, Succeeded is displayed in the status column.a.Access your new instance by clicking the link shown at the top of the page: Application "instance_name " migrated successfully Access the Instance at Oracle Integration b.Go to the Integrations page to activate the migrated instance.See Verify Your Environment and Activate Your Integrations .6.If unsuccessful, Failed is displayed in the status column.The logs provide details about what failed.Step 5: Migrate Your Visual Builder Design-Time Metadata You can migrate a visual application from an Oracle Integration Classic instance by importing the application as an archive or by importing it from a Git repository. |
During this process, the design-time metadata of the instance is exported and imported into the new instance.2.Click Start when prompted to start the migration.3.Follow the progress of migration in the Percent Complete column.Chapter 3 Step 4: Migrate Integrations and Processes 3-14 4.Click Migrate Application to view in-progress details about the entire migration process, including: Creating an archive location in the object storage bucket for the design-time metadata.Exporting the design-time metadata of the instance to the archive location.Creating a new Oracle Integration Generation 2 instance.Importing the design-time metadata archive from the object storage bucket into the new instance.Deleting the archive from the object storage bucket when the import completes.5.If successful, Succeeded is displayed in the status column.a.Access your new instance by clicking the link shown at the top of the page: Application "instance_name " migrated successfully Access the Instance at Oracle Integration b.Go to the Integrations page to activate the migrated instance.See Verify Your Environment and Activate Your Integrations .6.If unsuccessful, Failed is displayed in the status column.The logs provide details about what failed.Step 5: Migrate Your Visual Builder Design-Time Metadata You can migrate a visual application from an Oracle Integration Classic instance by importing the application as an archive or by importing it from a Git repository.The credentials for services used by the application are not imported. |
2.Click Start when prompted to start the migration.3.Follow the progress of migration in the Percent Complete column.Chapter 3 Step 4: Migrate Integrations and Processes 3-14 4.Click Migrate Application to view in-progress details about the entire migration process, including: Creating an archive location in the object storage bucket for the design-time metadata.Exporting the design-time metadata of the instance to the archive location.Creating a new Oracle Integration Generation 2 instance.Importing the design-time metadata archive from the object storage bucket into the new instance.Deleting the archive from the object storage bucket when the import completes.5.If successful, Succeeded is displayed in the status column.a.Access your new instance by clicking the link shown at the top of the page: Application "instance_name " migrated successfully Access the Instance at Oracle Integration b.Go to the Integrations page to activate the migrated instance.See Verify Your Environment and Activate Your Integrations .6.If unsuccessful, Failed is displayed in the status column.The logs provide details about what failed.Step 5: Migrate Your Visual Builder Design-Time Metadata You can migrate a visual application from an Oracle Integration Classic instance by importing the application as an archive or by importing it from a Git repository.The credentials for services used by the application are not imported.You need to supply the credentials after creating the new application from the imported sources. |
3.Follow the progress of migration in the Percent Complete column.Chapter 3 Step 4: Migrate Integrations and Processes 3-14 4.Click Migrate Application to view in-progress details about the entire migration process, including: Creating an archive location in the object storage bucket for the design-time metadata.Exporting the design-time metadata of the instance to the archive location.Creating a new Oracle Integration Generation 2 instance.Importing the design-time metadata archive from the object storage bucket into the new instance.Deleting the archive from the object storage bucket when the import completes.5.If successful, Succeeded is displayed in the status column.a.Access your new instance by clicking the link shown at the top of the page: Application "instance_name " migrated successfully Access the Instance at Oracle Integration b.Go to the Integrations page to activate the migrated instance.See Verify Your Environment and Activate Your Integrations .6.If unsuccessful, Failed is displayed in the status column.The logs provide details about what failed.Step 5: Migrate Your Visual Builder Design-Time Metadata You can migrate a visual application from an Oracle Integration Classic instance by importing the application as an archive or by importing it from a Git repository.The credentials for services used by the application are not imported.You need to supply the credentials after creating the new application from the imported sources.Similarly, the entries for mobile build configurations, such as iOS provisioning profiles, keystores, and passwords are not imported. |
Chapter 3 Step 4: Migrate Integrations and Processes 3-14 4.Click Migrate Application to view in-progress details about the entire migration process, including: Creating an archive location in the object storage bucket for the design-time metadata.Exporting the design-time metadata of the instance to the archive location.Creating a new Oracle Integration Generation 2 instance.Importing the design-time metadata archive from the object storage bucket into the new instance.Deleting the archive from the object storage bucket when the import completes.5.If successful, Succeeded is displayed in the status column.a.Access your new instance by clicking the link shown at the top of the page: Application "instance_name " migrated successfully Access the Instance at Oracle Integration b.Go to the Integrations page to activate the migrated instance.See Verify Your Environment and Activate Your Integrations .6.If unsuccessful, Failed is displayed in the status column.The logs provide details about what failed.Step 5: Migrate Your Visual Builder Design-Time Metadata You can migrate a visual application from an Oracle Integration Classic instance by importing the application as an archive or by importing it from a Git repository.The credentials for services used by the application are not imported.You need to supply the credentials after creating the new application from the imported sources.Similarly, the entries for mobile build configurations, such as iOS provisioning profiles, keystores, and passwords are not imported.You need to re-enter these details in the new instance.Chapter 3 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-15Export Visual Builder Design-Time Metadata In your Oracle Integration Classic instance, use the Export action to create a ZIP archive of the visual application you want to migrate to the new instance on Oracle Cloud Infrastructure. |
Exporting the design-time metadata of the instance to the archive location.Creating a new Oracle Integration Generation 2 instance.Importing the design-time metadata archive from the object storage bucket into the new instance.Deleting the archive from the object storage bucket when the import completes.5.If successful, Succeeded is displayed in the status column.a.Access your new instance by clicking the link shown at the top of the page: Application "instance_name " migrated successfully Access the Instance at Oracle Integration b.Go to the Integrations page to activate the migrated instance.See Verify Your Environment and Activate Your Integrations .6.If unsuccessful, Failed is displayed in the status column.The logs provide details about what failed.Step 5: Migrate Your Visual Builder Design-Time Metadata You can migrate a visual application from an Oracle Integration Classic instance by importing the application as an archive or by importing it from a Git repository.The credentials for services used by the application are not imported.You need to supply the credentials after creating the new application from the imported sources.Similarly, the entries for mobile build configurations, such as iOS provisioning profiles, keystores, and passwords are not imported.You need to re-enter these details in the new instance.Chapter 3 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-15Export Visual Builder Design-Time Metadata In your Oracle Integration Classic instance, use the Export action to create a ZIP archive of the visual application you want to migrate to the new instance on Oracle Cloud Infrastructure.When you export the application you can choose if you want the archive to include the development data contained in the applications custom business objects. |
Creating a new Oracle Integration Generation 2 instance.Importing the design-time metadata archive from the object storage bucket into the new instance.Deleting the archive from the object storage bucket when the import completes.5.If successful, Succeeded is displayed in the status column.a.Access your new instance by clicking the link shown at the top of the page: Application "instance_name " migrated successfully Access the Instance at Oracle Integration b.Go to the Integrations page to activate the migrated instance.See Verify Your Environment and Activate Your Integrations .6.If unsuccessful, Failed is displayed in the status column.The logs provide details about what failed.Step 5: Migrate Your Visual Builder Design-Time Metadata You can migrate a visual application from an Oracle Integration Classic instance by importing the application as an archive or by importing it from a Git repository.The credentials for services used by the application are not imported.You need to supply the credentials after creating the new application from the imported sources.Similarly, the entries for mobile build configurations, such as iOS provisioning profiles, keystores, and passwords are not imported.You need to re-enter these details in the new instance.Chapter 3 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-15Export Visual Builder Design-Time Metadata In your Oracle Integration Classic instance, use the Export action to create a ZIP archive of the visual application you want to migrate to the new instance on Oracle Cloud Infrastructure.When you export the application you can choose if you want the archive to include the development data contained in the applications custom business objects.Some information, such as credentials for external REST end points, is removed when you export an application. |
Importing the design-time metadata archive from the object storage bucket into the new instance.Deleting the archive from the object storage bucket when the import completes.5.If successful, Succeeded is displayed in the status column.a.Access your new instance by clicking the link shown at the top of the page: Application "instance_name " migrated successfully Access the Instance at Oracle Integration b.Go to the Integrations page to activate the migrated instance.See Verify Your Environment and Activate Your Integrations .6.If unsuccessful, Failed is displayed in the status column.The logs provide details about what failed.Step 5: Migrate Your Visual Builder Design-Time Metadata You can migrate a visual application from an Oracle Integration Classic instance by importing the application as an archive or by importing it from a Git repository.The credentials for services used by the application are not imported.You need to supply the credentials after creating the new application from the imported sources.Similarly, the entries for mobile build configurations, such as iOS provisioning profiles, keystores, and passwords are not imported.You need to re-enter these details in the new instance.Chapter 3 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-15Export Visual Builder Design-Time Metadata In your Oracle Integration Classic instance, use the Export action to create a ZIP archive of the visual application you want to migrate to the new instance on Oracle Cloud Infrastructure.When you export the application you can choose if you want the archive to include the development data contained in the applications custom business objects.Some information, such as credentials for external REST end points, is removed when you export an application.This information needs to be provided after the archive is imported. |
Deleting the archive from the object storage bucket when the import completes.5.If successful, Succeeded is displayed in the status column.a.Access your new instance by clicking the link shown at the top of the page: Application "instance_name " migrated successfully Access the Instance at Oracle Integration b.Go to the Integrations page to activate the migrated instance.See Verify Your Environment and Activate Your Integrations .6.If unsuccessful, Failed is displayed in the status column.The logs provide details about what failed.Step 5: Migrate Your Visual Builder Design-Time Metadata You can migrate a visual application from an Oracle Integration Classic instance by importing the application as an archive or by importing it from a Git repository.The credentials for services used by the application are not imported.You need to supply the credentials after creating the new application from the imported sources.Similarly, the entries for mobile build configurations, such as iOS provisioning profiles, keystores, and passwords are not imported.You need to re-enter these details in the new instance.Chapter 3 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-15Export Visual Builder Design-Time Metadata In your Oracle Integration Classic instance, use the Export action to create a ZIP archive of the visual application you want to migrate to the new instance on Oracle Cloud Infrastructure.When you export the application you can choose if you want the archive to include the development data contained in the applications custom business objects.Some information, such as credentials for external REST end points, is removed when you export an application.This information needs to be provided after the archive is imported.To export a visual application and its custom business objects: 1.Open the Visual Builder Home page of your Oracle Integration Classic instance. |
5.If successful, Succeeded is displayed in the status column.a.Access your new instance by clicking the link shown at the top of the page: Application "instance_name " migrated successfully Access the Instance at Oracle Integration b.Go to the Integrations page to activate the migrated instance.See Verify Your Environment and Activate Your Integrations .6.If unsuccessful, Failed is displayed in the status column.The logs provide details about what failed.Step 5: Migrate Your Visual Builder Design-Time Metadata You can migrate a visual application from an Oracle Integration Classic instance by importing the application as an archive or by importing it from a Git repository.The credentials for services used by the application are not imported.You need to supply the credentials after creating the new application from the imported sources.Similarly, the entries for mobile build configurations, such as iOS provisioning profiles, keystores, and passwords are not imported.You need to re-enter these details in the new instance.Chapter 3 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-15Export Visual Builder Design-Time Metadata In your Oracle Integration Classic instance, use the Export action to create a ZIP archive of the visual application you want to migrate to the new instance on Oracle Cloud Infrastructure.When you export the application you can choose if you want the archive to include the development data contained in the applications custom business objects.Some information, such as credentials for external REST end points, is removed when you export an application.This information needs to be provided after the archive is imported.To export a visual application and its custom business objects: 1.Open the Visual Builder Home page of your Oracle Integration Classic instance.2.On the Visual Applications home page, open the Application Options menu for the application version you want to export and select Export . |
a.Access your new instance by clicking the link shown at the top of the page: Application "instance_name " migrated successfully Access the Instance at Oracle Integration b.Go to the Integrations page to activate the migrated instance.See Verify Your Environment and Activate Your Integrations .6.If unsuccessful, Failed is displayed in the status column.The logs provide details about what failed.Step 5: Migrate Your Visual Builder Design-Time Metadata You can migrate a visual application from an Oracle Integration Classic instance by importing the application as an archive or by importing it from a Git repository.The credentials for services used by the application are not imported.You need to supply the credentials after creating the new application from the imported sources.Similarly, the entries for mobile build configurations, such as iOS provisioning profiles, keystores, and passwords are not imported.You need to re-enter these details in the new instance.Chapter 3 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-15Export Visual Builder Design-Time Metadata In your Oracle Integration Classic instance, use the Export action to create a ZIP archive of the visual application you want to migrate to the new instance on Oracle Cloud Infrastructure.When you export the application you can choose if you want the archive to include the development data contained in the applications custom business objects.Some information, such as credentials for external REST end points, is removed when you export an application.This information needs to be provided after the archive is imported.To export a visual application and its custom business objects: 1.Open the Visual Builder Home page of your Oracle Integration Classic instance.2.On the Visual Applications home page, open the Application Options menu for the application version you want to export and select Export .If there are multiple versions of an application you must use the Options menu of the version that you want to export. |
See Verify Your Environment and Activate Your Integrations .6.If unsuccessful, Failed is displayed in the status column.The logs provide details about what failed.Step 5: Migrate Your Visual Builder Design-Time Metadata You can migrate a visual application from an Oracle Integration Classic instance by importing the application as an archive or by importing it from a Git repository.The credentials for services used by the application are not imported.You need to supply the credentials after creating the new application from the imported sources.Similarly, the entries for mobile build configurations, such as iOS provisioning profiles, keystores, and passwords are not imported.You need to re-enter these details in the new instance.Chapter 3 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-15Export Visual Builder Design-Time Metadata In your Oracle Integration Classic instance, use the Export action to create a ZIP archive of the visual application you want to migrate to the new instance on Oracle Cloud Infrastructure.When you export the application you can choose if you want the archive to include the development data contained in the applications custom business objects.Some information, such as credentials for external REST end points, is removed when you export an application.This information needs to be provided after the archive is imported.To export a visual application and its custom business objects: 1.Open the Visual Builder Home page of your Oracle Integration Classic instance.2.On the Visual Applications home page, open the Application Options menu for the application version you want to export and select Export .If there are multiple versions of an application you must use the Options menu of the version that you want to export.Alternatively, when a visual application is open, you can choose Export in the applications options menu in the toolbar. |
6.If unsuccessful, Failed is displayed in the status column.The logs provide details about what failed.Step 5: Migrate Your Visual Builder Design-Time Metadata You can migrate a visual application from an Oracle Integration Classic instance by importing the application as an archive or by importing it from a Git repository.The credentials for services used by the application are not imported.You need to supply the credentials after creating the new application from the imported sources.Similarly, the entries for mobile build configurations, such as iOS provisioning profiles, keystores, and passwords are not imported.You need to re-enter these details in the new instance.Chapter 3 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-15Export Visual Builder Design-Time Metadata In your Oracle Integration Classic instance, use the Export action to create a ZIP archive of the visual application you want to migrate to the new instance on Oracle Cloud Infrastructure.When you export the application you can choose if you want the archive to include the development data contained in the applications custom business objects.Some information, such as credentials for external REST end points, is removed when you export an application.This information needs to be provided after the archive is imported.To export a visual application and its custom business objects: 1.Open the Visual Builder Home page of your Oracle Integration Classic instance.2.On the Visual Applications home page, open the Application Options menu for the application version you want to export and select Export .If there are multiple versions of an application you must use the Options menu of the version that you want to export.Alternatively, when a visual application is open, you can choose Export in the applications options menu in the toolbar.3.Click Export with Data in the Export Application dialog box. |
The logs provide details about what failed.Step 5: Migrate Your Visual Builder Design-Time Metadata You can migrate a visual application from an Oracle Integration Classic instance by importing the application as an archive or by importing it from a Git repository.The credentials for services used by the application are not imported.You need to supply the credentials after creating the new application from the imported sources.Similarly, the entries for mobile build configurations, such as iOS provisioning profiles, keystores, and passwords are not imported.You need to re-enter these details in the new instance.Chapter 3 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-15Export Visual Builder Design-Time Metadata In your Oracle Integration Classic instance, use the Export action to create a ZIP archive of the visual application you want to migrate to the new instance on Oracle Cloud Infrastructure.When you export the application you can choose if you want the archive to include the development data contained in the applications custom business objects.Some information, such as credentials for external REST end points, is removed when you export an application.This information needs to be provided after the archive is imported.To export a visual application and its custom business objects: 1.Open the Visual Builder Home page of your Oracle Integration Classic instance.2.On the Visual Applications home page, open the Application Options menu for the application version you want to export and select Export .If there are multiple versions of an application you must use the Options menu of the version that you want to export.Alternatively, when a visual application is open, you can choose Export in the applications options menu in the toolbar.3.Click Export with Data in the Export Application dialog box.When you choose to export the application with data, the archive will include a json file ( entity.json ) and spreadsheet ( entity-data.csv ) for each custom business object. |
Step 5: Migrate Your Visual Builder Design-Time Metadata You can migrate a visual application from an Oracle Integration Classic instance by importing the application as an archive or by importing it from a Git repository.The credentials for services used by the application are not imported.You need to supply the credentials after creating the new application from the imported sources.Similarly, the entries for mobile build configurations, such as iOS provisioning profiles, keystores, and passwords are not imported.You need to re-enter these details in the new instance.Chapter 3 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-15Export Visual Builder Design-Time Metadata In your Oracle Integration Classic instance, use the Export action to create a ZIP archive of the visual application you want to migrate to the new instance on Oracle Cloud Infrastructure.When you export the application you can choose if you want the archive to include the development data contained in the applications custom business objects.Some information, such as credentials for external REST end points, is removed when you export an application.This information needs to be provided after the archive is imported.To export a visual application and its custom business objects: 1.Open the Visual Builder Home page of your Oracle Integration Classic instance.2.On the Visual Applications home page, open the Application Options menu for the application version you want to export and select Export .If there are multiple versions of an application you must use the Options menu of the version that you want to export.Alternatively, when a visual application is open, you can choose Export in the applications options menu in the toolbar.3.Click Export with Data in the Export Application dialog box.When you choose to export the application with data, the archive will include a json file ( entity.json ) and spreadsheet ( entity-data.csv ) for each custom business object.The json file describe the business object and the spreadsheet contains the business object data in the development database. |
The credentials for services used by the application are not imported.You need to supply the credentials after creating the new application from the imported sources.Similarly, the entries for mobile build configurations, such as iOS provisioning profiles, keystores, and passwords are not imported.You need to re-enter these details in the new instance.Chapter 3 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-15Export Visual Builder Design-Time Metadata In your Oracle Integration Classic instance, use the Export action to create a ZIP archive of the visual application you want to migrate to the new instance on Oracle Cloud Infrastructure.When you export the application you can choose if you want the archive to include the development data contained in the applications custom business objects.Some information, such as credentials for external REST end points, is removed when you export an application.This information needs to be provided after the archive is imported.To export a visual application and its custom business objects: 1.Open the Visual Builder Home page of your Oracle Integration Classic instance.2.On the Visual Applications home page, open the Application Options menu for the application version you want to export and select Export .If there are multiple versions of an application you must use the Options menu of the version that you want to export.Alternatively, when a visual application is open, you can choose Export in the applications options menu in the toolbar.3.Click Export with Data in the Export Application dialog box.When you choose to export the application with data, the archive will include a json file ( entity.json ) and spreadsheet ( entity-data.csv ) for each custom business object.The json file describe the business object and the spreadsheet contains the business object data in the development database.If you choose to export the application without data, the archive will only contain the json file describing the business objects. |
You need to supply the credentials after creating the new application from the imported sources.Similarly, the entries for mobile build configurations, such as iOS provisioning profiles, keystores, and passwords are not imported.You need to re-enter these details in the new instance.Chapter 3 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-15Export Visual Builder Design-Time Metadata In your Oracle Integration Classic instance, use the Export action to create a ZIP archive of the visual application you want to migrate to the new instance on Oracle Cloud Infrastructure.When you export the application you can choose if you want the archive to include the development data contained in the applications custom business objects.Some information, such as credentials for external REST end points, is removed when you export an application.This information needs to be provided after the archive is imported.To export a visual application and its custom business objects: 1.Open the Visual Builder Home page of your Oracle Integration Classic instance.2.On the Visual Applications home page, open the Application Options menu for the application version you want to export and select Export .If there are multiple versions of an application you must use the Options menu of the version that you want to export.Alternatively, when a visual application is open, you can choose Export in the applications options menu in the toolbar.3.Click Export with Data in the Export Application dialog box.When you choose to export the application with data, the archive will include a json file ( entity.json ) and spreadsheet ( entity-data.csv ) for each custom business object.The json file describe the business object and the spreadsheet contains the business object data in the development database.If you choose to export the application without data, the archive will only contain the json file describing the business objects.The archive will always include the data for any business objects that are identified as containing Application Setup Data. |
Similarly, the entries for mobile build configurations, such as iOS provisioning profiles, keystores, and passwords are not imported.You need to re-enter these details in the new instance.Chapter 3 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-15Export Visual Builder Design-Time Metadata In your Oracle Integration Classic instance, use the Export action to create a ZIP archive of the visual application you want to migrate to the new instance on Oracle Cloud Infrastructure.When you export the application you can choose if you want the archive to include the development data contained in the applications custom business objects.Some information, such as credentials for external REST end points, is removed when you export an application.This information needs to be provided after the archive is imported.To export a visual application and its custom business objects: 1.Open the Visual Builder Home page of your Oracle Integration Classic instance.2.On the Visual Applications home page, open the Application Options menu for the application version you want to export and select Export .If there are multiple versions of an application you must use the Options menu of the version that you want to export.Alternatively, when a visual application is open, you can choose Export in the applications options menu in the toolbar.3.Click Export with Data in the Export Application dialog box.When you choose to export the application with data, the archive will include a json file ( entity.json ) and spreadsheet ( entity-data.csv ) for each custom business object.The json file describe the business object and the spreadsheet contains the business object data in the development database.If you choose to export the application without data, the archive will only contain the json file describing the business objects.The archive will always include the data for any business objects that are identified as containing Application Setup Data.The visual application and its resources are exported as an archive file. |
You need to re-enter these details in the new instance.Chapter 3 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-15Export Visual Builder Design-Time Metadata In your Oracle Integration Classic instance, use the Export action to create a ZIP archive of the visual application you want to migrate to the new instance on Oracle Cloud Infrastructure.When you export the application you can choose if you want the archive to include the development data contained in the applications custom business objects.Some information, such as credentials for external REST end points, is removed when you export an application.This information needs to be provided after the archive is imported.To export a visual application and its custom business objects: 1.Open the Visual Builder Home page of your Oracle Integration Classic instance.2.On the Visual Applications home page, open the Application Options menu for the application version you want to export and select Export .If there are multiple versions of an application you must use the Options menu of the version that you want to export.Alternatively, when a visual application is open, you can choose Export in the applications options menu in the toolbar.3.Click Export with Data in the Export Application dialog box.When you choose to export the application with data, the archive will include a json file ( entity.json ) and spreadsheet ( entity-data.csv ) for each custom business object.The json file describe the business object and the spreadsheet contains the business object data in the development database.If you choose to export the application without data, the archive will only contain the json file describing the business objects.The archive will always include the data for any business objects that are identified as containing Application Setup Data.The visual application and its resources are exported as an archive file.The archive is saved to your local system in the location specified for your browsers downloads. |
When you export the application you can choose if you want the archive to include the development data contained in the applications custom business objects.Some information, such as credentials for external REST end points, is removed when you export an application.This information needs to be provided after the archive is imported.To export a visual application and its custom business objects: 1.Open the Visual Builder Home page of your Oracle Integration Classic instance.2.On the Visual Applications home page, open the Application Options menu for the application version you want to export and select Export .If there are multiple versions of an application you must use the Options menu of the version that you want to export.Alternatively, when a visual application is open, you can choose Export in the applications options menu in the toolbar.3.Click Export with Data in the Export Application dialog box.When you choose to export the application with data, the archive will include a json file ( entity.json ) and spreadsheet ( entity-data.csv ) for each custom business object.The json file describe the business object and the spreadsheet contains the business object data in the development database.If you choose to export the application without data, the archive will only contain the json file describing the business objects.The archive will always include the data for any business objects that are identified as containing Application Setup Data.The visual application and its resources are exported as an archive file.The archive is saved to your local system in the location specified for your browsers downloads.Import Visual Builder Design-Time Metadata In your new Oracle Integration instance on Oracle Cloud Infrastructure, you create a new visual application by importing the archive of the visual application you exported from the Oracle Integration Classic instance. |
Some information, such as credentials for external REST end points, is removed when you export an application.This information needs to be provided after the archive is imported.To export a visual application and its custom business objects: 1.Open the Visual Builder Home page of your Oracle Integration Classic instance.2.On the Visual Applications home page, open the Application Options menu for the application version you want to export and select Export .If there are multiple versions of an application you must use the Options menu of the version that you want to export.Alternatively, when a visual application is open, you can choose Export in the applications options menu in the toolbar.3.Click Export with Data in the Export Application dialog box.When you choose to export the application with data, the archive will include a json file ( entity.json ) and spreadsheet ( entity-data.csv ) for each custom business object.The json file describe the business object and the spreadsheet contains the business object data in the development database.If you choose to export the application without data, the archive will only contain the json file describing the business objects.The archive will always include the data for any business objects that are identified as containing Application Setup Data.The visual application and its resources are exported as an archive file.The archive is saved to your local system in the location specified for your browsers downloads.Import Visual Builder Design-Time Metadata In your new Oracle Integration instance on Oracle Cloud Infrastructure, you create a new visual application by importing the archive of the visual application you exported from the Oracle Integration Classic instance.To import a visual application archive: 1.Open the Visual Builder Home page on Oracle Cloud Infrastructure. |
This information needs to be provided after the archive is imported.To export a visual application and its custom business objects: 1.Open the Visual Builder Home page of your Oracle Integration Classic instance.2.On the Visual Applications home page, open the Application Options menu for the application version you want to export and select Export .If there are multiple versions of an application you must use the Options menu of the version that you want to export.Alternatively, when a visual application is open, you can choose Export in the applications options menu in the toolbar.3.Click Export with Data in the Export Application dialog box.When you choose to export the application with data, the archive will include a json file ( entity.json ) and spreadsheet ( entity-data.csv ) for each custom business object.The json file describe the business object and the spreadsheet contains the business object data in the development database.If you choose to export the application without data, the archive will only contain the json file describing the business objects.The archive will always include the data for any business objects that are identified as containing Application Setup Data.The visual application and its resources are exported as an archive file.The archive is saved to your local system in the location specified for your browsers downloads.Import Visual Builder Design-Time Metadata In your new Oracle Integration instance on Oracle Cloud Infrastructure, you create a new visual application by importing the archive of the visual application you exported from the Oracle Integration Classic instance.To import a visual application archive: 1.Open the Visual Builder Home page on Oracle Cloud Infrastructure.2.Click Import on the Visual Applications home page. |
To export a visual application and its custom business objects: 1.Open the Visual Builder Home page of your Oracle Integration Classic instance.2.On the Visual Applications home page, open the Application Options menu for the application version you want to export and select Export .If there are multiple versions of an application you must use the Options menu of the version that you want to export.Alternatively, when a visual application is open, you can choose Export in the applications options menu in the toolbar.3.Click Export with Data in the Export Application dialog box.When you choose to export the application with data, the archive will include a json file ( entity.json ) and spreadsheet ( entity-data.csv ) for each custom business object.The json file describe the business object and the spreadsheet contains the business object data in the development database.If you choose to export the application without data, the archive will only contain the json file describing the business objects.The archive will always include the data for any business objects that are identified as containing Application Setup Data.The visual application and its resources are exported as an archive file.The archive is saved to your local system in the location specified for your browsers downloads.Import Visual Builder Design-Time Metadata In your new Oracle Integration instance on Oracle Cloud Infrastructure, you create a new visual application by importing the archive of the visual application you exported from the Oracle Integration Classic instance.To import a visual application archive: 1.Open the Visual Builder Home page on Oracle Cloud Infrastructure.2.Click Import on the Visual Applications home page.3.Click Import from file in the Import Application dialog box. |
2.On the Visual Applications home page, open the Application Options menu for the application version you want to export and select Export .If there are multiple versions of an application you must use the Options menu of the version that you want to export.Alternatively, when a visual application is open, you can choose Export in the applications options menu in the toolbar.3.Click Export with Data in the Export Application dialog box.When you choose to export the application with data, the archive will include a json file ( entity.json ) and spreadsheet ( entity-data.csv ) for each custom business object.The json file describe the business object and the spreadsheet contains the business object data in the development database.If you choose to export the application without data, the archive will only contain the json file describing the business objects.The archive will always include the data for any business objects that are identified as containing Application Setup Data.The visual application and its resources are exported as an archive file.The archive is saved to your local system in the location specified for your browsers downloads.Import Visual Builder Design-Time Metadata In your new Oracle Integration instance on Oracle Cloud Infrastructure, you create a new visual application by importing the archive of the visual application you exported from the Oracle Integration Classic instance.To import a visual application archive: 1.Open the Visual Builder Home page on Oracle Cloud Infrastructure.2.Click Import on the Visual Applications home page.3.Click Import from file in the Import Application dialog box.4.Drag your visual application archive file on your local system into the dialog box. |
If there are multiple versions of an application you must use the Options menu of the version that you want to export.Alternatively, when a visual application is open, you can choose Export in the applications options menu in the toolbar.3.Click Export with Data in the Export Application dialog box.When you choose to export the application with data, the archive will include a json file ( entity.json ) and spreadsheet ( entity-data.csv ) for each custom business object.The json file describe the business object and the spreadsheet contains the business object data in the development database.If you choose to export the application without data, the archive will only contain the json file describing the business objects.The archive will always include the data for any business objects that are identified as containing Application Setup Data.The visual application and its resources are exported as an archive file.The archive is saved to your local system in the location specified for your browsers downloads.Import Visual Builder Design-Time Metadata In your new Oracle Integration instance on Oracle Cloud Infrastructure, you create a new visual application by importing the archive of the visual application you exported from the Oracle Integration Classic instance.To import a visual application archive: 1.Open the Visual Builder Home page on Oracle Cloud Infrastructure.2.Click Import on the Visual Applications home page.3.Click Import from file in the Import Application dialog box.4.Drag your visual application archive file on your local system into the dialog box.Alternatively, click the upload area in the dialog box and use the file browser to locate the archive on your local system. |
Alternatively, when a visual application is open, you can choose Export in the applications options menu in the toolbar.3.Click Export with Data in the Export Application dialog box.When you choose to export the application with data, the archive will include a json file ( entity.json ) and spreadsheet ( entity-data.csv ) for each custom business object.The json file describe the business object and the spreadsheet contains the business object data in the development database.If you choose to export the application without data, the archive will only contain the json file describing the business objects.The archive will always include the data for any business objects that are identified as containing Application Setup Data.The visual application and its resources are exported as an archive file.The archive is saved to your local system in the location specified for your browsers downloads.Import Visual Builder Design-Time Metadata In your new Oracle Integration instance on Oracle Cloud Infrastructure, you create a new visual application by importing the archive of the visual application you exported from the Oracle Integration Classic instance.To import a visual application archive: 1.Open the Visual Builder Home page on Oracle Cloud Infrastructure.2.Click Import on the Visual Applications home page.3.Click Import from file in the Import Application dialog box.4.Drag your visual application archive file on your local system into the dialog box.Alternatively, click the upload area in the dialog box and use the file browser to locate the archive on your local system.5.Enter a valid application name and ID in the dialog. |
3.Click Export with Data in the Export Application dialog box.When you choose to export the application with data, the archive will include a json file ( entity.json ) and spreadsheet ( entity-data.csv ) for each custom business object.The json file describe the business object and the spreadsheet contains the business object data in the development database.If you choose to export the application without data, the archive will only contain the json file describing the business objects.The archive will always include the data for any business objects that are identified as containing Application Setup Data.The visual application and its resources are exported as an archive file.The archive is saved to your local system in the location specified for your browsers downloads.Import Visual Builder Design-Time Metadata In your new Oracle Integration instance on Oracle Cloud Infrastructure, you create a new visual application by importing the archive of the visual application you exported from the Oracle Integration Classic instance.To import a visual application archive: 1.Open the Visual Builder Home page on Oracle Cloud Infrastructure.2.Click Import on the Visual Applications home page.3.Click Import from file in the Import Application dialog box.4.Drag your visual application archive file on your local system into the dialog box.Alternatively, click the upload area in the dialog box and use the file browser to locate the archive on your local system.5.Enter a valid application name and ID in the dialog.Click Import .Chapter 3 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-16After you import a visual application, you might need to provide additional details such as credential to service in the new copy of the application. |
When you choose to export the application with data, the archive will include a json file ( entity.json ) and spreadsheet ( entity-data.csv ) for each custom business object.The json file describe the business object and the spreadsheet contains the business object data in the development database.If you choose to export the application without data, the archive will only contain the json file describing the business objects.The archive will always include the data for any business objects that are identified as containing Application Setup Data.The visual application and its resources are exported as an archive file.The archive is saved to your local system in the location specified for your browsers downloads.Import Visual Builder Design-Time Metadata In your new Oracle Integration instance on Oracle Cloud Infrastructure, you create a new visual application by importing the archive of the visual application you exported from the Oracle Integration Classic instance.To import a visual application archive: 1.Open the Visual Builder Home page on Oracle Cloud Infrastructure.2.Click Import on the Visual Applications home page.3.Click Import from file in the Import Application dialog box.4.Drag your visual application archive file on your local system into the dialog box.Alternatively, click the upload area in the dialog box and use the file browser to locate the archive on your local system.5.Enter a valid application name and ID in the dialog.Click Import .Chapter 3 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-16After you import a visual application, you might need to provide additional details such as credential to service in the new copy of the application.For example, if the application you are importing contains Process definitions, you will be prompted to specify an existing Process application that contains all the process definitions required by the application you are importing. |
The json file describe the business object and the spreadsheet contains the business object data in the development database.If you choose to export the application without data, the archive will only contain the json file describing the business objects.The archive will always include the data for any business objects that are identified as containing Application Setup Data.The visual application and its resources are exported as an archive file.The archive is saved to your local system in the location specified for your browsers downloads.Import Visual Builder Design-Time Metadata In your new Oracle Integration instance on Oracle Cloud Infrastructure, you create a new visual application by importing the archive of the visual application you exported from the Oracle Integration Classic instance.To import a visual application archive: 1.Open the Visual Builder Home page on Oracle Cloud Infrastructure.2.Click Import on the Visual Applications home page.3.Click Import from file in the Import Application dialog box.4.Drag your visual application archive file on your local system into the dialog box.Alternatively, click the upload area in the dialog box and use the file browser to locate the archive on your local system.5.Enter a valid application name and ID in the dialog.Click Import .Chapter 3 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-16After you import a visual application, you might need to provide additional details such as credential to service in the new copy of the application.For example, if the application you are importing contains Process definitions, you will be prompted to specify an existing Process application that contains all the process definitions required by the application you are importing.Import Visual Builder Design-Time Metadata from a Git Repository If your visual application's sources are stored in a Git repository hosted on Oracle Developer Cloud Service, you can import the application by configuring the connection to the Git repository and creating the application from the imported sources. |
If you choose to export the application without data, the archive will only contain the json file describing the business objects.The archive will always include the data for any business objects that are identified as containing Application Setup Data.The visual application and its resources are exported as an archive file.The archive is saved to your local system in the location specified for your browsers downloads.Import Visual Builder Design-Time Metadata In your new Oracle Integration instance on Oracle Cloud Infrastructure, you create a new visual application by importing the archive of the visual application you exported from the Oracle Integration Classic instance.To import a visual application archive: 1.Open the Visual Builder Home page on Oracle Cloud Infrastructure.2.Click Import on the Visual Applications home page.3.Click Import from file in the Import Application dialog box.4.Drag your visual application archive file on your local system into the dialog box.Alternatively, click the upload area in the dialog box and use the file browser to locate the archive on your local system.5.Enter a valid application name and ID in the dialog.Click Import .Chapter 3 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-16After you import a visual application, you might need to provide additional details such as credential to service in the new copy of the application.For example, if the application you are importing contains Process definitions, you will be prompted to specify an existing Process application that contains all the process definitions required by the application you are importing.Import Visual Builder Design-Time Metadata from a Git Repository If your visual application's sources are stored in a Git repository hosted on Oracle Developer Cloud Service, you can import the application by configuring the connection to the Git repository and creating the application from the imported sources.To import a visual application from a Git repository: 1.Open the Oracle Visual Builder instance on Oracle Cloud Infrastructure. |
The archive will always include the data for any business objects that are identified as containing Application Setup Data.The visual application and its resources are exported as an archive file.The archive is saved to your local system in the location specified for your browsers downloads.Import Visual Builder Design-Time Metadata In your new Oracle Integration instance on Oracle Cloud Infrastructure, you create a new visual application by importing the archive of the visual application you exported from the Oracle Integration Classic instance.To import a visual application archive: 1.Open the Visual Builder Home page on Oracle Cloud Infrastructure.2.Click Import on the Visual Applications home page.3.Click Import from file in the Import Application dialog box.4.Drag your visual application archive file on your local system into the dialog box.Alternatively, click the upload area in the dialog box and use the file browser to locate the archive on your local system.5.Enter a valid application name and ID in the dialog.Click Import .Chapter 3 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-16After you import a visual application, you might need to provide additional details such as credential to service in the new copy of the application.For example, if the application you are importing contains Process definitions, you will be prompted to specify an existing Process application that contains all the process definitions required by the application you are importing.Import Visual Builder Design-Time Metadata from a Git Repository If your visual application's sources are stored in a Git repository hosted on Oracle Developer Cloud Service, you can import the application by configuring the connection to the Git repository and creating the application from the imported sources.To import a visual application from a Git repository: 1.Open the Oracle Visual Builder instance on Oracle Cloud Infrastructure.2.Click Import on the Visual Applications home page. |
The visual application and its resources are exported as an archive file.The archive is saved to your local system in the location specified for your browsers downloads.Import Visual Builder Design-Time Metadata In your new Oracle Integration instance on Oracle Cloud Infrastructure, you create a new visual application by importing the archive of the visual application you exported from the Oracle Integration Classic instance.To import a visual application archive: 1.Open the Visual Builder Home page on Oracle Cloud Infrastructure.2.Click Import on the Visual Applications home page.3.Click Import from file in the Import Application dialog box.4.Drag your visual application archive file on your local system into the dialog box.Alternatively, click the upload area in the dialog box and use the file browser to locate the archive on your local system.5.Enter a valid application name and ID in the dialog.Click Import .Chapter 3 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-16After you import a visual application, you might need to provide additional details such as credential to service in the new copy of the application.For example, if the application you are importing contains Process definitions, you will be prompted to specify an existing Process application that contains all the process definitions required by the application you are importing.Import Visual Builder Design-Time Metadata from a Git Repository If your visual application's sources are stored in a Git repository hosted on Oracle Developer Cloud Service, you can import the application by configuring the connection to the Git repository and creating the application from the imported sources.To import a visual application from a Git repository: 1.Open the Oracle Visual Builder instance on Oracle Cloud Infrastructure.2.Click Import on the Visual Applications home page.3.Click Application from GIT in the Import dialog box. |
The archive is saved to your local system in the location specified for your browsers downloads.Import Visual Builder Design-Time Metadata In your new Oracle Integration instance on Oracle Cloud Infrastructure, you create a new visual application by importing the archive of the visual application you exported from the Oracle Integration Classic instance.To import a visual application archive: 1.Open the Visual Builder Home page on Oracle Cloud Infrastructure.2.Click Import on the Visual Applications home page.3.Click Import from file in the Import Application dialog box.4.Drag your visual application archive file on your local system into the dialog box.Alternatively, click the upload area in the dialog box and use the file browser to locate the archive on your local system.5.Enter a valid application name and ID in the dialog.Click Import .Chapter 3 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-16After you import a visual application, you might need to provide additional details such as credential to service in the new copy of the application.For example, if the application you are importing contains Process definitions, you will be prompted to specify an existing Process application that contains all the process definitions required by the application you are importing.Import Visual Builder Design-Time Metadata from a Git Repository If your visual application's sources are stored in a Git repository hosted on Oracle Developer Cloud Service, you can import the application by configuring the connection to the Git repository and creating the application from the imported sources.To import a visual application from a Git repository: 1.Open the Oracle Visual Builder instance on Oracle Cloud Infrastructure.2.Click Import on the Visual Applications home page.3.Click Application from GIT in the Import dialog box.4.Click Add Credentials in the Import Application from GIT dialog box. |
Import Visual Builder Design-Time Metadata In your new Oracle Integration instance on Oracle Cloud Infrastructure, you create a new visual application by importing the archive of the visual application you exported from the Oracle Integration Classic instance.To import a visual application archive: 1.Open the Visual Builder Home page on Oracle Cloud Infrastructure.2.Click Import on the Visual Applications home page.3.Click Import from file in the Import Application dialog box.4.Drag your visual application archive file on your local system into the dialog box.Alternatively, click the upload area in the dialog box and use the file browser to locate the archive on your local system.5.Enter a valid application name and ID in the dialog.Click Import .Chapter 3 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-16After you import a visual application, you might need to provide additional details such as credential to service in the new copy of the application.For example, if the application you are importing contains Process definitions, you will be prompted to specify an existing Process application that contains all the process definitions required by the application you are importing.Import Visual Builder Design-Time Metadata from a Git Repository If your visual application's sources are stored in a Git repository hosted on Oracle Developer Cloud Service, you can import the application by configuring the connection to the Git repository and creating the application from the imported sources.To import a visual application from a Git repository: 1.Open the Oracle Visual Builder instance on Oracle Cloud Infrastructure.2.Click Import on the Visual Applications home page.3.Click Application from GIT in the Import dialog box.4.Click Add Credentials in the Import Application from GIT dialog box.5.Enter the URL, username and password for your Oracle Developer Cloud Service account. |
To import a visual application archive: 1.Open the Visual Builder Home page on Oracle Cloud Infrastructure.2.Click Import on the Visual Applications home page.3.Click Import from file in the Import Application dialog box.4.Drag your visual application archive file on your local system into the dialog box.Alternatively, click the upload area in the dialog box and use the file browser to locate the archive on your local system.5.Enter a valid application name and ID in the dialog.Click Import .Chapter 3 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-16After you import a visual application, you might need to provide additional details such as credential to service in the new copy of the application.For example, if the application you are importing contains Process definitions, you will be prompted to specify an existing Process application that contains all the process definitions required by the application you are importing.Import Visual Builder Design-Time Metadata from a Git Repository If your visual application's sources are stored in a Git repository hosted on Oracle Developer Cloud Service, you can import the application by configuring the connection to the Git repository and creating the application from the imported sources.To import a visual application from a Git repository: 1.Open the Oracle Visual Builder instance on Oracle Cloud Infrastructure.2.Click Import on the Visual Applications home page.3.Click Application from GIT in the Import dialog box.4.Click Add Credentials in the Import Application from GIT dialog box.5.Enter the URL, username and password for your Oracle Developer Cloud Service account.Click Save Credentials . |
2.Click Import on the Visual Applications home page.3.Click Import from file in the Import Application dialog box.4.Drag your visual application archive file on your local system into the dialog box.Alternatively, click the upload area in the dialog box and use the file browser to locate the archive on your local system.5.Enter a valid application name and ID in the dialog.Click Import .Chapter 3 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-16After you import a visual application, you might need to provide additional details such as credential to service in the new copy of the application.For example, if the application you are importing contains Process definitions, you will be prompted to specify an existing Process application that contains all the process definitions required by the application you are importing.Import Visual Builder Design-Time Metadata from a Git Repository If your visual application's sources are stored in a Git repository hosted on Oracle Developer Cloud Service, you can import the application by configuring the connection to the Git repository and creating the application from the imported sources.To import a visual application from a Git repository: 1.Open the Oracle Visual Builder instance on Oracle Cloud Infrastructure.2.Click Import on the Visual Applications home page.3.Click Application from GIT in the Import dialog box.4.Click Add Credentials in the Import Application from GIT dialog box.5.Enter the URL, username and password for your Oracle Developer Cloud Service account.Click Save Credentials .After your credentials are checked and saved, the new credentials are added to the list in the Configure DevCS Credentials dialog box. |
3.Click Import from file in the Import Application dialog box.4.Drag your visual application archive file on your local system into the dialog box.Alternatively, click the upload area in the dialog box and use the file browser to locate the archive on your local system.5.Enter a valid application name and ID in the dialog.Click Import .Chapter 3 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-16After you import a visual application, you might need to provide additional details such as credential to service in the new copy of the application.For example, if the application you are importing contains Process definitions, you will be prompted to specify an existing Process application that contains all the process definitions required by the application you are importing.Import Visual Builder Design-Time Metadata from a Git Repository If your visual application's sources are stored in a Git repository hosted on Oracle Developer Cloud Service, you can import the application by configuring the connection to the Git repository and creating the application from the imported sources.To import a visual application from a Git repository: 1.Open the Oracle Visual Builder instance on Oracle Cloud Infrastructure.2.Click Import on the Visual Applications home page.3.Click Application from GIT in the Import dialog box.4.Click Add Credentials in the Import Application from GIT dialog box.5.Enter the URL, username and password for your Oracle Developer Cloud Service account.Click Save Credentials .After your credentials are checked and saved, the new credentials are added to the list in the Configure DevCS Credentials dialog box.6.Select the URL of your account in the DevCS URL with Credentials field. |
4.Drag your visual application archive file on your local system into the dialog box.Alternatively, click the upload area in the dialog box and use the file browser to locate the archive on your local system.5.Enter a valid application name and ID in the dialog.Click Import .Chapter 3 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-16After you import a visual application, you might need to provide additional details such as credential to service in the new copy of the application.For example, if the application you are importing contains Process definitions, you will be prompted to specify an existing Process application that contains all the process definitions required by the application you are importing.Import Visual Builder Design-Time Metadata from a Git Repository If your visual application's sources are stored in a Git repository hosted on Oracle Developer Cloud Service, you can import the application by configuring the connection to the Git repository and creating the application from the imported sources.To import a visual application from a Git repository: 1.Open the Oracle Visual Builder instance on Oracle Cloud Infrastructure.2.Click Import on the Visual Applications home page.3.Click Application from GIT in the Import dialog box.4.Click Add Credentials in the Import Application from GIT dialog box.5.Enter the URL, username and password for your Oracle Developer Cloud Service account.Click Save Credentials .After your credentials are checked and saved, the new credentials are added to the list in the Configure DevCS Credentials dialog box.6.Select the URL of your account in the DevCS URL with Credentials field.7.Select the project, repository and branch of the application's sources. |
Alternatively, click the upload area in the dialog box and use the file browser to locate the archive on your local system.5.Enter a valid application name and ID in the dialog.Click Import .Chapter 3 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-16After you import a visual application, you might need to provide additional details such as credential to service in the new copy of the application.For example, if the application you are importing contains Process definitions, you will be prompted to specify an existing Process application that contains all the process definitions required by the application you are importing.Import Visual Builder Design-Time Metadata from a Git Repository If your visual application's sources are stored in a Git repository hosted on Oracle Developer Cloud Service, you can import the application by configuring the connection to the Git repository and creating the application from the imported sources.To import a visual application from a Git repository: 1.Open the Oracle Visual Builder instance on Oracle Cloud Infrastructure.2.Click Import on the Visual Applications home page.3.Click Application from GIT in the Import dialog box.4.Click Add Credentials in the Import Application from GIT dialog box.5.Enter the URL, username and password for your Oracle Developer Cloud Service account.Click Save Credentials .After your credentials are checked and saved, the new credentials are added to the list in the Configure DevCS Credentials dialog box.6.Select the URL of your account in the DevCS URL with Credentials field.7.Select the project, repository and branch of the application's sources.8.Enter a valid application name and ID. |
5.Enter a valid application name and ID in the dialog.Click Import .Chapter 3 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-16After you import a visual application, you might need to provide additional details such as credential to service in the new copy of the application.For example, if the application you are importing contains Process definitions, you will be prompted to specify an existing Process application that contains all the process definitions required by the application you are importing.Import Visual Builder Design-Time Metadata from a Git Repository If your visual application's sources are stored in a Git repository hosted on Oracle Developer Cloud Service, you can import the application by configuring the connection to the Git repository and creating the application from the imported sources.To import a visual application from a Git repository: 1.Open the Oracle Visual Builder instance on Oracle Cloud Infrastructure.2.Click Import on the Visual Applications home page.3.Click Application from GIT in the Import dialog box.4.Click Add Credentials in the Import Application from GIT dialog box.5.Enter the URL, username and password for your Oracle Developer Cloud Service account.Click Save Credentials .After your credentials are checked and saved, the new credentials are added to the list in the Configure DevCS Credentials dialog box.6.Select the URL of your account in the DevCS URL with Credentials field.7.Select the project, repository and branch of the application's sources.8.Enter a valid application name and ID.Click Import . |
Click Import .Chapter 3 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-16After you import a visual application, you might need to provide additional details such as credential to service in the new copy of the application.For example, if the application you are importing contains Process definitions, you will be prompted to specify an existing Process application that contains all the process definitions required by the application you are importing.Import Visual Builder Design-Time Metadata from a Git Repository If your visual application's sources are stored in a Git repository hosted on Oracle Developer Cloud Service, you can import the application by configuring the connection to the Git repository and creating the application from the imported sources.To import a visual application from a Git repository: 1.Open the Oracle Visual Builder instance on Oracle Cloud Infrastructure.2.Click Import on the Visual Applications home page.3.Click Application from GIT in the Import dialog box.4.Click Add Credentials in the Import Application from GIT dialog box.5.Enter the URL, username and password for your Oracle Developer Cloud Service account.Click Save Credentials .After your credentials are checked and saved, the new credentials are added to the list in the Configure DevCS Credentials dialog box.6.Select the URL of your account in the DevCS URL with Credentials field.7.Select the project, repository and branch of the application's sources.8.Enter a valid application name and ID.Click Import .After you import a visual application, you might need to provide additional details such as credential to service in the new copy of the application. |
For example, if the application you are importing contains Process definitions, you will be prompted to specify an existing Process application that contains all the process definitions required by the application you are importing.Import Visual Builder Design-Time Metadata from a Git Repository If your visual application's sources are stored in a Git repository hosted on Oracle Developer Cloud Service, you can import the application by configuring the connection to the Git repository and creating the application from the imported sources.To import a visual application from a Git repository: 1.Open the Oracle Visual Builder instance on Oracle Cloud Infrastructure.2.Click Import on the Visual Applications home page.3.Click Application from GIT in the Import dialog box.4.Click Add Credentials in the Import Application from GIT dialog box.5.Enter the URL, username and password for your Oracle Developer Cloud Service account.Click Save Credentials .After your credentials are checked and saved, the new credentials are added to the list in the Configure DevCS Credentials dialog box.6.Select the URL of your account in the DevCS URL with Credentials field.7.Select the project, repository and branch of the application's sources.8.Enter a valid application name and ID.Click Import .After you import a visual application, you might need to provide additional details such as credential to service in the new copy of the application.For example, if the application you are importing contains Process definitions, you will be prompted to specify an existing Process application that contains all the process definitions required by the application you are importing.Chapter 3 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-174 Complete the Post-Migration Tasks After successfully migrating your Oracle Integration Classic instances to Oracle Cloud Infrastructure, test your integrations thoroughly, and then perform cleanup and other optional configuration tasks. |
Import Visual Builder Design-Time Metadata from a Git Repository If your visual application's sources are stored in a Git repository hosted on Oracle Developer Cloud Service, you can import the application by configuring the connection to the Git repository and creating the application from the imported sources.To import a visual application from a Git repository: 1.Open the Oracle Visual Builder instance on Oracle Cloud Infrastructure.2.Click Import on the Visual Applications home page.3.Click Application from GIT in the Import dialog box.4.Click Add Credentials in the Import Application from GIT dialog box.5.Enter the URL, username and password for your Oracle Developer Cloud Service account.Click Save Credentials .After your credentials are checked and saved, the new credentials are added to the list in the Configure DevCS Credentials dialog box.6.Select the URL of your account in the DevCS URL with Credentials field.7.Select the project, repository and branch of the application's sources.8.Enter a valid application name and ID.Click Import .After you import a visual application, you might need to provide additional details such as credential to service in the new copy of the application.For example, if the application you are importing contains Process definitions, you will be prompted to specify an existing Process application that contains all the process definitions required by the application you are importing.Chapter 3 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-174 Complete the Post-Migration Tasks After successfully migrating your Oracle Integration Classic instances to Oracle Cloud Infrastructure, test your integrations thoroughly, and then perform cleanup and other optional configuration tasks.Topics: Verify Your Environment and Activate Your Integrations Complete Post-Migration Tasks for Processes Complete Post-Migration Tasks for Visual Builder Applications Verify Your Environment and Activate Your Integrations After Integrations migration to Oracle Integration is complete, perform the following post- migration tasks. |
To import a visual application from a Git repository: 1.Open the Oracle Visual Builder instance on Oracle Cloud Infrastructure.2.Click Import on the Visual Applications home page.3.Click Application from GIT in the Import dialog box.4.Click Add Credentials in the Import Application from GIT dialog box.5.Enter the URL, username and password for your Oracle Developer Cloud Service account.Click Save Credentials .After your credentials are checked and saved, the new credentials are added to the list in the Configure DevCS Credentials dialog box.6.Select the URL of your account in the DevCS URL with Credentials field.7.Select the project, repository and branch of the application's sources.8.Enter a valid application name and ID.Click Import .After you import a visual application, you might need to provide additional details such as credential to service in the new copy of the application.For example, if the application you are importing contains Process definitions, you will be prompted to specify an existing Process application that contains all the process definitions required by the application you are importing.Chapter 3 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-174 Complete the Post-Migration Tasks After successfully migrating your Oracle Integration Classic instances to Oracle Cloud Infrastructure, test your integrations thoroughly, and then perform cleanup and other optional configuration tasks.Topics: Verify Your Environment and Activate Your Integrations Complete Post-Migration Tasks for Processes Complete Post-Migration Tasks for Visual Builder Applications Verify Your Environment and Activate Your Integrations After Integrations migration to Oracle Integration is complete, perform the following post- migration tasks.1.Verify your integrations (for example, check the connections, lookups, and more). |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.