The Integration blog covers the latest in product updates, best practices, customer stories, and more.

Oracle Integration November 2020 Update for Technical Adapters

Prakash Masand
Senior Principal Product Manager


Oracle Integration has rich capabilities for connecting with diverse technical end points may it be service / API based like SOAP and REST or messaging based like Kafka and JMS or database management system like ADW, ATP etc. OIC supports wide array of technical adapters enabling customers to connect, integrate and reap advantages of core digital technologies in their business processes. Oracle Integration continues to improve the technical adapters capabilities further empowering customers in their digital transformation journey.

In November 2020 update we are pleased to announce following updates to the technology adapters:

REST Adapter Improvements

Oracle Integration REST adapter is a versatile adapter helping customers to communicate with wide array of products & services like Oracle Functions, OCI Object storage, AWS S3 etc, proving to be a one of the cornerstone adapters for customers modern integration solutions. In the conquest of further empowering the customers, Oracle Integration has been further enhanced the REST adapter with following capabilities.

  1. Generation of sample curl command
  2. Standard OAuth policy Improvements
  3. Connectivity Properties Improvements

Let us now dive deeper into each enhancements.

Generation of sample curl command

As Oracle Integration customers look to leverage REST adapter for integrating with wide array of products and services, having variety of different configuration options like security policy, headers, parameters etc. As these options are configured at different stages, they get lost and Integration developer loses the visibility into the configuration. Oracle Integration envisaging Integration developer need, has provided an option in the REST adapter wizard configuration summary page to generate the sample curl command. The new link has been added in the summary page, on clicking it adapter would generate the sample cURL command. Please note this command cannot be executed on the command line right off the shelf as it misses few information, one would need to provide those before execution, as an example one needs to place in parameters value, security configuration parameters etc. Let us now take a quick look at the configuration summary screen, as you can see below Integration developer now has an option in the summary page to generate a sample cURL command:

On clicking the "Generate a sample cURL" link, adapter would generate the sample cURL command. This greatly summarizes the configuration performed by the Integration developer in the format they are well accustomed to and provides them a handy tool to validate the configuration of specific invoke before hand i.e. before executing the same as part of the flow.

Standard OAuth Policy Improvements

OAuth is a widely accepted open standards for exchanging security token, simplifying access to APIs, resources & services in the digital world. One of the challenge though is OAuth specification defines high level exchange of information between participating parties leaving details of implementation on the implementor. Oracle Integration REST adapter supports variety of OAuth security policy out of the box viz. OAuth Client Credentials, OAuth Resource Owner Password Credentials and OAuth Authorization Code Credentials. This has created a unique challenge for Oracle Integration to seamlessly connect with different products and services using single adapter, as different vendors require different mechanism for exchanging the required security token. At same time Oracle Integration is looking to make it really simple for customers to connect and communicate with all the digital REST services using supported OAuth security policy, on the same conquest REST adapter now supports an additional configuration parameter "Client Authentication" in the connection page. The client authentication parameters enables Integration architect to configure how Oracle Integration exchanges security token over the wire, as an example whether client id and secret is sent as a part of basic auth header or in a body. This enables Oracle Integration customers to seamlessly connect and communicate with variety of digital products and services without requiring custom OAuth policy for overcoming the difference in the vendor implementation.

Let us now look at the new parameter option in the REST adapter connection page, as you can see below just by selecting the option highlighted below, Integration architect can configure how to send the security token to the desired service.

Connectivity Properties Improvements

Oracle Integration REST adapter is used for wide variety of use cases, and requires additional flexibility such as querying and overriding the base URI, relative URI or even absolute endpoint URI  for scenarios where you want to conditionally change endpoint based on the received payload. The connectivity properties provide a great flexibility to Integration architect for querying and updating the endpoint through mapper based on the realtime information as received in the flow. The connectivity properties have been further enhanced to support the trigger requests as well i.e. with November release you will be able to access connectivity properties under trigger request node. This is really helpful for building contextual endpoints based on current trigger configuration, consider a scenario you would like to pass the location for next integration flow in the response of current trigger flow. The ability to consume trigger rest base URI along with XSL function would allow you to do exactly the same:

In the above example you can see how we can build next flow access URL by accessing the current trigger connectivity properties. The connectivity properties for the invoke endpoint has also been enhanced to support skipping control characters from the response, this is helpful where your 3rd party application response includes control characters and you would like to exclude them while parsing the response.

Kafka Adapter Improvements

Apache Kafka is one of the modern pillars in customer big data and digital ecosystem where high volume of messages are being ingested and consumed for publishing the state of business at rapid pace. Oracle Integration Kafka adapters enables customers to decouple large components of their business applications by broadcasting and consuming business events on Kafka without writing any code. Kafka adapter already supports wide array of use cases such as publishing messages to specific topic & partition, consuming messages from specific consumer group and reading from beginning / latest from topic.

With November 2020 update, Kafka adapter now supports configuring the Kafka connection as a trigger for the Integration flow. Please note this is only supported for the Kafka hosted behind corporate firewall or private network configuration and with the connectivity agent. This enables customers to consume the high volume of messages from Kafka topic and consume them in the application flow. As an example a fully automated robotic manufacturing factory is placing updates on the manufacturing on the products in real time on the Kafka topics, can now be consumed in application through Oracle Integration.

Let us now take a look at the configuration of Kafka as a trigger, the key aspect of configuring the Kafka as a trigger is the polling interval, the rest of configuration is very similar to consuming messages from topic using Invoke pattern. Once you have given the name to the endpoint, the next screen will take the configuration of topic, consumer group with polling interval, the polling interval is used by the Oracle Integration connectivity agent to poll for the new messages on the configured Kafka instance.

As you can see in the above configuration, all integration architect needs to configure is, consumption of the message from Kafka topic by configuring topic, partition, consumer group etc. along with the polling frequency. Once configured message is consumed and available for consumption in the down stream processes. One more key piece of information to take note off here is Maximum Number of Records to be fetched field, Integration architect can choose maximum number of records to fetch, lets say one picks 1000 based on the customers business need. The Kafka adapter will honour the 10MB payload limit by fetching either Maximum number of records as specified by integration architect or as many records that can be packed in the 10MB payload. This optimises the max number of records that can be read based on the technical limitation of OIC and at same time enables Integration architect to provide the limit based on the customer business requirements.

The next key enhancement for Kafka adapter is, Kafka adapter now supports integration with the Confluent Kafka platform to produce and consume messages. Confluent Kafka is one of the prominent Kafka providers out there in the market supporting Kafka features and capabilities in the cloud pay as you go service model meeting the customers digital scale needs.


This concludes enhancements done in the November 2020 update of Oracle Integration to the technical adapters viz. REST and Kafka. Oracle Integration continues to invest significantly in the technical adapters helping customers in their digital transformation journey by meeting their modern use cases. I hope you enjoyed the blog and are eagerly waiting to consume the enhancements done in the technical adapters and reap advantage in your business processes.


Join the discussion

Comments ( 2 )
  • Owen Thomas Wednesday, January 13, 2021
    Hi Prakash,

    Is there plans in the roadworks to remove the requirement for the Agent with the Kafka Adapter so this will then work with Confluent.

    Also the need to have this schedule so it operates like most other Kafka consumers

  • Prakash Masand Tuesday, February 23, 2021
    Hi Owen,

    OIC Kafka Adapter supports connecting with Confluent Kafka from November 2020 OIC release, please find the supporting documentation link below.


    Additionally, the OIC Kafka adapter does not require the connectivity agent for general use cases, rather connectivity agent is only required for the polling/trigger use cases.

Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.