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

More documents

Recommendations

Info

5. Design External Application External Application BackendProviderAPI (POST) BackendProviderAPI (POST) Amazon Dynamo Google App Engine OSGi JBI Environment Registry- Cache Bundle NoSQL Cache instance (*) (**) !"#$%#&%'()%*+$")&,#-)(*,.&*/'$%'$0*1.23.$)$"(* !"#$%&'()*+,)--%.)+/"01)#+ !"#$%#&%'()%*+$")&,#-)(*,.&*!)&/'-)*0$1'$)(* Legend PostgreSQL ServiceR egistry Endpoint Interface ESB Endpoint (*) Query and data transformation might exist Multi-tenant context & messaging Figure 5.6.: Architectural overview of the design approach to support JSON over HTTP communication protocol and routing to NoSQL data stores. When query or data transformation is needed, the message is forwarded from the HTTP consumer to the transformer component’s endpoint, which must then forward the message to the HTTP provider endpoint. 62
6. Implementation In this chapter we describe the challenges and problems during the implementation phase to fulfill the requirements specified in Chapter 4 and the design presented in Chapter 5 of the system. Furthermore, we discuss the incompatibilities found with components we must extend. We divide, as in the previous chapters, the implementation phase into the SQL and NoSQL databases support, and provide a separate section for the extensions made to JBIMulti2 and the Cache. 6.1. SQL Support Implementation The implementation of the different components described in the SQL architecture approaches in Chapter 5 are explained in this section. We describe the implementation of the three main components which provide support for MySQL incoming requests, and a multi-database protocol for outgoing requests. NMF routing in ServiceMix-mt is supported by the NMR and a set of endpoints which are deployed on the ServiceMix-camel, and ServiceMix-camel-mt. 6.1.1. CDASMix MySQL Proxy The CDASMix MySQL Proxy provides support for MySQL connections. It implements the functionalities of a MySQL proxy and the needed routing operations and transformation to integrate it in ServiceMix-mt. As discussed in Chapter 3, the original MySQL proxy is implemented in the C programming language. Therefore, we cannot integrate it with ServiceMix-mt, as this runs on a Java platform. The Myosotis Tungsten Connector is part of a data replication engine developed by Continuent, Inc [Con]. One of the components which build the application is a MySQL proxy written in the Java programming language. This component suites the proxying requirements in this diploma thesis, and it runs on the Java platform. However, it is not OSGi compliant, it is not integrated with the JBI environment, and the backend databases’ meta-data must be explicitly defined in its configuration file. Furthermore, it provides a direct connection from the component to the database. We utilize it as a base for implementing the CDASMix MySQL Proxy, and aggregate the required functionalities of this diploma thesis. We present the class diagram of the component in Section A.1, but omit the attributes and operations listings due to the high amount of operations, and attributes we manage in the component. ServiceMix-mt is built as an OSGi container with JBI integration functionalities. Furthermore, ServiceMix 4.x and later version consider the JBI framework deprecated in their systems. Therefore, we build the CDASMix MySQL Proxy component as an OSGi bundle. During 63
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 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 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?