Diploma Thesis Santiago Gómez Sáez - IAAS

2. Fundamentals
the tenant level, but also isolation at the user level. We discuss this requirement in detail in
Chapters 4 and 5.
4. Concept and
4. Concept
Specification
and Specification
4. Concept and Specification
Backend
Web-Service
Tenant1
4. Concept and Specification
!"#$%&%"' WSDL
!"#$%&%"' WSDL
!"#$%&%"' WSDL
!"#$%&%"' WSDL
Backend
Web-Service
Tenant2
JBI Environment
Figure 4.1.: Overview of the system JBIMulti2. Arrows illustrate data flow between core
components and resources.
Figure 4.1.: Overview of the system JBIMulti2. Arrows illustrate data flow between core
system is called JBI Multi-tenancy Multi-container Support (JBIMulti2), because it supports
components and resources.
many tenants and a cluster of ServiceMix instances.
!"#$%#&%'()%*+$")&,#-)(*,.&*/'$%'$0*1.23.$)$"(*
JBIMulti2 relies on three data resources: the Tenant Registry, the Service Registry, and the
system is called JBI Multi-tenancy Multi-container Support (JBIMulti2), because it supports
Configuration Registry. Tenant contexts are obtained from the Tenant Registry. It delivers tenant
Figure 4.1.: Overview many of the tenants systemand JBIMulti2. a cluster Arrows of ServiceMix illustrate data instances.
Figure 4.1.: Overview ofusers the system and their JBIMulti2. role inside Arrows the illustrate corresponding data flowtenant between(see flow
coreSect. between 4.3.2). coreThe Service Registry
stores components service JBIMulti2 and assemblies resources. relies on andthree service data descriptions resources: for theeach Tenant tenant, Registry, whilethe isolating Service the Registry, data of and the
components and resources.
!"#$%&'()*+,)--%.)+/"01)#+
differentConfiguration tenants (see Sect. Registry. 4.2). Tenant All other contexts non-tenant are obtained relatedfrom andthe tenant Tenant related Registry. data is It stored delivers tenant
by the Configuration users and their Registry. role inside This includes the corresponding configurations tenant created (see by Sect. system 4.3.2). administrators
The Service Registry
or tenantstores administrators. service assemblies As service andassemblies service descriptions and services forare each stored tenant, to awhile separate isolating Service the data of
system is called
system
JBI
is
Multi-tenancy
calledRegistry, JBI Multi-tenancy different they must tenants not
Multi-container
Multi-container be(see stored Sect. to4.2). Support (JBIMulti2),
Support the All Configuration other (JBIMulti2), non-tenant Registry
because it supports
because related (see it supports Sect. and tenant 4.3.3). related data is stored
by the Configuration Registry. This includes configurations created by system administrators
!"#$%#&%'()%*+$")&,#-)(*,.&*!)&/'-)*0$1'$)(*
many tenants
many
and
tenants
a cluster
and We propose
of ServiceMix
a clusteraof graphical
instances.
ServiceMix Web-based instances. user interface named Web UI that exposes the functionality
or tenant administrators. As service assemblies and services are stored to a separate Service
of JBIMulti2. It can be used by system administrators and tenant users and supports all
Registry, they must not be stored to the Configuration Registry (see Sect. 4.3.3).
use cases listed in Section 4.4. Likewise, all functionality supported by the Web UI must be
JBIMulti2 relies
JBIMulti2
on three
relies
data
on
resources:
three data
the
resources:
Tenant Registry,
the Tenant
the
Registry,
Service Registry,
the Service
and
Registry,
the
and the
supported Weby propose a Web aService graphical APIWeb-based well (seeuser Sect. interface 4.5.2). Currently, named Web the UIprototype that exposes developed the functionality
Configuration
Configuration
Registry. Tenant
Registry. within
contexts
Tenant the of scope JBIMulti2.
are obtained
contexts of this are Itdiploma can
from
obtained be used thesis
the Tenant
frombyonly Registry.
the system Tenant implements administrators
It delivers
Registry. the
tenant
ItWeb delivers and Service tenant API. users However, and supports a all
concept for usethe cases layout listedof the Section Web UI 4.4. can Likewise, be foundall infunctionality Section 4.5.1. supported by the Web UI must be
users and their
users
role
and
inside
their
the
role
corresponding
inside supported corresponding
tenant (see Sect.
tenant
4.3.2).
(see Sect.
The Service
4.3.2). The
Registry
Service Registry
The preceding components Legend by a Web Service API
are built on(1) as
top and well
of (2): SOAP (see
Integration over Sect. 4.5.2). Currently, the prototype developed
Layer that encapsulates the access
stores service
stores
assemblies
service
and
assemblies within
service descriptions
and service the scope descriptions of this diploma
to databases and the ServiceMix for each tenant, clusters. for each HTTP thesis
while Moreover, Consumer tenant, only
isolating
while implements
the
isolating
data of
thedata Webof
Service API. However, a
it can initiate atomic transactions among
concept for the layoutEndpoint
of the Web
different tenants
different
(see
tenants the
Sect. 4.2).
(see resources.
All
Sect.
other
4.2). An
non-tenant
All extension other
related
non-tenant component Endpoints
UI can be found in Section 4.5.1.
and tenant
related for ServiceMix
related
and tenant provides
data
related
is stored
data integration is storedwith JBIMulti2.
It installs The JBI preceding components, components Interface
processes are(3) service built and (4): onassemblies SOAP top of over an Integration by adding Layer a tenant that encapsulates context, andthe access
by the Configuration
by the Configuration deploys Registry. This
Registry. to service databases includes
This assemblies. configurations
includes and theOnce configurations ServiceMix ESB deployed, created by system
created
administrators
by system administrators
HTTP clusters. Provider a service Moreover, Endpoints assembly it canmust initiate notatomic interfere transactions with the among
or tenant administrators.
or tenant administrators. service assemblies the resources.
As assemblies
As service of
and
assemblies other An extension tenants. Endpointcomponent services
and To
are
services ensure
stored to
are data for ServiceMix
a separate
stored isolation, to
Service
a separate the provides tenant integration Service context inside withthe
JBIMulti2.
service units It installs of a service JBI components, assembly is processes processed service by a setassemblies of new BCsby andadding SEs. JBI a components
tenant context, and
Registry, they
Registry,
must not
they
be
must
stored
notdeploys to
be
the
storedservice Configuration the assemblies. Configuration Once Bidirectional
Registry (see
Registry deployed,
Sect. 4.3.3).
(see Sect. a service 4.3.3). assembly must not interfere with the
service assemblies of other tenants. Communication To ensure data isolation, the tenant context inside the
service units of a service assembly is processed by a set of new BCs and SEs. JBI components
We propose a
We
graphical
propose
Web-based
a graphical 24
user
Web-based
interface
user
named
interface
Web UI
named
that exposes
Web UI that
the functionality
exposes the functionality
of JBIMulti2.
of
It
JBIMulti2.
can be used
It can
by
be
system
used
administrators
by system administrators
and tenant users
and tenant
and supports
users and
all
supports all
use cases listed
use
in
cases
Section
listed
4.4.
in
Likewise,
Section 24 4.4.
all
Likewise,
functionality
all functionality
supported by
supported
the Web UI
by
must
the Web
be
UI must be
supported by
supported
a Web Service
by a
API
Web
as
Service
well (see
API
Sect.
as well
4.5.2).
(see
Currently,
Sect. 4.5.2).
the
Currently,
prototype
the
developed
prototype developed
within the scope
within
of
the
this
scope
diploma
of this
thesis
diploma
only implements
thesis only implements
the Web Service
the Web
API.
Service
However,
API.
a
However, a
concept for the
concept
layout
for
of
the
the
layout
Web UI
of
can
the
be
Web
found
UI can
in Section
be found
4.5.1.
in Section 4.5.1.
The preceding
The
components
preceding components
are built on top
are
of
built
an
on
Integration
top of an
Layer
Integration
that encapsulates
Layer that encapsulates
the access
the access
to databases
to
and
databases
the ServiceMix
and the
clusters.
ServiceMix
Moreover,
clusters.
it
Moreover,
can initiate
it
atomic
can initiate
transactions
atomic transactions
among
among
the resources. the An resources. extension An component extension for component ServiceMix for provides ServiceMix integration provides with integration JBIMulti2.
with JBIMulti2.
It installs JBI
It
components,
installs JBI components,
processes service
processes
assemblies
service
by
assemblies
adding a
by
tenant
adding
context,
a tenant
and
context, and
deploys service
deploys
assemblies.
service assemblies.
Once deployed,
Once
a
deployed,
service assembly
a service
must
assembly
not interfere
must not
with
interfere
the
with the
service assemblies
service
of
assemblies
other tenants.
of other
To ensure
tenants.
data
To ensure
isolation,
data
the
isolation,
tenant context
the tenant
inside
context
the
inside the
service units
service
of a service
units
assembly
of a service
is processed
assembly is
by
processed
a set of new
by a
BCs
set
and
of new
SEs.
BCs
JBI
and
components
SEs. JBI components
Figure 2.5.: Multi-tenant HTTP Binding Component [Sá12].
As seen in Figure 2.5, the multi-tenant HTTP BC is mainly used in ServiceMix-mt to support
the SOAP over HTTP communication protocol by exposing a Web service in the tenantaware
consumer endpoint and consuming an external Web service in the provider endpoint.
SOAP defines an XML message 24 format
24
which is sent over the network and a set of rules
for processing the SOAP message in the different SOAP nodes which build the message
path between two endpoints [WCL + 05]. A SOAP message is a composition of three main
elements: a SOAP envelope, header, and body. A SOAP envelope may contain zero or
more headers and one body. The header may contain processing or authentication data
for the ultimate receiver or for the intermediate nodes through the message is routed. The
message payload or business data is included in the SOAP body. SOAP is used as a message
framework for accessing Web services in loosely coupled infrastructures [WCL + 05]. The Web
service consumer specifies the functionality to invoke in the SOAP body. If the Web service
functionality has a request-response Message Exchange Patterns (MEP), a SOAP message
is used to send the response data when the corresponding operation has been executed
successfully or the error data in case an error occurred during execution.
Most of the Cloud storage providers provide an HTTP interface to the tenants for data
management, retrieval, and storage. In this diploma thesis we extend this JBI BC in order to
provide the tenant a transparent access to his NoSQL Cloud data stores.
2.8. Service Engine
A SE can provide different kinds of services, e.g. business logic, routing, and message
transformation. In this diploma thesis we will mainly concentrate on one: Apache Camel
[APA11a], which is wrapped in a ServiceMix-camel JBI SE in ServiceMix, and in a ServiceMixcamel-mt
JBI SE in ServiceMix-mt for multi-tenancy awareness..
18