Service Component Architecture within SOA Composite Applications
Service Component Architecture within SOA Composite Applications
Oracle SOA Suite uses the SCA standard as a way to assemble service components into a SOA composite application. SCA provides a programming model for the following:
In the SCA environment, service components are the building blocks of applications.SCA provides a model for assembling distributed groups of service components into an application.Composites are used to group service components and wires are used to connect service components.
The key benefits of SCA include the following:
- Loose coupling : Service components integrate with other service components without needing to know how other service components are implemented.
- Flexibility : Service components can easily be replaced by other service components.
- Services invocation : Services can be invoked either synchronously or asynchronously.
- Productivity :Service components are easily integrated to create a SOA composite application.
- Easy Maintenance and Debugging :Service components can be easily maintained and debugged when an issue is encountered.
A SOA composite is an assembly of services, service components, and references designed and deployed in a single application. Wiring between the services, service components, and references enables message communication.
In SOA Application all the details for a composite are stored in the composite.xml file.SOA Components are mainly divided into 3 types
- Service Components
- Binding Components
- Wires
Service Components :
Service components are the building blocks that you use to construct a SOA composite application.Following service components are available. There is a corresponding service engine of the same name for each service component. All service engines can interact in a single composite.
BPEL processes provide process orchestration and storage of a synchronous or an asynchronous process.We can design a business process that integrates a series of business activities and services into an end-to-end process flow.
- Business rules enable you to design a business decision based on rules.
- Human tasks provide workflow modeling that describes the tasks for users or groups to perform as part of an end-to-end business process flow.
- Mediators route events or messages between different components.
- Spring enables you to integrate Java interfaces into SOA composite applications.
Binding Components:
Binding components establish a connection between a SOA composite and the external world. There are two types of binding components:
- Services provide the outside world with an entry point to the SOA composite application. The WSDL file of the service advertises its capabilities to external applications. These capabilities are used for contacting the SOA composite application components. The binding connectivity of the service describes the protocols that can communicate with the service, for example, SOAP/HTTP or a JCA adapter.
- References enable messages to be sent from the SOA composite application to external services in the outside world.
Below are the binding Components available in SOA 11g and 12C
Binding Components
|
Description
|
Use for connecting
to standards-based services using SOAP over HTTP.
|
|
Use for integrating
services and references with technologies (for example, databases, file
systems, FTP servers, messaging: JMS, IBM WebSphere MQ, and so on) and
applications (Oracle E-Business Suite, PeopleSoft, and so on). This includes
the AQ adapter, database adapter, file adapter, FTP adapter, JMS adapter, MQ
adapter, and Socket adapter.
|
|
Use for browsing B2B
metadata in the MDS repository and selecting document definitions.
|
|
Use for connecting
Oracle Application Development Framework (ADF) applications using SDO with
the SOA platform.
|
|
Oracle Applications
|
Use for integrating
the Oracle Applications adapter with Oracle applications.
|
Use for integrating
Java EE applications with Oracle BAM Server to send data, and also use as a
reference binding component in a SOA composite application.
|
|
Use for integrating
SDO parameters or Java interfaces with Enterprise JavaBeans.
|
|
Use to invoke a SOA
composite application and exchange messages over a remote method invocation
(RMI) in the inbound direction and to invoke an Oracle Service Bus (OSB) flow
or another SOA composite application in the outbound direction.
|
|
HTTP binding
|
Use to integrate SOA
composite applications with HTTP binding.
|
Wires :
Wires enable you to graphically connect the following components in a single SOA composite application for message communication:
- Services to service components
- Service components to other service components
- Service components to references
Post a Comment