Database Reference
In-Depth Information
SAIF BF pro-
cess semantics
SAIF description
Oracle Composition framework
Sequence flow Ordered sequence of actions
Execution plan
Mediator in the SCA Service Broker (
Chapter 3
,
Building the Core - Enterprise
Business Flows
)
Control element that performs branch-
ing, forking, merging, and joining
Gateway
Traditional Integration to Composition - Enterprise Business Services
)
As we can see from this reference table, SAIF-CD is pretty close to our understanding of
the general service taxonomy. We will use the best of these three open frameworks to es-
tablish logically structured, universal, and most importantly, well-performing metadata
storage for runtime and design-time discovery. One open standard remains, which is espe-
cially designed for runtime discovery; it's our "yellow" topic, and we will look at it now.
The UDDI taxonomy (V.3) in Oracle OSR
In contrast to all the possible repository taxonomies and ontologies, Service Registry is
very well standardized. UDDI was one of the cornerstones of contemporary SOA, and
Oracle can offer the latest release compliant with Version 3 of the open standard. To un-
derstand this standard, we must take a look at the
tModel
concept (
http://uddi.org/tax-
onomies/UDDI_CoreOther_tModels.htm
)
as the key aspect of UDDI organization.
In discussing the Open Group Ontology, we mentioned two entities that represent a ser-
vice to consumers and other composition members:
ServiceContract
and
Ser-
viceInterface
. We also mentioned that the definition of
ServiceInterface
is
generic and needs more detail for practical implementation. So, now, we can formulate
that tModel (the technical model) as a complex data type, used for defining and represent-
ing the interface of a service we are going to discover and invoke (dynamically in our
composition controller). In the case of the web service, tModel will at least represent the
Search WWH ::
Custom Search