A list of alternate custom endpoints to be used for the integration instance URL (contact Oracle for alternateCustomEndpoints availability for a specific instance).
Compartment Identifier.
Optional parameter specifying which entitlement to use for billing purposes. Only required if the account possesses more than one entitlement.
Usage of predefined tag keys. These predefined keys are scoped to namespaces. Example: {@code {"foo-namespace": {"bar-key": "value"}}}
Integration Instance Identifier.
The OCID of the identity domain, that will be used to determine the corresponding Idcs Stripe and create an Idcs application within the stripe. This parameter is mutually exclusive with parameter: idcsAt, i.e only one of two parameters should be specified.
Simple key-value pair that is applied without any predefined name, type or scope. Exists for cross-compatibility only. Example: {@code {"bar-key": "value"}}
IDCS Authentication token. This is required for all realms with IDCS. Its optional as its not required for non IDCS realms.
Standard or Enterprise type, Oracle Integration Generation 2 uses ENTERPRISE and STANDARD, Oracle Integration 3 uses ENTERPRISEX and STANDARDX
Bring your own license.
The file server is enabled or not.
Visual Builder is enabled or not.
The number of configured message packs Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
Shape
The information about new IntegrationInstance. Some properties may not be applicable to specific integration types, see Differences in Instance Management for details.