Diploma Thesis Santiago GÃ³mez SÃ¡ez - IAAS

More documents

Recommendations

Info

5. Design received in the vendor’s communication protocol, e.g. MySQL communication protocol for MySQL database systems, or JSON over HTTP for NoSQL databases, must be marshaled to the NMF structure. The NMF sections we use for incoming requests are the message properties, and the message attachment (see Figure 5.2). In the message properties we attach tenant context information (tenant and user UUID), and the request’s meta-data, which is divided into: • Backend configuration queries: server configuration queries sent prior to the request query, e.g. setting the predefined language, character encoding, etc. These must be executed in the backend database system, and are sent to the backend database system prior to the request query. • Backend data source properties: in this property structure the set of backend data sources meta-data are stored, e.g. access credentials, main (and secondary) information structures names, data source type, etc. • Queries number: the number of queries which are sent as attachment. The default value is one, but in multi-querying this value increases. The NMF body supports text data format. The data transferred to or retrieved from a backend Cloud data store is represented as different data types, e.g. string, integer, float, binary, etc., and must be transferred as binary data. Therefore, the queries contained in the user’s requests are sent in the attachment section of the NMF, which supports objects serialization. The queries are stored in a vector structure which can contain multiple queries. The NMF request must be demarshaled to the appropriate database system’s communication protocol before forwarding the user’s request to the backend database system. Responses from the backend data stores are correlated with the user’s request, marshaled, and sent back in the response NMF (see Figure 5.2). Data retrieved from a data store, e.g. in a data retrieval or update operation, contains both data and meta-data. Both informations are stored in vector structures in the attachment section of the response NMF. In case of error, the error message is stored in the response NMF, and forwarded back to the user. In the message properties section the tenant context information (tenant and user UUID) is stored, and the response meta-data, which contains the following information: • Backend data source properties: in this property structure the set of backend data sources meta-data are stored, e.g. main (and secondary) information structures names, data source type, etc. • Backend data source number: the number of targeted data stores. • Backend operation status: the overall operation status. We consider operations over one or more target data stores as atomic. If one or more backend data stores returns an error, the operation status is set to error, and an error is forwarded back to the user. The message body may be used for sending structured data in XML format. However, we do not send information in this NMF section in this diploma thesis, due to the need to transfer the requests and response data as binary serializable objects (serializable vectors) in order to 54
5.3. SQL Support Architectural Overview avoid errors in the data content if the data is transformed to string, and structured in XML format. 5.3. SQL Support Architectural Overview In this section we provide an overview of a preliminary, and final architectural approaches designed in this diploma thesis, in order to support a transparent data access to backend SQL databases. We first expose the integration approaches we should consider, and the main problems found when implementing the first approach which led us to design a second architectural approach. 5.3.1. Integration As described in Chapter 4, we build the new components in ServiceMix-mt following the OSGi compliance. However, these must interact with components which follow the JBI specification. The integration between components built for different containers in ServiceMix-mt must be done at two levels: messaging, and resources sharing. The ServiceMix-mt NMR API OSGi bundle exposes a set of operations for sending messages through the NMR to a specified target endpoint. Hereby we can perform message exchanges between endpoints configured on OSGi bundles and endpoints configured on JBI components, and provide communication support between components hosted in the two containers. JBI Service Assembly JBI Service Unit 1 xbean.xml META-INF jbi.xml maven properties and pom manifest java classes OSGi Bundle JBI Service Unit 1 xbean.xml META-INF jbi.xml maven properties and pom manifest java classes ... ... JBI Service Unit N JBI Service Unit N META-INF META-INF Legend folder / package file Zip package Jar package Figure 5.3.: ServiceMix 4.x repackaging mechanism for deploying JBI components in OSGi container. The resources sharing integration level refers to the deployment of JBI components in the OSGi container, and the utilization of packages exposed by OSGi bundles in the OSGi container in a loosely coupled manner. The former is part of the integration between containers provided in ServiceMix 4.x versions and described in Figure 5.3. The deployment mechanism of a 55
Page 1:
Institute of Architecture of Applic
Page 5 and 6:
Contents 1. Introduction 1 1.1. Pro
Page 7 and 8:
Contents 7.3.3. Evaluation Analysis
Page 9 and 10:
List of Figures 1.1. Migration Scen
Page 11 and 12:
List of Tables 4.1. Description of
Page 13:
List of Listings 5.1. Tenant-aware
Page 16 and 17:
1. Introduction and multi-protocol
Page 18 and 19: 1. Introduction Definitions List of
Page 20 and 21: 1. Introduction • Implementation,
Page 22 and 23: 2. Fundamentals usage of it. PaaS p
Page 24 and 25: 2. Fundamentals 2.2.1. Enterprise S
Page 26 and 27: 2. Fundamentals through the network
Page 28 and 29: Management Framework Component Fram
Page 30 and 31: 2. Fundamentals corresponding works
Page 32 and 33: 2. Fundamentals the tenant level, b
Page 34 and 35: 2. Fundamentals 2.9. Structured Que
Page 36 and 37: 2. Fundamentals 2.9.2. PostgreSQL D
Page 38 and 39: 2. Fundamentals 2.10.1. Key-value D
Page 40 and 41: 2. Fundamentals User Interface Web
Page 42 and 43: 28 2. Fundamentals
Page 44 and 45: 3. Related Works and balancing the
Page 46 and 47: 3. Related Works store may contain
Page 48 and 49: 3. Related Works In the second plac
Page 50 and 51: 4. Concept and Specification VM0 or
Page 52 and 53: 4. Concept and Specification then f
Page 54 and 55: 4. Concept and Specification 4.3. D
Page 56 and 57: 4. Concept and Specification 4.6. U
Page 58 and 59: 4. Concept and Specification Name G
Page 60 and 61: 4. Concept and Specification Name G
Page 62 and 63: 4. Concept and Specification 4.8.3.
Page 64 and 65: 5. Design stores have two main stor
Page 66 and 67: 5. Design userId serviceName XMLNam
Page 70 and 71: 5. Design JBI SA into an OSGi conta
Page 72 and 73: 5. Design Apache Camel provides a s
Page 74 and 75: 5. Design External Application Lege
Page 76 and 77: 5. Design External Application Exte
Page 78 and 79: 6. Implementation the bundle activa
Page 80 and 81: 6. Implementation each of the queri
Page 82 and 83: 6. Implementation multi-tenancy awa
Page 84 and 85: 6. Implementation The HTTP endpoint
Page 86 and 87: 6. Implementation stored. Both auth
Page 88 and 89: 74 6. Implementation
Page 90 and 91: 7. Validation and Evaluation We mus
Page 92 and 93: 7. Validation and Evaluation When t
Page 94 and 95: 7. Validation and Evaluation in the
Page 96 and 97: 1. Introduction 1. Introduction 7.
Page 98 and 99: 7. Validation and Evaluation proble
Page 100 and 101: 7. Validation and Evaluation access
Page 102 and 103: 8. Outcome and Future Work The func
Page 104 and 105: 90 8. Outcome and Future Work
Page 106 and 107: Appendix A. Components A.2. CDASMix
Page 108 and 109: 94 Appendix A. Components
Page 110 and 111: Appendix B. Messages 20 - target da
Page 112 and 113: Appendix B. Messages 110 111 - OK r
Page 114 and 115: Appendix B. Messages 1 interface: l
Page 116 and 117: 102 Appendix B. Messages
Page 118 and 119:
Bibliography [CC06] F. Chong and G.
Page 120 and 121:
Bibliography [SAS + 12] [SBK + 12]
Page 122 and 123:
Acknowledgement I am heartily thank
show all

Diploma Thesis Santiago GÃ³mez SÃ¡ez - IAAS

Create successful ePaper yourself

Delete template?

Save as template?