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

More documents

Recommendations

Info

Appendix B. Messages 20 - target datasource endpoint url: string 21 - target datasource user and password : string, string 22 - source & target endpoint type: endpoint.type.jdbc | endpoint.type.http | endpoint. type.jms 23 - targetJBIEndpointURI: QName 24 - source and target information structure information: 25 if source is sql 26 - src_main_info_structure_name : string 27 - target_main_info_structure_name : string 28 if source is nosql 29 - src_main_info_structure_name : string 30 - target_main_info_structure_name : string 31 - src_secondary_info_structure_name : string 32 - target_secondary_info_structure_name : string 33 34 - if the target protocol == mysql 35 - target native driver name : native driver name, e.g. "com.mysql.jdbc.driver" 36 - bean DS name (if exists) 37 - escapeProcessing : true | false //statement property of mysql 38 - fetchSize : int (statement property of mysql) 39 - returnGeneratedKeys : true | false //statement property of mysql 40 41 // Attachment 42 if (SQL) 43 - Query/ies go/es in the NMF body as a vector, with query data (for insert 44 else queries). 45 - NoSQL JSON payload 46 47 48 //////////////////////////////////////////////////////////////////////// 49 50 - NMF -> MySQL || NoSql (Response Message) 51 // Main properties 52 - target_data_sources : number of target data sources. This number will set the length of the properties vector and the length of the result 53 - tenantId : string (UUID) 54 - userId : string (UUID) 55 - target_op_status = ok | error 56 57 - if source protocol == mysql 58 59 - updateCount = int // the current result as an update count 60 - resultSetMetadataNumber: int // number of result set in the vector of response 61 (index in the result set metadata vector) 62 // Backend datasource dependent properties : stored as Properties in the vector< properties>. 63 - source & target dataSource name : string 64 - source & target dataSource type : family-mainInfoStructure-secondaryInfoStructureversion 65 - source & target dataSource protocol : mysql | http.[xml|rest] 66 - source & target endpoint type: endpoint.type.jdbc | endpoint.type.http | endpoint.type .jms 67 - source and target information structure information: 96
B.1. Normalized Message Format Content Description 68 if source is sql 69 - src_main_info_structure_name : string 70 - target_main_info_structure_name : string 71 if source is nosql 72 - src_main_info_structure_name : string 73 - target_main_info_structure_name : string 74 - src_secondary_info_structure_name : string 75 - target_secondary_info_structure_name : string 76 77 // Attachment 78 - if target_op_status == error 79 - target_op_error : vector // map of error code and 80 else 81 82 error message per backend db 83 - if source protocol == mysql 84 85 - vector // result sets are 86 inserted as arraylist in the body 87 - ResultSetMetadata: Vector 88 - columncount : int // number of columns in this ResultSet object. 89 - columntype : arraylist // the designated column’s SQL type. 90 - isnullable : arraylist // if the column can contain null values 91 - isAutoIncrement : arraylist // if the column values increment when the rows do 92 - tableName : arraylist // name of the table where a column is contained 93 - stringcolumnlabel : arraylist // label which sql proposes for printing reasons 94 - stringcolumnname : arraylist // column name 95 - ColumnDisplaySize : arraylist // Indicates the designated column’s normal maximum width in characters. 96 - Scale : arraylist // column’s number of digits to right of the decimal point 97 - RowCount : int // number of rows 98 - ColumnMapper : Hashmap (column index, name) // mapping of the column index with the column name 99 - ColumnSigned : arraylist // if the values of the columns 100 else 101 - versionControl 102 - nosql metadata are signed or unsigned 103 - nosql JSON payload 104 105 //////////////////////////////////////////////////////////////////////// 106 107 Note: response to the user -> distributed atomic transaction mechanism used. If one of the backend datasources reports an error as a response, the final response to the tenant is an error response: 108 109 - Error response: string of the error + the datasource/s which gave the error. 97
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 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 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?