Introduction 

Oracle Integration Cloud (OIC) licensing is based on message pack consumption. Understanding how messages are billed is important because integration design choices such as payload size, trigger type, file processing, and API responses directly affect message usage and therefore licensing cost. 

This document explains how message packs are consumed in OIC, the key billing rules that developers and architects must consider, real-world usage scenarios, and practical steps to optimize message consumption. 

What Is a Message Pack in OIC? 

A message pack represents a predefined number of messages processed by an Oracle Integration Cloud instance. 

Consumption Models 

• BYOL (Bring Your Own License): 1 pack = 20,000 messages per hour. 
• Non-BYOL: 1 pack = 5.000 messages per hour. 
• OIC for SaaS: 1 pack = 1 million messages per month. 
• Each message is calculated in increments of 50 KB of payload size.

Core Rules That Impact Message Consumption 

1. Trigger Rule 

Every inbound trigger is billed. Payload size is rounded up in blocks of 50 KB. 

Examples: 

• 30 KB payload → 1 message 
• 70 KB payload → 2 messages 
• 120 KB payload → 3 messages 
• Trigger payload size is often the most important factor affecting OIC licensing cost. 

2. Invoke Rule 

• Invoke request messages are not billed. 
• Invoke responses are billed only if the response size exceeds 50 KB. 
• Large responses from REST APIs, SOAP services, BIP reports, or SaaS APIs can increase message consumption. 

3. File Server Rule 

• This rule applies mainly to scheduled integrations that download or process files. 
• Files larger than 50 KB are billed based on the formula: ceil(file_size / 50 KB). 
• Example: 170 KB file → ceil(170 / 50) = 4 messages. 

4. Internal Calls Rule 

Calls within the same OIC instance are not billed. Examples include Integration-to-Integration calls, Process Automation calls to integrations, and Visual Builder calls within the same environment. 

If one OIC instance calls another OIC instance, billing may occur on both sides depending on the response payload size.

Real-World Use Cases and Message Consumption 

Use Case 1: REST Inbound → SaaS Update 

• REST inbound payload: 40 KB 
• SaaS invoke response: 20 KB 
• Consumption: Trigger = 1 message, response not counted. Total = 1 message. 

Use Case 2: Large REST Inbound Payload 

• REST inbound payload: 120 KB 
• Consumption: ceil(120/50) = 3 messages. 

Use Case 3: File-Based Scheduled Integration 

• Scheduled job downloads files: 20 KB, 40 KB, and 170 KB. 
• Only the file larger than 50 KB is counted. 
• Consumption: ceil(170/50) = 4 messages. 

Use Case 4: Database Adapter with Loop Invokes 

• Database query returns 2 rows totaling 20 KB. 
• REST invoke response per row: 20 KB. 
• Consumption: Trigger = 1 message; responses not billed. Total = 1 message. 

Use Case 5: SOAP Trigger with File Downloads 

• SOAP inbound payload: 70 KB. 
• Files downloaded: 20 KB, 170 KB, 40 KB. 
• Consumption: Trigger = 2 messages, large file = 4 messages. Total = 6 messages. 

Best Practices to Optimise Message Consumption 

1. Minimize Trigger Payload Size 

Remove unnecessary fields and use lightweight payload formats such as JSON. 

2. Control Invoke Response Size 

Use APIs that return only required fields and apply pagination when retrieving large datasets. 

3. Handle Large Files Efficiently 

Split large files, process only delta files, and avoid downloading unnecessary data. 

4. Prefer Internal OIC Calls 

Reuse integrations within the same OIC instance to avoid unnecessary billing. 

5. Use Scheduled Integrations Carefully 

Avoid unnecessary polling and schedule integrations only when required. 

6. Monitor Usage Regularly 

Track billable messages using OIC usage metrics to identify spikes caused by large payloads.

Business Benefits of Understanding Message Pack Consumption in Oracle Integration Cloud (OIC)

1. Cost Optimization:

Gain visibility into message usage patterns to avoid unnecessary consumption and control subscription costs.

2. Improved Resource Planning:

Monitor integration workloads effectively and forecast future capacity requirements with greater accuracy.

3. Enhanced Performance:

Identify high-volume integrations and optimize processing to ensure reliable and efficient system performance.

4. Proactive Governance:

Establish monitoring and usage controls to prevent unexpected message pack overages and maintain compliance.

5. Better Scalability:

Design integrations that support business growth while keeping message consumption under control.

6. Increased Operational Visibility:

Access detailed insights into message traffic, helping IT teams make informed optimisation decisions.

7. Efficient Integration Design

Detect inefficient integration patterns and implement best practices to reduce processing overhead.

8. Maximized ROI:

Ensure Oracle Integration Cloud resources are utilized effectively, helping organizations derive greater value from their OIC investment.

Conclusion 

Understanding message pack consumption is essential for organizations looking to maximize the value of their Oracle Integration Cloud investment. By gaining visibility into how messages are processed and consumed across integrations, businesses can optimize performance, control costs, and plan for future scalability more effectively. Regular monitoring and analysis of message usage not only improve operational efficiency but also help ensure that integration environments remain aligned with evolving business requirements. 

Optimise OIC Performance While Reducing Integration Costs

Effective message pack management is key to maintaining a scalable, cost-efficient Oracle Integration Cloud environment. By understanding consumption patterns and optimising integration workloads, organisations can improve performance while maximising their OIC investment.

At Kovaion, our Oracle Integration experts help businesses design, optimize, and govern OIC environments to achieve greater efficiency, visibility, and scalability. Whether you’re looking to monitor message consumption, streamline integrations, or enhance overall platform performance, we can help you unlock the full potential of Oracle Integration Cloud.

Looking to optimise message consumption and maximise your Oracle Integration Cloud investment? Contact Kovaion to get started.