Database Reference
In-Depth Information
Dynamic compensations in a simple agnostic
controller
We want to demonstrate another interesting Mediator feature we used in some inbound
flows, although it's not related to any SOA patterns directly at first glance. For some opera-
tions within a single service invocation group, we will need to translate the remote re-
sponse code (errors, messages, and statuses) into generic agnostic controller statuses. Using
these statuses, the controller will decide whether to proceed with the next task or execute
the compensative action. You can see it in a flows fragment as demonstrated in the earlier
screenshot. The task is fairly obvious as external applications, which are not in our Service
Inventory, naturally have their own code, statuses, and resolution logic. At best, they will
provide you with certain code, reflecting their operational status; however, those situations
when some error dumps will be returned are also quite common. Codes and related resolu-
tions should be discussed during the service encapsulation and functional decomposition
stage, and we should have at least the initial table with values and code in the form of
Domain-Value Map ( DVM ). You can create DVM for your SCA application/active pro-
ject ( Ctrl + N , then navigate to All Technologies | Domain-Value Map ) and store it in your
MDS for common use. You can use it in any of your XSLTs as well (you can find plenty of
examples on that), but the usage in Mediator is most interesting to us.
Using DVM in Mediator for error code mappings
Search WWH ::




Custom Search