Migration of a Chosen Architectural Pattern to Service Oriented ...
Migration of a Chosen Architectural Pattern to Service Oriented ... Migration of a Chosen Architectural Pattern to Service Oriented ...
Chapter 5. Guidelines 134(b) Assign a temporary identifier to created asset. Format of the id ofthe temporary asset is not specified. It does not matter for temporaryassets.(c) if asset is meant to be persisted, generate a proper (unique) identitynumber, otherwise do not generate a number.(d) Persist selected assets.The rationale for having Business Process Logic “clean” from non- flowrelated code is usage of Business Process Execution Language (BPEL) toorchestrate processes. BPEL allows only to design a process flow and thelanguage syntax does not allow introducing any code (like Java, C#) withinprocess. It is a graphical/xml language that bases on invocation of previouslydefined services.Output: Two addition documents are created as a result of application ofthis steps. Those documents are:(a) WSDL –defines available request and response SOAP messages. LinksXSD schema and sets some technology related parameters like Port-Types and bindings.(b) BPEL –this document defines the process, invoked services and theiroperations.11. Identify all statefull services and decide if their state can be deferredApplied SOA pattern: State RepositoryApplication: Considered migration example have no asynchronous or longliving processes.Output: No new services are implemented in case of this project becausethere are no long living processes. The implementation also does not containany process that consumes a lot of resources. An implementation of a staterepository would be similar to implementation of other basic services.12. Identify current points of access to the migrated systemApplied SOA pattern: FrontendsApplication:Considered project is neither large nor User Interface sensitive.Only a few people use current application and they got used to currentinterface. Introduction of a complex presentation layer will not pay off atall, therefore a simple migration of View Layer towards Frontend Layer issufficient.
Chapter 5. Guidelines 135Output: During this step, GUI was migrated to Frontend Project. TheProject contains the original GUI and some Business Objects that werecreated based on XML schema.13. Identify all the places in user interface where a continuous feedback fromapplication to end user is providedApplied SOA pattern: UI mediatorApplication: Available documentation and implementation does not requireany functionality providing continuous feedback to end users.Output: There is no implementation regarding this pattern.5.4.1 ResultsThe guidelines presented previously were a base for migration of the student’sproject. Purpose of the this migration was didactic. It was meant to illustrate anexample application of the guidelines. The migration was conducted according tothe sequence listed above. As a result of migration, an asset storing process wascreated. This is also the only fully implemented process in the migrated project(see BPEL 5.19, deploy model 5.20). The migrated process consists of followingsteps:1. Create Asset object via UI2. Retrieve the highest stored Asset id in the database3. Generate unique identifier for the entity4. Store the entity
- Page 93 and 94: Chapter 4. Service Oriented Archite
- Page 95 and 96: Chapter 4. Service Oriented Archite
- Page 97 and 98: Chapter 4. Service Oriented Archite
- Page 99 and 100: Chapter 4. Service Oriented Archite
- Page 101 and 102: Chapter 4. Service Oriented Archite
- Page 103 and 104: Chapter 4. Service Oriented Archite
- Page 105 and 106: Chapter 4. Service Oriented Archite
- Page 107 and 108: Chapter 4. Service Oriented Archite
- Page 109 and 110: Chapter 4. Service Oriented Archite
- Page 111 and 112: 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: Chapter 5. Guidelines 133Group 3 ma
- 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
Chapter 5. Guidelines 134(b) Assign a temporary identifier <strong>to</strong> created asset. Format <strong>of</strong> the id <strong>of</strong>the temporary asset is not specified. It does not matter for temporaryassets.(c) if asset is meant <strong>to</strong> be persisted, generate a proper (unique) identitynumber, otherwise do not generate a number.(d) Persist selected assets.The rationale for having Business Process Logic “clean” from non- flowrelated code is usage <strong>of</strong> Business Process Execution Language (BPEL) <strong>to</strong>orchestrate processes. BPEL allows only <strong>to</strong> design a process flow and thelanguage syntax does not allow introducing any code (like Java, C#) withinprocess. It is a graphical/xml language that bases on invocation <strong>of</strong> previouslydefined services.Output: Two addition documents are created as a result <strong>of</strong> application <strong>of</strong>this steps. Those documents are:(a) WSDL –defines available request and response SOAP messages. LinksXSD schema and sets some technology related parameters like Port-Types and bindings.(b) BPEL –this document defines the process, invoked services and theiroperations.11. Identify all statefull services and decide if their state can be deferredApplied SOA pattern: State Reposi<strong>to</strong>ryApplication: Considered migration example have no asynchronous or longliving processes.Output: No new services are implemented in case <strong>of</strong> this project becausethere are no long living processes. The implementation also does not containany process that consumes a lot <strong>of</strong> resources. An implementation <strong>of</strong> a statereposi<strong>to</strong>ry would be similar <strong>to</strong> implementation <strong>of</strong> other basic services.12. Identify current points <strong>of</strong> access <strong>to</strong> the migrated systemApplied SOA pattern: FrontendsApplication:Considered project is neither large nor User Interface sensitive.Only a few people use current application and they got used <strong>to</strong> currentinterface. Introduction <strong>of</strong> a complex presentation layer will not pay <strong>of</strong>f atall, therefore a simple migration <strong>of</strong> View Layer <strong>to</strong>wards Frontend Layer issufficient.
Change language