Create an Oracle Integration instance in a selected compartment.

1. After signing in to the Oracle Cloud Infrastructure Console, note your selected region.

   For information about regions, see Regions and Availability Domains.

   
   

   
   

   
   
2. Open the navigation menu and click Developer Services. Under Application Integration, click Integration.
3. From the Compartment list, click through the hierarchy of compartments and select the one in which to create the instance. You may need to expand the + icon to find the compartment to use. Compartments can contain other compartments. It may take several minutes for the new compartment to appear after the policy has been created.
   
   
   
   
   Note
   
   

   Do not create your instance in the root or ManagedCompartmentForPaaS compartment.

   The page is refreshed to show any existing instances in that compartment.

4. Click Create.
5. Enter the following details:

   Field	Description
   Name	Enter a name for this instance. The name becomes part of the URL for accessing the instance.
   Version	Select the version you want to use for this instance: Oracle Integration 3 is the latest generation of Oracle Integration, providing the latest features and infrastructure technology including Integrations, Process Automation, robotic process automation, healthcare, Visual Builder, B2B for Oracle Integration, File Server, and our portfolio of adapters. Oracle Integration Generation 2 is the full-featured premier service, providing features and infrastructure technology including Integrations, Processes, Integration Insight, Visual Builder, B2B for Oracle Integration, File Server, and our portfolio of adapters. If you choose to create an Oracle Integration Generation 2 instance, see Provisioning and Administering Oracle Integration Generation 2. Note: This field appears only if you can provision both Oracle Integration Generation 2 and Oracle Integration 3 instances. Everyone can provision an Oracle Integration 3 instance. You can create a new Oracle Integration Generation 2 instance only if you have an existing Oracle Integration Generation 2 instance in the region.
   Consumption model	Typically, only one consumption model is displayed, but if multiple consumption models are available in your tenancy, select the one you want to use for this instance: Metered (universal credit) Note: The Healthcare edition is available only in tenancies that use Universal Credits. Subscription (OIC4SaaS) Oracle Integration Government
   Edition	Select the edition you want to use for this instance: Standard: Includes integrations, standard adapters, recipes and accelerators, Visual Builder, and File Server. Enterprise: Includes all the features of Standard edition, plus additional technologies and services, including enterprise adapters, and enables you to design, automate, and manage your business processes in the cloud with Process Automation, perform UI-based automation with robots using robotic process automation, and support business-to-business communications using B2B for Oracle Integration. Healthcare: Includes all the features of Enterprise edition, plus additional technologies for Health Level 7 (HL7), including an MLLP adapter, a FHIR adapter, and healthcare action. Note: The Healthcare edition is available only in tenancies that use Universal Credits. See Oracle Integration Editions to see what's licensed in each edition.
   Shape	Select a shape for this instance. The shape determines when the instance receives updates, which happen every other month. Development: Instances with this shape receive updates two weeks before instances with a Production shape. Production: Instances with this shape receive updates two weeks after instances with a Development shape. Only some regions allow you to choose a shape. If you don't see the option to choose a shape, your instance is created in the Production shape. For details about the shapes that each region supports, see Availability. Note: You can't change the shape after you create the instance. However, you can move data to another instance using the export and import features.
   License type	Select a license type for this instance. Subscribe to a new Oracle Integration license: Select this option if you want to purchase a new license. With this option, each message pack includes 5,000 messages per hour. Existing Oracle Fusion Middleware license (BYOL): Select this option if you want to use your existing license. With this option, each message pack includes 20,000 messages per hour. (This option isn't available for the Healthcare edition.) Note: This field appears only if you are provisioning an Oracle Integration instance. It doesn't apply to Oracle Integration for SaaS.
   Message packs	Message pack options are based on the type of Oracle Integration license you have. For Oracle Integration: If you created a new Oracle Integration license in the cloud: Each message pack includes 5,000 messages per hour. You can select up to 12 message packs in the user interface. If you brought an existing Oracle Fusion Middleware license to the cloud (BYOL): Each message pack includes 20,000 messages per hour. You can select up to 3 message packs in the user interface. For Oracle Integration for SaaS: Each message pack includes one million messages per month. Note that usage is tracked on a monthly basis instead of hourly, which keeps costs predictable even when you have unpredictable hourly volumes. You can select up to 43 message packs in the user interface. Note: You are responsible for billing based on the number of message packs you select. Select enough message packs to adequately handle your instance's activity. See About Integrations Usage. The number of message packs you subscribe to can also affect the processing time of synchronous requests. See Message Pack Usage and Synchronous Requests. You can also specify the number of message packs using the command line option. This enables you to specify larger values than permitted by the user interface. See Override the Message Pack Limit Using the Command Line.
   Access token	If this field is displayed, you are creating an instance as a non-federated user. Sign in as a federated user and restart creating an instance.
   Show advanced options	Identity domain: (Available only if you are provisioning an Oracle Integration 3 instance that uses identity domains. See Differences Between Tenancies With and Without Identity Domains.) Configure this tab to associate this instance with a secondary identity domain—an identity domain other than the one you're signed into. This allows you to manage all your instances in your tenancy from one domain, rather than having to sign into each domain to manage the associated instances. Change compartment: The compartment you select here is the one that includes the secondary identity domain, not the one in which the instance will be created. The instance will be created in the compartment you selected in step 3. Domain: Select the secondary identity domain you want to associate with this instance. Note: You must have read permission for the secondary identity domain. If you don't, the secondary identity domain administrator needs to add an IAM policy such as the following: Allow group primary_identity_domain/group_name to read domains in compartment secondary_identity_domain_compartment See Managing Policies and Details for IAM with Identity Domains. If you configure a secondary identity domain, Oracle Integration creates an Oracle Identity Cloud Service (IDCS) application in the secondary identity domain when it provisions your Oracle Integration 3 instance. If you don't configure a secondary identity domain, the IDCS application is created in the primary identity domain—the one you're signed into. After the Oracle Integration 3 instance has been created in the secondary identity domain, you need to assign administrators the ServiceAdministrator role in the IDCS application that was created. See Assign Oracle Integration Roles to Groups in an Identity Domain. Network access: Configure an allowlist for your instance. See Configure an Allowlist for Your Instance. Tags: Enter a key and optional value. Tags enable you to track resources within your tenancy. See Resource Tags. Note: If you want to configure a custom endpoint URL for this instance, you do so after the instance is created. See Configure a Custom Endpoint for an Instance.

6. Click Create.
   Instance creation typically takes just a few minutes. If you attempt to click the instance name and receive a 401: Authorization failed or a 404: Not Found error, but followed all the correct steps, instance creation has not completed. Wait a minute and try again.
7. When instance creation completes successfully, the instance shows as Active in the State column.
   Once created, an instance is visible only in the region in which it was created.