X

The Integration blog covers the latest in product updates, best practices, customer stories, and more.

  • October 30, 2019

How SOA Suite Adapter Can Help Leverage your On-premises Investments

Vijaya Bhat
Software Engineer

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:

  • Oracle SOA Suite and/or Oracle Service Bus hosted on-premise
  • Oracle SOA Suite and/or Oracle Service Bus hosted on SOA Cloud Services 

 

Configuring SOA Suite Adapter to connect to a SOA Suite / Service Bus instance

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.

 

Configure connectivity:

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 :

  • The Load Balancer URL
  • The OTD or Cluster Frontend URL
  • or just the Managed Server URL where the SOA Suite / Service Bus instance is running.

 

Configure Security:

Provide the SOA Suite / Service Bus user credentials here. 

  • If you are integrating with SOA Suite, make sure this user is a part of the 'Operators' group and has the 'SOAOperator' role on that server.
  • Likewise if you are integrating with Service Bus, make sure this user is a part of the 'Deployers' group on that server. 

 

Configure Connectivity Agents:

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:

 

Test and Save the connection:

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.

 

How to configure a SOA Suite invoke endpoint in an Orchestration Flow

(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.

 

To configure this endpoint to invoke SOA Composites:

(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.

 

To configure this endpoint to invoke Service Bus Projects:

(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:

 

Configuring Service details:

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

  • SOAP services with Synchronous Request-Response or One Way Notifications are supported.
  • Asynchronous Requests are supported as One Way Notifications only. Callbacks are currently not supported.

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. 

  • REST services which have the schemas defined (i.e., non-native REST services and non-end-to-end-json based REST services) are supported.
  • The following Request and Response Content Types are supported:
    • application/xml
    • application/json

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.

 

Runtime invocation from OIC to SOA composites / Service Bus projects: 

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.

 

What this adapter needs on the SOA Suite / Service Bus side

Supported SOA Suite Versions:

  • Oracle SOA Suite v 12.2.1.4 onwards
  • Oracle SOA Suite v 12.2.1.3 - with these patches applied. 

Supported OWSM policies:

  • For SOAP webservices 
    • oracle/http_basic_auth_over_ssl_service_policy
    • oracle/wss_username_token_over_ssl_service_policy
    • oracle/wss_http_token_over_ssl_service_policy
    • oracle/wss_username_token_service_policy
    • oracle/wss_http_token_service_policy
    • no authentication policy configured
    • Services protected by multiple policies are not supported
  • For RESTful webservices  
    • oracle/http_basic_auth_over_ssl_service_policy
    • oracle/wss_http_token_service_policy
    • no authentication policy configured
    • Services protected by multiple policies are not supported

 

Join the discussion

Comments ( 1 )
  • Siva Tuesday, December 10, 2019
    Very nice & clear explanation with all the details.
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.