ServiceOriented Architectures Software Architecture Matthew Moccaro Overview Introduction

  • Slides: 12
Download presentation
Service-Oriented Architectures Software Architecture Matthew Moccaro

Service-Oriented Architectures Software Architecture Matthew Moccaro

Overview Introduction WSDL WS-BPEL

Overview Introduction WSDL WS-BPEL

Introduction Service-Oriented Architectures SOA Design Pattern based on pieces of software providing services. Directed

Introduction Service-Oriented Architectures SOA Design Pattern based on pieces of software providing services. Directed at Supporting Business Enterprises on the Internet Independence of various interacting organizations

Example: Page 434

Example: Page 434

Core Problem How should these things be realized? Components (Services) Types of Connectors The

Core Problem How should these things be realized? Components (Services) Types of Connectors The application as a whole

Web Services Description Language (WSDL) Web Services A way of providing SOA Describe services

Web Services Description Language (WSDL) Web Services A way of providing SOA Describe services needed Uses XML to describe the operations needed.

Example: Page 435

Example: Page 435

Example WSDL 1. 1 XML Schema Information Needed Function Call Defines the Protocol Endpoints

Example WSDL 1. 1 XML Schema Information Needed Function Call Defines the Protocol Endpoints

Web Services Business Process Execution Language (WS-BPEL) Need a Way to Describe Entire Application

Web Services Business Process Execution Language (WS-BPEL) Need a Way to Describe Entire Application Scripting Language Allows Effective Expression of Business workflows and processes. Also uses XML.

Example WS-BPEL Copy. Invoke Import Create Value Link To Operation Into WSDL Variables Service

Example WS-BPEL Copy. Invoke Import Create Value Link To Operation Into WSDL Variables Service Variable File <import. Type="http: //schemas. xmlsoap. org/wsdl/" location=". . /test_bucket/service_libraries/tptp_Engine. Printer. Port. wsdl" namespace="http: //www. eclipse. org/tptp/choreography/2004/engine/Print" /> <partner. Links> <partner. Link name="print. Service“ partner. Link. Type="print: print. Link” partner. Role="print. Service"/> </partner. Links> <variable </variables> <assign> </assign> <copy> </copy> name="hello_world“ message. Type="print: Print. Message" /> <from><literal>Hello World</literal></from> <to>$hello_world. value</to> <invoke partner. Link="print. Service" operation="print" input. Variable="hello_world" />

Conclusion SOA - Design Pattern based on pieces of software providing services. Different languages

Conclusion SOA - Design Pattern based on pieces of software providing services. Different languages can be used to describe and help realize SOA including WSDL and WSBPEL. Simultaneously trying to satisfy many goals. Interoperability between heterogeneous platforms.

Thanks!

Thanks!