Estimate Message Pack Usage for a Metered Tenancy

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.

1. Do you experience higher business transaction volumes at specific times of month or year?

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

   • If so, what's the maximum daily transaction volume you've seen during a surge? Divide your daily surge volume by 24. This is your Peak hourly transaction volume.
   • If not, move on to the next question.
2. Are your business transactions evenly distributed throughout the day?
   • If so, move on to the next question.
   • If not, during peak hours, how many transactions do you expect? This is your Peak hourly transaction volume.
3. How many business transactions flow through your systems 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.

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.

1. Do you exchange data using files or batch loads as part of your integrations?

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

   • If so, move on to the next question.
   • If not, you don't need to calculate a peak hourly file load.
2. What's the maximum size (in MB) of these files or batches?

   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.
3. Are these files or batches typically processed concurrently (or within the same hour)?

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

   • If so, approximately how many files or batches are processed concurrently? This is your Number of concurrent files.
   • If not, use 1 as your Number of concurrent files.

Based on your answers, calculate your peak file load, using the following formula:

Max file size x Number of concurrent files = Peak hourly file load

1. 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

2. 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

3. 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

4. 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