The SOA Suite Adapter on Oracle Integration (OIC) enables you to take advantage of the latest feature rich adapters on OIC, while leveraging your existing investments on SOA Suite and Service Bus. It provides a rich design-time experience to create a single connection to SOA Suite / Service Bus, browse through the services running on them, and create integrations. For runtime, it relies on the standard SOAP and REST Adapters with or without the Connectivity Agent, depending on how the SOA Suite / Service Bus is accessible over the network.
The current SOAP and REST adapters on OIC already provide integration to these services, but with this new adapter, you can do away with the hassles of multiple connections or fetching service metadata manually.
The SOA Suite adapter supports connectivity to:
In the connection palette, select the SOA Suite Adapter.
Provide a meaningful name for this connection and click on 'Create'. This opens up the page where the connection details can be configured.
To determine what URL to provide here, examine the topology of the SOA Suite / Service Bus instance i.e., whether the instance is accessible through :
Provide the SOA Suite / Service Bus user credentials here.
In case the SOA Suite / Service Bus instance is not directly accessible from Oracle Integration, for eg. if deployed on-premise, or behind a firewall, a Connectivity Agent needs to be configured for this connection. This can be done using the 'Configure Agents' section.
However, Connectivity Agent may not be required when the SOA Suite / Service Bus URL is publicly accessible, for eg. if deployed on SOA Cloud Service.
To know more about Connectivity Agent, check out these:
A simple 'Test' connection on this page verifies that the SOA Suite / Service Bus is accessible through the connection details provided, that the version of this instance is supported by the adapter, and that the user is authenticated and authorised to access this instance.
(This adapter can be configured only as an invoke activity to the services exposed by SOA Suite / Service Bus.)
Drag and drop a SOA Suite adapter connection into an orchestration flow.
Name the endpoint and proceed to configure the invoke operation.
If only SOA Suite or Service Bus instance is accessible through the URL provided in the connections page, the same is shown as a read-only label. But if both are accessible, they are shown as options.
If the options are shown, select option 'SOA' or 'Service Bus' - to configure this endpoint to invoke SOA Composites or Service Bus projects respectively.
(If both SOA and Service Bus are available as options, select option 'SOA')
Select a partition to browse the composites in it
Select a composite to view the services that it exposes.
(If both SOA and Service Bus are available as options, select option 'Service Bus')
Select a project to view the services that this it exposes:
Select a service from the desired SOA composite or Service Bus project, to integrate.
If the selected service is a SOAP web service, the Operation, Request / Response objects, and the Message Exchange Patterns are displayed
If the selected service is a RESTFul web service, proceed to the next page to complete further configurations for the Resource, Verb, Request and Response Content Types, Query Parameters, etc.
Proceed to the next page to view the summary and complete the wizard.
The newly created endpoint can now be seen in the orchestration flow.
The request and response objects of this invoke are available for mapping in the orchestration.
Once the request and response objects are mapped, this flow can be activated like any other flows on OIC.
The activated flow would be ready to send requests to running SOA composites / Service Bus projects via SOAP or REST invocations. You can use the OIC Instance Tracking page to monitor the runtime invocation after flow is activated and invoked.