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

More documents

Recommendations

Info

4. Concept and Specification 4.6. Use Cases In this section we extend the tenant operator use cases which are described in Muhler’s and Uralov’s approach [Muh12], [Ura12]. The tenant operators are the users with less permissions in JBIMulti2, who perform service registration and endpoint configuration operations in ServiceMix-mt. An overview of the set of use cases for the tenant operators is presented in Figure 4.3. The set of use cases we add to the previous version are highlighted, and described in detail. List policy Retrieve policy View policy View service registrations Unregister service Delete policy Attach policy Register service Tenant Operator View service assemblies Deploy service assembly Undeploy service assembly Register data source Legend Register secondary information structure Attach Target Data Source Register main information structure Developed in this <strong>Diploma</strong> thesis Figure 4.3.: Use case diagram for tenant operator. 42
4.6. Use Cases Name Goal Actor Pre-Condition Post-Condition Post-Condition Special Case Normal Case in Register Data Source The tenant operator wants to register a source and backend data source configuration data and associate it to an existing service assembly. Tenant Operator The tenant operator has the permissions in the service unit contingent and has registered a service assembly with no datasources associated to it. Source and backend data source configuration data is stored successfully, and associated with a tenant’s operator service assembly. Source and backend data source configuration data are not stored, and not associated with the specified service assembly. 1. The tenant operator selects the service assembly to which the data sources are associated. 2. The source and target data sources configuration data are registered in the system, and associated to the specified service assembly. Special Cases 1a. The service assembly does not exist. a) The system shows an error message and aborts. 2a. The service assembly is already associated with a source data source. a) The system shows an error message and aborts. 2b. The source data source configuration data already exists. a) The system shows an error message and aborts. 2c. The target data source configuration data already exists. a) The system shows an error message and aborts. Table 4.1.: Description of Use Case Register Data Source. 43
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 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

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

Delete template?

Save as template?