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 with the cost estimator tool.
• Optional features

  Some optional features increase your message consumption. See the following topics:

  • Extended Data Retention Message Consumption
  • Disaster Recovery Message Consumption
  • Additional Message Consumption for Optional Features
• Peak loads

  When you use the cost estimator tool, you'll enter your peak transaction volume and peak file load.

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.