Monitoring Billable Messages

As an administrator, you can monitor the number of billable messages consumed in a selected Oracle Integration or Oracle Integration for SaaS instance.

Oracle Integration consumption models

The type of license you choose determines how message packs are defined and metered. The Usage Metrics page is different for Oracle Integration versus Oracle Integration for SaaS.

  • For Oracle Integration:
    • BYOL: For Bring Your Own License users, one message pack is defined as 20,000 messages per hour. You can select up to 3 message packs if you bring an existing Oracle Fusion Middleware license to the cloud.

    • Non-BYOL: For these license types, one message pack is defined as 5,000 messages per hour. You can select up to 12 message packs if you create a new Oracle Integration license in the cloud.

  • For Oracle Integration for SaaS, usage is tracked on a monthly basis in packs of one million messages per month, which keeps costs predictable even when you have unpredictable hourly volumes. Usage is reported monthly instead of hourly. You can select up to 43 message packs.

Oracle Integration features included

Usage metrics cover these features:

  • Integration

    For information on how Integration billable messages are calculated, see About Integrations Usage.

  • Process

    For information on how Process billable messages are calculated, see About Process Usage.

  • Integration Insight

    Each business transaction in Integration Insight counts as one message.

Note:

The billable messages shown in the chart do not include Visual Builder usage metrics.

Viewing usage metrics

  1. On the Home page, select Monitoring in the navigation pane, then Usage Metrics.
    The Usage Metrics page is displayed.

    Note:

    Data metrics are displayed using UTC standard time.

    • For Oracle Integration
      The Usage Metrics page shows the total messages used during each hour of a selected day. In the example illustration below, the blue Configured 5K line shows that the Oracle Integration instance was configured for 5,000 messages per hour during provisioning. Values below the configured usage are shown in light pink and values above it are shown in dark pink.
      • To view messages consumed on a different date, select a date using the View calendar.

      • Hover the cursor over an hour time period to view its approximate message consumption.

      • Click Summary by Hour icon in the upper right of the screen to expand a table that lists each hour and its billable messages for the selected day.



    • For Oracle Integration for SaaS
      The Usage Metrics page for SaaS shows the total messages used during each month. In the example illustration below, the blue Configured 5M line shows that the Oracle Integration for SaaS instance was configured for 5 million messages per month during provisioning. Values below the configured usage are shown in light pink and values above it are shown in dark pink.
      • To view messages consumed during a different timeframe, select another timeframe using the View calendar.

      • Hover the cursor over a month time period to view its approximate message consumption.

      • Click Summary by Month icon in the upper right of the screen to expand a table that lists each month and its billable messages.

  2. Export usage metrics to a CSV file, if needed.
    1. Click Export.
    2. In the Export Usage Metrics dialog, select a start date and end date and click Export.
      Each hour is depicted as a record. A maximum of 1000 hours of information (shown as lines in the CSV file) can be exported.
    3. Use your browser's download list to access the CSV file.
    The exported file shows columns for the date, configured messages, and total messages consumed.
    Shows columns for the date, configured messages, and total messages consumed

  3. If needed, change the Oracle Integration instance's configured message packs. See Editing the Edition, License Type, and Message Packs of an Instance.

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:

  • Process to Integration

  • Visual Builder to Integration

  • Integration to Integration

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)

  1. Eloqua inbound with 40KB payload.

  2. Data transformation.

  3. External invoke to push data to Sales Cloud.

Payload size is considered at trigger.

ceil(40/50) = 1 message

#1 (Trigger)

Sync/Async (Trigger)

  1. REST inbound with 120KB payload.

  2. Data transformation.

  3. External invoke to push data to Logfire.

Payload size is considered at trigger.

ceil(120/50) = 3 messages

#1 (Trigger)

Sync/Async (Trigger)

  1. SOAP inbound with 70KB payload.

  2. Download files in a loop.

  3. 3 files downloaded of sizes 20KB, 170KB, and 40KB, respectively.

  4. Data transformation/enrichment.

  5. External invoke to push data to an external system via REST.

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)

  1. Database adapter pulling in 20KB data and 2 rows.

  2. For each row, 1 outbound REST invoke is made, which results in 20KB data for each invoke.

  3. Data enrichment/transformation.

  4. FTP to an external location.

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)

  1. SOAP inbound with 10KB payload.

  2. Download files in a loop. Two files downloaded of sizes 20KB and 70KB, respectively.

  3. External invoke to get further data via REST adapter. Returns 100KB data.

  4. FTP to an external location.

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)

  1. Simple REST GET request with template parameters without payload.

  2. Call to Oracle Service Cloud to get contact details. Returns a response of 40KB.

  3. Return the contact data.

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

  1. Scheduled trigger.
  2. Download files in a loop. Three files downloaded of sizes 20KB, 170KB, and 40KB, respectively.
  3. Data transformation.

  4. External invoke to transfer data which results in 10 bytes of response.

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

  1. Scheduled trigger.
  2. Database adapter pulling in 30KB data and 10 rows.
  3. Data transformation.

  4. External invoke to transfer data which results in 5 bytes of response.

Each invoke/file is considered in multiples of 50KB when response data is more than 50KB.

Not counted.

None

Scheduled flow

  1. Scheduled trigger.
  2. External SOAP invoke to get data via BIP reports. Returns 130KB data.
  3. External invoke to get further data via REST adapter. Returns 10KB data.

  4. Data transformation.
  5. External invoke to transfer data which results in 5 bytes of response.

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

  1. Scheduled trigger.
  2. Download files in a loop. Two files downloaded of sizes 20KB and 40KB, respectively.
  3. External invoke to get further data via REST adapter. Returns 100KB data.

  4. FTP to an external location.

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

  1. Scheduled trigger.
  2. External invoke to get data via REST adapter. Returns 10KB data.
  3. Data transformation.

  4. External REST invoke to transfer data which results in 500 bytes of response.

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

  1. A parent Integration flow calls a child Integration flow via REST in a loop.
  2. The child Integration flow sends a notification email with the information passed from a parent flow.
  3. Child flow execution completes.

Integration child flow invoke is waived from metering.

Not counted. Note that the parent may count.

#4 (Internal)

None counted

Child Integration flow

  1. Parent Integration flow downloads a CSV file via the FTP adapter. The CSV contains 5 rows.
  2. Each row in the CSV file calls a child Integration child flow.
    1. The child Integration flow reads a orderid passed as an input.

    2. Invokes a request to Oracle Service Cloud to get data about the order. Each invoke returns 70KB data.

    3. Data transformation in child flow.

    4. Pushes the data via an FTP adapter to write it to a file.

    5. Child execution completes.

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)

Pub/Sub Flows

  1. Single publisher flow with REST trigger as 30 KB payload.
  2. Single subscriber to the above which processes data and sends it to an external service.

Pub counts as 1 message.

Sub is waived on trigger.

#1 (Trigger)

Pub/Sub Flows

  1. Single publisher flow with REST trigger as 30KB payload.
  2. Single subscriber to the above which processes data.
  3. Sub flow calls OSC to get a response back as 70KB.
  4. Sub flow completes.

Pub counts as 1 message.

Sub trigger is waived. However, the invoke is metered when the response is greater than 50KB. So the sub flow in this case counts as 2 messages.

#1 (Trigger)

#2 (Invoke)

About Process Usage

When creating Oracle Integration instances, administrators specify the number of message packs they plan to use for per instance.

Process message metering

Process metering tracks the number of concurrent, unique users interacting within a 1 hour interval. Sizing is based on concurrent users, which are converted to message packs. One Process user/hour is equivalent to 400 messages/hour.

  • If you have 1,000 messages per hour and 10 distinct users, these would count as 1,000 integration messages + (400)*10 users = 5,000, so 1 message pack of 5,000 messages per hour.

  • Another way to visualize Process sizing: 5,000 message packs per hour equate to 12.5 distinct concurrent users performing tasks.

What's counted?

A logged in user is counted for a minimum of one hour when performing any write operations that update a task or process instance, which includes:

  • Updating or processing tasks (approve/reject a task, add an attachment/comment, re-assign, or request for information)
  • Creating process instances

Within each hour of use, a distinct user can perform an unlimited number of write operations.

Oracle Integration has a 1 message pack minimum charge per hour to keep the system available, even with no usage. Note that you can turn off your Oracle Integration instance for billing purposes, but no instances are processed while the instance is stopped.

What's NOT counted?

This count doesn’t include:

  • Logged in users performing read-only only (query or read) operations.
  • Integrations triggered from the process (integrations are waived).

Process Usage Examples

This table shows by example how message billing is calculated and the rules that apply.

Scenario Type Scenario Billing Message Calculation

Process Workspace

Between 9am and 10am, 20 employees access Workspace. Within the one hour timeframe:

  • 5 users (user1 through user5) create a total of 100 new process instances.

  • 10 other users (user6 through user15) process different tasks created by user1 through user5, and complete them.

  • The remaining 5 users (user16 through user20) only check the task and process instance status, but do not perform any update/write operations.

The 9am-10 am hour block reports 15 concurrent users (5 created new instances and 10 processed tasks).

Process Workspace and mobile app

Between 10 and 11am, 10 users access Workspace and 5 access the Oracle Process Mobile app. Within the one hour timeframe:

  • 10 users (user1 through user10) create new process instances and also approve at least 1 task total.

  • 5 users (user11 through user15) log into the mobile app: 3 of them create new instances, and the other 2 perform only read-only operations.

The 10am-11am hour block reports 13 concurrent users (10 workspace users plus 3 mobile users performed update/write operations, while 2 mobile users did not perform any update/write operations).

Process Workspace and Visual Builder

Between 11am and 12pm, 5 users access Oracle Integration from a Visual Builder application and 5 other users access Workspace.

  • 2 of the 5 Visual Builder users access Visual Builder, and interact with a Visual Builder app that in turn triggers execution of an API that creates new process instances and processes tasks.

  • The other 3 Visual Builder users access the Visual Builder app and read and access task and process instance status.

  • The 5 users access Workspace and approve a minimum of 1 task each within the hour timeframe.

The 11am-12pm hour block reports 7 concurrent users (2 Visual Builder users and 5 Workspace users performed update/write operations). This result does not include the Visual Builder concurrent user licenses. Visual Builder concurrent users are metered separately.