Database Reference
In-Depth Information
For now, it's important to provide all combinations of one- and two-way MEPs.
Mediators' MEPs (green one- and two-way arrows to the left of the service address fields)
are based on the service WSDL we are selecting for target service operations. We have
already decomposed a considerable number of processes, and we are quite aware of their
WSDL. Therefore, any speculation about the possible MEPs and operations will be easy,
and it's pretty similar to defining the "generic LoanService" from the
DynamicPartnerLink
example in
SOA Best Practices: The BPEL Cookbook
,
Oracle
.
Here, we just go a little further and define the abstract and generic "Sync CustomService",
"Async CustomService", and "OneWay CustomService" for services we would like to in-
voke directly from our service broker. Also, in the earlier screenshot, you can see some
statically defined services such as Audit, EP Lookup Service, and Error Handler, which
we will be using anyway. The CRM facade here is just an example of the static business
non-agnostic service, which is still not covered by a dynamic composition. Feel free to
amend it in your actual implementation.
The generic Adapter endpoint in the list is probably the most important endpoint for
cross-framework communication as it represents an OSB adapter, fulfilling the same rout-
ing/transformation functions in the EBS framework. That's how we communicate with
eternal standalone services and applications that are not directly invoked by a single SCA.
The sequence of establishing this static routing is quite standard (see the Oracle docs,
ht-
shortly highlight the important step. After clicking on the green plus sign in the upper-
right corner, you will be invited to select the target service. It is obvious that static and dy-
namic routes cannot be mixed in one mediator instance (a warning is shown in the screen-
shot); you can consider it as a limitation, but there are several simple ways to mitigate it.
Nothing prevents you from calling another mediator of the desired type sequentially.
The next step is to learn how to set content-based routing using an expression builder. The
content and structure of our execution plan are completely related to our metadata tax-
onomy in ESR; we will have to dedicate much more time to it later, although we have
already displayed several key fields in the earlier screenshot:
•
mep
: This is the flag that is used for routing to the appropriate abstract service. In
our case, it could be generic sync, async, and one-way flags. You can add your
own MEP type according to WSDL 2.0 MEP if you want.
Search WWH ::
Custom Search