February 2021 Oracle Integration Update by Antony Reynolds
March 30, 2021 Leave a comment
It is time for the February quarterly update to Oracle Integration. Lilly, the Oracle integration mascot, has lots of exciting new features and improvements to share with you. Note that testing is still underway for these features and, although unlikely, it is possible that some will not meet our quality standard and be deferred to a later release.
Announcements & Update Windows
Currently tenant administrators get notified of OIC Gen 2 updates via notifications in the OCI console. OIC Gen 2 administrators can also see the same upgrade notice in the OIC console, so watch out for the date of your upgrade.
Remember, you can also mark your Gen 2 instance for update in either the first or second upgrade window, as explained in Choose Your Update Window. If you previously tagged your instance, then there is no need to tag it again. If it is not yet tagged for window 1, then the deadline for tagging for February is 14 January. Tags added after this date will take effect for the May release.
API Led Integration
We are making it easier to work with Oracle API products. Previously we supported only Oracle API Platform. We are now building out support for Oracle API Gateway.
- Auto-generation of API gateway deployment from OIC
- You can now create an Oracle OCI API Gateway Deployment from a REST based Integration at the click of a button. The API deployment will be created with routing rules pointing to the activated integration. Integrations with multiple verbs/paths will have a rule created for each verb/path.
Developer Productivity Enhancements
We are making the following improvements for developers:
- Support for attachments in Integration Test UI
- The testing tool built within Oracle Integration now offers the support for attachments. This will help developers test Integrations with attachment support without having to leave Oracle Integration UI.
- Ability to edit XLST code in Oracle Integration Mapper
- Developers can now edit XLST code within the Mapper while building their Integration flows. This will tremendously help them with complex XLST transformations. Avoiding the need to copy the XSLT and then import it back into the mapper. Read the complete article here.
For regular information on Oracle PaaS become a member in the PaaS (Integration & Process) Partner Community please register here.
Blog
Twitter
LinkedIn
Facebook
Wiki
Technorati Tags: SOA Community,Oracle SOA,Oracle BPM,OPN,Jürgen Kress