text
stringlengths 65
20k
|
|---|
Step 2: Create a User and Group and Add Policies To export design-time metadata into an Oracle Integration instance, you must also create a user and group and add policies that enable you to perform the migration.1.Open the navigation menu.2.Go to Governance and Administration > Identity > Users to create the user to use for migration.3.Click Create User .4.Enter a name and description.5.Click Create .6.Under Governance and Administration , go to Identity , then click Groups .A list of the groups in your tenancy is displayed.7.Click Create Group to export your design-time metadata.8.Enter a name and description.9.Click Create Group .You are now ready to add the user to the group.When configuration is complete, users in this group can export design-time metadata into Oracle Integration.10.Locate the group you created in the list.11.Click the group. |
1.Open the navigation menu.2.Go to Governance and Administration > Identity > Users to create the user to use for migration.3.Click Create User .4.Enter a name and description.5.Click Create .6.Under Governance and Administration , go to Identity , then click Groups .A list of the groups in your tenancy is displayed.7.Click Create Group to export your design-time metadata.8.Enter a name and description.9.Click Create Group .You are now ready to add the user to the group.When configuration is complete, users in this group can export design-time metadata into Oracle Integration.10.Locate the group you created in the list.11.Click the group.Its details are displayed. |
2.Go to Governance and Administration > Identity > Users to create the user to use for migration.3.Click Create User .4.Enter a name and description.5.Click Create .6.Under Governance and Administration , go to Identity , then click Groups .A list of the groups in your tenancy is displayed.7.Click Create Group to export your design-time metadata.8.Enter a name and description.9.Click Create Group .You are now ready to add the user to the group.When configuration is complete, users in this group can export design-time metadata into Oracle Integration.10.Locate the group you created in the list.11.Click the group.Its details are displayed.12.Click Add User to Group . |
3.Click Create User .4.Enter a name and description.5.Click Create .6.Under Governance and Administration , go to Identity , then click Groups .A list of the groups in your tenancy is displayed.7.Click Create Group to export your design-time metadata.8.Enter a name and description.9.Click Create Group .You are now ready to add the user to the group.When configuration is complete, users in this group can export design-time metadata into Oracle Integration.10.Locate the group you created in the list.11.Click the group.Its details are displayed.12.Click Add User to Group .13.Select the user you created from the list, then click Add User . |
4.Enter a name and description.5.Click Create .6.Under Governance and Administration , go to Identity , then click Groups .A list of the groups in your tenancy is displayed.7.Click Create Group to export your design-time metadata.8.Enter a name and description.9.Click Create Group .You are now ready to add the user to the group.When configuration is complete, users in this group can export design-time metadata into Oracle Integration.10.Locate the group you created in the list.11.Click the group.Its details are displayed.12.Click Add User to Group .13.Select the user you created from the list, then click Add User .14.Return to the navigation menu. |
5.Click Create .6.Under Governance and Administration , go to Identity , then click Groups .A list of the groups in your tenancy is displayed.7.Click Create Group to export your design-time metadata.8.Enter a name and description.9.Click Create Group .You are now ready to add the user to the group.When configuration is complete, users in this group can export design-time metadata into Oracle Integration.10.Locate the group you created in the list.11.Click the group.Its details are displayed.12.Click Add User to Group .13.Select the user you created from the list, then click Add User .14.Return to the navigation menu.15.Under Governance and Administration , go to Identity , then click Policies . |
6.Under Governance and Administration , go to Identity , then click Groups .A list of the groups in your tenancy is displayed.7.Click Create Group to export your design-time metadata.8.Enter a name and description.9.Click Create Group .You are now ready to add the user to the group.When configuration is complete, users in this group can export design-time metadata into Oracle Integration.10.Locate the group you created in the list.11.Click the group.Its details are displayed.12.Click Add User to Group .13.Select the user you created from the list, then click Add User .14.Return to the navigation menu.15.Under Governance and Administration , go to Identity , then click Policies .16.Select the compartment you previously created. |
A list of the groups in your tenancy is displayed.7.Click Create Group to export your design-time metadata.8.Enter a name and description.9.Click Create Group .You are now ready to add the user to the group.When configuration is complete, users in this group can export design-time metadata into Oracle Integration.10.Locate the group you created in the list.11.Click the group.Its details are displayed.12.Click Add User to Group .13.Select the user you created from the list, then click Add User .14.Return to the navigation menu.15.Under Governance and Administration , go to Identity , then click Policies .16.Select the compartment you previously created.17.Click Create Policy . |
7.Click Create Group to export your design-time metadata.8.Enter a name and description.9.Click Create Group .You are now ready to add the user to the group.When configuration is complete, users in this group can export design-time metadata into Oracle Integration.10.Locate the group you created in the list.11.Click the group.Its details are displayed.12.Click Add User to Group .13.Select the user you created from the list, then click Add User .14.Return to the navigation menu.15.Under Governance and Administration , go to Identity , then click Policies .16.Select the compartment you previously created.17.Click Create Policy .18.Enter a name and optional description. |
8.Enter a name and description.9.Click Create Group .You are now ready to add the user to the group.When configuration is complete, users in this group can export design-time metadata into Oracle Integration.10.Locate the group you created in the list.11.Click the group.Its details are displayed.12.Click Add User to Group .13.Select the user you created from the list, then click Add User .14.Return to the navigation menu.15.Under Governance and Administration , go to Identity , then click Policies .16.Select the compartment you previously created.17.Click Create Policy .18.Enter a name and optional description.19.Leave KEEP POLICY CURRENT as the Policy Versioning selection. |
9.Click Create Group .You are now ready to add the user to the group.When configuration is complete, users in this group can export design-time metadata into Oracle Integration.10.Locate the group you created in the list.11.Click the group.Its details are displayed.12.Click Add User to Group .13.Select the user you created from the list, then click Add User .14.Return to the navigation menu.15.Under Governance and Administration , go to Identity , then click Policies .16.Select the compartment you previously created.17.Click Create Policy .18.Enter a name and optional description.19.Leave KEEP POLICY CURRENT as the Policy Versioning selection.20.Add the following statements to migrate to Oracle Integration Generation 2. |
You are now ready to add the user to the group.When configuration is complete, users in this group can export design-time metadata into Oracle Integration.10.Locate the group you created in the list.11.Click the group.Its details are displayed.12.Click Add User to Group .13.Select the user you created from the list, then click Add User .14.Return to the navigation menu.15.Under Governance and Administration , go to Identity , then click Policies .16.Select the compartment you previously created.17.Click Create Policy .18.Enter a name and optional description.19.Leave KEEP POLICY CURRENT as the Policy Versioning selection.20.Add the following statements to migrate to Oracle Integration Generation 2.The statements to add are based on the migration tool you use.Chapter 3 Step 2: Create a User and Group and Add Policies 3-3Migration Tool Statements If using Application Migration ServiceAdd these statements: allow service applicationmigration to inspect compartments in tenancy allow service applicationmigration to { TENANCY_INSPECT } in tenancy allow service applicationmigration to { IDENTITY_PROVIDER_INSPECT } in tenancy allow service applicationmigration to manage database-family in tenancy allow service applicationmigration to use vcns in tenancy allow service applicationmigration to use subnets in tenancy allow service applicationmigration to use vnics in tenancy allow service applicationmigration to { VNIC_ATTACHMENT_READ } in tenancy allow service applicationmigration to { INSTANCE_INSPECT } in tenancy allow service applicationmigration to manage analytics-instances in tenancy allow service applicationmigration to manage integration-instances in tenancy allow service PSM to inspect vcns in tenancy allow service PSM to use subnets in tenancy allow service PSM to use vnics in tenancy allow service PSM to manage security-lists in tenancy allow service PSM to inspect database-family in tenancy If using a different migration tool, for example: Import tool to export and import Processes design-time metadata curl or postman command to export and import Integrations and Processes design-time metadataAdd the following statements. |
When configuration is complete, users in this group can export design-time metadata into Oracle Integration.10.Locate the group you created in the list.11.Click the group.Its details are displayed.12.Click Add User to Group .13.Select the user you created from the list, then click Add User .14.Return to the navigation menu.15.Under Governance and Administration , go to Identity , then click Policies .16.Select the compartment you previously created.17.Click Create Policy .18.Enter a name and optional description.19.Leave KEEP POLICY CURRENT as the Policy Versioning selection.20.Add the following statements to migrate to Oracle Integration Generation 2.The statements to add are based on the migration tool you use.Chapter 3 Step 2: Create a User and Group and Add Policies 3-3Migration Tool Statements If using Application Migration ServiceAdd these statements: allow service applicationmigration to inspect compartments in tenancy allow service applicationmigration to { TENANCY_INSPECT } in tenancy allow service applicationmigration to { IDENTITY_PROVIDER_INSPECT } in tenancy allow service applicationmigration to manage database-family in tenancy allow service applicationmigration to use vcns in tenancy allow service applicationmigration to use subnets in tenancy allow service applicationmigration to use vnics in tenancy allow service applicationmigration to { VNIC_ATTACHMENT_READ } in tenancy allow service applicationmigration to { INSTANCE_INSPECT } in tenancy allow service applicationmigration to manage analytics-instances in tenancy allow service applicationmigration to manage integration-instances in tenancy allow service PSM to inspect vcns in tenancy allow service PSM to use subnets in tenancy allow service PSM to use vnics in tenancy allow service PSM to manage security-lists in tenancy allow service PSM to inspect database-family in tenancy If using a different migration tool, for example: Import tool to export and import Processes design-time metadata curl or postman command to export and import Integrations and Processes design-time metadataAdd the following statements.allow group Upgrade_Group to manage buckets in compartment Upgrade_Compartment allow group Upgrade_Group to manage objects in compartment Upgrade_Compartment where any {request.permission=OBJECT_CREATE,request.permissi on=OBJECT_DELETE,request.permission=OBJECT_INSPEC T} where: Upgrade_Group is the group you created. |
10.Locate the group you created in the list.11.Click the group.Its details are displayed.12.Click Add User to Group .13.Select the user you created from the list, then click Add User .14.Return to the navigation menu.15.Under Governance and Administration , go to Identity , then click Policies .16.Select the compartment you previously created.17.Click Create Policy .18.Enter a name and optional description.19.Leave KEEP POLICY CURRENT as the Policy Versioning selection.20.Add the following statements to migrate to Oracle Integration Generation 2.The statements to add are based on the migration tool you use.Chapter 3 Step 2: Create a User and Group and Add Policies 3-3Migration Tool Statements If using Application Migration ServiceAdd these statements: allow service applicationmigration to inspect compartments in tenancy allow service applicationmigration to { TENANCY_INSPECT } in tenancy allow service applicationmigration to { IDENTITY_PROVIDER_INSPECT } in tenancy allow service applicationmigration to manage database-family in tenancy allow service applicationmigration to use vcns in tenancy allow service applicationmigration to use subnets in tenancy allow service applicationmigration to use vnics in tenancy allow service applicationmigration to { VNIC_ATTACHMENT_READ } in tenancy allow service applicationmigration to { INSTANCE_INSPECT } in tenancy allow service applicationmigration to manage analytics-instances in tenancy allow service applicationmigration to manage integration-instances in tenancy allow service PSM to inspect vcns in tenancy allow service PSM to use subnets in tenancy allow service PSM to use vnics in tenancy allow service PSM to manage security-lists in tenancy allow service PSM to inspect database-family in tenancy If using a different migration tool, for example: Import tool to export and import Processes design-time metadata curl or postman command to export and import Integrations and Processes design-time metadataAdd the following statements.allow group Upgrade_Group to manage buckets in compartment Upgrade_Compartment allow group Upgrade_Group to manage objects in compartment Upgrade_Compartment where any {request.permission=OBJECT_CREATE,request.permissi on=OBJECT_DELETE,request.permission=OBJECT_INSPEC T} where: Upgrade_Group is the group you created.Upgrade_Compartment is the compartment you created. |
11.Click the group.Its details are displayed.12.Click Add User to Group .13.Select the user you created from the list, then click Add User .14.Return to the navigation menu.15.Under Governance and Administration , go to Identity , then click Policies .16.Select the compartment you previously created.17.Click Create Policy .18.Enter a name and optional description.19.Leave KEEP POLICY CURRENT as the Policy Versioning selection.20.Add the following statements to migrate to Oracle Integration Generation 2.The statements to add are based on the migration tool you use.Chapter 3 Step 2: Create a User and Group and Add Policies 3-3Migration Tool Statements If using Application Migration ServiceAdd these statements: allow service applicationmigration to inspect compartments in tenancy allow service applicationmigration to { TENANCY_INSPECT } in tenancy allow service applicationmigration to { IDENTITY_PROVIDER_INSPECT } in tenancy allow service applicationmigration to manage database-family in tenancy allow service applicationmigration to use vcns in tenancy allow service applicationmigration to use subnets in tenancy allow service applicationmigration to use vnics in tenancy allow service applicationmigration to { VNIC_ATTACHMENT_READ } in tenancy allow service applicationmigration to { INSTANCE_INSPECT } in tenancy allow service applicationmigration to manage analytics-instances in tenancy allow service applicationmigration to manage integration-instances in tenancy allow service PSM to inspect vcns in tenancy allow service PSM to use subnets in tenancy allow service PSM to use vnics in tenancy allow service PSM to manage security-lists in tenancy allow service PSM to inspect database-family in tenancy If using a different migration tool, for example: Import tool to export and import Processes design-time metadata curl or postman command to export and import Integrations and Processes design-time metadataAdd the following statements.allow group Upgrade_Group to manage buckets in compartment Upgrade_Compartment allow group Upgrade_Group to manage objects in compartment Upgrade_Compartment where any {request.permission=OBJECT_CREATE,request.permissi on=OBJECT_DELETE,request.permission=OBJECT_INSPEC T} where: Upgrade_Group is the group you created.Upgrade_Compartment is the compartment you created.This action enables users in this group to export design-time metadata to Oracle Integration.Chapter 3 Step 2: Create a User and Group and Add Policies 3-421.Click Create . |
Its details are displayed.12.Click Add User to Group .13.Select the user you created from the list, then click Add User .14.Return to the navigation menu.15.Under Governance and Administration , go to Identity , then click Policies .16.Select the compartment you previously created.17.Click Create Policy .18.Enter a name and optional description.19.Leave KEEP POLICY CURRENT as the Policy Versioning selection.20.Add the following statements to migrate to Oracle Integration Generation 2.The statements to add are based on the migration tool you use.Chapter 3 Step 2: Create a User and Group and Add Policies 3-3Migration Tool Statements If using Application Migration ServiceAdd these statements: allow service applicationmigration to inspect compartments in tenancy allow service applicationmigration to { TENANCY_INSPECT } in tenancy allow service applicationmigration to { IDENTITY_PROVIDER_INSPECT } in tenancy allow service applicationmigration to manage database-family in tenancy allow service applicationmigration to use vcns in tenancy allow service applicationmigration to use subnets in tenancy allow service applicationmigration to use vnics in tenancy allow service applicationmigration to { VNIC_ATTACHMENT_READ } in tenancy allow service applicationmigration to { INSTANCE_INSPECT } in tenancy allow service applicationmigration to manage analytics-instances in tenancy allow service applicationmigration to manage integration-instances in tenancy allow service PSM to inspect vcns in tenancy allow service PSM to use subnets in tenancy allow service PSM to use vnics in tenancy allow service PSM to manage security-lists in tenancy allow service PSM to inspect database-family in tenancy If using a different migration tool, for example: Import tool to export and import Processes design-time metadata curl or postman command to export and import Integrations and Processes design-time metadataAdd the following statements.allow group Upgrade_Group to manage buckets in compartment Upgrade_Compartment allow group Upgrade_Group to manage objects in compartment Upgrade_Compartment where any {request.permission=OBJECT_CREATE,request.permissi on=OBJECT_DELETE,request.permission=OBJECT_INSPEC T} where: Upgrade_Group is the group you created.Upgrade_Compartment is the compartment you created.This action enables users in this group to export design-time metadata to Oracle Integration.Chapter 3 Step 2: Create a User and Group and Add Policies 3-421.Click Create .Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) If you are not using the Application Migration Service for migration, you must create a storage bucket (if one does not already exist) and construct the storage URL to specify in order to export design-time metadata into an Oracle Integration instance. |
12.Click Add User to Group .13.Select the user you created from the list, then click Add User .14.Return to the navigation menu.15.Under Governance and Administration , go to Identity , then click Policies .16.Select the compartment you previously created.17.Click Create Policy .18.Enter a name and optional description.19.Leave KEEP POLICY CURRENT as the Policy Versioning selection.20.Add the following statements to migrate to Oracle Integration Generation 2.The statements to add are based on the migration tool you use.Chapter 3 Step 2: Create a User and Group and Add Policies 3-3Migration Tool Statements If using Application Migration ServiceAdd these statements: allow service applicationmigration to inspect compartments in tenancy allow service applicationmigration to { TENANCY_INSPECT } in tenancy allow service applicationmigration to { IDENTITY_PROVIDER_INSPECT } in tenancy allow service applicationmigration to manage database-family in tenancy allow service applicationmigration to use vcns in tenancy allow service applicationmigration to use subnets in tenancy allow service applicationmigration to use vnics in tenancy allow service applicationmigration to { VNIC_ATTACHMENT_READ } in tenancy allow service applicationmigration to { INSTANCE_INSPECT } in tenancy allow service applicationmigration to manage analytics-instances in tenancy allow service applicationmigration to manage integration-instances in tenancy allow service PSM to inspect vcns in tenancy allow service PSM to use subnets in tenancy allow service PSM to use vnics in tenancy allow service PSM to manage security-lists in tenancy allow service PSM to inspect database-family in tenancy If using a different migration tool, for example: Import tool to export and import Processes design-time metadata curl or postman command to export and import Integrations and Processes design-time metadataAdd the following statements.allow group Upgrade_Group to manage buckets in compartment Upgrade_Compartment allow group Upgrade_Group to manage objects in compartment Upgrade_Compartment where any {request.permission=OBJECT_CREATE,request.permissi on=OBJECT_DELETE,request.permission=OBJECT_INSPEC T} where: Upgrade_Group is the group you created.Upgrade_Compartment is the compartment you created.This action enables users in this group to export design-time metadata to Oracle Integration.Chapter 3 Step 2: Create a User and Group and Add Policies 3-421.Click Create .Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) If you are not using the Application Migration Service for migration, you must create a storage bucket (if one does not already exist) and construct the storage URL to specify in order to export design-time metadata into an Oracle Integration instance.You must specify this URL later during the configuration process to migrate your instance. |
13.Select the user you created from the list, then click Add User .14.Return to the navigation menu.15.Under Governance and Administration , go to Identity , then click Policies .16.Select the compartment you previously created.17.Click Create Policy .18.Enter a name and optional description.19.Leave KEEP POLICY CURRENT as the Policy Versioning selection.20.Add the following statements to migrate to Oracle Integration Generation 2.The statements to add are based on the migration tool you use.Chapter 3 Step 2: Create a User and Group and Add Policies 3-3Migration Tool Statements If using Application Migration ServiceAdd these statements: allow service applicationmigration to inspect compartments in tenancy allow service applicationmigration to { TENANCY_INSPECT } in tenancy allow service applicationmigration to { IDENTITY_PROVIDER_INSPECT } in tenancy allow service applicationmigration to manage database-family in tenancy allow service applicationmigration to use vcns in tenancy allow service applicationmigration to use subnets in tenancy allow service applicationmigration to use vnics in tenancy allow service applicationmigration to { VNIC_ATTACHMENT_READ } in tenancy allow service applicationmigration to { INSTANCE_INSPECT } in tenancy allow service applicationmigration to manage analytics-instances in tenancy allow service applicationmigration to manage integration-instances in tenancy allow service PSM to inspect vcns in tenancy allow service PSM to use subnets in tenancy allow service PSM to use vnics in tenancy allow service PSM to manage security-lists in tenancy allow service PSM to inspect database-family in tenancy If using a different migration tool, for example: Import tool to export and import Processes design-time metadata curl or postman command to export and import Integrations and Processes design-time metadataAdd the following statements.allow group Upgrade_Group to manage buckets in compartment Upgrade_Compartment allow group Upgrade_Group to manage objects in compartment Upgrade_Compartment where any {request.permission=OBJECT_CREATE,request.permissi on=OBJECT_DELETE,request.permission=OBJECT_INSPEC T} where: Upgrade_Group is the group you created.Upgrade_Compartment is the compartment you created.This action enables users in this group to export design-time metadata to Oracle Integration.Chapter 3 Step 2: Create a User and Group and Add Policies 3-421.Click Create .Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) If you are not using the Application Migration Service for migration, you must create a storage bucket (if one does not already exist) and construct the storage URL to specify in order to export design-time metadata into an Oracle Integration instance.You must specify this URL later during the configuration process to migrate your instance.If you use the Application Migration Service, these tasks are automatically performed for you. |
14.Return to the navigation menu.15.Under Governance and Administration , go to Identity , then click Policies .16.Select the compartment you previously created.17.Click Create Policy .18.Enter a name and optional description.19.Leave KEEP POLICY CURRENT as the Policy Versioning selection.20.Add the following statements to migrate to Oracle Integration Generation 2.The statements to add are based on the migration tool you use.Chapter 3 Step 2: Create a User and Group and Add Policies 3-3Migration Tool Statements If using Application Migration ServiceAdd these statements: allow service applicationmigration to inspect compartments in tenancy allow service applicationmigration to { TENANCY_INSPECT } in tenancy allow service applicationmigration to { IDENTITY_PROVIDER_INSPECT } in tenancy allow service applicationmigration to manage database-family in tenancy allow service applicationmigration to use vcns in tenancy allow service applicationmigration to use subnets in tenancy allow service applicationmigration to use vnics in tenancy allow service applicationmigration to { VNIC_ATTACHMENT_READ } in tenancy allow service applicationmigration to { INSTANCE_INSPECT } in tenancy allow service applicationmigration to manage analytics-instances in tenancy allow service applicationmigration to manage integration-instances in tenancy allow service PSM to inspect vcns in tenancy allow service PSM to use subnets in tenancy allow service PSM to use vnics in tenancy allow service PSM to manage security-lists in tenancy allow service PSM to inspect database-family in tenancy If using a different migration tool, for example: Import tool to export and import Processes design-time metadata curl or postman command to export and import Integrations and Processes design-time metadataAdd the following statements.allow group Upgrade_Group to manage buckets in compartment Upgrade_Compartment allow group Upgrade_Group to manage objects in compartment Upgrade_Compartment where any {request.permission=OBJECT_CREATE,request.permissi on=OBJECT_DELETE,request.permission=OBJECT_INSPEC T} where: Upgrade_Group is the group you created.Upgrade_Compartment is the compartment you created.This action enables users in this group to export design-time metadata to Oracle Integration.Chapter 3 Step 2: Create a User and Group and Add Policies 3-421.Click Create .Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) If you are not using the Application Migration Service for migration, you must create a storage bucket (if one does not already exist) and construct the storage URL to specify in order to export design-time metadata into an Oracle Integration instance.You must specify this URL later during the configuration process to migrate your instance.If you use the Application Migration Service, these tasks are automatically performed for you.Note: If using the Application Migration Service, skip this section. |
15.Under Governance and Administration , go to Identity , then click Policies .16.Select the compartment you previously created.17.Click Create Policy .18.Enter a name and optional description.19.Leave KEEP POLICY CURRENT as the Policy Versioning selection.20.Add the following statements to migrate to Oracle Integration Generation 2.The statements to add are based on the migration tool you use.Chapter 3 Step 2: Create a User and Group and Add Policies 3-3Migration Tool Statements If using Application Migration ServiceAdd these statements: allow service applicationmigration to inspect compartments in tenancy allow service applicationmigration to { TENANCY_INSPECT } in tenancy allow service applicationmigration to { IDENTITY_PROVIDER_INSPECT } in tenancy allow service applicationmigration to manage database-family in tenancy allow service applicationmigration to use vcns in tenancy allow service applicationmigration to use subnets in tenancy allow service applicationmigration to use vnics in tenancy allow service applicationmigration to { VNIC_ATTACHMENT_READ } in tenancy allow service applicationmigration to { INSTANCE_INSPECT } in tenancy allow service applicationmigration to manage analytics-instances in tenancy allow service applicationmigration to manage integration-instances in tenancy allow service PSM to inspect vcns in tenancy allow service PSM to use subnets in tenancy allow service PSM to use vnics in tenancy allow service PSM to manage security-lists in tenancy allow service PSM to inspect database-family in tenancy If using a different migration tool, for example: Import tool to export and import Processes design-time metadata curl or postman command to export and import Integrations and Processes design-time metadataAdd the following statements.allow group Upgrade_Group to manage buckets in compartment Upgrade_Compartment allow group Upgrade_Group to manage objects in compartment Upgrade_Compartment where any {request.permission=OBJECT_CREATE,request.permissi on=OBJECT_DELETE,request.permission=OBJECT_INSPEC T} where: Upgrade_Group is the group you created.Upgrade_Compartment is the compartment you created.This action enables users in this group to export design-time metadata to Oracle Integration.Chapter 3 Step 2: Create a User and Group and Add Policies 3-421.Click Create .Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) If you are not using the Application Migration Service for migration, you must create a storage bucket (if one does not already exist) and construct the storage URL to specify in order to export design-time metadata into an Oracle Integration instance.You must specify this URL later during the configuration process to migrate your instance.If you use the Application Migration Service, these tasks are automatically performed for you.Note: If using the Application Migration Service, skip this section.Do not create a Classic Storage bucket. |
16.Select the compartment you previously created.17.Click Create Policy .18.Enter a name and optional description.19.Leave KEEP POLICY CURRENT as the Policy Versioning selection.20.Add the following statements to migrate to Oracle Integration Generation 2.The statements to add are based on the migration tool you use.Chapter 3 Step 2: Create a User and Group and Add Policies 3-3Migration Tool Statements If using Application Migration ServiceAdd these statements: allow service applicationmigration to inspect compartments in tenancy allow service applicationmigration to { TENANCY_INSPECT } in tenancy allow service applicationmigration to { IDENTITY_PROVIDER_INSPECT } in tenancy allow service applicationmigration to manage database-family in tenancy allow service applicationmigration to use vcns in tenancy allow service applicationmigration to use subnets in tenancy allow service applicationmigration to use vnics in tenancy allow service applicationmigration to { VNIC_ATTACHMENT_READ } in tenancy allow service applicationmigration to { INSTANCE_INSPECT } in tenancy allow service applicationmigration to manage analytics-instances in tenancy allow service applicationmigration to manage integration-instances in tenancy allow service PSM to inspect vcns in tenancy allow service PSM to use subnets in tenancy allow service PSM to use vnics in tenancy allow service PSM to manage security-lists in tenancy allow service PSM to inspect database-family in tenancy If using a different migration tool, for example: Import tool to export and import Processes design-time metadata curl or postman command to export and import Integrations and Processes design-time metadataAdd the following statements.allow group Upgrade_Group to manage buckets in compartment Upgrade_Compartment allow group Upgrade_Group to manage objects in compartment Upgrade_Compartment where any {request.permission=OBJECT_CREATE,request.permissi on=OBJECT_DELETE,request.permission=OBJECT_INSPEC T} where: Upgrade_Group is the group you created.Upgrade_Compartment is the compartment you created.This action enables users in this group to export design-time metadata to Oracle Integration.Chapter 3 Step 2: Create a User and Group and Add Policies 3-421.Click Create .Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) If you are not using the Application Migration Service for migration, you must create a storage bucket (if one does not already exist) and construct the storage URL to specify in order to export design-time metadata into an Oracle Integration instance.You must specify this URL later during the configuration process to migrate your instance.If you use the Application Migration Service, these tasks are automatically performed for you.Note: If using the Application Migration Service, skip this section.Do not create a Classic Storage bucket.Classic Storage is not supported. |
17.Click Create Policy .18.Enter a name and optional description.19.Leave KEEP POLICY CURRENT as the Policy Versioning selection.20.Add the following statements to migrate to Oracle Integration Generation 2.The statements to add are based on the migration tool you use.Chapter 3 Step 2: Create a User and Group and Add Policies 3-3Migration Tool Statements If using Application Migration ServiceAdd these statements: allow service applicationmigration to inspect compartments in tenancy allow service applicationmigration to { TENANCY_INSPECT } in tenancy allow service applicationmigration to { IDENTITY_PROVIDER_INSPECT } in tenancy allow service applicationmigration to manage database-family in tenancy allow service applicationmigration to use vcns in tenancy allow service applicationmigration to use subnets in tenancy allow service applicationmigration to use vnics in tenancy allow service applicationmigration to { VNIC_ATTACHMENT_READ } in tenancy allow service applicationmigration to { INSTANCE_INSPECT } in tenancy allow service applicationmigration to manage analytics-instances in tenancy allow service applicationmigration to manage integration-instances in tenancy allow service PSM to inspect vcns in tenancy allow service PSM to use subnets in tenancy allow service PSM to use vnics in tenancy allow service PSM to manage security-lists in tenancy allow service PSM to inspect database-family in tenancy If using a different migration tool, for example: Import tool to export and import Processes design-time metadata curl or postman command to export and import Integrations and Processes design-time metadataAdd the following statements.allow group Upgrade_Group to manage buckets in compartment Upgrade_Compartment allow group Upgrade_Group to manage objects in compartment Upgrade_Compartment where any {request.permission=OBJECT_CREATE,request.permissi on=OBJECT_DELETE,request.permission=OBJECT_INSPEC T} where: Upgrade_Group is the group you created.Upgrade_Compartment is the compartment you created.This action enables users in this group to export design-time metadata to Oracle Integration.Chapter 3 Step 2: Create a User and Group and Add Policies 3-421.Click Create .Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) If you are not using the Application Migration Service for migration, you must create a storage bucket (if one does not already exist) and construct the storage URL to specify in order to export design-time metadata into an Oracle Integration instance.You must specify this URL later during the configuration process to migrate your instance.If you use the Application Migration Service, these tasks are automatically performed for you.Note: If using the Application Migration Service, skip this section.Do not create a Classic Storage bucket.Classic Storage is not supported.1.Log in to the My Services Console with the user that the administrator added to the group for exporting design-time metadata. |
18.Enter a name and optional description.19.Leave KEEP POLICY CURRENT as the Policy Versioning selection.20.Add the following statements to migrate to Oracle Integration Generation 2.The statements to add are based on the migration tool you use.Chapter 3 Step 2: Create a User and Group and Add Policies 3-3Migration Tool Statements If using Application Migration ServiceAdd these statements: allow service applicationmigration to inspect compartments in tenancy allow service applicationmigration to { TENANCY_INSPECT } in tenancy allow service applicationmigration to { IDENTITY_PROVIDER_INSPECT } in tenancy allow service applicationmigration to manage database-family in tenancy allow service applicationmigration to use vcns in tenancy allow service applicationmigration to use subnets in tenancy allow service applicationmigration to use vnics in tenancy allow service applicationmigration to { VNIC_ATTACHMENT_READ } in tenancy allow service applicationmigration to { INSTANCE_INSPECT } in tenancy allow service applicationmigration to manage analytics-instances in tenancy allow service applicationmigration to manage integration-instances in tenancy allow service PSM to inspect vcns in tenancy allow service PSM to use subnets in tenancy allow service PSM to use vnics in tenancy allow service PSM to manage security-lists in tenancy allow service PSM to inspect database-family in tenancy If using a different migration tool, for example: Import tool to export and import Processes design-time metadata curl or postman command to export and import Integrations and Processes design-time metadataAdd the following statements.allow group Upgrade_Group to manage buckets in compartment Upgrade_Compartment allow group Upgrade_Group to manage objects in compartment Upgrade_Compartment where any {request.permission=OBJECT_CREATE,request.permissi on=OBJECT_DELETE,request.permission=OBJECT_INSPEC T} where: Upgrade_Group is the group you created.Upgrade_Compartment is the compartment you created.This action enables users in this group to export design-time metadata to Oracle Integration.Chapter 3 Step 2: Create a User and Group and Add Policies 3-421.Click Create .Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) If you are not using the Application Migration Service for migration, you must create a storage bucket (if one does not already exist) and construct the storage URL to specify in order to export design-time metadata into an Oracle Integration instance.You must specify this URL later during the configuration process to migrate your instance.If you use the Application Migration Service, these tasks are automatically performed for you.Note: If using the Application Migration Service, skip this section.Do not create a Classic Storage bucket.Classic Storage is not supported.1.Log in to the My Services Console with the user that the administrator added to the group for exporting design-time metadata.You must have the admin role to access this page. |
19.Leave KEEP POLICY CURRENT as the Policy Versioning selection.20.Add the following statements to migrate to Oracle Integration Generation 2.The statements to add are based on the migration tool you use.Chapter 3 Step 2: Create a User and Group and Add Policies 3-3Migration Tool Statements If using Application Migration ServiceAdd these statements: allow service applicationmigration to inspect compartments in tenancy allow service applicationmigration to { TENANCY_INSPECT } in tenancy allow service applicationmigration to { IDENTITY_PROVIDER_INSPECT } in tenancy allow service applicationmigration to manage database-family in tenancy allow service applicationmigration to use vcns in tenancy allow service applicationmigration to use subnets in tenancy allow service applicationmigration to use vnics in tenancy allow service applicationmigration to { VNIC_ATTACHMENT_READ } in tenancy allow service applicationmigration to { INSTANCE_INSPECT } in tenancy allow service applicationmigration to manage analytics-instances in tenancy allow service applicationmigration to manage integration-instances in tenancy allow service PSM to inspect vcns in tenancy allow service PSM to use subnets in tenancy allow service PSM to use vnics in tenancy allow service PSM to manage security-lists in tenancy allow service PSM to inspect database-family in tenancy If using a different migration tool, for example: Import tool to export and import Processes design-time metadata curl or postman command to export and import Integrations and Processes design-time metadataAdd the following statements.allow group Upgrade_Group to manage buckets in compartment Upgrade_Compartment allow group Upgrade_Group to manage objects in compartment Upgrade_Compartment where any {request.permission=OBJECT_CREATE,request.permissi on=OBJECT_DELETE,request.permission=OBJECT_INSPEC T} where: Upgrade_Group is the group you created.Upgrade_Compartment is the compartment you created.This action enables users in this group to export design-time metadata to Oracle Integration.Chapter 3 Step 2: Create a User and Group and Add Policies 3-421.Click Create .Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) If you are not using the Application Migration Service for migration, you must create a storage bucket (if one does not already exist) and construct the storage URL to specify in order to export design-time metadata into an Oracle Integration instance.You must specify this URL later during the configuration process to migrate your instance.If you use the Application Migration Service, these tasks are automatically performed for you.Note: If using the Application Migration Service, skip this section.Do not create a Classic Storage bucket.Classic Storage is not supported.1.Log in to the My Services Console with the user that the administrator added to the group for exporting design-time metadata.You must have the admin role to access this page.2.If the Compute section is not displayed, select in the upper right corner of the My Services Dashboard. |
20.Add the following statements to migrate to Oracle Integration Generation 2.The statements to add are based on the migration tool you use.Chapter 3 Step 2: Create a User and Group and Add Policies 3-3Migration Tool Statements If using Application Migration ServiceAdd these statements: allow service applicationmigration to inspect compartments in tenancy allow service applicationmigration to { TENANCY_INSPECT } in tenancy allow service applicationmigration to { IDENTITY_PROVIDER_INSPECT } in tenancy allow service applicationmigration to manage database-family in tenancy allow service applicationmigration to use vcns in tenancy allow service applicationmigration to use subnets in tenancy allow service applicationmigration to use vnics in tenancy allow service applicationmigration to { VNIC_ATTACHMENT_READ } in tenancy allow service applicationmigration to { INSTANCE_INSPECT } in tenancy allow service applicationmigration to manage analytics-instances in tenancy allow service applicationmigration to manage integration-instances in tenancy allow service PSM to inspect vcns in tenancy allow service PSM to use subnets in tenancy allow service PSM to use vnics in tenancy allow service PSM to manage security-lists in tenancy allow service PSM to inspect database-family in tenancy If using a different migration tool, for example: Import tool to export and import Processes design-time metadata curl or postman command to export and import Integrations and Processes design-time metadataAdd the following statements.allow group Upgrade_Group to manage buckets in compartment Upgrade_Compartment allow group Upgrade_Group to manage objects in compartment Upgrade_Compartment where any {request.permission=OBJECT_CREATE,request.permissi on=OBJECT_DELETE,request.permission=OBJECT_INSPEC T} where: Upgrade_Group is the group you created.Upgrade_Compartment is the compartment you created.This action enables users in this group to export design-time metadata to Oracle Integration.Chapter 3 Step 2: Create a User and Group and Add Policies 3-421.Click Create .Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) If you are not using the Application Migration Service for migration, you must create a storage bucket (if one does not already exist) and construct the storage URL to specify in order to export design-time metadata into an Oracle Integration instance.You must specify this URL later during the configuration process to migrate your instance.If you use the Application Migration Service, these tasks are automatically performed for you.Note: If using the Application Migration Service, skip this section.Do not create a Classic Storage bucket.Classic Storage is not supported.1.Log in to the My Services Console with the user that the administrator added to the group for exporting design-time metadata.You must have the admin role to access this page.2.If the Compute section is not displayed, select in the upper right corner of the My Services Dashboard.a.Click Show in the Compute section. |
The statements to add are based on the migration tool you use.Chapter 3 Step 2: Create a User and Group and Add Policies 3-3Migration Tool Statements If using Application Migration ServiceAdd these statements: allow service applicationmigration to inspect compartments in tenancy allow service applicationmigration to { TENANCY_INSPECT } in tenancy allow service applicationmigration to { IDENTITY_PROVIDER_INSPECT } in tenancy allow service applicationmigration to manage database-family in tenancy allow service applicationmigration to use vcns in tenancy allow service applicationmigration to use subnets in tenancy allow service applicationmigration to use vnics in tenancy allow service applicationmigration to { VNIC_ATTACHMENT_READ } in tenancy allow service applicationmigration to { INSTANCE_INSPECT } in tenancy allow service applicationmigration to manage analytics-instances in tenancy allow service applicationmigration to manage integration-instances in tenancy allow service PSM to inspect vcns in tenancy allow service PSM to use subnets in tenancy allow service PSM to use vnics in tenancy allow service PSM to manage security-lists in tenancy allow service PSM to inspect database-family in tenancy If using a different migration tool, for example: Import tool to export and import Processes design-time metadata curl or postman command to export and import Integrations and Processes design-time metadataAdd the following statements.allow group Upgrade_Group to manage buckets in compartment Upgrade_Compartment allow group Upgrade_Group to manage objects in compartment Upgrade_Compartment where any {request.permission=OBJECT_CREATE,request.permissi on=OBJECT_DELETE,request.permission=OBJECT_INSPEC T} where: Upgrade_Group is the group you created.Upgrade_Compartment is the compartment you created.This action enables users in this group to export design-time metadata to Oracle Integration.Chapter 3 Step 2: Create a User and Group and Add Policies 3-421.Click Create .Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) If you are not using the Application Migration Service for migration, you must create a storage bucket (if one does not already exist) and construct the storage URL to specify in order to export design-time metadata into an Oracle Integration instance.You must specify this URL later during the configuration process to migrate your instance.If you use the Application Migration Service, these tasks are automatically performed for you.Note: If using the Application Migration Service, skip this section.Do not create a Classic Storage bucket.Classic Storage is not supported.1.Log in to the My Services Console with the user that the administrator added to the group for exporting design-time metadata.You must have the admin role to access this page.2.If the Compute section is not displayed, select in the upper right corner of the My Services Dashboard.a.Click Show in the Compute section.This enables this service to appear on the My Services page. |
allow group Upgrade_Group to manage buckets in compartment Upgrade_Compartment allow group Upgrade_Group to manage objects in compartment Upgrade_Compartment where any {request.permission=OBJECT_CREATE,request.permissi on=OBJECT_DELETE,request.permission=OBJECT_INSPEC T} where: Upgrade_Group is the group you created.Upgrade_Compartment is the compartment you created.This action enables users in this group to export design-time metadata to Oracle Integration.Chapter 3 Step 2: Create a User and Group and Add Policies 3-421.Click Create .Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) If you are not using the Application Migration Service for migration, you must create a storage bucket (if one does not already exist) and construct the storage URL to specify in order to export design-time metadata into an Oracle Integration instance.You must specify this URL later during the configuration process to migrate your instance.If you use the Application Migration Service, these tasks are automatically performed for you.Note: If using the Application Migration Service, skip this section.Do not create a Classic Storage bucket.Classic Storage is not supported.1.Log in to the My Services Console with the user that the administrator added to the group for exporting design-time metadata.You must have the admin role to access this page.2.If the Compute section is not displayed, select in the upper right corner of the My Services Dashboard.a.Click Show in the Compute section.This enables this service to appear on the My Services page.3.Click Compute to access the Oracle Cloud Infrastructure page. |
Upgrade_Compartment is the compartment you created.This action enables users in this group to export design-time metadata to Oracle Integration.Chapter 3 Step 2: Create a User and Group and Add Policies 3-421.Click Create .Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) If you are not using the Application Migration Service for migration, you must create a storage bucket (if one does not already exist) and construct the storage URL to specify in order to export design-time metadata into an Oracle Integration instance.You must specify this URL later during the configuration process to migrate your instance.If you use the Application Migration Service, these tasks are automatically performed for you.Note: If using the Application Migration Service, skip this section.Do not create a Classic Storage bucket.Classic Storage is not supported.1.Log in to the My Services Console with the user that the administrator added to the group for exporting design-time metadata.You must have the admin role to access this page.2.If the Compute section is not displayed, select in the upper right corner of the My Services Dashboard.a.Click Show in the Compute section.This enables this service to appear on the My Services page.3.Click Compute to access the Oracle Cloud Infrastructure page.4.In the upper right corner, click . |
This action enables users in this group to export design-time metadata to Oracle Integration.Chapter 3 Step 2: Create a User and Group and Add Policies 3-421.Click Create .Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) If you are not using the Application Migration Service for migration, you must create a storage bucket (if one does not already exist) and construct the storage URL to specify in order to export design-time metadata into an Oracle Integration instance.You must specify this URL later during the configuration process to migrate your instance.If you use the Application Migration Service, these tasks are automatically performed for you.Note: If using the Application Migration Service, skip this section.Do not create a Classic Storage bucket.Classic Storage is not supported.1.Log in to the My Services Console with the user that the administrator added to the group for exporting design-time metadata.You must have the admin role to access this page.2.If the Compute section is not displayed, select in the upper right corner of the My Services Dashboard.a.Click Show in the Compute section.This enables this service to appear on the My Services page.3.Click Compute to access the Oracle Cloud Infrastructure page.4.In the upper right corner, click .5.In the upper left corner of the Oracle Cloud Infrastructure page, click . |
Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) If you are not using the Application Migration Service for migration, you must create a storage bucket (if one does not already exist) and construct the storage URL to specify in order to export design-time metadata into an Oracle Integration instance.You must specify this URL later during the configuration process to migrate your instance.If you use the Application Migration Service, these tasks are automatically performed for you.Note: If using the Application Migration Service, skip this section.Do not create a Classic Storage bucket.Classic Storage is not supported.1.Log in to the My Services Console with the user that the administrator added to the group for exporting design-time metadata.You must have the admin role to access this page.2.If the Compute section is not displayed, select in the upper right corner of the My Services Dashboard.a.Click Show in the Compute section.This enables this service to appear on the My Services page.3.Click Compute to access the Oracle Cloud Infrastructure page.4.In the upper right corner, click .5.In the upper left corner of the Oracle Cloud Infrastructure page, click .6.Select Object Storage > Object Storage . |
You must specify this URL later during the configuration process to migrate your instance.If you use the Application Migration Service, these tasks are automatically performed for you.Note: If using the Application Migration Service, skip this section.Do not create a Classic Storage bucket.Classic Storage is not supported.1.Log in to the My Services Console with the user that the administrator added to the group for exporting design-time metadata.You must have the admin role to access this page.2.If the Compute section is not displayed, select in the upper right corner of the My Services Dashboard.a.Click Show in the Compute section.This enables this service to appear on the My Services page.3.Click Compute to access the Oracle Cloud Infrastructure page.4.In the upper right corner, click .5.In the upper left corner of the Oracle Cloud Infrastructure page, click .6.Select Object Storage > Object Storage .7.Select the compartment in which to create the storage bucket. |
If you use the Application Migration Service, these tasks are automatically performed for you.Note: If using the Application Migration Service, skip this section.Do not create a Classic Storage bucket.Classic Storage is not supported.1.Log in to the My Services Console with the user that the administrator added to the group for exporting design-time metadata.You must have the admin role to access this page.2.If the Compute section is not displayed, select in the upper right corner of the My Services Dashboard.a.Click Show in the Compute section.This enables this service to appear on the My Services page.3.Click Compute to access the Oracle Cloud Infrastructure page.4.In the upper right corner, click .5.In the upper left corner of the Oracle Cloud Infrastructure page, click .6.Select Object Storage > Object Storage .7.Select the compartment in which to create the storage bucket.The compartment to use for exporting design-time metadata was created in Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment . |
Note: If using the Application Migration Service, skip this section.Do not create a Classic Storage bucket.Classic Storage is not supported.1.Log in to the My Services Console with the user that the administrator added to the group for exporting design-time metadata.You must have the admin role to access this page.2.If the Compute section is not displayed, select in the upper right corner of the My Services Dashboard.a.Click Show in the Compute section.This enables this service to appear on the My Services page.3.Click Compute to access the Oracle Cloud Infrastructure page.4.In the upper right corner, click .5.In the upper left corner of the Oracle Cloud Infrastructure page, click .6.Select Object Storage > Object Storage .7.Select the compartment in which to create the storage bucket.The compartment to use for exporting design-time metadata was created in Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment .You can also click Learn more about Compartments to find the appropriate compartment for your environment. |
Do not create a Classic Storage bucket.Classic Storage is not supported.1.Log in to the My Services Console with the user that the administrator added to the group for exporting design-time metadata.You must have the admin role to access this page.2.If the Compute section is not displayed, select in the upper right corner of the My Services Dashboard.a.Click Show in the Compute section.This enables this service to appear on the My Services page.3.Click Compute to access the Oracle Cloud Infrastructure page.4.In the upper right corner, click .5.In the upper left corner of the Oracle Cloud Infrastructure page, click .6.Select Object Storage > Object Storage .7.Select the compartment in which to create the storage bucket.The compartment to use for exporting design-time metadata was created in Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment .You can also click Learn more about Compartments to find the appropriate compartment for your environment.8.After determining the compartment to use, click Create Bucket . |
Classic Storage is not supported.1.Log in to the My Services Console with the user that the administrator added to the group for exporting design-time metadata.You must have the admin role to access this page.2.If the Compute section is not displayed, select in the upper right corner of the My Services Dashboard.a.Click Show in the Compute section.This enables this service to appear on the My Services page.3.Click Compute to access the Oracle Cloud Infrastructure page.4.In the upper right corner, click .5.In the upper left corner of the Oracle Cloud Infrastructure page, click .6.Select Object Storage > Object Storage .7.Select the compartment in which to create the storage bucket.The compartment to use for exporting design-time metadata was created in Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment .You can also click Learn more about Compartments to find the appropriate compartment for your environment.8.After determining the compartment to use, click Create Bucket .Chapter 3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-5 9.In the Bucket Name field, enter a name. |
1.Log in to the My Services Console with the user that the administrator added to the group for exporting design-time metadata.You must have the admin role to access this page.2.If the Compute section is not displayed, select in the upper right corner of the My Services Dashboard.a.Click Show in the Compute section.This enables this service to appear on the My Services page.3.Click Compute to access the Oracle Cloud Infrastructure page.4.In the upper right corner, click .5.In the upper left corner of the Oracle Cloud Infrastructure page, click .6.Select Object Storage > Object Storage .7.Select the compartment in which to create the storage bucket.The compartment to use for exporting design-time metadata was created in Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment .You can also click Learn more about Compartments to find the appropriate compartment for your environment.8.After determining the compartment to use, click Create Bucket .Chapter 3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-5 9.In the Bucket Name field, enter a name.10.In the Storage Tier section, select Standard . |
You must have the admin role to access this page.2.If the Compute section is not displayed, select in the upper right corner of the My Services Dashboard.a.Click Show in the Compute section.This enables this service to appear on the My Services page.3.Click Compute to access the Oracle Cloud Infrastructure page.4.In the upper right corner, click .5.In the upper left corner of the Oracle Cloud Infrastructure page, click .6.Select Object Storage > Object Storage .7.Select the compartment in which to create the storage bucket.The compartment to use for exporting design-time metadata was created in Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment .You can also click Learn more about Compartments to find the appropriate compartment for your environment.8.After determining the compartment to use, click Create Bucket .Chapter 3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-5 9.In the Bucket Name field, enter a name.10.In the Storage Tier section, select Standard .11.Click Create Bucket . |
2.If the Compute section is not displayed, select in the upper right corner of the My Services Dashboard.a.Click Show in the Compute section.This enables this service to appear on the My Services page.3.Click Compute to access the Oracle Cloud Infrastructure page.4.In the upper right corner, click .5.In the upper left corner of the Oracle Cloud Infrastructure page, click .6.Select Object Storage > Object Storage .7.Select the compartment in which to create the storage bucket.The compartment to use for exporting design-time metadata was created in Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment .You can also click Learn more about Compartments to find the appropriate compartment for your environment.8.After determining the compartment to use, click Create Bucket .Chapter 3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-5 9.In the Bucket Name field, enter a name.10.In the Storage Tier section, select Standard .11.Click Create Bucket .The new bucket is displayed in the list. |
a.Click Show in the Compute section.This enables this service to appear on the My Services page.3.Click Compute to access the Oracle Cloud Infrastructure page.4.In the upper right corner, click .5.In the upper left corner of the Oracle Cloud Infrastructure page, click .6.Select Object Storage > Object Storage .7.Select the compartment in which to create the storage bucket.The compartment to use for exporting design-time metadata was created in Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment .You can also click Learn more about Compartments to find the appropriate compartment for your environment.8.After determining the compartment to use, click Create Bucket .Chapter 3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-5 9.In the Bucket Name field, enter a name.10.In the Storage Tier section, select Standard .11.Click Create Bucket .The new bucket is displayed in the list.12.If you want to view bucket details, click the name (for this example, cloneRepo ). |
This enables this service to appear on the My Services page.3.Click Compute to access the Oracle Cloud Infrastructure page.4.In the upper right corner, click .5.In the upper left corner of the Oracle Cloud Infrastructure page, click .6.Select Object Storage > Object Storage .7.Select the compartment in which to create the storage bucket.The compartment to use for exporting design-time metadata was created in Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment .You can also click Learn more about Compartments to find the appropriate compartment for your environment.8.After determining the compartment to use, click Create Bucket .Chapter 3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-5 9.In the Bucket Name field, enter a name.10.In the Storage Tier section, select Standard .11.Click Create Bucket .The new bucket is displayed in the list.12.If you want to view bucket details, click the name (for this example, cloneRepo ).Note: Ensure that you click the Public button and deselect the Allow Users To List Objects From This Bucket check box. |
3.Click Compute to access the Oracle Cloud Infrastructure page.4.In the upper right corner, click .5.In the upper left corner of the Oracle Cloud Infrastructure page, click .6.Select Object Storage > Object Storage .7.Select the compartment in which to create the storage bucket.The compartment to use for exporting design-time metadata was created in Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment .You can also click Learn more about Compartments to find the appropriate compartment for your environment.8.After determining the compartment to use, click Create Bucket .Chapter 3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-5 9.In the Bucket Name field, enter a name.10.In the Storage Tier section, select Standard .11.Click Create Bucket .The new bucket is displayed in the list.12.If you want to view bucket details, click the name (for this example, cloneRepo ).Note: Ensure that you click the Public button and deselect the Allow Users To List Objects From This Bucket check box.This action ensures that the storage bucket you create is publicly visible. |
4.In the upper right corner, click .5.In the upper left corner of the Oracle Cloud Infrastructure page, click .6.Select Object Storage > Object Storage .7.Select the compartment in which to create the storage bucket.The compartment to use for exporting design-time metadata was created in Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment .You can also click Learn more about Compartments to find the appropriate compartment for your environment.8.After determining the compartment to use, click Create Bucket .Chapter 3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-5 9.In the Bucket Name field, enter a name.10.In the Storage Tier section, select Standard .11.Click Create Bucket .The new bucket is displayed in the list.12.If you want to view bucket details, click the name (for this example, cloneRepo ).Note: Ensure that you click the Public button and deselect the Allow Users To List Objects From This Bucket check box.This action ensures that the storage bucket you create is publicly visible.Otherwise, the export utility cannot see the storage. |
5.In the upper left corner of the Oracle Cloud Infrastructure page, click .6.Select Object Storage > Object Storage .7.Select the compartment in which to create the storage bucket.The compartment to use for exporting design-time metadata was created in Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment .You can also click Learn more about Compartments to find the appropriate compartment for your environment.8.After determining the compartment to use, click Create Bucket .Chapter 3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-5 9.In the Bucket Name field, enter a name.10.In the Storage Tier section, select Standard .11.Click Create Bucket .The new bucket is displayed in the list.12.If you want to view bucket details, click the name (for this example, cloneRepo ).Note: Ensure that you click the Public button and deselect the Allow Users To List Objects From This Bucket check box.This action ensures that the storage bucket you create is publicly visible.Otherwise, the export utility cannot see the storage.Chapter 3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-613.In the upper left corner of the page, click . |
6.Select Object Storage > Object Storage .7.Select the compartment in which to create the storage bucket.The compartment to use for exporting design-time metadata was created in Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment .You can also click Learn more about Compartments to find the appropriate compartment for your environment.8.After determining the compartment to use, click Create Bucket .Chapter 3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-5 9.In the Bucket Name field, enter a name.10.In the Storage Tier section, select Standard .11.Click Create Bucket .The new bucket is displayed in the list.12.If you want to view bucket details, click the name (for this example, cloneRepo ).Note: Ensure that you click the Public button and deselect the Allow Users To List Objects From This Bucket check box.This action ensures that the storage bucket you create is publicly visible.Otherwise, the export utility cannot see the storage.Chapter 3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-613.In the upper left corner of the page, click .14.Select Identity > Users . |
7.Select the compartment in which to create the storage bucket.The compartment to use for exporting design-time metadata was created in Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment .You can also click Learn more about Compartments to find the appropriate compartment for your environment.8.After determining the compartment to use, click Create Bucket .Chapter 3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-5 9.In the Bucket Name field, enter a name.10.In the Storage Tier section, select Standard .11.Click Create Bucket .The new bucket is displayed in the list.12.If you want to view bucket details, click the name (for this example, cloneRepo ).Note: Ensure that you click the Public button and deselect the Allow Users To List Objects From This Bucket check box.This action ensures that the storage bucket you create is publicly visible.Otherwise, the export utility cannot see the storage.Chapter 3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-613.In the upper left corner of the page, click .14.Select Identity > Users .This opens the Oracle Identity Service Console to generate a password. |
The compartment to use for exporting design-time metadata was created in Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment .You can also click Learn more about Compartments to find the appropriate compartment for your environment.8.After determining the compartment to use, click Create Bucket .Chapter 3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-5 9.In the Bucket Name field, enter a name.10.In the Storage Tier section, select Standard .11.Click Create Bucket .The new bucket is displayed in the list.12.If you want to view bucket details, click the name (for this example, cloneRepo ).Note: Ensure that you click the Public button and deselect the Allow Users To List Objects From This Bucket check box.This action ensures that the storage bucket you create is publicly visible.Otherwise, the export utility cannot see the storage.Chapter 3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-613.In the upper left corner of the page, click .14.Select Identity > Users .This opens the Oracle Identity Service Console to generate a password.15.Select the appropriate user. |
You can also click Learn more about Compartments to find the appropriate compartment for your environment.8.After determining the compartment to use, click Create Bucket .Chapter 3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-5 9.In the Bucket Name field, enter a name.10.In the Storage Tier section, select Standard .11.Click Create Bucket .The new bucket is displayed in the list.12.If you want to view bucket details, click the name (for this example, cloneRepo ).Note: Ensure that you click the Public button and deselect the Allow Users To List Objects From This Bucket check box.This action ensures that the storage bucket you create is publicly visible.Otherwise, the export utility cannot see the storage.Chapter 3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-613.In the upper left corner of the page, click .14.Select Identity > Users .This opens the Oracle Identity Service Console to generate a password.15.Select the appropriate user.16.From the Resources list on the left side of the page, select Auth Tokens . |
8.After determining the compartment to use, click Create Bucket .Chapter 3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-5 9.In the Bucket Name field, enter a name.10.In the Storage Tier section, select Standard .11.Click Create Bucket .The new bucket is displayed in the list.12.If you want to view bucket details, click the name (for this example, cloneRepo ).Note: Ensure that you click the Public button and deselect the Allow Users To List Objects From This Bucket check box.This action ensures that the storage bucket you create is publicly visible.Otherwise, the export utility cannot see the storage.Chapter 3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-613.In the upper left corner of the page, click .14.Select Identity > Users .This opens the Oracle Identity Service Console to generate a password.15.Select the appropriate user.16.From the Resources list on the left side of the page, select Auth Tokens .17.Click . |
Chapter 3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-5 9.In the Bucket Name field, enter a name.10.In the Storage Tier section, select Standard .11.Click Create Bucket .The new bucket is displayed in the list.12.If you want to view bucket details, click the name (for this example, cloneRepo ).Note: Ensure that you click the Public button and deselect the Allow Users To List Objects From This Bucket check box.This action ensures that the storage bucket you create is publicly visible.Otherwise, the export utility cannot see the storage.Chapter 3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-613.In the upper left corner of the page, click .14.Select Identity > Users .This opens the Oracle Identity Service Console to generate a password.15.Select the appropriate user.16.From the Resources list on the left side of the page, select Auth Tokens .17.Click .18.Provide a token description and click . |
10.In the Storage Tier section, select Standard .11.Click Create Bucket .The new bucket is displayed in the list.12.If you want to view bucket details, click the name (for this example, cloneRepo ).Note: Ensure that you click the Public button and deselect the Allow Users To List Objects From This Bucket check box.This action ensures that the storage bucket you create is publicly visible.Otherwise, the export utility cannot see the storage.Chapter 3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-613.In the upper left corner of the page, click .14.Select Identity > Users .This opens the Oracle Identity Service Console to generate a password.15.Select the appropriate user.16.From the Resources list on the left side of the page, select Auth Tokens .17.Click .18.Provide a token description and click .This token is used as part of your JSON payload when upgrading. |
11.Click Create Bucket .The new bucket is displayed in the list.12.If you want to view bucket details, click the name (for this example, cloneRepo ).Note: Ensure that you click the Public button and deselect the Allow Users To List Objects From This Bucket check box.This action ensures that the storage bucket you create is publicly visible.Otherwise, the export utility cannot see the storage.Chapter 3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-613.In the upper left corner of the page, click .14.Select Identity > Users .This opens the Oracle Identity Service Console to generate a password.15.Select the appropriate user.16.From the Resources list on the left side of the page, select Auth Tokens .17.Click .18.Provide a token description and click .This token is used as part of your JSON payload when upgrading.19.Copy and save the generated token. |
The new bucket is displayed in the list.12.If you want to view bucket details, click the name (for this example, cloneRepo ).Note: Ensure that you click the Public button and deselect the Allow Users To List Objects From This Bucket check box.This action ensures that the storage bucket you create is publicly visible.Otherwise, the export utility cannot see the storage.Chapter 3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-613.In the upper left corner of the page, click .14.Select Identity > Users .This opens the Oracle Identity Service Console to generate a password.15.Select the appropriate user.16.From the Resources list on the left side of the page, select Auth Tokens .17.Click .18.Provide a token description and click .This token is used as part of your JSON payload when upgrading.19.Copy and save the generated token.a. |
12.If you want to view bucket details, click the name (for this example, cloneRepo ).Note: Ensure that you click the Public button and deselect the Allow Users To List Objects From This Bucket check box.This action ensures that the storage bucket you create is publicly visible.Otherwise, the export utility cannot see the storage.Chapter 3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-613.In the upper left corner of the page, click .14.Select Identity > Users .This opens the Oracle Identity Service Console to generate a password.15.Select the appropriate user.16.From the Resources list on the left side of the page, select Auth Tokens .17.Click .18.Provide a token description and click .This token is used as part of your JSON payload when upgrading.19.Copy and save the generated token.a.The storage payload format is as follows with object storage bucket details: {"storageInfo": { "storageUrl":"https:// swiftobjectstorage. |
Note: Ensure that you click the Public button and deselect the Allow Users To List Objects From This Bucket check box.This action ensures that the storage bucket you create is publicly visible.Otherwise, the export utility cannot see the storage.Chapter 3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-613.In the upper left corner of the page, click .14.Select Identity > Users .This opens the Oracle Identity Service Console to generate a password.15.Select the appropriate user.16.From the Resources list on the left side of the page, select Auth Tokens .17.Click .18.Provide a token description and click .This token is used as part of your JSON payload when upgrading.19.Copy and save the generated token.a.The storage payload format is as follows with object storage bucket details: {"storageInfo": { "storageUrl":"https:// swiftobjectstorage.region .oraclecloud.com/v1/ namespace /bucket ", "storageUser":"[email protected]", "storagePassword":" generated_token " } } For example: { "storageInfo": { "storageUrl":"https://swiftobjectstorage.us- ashburn-1.oraclecloud. |
This action ensures that the storage bucket you create is publicly visible.Otherwise, the export utility cannot see the storage.Chapter 3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-613.In the upper left corner of the page, click .14.Select Identity > Users .This opens the Oracle Identity Service Console to generate a password.15.Select the appropriate user.16.From the Resources list on the left side of the page, select Auth Tokens .17.Click .18.Provide a token description and click .This token is used as part of your JSON payload when upgrading.19.Copy and save the generated token.a.The storage payload format is as follows with object storage bucket details: {"storageInfo": { "storageUrl":"https:// swiftobjectstorage.region .oraclecloud.com/v1/ namespace /bucket ", "storageUser":"[email protected]", "storagePassword":" generated_token " } } For example: { "storageInfo": { "storageUrl":"https://swiftobjectstorage.us- ashburn-1.oraclecloud.com/v1/paasdevoic/cloneRepo", "storageUser":"[email protected]", "storagePassword":" generated_token " } } 20.Construct the storage URL using the following example. |
Otherwise, the export utility cannot see the storage.Chapter 3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-613.In the upper left corner of the page, click .14.Select Identity > Users .This opens the Oracle Identity Service Console to generate a password.15.Select the appropriate user.16.From the Resources list on the left side of the page, select Auth Tokens .17.Click .18.Provide a token description and click .This token is used as part of your JSON payload when upgrading.19.Copy and save the generated token.a.The storage payload format is as follows with object storage bucket details: {"storageInfo": { "storageUrl":"https:// swiftobjectstorage.region .oraclecloud.com/v1/ namespace /bucket ", "storageUser":"[email protected]", "storagePassword":" generated_token " } } For example: { "storageInfo": { "storageUrl":"https://swiftobjectstorage.us- ashburn-1.oraclecloud.com/v1/paasdevoic/cloneRepo", "storageUser":"[email protected]", "storagePassword":" generated_token " } } 20.Construct the storage URL using the following example.You must specify the URL later during the configuration process to migrate your instance. |
Chapter 3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-613.In the upper left corner of the page, click .14.Select Identity > Users .This opens the Oracle Identity Service Console to generate a password.15.Select the appropriate user.16.From the Resources list on the left side of the page, select Auth Tokens .17.Click .18.Provide a token description and click .This token is used as part of your JSON payload when upgrading.19.Copy and save the generated token.a.The storage payload format is as follows with object storage bucket details: {"storageInfo": { "storageUrl":"https:// swiftobjectstorage.region .oraclecloud.com/v1/ namespace /bucket ", "storageUser":"[email protected]", "storagePassword":" generated_token " } } For example: { "storageInfo": { "storageUrl":"https://swiftobjectstorage.us- ashburn-1.oraclecloud.com/v1/paasdevoic/cloneRepo", "storageUser":"[email protected]", "storagePassword":" generated_token " } } 20.Construct the storage URL using the following example.You must specify the URL later during the configuration process to migrate your instance.Step Description Example 1 Enter the Swift API as the base for the URL because you are dealing with object storage.https:// swiftobjectstorage 2 Enter a required data center. |
14.Select Identity > Users .This opens the Oracle Identity Service Console to generate a password.15.Select the appropriate user.16.From the Resources list on the left side of the page, select Auth Tokens .17.Click .18.Provide a token description and click .This token is used as part of your JSON payload when upgrading.19.Copy and save the generated token.a.The storage payload format is as follows with object storage bucket details: {"storageInfo": { "storageUrl":"https:// swiftobjectstorage.region .oraclecloud.com/v1/ namespace /bucket ", "storageUser":"[email protected]", "storagePassword":" generated_token " } } For example: { "storageInfo": { "storageUrl":"https://swiftobjectstorage.us- ashburn-1.oraclecloud.com/v1/paasdevoic/cloneRepo", "storageUser":"[email protected]", "storagePassword":" generated_token " } } 20.Construct the storage URL using the following example.You must specify the URL later during the configuration process to migrate your instance.Step Description Example 1 Enter the Swift API as the base for the URL because you are dealing with object storage.https:// swiftobjectstorage 2 Enter a required data center.To find a data center, navigate to Menu > Administration > Tenancy Details > Home Region (for example: us- ashburn-1 ).https:// swiftobjectstorage.us- ashburn-1Chapter 3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-7Step Description Example 3 Enter the domain name. |
This opens the Oracle Identity Service Console to generate a password.15.Select the appropriate user.16.From the Resources list on the left side of the page, select Auth Tokens .17.Click .18.Provide a token description and click .This token is used as part of your JSON payload when upgrading.19.Copy and save the generated token.a.The storage payload format is as follows with object storage bucket details: {"storageInfo": { "storageUrl":"https:// swiftobjectstorage.region .oraclecloud.com/v1/ namespace /bucket ", "storageUser":"[email protected]", "storagePassword":" generated_token " } } For example: { "storageInfo": { "storageUrl":"https://swiftobjectstorage.us- ashburn-1.oraclecloud.com/v1/paasdevoic/cloneRepo", "storageUser":"[email protected]", "storagePassword":" generated_token " } } 20.Construct the storage URL using the following example.You must specify the URL later during the configuration process to migrate your instance.Step Description Example 1 Enter the Swift API as the base for the URL because you are dealing with object storage.https:// swiftobjectstorage 2 Enter a required data center.To find a data center, navigate to Menu > Administration > Tenancy Details > Home Region (for example: us- ashburn-1 ).https:// swiftobjectstorage.us- ashburn-1Chapter 3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-7Step Description Example 3 Enter the domain name.This is typically oraclecloud.com .https:// swiftobjectstorage.us- ashburn-1.oraclecloud.co m 4 Enter the version: v1. |
15.Select the appropriate user.16.From the Resources list on the left side of the page, select Auth Tokens .17.Click .18.Provide a token description and click .This token is used as part of your JSON payload when upgrading.19.Copy and save the generated token.a.The storage payload format is as follows with object storage bucket details: {"storageInfo": { "storageUrl":"https:// swiftobjectstorage.region .oraclecloud.com/v1/ namespace /bucket ", "storageUser":"[email protected]", "storagePassword":" generated_token " } } For example: { "storageInfo": { "storageUrl":"https://swiftobjectstorage.us- ashburn-1.oraclecloud.com/v1/paasdevoic/cloneRepo", "storageUser":"[email protected]", "storagePassword":" generated_token " } } 20.Construct the storage URL using the following example.You must specify the URL later during the configuration process to migrate your instance.Step Description Example 1 Enter the Swift API as the base for the URL because you are dealing with object storage.https:// swiftobjectstorage 2 Enter a required data center.To find a data center, navigate to Menu > Administration > Tenancy Details > Home Region (for example: us- ashburn-1 ).https:// swiftobjectstorage.us- ashburn-1Chapter 3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-7Step Description Example 3 Enter the domain name.This is typically oraclecloud.com .https:// swiftobjectstorage.us- ashburn-1.oraclecloud.co m 4 Enter the version: v1.https:// swiftobjectstorage.us- ashburn-1.oraclecloud.co m/v1 5 Enter the automatically generated object storage namespace. |
16.From the Resources list on the left side of the page, select Auth Tokens .17.Click .18.Provide a token description and click .This token is used as part of your JSON payload when upgrading.19.Copy and save the generated token.a.The storage payload format is as follows with object storage bucket details: {"storageInfo": { "storageUrl":"https:// swiftobjectstorage.region .oraclecloud.com/v1/ namespace /bucket ", "storageUser":"[email protected]", "storagePassword":" generated_token " } } For example: { "storageInfo": { "storageUrl":"https://swiftobjectstorage.us- ashburn-1.oraclecloud.com/v1/paasdevoic/cloneRepo", "storageUser":"[email protected]", "storagePassword":" generated_token " } } 20.Construct the storage URL using the following example.You must specify the URL later during the configuration process to migrate your instance.Step Description Example 1 Enter the Swift API as the base for the URL because you are dealing with object storage.https:// swiftobjectstorage 2 Enter a required data center.To find a data center, navigate to Menu > Administration > Tenancy Details > Home Region (for example: us- ashburn-1 ).https:// swiftobjectstorage.us- ashburn-1Chapter 3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-7Step Description Example 3 Enter the domain name.This is typically oraclecloud.com .https:// swiftobjectstorage.us- ashburn-1.oraclecloud.co m 4 Enter the version: v1.https:// swiftobjectstorage.us- ashburn-1.oraclecloud.co m/v1 5 Enter the automatically generated object storage namespace.Open the User menu and click Tenancy: your_tenancy_name . |
17.Click .18.Provide a token description and click .This token is used as part of your JSON payload when upgrading.19.Copy and save the generated token.a.The storage payload format is as follows with object storage bucket details: {"storageInfo": { "storageUrl":"https:// swiftobjectstorage.region .oraclecloud.com/v1/ namespace /bucket ", "storageUser":"[email protected]", "storagePassword":" generated_token " } } For example: { "storageInfo": { "storageUrl":"https://swiftobjectstorage.us- ashburn-1.oraclecloud.com/v1/paasdevoic/cloneRepo", "storageUser":"[email protected]", "storagePassword":" generated_token " } } 20.Construct the storage URL using the following example.You must specify the URL later during the configuration process to migrate your instance.Step Description Example 1 Enter the Swift API as the base for the URL because you are dealing with object storage.https:// swiftobjectstorage 2 Enter a required data center.To find a data center, navigate to Menu > Administration > Tenancy Details > Home Region (for example: us- ashburn-1 ).https:// swiftobjectstorage.us- ashburn-1Chapter 3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-7Step Description Example 3 Enter the domain name.This is typically oraclecloud.com .https:// swiftobjectstorage.us- ashburn-1.oraclecloud.co m 4 Enter the version: v1.https:// swiftobjectstorage.us- ashburn-1.oraclecloud.co m/v1 5 Enter the automatically generated object storage namespace.Open the User menu and click Tenancy: your_tenancy_name .The namespace string is listed under Object Storage Settings. |
18.Provide a token description and click .This token is used as part of your JSON payload when upgrading.19.Copy and save the generated token.a.The storage payload format is as follows with object storage bucket details: {"storageInfo": { "storageUrl":"https:// swiftobjectstorage.region .oraclecloud.com/v1/ namespace /bucket ", "storageUser":"[email protected]", "storagePassword":" generated_token " } } For example: { "storageInfo": { "storageUrl":"https://swiftobjectstorage.us- ashburn-1.oraclecloud.com/v1/paasdevoic/cloneRepo", "storageUser":"[email protected]", "storagePassword":" generated_token " } } 20.Construct the storage URL using the following example.You must specify the URL later during the configuration process to migrate your instance.Step Description Example 1 Enter the Swift API as the base for the URL because you are dealing with object storage.https:// swiftobjectstorage 2 Enter a required data center.To find a data center, navigate to Menu > Administration > Tenancy Details > Home Region (for example: us- ashburn-1 ).https:// swiftobjectstorage.us- ashburn-1Chapter 3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-7Step Description Example 3 Enter the domain name.This is typically oraclecloud.com .https:// swiftobjectstorage.us- ashburn-1.oraclecloud.co m 4 Enter the version: v1.https:// swiftobjectstorage.us- ashburn-1.oraclecloud.co m/v1 5 Enter the automatically generated object storage namespace.Open the User menu and click Tenancy: your_tenancy_name .The namespace string is listed under Object Storage Settings.See Understanding Object Storage Namespaces .paasdevoic 6 Enter the bucket name as the last part of the URL.https:// swiftobjectstorage.us- ashburn-1.oraclecloud.co m/v1/paasdevoic/ BUCKET_NAME Examples of the full storage URL to use later in the payload are as follows: https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic/cloneRepo https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic/migrationartifacts_bucket-20190717-1223 Step 4: Migrate Integrations and Processes You can use the Application Migration Service to migrate Integrations and Processes design-time metadata in your instance to Oracle Integration Generation 2. |
This token is used as part of your JSON payload when upgrading.19.Copy and save the generated token.a.The storage payload format is as follows with object storage bucket details: {"storageInfo": { "storageUrl":"https:// swiftobjectstorage.region .oraclecloud.com/v1/ namespace /bucket ", "storageUser":"[email protected]", "storagePassword":" generated_token " } } For example: { "storageInfo": { "storageUrl":"https://swiftobjectstorage.us- ashburn-1.oraclecloud.com/v1/paasdevoic/cloneRepo", "storageUser":"[email protected]", "storagePassword":" generated_token " } } 20.Construct the storage URL using the following example.You must specify the URL later during the configuration process to migrate your instance.Step Description Example 1 Enter the Swift API as the base for the URL because you are dealing with object storage.https:// swiftobjectstorage 2 Enter a required data center.To find a data center, navigate to Menu > Administration > Tenancy Details > Home Region (for example: us- ashburn-1 ).https:// swiftobjectstorage.us- ashburn-1Chapter 3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-7Step Description Example 3 Enter the domain name.This is typically oraclecloud.com .https:// swiftobjectstorage.us- ashburn-1.oraclecloud.co m 4 Enter the version: v1.https:// swiftobjectstorage.us- ashburn-1.oraclecloud.co m/v1 5 Enter the automatically generated object storage namespace.Open the User menu and click Tenancy: your_tenancy_name .The namespace string is listed under Object Storage Settings.See Understanding Object Storage Namespaces .paasdevoic 6 Enter the bucket name as the last part of the URL.https:// swiftobjectstorage.us- ashburn-1.oraclecloud.co m/v1/paasdevoic/ BUCKET_NAME Examples of the full storage URL to use later in the payload are as follows: https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic/cloneRepo https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic/migrationartifacts_bucket-20190717-1223 Step 4: Migrate Integrations and Processes You can use the Application Migration Service to migrate Integrations and Processes design-time metadata in your instance to Oracle Integration Generation 2.Access to the Application Migration Service is included in the One Console of Oracle Cloud Infrastructure. |
19.Copy and save the generated token.a.The storage payload format is as follows with object storage bucket details: {"storageInfo": { "storageUrl":"https:// swiftobjectstorage.region .oraclecloud.com/v1/ namespace /bucket ", "storageUser":"[email protected]", "storagePassword":" generated_token " } } For example: { "storageInfo": { "storageUrl":"https://swiftobjectstorage.us- ashburn-1.oraclecloud.com/v1/paasdevoic/cloneRepo", "storageUser":"[email protected]", "storagePassword":" generated_token " } } 20.Construct the storage URL using the following example.You must specify the URL later during the configuration process to migrate your instance.Step Description Example 1 Enter the Swift API as the base for the URL because you are dealing with object storage.https:// swiftobjectstorage 2 Enter a required data center.To find a data center, navigate to Menu > Administration > Tenancy Details > Home Region (for example: us- ashburn-1 ).https:// swiftobjectstorage.us- ashburn-1Chapter 3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-7Step Description Example 3 Enter the domain name.This is typically oraclecloud.com .https:// swiftobjectstorage.us- ashburn-1.oraclecloud.co m 4 Enter the version: v1.https:// swiftobjectstorage.us- ashburn-1.oraclecloud.co m/v1 5 Enter the automatically generated object storage namespace.Open the User menu and click Tenancy: your_tenancy_name .The namespace string is listed under Object Storage Settings.See Understanding Object Storage Namespaces .paasdevoic 6 Enter the bucket name as the last part of the URL.https:// swiftobjectstorage.us- ashburn-1.oraclecloud.co m/v1/paasdevoic/ BUCKET_NAME Examples of the full storage URL to use later in the payload are as follows: https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic/cloneRepo https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic/migrationartifacts_bucket-20190717-1223 Step 4: Migrate Integrations and Processes You can use the Application Migration Service to migrate Integrations and Processes design-time metadata in your instance to Oracle Integration Generation 2.Access to the Application Migration Service is included in the One Console of Oracle Cloud Infrastructure.A user that is an administrator of the tenancy (in the Administrators group) can perform the migration. |
a.The storage payload format is as follows with object storage bucket details: {"storageInfo": { "storageUrl":"https:// swiftobjectstorage.region .oraclecloud.com/v1/ namespace /bucket ", "storageUser":"[email protected]", "storagePassword":" generated_token " } } For example: { "storageInfo": { "storageUrl":"https://swiftobjectstorage.us- ashburn-1.oraclecloud.com/v1/paasdevoic/cloneRepo", "storageUser":"[email protected]", "storagePassword":" generated_token " } } 20.Construct the storage URL using the following example.You must specify the URL later during the configuration process to migrate your instance.Step Description Example 1 Enter the Swift API as the base for the URL because you are dealing with object storage.https:// swiftobjectstorage 2 Enter a required data center.To find a data center, navigate to Menu > Administration > Tenancy Details > Home Region (for example: us- ashburn-1 ).https:// swiftobjectstorage.us- ashburn-1Chapter 3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-7Step Description Example 3 Enter the domain name.This is typically oraclecloud.com .https:// swiftobjectstorage.us- ashburn-1.oraclecloud.co m 4 Enter the version: v1.https:// swiftobjectstorage.us- ashburn-1.oraclecloud.co m/v1 5 Enter the automatically generated object storage namespace.Open the User menu and click Tenancy: your_tenancy_name .The namespace string is listed under Object Storage Settings.See Understanding Object Storage Namespaces .paasdevoic 6 Enter the bucket name as the last part of the URL.https:// swiftobjectstorage.us- ashburn-1.oraclecloud.co m/v1/paasdevoic/ BUCKET_NAME Examples of the full storage URL to use later in the payload are as follows: https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic/cloneRepo https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic/migrationartifacts_bucket-20190717-1223 Step 4: Migrate Integrations and Processes You can use the Application Migration Service to migrate Integrations and Processes design-time metadata in your instance to Oracle Integration Generation 2.Access to the Application Migration Service is included in the One Console of Oracle Cloud Infrastructure.A user that is an administrator of the tenancy (in the Administrators group) can perform the migration.Note: Visual Builder design-time metadata cannot be migrated with the Application Migration Service. |
The storage payload format is as follows with object storage bucket details: {"storageInfo": { "storageUrl":"https:// swiftobjectstorage.region .oraclecloud.com/v1/ namespace /bucket ", "storageUser":"[email protected]", "storagePassword":" generated_token " } } For example: { "storageInfo": { "storageUrl":"https://swiftobjectstorage.us- ashburn-1.oraclecloud.com/v1/paasdevoic/cloneRepo", "storageUser":"[email protected]", "storagePassword":" generated_token " } } 20.Construct the storage URL using the following example.You must specify the URL later during the configuration process to migrate your instance.Step Description Example 1 Enter the Swift API as the base for the URL because you are dealing with object storage.https:// swiftobjectstorage 2 Enter a required data center.To find a data center, navigate to Menu > Administration > Tenancy Details > Home Region (for example: us- ashburn-1 ).https:// swiftobjectstorage.us- ashburn-1Chapter 3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-7Step Description Example 3 Enter the domain name.This is typically oraclecloud.com .https:// swiftobjectstorage.us- ashburn-1.oraclecloud.co m 4 Enter the version: v1.https:// swiftobjectstorage.us- ashburn-1.oraclecloud.co m/v1 5 Enter the automatically generated object storage namespace.Open the User menu and click Tenancy: your_tenancy_name .The namespace string is listed under Object Storage Settings.See Understanding Object Storage Namespaces .paasdevoic 6 Enter the bucket name as the last part of the URL.https:// swiftobjectstorage.us- ashburn-1.oraclecloud.co m/v1/paasdevoic/ BUCKET_NAME Examples of the full storage URL to use later in the payload are as follows: https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic/cloneRepo https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic/migrationartifacts_bucket-20190717-1223 Step 4: Migrate Integrations and Processes You can use the Application Migration Service to migrate Integrations and Processes design-time metadata in your instance to Oracle Integration Generation 2.Access to the Application Migration Service is included in the One Console of Oracle Cloud Infrastructure.A user that is an administrator of the tenancy (in the Administrators group) can perform the migration.Note: Visual Builder design-time metadata cannot be migrated with the Application Migration Service.Topics: Create a Source Create a Migration Configure the Migration Target InstanceChapter 3 Step 4: Migrate Integrations and Processes 3-8Start the Migration The Application Migration Service is also described in the Oracle Cloud Infrastructure Documentation Library. |
region .oraclecloud.com/v1/ namespace /bucket ", "storageUser":"[email protected]", "storagePassword":" generated_token " } } For example: { "storageInfo": { "storageUrl":"https://swiftobjectstorage.us- ashburn-1.oraclecloud.com/v1/paasdevoic/cloneRepo", "storageUser":"[email protected]", "storagePassword":" generated_token " } } 20.Construct the storage URL using the following example.You must specify the URL later during the configuration process to migrate your instance.Step Description Example 1 Enter the Swift API as the base for the URL because you are dealing with object storage.https:// swiftobjectstorage 2 Enter a required data center.To find a data center, navigate to Menu > Administration > Tenancy Details > Home Region (for example: us- ashburn-1 ).https:// swiftobjectstorage.us- ashburn-1Chapter 3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-7Step Description Example 3 Enter the domain name.This is typically oraclecloud.com .https:// swiftobjectstorage.us- ashburn-1.oraclecloud.co m 4 Enter the version: v1.https:// swiftobjectstorage.us- ashburn-1.oraclecloud.co m/v1 5 Enter the automatically generated object storage namespace.Open the User menu and click Tenancy: your_tenancy_name .The namespace string is listed under Object Storage Settings.See Understanding Object Storage Namespaces .paasdevoic 6 Enter the bucket name as the last part of the URL.https:// swiftobjectstorage.us- ashburn-1.oraclecloud.co m/v1/paasdevoic/ BUCKET_NAME Examples of the full storage URL to use later in the payload are as follows: https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic/cloneRepo https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic/migrationartifacts_bucket-20190717-1223 Step 4: Migrate Integrations and Processes You can use the Application Migration Service to migrate Integrations and Processes design-time metadata in your instance to Oracle Integration Generation 2.Access to the Application Migration Service is included in the One Console of Oracle Cloud Infrastructure.A user that is an administrator of the tenancy (in the Administrators group) can perform the migration.Note: Visual Builder design-time metadata cannot be migrated with the Application Migration Service.Topics: Create a Source Create a Migration Configure the Migration Target InstanceChapter 3 Step 4: Migrate Integrations and Processes 3-8Start the Migration The Application Migration Service is also described in the Oracle Cloud Infrastructure Documentation Library.See Manage Migrations . |
com/v1/paasdevoic/cloneRepo", "storageUser":"[email protected]", "storagePassword":" generated_token " } } 20.Construct the storage URL using the following example.You must specify the URL later during the configuration process to migrate your instance.Step Description Example 1 Enter the Swift API as the base for the URL because you are dealing with object storage.https:// swiftobjectstorage 2 Enter a required data center.To find a data center, navigate to Menu > Administration > Tenancy Details > Home Region (for example: us- ashburn-1 ).https:// swiftobjectstorage.us- ashburn-1Chapter 3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-7Step Description Example 3 Enter the domain name.This is typically oraclecloud.com .https:// swiftobjectstorage.us- ashburn-1.oraclecloud.co m 4 Enter the version: v1.https:// swiftobjectstorage.us- ashburn-1.oraclecloud.co m/v1 5 Enter the automatically generated object storage namespace.Open the User menu and click Tenancy: your_tenancy_name .The namespace string is listed under Object Storage Settings.See Understanding Object Storage Namespaces .paasdevoic 6 Enter the bucket name as the last part of the URL.https:// swiftobjectstorage.us- ashburn-1.oraclecloud.co m/v1/paasdevoic/ BUCKET_NAME Examples of the full storage URL to use later in the payload are as follows: https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic/cloneRepo https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic/migrationartifacts_bucket-20190717-1223 Step 4: Migrate Integrations and Processes You can use the Application Migration Service to migrate Integrations and Processes design-time metadata in your instance to Oracle Integration Generation 2.Access to the Application Migration Service is included in the One Console of Oracle Cloud Infrastructure.A user that is an administrator of the tenancy (in the Administrators group) can perform the migration.Note: Visual Builder design-time metadata cannot be migrated with the Application Migration Service.Topics: Create a Source Create a Migration Configure the Migration Target InstanceChapter 3 Step 4: Migrate Integrations and Processes 3-8Start the Migration The Application Migration Service is also described in the Oracle Cloud Infrastructure Documentation Library.See Manage Migrations .Create a Source You must create a source migration to map your Oracle Integration Classic account and region to the Oracle Cloud Infrastructure tenancy. |
You must specify the URL later during the configuration process to migrate your instance.Step Description Example 1 Enter the Swift API as the base for the URL because you are dealing with object storage.https:// swiftobjectstorage 2 Enter a required data center.To find a data center, navigate to Menu > Administration > Tenancy Details > Home Region (for example: us- ashburn-1 ).https:// swiftobjectstorage.us- ashburn-1Chapter 3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-7Step Description Example 3 Enter the domain name.This is typically oraclecloud.com .https:// swiftobjectstorage.us- ashburn-1.oraclecloud.co m 4 Enter the version: v1.https:// swiftobjectstorage.us- ashburn-1.oraclecloud.co m/v1 5 Enter the automatically generated object storage namespace.Open the User menu and click Tenancy: your_tenancy_name .The namespace string is listed under Object Storage Settings.See Understanding Object Storage Namespaces .paasdevoic 6 Enter the bucket name as the last part of the URL.https:// swiftobjectstorage.us- ashburn-1.oraclecloud.co m/v1/paasdevoic/ BUCKET_NAME Examples of the full storage URL to use later in the payload are as follows: https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic/cloneRepo https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic/migrationartifacts_bucket-20190717-1223 Step 4: Migrate Integrations and Processes You can use the Application Migration Service to migrate Integrations and Processes design-time metadata in your instance to Oracle Integration Generation 2.Access to the Application Migration Service is included in the One Console of Oracle Cloud Infrastructure.A user that is an administrator of the tenancy (in the Administrators group) can perform the migration.Note: Visual Builder design-time metadata cannot be migrated with the Application Migration Service.Topics: Create a Source Create a Migration Configure the Migration Target InstanceChapter 3 Step 4: Migrate Integrations and Processes 3-8Start the Migration The Application Migration Service is also described in the Oracle Cloud Infrastructure Documentation Library.See Manage Migrations .Create a Source You must create a source migration to map your Oracle Integration Classic account and region to the Oracle Cloud Infrastructure tenancy.If migrating from multiple regions (for example, uscom-central-1 and uscom-east-1), a different source is required for each. |
Step Description Example 1 Enter the Swift API as the base for the URL because you are dealing with object storage.https:// swiftobjectstorage 2 Enter a required data center.To find a data center, navigate to Menu > Administration > Tenancy Details > Home Region (for example: us- ashburn-1 ).https:// swiftobjectstorage.us- ashburn-1Chapter 3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-7Step Description Example 3 Enter the domain name.This is typically oraclecloud.com .https:// swiftobjectstorage.us- ashburn-1.oraclecloud.co m 4 Enter the version: v1.https:// swiftobjectstorage.us- ashburn-1.oraclecloud.co m/v1 5 Enter the automatically generated object storage namespace.Open the User menu and click Tenancy: your_tenancy_name .The namespace string is listed under Object Storage Settings.See Understanding Object Storage Namespaces .paasdevoic 6 Enter the bucket name as the last part of the URL.https:// swiftobjectstorage.us- ashburn-1.oraclecloud.co m/v1/paasdevoic/ BUCKET_NAME Examples of the full storage URL to use later in the payload are as follows: https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic/cloneRepo https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic/migrationartifacts_bucket-20190717-1223 Step 4: Migrate Integrations and Processes You can use the Application Migration Service to migrate Integrations and Processes design-time metadata in your instance to Oracle Integration Generation 2.Access to the Application Migration Service is included in the One Console of Oracle Cloud Infrastructure.A user that is an administrator of the tenancy (in the Administrators group) can perform the migration.Note: Visual Builder design-time metadata cannot be migrated with the Application Migration Service.Topics: Create a Source Create a Migration Configure the Migration Target InstanceChapter 3 Step 4: Migrate Integrations and Processes 3-8Start the Migration The Application Migration Service is also described in the Oracle Cloud Infrastructure Documentation Library.See Manage Migrations .Create a Source You must create a source migration to map your Oracle Integration Classic account and region to the Oracle Cloud Infrastructure tenancy.If migrating from multiple regions (for example, uscom-central-1 and uscom-east-1), a different source is required for each.Creating a source migration enables you to discover the list of applications (instances) that are available to migrate. |
To find a data center, navigate to Menu > Administration > Tenancy Details > Home Region (for example: us- ashburn-1 ).https:// swiftobjectstorage.us- ashburn-1Chapter 3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-7Step Description Example 3 Enter the domain name.This is typically oraclecloud.com .https:// swiftobjectstorage.us- ashburn-1.oraclecloud.co m 4 Enter the version: v1.https:// swiftobjectstorage.us- ashburn-1.oraclecloud.co m/v1 5 Enter the automatically generated object storage namespace.Open the User menu and click Tenancy: your_tenancy_name .The namespace string is listed under Object Storage Settings.See Understanding Object Storage Namespaces .paasdevoic 6 Enter the bucket name as the last part of the URL.https:// swiftobjectstorage.us- ashburn-1.oraclecloud.co m/v1/paasdevoic/ BUCKET_NAME Examples of the full storage URL to use later in the payload are as follows: https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic/cloneRepo https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic/migrationartifacts_bucket-20190717-1223 Step 4: Migrate Integrations and Processes You can use the Application Migration Service to migrate Integrations and Processes design-time metadata in your instance to Oracle Integration Generation 2.Access to the Application Migration Service is included in the One Console of Oracle Cloud Infrastructure.A user that is an administrator of the tenancy (in the Administrators group) can perform the migration.Note: Visual Builder design-time metadata cannot be migrated with the Application Migration Service.Topics: Create a Source Create a Migration Configure the Migration Target InstanceChapter 3 Step 4: Migrate Integrations and Processes 3-8Start the Migration The Application Migration Service is also described in the Oracle Cloud Infrastructure Documentation Library.See Manage Migrations .Create a Source You must create a source migration to map your Oracle Integration Classic account and region to the Oracle Cloud Infrastructure tenancy.If migrating from multiple regions (for example, uscom-central-1 and uscom-east-1), a different source is required for each.Creating a source migration enables you to discover the list of applications (instances) that are available to migrate.Note: Ensure you have the required permissions to perform a migration. |
This is typically oraclecloud.com .https:// swiftobjectstorage.us- ashburn-1.oraclecloud.co m 4 Enter the version: v1.https:// swiftobjectstorage.us- ashburn-1.oraclecloud.co m/v1 5 Enter the automatically generated object storage namespace.Open the User menu and click Tenancy: your_tenancy_name .The namespace string is listed under Object Storage Settings.See Understanding Object Storage Namespaces .paasdevoic 6 Enter the bucket name as the last part of the URL.https:// swiftobjectstorage.us- ashburn-1.oraclecloud.co m/v1/paasdevoic/ BUCKET_NAME Examples of the full storage URL to use later in the payload are as follows: https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic/cloneRepo https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic/migrationartifacts_bucket-20190717-1223 Step 4: Migrate Integrations and Processes You can use the Application Migration Service to migrate Integrations and Processes design-time metadata in your instance to Oracle Integration Generation 2.Access to the Application Migration Service is included in the One Console of Oracle Cloud Infrastructure.A user that is an administrator of the tenancy (in the Administrators group) can perform the migration.Note: Visual Builder design-time metadata cannot be migrated with the Application Migration Service.Topics: Create a Source Create a Migration Configure the Migration Target InstanceChapter 3 Step 4: Migrate Integrations and Processes 3-8Start the Migration The Application Migration Service is also described in the Oracle Cloud Infrastructure Documentation Library.See Manage Migrations .Create a Source You must create a source migration to map your Oracle Integration Classic account and region to the Oracle Cloud Infrastructure tenancy.If migrating from multiple regions (for example, uscom-central-1 and uscom-east-1), a different source is required for each.Creating a source migration enables you to discover the list of applications (instances) that are available to migrate.Note: Ensure you have the required permissions to perform a migration.See Service Permissions . |
https:// swiftobjectstorage.us- ashburn-1.oraclecloud.co m/v1 5 Enter the automatically generated object storage namespace.Open the User menu and click Tenancy: your_tenancy_name .The namespace string is listed under Object Storage Settings.See Understanding Object Storage Namespaces .paasdevoic 6 Enter the bucket name as the last part of the URL.https:// swiftobjectstorage.us- ashburn-1.oraclecloud.co m/v1/paasdevoic/ BUCKET_NAME Examples of the full storage URL to use later in the payload are as follows: https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic/cloneRepo https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic/migrationartifacts_bucket-20190717-1223 Step 4: Migrate Integrations and Processes You can use the Application Migration Service to migrate Integrations and Processes design-time metadata in your instance to Oracle Integration Generation 2.Access to the Application Migration Service is included in the One Console of Oracle Cloud Infrastructure.A user that is an administrator of the tenancy (in the Administrators group) can perform the migration.Note: Visual Builder design-time metadata cannot be migrated with the Application Migration Service.Topics: Create a Source Create a Migration Configure the Migration Target InstanceChapter 3 Step 4: Migrate Integrations and Processes 3-8Start the Migration The Application Migration Service is also described in the Oracle Cloud Infrastructure Documentation Library.See Manage Migrations .Create a Source You must create a source migration to map your Oracle Integration Classic account and region to the Oracle Cloud Infrastructure tenancy.If migrating from multiple regions (for example, uscom-central-1 and uscom-east-1), a different source is required for each.Creating a source migration enables you to discover the list of applications (instances) that are available to migrate.Note: Ensure you have the required permissions to perform a migration.See Service Permissions .1.Sign in to the One Console of Oracle Cloud Infrastructure. |
Open the User menu and click Tenancy: your_tenancy_name .The namespace string is listed under Object Storage Settings.See Understanding Object Storage Namespaces .paasdevoic 6 Enter the bucket name as the last part of the URL.https:// swiftobjectstorage.us- ashburn-1.oraclecloud.co m/v1/paasdevoic/ BUCKET_NAME Examples of the full storage URL to use later in the payload are as follows: https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic/cloneRepo https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic/migrationartifacts_bucket-20190717-1223 Step 4: Migrate Integrations and Processes You can use the Application Migration Service to migrate Integrations and Processes design-time metadata in your instance to Oracle Integration Generation 2.Access to the Application Migration Service is included in the One Console of Oracle Cloud Infrastructure.A user that is an administrator of the tenancy (in the Administrators group) can perform the migration.Note: Visual Builder design-time metadata cannot be migrated with the Application Migration Service.Topics: Create a Source Create a Migration Configure the Migration Target InstanceChapter 3 Step 4: Migrate Integrations and Processes 3-8Start the Migration The Application Migration Service is also described in the Oracle Cloud Infrastructure Documentation Library.See Manage Migrations .Create a Source You must create a source migration to map your Oracle Integration Classic account and region to the Oracle Cloud Infrastructure tenancy.If migrating from multiple regions (for example, uscom-central-1 and uscom-east-1), a different source is required for each.Creating a source migration enables you to discover the list of applications (instances) that are available to migrate.Note: Ensure you have the required permissions to perform a migration.See Service Permissions .1.Sign in to the One Console of Oracle Cloud Infrastructure.2.In the upper left corner, select . |
The namespace string is listed under Object Storage Settings.See Understanding Object Storage Namespaces .paasdevoic 6 Enter the bucket name as the last part of the URL.https:// swiftobjectstorage.us- ashburn-1.oraclecloud.co m/v1/paasdevoic/ BUCKET_NAME Examples of the full storage URL to use later in the payload are as follows: https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic/cloneRepo https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic/migrationartifacts_bucket-20190717-1223 Step 4: Migrate Integrations and Processes You can use the Application Migration Service to migrate Integrations and Processes design-time metadata in your instance to Oracle Integration Generation 2.Access to the Application Migration Service is included in the One Console of Oracle Cloud Infrastructure.A user that is an administrator of the tenancy (in the Administrators group) can perform the migration.Note: Visual Builder design-time metadata cannot be migrated with the Application Migration Service.Topics: Create a Source Create a Migration Configure the Migration Target InstanceChapter 3 Step 4: Migrate Integrations and Processes 3-8Start the Migration The Application Migration Service is also described in the Oracle Cloud Infrastructure Documentation Library.See Manage Migrations .Create a Source You must create a source migration to map your Oracle Integration Classic account and region to the Oracle Cloud Infrastructure tenancy.If migrating from multiple regions (for example, uscom-central-1 and uscom-east-1), a different source is required for each.Creating a source migration enables you to discover the list of applications (instances) that are available to migrate.Note: Ensure you have the required permissions to perform a migration.See Service Permissions .1.Sign in to the One Console of Oracle Cloud Infrastructure.2.In the upper left corner, select .3.Under Solutions and Platform , select Application Migration . |
See Understanding Object Storage Namespaces .paasdevoic 6 Enter the bucket name as the last part of the URL.https:// swiftobjectstorage.us- ashburn-1.oraclecloud.co m/v1/paasdevoic/ BUCKET_NAME Examples of the full storage URL to use later in the payload are as follows: https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic/cloneRepo https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic/migrationartifacts_bucket-20190717-1223 Step 4: Migrate Integrations and Processes You can use the Application Migration Service to migrate Integrations and Processes design-time metadata in your instance to Oracle Integration Generation 2.Access to the Application Migration Service is included in the One Console of Oracle Cloud Infrastructure.A user that is an administrator of the tenancy (in the Administrators group) can perform the migration.Note: Visual Builder design-time metadata cannot be migrated with the Application Migration Service.Topics: Create a Source Create a Migration Configure the Migration Target InstanceChapter 3 Step 4: Migrate Integrations and Processes 3-8Start the Migration The Application Migration Service is also described in the Oracle Cloud Infrastructure Documentation Library.See Manage Migrations .Create a Source You must create a source migration to map your Oracle Integration Classic account and region to the Oracle Cloud Infrastructure tenancy.If migrating from multiple regions (for example, uscom-central-1 and uscom-east-1), a different source is required for each.Creating a source migration enables you to discover the list of applications (instances) that are available to migrate.Note: Ensure you have the required permissions to perform a migration.See Service Permissions .1.Sign in to the One Console of Oracle Cloud Infrastructure.2.In the upper left corner, select .3.Under Solutions and Platform , select Application Migration .The Overview page shows a workflow for using the Application Migration Service. |
Access to the Application Migration Service is included in the One Console of Oracle Cloud Infrastructure.A user that is an administrator of the tenancy (in the Administrators group) can perform the migration.Note: Visual Builder design-time metadata cannot be migrated with the Application Migration Service.Topics: Create a Source Create a Migration Configure the Migration Target InstanceChapter 3 Step 4: Migrate Integrations and Processes 3-8Start the Migration The Application Migration Service is also described in the Oracle Cloud Infrastructure Documentation Library.See Manage Migrations .Create a Source You must create a source migration to map your Oracle Integration Classic account and region to the Oracle Cloud Infrastructure tenancy.If migrating from multiple regions (for example, uscom-central-1 and uscom-east-1), a different source is required for each.Creating a source migration enables you to discover the list of applications (instances) that are available to migrate.Note: Ensure you have the required permissions to perform a migration.See Service Permissions .1.Sign in to the One Console of Oracle Cloud Infrastructure.2.In the upper left corner, select .3.Under Solutions and Platform , select Application Migration .The Overview page shows a workflow for using the Application Migration Service.The Application Migration Service also checks if you have satisfied migration perquisites and identifies any issues that must be satisfied before beginning. |
A user that is an administrator of the tenancy (in the Administrators group) can perform the migration.Note: Visual Builder design-time metadata cannot be migrated with the Application Migration Service.Topics: Create a Source Create a Migration Configure the Migration Target InstanceChapter 3 Step 4: Migrate Integrations and Processes 3-8Start the Migration The Application Migration Service is also described in the Oracle Cloud Infrastructure Documentation Library.See Manage Migrations .Create a Source You must create a source migration to map your Oracle Integration Classic account and region to the Oracle Cloud Infrastructure tenancy.If migrating from multiple regions (for example, uscom-central-1 and uscom-east-1), a different source is required for each.Creating a source migration enables you to discover the list of applications (instances) that are available to migrate.Note: Ensure you have the required permissions to perform a migration.See Service Permissions .1.Sign in to the One Console of Oracle Cloud Infrastructure.2.In the upper left corner, select .3.Under Solutions and Platform , select Application Migration .The Overview page shows a workflow for using the Application Migration Service.The Application Migration Service also checks if you have satisfied migration perquisites and identifies any issues that must be satisfied before beginning.4.In the left pane under Application Migration , click Sources . |
Note: Visual Builder design-time metadata cannot be migrated with the Application Migration Service.Topics: Create a Source Create a Migration Configure the Migration Target InstanceChapter 3 Step 4: Migrate Integrations and Processes 3-8Start the Migration The Application Migration Service is also described in the Oracle Cloud Infrastructure Documentation Library.See Manage Migrations .Create a Source You must create a source migration to map your Oracle Integration Classic account and region to the Oracle Cloud Infrastructure tenancy.If migrating from multiple regions (for example, uscom-central-1 and uscom-east-1), a different source is required for each.Creating a source migration enables you to discover the list of applications (instances) that are available to migrate.Note: Ensure you have the required permissions to perform a migration.See Service Permissions .1.Sign in to the One Console of Oracle Cloud Infrastructure.2.In the upper left corner, select .3.Under Solutions and Platform , select Application Migration .The Overview page shows a workflow for using the Application Migration Service.The Application Migration Service also checks if you have satisfied migration perquisites and identifies any issues that must be satisfied before beginning.4.In the left pane under Application Migration , click Sources .5.From the Compartment list, select a compartment in which you have permission to work. |
Topics: Create a Source Create a Migration Configure the Migration Target InstanceChapter 3 Step 4: Migrate Integrations and Processes 3-8Start the Migration The Application Migration Service is also described in the Oracle Cloud Infrastructure Documentation Library.See Manage Migrations .Create a Source You must create a source migration to map your Oracle Integration Classic account and region to the Oracle Cloud Infrastructure tenancy.If migrating from multiple regions (for example, uscom-central-1 and uscom-east-1), a different source is required for each.Creating a source migration enables you to discover the list of applications (instances) that are available to migrate.Note: Ensure you have the required permissions to perform a migration.See Service Permissions .1.Sign in to the One Console of Oracle Cloud Infrastructure.2.In the upper left corner, select .3.Under Solutions and Platform , select Application Migration .The Overview page shows a workflow for using the Application Migration Service.The Application Migration Service also checks if you have satisfied migration perquisites and identifies any issues that must be satisfied before beginning.4.In the left pane under Application Migration , click Sources .5.From the Compartment list, select a compartment in which you have permission to work.The page updates to display only the resources in that compartment. |
See Manage Migrations .Create a Source You must create a source migration to map your Oracle Integration Classic account and region to the Oracle Cloud Infrastructure tenancy.If migrating from multiple regions (for example, uscom-central-1 and uscom-east-1), a different source is required for each.Creating a source migration enables you to discover the list of applications (instances) that are available to migrate.Note: Ensure you have the required permissions to perform a migration.See Service Permissions .1.Sign in to the One Console of Oracle Cloud Infrastructure.2.In the upper left corner, select .3.Under Solutions and Platform , select Application Migration .The Overview page shows a workflow for using the Application Migration Service.The Application Migration Service also checks if you have satisfied migration perquisites and identifies any issues that must be satisfied before beginning.4.In the left pane under Application Migration , click Sources .5.From the Compartment list, select a compartment in which you have permission to work.The page updates to display only the resources in that compartment.If you're not sure which compartment to use, contact an administrator. |
Create a Source You must create a source migration to map your Oracle Integration Classic account and region to the Oracle Cloud Infrastructure tenancy.If migrating from multiple regions (for example, uscom-central-1 and uscom-east-1), a different source is required for each.Creating a source migration enables you to discover the list of applications (instances) that are available to migrate.Note: Ensure you have the required permissions to perform a migration.See Service Permissions .1.Sign in to the One Console of Oracle Cloud Infrastructure.2.In the upper left corner, select .3.Under Solutions and Platform , select Application Migration .The Overview page shows a workflow for using the Application Migration Service.The Application Migration Service also checks if you have satisfied migration perquisites and identifies any issues that must be satisfied before beginning.4.In the left pane under Application Migration , click Sources .5.From the Compartment list, select a compartment in which you have permission to work.The page updates to display only the resources in that compartment.If you're not sure which compartment to use, contact an administrator.For more information, see Access Control . |
If migrating from multiple regions (for example, uscom-central-1 and uscom-east-1), a different source is required for each.Creating a source migration enables you to discover the list of applications (instances) that are available to migrate.Note: Ensure you have the required permissions to perform a migration.See Service Permissions .1.Sign in to the One Console of Oracle Cloud Infrastructure.2.In the upper left corner, select .3.Under Solutions and Platform , select Application Migration .The Overview page shows a workflow for using the Application Migration Service.The Application Migration Service also checks if you have satisfied migration perquisites and identifies any issues that must be satisfied before beginning.4.In the left pane under Application Migration , click Sources .5.From the Compartment list, select a compartment in which you have permission to work.The page updates to display only the resources in that compartment.If you're not sure which compartment to use, contact an administrator.For more information, see Access Control .6.Click Create Source . |
Creating a source migration enables you to discover the list of applications (instances) that are available to migrate.Note: Ensure you have the required permissions to perform a migration.See Service Permissions .1.Sign in to the One Console of Oracle Cloud Infrastructure.2.In the upper left corner, select .3.Under Solutions and Platform , select Application Migration .The Overview page shows a workflow for using the Application Migration Service.The Application Migration Service also checks if you have satisfied migration perquisites and identifies any issues that must be satisfied before beginning.4.In the left pane under Application Migration , click Sources .5.From the Compartment list, select a compartment in which you have permission to work.The page updates to display only the resources in that compartment.If you're not sure which compartment to use, contact an administrator.For more information, see Access Control .6.Click Create Source .Note: The Create Source option is also available in the workflow on the Overview page. |
Note: Ensure you have the required permissions to perform a migration.See Service Permissions .1.Sign in to the One Console of Oracle Cloud Infrastructure.2.In the upper left corner, select .3.Under Solutions and Platform , select Application Migration .The Overview page shows a workflow for using the Application Migration Service.The Application Migration Service also checks if you have satisfied migration perquisites and identifies any issues that must be satisfied before beginning.4.In the left pane under Application Migration , click Sources .5.From the Compartment list, select a compartment in which you have permission to work.The page updates to display only the resources in that compartment.If you're not sure which compartment to use, contact an administrator.For more information, see Access Control .6.Click Create Source .Note: The Create Source option is also available in the workflow on the Overview page.7.Enter the following details, then click Create . |
See Service Permissions .1.Sign in to the One Console of Oracle Cloud Infrastructure.2.In the upper left corner, select .3.Under Solutions and Platform , select Application Migration .The Overview page shows a workflow for using the Application Migration Service.The Application Migration Service also checks if you have satisfied migration perquisites and identifies any issues that must be satisfied before beginning.4.In the left pane under Application Migration , click Sources .5.From the Compartment list, select a compartment in which you have permission to work.The page updates to display only the resources in that compartment.If you're not sure which compartment to use, contact an administrator.For more information, see Access Control .6.Click Create Source .Note: The Create Source option is also available in the workflow on the Overview page.7.Enter the following details, then click Create .Element Description Name Enter a name for the source (for this example, oicmigrationamsdemo is entered). |
1.Sign in to the One Console of Oracle Cloud Infrastructure.2.In the upper left corner, select .3.Under Solutions and Platform , select Application Migration .The Overview page shows a workflow for using the Application Migration Service.The Application Migration Service also checks if you have satisfied migration perquisites and identifies any issues that must be satisfied before beginning.4.In the left pane under Application Migration , click Sources .5.From the Compartment list, select a compartment in which you have permission to work.The page updates to display only the resources in that compartment.If you're not sure which compartment to use, contact an administrator.For more information, see Access Control .6.Click Create Source .Note: The Create Source option is also available in the workflow on the Overview page.7.Enter the following details, then click Create .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. |
2.In the upper left corner, select .3.Under Solutions and Platform , select Application Migration .The Overview page shows a workflow for using the Application Migration Service.The Application Migration Service also checks if you have satisfied migration perquisites and identifies any issues that must be satisfied before beginning.4.In the left pane under Application Migration , click Sources .5.From the Compartment list, select a compartment in which you have permission to work.The page updates to display only the resources in that compartment.If you're not sure which compartment to use, contact an administrator.For more information, see Access Control .6.Click Create Source .Note: The Create Source option is also available in the workflow on the Overview page.7.Enter the following details, then click Create .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. |
3.Under Solutions and Platform , select Application Migration .The Overview page shows a workflow for using the Application Migration Service.The Application Migration Service also checks if you have satisfied migration perquisites and identifies any issues that must be satisfied before beginning.4.In the left pane under Application Migration , click Sources .5.From the Compartment list, select a compartment in which you have permission to work.The page updates to display only the resources in that compartment.If you're not sure which compartment to use, contact an administrator.For more information, see Access Control .6.Click Create Source .Note: The Create Source option is also available in the workflow on the Overview page.7.Enter the following details, then click Create .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. |
The Overview page shows a workflow for using the Application Migration Service.The Application Migration Service also checks if you have satisfied migration perquisites and identifies any issues that must be satisfied before beginning.4.In the left pane under Application Migration , click Sources .5.From the Compartment list, select a compartment in which you have permission to work.The page updates to display only the resources in that compartment.If you're not sure which compartment to use, contact an administrator.For more information, see Access Control .6.Click Create Source .Note: The Create Source option is also available in the workflow on the Overview page.7.Enter the following details, then click Create .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. |
The Application Migration Service also checks if you have satisfied migration perquisites and identifies any issues that must be satisfied before beginning.4.In the left pane under Application Migration , click Sources .5.From the Compartment list, select a compartment in which you have permission to work.The page updates to display only the resources in that compartment.If you're not sure which compartment to use, contact an administrator.For more information, see Access Control .6.Click Create Source .Note: The Create Source option is also available in the workflow on the Overview page.7.Enter the following details, then click Create .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. |
4.In the left pane under Application Migration , click Sources .5.From the Compartment list, select a compartment in which you have permission to work.The page updates to display only the resources in that compartment.If you're not sure which compartment to use, contact an administrator.For more information, see Access Control .6.Click Create Source .Note: The Create Source option is also available in the workflow on the Overview page.7.Enter the following details, then click Create .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 . |
5.From the Compartment list, select a compartment in which you have permission to work.The page updates to display only the resources in that compartment.If you're not sure which compartment to use, contact an administrator.For more information, see Access Control .6.Click Create Source .Note: The Create Source option is also available in the workflow on the Overview page.7.Enter the following details, then click Create .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. |
The page updates to display only the resources in that compartment.If you're not sure which compartment to use, contact an administrator.For more information, see Access Control .6.Click Create Source .Note: The Create Source option is also available in the workflow on the Overview page.7.Enter the following details, then click Create .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. |
If you're not sure which compartment to use, contact an administrator.For more information, see Access Control .6.Click Create Source .Note: The Create Source option is also available in the workflow on the Overview page.7.Enter the following details, then click Create .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. |
For more information, see Access Control .6.Click Create Source .Note: The Create Source option is also available in the workflow on the Overview page.7.Enter the following details, then click Create .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. |
6.Click Create Source .Note: The Create Source option is also available in the workflow on the Overview page.7.Enter the following details, then click Create .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. |
Note: The Create Source option is also available in the workflow on the Overview page.7.Enter the following details, then click Create .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. |
7.Enter the following details, then click Create .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 ). |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.