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

More documents

Recommendations

Info

6. Implementation multi-tenancy awareness operations which listen to and send messages to multi-tenant aware JBI endpoints. In the design approach two for SQL support described in Chapter 5 we define two Camel JBI endpoints for routing requests to the CDASMixjdbc component: the tentants’ JBI endpoints, and the JBIToCamelJdbc endpoint. The former is deployed on ServiceMix-camel-mt, and the latter on ServiceMix-camel. Both routes definitions are packed and deployed in different SUs, and SAs, due to their deployment on different components. In the URI endpoint definition we set the Camel JBI option check serialization= nocheck, which deactivates the serialization checking of objects contained in the property section of the NMF. The objects the system sends in the NMF properties section implement the interface serializable. Therefore, there is no need of overloading the system with checking operations. The JBIToCamelJdbc endpoint forwards the messages exchanges to the CDASMixjdbc camel component (see Listing 6.3). 6.1.3. Camel CDASMix JDBC Component The Camel CDASMix JDBC component provides support for creating and exchanging requests with external database systems via JDBC. We implement the communication support for the following three database systems: MySQL, PostgreSQL, and Oracle. The connections to the databases are established by utilizing its client native drivers via JDBC: mysql-connectorjava-5.1.22, postgresql-9.1-901.jdbc3, and ojdbc14-10.2.0. These are included in the OSGi bundle of the CDASMixjdbc component, and DataSource objects are created for establishing the connection with the backend database systems. The CdasmixDataSource interface is implemented by the three protocol specific datasources: CdasmixMySQLDS, CdasmixPostgresDS, and CdasmixOracleDS (see Figure A.2). Therefore, the database specific DataSource creation is handled in the DataSourceHandler class, which evaluates the target datasource driver property contained in the NMF. This class interacts with the JNDI registry of the system for registering, and retrieving the DataSource instances. 1 ... 2 4 5 6 7 8 9 ... Listing 6.3: Route definition for JBIToCamelJdbc JBI endpoint to JDBCCDASMix Camel Component. This component is developed as a custom camel component, and in the Camel registry its endpoints are identified by the prefix cdasmixjdbc (see Listing 6.3). The OSGi container allows the redeployment of the component without the need of redeploying the external components 68
6.2. NoSQL Support Implementation which use its libraries. During the activation process of this OSGi bundle, an instance of the component is created and registered in the Camel registry. Camel endpoints containing in its URI the jdbccdasmix component create an instance of the JdbcCdasmixComponent class. The original Camel-jdbc component requires the user to specify the data source name in the endpoint URI, and its properties in the bean configuration. However, we do not require the explicit description of the data source in the URI, as the component retrieves it from the NMF, and creates it dynamically. The JdbcCdasmixEndpoint class creates an instance of the producer endpoint, the JdbcCdasmixProducer. The JdbcCdasmixProducer includes the main logic of the component. When a NMF is received in the jdbccdasmix endpoint, its properties are extracted and analyzed, the connection to the backend database is established, the message is demarshaled, the request on the database system is performed, the response from the database system is marshaled into the NMF, and forwarded back to the endpoint which created the exchange. The response’s meta-data is stored in the properties section of the NMF, while the data is stored in the attachment section of the NMF. The storage of attachments in the NMF through the Camel API requires the storage of the data in a class which implement the javax.activation.DataSource class. Threfore, we implement two different classes which implement it, and store different data: the data retrieved from the backend database system (when success), or the error messages (when an error occurs). Operations on different backend database systems in one message exchange are considered atomic. If one backend database system answers with an error, the message exchange status is set to error, and forwarded to the endpoint which created the message exchange. The support of JDBC in a custom component and a unique endpoint URI prefix allows the developers to use the existing Camel-jdbc component for their non multi-tenant aware connections. 6.2. NoSQL Support Implementation The prototype requirements described in Chapter 4 specify the need of support to NoSQL Cloud data stores. In Chapter 5 we present a design for accessing backend NoSQL Cloud data stores via a standardized protocol which is supported in most of the data stores interfaces: JSON over HTTP. Gomez [Sá12] and Muhler [Muh12] extend the ServiceMix-http JBI BC in order to provide multi-tenancy awareness at the communication level. We reuse and extend the BC to support the communication protocol required in this diploma thesis. 6.2.1. Multi-tenant ServiceMix HTTP Binding Component As discussed in previous chapters, the ServiceMix-mt JBI BC implements multi-tenancy awareness for the HTTP communication protocol. However, the multi-tenancy awareness supported ensures endpoint isolation at the tenant level, but not at the user level. Ensuring tenant isolation in a system which connects to multiple tenant’s databases, and is accessed by multiple tenant’s users, is not enough. Therefore, we modify the operations implemented in Muhler’s approach [Muh12], in order to ensure tenant and user isolation. 69
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 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?