E-Book, Englisch, 210 Seiten
Dimitrakos / Martrat / Wesner Service Oriented Infrastructures and Cloud Service Platforms for the Enterprise
1. Auflage 2009
ISBN: 978-3-642-04086-3
Verlag: Springer
Format: PDF
Kopierschutz: 1 - PDF Watermark
A selection of common capabilities validated in real-life business trials by the BEinGRID consortium
E-Book, Englisch, 210 Seiten
ISBN: 978-3-642-04086-3
Verlag: Springer
Format: PDF
Kopierschutz: 1 - PDF Watermark
Service-Oriented Infrastructures including Grid and Cloud Computing are technologies in a critical transition to wider adoption by business. Their use may enable enterprises to achieve optimal IT utilization, including sharing resources and services across enterprises and on-demand utilization of those made available by business partners over the network. This book is an essential reference for researchers and practitioners in service-oriented IT. It analyses a selection of common capabilities (services capturing reusable functionality of IT solutions) that have been applied to tackle challenging business problems and were validated by the BEinGRID consortium in real-life business trials covering most European market sectors.
Autoren/Hrsg.
Weitere Infos & Material
1;Preface;5
2;Contents;9
3;Contributors;13
4;Introduction;16
4.1;Motivation;16
4.2;The BEinGRID Project;19
4.2.1;The BEinGRID Matrix;20
4.2.1.1;Vertical Market Sectors;20
4.2.1.2;Business Models;21
4.2.1.3;Research and Technological Innovation Themes;21
4.2.1.4;Knowledge Repository for SOI and Cloud Computing;23
4.3;Common Capabilities for SOI and Cloud Services;23
4.3.1;Life-Cycle Management of Virtual Organizations;24
4.3.2;Federated Identity and Access Management;26
4.3.2.1;Identity Brokerage and Identity Federation Context Management;27
4.3.2.2;Distributed Access Management;29
4.3.3;Common Capabilities for Managing Software Licenses;32
4.3.4;Common Capabilities for Managing Service Level Agreements;33
4.3.5;Common Capabilities for Data Management;37
4.3.6;Common Capabilities for Data and Service Portals;38
4.4;An Example that Brings it all Together;40
4.5;About the Contents and Structure of this Book;43
4.6;References;45
5;Approach Towards Technical Innovations for Service Oriented Infrastructures and Clouds;47
5.1;Introduction;47
5.2;High-Level Objectives;48
5.3;The Innovation Delivery Process;50
5.3.1;Elicitation of Common Technical Requirements;53
5.3.2;Thematic Areas;54
5.3.3;Prioritisation of Common Technical Requirements;57
5.3.4;Common Capabilities and Design Patterns;58
5.3.5;Generic Components: Reference Implementations of Common Capabilities;60
5.4;References;61
6;Management of Virtual Organizations;62
6.1;Introduction;62
6.2;The Main Challenges;63
6.3;Technical Requirements;65
6.3.1;Secure Federation;65
6.3.2;Separation of Infrastructure Management Capabilities from Application Specific Ones;66
6.3.3;Automatic Resource and Service Discovery;66
6.4;Common Capabilities;66
6.4.1;VO Set Up;67
6.4.1.1;High Level Design;67
6.4.1.2;Sample Implementation;67
6.4.2;Creation of Instances in Service Oriented Distributed Infrastructures;69
6.4.2.1;High Level Design;70
6.4.2.2;Sample Implementation;70
6.4.3;Application Virtualization;71
6.4.3.1;High Level Design;71
6.4.3.2;Sample Implementation;73
6.4.4;Automatic Resource/Service Discovery;74
6.4.4.1;High Level Design;74
6.4.4.2;Sample Implementation;75
6.5;A Sample Scenario and Integrated View of the Components;76
6.5.1;VO Identification & Formation;78
6.5.2;VO Creation;80
6.5.3;VO Operation and Evolution;80
6.5.4;VO Dissolution;81
6.6;Lessons Learnt;81
6.7;Business Benefits;83
6.8;Conclusion;84
6.9;References;85
7;Aspects of General Security & Trust;87
7.1;Introduction;87
7.2;The Overall Challenge;90
7.3;Business Motivation;92
7.4;Technical Requirements;93
7.4.1;Primary Security Requirements;94
7.4.1.1;Authentication (AuthC) & Authorization (AuthZ);94
7.4.1.2;Auditing & Assurance;94
7.4.2;Distributed Systems Security;95
7.4.3;Adaptive Enforcement;96
7.4.4;Data Protection & Infrastructure Security;96
7.4.5;SOA Security Governance;97
7.5;Common Capabilities;97
7.5.1;Overview;97
7.5.2;Identity Brokerage & Secure Federation Management;98
7.5.2.1;Architecture;99
7.5.2.2;Business Benefits;102
7.5.3;Access Control & Authorization;102
7.5.3.1;Architecture;103
7.5.3.2;Business Benefits;105
7.5.4;Secure Messaging Gateway;106
7.5.4.1;Architecture;106
7.5.4.2;Business Benefits;107
7.5.5;Security Observer;108
7.5.5.1;Architecture;108
7.5.5.2;Business Benefits;110
7.5.6;The SOI Governance Gateway (SOI-GGW);110
7.5.6.1;Architecture;110
7.5.6.2;Business Benefits;112
7.6;Conclusion;112
7.7;References;114
8;Management for Service Level Agreements;115
8.1;The Overall Challenge;115
8.2;Technical Requirements;116
8.2.1;SLA Negotiation;117
8.2.1.1;Business Benefit;117
8.2.1.2;State of the Art and Innovation;118
8.2.2;SLA Optimisation of Resource Selection;118
8.2.2.1;Business Benefit;119
8.2.2.2;State of the Art and Innovation;119
8.2.3;SLA Evaluation;119
8.2.3.1;Business Benefit;120
8.2.3.2;State of the Art and Innovation;121
8.2.4;SLA Accounting;121
8.2.4.1;Business Benefit;122
8.2.4.2;State of the Art and Innovation;122
8.3;Common Capabilities;122
8.3.1;SLA Negotiation Capability;123
8.3.1.1;High Level Design;123
8.3.1.2;Implementation;125
8.3.1.3;Example of Use;125
8.3.2;SLA Optimisation Capability;126
8.3.2.1;High Level Design;126
8.3.2.2;Implementation;126
8.3.2.3;Example of Use;127
8.3.3;SLA Evaluation and Monitoring;128
8.3.3.1;High Level Design;128
8.3.3.2;Implementation;129
8.3.3.3;Example of Use;130
8.4;Motivation;130
8.5;Conclusion;131
8.5.1;Lessons Learned;132
8.5.1.1;SLA Concept Penetration;132
8.5.1.2;Need for an Integrated SLA Functionality;133
8.5.1.3;Renegotiation Is not Clearly Needed;133
8.5.2;Recommendations;134
8.5.2.1;Plan Your SLA Usage in the Early Stages;134
8.5.2.2;Who Wants to Sign an SLA?;135
8.6;References;135
9;License Management;137
9.1;Introduction;137
9.2;The Overall Challenge;137
9.3;Technical Requirements;138
9.3.1;Gridification of Currently Used License Management Systems;138
9.3.1.1;Description;138
9.3.1.2;Innovation;138
9.3.1.3;Business Impact;138
9.3.2;Limited License Service Provider (LSP) Capability;139
9.3.2.1;Description;139
9.3.2.2;Business Impact;139
9.4;Common Capabilities;140
9.4.1;LM Authorization;141
9.4.1.1;Purpose;141
9.4.1.2;Architecture;141
9.4.1.3;Implementation;142
9.4.1.4;Validation Scenario;143
9.4.2;Extension of Job Description and Submission;144
9.4.2.1;Purpose;144
9.4.2.2;Architecture;144
9.4.2.3;Implementation;144
9.4.2.4;Validation Scenario;145
9.4.3;Resource Management Extension;145
9.4.3.1;Purpose;145
9.4.3.2;Architecture;145
9.4.3.3;Implementation;145
9.4.3.4;Validation Scenario;146
9.4.4;Encapsulation of License Server;146
9.4.4.1;Purpose;146
9.4.4.2;Architecture;146
9.4.4.3;Implementation;146
9.4.4.4;Validation Scenario;146
9.4.5;Accounting and Billing;147
9.4.5.1;Purpose;147
9.4.5.2;Architecture;147
9.4.5.3;Implementation;147
9.4.5.4;Validation Scenario;148
9.4.6;LM Monitor;148
9.4.6.1;Purpose;148
9.4.6.2;Architecture;148
9.4.6.3;Implementation;149
9.4.6.4;Validation Scenario;149
9.5;Conclusion;149
9.5.1;Lessons Learnt;149
9.5.1.1;Support for License Management in Grid Environments;149
9.5.1.2;Transition to Pay-Per-Use;149
9.5.2;Recommendations;150
9.5.2.1;Transition to Pay-Per-Use-the Business Model Aspect;150
9.5.2.2;Recommendations for Use of LM Components;150
9.6;References;150
10;Data Management;152
10.1;Introduction;152
10.2;The Overall Challenge;153
10.3;Technical Requirements;154
10.3.1;Accessing Data from Different Locations;155
10.3.1.1;Business Benefit;155
10.3.1.2;State of the Art and Innovation;156
10.3.2;Accessing Heterogeneous Data;156
10.3.2.1;Business Benefit;156
10.3.2.2;State of the Art and Innovation;157
10.3.3;Respond to Changes of Data in a Database;157
10.3.3.1;Business Benefit;157
10.3.3.2;State of the Art and Innovation;158
10.4;Common Capabilities;158
10.4.1;Access to Remote Data Sources;158
10.4.1.1;Purpose;159
10.4.1.2;Implementation;159
10.4.1.3;Example of Use;161
10.4.2;Homogenise Data Sources;161
10.4.2.1;Purpose;162
10.4.2.2;Implementation;162
10.4.2.3;Example of Use;163
10.4.3;Synchronise Multiple Data Sources;163
10.4.3.1;Purpose;165
10.4.3.2;Implementation;165
10.4.3.3;Example of Use;167
10.5;Conclusion;167
10.5.1;Recommendations;167
10.5.1.1;Do the Simple Thing if Possible;167
10.5.1.2;Use Native Database Functionality where Possible;168
10.5.1.3;For Simple Deployment of OGSA-DAI Data Resources Use the Data Source Publisher;168
10.5.1.4;For Reflecting Data Changes Outside of a Database Use the OGSA-DAI Trigger;168
10.6;References;168
11;Portals for Service Oriented Infrastructures;170
11.1;Introduction;170
11.2;The Overall Challenge;171
11.3;Common Capabilities and Technical Requirements;172
11.3.1;User Management;173
11.3.1.1;Requirements and Features;173
11.3.1.2;Architecture;173
11.3.1.3;Implementation;174
11.3.1.4;Innovation and Business Value;175
11.3.1.5;Example Usage;176
11.3.2;Portals Security;176
11.3.2.1;Requirements and Features;176
11.3.2.2;Architecture;177
11.3.2.3;Implementation;178
11.3.2.4;Innovation and Business Value;179
11.3.2.5;Example Usage;179
11.3.3;File Management;180
11.3.3.1;Requirements and Features;180
11.3.3.2;Architecture;181
11.3.3.3;Implementation;182
11.3.3.4;Innovation and Business Value;182
11.3.3.5;Example Usage;183
11.3.4;Job Submission Monitoring and Control;183
11.3.4.1;Requirements and Features;183
11.3.4.2;Architecture;184
11.3.4.3;Implementation;185
11.3.4.4;Innovation and Business Value;186
11.3.4.5;Example Usage;186
11.4;Conclusion;187
11.5;References;188
12;Bringing it all Together;189
12.1;Business Benefits and Innovations per Thematic Area;189
12.1.1;VO Management;189
12.1.2;SLA Management;191
12.1.3;License Management;193
12.1.4;Data Management;194
12.1.5;Security;195
12.1.6;Portals;198
12.2;Analysis of Technical Requirements;199
12.3;Overview of Common Technical Capabilities;202
12.4;Integration Scenarios;205
12.4.1;The Federated ASP Scenario;205
12.4.1.1;Description of the Scenario;205
12.4.1.2;Main Challenges of the Scenario: How Complementary CC Can Help?;206
12.4.1.3;Business Benefits of the Scenario;208
12.4.1.4;Overview of the BEinGRID Components Used in the Scenario;209
12.4.2;The Collaborative Engineering Scenario;213
12.4.2.1;Description of the Scenario;213
12.4.2.2;Main Challenges of the Scenario: How Complementary CC Can Help?;214
12.4.2.3;Business Benefits of the Scenario;217
12.4.2.4;Overview of the BEinGRID Components Used in the Scenario;217
12.5;References;219




