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

More documents

Recommendations

Info

7. Validation and Evaluation We must maximize the approximation of the testing and evaluation scenarios with the motivating scenario. Therefore, we perform the testing cases from a local machine in the University of Stuttgart network infrastructure, in order to simulate the access to the data from an on-premise data access layer. Communication with the JBIMulti2 application for tenant configuration, and deployment of SAs is established using soapUI 3.6. Communication with the MySQL endpoint in ServiceMix-mt is established using the MySQL Connector/J 5.1.22, while for the different tenant-aware HTTP endpoints we use the Java libraries provided by the Cloud data store providers. 7.2. Validation In this section we provide an overview of the messages, and programs used for the validation of the prototype. The transmission of the following message samples requires the system to be started, and the operations until the deployment of the tenant operator’s SA to be executed. These messages are provided in a soapUI test suite shipped with the prototype. From the moment when the tenant deploys the SA, the configuration of the frontend and backend data stores can be associated to it. The data store configuration is done through the execution of operations which are accessible through a Web service interface. Therefore, either the Cloud Data Migration Tool, or the tenant can configure their database connections through the ESB to the backend Cloud data store where his data is migrated to. 1 2 3 4 ${tenantProperties#taxiCompany-UUID} 5 ${tenantUserProperties#tenantOperatorA} 6 7 password 8 tenantOperatorApw 9 10 11 12 13 14 servicemix.cdasmix.jbi.camel-SA 15 tenant1tpchaws 16 mysql-database-table-5.1.3 17 mysql 18 localhost:3311 19 tenant1tpchaws 20 mysql-database-table-5.1.3 21 mysql 22 tenant1tpchaws.c0giusfeitsw.us-east-1.rds.amazonaws. com:3306/tenant1tpchaws 76
7.2. Validation 23 com.mysql.jdbc.Driver 24 tenant1user1tpch 25 passwordtenant1user1 26 27 28 Listing 7.1: Add Source and Target SQL Data Source SOAP over HTTP sample request. The message described in Listing 7.1 contains the needed information for registering and providing access to the tenant operator A in the MySQL CDASMix Proxy, and connecting with an SQL database system in a backend Cloud data store. The tenant operator must authenticate with JBIMulti2 in order to register the connection meta-data, e.g. protocol, URL, database type, access credentials, etc. In Listing 7.1 the tenant operator A, which is a user of the tenant Taxi Company, registers for the endpoint configuration described in the servicemix.cdasmix.jbi.camelSA a connection with a MySQL 5.1.3 database system instance in the Amazon RDS infrastructure. When more than one target database system wants to be attached to an existing source data source registered in the system, this provides the AttachTargetDataSource operation, which has as pre-condition the existence of the specified source data source. 1 2 3 4 ${tenantProperties#taxiCompany-UUID} 5 ${tenantUserProperties#tenantOperatorA} 6 7 password 8 tenantOperatorApw 9 10 11 12 13 14 servicemix.cdasmix.jbi.camel-SA 15 tenant1tpchaws 16 tenant1tpchaws 17 mysql-database-table-5.1.3 18 mysql-database-table-5.1.3 19 customer 20 21 22 Listing 7.2: Add Source and Target SQL Main Information Structure SOAP over HTTP sample request. 77
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 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?