Migration of a Chosen Architectural Pattern to Service Oriented ...

More documents

Recommendations

Info

Chapter 4. Service Oriented Architecture 88Figure 4.3: SOA layers of abstraction according to IBM. Adpoted from [13]Service Design IBM offers support of Service Designing activities with twotools. The first is IBM WebShare Business Modeller which simplifies businessprocess modelling based on business requirements. The second is IBM RationalSoftware Architect (RSA) that enables to model services with usage of UML.An important property of RSA tool is that it can import models of WebShareBusiness Modeller for further and more detailed modelling with UML.Service Creation – As the previous aspect, Service Creation is also supportedby two tools, but in a different way. The first tool -Rational Application Developer-supports Service Creation with both top-down and bottom-up approaches. Thetool provides also a wizard that supports quick creation and publication of WebServices and their clients. The next supporting tool is also a backbone of thewhole suite-Application Server. Application Server as other application serversallows deploying and executing services. It is also enriched with WebSphereProcess Server, WebSphere ESB, WebSphere Service Registry and Repository,WebSphere Portal, and WebSphere Services Business Fabric [60].Service Governance – IBM provides two tools supporting Service Governance,namely WebShare Service Repository and Registry (WSRR) hosted on
Chapter 4. Service Oriented Architecture 89Application Server and WebShare DataPower SOA Appliance. WSRR serves asa source of information about Services for ESB (see 3.2 for service repository),while WebShare DataPower SOA Appliance is an endpoint which is invoked everytime a consumer wants to consume a service, the tool can also enforce policyand routing service request because it has an access to the registry. WebShareDataPower SOA Appliance acts as ESB. In fact it is second out of three (ESB,DataPower, Message Broker) Service Buses provided by IBM.Service Integration – provides two more tools supporting Service Integration.The first tool is WebShare Integration Developer which simplifies process orchestrationwith Business Process Execution Language (BPEL). WebShare ProcessServer (WSPS) is the second tool. It is integrated with Application Server. Thistool enables deployment of previously created processes and mediates ESB flow.WSPS enables communication of those processes with WSRR in order to acquirelatest data. The communication is also established with WebShare Business ServiceFabric, which provides latest service endpoints -dynamic binding.Service Connectivity – The third type of Enterprise Service Bus is IBM Web-Share Message Broker, which is meant to simplify Service communication betweendifferent companies and different technologies applied for web service creation.Service Collaboration – IBM provides a tool simplifying creation of webbasedportals enabling a rule-based access to company’s resources. This toolis IBM WebSphere Portal. Another supporting tool is IBM WebSphere PortletFactory facilitating creation of applications for portals.Service Security – Security is a very important aspect of an application andSOA-applications are not exceptions here. The tool-IBM Tivoli Federated IdentityManager - is introduced to support this aspect of services. The facility provides[60] security infrastructure services, which include secure token services,authorization services, authentication services and directory services for the informationtechnology (IT) infrastructure. In other words, the tools enablingmessage-based authentication and authorization as well as creation of trust relationshipsbetween elements of architecture.4.6 Architectural Patterns in SOAA term “pattern” in the context of Service Oriented Architecture appears veryoften with an adjective “design”, but it is not always clear whether “design” refersto a design pattern in terms of previously stated definitions (see section 3.1.2) orrather refers to design activities including design of whole system (architectural
Page 1 and 2:
Master ThesisSoftware EngineeringTh
Page 3 and 4:
AbstractContext: Several examples o
Page 5 and 6:
List of Figures1.1 Research methodo
Page 7 and 8:
List of Tables3.1 Summary of archit
Page 9 and 10:
3.3.1 Definition of Pattern Languag
Page 11 and 12:
Chapter 1Introduction1.1 Background
Page 13 and 14:
Chapter 1. Introduction 3technique
Page 15 and 16:
Chapter 1. Introduction 5was notice
Page 17 and 18:
Chapter 1. Introduction 7do not pro
Page 19 and 20:
Chapter 1. Introduction 9Chapter 4
Page 21 and 22:
Chapter 2. Related Work 11This chap
Page 23 and 24:
Chapter 2. Related Work 13(b) Chara
Page 25 and 26:
Chapter 2. Related Work 15Figure 2.
Page 27 and 28:
Chapter 2. Related Work 17Drawbacks
Page 29 and 30:
Chapter 2. Related Work 19Figure 2.
Page 31 and 32:
Chapter 2. Related Work 21Advantage
Page 33 and 34:
Chapter 2. Related Work 23between a
Page 35 and 36:
Chapter 2. Related Work 252. Applic
Page 37 and 38:
Chapter 2. Related Work 274. Mediat
Page 39 and 40:
Chapter 2. Related Work 292.3 Summa
Page 41 and 42:
Chapter 3. Architectural Patterns 3
Page 43 and 44:
Page 45 and 46:
Page 47 and 48: Chapter 3. Architectural Patterns 3
Page 85 and 86: Chapter 4. Service Oriented Archite
Page 97: Chapter 4. Service Oriented Archite
Page 113 and 114: Chapter 5. Guidelines 1035.1 Patter
Page 115 and 116: Chapter 5. Guidelines 105Descriptio
Page 117 and 118: Chapter 5. Guidelines 107Result Con
Page 119 and 120: Chapter 5. Guidelines 109ContextAn
Page 121 and 122: Chapter 5. Guidelines 111Result Con
Page 123 and 124: Chapter 5. Guidelines 113System’s
Page 125 and 126: Chapter 5. Guidelines 115ViewSchema
Page 127 and 128: Chapter 5. Guidelines 117ViewViewCo
Page 129 and 130: Chapter 5. Guidelines 119ViewViewCo
Page 131 and 132: Chapter 5. Guidelines 121ViewViewPr
Page 133 and 134: Chapter 5. Guidelines 123FrontendFr
Page 135 and 136: Chapter 5. Guidelines 125complicati
Page 137 and 138: Chapter 5. Guidelines 127Concluding
Page 139 and 140: Chapter 5. Guidelines 129UsecasesTh
Page 141 and 142: Chapter 5. Guidelines 131puter (ext
Page 143 and 144: Chapter 5. Guidelines 133Group 3 ma
Page 145 and 146: Chapter 5. Guidelines 135Output: Du
Page 147 and 148: Chapter 5. Guidelines 137generation
Page 149 and 150:
Chapter 5. Guidelines 139(a) Fronte
Page 151 and 152:
Chapter 5. Guidelines 141Figure 5.1
Page 153 and 154:
Chapter 5. Guidelines 143Figure 5.1
Page 155 and 156:
Chapter 5. Guidelines 145FrontendSc
Page 157 and 158:
Chapter 6. Conclusion 147There are
Page 159 and 160:
Chapter 6. Conclusion 149RQ.6 How t
Page 161 and 162:
References[1] http://www.soa-manife
Page 163 and 164:
References 153[22] Frank Buschmann,
Page 165 and 166:
References 155[46] Dirk Krafzig, Ka
Page 167 and 168:
References 157[67] Xiaohong Qiu. Bu
show all

Migration of a Chosen Architectural Pattern to Service Oriented ...

Create successful ePaper yourself

Delete template?

Save as template?