This section presents the multiple layers of services that are available to the solution architect when developing capabilities.
The reference architecture defines each layer, identifies the criteria for determining the right layer, and suggests ways of keeping capabilities and services at the right level of granularity.
A target specifies the next service or event to which an Oracle Mediator sends messages and also specifies which service operation to invoke.
You can specify a service or an event as a target type.
Routing rules specify where an Oracle Mediator sends the message, how it sends the message, and what changes should be made to the message structure before sending it to the target service.
Routing rules can be of the following two types: Routing rules can only be defined for an Oracle Mediator with a defined interface.
Architecture Blue Print This provides the basis of the reference architecture.
It introduces key concepts used across all other sections, and outlines the objectives and goals of transitioning an organization from a system oriented to a service oriented architecture.
Oracle Mediator provides a lightweight framework to mediate between various components within a composite application.
Canonical Data Format This section provides a comprehensive look at how to develop a CDF leveraging existing system formats and taking into account industry standards.
The section focuses on Data Modelling, Partitioning the Canonical Data Form Design Pattern and specifying Attributes and Annotations to support the goals and objects of a Service Oriented Architecture using Oracle’s SOA offerings.
The Mediator Editor with a multipart source appears as shown in Figure 20-1.
If you add a validation for a multiple part message, then the Add Validation dialog displays a list of parts from which you can choose one part, as shown in Figure 20-3.