Database Reference
In-Depth Information
Automated recovery concepts
Business Flows
,
Chapter 4
,
From Traditional Integration to Composition - Enterprise
Business Services
, and
Chapter 5
,
Maintaining the Core - the Service Repository
, and from
this one, we can assume the following:
1. The Service Repository with all the service metadata elements is properly main-
tained. We have clear associations between services, endpoints, and Audit mes-
sages under the roof of processes. Simply put, every process has a distinct service
invocations footprint. Technically, it can be presented as a master
tModel
for a
task-orchestrated service if we look at the UDDI analogy.
Tip
The preceding assumption is too bold. In dynamic compositions, the sequence of
service invocations and even the number of invocations (that is, footprint) can be
different for the same abstractly defined process. The key here is to watch out for
the services with specific service roles, sometimes ignoring low-level composition
members.
2. Auditing a sequence is strictly observed, which means that we can always find re-
cords in logs according to the declared design rules. Simply put, we can always re-
construct the process path from the logs in the exact way as we see it in the Oracle
SCA Enterprise Management Console (instances).
3. Every service (Entity or Task) is clearly documented in ESR in terms of execution
policy, performance, and consumed resources. Generally, from practical tests and
business requirements, we should know that an end-to-end time of 700 ms for this
service is acceptable, but 1200 ms is not.
4. Our unified composition descriptors (EPs and routing slips) are redundantly imple-
mented by ESR and FSO/NAS. They are critical for any type of composition con-
trollers (dynamic or static), and redundant implementation of this part in not ex-
pensive if we decide to keep the XML EP definitions as files in parallel with DB
storage (which is SAN/RAC-based).
Services
, in the
A simplified Message Broker implementation
section, we learned
that the design and deployment of a simple service broker for most of our composi-
tions (and definitely for all compensative compositions as well) is absolutely
achievable outside of OFM.
Search WWH ::
Custom Search