The graphic provides an example of a composite that includes a mediator service component and a BPEL service component, an inbound service binding component, and an outbound reference binding component.
Service components are the building blocks of an SOA composite application. Each service component is hosted in its own service engine container. Messages sent to the service engine are targeted at specific service components. For example, a message targeted for a BPEL process is sent to the BPEL service engine. Service engines process the message information received from the .
The following service components are available. There is a corresponding service engine of the same name for each service component. All service engines can interact together in a single composite.
For process orchestration and storage of synchronous or asynchronous process. You design a business process that integrates a series of business activities and services into an end-to-end process flow.
For designing a business decision based on rules.
For modeling a workflow that describes the tasks for users or groups to perform as part of an end-to-end business process flow.
For routing events (messages) between different 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.
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 reference