Chapter 8. Communicating with SOA Suite

In this chapter, we will cover:

  • Invoking a SCA composite synchronously from an OSB service
  • Invoking a SCA composite asynchronously from an OSB service
  • Invoking an OSB service from SCA composite synchronously
  • Invoking an OSB service from SCA composite asynchronously

Introduction

The OSB provides a SOA-DIRECT transport that can be used to invoke Oracle SOA Suite service components, such as BPEL processes, human tasks, rules, and Oracle Mediator components.

The SOA-DIRECT transport provides native connectivity between OSB services and Oracle SOA Suite service components. Oracle SOA Suite provides a direct binding framework that can be used to expose Oracle SOA Suite service components of an SCA composite. The OSB SOA-DIRECT transport can be used to interact with those exposed services through the SOA Direct Binding framework, letting those service components interact in the service bus layer and leverage the capabilities and features of OSB

The SOA-DIRECT transport supports the following features:

  • Invocation of any SOA binding component services through Java Remote Method Invocation (RMI)
  • WS-Addressing
  • Identity propagation
  • Transaction propagation
  • Attachments
  • Optimized RMI transport for invoking SOA services
  • High availability and clustering support
  • Failover and load balancing (not available for services in the service callback role)
  • Connection and application retries on errors

The SOA-DIRECT transport uses WS-Addressing for message correlation in synchronous and asynchronous communications. We will see the WS-Addressing applied in the recipe, Invoking, an, OSB, proxy, service, from, SCA, composite, asynchronously.

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset