Estimate Message Pack Usage for a Metered Tenancy

Use the following information to help estimate how many message packs your Oracle Integration instance will use. By correctly sizing your instance based on peak loads, you ensure smooth, scalable, and resilient day-to-day operations for both your real-time transactions and your scheduled batch processing.

Message pack estimation varies based on several factors:

  • Consumption model

    This topic applies to tenancies that use the metered (universal credit) model.

  • License type
    • If you created a new Oracle Integration license in the cloud, each message pack includes 5,000 billing messages per hour.
    • If you brought an existing Oracle Fusion Middleware license to the cloud (BYOL), each message pack includes 20,000 billing messages per hour.
  • Instance shape
    • For a development shape (non-production instance), you typically need only one message pack.
    • For a production shape, estimate your message pack usage based on the calculations in this topic.
  • Optional features

    Some optional features increase your message consumption. These options aren't included in the calculations in this topic. See the following topics:

  • Peak loads

    Use the calculations in this topic to help you estimate your peak loads.

The number of message packs you subscribe to can also affect the processing time of synchronous requests. See Message Pack Usage and Synchronous/Asynchronous Requests.

To understand how billing message usage is calculated for different features, see How Features Impact Billing Messages.

Use the Cost Estimator Tool to Determine Your Monthly Bill

Oracle provides a cost estimator tool to help you determine your monthly usage and bill for Oracle Integration.

  1. Go to the cost estimator tool.
  2. From the Select category list, choose Integration.
  3. On the Application Integration card, click Load.

    The Services, Compute shapes, Reference architectures, My favorites, and Advanced Search tabs are shown. The Services tab is selected. The Select category list shows Integration selected. A Search field appears to the right. Below this are boxes named API Management and Application Integration. Both boxes include a Load button.

  4. Select the License Edition for your instance. See Oracle Integration Editions.
  5. Select the License Type for your instance. See License Types.
  6. Enter information about your transaction volume.

    It's critical to understand when peak transaction volumes occur—whether during month-end, quarter-end, or seasonal events. These spikes might last an hour or span several days. Identifying such patterns helps you accurately estimate message volumes.

    Consider the question in the first column, then complete the steps listed in the second column based on your answer to the question.

    Question and details Next steps

    Does your business transaction volume increase at specific times of month or year?

    For example, payroll runs, month-end processing, Black Friday, open enrollment, flash sales

    Yes

    Select Peak seasonal/event-based volume, and enter your Peak daily volume during surge events.

    Make sure to enter the peak daily volume.

    Move on to the next question.

    No

    Clear the Peak seasonal/event-based volume box.

    Move on to the next question.

    Are your transactions evenly distributed throughout the day?

    Examples of transactions are orders, invoices, employee updates, patient records, real-time chat

    Yes

    Select Transactions distributed throughout the day, and enter your Daily business transactions.

    Make sure to enter the daily volume.

    Move on to the next step.

    No

    Clear the Transactions distributed throughout the day box, and enter your Peak hour transaction rate (normal days).

    Make sure to enter the peak hourly volume.

    Move on to the next step.
  7. Enter information about your file load:

    It's also important to understand the frequency, size, and timing of any batch processes you run—such as daily file uploads, scheduled data syncs, or end-of-day processing. This number helps you accurately assess overall message volume and ensure your environment is sized appropriately to handle both real-time and scheduled workloads efficiently.

    Consider the question in the first column, then complete the steps listed in the second column based on your answer to the question.

    Question and details Next steps

    Do your integrations perform any batch file processing?

    For example, CSV files for payroll, XML for purchase orders, JSON exports for analytics, PDF invoices

    Yes

    Select File-based or batch processing involved?, and enter your Max file/batch size (MB).

    For example, “Our largest batch is an employee master file at 150 MB.”

    Move on to the next question.

    No

    You don't need to calculate file load. Skip the remaining questions in this table, and move on to the next step.

    Are these batch files processed concurrently (within the same hour)?

    For example, “During payroll week, we process 5 large XML files within a 30-minute window.”

    Yes

    Select Files processed concurrently within same hour, and enter the number of Files processed concurrently.

    Move on to the next step.

    No

    Clear the Files processed concurrently within same hour box.

    Move on to the next step.
  8. If you have enabled disaster recovery for your instance, select Disaster Recovery.
The number of message packs you should subscribe to for your instance is automatically calculated and shown in the Message Packs box.

If you selected disaster recovery, you'll also see a Message Packs for DR box. You don't need to subscribe to these extra message packs, they will automatically by charged to your account.

Your Estimated Monthly Cost is shown in the upper right corner of the cost calculator.

Calculate Peak Loads and Message Pack Usage

If you don't want to use the cost estimator tool, and you'd prefer to manually calculate the number of message packs you'll need for your Oracle Integration instance, use the calculations in this section.

Estimate your peak hourly transaction volume

It's critical to understand when peak transaction volumes occur—whether during month-end, quarter-end, or seasonal events. These spikes might last an hour or span several days. Identifying such patterns helps you accurately estimate message volumes.

This decision tree walks you through how to estimate your peak hourly transaction volume. The same information is presented in the table below this image.

Question path and details Next steps

Does your business transaction volume increase at specific times of month or year?

For example, payroll runs, month-end processing, Black Friday, open enrollment, flash sales

Yes

What's the maximum daily transaction volume during a surge?

Divide your daily surge volume by 24.

This is your Peak hourly transaction volume.

No

Move on to the next question.

Are your transactions evenly distributed throughout the day?

Yes

Move on to the next question.

No

During peak hours, how many transactions do you expect?

This is your Peak hourly transaction volume.

How many transactions do your systems process daily?

For example, orders, invoices, employee updates, patient records, real-time chat

Divide your daily business transactions by 24.

This is your Peak hourly transaction volume.

Estimate your peak hourly file load

It's also important to understand the frequency, size, and timing of any batch processes you run—such as daily file uploads, scheduled data syncs, or end-of-day processing. This number helps you accurately assess overall message volume and ensure your environment is sized appropriately to handle both real-time and scheduled workloads efficiently.

This decision tree walks you through how to estimate your peak hourly file load. The same information is presented in the table below this image.

Question path and details Next steps

Do your integrations perform any batch file processing?

For example, CSV files for payroll, XML for purchase orders, JSON exports for analytics, PDF invoices

Yes

Move on to the next question.

No

You don't need to calculate a peak hourly file load.

What's the maximum size (in MB) of these batch files?

For example, “Our largest batch is an employee master file at 150 MB.”

This is your Max file size.

Move on to the next question.

Are these batch files processed concurrently (within the same hour)?

For example, “During payroll week, we process 5 large XML files within a 30-minute window.”

Yes

How many batch files are processed concurrently?

This is your Number of concurrent files.

Move on to the next question.

No

Use 1 as your Number of concurrent files.

Move on to the next question.

Based on your answers, calculate your peak file load

Multiply your Max file size by your Number of concurrent files.

This is your Peak hourly file load.

Calculate how many message packs you need

Now that you know your peak hourly transaction volume and your peak hourly file load, you can calculate how many message packs you need for your Oracle Integration instance using the steps in the following table.

What to calculate Formula

Calculate your peak hourly file load in KB, rounded up to a whole number.

Peak hourly file load x 1024 = Peak hourly file load in KB

Calculate the number of messages used for your peak hourly file load, rounded up to a whole number. One message is used for each 50 KB.

Peak hourly file load in KB / 50 = Number of messages used for peak hourly file load

Calculate the number of total messages used for your peak hourly file load and peak hourly transaction volume, rounded up to a whole number.

Number of messages used for peak hourly file load + Peak hourly transaction volume = Number of messages used

Calculate the number of message packs needed to accommodate the number of messages used, rounded up to a whole number. As noted above, the number of messages included in a message pack is based on the type of Oracle Integration license you select.

Number of messages used / Messages per message pack = Number of message packs to subscribe to