Service Orchestration as Organization : Building Multi-Tenant Service Applications in the Cloud
By: Kapuruge, Malinda.
Contributor(s): Han, Jun | Colman, Alan.Material type: TextSeries: eBooks on Demand.Publisher: Burlington : Elsevier Science, 2014Description: 1 online resource (335 p.).ISBN: 9780128010976.Subject(s): Application software -- Development | Business -- Data processing | Business enterprises -- Computer networks -- Management | Service-oriented architecture (Computer science)Genre/Form: Electronic books.Additional physical formats: Print version:: Service Orchestration as Organization : Building Multi-Tenant Service Applications in the CloudDDC classification: 004.6/54 LOC classification: TK5105.5828 K37 2014Online resources: Click here to view this ebook.
|Item type||Current location||Call number||URL||Status||Date due||Barcode|
|Electronic Book||UT Tyler Online Online||TK5105.5828 K37 2014 (Browse shelf)||http://uttyler.eblib.com/patron/FullRecord.aspx?p=1766352||Available||EBL1766352|
Front Cover; Service Orchestration as Organization; Copyright Page; Contents; List of Figures; List of Tables; List of Listings; Preface; About the Authors; One; 1 Introduction; 1.1 Business process management; 1.1.1 BPM in practice; 1.1.2 BPM in service-oriented systems; 1.2 Service orchestration and its adaptation; 1.2.1 Novel requirements for service orchestration; 1.2.2 Runtime adaptability in service orchestration; 1.3 Research goals; 1.4 Approach overview; 1.5 Contributions; 1.6 Overview of this book; 2 Motivational Scenario; 2.1 RoSAS business model; 2.2 Support for controlled change
2.3 Support for SIMT2.4 Requirements of service orchestration; 2.5 Summary; 3 Literature Review; 3.1 BPM - an overview; 3.2 BPM and SOA; 3.3 Adaptability in BPM; 3.4 Techniques to improve adaptability in BPM; 3.4.1 Proxy-based adaptation; 3.4.2 Dynamic explicit changes; 3.4.3 Business rules integration; 3.4.4 Aspect orientation; 3.4.5 Template customisation; 3.4.6 Constraint satisfaction; 3.5 Summary and observations; 3.5.1 Summary and evaluation; 3.5.2 Observations and lessons learnt; 3.6 Towards an adaptive service orchestration framework; 3.7 Summary; Two; 4 Orchestration as Organisation
4.1 The organisation4.1.1 Structure; 4.1.2 Processes; 4.2 Loosely coupled tasks; 4.2.1 Task dependencies; 4.2.2 Events and event patterns; 4.2.3 Support for dynamic modifications; 4.3 Behaviour-based processes; 4.3.1 Organisational behaviour; 4.3.2 Process definitions; 4.4 Two-tier constraints; 4.4.1 The boundary for a safe modification; 4.4.2 The minimal set of constraints; 4.4.3 Benefits of two-tier constraints; 4.5 Behaviour specialisation; 4.5.1 Variations in organisational behaviour; 4.5.2 Specialisation rules; 4.5.3 Support for unforeseen variations; 4.6 Interaction membranes
4.6.1 Indirection of processes and external interactions4.6.2 Data transformation; 4.6.3 Benefits of membranous design; 4.7 Support for adaptability; 4.7.1 Adaptability in layers of the organisation; 4.7.2 Separation of control and functional process; 4.8 Managing complexity; 4.8.1 Hierarchical and recursive composition; 4.8.2 Support for heterogeneity of task execution; 4.8.3 Explicit service relationships; 4.9 The meta-model; 4.10 Summary; 5 Serendip Runtime; 5.1 The design of an adaptive service orchestration runtime; 5.1.1 Design expectations; 5.1.2 Core components; 5.2 Process life cycle
5.2.1 Stages of a process instance5.2.2 Process progression; 5.3 Event processing; 5.3.1 The event cloud; 5.3.2 Event triggering and business rules integration; 5.4 Data synthesis of tasks; 5.4.1 The role design; 5.4.2 The transformation process; 5.5 Dynamic process graphs; 5.5.1 Atomic graphs; 5.5.2 Patterns of event mapping and construction of EPC graphs; 5.6 Summary; 6 Adaptation Management; 6.1 Overview of process management and adaptation; 6.1.1 Process modelling life cycles; 6.1.2 Adaptation phases; 6.2 Adaptation management; 6.2.1 Functional and management systems; 6.2.2 The organiser
6.2.3 The adaptation engine
Service orchestration techniques combine the benefits of Service Oriented Architecture (SOA) and Business Process Management (BPM) to compose and coordinate distributed software services. On the other hand, Software-as-a-Service (SaaS) is gaining popularity as a software delivery model through cloud platforms due to the many benefits to software vendors, as well as their customers. Multi-tenancy, which refers to the sharing of a single application instance across multiple customers or user groups (called tenants), is an essential characteristic of the SaaS model. Written in an easy to foll
Description based upon print version of record.