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

More documents

Recommendations

Info

5. Design userId serviceName XMLNamespace interfaceName tenantId Service (1,n) implements (1,n) ServiceInterface wsdlFile (1,n) policyFile has (1,1) Policy policyName zipFile SAName userId dsName userId dsLocation Id dsBean Name ServiceAssembly (1,1) tenantId tenantId correlates dsType dsProtocol dsEndpoint URL dsNativeDriver Name dsUser id locationId dsPssw (0,n) TenantBackendDS (1,1) refersTo (1,1) (1,n) stores (1,n) MainInfoStructure name (1,1) tenantId locationId id contains (0,n) SecondaryInfoStructure tenantId name Figure 5.1.: Extended service registry ER Diagram using (Min, Max) notation. Note: extended from outputs in [Muh12] and [Ura12] 52
5.2. Normalized Message Format 5.2. Normalized Message Format In this diploma thesis we modify the NMF design in [Sá12], due to the different data types which are transferred in it. Gomez presents a NMF where the data is transferred in its body in XML format, which suites for the communication protocols his prototype supports (SOAP, JMS, and E-mail), and the text data type contained in the requests. Furthermore, the multi-tenant aware routing supported in his approach is static between endpoints (e.g. one incoming request is routed from one tenant’s consumer endpoint to one tenant’s provider endpoint). The complexity of the data types transferred in the system and the dynamic routing between backend Cloud data stores leads us to modify the meta-data transported in the NMF properties section, and to send the data in the attachment section. We are also forced to design two different data structures for the NMF: one for request messages, and another for response messages. The data and meta-data contained in the MySQL requests and responses messages require the utilization of different data structures to transmit them in the NMF (see Listing B.1). MySQL requests contain user, authentication, etc. meta-data, while the MySQL response contain meta-data which describes the data transferred. Message Properties TenantID UserID Backend config. queries Backend datasource properties Queries number TenantID Message Properties UserID Backend datasource properties Backend datasources number Backend operation status Message Payload Message Payload Queries Message Attachments Message Attachments Queries results OR Queries results meta-data Error Message Request Message Response Message Figure 5.2.: Design of the Normalized Message Format used in the system. Data access or modification requests to backend data stores through ServiceMix-mt are 53
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 68 and 69: 5. Design received in the vendor’
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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?