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

More documents

Recommendations

Info

4. Concept and Specification VM0 or VM1 VM1 Java 6 (JDK) JOnAS v5.3.0 CloudDataMigrationTool JBIMulti2 MigrationDB External Application PostgreSQL T1U1 Data Access Layer (MySQL ConnectorJ) External Application TenantRegistry Config.Registry ServiceRegistry T1U2 Data Access Layer (MySQL ConnectorJ) External Application Extended Apache ServiceMix-mt T2U1 BackendProviderAPI (POST) External Application MySQL PostgreSQL T2U2 BackendProviderAPI (POST) Legend Amazon RDS MySQL Oracle ... Google Cloud Storage Sql requests TiUj NoSql requests Tenant i User j Amazon DynamoDB Figure 4.1.: Transparent Cloud data access system overview, including the Cloud Data Migration Application [Bac12]. Note: represents the system in the post-migration phase The transparent Cloud data access access support is achieved by the interaction of three main components: JBIMulti2, registries containing tenant-aware information, and an extended version of ServiceMix-mt (see Figure 4.1). JBIMulti2 deploys in ServiceMix-mt the SAs containing the endpoint and routing configurations selected by the tenant, which support two different communication protocols: MySQL and HTTP. From this point the DAL of the tenant’s application can retrieve and modify data in his data container in the Cloud through the ESB connecting to a single logical endpoint which connects to multiple physical backend data stores. In our approach we provide also the possibility, either to configure a connection to the traditional database, e.g. when a hybrid model is pursued, or to utilize a DBMS provided in our system, which is described in the following subsection. 36
4.1. System Overview 4.1.1. Components In Figure 4.2 we specify the main components which build the subsystem mentioned in Section 4.1. We highlight the components which require an extension, and the new components which are implemented and included in the system. Web UI Web Service API Business Logic Data Access Bus TenantRegistry JMS Management Service MySQL Proxy (port 3311) Cache SQL Config.Registry ServiceRegistry Normalized Message Router On-premise On-premise Data Source T3 On-premise Data Source T2 Data Source T1 Cache NoSQL HTTP-mt BC Camel-mt SE Camel JDBCCdasMix Legend Ti Internal Bidirectional Communication External Application External Cloud data store External Bidirectional Communication Tenant i Extended Components New Components Figure 4.2.: Transparent Cloud data access components overview. As described in Section 4.1, we extend the JBIMulti2 Web service API and its associated business logic. The operations we include perform access and modifications to one particular registry: the Service Registry. This registry persists information about services, its policies, and SAs deployed by one tenant. The last kind of information is the one we mainly focus on, due to the information which is contained in it: the tenant-aware endpoint configuration in ServiceMix-mt. Therefore, we extend this registry to persist the configuration about the data stores. We make a differentiation between data stores and name it source and target data sources, to be able to relate the one that the tenant physically accesses and the one which the tenant logically accesses, which is the one that the system physically accesses. To support transparent access to two different database types, we divide our architecture and implementation into the the communication protocols they support: MySQL for MySQL databases, and HTTP for NoSQL databases (see Figure 4.2). For the first one, the single access physical endpoint is provided through a TCP port, which 37
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 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 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?