Information Technology Reference
In-Depth Information
generic operations divided to syntactic, semantic,
behavioral and qualitative operations. Starting
from this point, new categorizing level has to
be done by the help of cloud provider (see next
paragraph) who will have the responsibility of
grouping WSs in clouds. The classifying will be
based on the business domain of interest, each of
these clouds is itself a WS and the cloud provider
will advertise them in the WS directory.
At this point the WS provider system will search
in the directory for its cloud based on its business
domain's interests and will register itself in one
of them to later on entail the required concepts
out of that cloud and implement its own WSs to
be registered also in it, and if there is no cloud
matches with its purposes, the service provider
will ask the cloud provider to create a new one
and advertise it in the directory as well, and here
the concepts will be inherit from the metadata
cloud ontology.
The process of adding semantic on WS request
and capability will take benefits from the semantic
mediator-based system functionality by submitting
semantic goal to be fulfilled with SWS capability.
The mediation issues will be also applied depend-
ing on the variety of mediators provided by the
mediator-based system as well.
At the later stages, the model will be applied
on one of the business applications like ERP to
have semi-automated solution in the ERP world,
and by using a workflow system we can use the
market best practices by storing workflows in
an internal database. Everything mentioned here
will be described later on in more details in the
following sections.
This subsystem is able to generate user
screens at runtime.
•
Workflow System: Deals with business
processes described in an appropriate
XML-based workflow language.
•
Web Service Consumer System: Contains
XML schema definitions and functions
needed for the processes of WS discovery
and invocation provided by different ser-
vice providers.
•
Web Service Provider System: It deals with
HTTP incoming and outgoing user's re-
quests and contains functions required for
providing Web Services, and has connec-
tion to WS directory to allow the publica-
tion of them. And it has also a connection
to the validation system in order to validate
its Web Services before being annotated
with semantics.
•
Web Service Directory: Its interface has
the responsibility of the publication and
searching for WSs following the highly de-
fined WS requests (semantic goals) provid-
ed by the WS consumer system, it resides
in the validation system and has a link to
the validation repository so that it can store
data about Web Services to be used for the
validation process.
•
Semantic Web Service System: The main
two entities that have interactions with this
component are the cloud ontology and the
clouds. The cloud ontology is a metadata
ontology that serves as a base to provide
concepts leading the process of creating
the clouds and the Web Services within
them by enabling derivation of the con-
cepts descriptions from the ontology. The
clouds are defined by the cloud provider.
Clouds are services themselves, and can
be created, advertised, discovered and in-
voked in the traditional way. Each cloud
has a category type and generic operations.
In addition, clouds are published in the WS
component description
The Semantic SOA-based model has the follow-
ing components:
•
User System: Implements functions that
will be used in the end users interfaces.
Search WWH ::
Custom Search