Diploma Thesis Santiago Gómez Sáez - IAAS

6. Implementation
The HTTP endpoint configuration is described in the xbean.xml file of the SU, and its XML
format complies the Spring specification. The XBeanDeployerMT class extends the original
BaseXBeanDeployer class in ServiceMix, which performs the loading of the endpoint properties,
and the creation and configuration of the deployed endpoint. The XBeanDeployerMT created in
Muhler’s work provides the operations which inject tenant information in the endpoint’s URI
during the deployment process [Muh12]. We modify such operations in order to inject tenant
and user information in the endpoint’s URI during the endpoint creation. The HTTP consumer
and provider endpoints are described in the HttpConsumerEndpoint and HttpProviderEndpoint
respectively. The former implements the necessary operations for accepting incoming HTTP
requests to ServiceMix-mt, while the latter implements the operations to communicate with an
external HTTP server. Both endpoints are created on a Jetty server, which provides an interface
for sending HTTP requests, and listening on a specific port for incoming HTTP requests.
Therefore, the endpoints process incoming, and outgoing requests. Request messages are
marshaled and demarshaled into or from the NMF, a message exchange is created, and the
response message is correlated with the initial request.
As described in Chapter 3, the different NoSQL Cloud data store provider products available
nowadays belong to a specific NoSQL family, but the naming the Cloud providers use to
identify the storage structures is different. We address this issue in Chapter 5, but we find
further issues in its communication protocol. Although most of the NoSQL Cloud data store
providers, e.g. Amazon [Amaa], Google Cloud Storage [Gooc], provide a REST interface for
accessing their stores, the HTTP content and header values are not standardized between the
providers. For this reason, they provide their users their Java SDKs for accessing the Cloud
services. Operations on the driver’s API create the JSON over HTTP requests. Furthermore,
MongoDB [10G] does not provide a REST interface, but there are several external projects
which create an Jetty HTTP server, and transform the HTTP requests into parameters of the
Mongo Java SDK. For these reason we are not able to provide a standardized marshaling
interface in the HTTP JBI BC for all the Cloud data store providers, but we concentrate on the
three which we mention before.
1 POST / HTTP/1.1
2 host: dynamodb.us-east-1.amazonaws.com
3 x-amz-date: Mon, 16 Jan 2012 17:49:52 GMT
4 x-amz-target: DynamoDB_20111205.CreateTable
5 Authorization: AWS4-HMAC-SHA256 Credential=AccessKeyID/20120116/us-east-1/dynamodb/
aws4_request,SignedHeaders=host;x-amz-date;x-amz-target,Signature=145
b1567ab3c50d929412f28f52c45dbf1e63ec5c66023d232a539a4afd11fd9
6 content-type: application/x-amz-json-1.0
7 content-length: 23
8 connection: Keep-Alive
9
10
11 {"RequestItems":
12 {"highscores":
13 {"Keys":
14 [{"HashKeyElement":{"S":"Dave"}},
15 {"HashKeyElement":{"S":"John"}},
16 {"HashKeyElement":{"S":"Jane"}}],
70