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

More documents

Recommendations

Info

5. Design JBI SA into an OSGi container is simple: repackaging of the SA as a JAR. However, this cannot be consider a full integration in the OSGi container. OSGi bundles contain in their META-INF folder one fundamental file for the OSGi kernel: the manifest file. This contains a description of the bundle, the packages it imports, and exports. Imported packages can be either statically stored in the bundle or imported from third party bundles, and exported packages are the ones which exposed to third party bundles. These can be imported with an internal class loading mechanisms developed in the OSGi container. The repackaging of the SA into a JAR, as it is shown in Figure 5.3, contains the META-INF folder, and the manifest file. However, the latter only contains information about the author, date of creation, but it does not contain information related to the exported packages, and the needed packages to be imported. This manifest file describes the SA, and not the SUs. Java classes and package importing description are contained in the SU package, and not in the SA package. Therefore, the OSGi container cannot register in its registry the packages it exports as a service, and cannot load the imported packages to the bundle context. This fact forces us to statically include in the SA, and the SU the packages which are referenced in each SU, and leads to scalability constraints with the tenant-aware deployment process of the system. ServiceMix 4.x versions are shipped with different JBI BCs packed as an OSGi bundle. However, they are deployed as OSGi bundles, and not as SAs, in order to enable loose coupling and package sharing between components in the OSGi container. ServiceMix-mt allows the deployment of the JBI BCs, but deployment of JBI BCs as OSGi bundles is not supported in the JBIMulti2 application. This lack of support forces us to design a second architectural approach, as described in the following sections. 5.3.2. Approach 1 SQL database systems provide access to their databases through an endpoint, which is represented as an URL. The native driver used in the data access layer of an application connects to the endpoint, authenticates, sends the query, and reads the response. Therefore, we must support in our system the same operational steps. As discussed in this diploma thesis, the communication protocol varies between different vendors. In this diploma thesis we provide support for incoming MySQL messages. Tenants must access our system through a single physical endpoint. This endpoint is provided by a MySQL proxy which is enriched with authentication, cashing, marshaling, and demarshaling operations. As shown in Figure 5.4, the MySQL Proxy Bundle implements the MySQL server operations which are related with the client/server communication protocol. In Figure 5.4 we specify a server running on port 3306. However, this value can be configured before the deployment of the OSGi component. This component is built as an OSGi bundle and its packages are exported as services in the OSGi container. It interacts with three different components in the system: the NMR API, the Cache, and the Service Registry. Cashing mechanisms are implemented in both the Registry-Cache, and the MySQL Proxy Bundle. The former provides an API for creating cache instances, and for persisting and retrieving data. We create a separate cache instance for the SQL support due to the need of a custom key creation mechanism which may not coexist in a shared cache between different 56
5.3. SQL Support Architectural Overview bundles, as well as the needed isolation of sensible tenant configuration information from third party bundles. The system provides a set of operations which ease the creation of multi-tenant aware keys for persisting frontend authentication data, and queries results form the backend database systems. The NMR API is shipped in ServiceMix as an OSGi bundle which exports its API as an OSGi service. The set of operations included in its API allows OSGi bundles to create, send, and receive message exchanges to JBI endpoints (see Figure 5.4). Before creating the message exchange, the MySQL Proxy Bundle must build dynamically the target endpoint’s URL by injecting the tenant context information, and service and endpoint name. External Application Legend Data Access Layer (MySQL ConnectorJ) T1 ... TN (*) Tenant-aware Endpoint Tenant1 ... TenantN Query and data transformation might exist Multi-tenant context & messaging SELECT * FROM myTable / INSERT * INTO * VALUES * OSGi JBI Environment Registry-Cache SQL Cache instance SQL Server (port 3306) MySQL Proxy Bundle Standardised Interfaces for Binding Components Normalized Message API !"#$%&'()*+,)--%.)+/"01)#+ (*) !"#$%#&%'()%*+$")&,#-)(*,.&*!)&/'-)*0$1'$)(* Camel JDBC T1 T2 T3 ... Camel JBI TN Smx-Camel-mt PostgreSQL Service Registry Amazon RDS Local VM MySQL Oracle ... MySQL PostgreSql Figure 5.4.: Architectural overview of the design approach one to support the MySQL communication protocol and routing to backend SQL databases. 57
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 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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?