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.