ICS (Integration Cloud Service) is a PaaS cloud offering from Oracle that provides capabilities of integrating applications both on-cloud and on-premise. With any integration, there is a requirement to version the integration flows/services. The need to version integration flows is because the endpoint’s schemas change from time to time, due to application changes, for business needs. When the endpoints change, the integration flow needs to also change to make use of the new schema fields. ICS provides capabilities to version integration flows. This is a great way to add new versions of services/Integration flows and also keep the old services/Integration flows intact.

When a new version of Integration flow is created there is a need to retain the old mappings and create new mappings for new fields. ICS provides the functionality of retaining the mapping through the “Regenerate” endpoint functionality.

This blog demonstrates the functionality to regenerate endpoint.

Sample Integration Flow

Below is a simple ICS integration flow to demonstrate the regenerate endpoint functionality. The integration flow has a SOAP source endpoint and REST destination endpoint. The integration flow was created on version 16.1.5 of ICS.

Flow Overview

Mapping

The integration flow has a simple Request mapping as shown below.

WSDL

The source SOAP endpoint has 2 input fields input1 and input2 as shown below.

Regenerate Endpoint WSDL

Change WSDL

Assume that the SOAP endpoint schema changes and  2 more fields’ input3 and input4 are added as shown below.

Import New WSDL

After these above fields are added, a new WSDL is created. Once the new WSDL is created, one may choose to clone the existing integration or edit the existing integration if versioning is not required. After this, the connection needs to be updated with the new WSDL.

Updating the WSDL and trying to save the connection pops up a warning that the connection being modified is used by one or more integration and that the integrations needs to be reactivated for changes to take effect. Click Yes.

Regenerate Endpoint

To regenerate endpoint wsdl, go to the integration flow and click on the source endpoint (endpoint whose schema was updated). To retain the mappings click on the regenerate icon as shown below.

This will pop up confirmation message whether you would like to proceed with the regeneration. Click Yes.

After confirming, a message that the regeneration successful message will be shown as below.

By clicking on the mappings, one can see that the old mappings have been retained and the new fields added.

Edit Endpoint Vs Regenerate Endpoint

Editing the endpoint instead of regenerate does not retain the mappings as shown below.

After clicking on the edit icon the following screens pop up.

As seen below the color of the mappings activities change from green to grey. This indicates that both request and response mappings are lost on edit.

Summary

The regeneration of endpoints is supported for all endpoints.This blog demonstrates how to regenerate endpoints when the schema on the applications change. This functionality comes in handy when they are incremental schema changes. The regenerate endpoint functionality helps retain existing mapping therby saving effort to redo all mappings on schema changes.

All content listed on this page is the property of Oracle Corp. Redistribution not allowed without written permission