The key components that build the SOA composite applications are as follows:
Oracle BPEL process components used for process/service orchestration.
Oracle Business Rule components used for centralized services/ process-related business rule implementation and execution.
Various adapter services such as file, JMS, and database adapters.
Oracle Mediator components used for filter, data transformation, and routing.
Oracle Human Task components used to define the human actions to be executed in the business process flow.
EDN that supports an event-driven architecture for event-driven applications.
Wires are used to create interaction between service end points, components, and references in SOA composites.
A composite is the unit of deployment for SCA. It holds services that can be accessed remotely and it contains one or more components.
SCA components are integrated together into one application and communicate with the outside world through binding components such as adapters and Web Services.
The ADF BC component can be configured to publish events for the CRUD operations it can perform.
SCA provides an assembly model for SOA-style applications.
SCA components are basic elements of business functions in an SCA assembly. Components are combined into complete business solutions by SCA composites.
Oracle User Messaging Service (UMS) provides a common service responsible for sending out messages from applications to devices.
Service interactions within SOA Suite are handled using Oracle Mediator.
Service Virtualization cannot be achieved using Mediator.
Oracle Service Bus or Enterprise Service Bus is required to carry out Service Virtualization. Only mediation of a service can be achieved using Oracle Mediator.
The BPEL/BPM Engine represents the orchestration component of SOA infrastructure.
Oracle BPEL Engine supports BPEL 1.1 and 2.0.
Incoming and outgoing XML documents for a Partner Link can be validated by setting the
validateXMLproperty on a Partner Link totrue.Metadata Service (MDS) allows you to share common artifacts such as XML schemas across SOA composites. It supports two types of repositories, namely, file-based repository and database repository.
The Service Infrastructure provides the internal message routing infrastructure capabilities for connecting components and enabling data flow.
The Service Infrastructure is responsible for the internal routing of messages between service engines and binding components.
Weblogic JMS is used as a messaging layer for delivering events through EDN. EDN can also be configured to use EDN-DB. EDN-DB uses an Oracle database as a backend store.
Event definitions are stored in the EDL file.
Event Delivery Network can work across SOA Suite.
Business Activity Monitoring (BAM) is used for visualizing and monitoring business activity.