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

More documents

Recommendations

Info

6. Implementation stored. Both authentication and data retrieval are susceptible of being cashed in the system. The cashing mechanisms we use for this BC is the same as in the CDASMix MySQL Proxy component. The difference relies on a separate cache instance for NoSQL requests, and the need of including the JBI ServiceMix Registry library in the SA of this BC, due to the problems found when loading external OSGi bundles from components packed as SAs. 6.3. Extensions Apart from the components which we implement in this diploma thesis, we extend existing components developed in the works from Muhler [Muh12], and Uralov [Ura12]. We extend the JBIMulti2 application developed by Muhler, and adapt the JBI ServiceMix Registry performed by Uralov. 6.3.1. JBIMulti2 The multi-tenant aware administration and management application JBIMulti2 offers a list of operations through its Web service interface in order to allow tenants to deploy multi-tenant aware endpoints in ServiceMix-mt. However, it does not provide support for persisting the tenant’s Cloud data stores communication meta-data. In Chapter 5 we describe the necessary modifications on the service registry, and the need of extending the application’s Web service interface to avoid a connection from the Cloud Data Migration Application to the database system which stores the tenant configuration data. The Service Registry database schema is created using the Java Persistence API, and annotating the Java classes with meta-data. We extend the Java class ServiceAssembly, which stores the SAs deployed by the tenant. The ServiceAssembly class contains the schema representation, and the data storage and retrieval operations. The Web service interface developed by Muhler [Muh12], and extended by Uralov [Ura12], contains several management operations, e.g. deploy service assembly, create tenant, create user, deploy JBI BC, etc., which allows the system administrator and tenants to perform management operations on ServiceMix-mt. The Cloud Data Migration Application described in Chapter 2 retrieves from the user the backend database system meta-data, such as access credentials, database name, etc. The application may be hosted on a separate server as JBIMulti2. In order to avoid a direct connection from the Cloud Data Migration Application to the Service Registry, which contains sensible data, we extend the JBIMulti2 Web service interface, and provide the operations for registering the tenant’s backend Cloud data store meta-data. 6.3.2. Cache The cashing support in ServiceMix-mt is provided in the OSGi component JBI ServiceMix Registry. Uralov provides a set of operations to set up a cache instance, store elements, and 72
6.3. Extensions retrieve stored elements [Ura12]. However, the JBI ServiceMix Registry OSGi bundle libraries are not registered as an OSGi service. Therefore, this component is not accessible from third party OSGi bundles in the OSGi container. We modify its original BundleActivator class and include the OSGi service registration to allow its usage from external OSGi bundles. 1 2 3 13 14 15 16 Listing 6.6: Eh cache configuration for SQL support. The cache instances are created on the Ehcache 2.6.0 component [Ter], which provides support to store serializable objects indexed by a key. A cache instance configuration in the Ehcache component must be specified in an XML file, which is described in Listing 6.6. However, the cashing support is not multi-tenant aware. We implement a dynamic creation of multi-tenant aware cache keys in order to ensure isolation between the cashed tenant’s information, and data (see Listing 6.2). 73
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 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?