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

More documents

Recommendations

Info

7. Validation and Evaluation When the source and target data source configuration are registered, the tenant operator (or through the Cloud Data Migration Tool) can register the storage structure meta-data of his database. For example, for a MySQL database system instance in Amazon RDS, the tenant operator must provide the tables’ name (see Listing 7.2), or for a bucket stored in a backend Google Cloud Storage container the tenant must provide the bucket identifier. 1 2 3 4 ${tenantProperties#taxiCompany-UUID} 5 ${tenantUserProperties#tenantOperatorA} 6 7 password 8 tenantOperatorApw 9 10 11 12 13 14 servicemix.cdasmix.jbi.http-SA 15 dataSourceTest1 16 nosql-bucket-object-5.1.3 17 dynamodb 18 dynamodb#datasourcej 19 nosqlKeyValue-table-item-1.0 20 nosqlKeyValue-table-item-1.0 21 customers 22 customer1 23 24 25 Listing 7.3: Add Source and Target NoSQL Secondary Information Structure SOAP over HTTP sample request. Registration of secondary information structure meta-data applies only for NoSQL databases. The message described in Listing 7.3 contains the registration meta-data for an item stored in a table in the Amazon DynamoDB infrastructure. After the migrated data’s meta-data is registered in the system, the tenant operator can access transparently the system using the standardized database access protocols, e.g. MySQL for the MySQL database system, and HTTP for NoSQL databases. 1 ... 2 3 connect = DriverManager 4 .getConnection( 78
7.2. Validation 5 "jdbc:mysql://" + "IPADDRESS" + ":3311/" + DB +"?allowMultiQueries=true; cacheServerConfiguration=true&" + 6 "jdbcCompliantTruncation=false&zeroDateTimeBehavior=convertToNull&tinyInt1isBit= false&allowMultiQueries=true&yearIsDateType=false", 7 TENANT_ID + "#" + USER_ID,"tenant1password"); 8 10 11 9 ... 12 resultSet = executeQuery(connect, "select ID from customer; select * from mainInfoTest4;" + 13 "select * from mainInfoTest4 as t1, mainInfoTest1 as t2 where t1.ID = t2.ID;"); 14 while (resultSet.next()) { 15 System.out.println("IDs " + resultSet.getInt("C_CUSTKEY")); 16 } 17 if (statement.getMoreResults()) { 18 ResultSet nextRs = statement.getResultSet(); 19 while (nextRs.next()) { 20 System.out.println("ID_" + nextRs.getInt("ID")); 21 System.out.println("Name_" + nextRs.getString("Name")); 22 System.out.println("SecondName_" + nextRs.getString("SecondName")); 23 } 24 } 25 if (statement.getMoreResults()) { 26 ResultSet nextRs = statement.getResultSet(); 27 while (nextRs.next()) { 28 System.out.println("ColumnCount:_" + nextRs.getMetaData().getColumnCount()); 29 System.out.println("ID1_" + nextRs.getInt(1)); 30 System.out.println("name_" + nextRs.getString(2)); 31 System.out.println("SecondName_" + nextRs.getString(3)); 32 System.out.println("ID2_" + nextRs.getInt(4)); 33 System.out.println("name_" + nextRs.getString(5)); 34 } 35 } 36 37 ... Listing 7.4: Retrieve data via JDBC and MySQL protocol migrated to a backend Cloud data store, or local database system. In Listing 7.4 we provide part of a Java program which connects via the MySQL Connector/J native driver with the MySQL CDASMix Proxy component on the port 3311. The options attached to the connection URL must be set as in the provided code in order to increase the performance of the communication, e.g. multi-querying for multiple queries in one statement, cache server configuration in order not to request the server configuration data per request, etc. In the MySQL request in Listing 7.4, the tenant operator authenticates with the tenant and user UUID, and its password. Password is read in the system, but it is not compared in the authentication process, as the CDASMix MySQL proxy does not implement the hashing mechanisms of a MySQL server. After successful authentication, it executes a query which contains multiple queries in the same request. Each query is processed independently in the system when retrieving information from the different backend database systems, e.g. the customer table is stored in Amazon RDS, while mainInfoTest4 and mainInfoTest1 are stored 79
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 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 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?