Docsity
Docsity

Prepare for your exams
Prepare for your exams

Study with the several resources on Docsity


Earn points to download
Earn points to download

Earn points by helping other students or get them with a premium plan


Guidelines and tips
Guidelines and tips

SOAP and Web Services in Electronic Commerce: Technologies and Architectures, Slides of Fundamentals of E-Commerce

An overview of soap (simple object access protocol) and its role in electronic commerce. It discusses existing distribution architectures and technologies, such as corba, dcom, java rmi, and unix-rpc, and their limitations for dynamic and interorganizational service integration. The document also introduces soap message structure and its use in the universal description, discovery and integration (uddi) project, which aims to create a platform-independent, open framework for describing, discovering, and integrating business services using the internet. Wsdl (web services description language) is introduced as a standard for describing service operations and message formats for these operations.

Typology: Slides

2012/2013

Uploaded on 07/29/2013

sharad_984
sharad_984 🇮🇳

4.5

(13)

146 documents

1 / 10

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
4-35
Electronic Commerce (WS-05/06)
SOAP: Related, Existing Technologies
Existing distribution architectures and technologies include
OMG CORBA, Microsoft DCOM, Java RMI, Unix-RPC, ...
But no single technology is used for dynamic and interorganizational service integration.
Some reasons:
Unix-RPC: requires binary-compatible Unix systems on both sides
CORBA: not widely adopted
RMI: requires Java on both sides
DCOM: requires Windows systems on both sides
Firewall problems (packets are filtered by firewalls if using dynamic ports)
Docsity.com
pf3
pf4
pf5
pf8
pf9
pfa

Partial preview of the text

Download SOAP and Web Services in Electronic Commerce: Technologies and Architectures and more Slides Fundamentals of E-Commerce in PDF only on Docsity!

Electronic Commerce (WS-05/06) 4-^35

SOAP: Related, Existing Technologies

Existing distribution architectures and technologies include  OMG CORBA, Microsoft DCOM, Java RMI, Unix-RPC, ...

But no single technology is used for dynamic and interorganizational service integration.

Some reasons:  Unix-RPC: requires binary-compatible Unix systems on both sides

  CORBA: not widely adoptedRMI: requires Java on both sides

  DCOM: requires Windows systems on both sidesFirewall problems (packets are filtered by firewalls if using dynamic ports)

Electronic Commerce (WS-05/06) 4-^36

SOAP Message Structure

SOAP extends HTTP request / responses with

 SOAP-Header to identify that it’s a SOAP message

 SOAP-Body containing an XML payload : the actual data to be transmitted

Electronic Commerce (WS-05/06) 4-^38

Lookup Services: UDDI

The open framework for Universal Description, Discovery and Integration (UDDI) project aims at creating a platform-independent,   describing servicesdiscovering businesses and as well as an^ ^ integrating business services using the Internet, UDDI uses SOAP as protocol.^ ^ operational registry (i.e., naming service) [UDDI02]. A Currently, there exist some public UDDI nodes at IBM and Microsoft, HP, etc. UDDI node is a global directory service for companies and web services that companies provide. See: http://www.uddi.org

Electronic Commerce (WS-05/06) 4-^39

UDDI (2)

Content types of UDDI nodes:  White Pages: General information about companies:

 name, address, contact, etc. Yellow Pages: Classification of companies

Based on existing, non-electronic standards (example: North American Industry Classification System, NAICS)

 Green Pages: WebServices will be explained in 6.3.4. Technical information about WebServices provided by a company.

Electronic Commerce (WS-05/06) 4-^41

WSDL Example

<message <part name=name=”” OrderMsgproductName "> " type=" xsd:string " /> ^ <part^ name=” quantity "^ type=" xsd:integer "^ /> <portType <operation name=” procurementPortType name=” orderGoods "">> </portType^ >^ <input^ message=” OrderMsg "/> <binding <soap:binding name= type="” ProcurementSoapBindingprocurementPortType transport=“http://schemas."> ” xmlsoap.org/soap/http”/> <operation <soap:operation name= <soap:body“ OrderGoods soapAction= …/> ”> “http://example.com/orderGoods”/> ^ <service <port name= name=” >ProcurementServiceProcurementPort " binding=""> ProcurementSoapBinding "> ^ ^ <soap:address^ location=" http://example.com/procurement "^ />

Electronic Commerce (WS-05/06) 4-^42

WSDL Example Explanation

types: used in the messages sent between the server and client. Specifies all the data types, either predefined or user-provided, that are

message: request message. Describes a one-way message, may it be a request or response to a

portType operation (for instance for a request/response scheme commonly used in SOAP : Combines multiple message elements to one one-way or round-trip

services). binding: Specifies how the service will be implemented ‘on the wire’, meaning it

gives details on how messages should be transported over the Internet. They can be sent via HTTP, using either the GET or POST method, or SOAP (which itself again can

be configured to work over HTTP, or e.g., SMTP). service: Defines the address for invoking the service, usually a URL where a

SOAP service is deployed at.

Electronic Commerce (WS-05/06) 4-^44

Extending WebServices to Business WebServices

Simple  Point-to-point connections (binary conversations)WebServices:

  No transactions neededNo / simple security measures

 Technologies: SOAP, WSDL, UDDI

Business  Can involve several business partners (multi-party business processes) WebServices:

 Complex workflows (control-flow and information-flow, events, triggers, exceptions)

  Long-term transactionsSecurity is required

 WebServices must be extended