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

More documents

Recommendations

Info

2. Fundamentals corresponding works in [Muh12], [Sá12], leading to a multi-tenant ServiceMix prototype supporting different communication protocols. We will refer to it as ServiceMix-mt. As a main difference with previous versions’ architectures, ServiceMix is an integration container based on the OSGi Framework implementation Apache Karaf [APA11b]. It provides a light environment in which components and applications can be deployed in a loose coupled way. Apache Karaf provides an extensible management command line console where management of the components lifecycle, such us OSGi bundles, JBI components or SAs, can be done in a user friendly way (see Figure 2.4). Furthermore, a hot deployment directory is shipped with the ESB package where users can deploy OSGi bundles, JBI components wrapped in SA’s, etc. just by copying the file into it. The undeployment is done automatically when the user deletes the file from the deploy directory. The main advantage in the ServiceMix 4.3.0 it is its full compliance with the JBI specification. Its JBI container has as its main component the NMR (See Figure 2.4). In the JBI container users are provided with JBI deployment support and management. The communication between the JBI and OSGi container, e.g. from one OSGi service to a JBI Binding Component can be achieved through the NMR using its API wrapped as an already deployed OSGi bundle. This fact eases the integration process of components between different ServiceMix’s versions, and take advantage of it in this diploma thesis. Furthermore, JBI components or endpoint configurations packed as SE or SA and deployed in ServiceMix are internally packed into OSGi bundles. ServiceMix is shipped with different JBI components already deployed as OSGi bundles in its OSGi container. In this thesis we will concentrate on the following ones: HTTP and Apache Camel. Apache Camel is a powerful open source integration framework based on Enterprise Application Integration (EAI) [APA11a]. Furthermore, it provides a widespread list of components which support different communication protocols. The user can configure logical endpoints between BCs and different routing paths between them by deploying their configuration wrapped in a SA in the deploy directory. Different Maven plugins can make the configuration of a JBI or SE as simple as possible by providing different built archetypes which generates the SU files and directories where the developer can configure the component [AMV]. Apache Camel provides a set of maven archetypes which already contain the structure for developing custom camel components. The NMR routes the messages between the endpoints created by the JBI components (see Figure 2.4). This endpoints are divided in two types: consumers and providers. A consumer endpoint is exposed as a service while a provider endpoint consumes an external service. When a message arrives to a consumer endpoint of a JBI Binding Component, it is transformed into a Normalized Message Format (NMF). The NMF is the protocol neutral format which is routed in a JBI environment and described in Section 2.4. The ServiceMix-mt prototype we extend in this diploma thesis already provides multi-tenant support for different communication protocols: HTTP, JMS, and E-mail. However, the data retrieval and storage in an application’s architecture relies on one specific layer: Data Access Layer, and its main used communication protocols for data transfer are in most of the cases vendor specific. Communication with SQL databases, such as MySQL, Oracle, 16
2.7. Binding Components Figure 2.4.: Architecture of Apache ServiceMix [ASM] and PostgreSQL are managed by its vendor-specific native driver, which implements the communication protocol with the database server in the DBMS. Such protocols are not supported in the multi-tenant prototype ServiceMix-mt, and must be taken into account in the extension of the prototype in this diploma thesis. On the other hand, communication with Not only Structured Query Language (NoSQL) databases can be also considered vendorspecific, because most of the Cloud storage providers facilitate its own API to the users to manipulate data in their data containers, but almost all of them provide either REST or SOAP over HTTP interfaces. This fact permits us to reuse and extend the multi-tenant HTTP BC in ServiceMix-mt. The components we create or extend in this diploma thesis are identified by CDASMix (Cloud Data Access Support in ServiceMix-mt). 2.7. Binding Components In this section we describe the JBI BCs shipped in the ServiceMix-mt prototype this diploma thesis focuses on, and the transport protocols they support. 2.7.1. Multi-tenant HTTP Binding Component ServiceMix provides HTTP communication support in its HTTP JBI BC. Its HTTP consumer and provider endpoints are built on the HTTP Jetty 6 server and Jakarta Commons HTTP Client respectively, providing support for both REST and SOAP over HTTP 1.1 and 1.2 requests. The original HTTP BC is extended in the ServiceMix-mt prototype to provide multi-tenant support in [Muh12] and [Sá12]. Muhler provides an internal dynamic creation of tenantaware endpoints in the BC, by injecting tenant context in the JBI endpoint’s URLs [Muh12]. Gomez provides a NMF with tenant context information in its properties for routing in the NMR [Sá12]. However, in this diploma thesis we must not only provide tenant isolation at 17
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 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 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?