#1017 OIC 24.06 Release New Features

The mid-summer release of OIC3 has a lot in it. So, without further ado, let's begin.

For me, the most compelling feature is the design time dependencies viewer we get in Projects.

DesignTime Dependencies

Note the new icon on the Projects page -

I have a couple of artefacts in this project, so let's view the dependencies - 

Note the filters available -

Clicking on Integrations, I see the following - 

I now click on the integration, AA-Subscribe2NewSR -

Clicking on Events - 

You get the idea!

Clicking on Connections, I see the following. As you can see, the REST connection, BB-REST-Trigger, is not being used. 

Net, net, very enlightening, even for this small project.

Observability

View activity stream by duration - 

Note the support now for rollups.

OIC Projects support for Events

As you have seen above, Pub/Sub support is now available within the context of a project.

OIC Projects - simplifying Deployment creation

With 24.06, we have improved the UI for creating deployments.

Service Limits Increase

Activated Integration limit increased from 700 to 800.

Active Integration Count by Projects

Debug Tracing reset after 24 hours

Setting trace to debug causes all actions and payloads to be logged. This is an expensive operation. Therefore, starting with 24.06, the trace level is reset from Debug to Production after 24 hours.

You can set the trace level to Audit, if they need to capture inbound payloads, etc.

B2B Export Design time Artefacts

OIC Logging

there are new fields in the OIC activity stream as well as new fields pushed to OCI Logging.

OIC activity stream

I run the integration and download the activity stream from OIC.

Note the net new field, billedMsgUnits. Also note the 2 replay fields - replayableFrom and replayableContent. The latter 2 are there because I checked Allow to run again.

I run the integration flow again - 

and check out the activity stream - 

Activity Stream in OCI Logging

There is a new field here - instanceCompletionState. The value, "ProcessCompleted" signals the flow completed successfully.

If there's an error - 

parentEventId is another new field surfaced in the activity stream pushed to OCI Logging -

the value -1, indicates this is the first event. 

Here's another example - 

The replayedParentInstance field, shown in a previous OIC Activity Stream screenshot, is also pushed to OCI Logging. The field name used in OCI Logging is replayedParentInstanceId. 

Having this in OCI Logging makes it very easy to create an OCI Dashboard widget based on this -

Clicking on Open with logging search -

and I see the salient details.
 

 

OIC Connectivity

Naturally, there are a plethora of new features in respect of Connectivity, please see the post here for details.