The Integration blog covers the latest in product updates, best practices, customer stories, and more.
-
Integration
July 21, 2020
Convert Basic Routing style Integration to Orchestration style.
Convert Integrations Style from Basic Routing to App Driven Orchestration.
The Basic Routing Integrations are deprecated now and currently, there is no way to convert a Basic Routing Integration to Orchestration. With this new feature, the user will be able to do the conversion from Basic Routing to App Driven Orchestration as the latter has more flexibility. The convert can be done with the help of "convert" action provided in the actions menu which is explained in detail in the below sections.
Prerequisites:
The minimum Oracle Integration version required for the feature is “20.36330”.
What happens during the conversion of Basic Routing style to Orchestration
During the conversion of Basic routing to Orchestration, the process goes through each and every entity of the ProjectModel( or flow) of Basic Routing and does a conversion to the corresponding entity of Orchestration style. The below table gives a brief mapping of the entities.
|
Basic Routing |
Orchestration |
|---|---|
| Source | Trigger |
| Target | Invoke |
| Request Enrichment | Invoke |
| Response Enrichment | Invoke |
| Content-Based Routing | Switch |
| Faults Mapping | Scope Action |
Why Orchestration style?
Below are the advantages of using Orchestration style over Basic Routing
- More flexibility in modeling the integration flow using looping actions like forEach(both serial and parallel), while, etc. which are not supported in Basic Routing
- Better fault handling mechanism using Scope action.
- Can use notification action for sending emails within the flow.
- Other actions like assign, stage write, stage read, etc can be used within Orchestration flow.
Why "Convert"?
If the customer needs to convert their Basic Routing Integration to Orchestration style manually then the customer needs to understand the corresponding entity/action in Orchestration style, the process is time consuming, prone to error, etc., with this feature through a click of a button the conversion is done automatically.
Steps to convert the Basic Routing Integrations to App Driven Orchestration integrations:
1. Navigate to Integrations Landing page.
2. Click the‘ Actions’ menu(Hamburger menu).
3. Click on the ‘Convert’ option under the actions menu.
NOTE: The option is not available for basic routing integrations that are active or locked.
4. A ‘Convert Integration Style’ dialog is displayed.
5. Select the appropriate option and click on the Convert button
- Copy as New App Driven Orchestration Integration.
This option will create a new App driven orchestration integration with provided name, identifier & version.
- Overwrites the selected Basic Routing Integration.
This option will overwrite the existing Basic Routing Integration with the App Driven Orchestration.
6. When conversion completes, the following message is displayed:
CONFIRMATION
Integration Integration_Name (version_number) was converted successfully.
Example:
Basic Routing Integration
Converted App Driven Orchestration Integration
Current Restrictions/Limitations:
Basic routing integrations listed below cannot be converted currently.
- Publish to OIC
- Subscribe to OIC
- Asynchronous integrations with delayed response
- Basic Routing Scheduled Integration
Faulted Integrations Behavior After Conversion
There is a change in behavior for faulted integrations after basic routing to app-driven orchestration integration conversion is complete. When a synchronous basic routing integration fails, a failed tracking instance is created. The failed integration is visible on the Tracking Details page for that integration under Home > Monitoring > Integrations.
If you select View Errors from the menu(Hamburger menu), the following error is displayed.
Error while invoking target service "integration_name" for sync flow. The Error was raised back to the calling client.
After conversion to an app-driven orchestration integration, the tracking instance is marked as succeeded for this integration. This is because the failure is handled in a scope fault handler.
If you select View Activity Stream from the menu(Hamburger menu), the following message is displayed.
Error Message is - Error has been recovered. No message to display.
Therefore, the integration is marked as succeeded instead of failed.