Database Reference
In-Depth Information
• The API and representation layer responsible for the exposure of the application
interfaces
Application modules and APIs within an application package are presented as red and
green boxes, respectively.
The Fusion Middleware layer is also based on the WLS Application Server and probably
should be placed in between the DB and App layers, according to its name; however, we
deliberately put it close to the southbound end of the Fusion perimeter, binding it with the
security layer. This layer hosts most of the SOA frameworks, which in turn compose most
of the patterns discussed later. Now, all abstract frameworks, discussed in
Chapter 1
,
SOA
Ecosystem - Interconnected Principle, Patterns, and Frameworks
, are mapped to this lay-
er and numbered. The layer itself can be vertically divided into Runtime and Design areas.
Note that this division is rather arbitrary as ESR and Governance frameworks are actively
used in both areas. The runtime area holds four distinctive frameworks, namely:
• Adapters (1)
• Service Bus (5)
• Orchestration (4)
• Service management (runtime part)
The Service Brokers, as agnostic controllers and subcontrollers, are the essential patterns
acting across these frameworks. So, it's impossible to say which runtime framework in
particular is used for their physical realization.
Business Activity Monitoring
(
BAM
) as
a tool is a part of the broader Service Monitoring solution, incorporated into the Service
Management (that is, Governance) framework; together they form a business and technic-
al service monitoring solution. This solution, among other functions, feeds the error-hand-
ling facility with the information needed for service recovery, both manual and automated.
The
Automated Recovery Tool
(
ART
) is a part of the error handler specific for particular
service inventory, but based on Oracle's common error hospital pattern, which is essen-
tially the implementation of the agnostic service controller SOA pattern linked to the En-
terprise Service Inventory.
The Service Inventory framework during its runtime provides the discoverability of ser-
vices and the service artifact to all runtime frameworks via unified API, constructed ac-
cording to the Service Inventory (Repository) Endpoint pattern. Any service, service
agent, or composition controller in these frameworks could perform the lookup and dis-
covery of any service metadata element according to the
Service Repository
(
SR
) tax-
onomy.
Search WWH ::
Custom Search