Oracle Integration continues to enhance the connectivity portfolio by building a new set of adapters as well as enriching the existing adapters with the key customer focused enhancements. Oracle Integration adapters are the corner stone for connecting and automating application business processes. Oracle Integration Adapter abstracts communication with diverse applications on a single pane, simplify integration interfaces as business resources and supports rapid development through configuration and declarative model rather than complex coding.
In the endeavour of building robust and diverse connectivity portfolio, Oracle Integration August release will offer two brand new adapters viz. PayPal Adapter & OCI Streaming Service.
Paypal Adapter is the newest addition to the E-commerce segment of adapters and shall enable Oracle Integration customers to connect and automate their web store business processes. In the stated release Paypal Adapter shall support outbound invoke to execute the REST APIs enabling Integration developer to perform CRUD operations on the Paypal exposed business resources. As an example while order is being manufactured you may want to authorize a payment that you can capture later on successful delivery of the order.
Paypal Adapter connection page requires two sets of information to establish connection with the Paypal environment. First you would need to select the environment type i.e. Sandbox / Live so that adapter can connect to the appropriate endpoint. On security / credentials front you would need to provide a client id & secret, you can get those by following instructions in Paypal developer guide.
Now on building Integration flows with Paypal, PayPal Adapter enriches the integration developer experience by grouping the Paypal business resources by modules, objects and operations. PayPal Adapter provides support for the Catalog Products, Orders , Payments , and Payouts modules. The configuration of invoke endpoint can be done graphically by selecting the options as prompted by the Adapter through the wizard interface. It can be easily accomplished by following three steps viz. 1) Configure Action Type 2) Configure Operation 3) Verify Configuration in Summary.
OCI Streaming Service adapter is the newest addition in enterprise messaging segment of adapters. The OCI Streaming service provides a fully managed, scalable, and durable storage solution for ingesting continuous, high-volume streams of data. Customers can use OCI Streaming Service as a backplane to decouple components of large systems. One of the common use cases for OIC customers would be to broadcast application events emitted by applications to external systems by having OIC integration flows publish messages to OCI Streaming Service. OCI Streaming Service adapter enables an integration architect to publish and consume messages from the OCI Streaming service stream in a simple declarative manner.
OCI Streaming Service adapter connection page needs bootstrap server and SASL credentials for establishing the connection with the OIC Streaming Services. The OCI Streaming service bootstrap servers can be obtained as described in the OCI Streaming documentation. OCI Streaming Services support SASL based authentication over SSL, Integration architect needs to configure the user name, password and trust store. The SASL username is combination of tennant id, username and stream pool id that are concatenated by the '/' character and can be represented as <tennant id>/<user id>/<stream pool id>. The trust store needs to be generated from the OCI Streaming services browser certificate using any standard tool like keytool.
On building flows with OCI Streaming Services, adapter greatly simplifies how you connect, produce and consume messages from the OCI Streaming services as part of the Integration flow. Lets now look at feature and functionality of the adapter, adapter supports consuming and producing messages to / from OCI Streaming service streams, however through invoke pattern. The ability to consume the message through trigger pattern is in the future roadmap. To produce the message, Integration architect would follow intuitive configuration wizard to configure the invoke endpoint, at an outset adapter supports following three operations:
The first operation enables Integration architect to produce the message to the stream, by selecting the details like stream, partition, message structure, etc. The second operation enables Integration architect to consume the message from the stream and associated partition. The message can be read from latest or beginning of the stream, latest will fetch messages produced in last 60 seconds, whereas beginning will fetch all messages that are produced since last read from the partition. The additional option user has while consuming message is he or she can specify the consumer group, this enables multiple flows to read from the partition. The last option to consume the message from the stream by offset is for the exceptional scenario where Integration architect wants to read a message from specific offset.
Oracle Talent Acquisition Cloud (OTAC) previously known as Taleo Enterprise Edition is the worlds most used recruitment platform. OTAC Customers conventionally use bulk import and bulk export integration patterns to load / update data into OTAC and extract updated data out from the OTAC instance. The OTAC Adapter reuses the Taleo Connect Client (TCC) job specification by using the wrapsoap xml file generated by the tool as a design artifact. This greatly saves time and money for the customers, as they can get started with the Integration flows in no time.
The current OTAC adapter already supports performing bulk import operation to load / update the data into OTAC instance. With August release now OTAC adapter supports performing bulk export to get data out of OTAC. As an example you might want to export the new hires information from OTAC and import the same into your HRMS systems.
Lets now look at how bulk export Integration pattern can be implemented in OIC using OTAC Adapter. In the below flow we are exporting the new hires from the Taleo system and importing the same into HRMS system. In the stated scenario we can have a scheduled flow that periodically submits the export job request to the OTAC server, get the message keys, loop until job is completed and finally loads the data into HRMS system. This can easily be decoupled into multiple flows, depending on the business requirements.
The bulk export pattern in OTAC Adapter is built on same principle as bulk import i.e. it uses the Taleo Connect Client artifact wrapsoap xml as a design configuration. The configuration steps for Integration developer would be as following:
As stated earlier bulk export is built on same pattern as bulk import, Integration architect would need to check / loop till job status is completed (i.e. 5). Once completed Integration architect would need to use corelation key to access the exported data.
File Adapter is part of the technology adapters, conceiving a possibility for the customer to empower their connectivity agents with the file server capabilities. As customers look to simplify, integrate and automate their business processes with on premise systems, file adapter carry out a pivotal role in exchanging files between cloud and on premise systems. File Adapter has gone through significant enrichment, allowing Integration developers to develop more robust files based integration with on premise systems. File Adapter now supports list, read, write, delete and move operations on files through connectivity agent.
These enhancements will allow customers to implement use cases such as periodic retrieval of data extracts from on premises application/databases available in the local file system - and synchronizing them with cloud applications, cloud databases, FTP servers as well as external systems using Apache Kafka, OCI Streaming Service, etc. As files will be exchanged between on premise systems and cloud through connectivity agent, the limit of the file that can be transferred through file adapter is 1 GB.
REST Adapter is one of the key technical adapter in the connectivity portfolio, enabling customers to connect with diverse applications based on the standards. Oracle Integration continues to adopt open standards to help customers simplify and streamline their integrations and reap the rewards from open standards. OpenAPI has indeed become a de facto standard for describing a REST API. Oracle Integration REST adapter in the conquest of open standards now supports consuming REST APIs described in OpenAPI specifications. This will now help Oracle Integrations to easily integrate with application and services that are exposing OpenAPI based APIs descriptor.
The experience of consuming OpenAPI catalog is very similiar to the swagger catalog URL, Integration architect needs to provide the OpenAPI catalog URL in the connection page along with other details. Once configured, while designing flows with configured connection adapter shall discover all the available resources and supported verbs. Integration architect needs to just select the resource and verb while configuring the invoke end point, adapter will automatically configure the payload to send and receive from the endpoint based on the OpenAPI definition. To learn more about the feature please follow this blog.
Salesforce.com adapter is a robust adapter supporting wide array of functionalities for integrating with Salesforce CRM applications right from creating bi-directional integration, discovering business objects to providing human readable names for elements found in business objects for easy mapping.
Salesforce.com allows customers to extend their application by developing and deploying custom business logic as APEX classes in Salesforce.com - And these APEX classes can be exposed by customers as a REST API which allows for programmatic invocation by external clients. With the August release, Salesforce adapter has been enhanced to allow integration flows to programmatically invoke the custom business logic deployed in Salesforce.com. Salesforce Adapter now enables you to consume the REST endpoints that are exposed through Apex REST classes on Salesforce.com and perform use cases such as Retrieve a Record, Create an Attachment, and so on.
The configuration of Apex REST endpoint in Salesforce.com Adapter can be done graphically by selecting the options as prompted by the Salesforce Adapter through the wizard interface. It can easily be accomplished by following steps:
SAP Commerce Cloud Adapter help you to connect and create an integration with SAP Commerce Cloud applications. SAP Commerce Cloud Adapter already supports performing CRUD operations with the standard objects in the SAP Commerce Cloud application through invoke pattern.
SAP Commerce Cloud adapter with the update in August release extends the capabilities for custom attributes/custom APIs/custom operations/custom objects in the SAP Commerce Cloud applications. SAP Commerce Cloud Adapter now enables you to integrate customized use cases such as Searched Based on Product Name, Get Store by Name, and so on. So let's start with a quick tour of the new features:
The Shopify Adapter enables you to design, set up, and manage digital stores across multiple sales channels including mobile, social media, web, online marketplaces, and so on. With the August release, we are announcing many exciting improvements for both inbound and outbound integration patterns. So, let's take a quick tour and find out what's new in the August release for the Shopify adapter:
This concludes all the connectivity features that are being delivered as part of the August 2020 release. Oracle Integration continues to invest in the adapters, helping customers in their digital transformation journey of integrating, automating and transforming their business processes to succeed in the digital era.