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

More documents

Recommendations

Info

4. Concept and Specification Name Goal Actor Pre-Condition Post-Condition Post-Condition Special Case Normal Case in Register Secondary Information Structure The tenant operator registeres a secondary information structure and associates it with the specified source and target main information structure. Tenant Operator The tenant operator has the permissions in the service unit contingent, has registered a source and target data source, has registered a source and target main information structure, and the source and target datasources are NoSQL databases. The source and target secondary information structure meta-data are registered successfully, and associated with the specified source and target main information structure. Source and target secondary information structure are not registered, and are not associated with the specified source and target main information structure. 1. The tenant operator selects the service assembly to which the source data source is already associated. 2. The tenant operator selects the source and target data source to which the main information structure are associated. 3. The tenant operator selects the source and target main information structure to which the secondary information structure is associated. 4. The source and target secondary information structure are registered and associated with their source and target main information structure. Special Cases 1a. The service assembly does not exist. a) The system shows an error message and aborts. 2a. The source or target data source does not exist. a) The system shows an error message and aborts. 2b. The source and target data source is a MySQL database. a) The system shows an error message and aborts. 3a. The main source or target information structure does not exist. a) The system shows an error message and aborts. 4a. The secondary source or target information structure already exists. a) The system shows an error message and aborts. Table 4.4.: Description of Use Case Register Secondary Information Structure. 46
4.7. Web Service Interface 4.7. Web Service Interface The system must provide an interface with a set of operations to allow both the tenants and the Cloud Data Migration Application to interact with the system and configure the connections between the single physical consumer endpoint and the multiple provider endpoints. 4.8. Non-functional Requirements In this section we list and describe the non-functional requirements our system must fulfill. The non-functional requirements described in this thesis are independent from the ones satisfied by the Cloud data store providers, which are specified in the Service Level Agreement between the Cloud provider and the user. 4.8.1. Security Securing the tenant context information in our system is one of the main requirements we must fulfill. Tenant context in our system does not only contains tenant configuration data, but also contains the necessary meta-data from the backend data sources, which include the databases schemas and its access credentials. In order to ensure confidentiality and integrity of the data migrated to the Cloud, tenant configuration data must be visible only to the system, and not transferred to third parties through the Web or Web service interface. 4.8.2. Backward Compatibility In this diploma thesis we must face to two architectural tendencies in ServiceMix-mt: OSGibased components and JBI-based components. Backward compatibility with the multi-tenant JBI components developed in [Sá12], [Muh12], and [Ess11] must be ensured. At the same time we must build the new components following the OSGi tendency. Compatibility with non multi-tenant aware endpoint configurations must be ensured in the system. In ServiceMix-mt we extend existing components, e.g. ServiceMix-http-mt, ServiceMix-camel-mt, JDBCCdasmix, etc., and deploy them as custom components. By deploying the extended components as separate custom components, we avoid conflicts with the non multi-tenant aware components ServiceMix is shipped with, e.g. ServiceMix-http [ASM], ServiceMix-camel [ASM], Camel-jdbc [Thec], etc. Configuration of non multi-tenant aware endpoints is still supported in ServiceMix-mt. 47
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 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?