#1113 - Extracting Billing Costs per Integration from OIC

Introduction

Here is a simple example, from which you can extrapolate - the basis is the following Project and it's integrations - 

validateOrder is only invoked via local invoke by the integrations - processOrderSync and processOrderAsync.

ProcessLargeOrderListSync - processes a file of 80KB.

Hourly Orders Run is a scheduled job that does essentially nothing, except WAIT for 10 seconds.

Let's run these integrations - 

Now to OCI Dashboards - 

As you can see, I have 2 widgets - OIC Integration Technical Message Count by Integration and Billable Messages by Integration

The former shows the number of "technical" messages / requests OIC received, while the latter shows the resulting billable messages. Both widgets are grouped by integration.

So why are there differences between the two? Let's investigate - 

The scheduled integration - Hourly_Orders_Run executed twice. However, all this flow does is WAIT for 10 seconds. It does not contain any invokes that retrieve data. If it did, only data > 50KB is counted, from a billing perspective. Ergo, no billable messages for this integration.

The integration, ProcessLargeOrdersListSync, has run twice. However, the input file of both occasions was 82KB, this results in 2 billable messages per flow.

ProcessOrder ran 5 times and generated 5 billable messages. 

ProcessOrderAsync ran 3 times and generated 3 billable messages. 

The integration, ValidateOrder, ran 8 times, but all of these were via local invoke from ProcessOrder and ProcessOrderAsync. Ergo, these are not billed.

Behind each widget lies a query, based on OCI service metrics.

For the "Technical" messages widget - 

MessagesReceivedCount[1h]

{resourceId=$(params.oic-env)}.grouping(FlowCode).sum()

For the "Billable" messages widget - 

BilledMessageCount[1h]

{resourceId=$(params.oic-env)}.

grouping(IntegrationFlowIdentifier).sum()

This Dashboard was created in OCI Log Analytics and includes the following filters - 

So how did I add the filters? I simply duplicated one of the OOTB Integration dashboards, delivered with OCI Log Analytics -

The OOTB dashboards are those created by Oracle - 

Open the Health Overview dashboard - 

Click on the Actions dropdown and select Duplicate - 

Give it a name -

Open the Dashboard - 

Click Edit and delete all the existing widgets in the dashboard -

All gone! - 

Now create a new query based widget - Action - Edit - 

Copy and paste the "technical" query - 

Note the $(params.oic-env)} - this is the link to the OIC resource id in the filter. We need to add this parameter to this widget - 

The default Visualisation is Table, let's change this - 

Amend as follows - 

This results in -

Do the same for the "Billing" widget.

A very nice feature is the ability to export to CSV - 

 

  
 

 

#1112 - OIC 26.01 New Features

Introduction

Firstly, a Very Happy New Year! May it bring us all an abundance of happiness & health, wisdom & wealth.

Here are some of the compelling new features coming with this release. So let's get going!

AI Related Features

Before commencing, please check out the quick Recap of what we achieved in 2025. Net, net, support for - 

• turbocharging OIC development with AI Assistant
• exposing OIC artifacts as AI Agent Tools via OIC Project MCP Server
• creating AI Agents in OIC Projects
• enabling Human-in-the-Loop (HITL) for Agent governance

CY26 will continue on this trajectory, producing lots of cool functionality in this space.

26.01 - Disable/Enable AI Assistant

Now I disable the assistant - 

No AI Assistant in the canvas.

Create B2B Trading Partner based on Natural Language

Let's try this out with the following input - - This TP profile sends X12 4010 850 via AS2 protocol.

- Application Partner ID for the TP is AI_TP

- AS2 Identifier is AI_TP_AS2

- Here is the ISA and GS segment from an X12 850 that was sent to OIC by the TP. Create B2B identifiers from this sample. 

ISA*00*00*01*AI_TP*01*MyCompany*241112*1245*U*00401*000000015*0*P~

GS*PO*AI_TP*MyCompany*19960807*1548*000001*X*004010~

Here's the result - 

This is exceedingly useful, especially when you have to create multiple trading partners. You can use the input as a template, then amend as necessary, for each new Trading Partner.

Create Integrations, based on those in the Integration Store

This is about jump starting your integration implementation journey. You describe your business use case in natural language and we identify potential integrations that could fulfill your requirements. These integrations could be part of a larger recipe / accelerator, however, only the relevant integration is imported into your project.

I click Start with a prebuilt integration -

I click Choose - 

I click Finish - 

AI Agents included in Project Deployments

With 26.01, we now include project lifecycle (Export/Import/Create deploy artifact) support for AI Agents & Agent artifacts.

Support for follow-up Agent Conversations

Follow up agent conversations are now supported through the use of a conversation id.

OIC File Server

Runtime Audit

File Server logging (Runtime Audit) is now available with the 26.01 release - 

Here's an extract from the downloaded audit file - 

This audits actions such as -

• Connect
• Disconnect
• Download Files
• Upload Files
• Change Directory
• Rename Files
• Create Folders
• Delete Folders
• Rename Folders
• etc.

OIC Observability

New Metrics in OCI Monitoring for OIC

The first new widget gives you visibility into the async queue (Metric AsyncInboundRequestsDepth) -

The next widget allows one to monitor OIC File Server connections -

We also get visibility into Scheduled Jobs (Metric SchedulerTriggeredInstancesCount) -

Directly push OIC Activity Stream logs to OCI Log Analytics

With the 26.01 release, one can now simply check a box, in the OCI Console for your OIC instance, to enable the direct push of OIC activity Stream log data to OCI Log Analytics. This makes it even easier for you to use OCI Log Analytics for OIC fleet management.  

Connectivity

As with every release, 26.01 ushers in new adapters and enhancements to existing adapters.

New Adapters

• Netsuite REST Adapter
• Google Sheets Adapter

The Google Sheets adapter is from our prime partner, Bristlecone, and it is available from the Integration Store -

Enhancements to existing Adapters

• ATP Adapter - AI vector search enabled, allowing intent-based data retrieval.

These are just some of the highlights; you can check out the detailed Connectivity Post for 26.01 here.