Diploma Thesis Santiago Gómez Sáez - IAAS

6.2. NoSQL Support Implementation
17 "AttributesToGet":
18 ["score"]
19 }
20 }
21 }
Listing 6.4: Amazon Dynamo DB JSON over HTTP sample request [Amaa].
Marshaling operations in the HTTP JBI BC are provided in the classes DefaultHttpConsumer-
Marshaler, and DefaultHttpProviderMarshaler. Hence, we start the extension of the marshalers
at this point. On the other hand, the marshalers do not support marshaling of JSON content,
as the NMF stores XML format. Therefore, we include JSON marshaling operations which are
provided by the Jackson v1.8.9 [Cod]. We select this version, as is the one provided in Amazon’s
AWS SDK [Amag]. We provide a marshaler handler interface, which is implemented for
the different Cloud data store providers. The handler is chosen based on the HTTP headers or
target HTTP URL content (see Listings 6.4 and 6.5). As in the MySQL approach, marshaling
operations include filling the NMF properties with the tenant’s source and backend data
source configuration data retrieved from the service registry, and storage of the HTTP request
content as an attachment. Properties and attachments identifiers are listed in the NMConstants
class.
1 - Request -
2 POST /upload/storage/v1beta1/b/myBucket/o?uploadType=media&name=myObject HTTP/1.1
3 Host: www.googleapis.com
4 Content-Type: image/jpeg
5 Content-Length: number_of_bytes_in_JPEG_file
6 Authorization: your_auth_token
7
8 {JPEG data}
9
10
11 - Response -
12 HTTP/1.1 200
13 Content-Type: application/json
14
15 {
16 "name": "myObject"
17 }
Listing 6.5: Google Coud Storage JSON over HTTP sample request [Gooc].
The same method described above applies in the HTTP provider endpoints. Demarshaling
operations in the multi-tenant aware provider endpoint create the HTTP requests for each
Cloud provider (see Listings 6.4 and 6.5) in a separate handler, based on the target data store
properties which are stored in the NMF.
Authentication mechanisms in the HTTP consumer endpoint processor rely on the tenant
and user UUIDs, and follow Gomez’s approach [Sá12]. However, we do not retrieve the
UUIDs from the SOAP header, but from the HTTP header where the authentication data is
71