About Integrations Usage
When creating Oracle Integration instances, administrators specify the number of message packs they plan to use for per instance.
Rules for tracking Integration billed messages
Follow these rules to determine how message consumption is calculated.
Number | Rule | Description |
---|---|---|
1 |
Trigger |
Each trigger activity counts as at least one message, up to 50KB inbound. If the inbound message payload exceeds 50KB, 1 additional message is counted for each additional 50KB. |
2 |
Invoke |
Invoke requests don't count as messages, but invoke responses over 50KB count. If the message payload exceeds 50KB, 1 additional message is counted for each additional 50KB. |
3 |
File |
For file based scheduled flows where there are incoming files into integrations, each file is converted into a billed message (in multiples of 50KB) only when the size is greater than 50KB. |
4 |
Internal |
Internal calls within the same Oracle Integration instance aren't counted as messages. For example, the following aren't counted:
Calling another Oracle Integration instance does incur messages in the target Oracle Integration instance, and, depending on the response size, may also incur messages in the calling Oracle Integration instance. |
Integration Usage Examples
This table shows by example how message billing is calculated and the rules that apply.
Integration Type | Scenario/Flow | Billing Message Calculation | Rules That Apply |
---|---|---|---|
Sync/Async (Trigger) |
|
Payload size is considered at trigger. ceil(120/50) = 3 messages |
#1 (Trigger) |
Sync/Async (Trigger) |
|
Payload size is considered at trigger. Any subsequent response greater than 50KB is also tracked. In this scenario, only files greater than 50KB are considered. ceil(70/50) + ceil(170/50) = 2 +4 = 6 messages |
#1 (Trigger) #3 (File) |
Sync/Async (Trigger) |
|
Payload size is considered at trigger. Any subsequent response greater than 50KB is also tracked. ceil (20/50) = 1 message |
#1 (Trigger) |
Sync/Async (Trigger) |
|
Payload size is considered at trigger. Any subsequent response greater than 50KB is also tracked. ceil(10/50)+ ceil (70/50) + ceil(100/50) = 1+2+2 = 5 messages |
#1 (Trigger) #2 (Invoke) #3 (File) |
Sync/Async (Trigger) |
|
Payload size is considered at trigger. Any subsequent response greater than 50KB is also tracked. Since the trigger is just a GET request with no payload, it's considered 1 billed message. 1 message |
#1 (Trigger) |
Scheduled flow |
|
Each invoke/file is considered in multiples of 50KB when response data is more than 50KB. ceil(170/50) = 4 messages |
#3 (File) |
Scheduled flow |
|
Each invoke/file is considered in multiples of 50KB when response data is more than 50KB. Not counted. |
None |
Scheduled flow |
|
Each invoke/file is considered in multiples of 50KB when response data is more than 50KB. ceil(130/50) = 3 messages |
#3 (File) |
Scheduled flow |
|
Each invoke/file is considered in multiples of 50KB when response data is more than 50KB. ceil(100/50) = 2 messages |
#2 (Invoke) |
Scheduled flow |
|
Each invoke/file is considered in multiples of 50KB when response data is more than 50KB. Not counted. |
#4 (Internal) None counted |
Child Integration flow |
|
Integration child flow invoke is waived from metering. Not counted. Note that the parent may count. |
#4 (Internal) None counted |
Child Integration flow |
|
Integration child flow invokes are waived from metering. Any subsequent response is metered. Each child = ceil(70/50) = 2 messages Note that the parent may count. |
#2 (Invoke) |