#1012 - OIC Rapid Adapter Builder Enhancements

There have been some enhancements to the Rapid Adapter Builder -

The project directory structure has changes somewhat - 

api - this is used when your input is an open api spec.

misc - this is used when your input is a postman collection. 

Note, the OIC instance connect information has been externalised.

This makes sense, imagine an oracle partner creating custom adapters. The partner will not know the OIC instance details of the end-consumers.

Check out the documentation here

#1011 OIC 24.02 New Features - Observability / REST API

Some nice new features coming with 24.02 - 

1. Activity Stream now shows which user triggered an integration flow - 

2. New REST API attributes for min/max execution duration.

Let's try this out on the following flows - 

So the 3 flows executed as follows - 

• 10.26 seconds
• DUg3ptn3Ee69UfUKGnU7wg
• 5.14 seconds
• KgPdvtn3Ee6_QJ3NwcOM1g 

• 2.03 seconds
• INMd3tn3Ee69UfUKGnU7wg

I run the api with minDuration=1000 msecs - 

https://design.integration.us-phoenix-1.ocp.oraclecloud.com/ic/api/integration/v1/monitoring/instances?integrationInstance=myOICInstance&q={timewindow:'1h', code:'AA_ORDERPROCESS', minDuration:'1000'}

Count = 3 is returned.

 I run again with minDuration = 5000 msecs - This time only 2 are returned - 

those with the following instance ids -

- KgPdvtn3Ee6_QJ3NwcOM1g (5.14 secs)

- DUg3ptn3Ee69UfUKGnU7wg (10.26 secs)

So this returns those instances that took at least 5000 msecs to execute.

Next test is with maxDuration = 3000 msecs -

This returns only 1 flow - that with the instance id INMd3tn3Ee69UfUKGnU7wg (2.03 secs)

I try again with max set to 6000 msecs - 

This returns 2 flows - 

- KgPdvtn3Ee6_QJ3NwcOM1g (5.14 secs)

- INMd3tn3Ee69UfUKGnU7w (2.03 secs)

i.e. those instances that executed within 6 seconds.