






Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Community
Ask the community for help and clear up your study doubts
Discover the best universities in your country according to Docsity users
Free resources
Download our free guides on studying techniques, anxiety management strategies, and thesis advice from Docsity tutors
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
1 / 10
This page cannot be seen from the preview
Don't miss anything!
Electronic Commerce (WS-05/06) 4-^35
Electronic Commerce (WS-05/06) 4-^36
Electronic Commerce (WS-05/06) 4-^38
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
Electronic Commerce (WS-05/06) 4-^41
<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
Electronic Commerce (WS-05/06) 4-^44
Extending WebServices to Business WebServices