Different business partners for different environments generally use these XML web services, where communication between different business partners is needed.
Copyright:
Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOC, PDF, TXT or read online from Scribd
Different business partners for different environments generally use these XML web services, where communication between different business partners is needed.
Different business partners for different environments generally use these XML web services, where communication between different business partners is needed.
Copyright:
Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOC, PDF, TXT or read online from Scribd
Different business partners for different environments generally use these XML web services, where communication between different business partners is needed.
Copyright:
Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOC, PDF, TXT or read online from Scribd
Different business partners for different environments
generally use these XML web services, where communication between different business partners is needed.
Company2 Company1
Website Website
SUN Solaris O/S Windows O/S
TOMCAT web server XML Products Web table JSP PAGE service
Maintained by IIS
If the company2 requires the information of product
table of company1 then it will send a request (HTTP request) and it will get the response. Both the request and response will be in the form of XML based format. In ASP3.0 publishing services is possible using MTS (Microsoft transaction server) MTS acts as a container for inprocess COM component, this will provide services only to the Microsoft products, under windows O/s. The advantages of MTS are, 1. It supports connection pooling, this will reduce burden from the web server and performance will be improved. 2. It supports DCOM implementation for inprocess components. 3. It supports transaction handling.
When the service has to be provided towards
heterogeneous platforms belonging to different vendors, then we require XML web services. Comparison between distributed applications: DCOM: 1. Remote procedure call (RPC) mechanism is based on DCE-RPC (proprietary standard) 2. Description of services will be generated using IDL compiler. (IDL is nothing but Interface Description language will be maintained in .tlb file. (Binary standard format) 3. Encoding for transmission is going to be network based (windows only) 4. Transmission protocol is TCP/UDP XML WEB SERVICES: 1. RPC mechanism is based on SOAP (Protocol) i.e. Simple object access protocol (Open Standard). 2. Description of services will be generated using WSDL compiler, i.e. web services description language. (XML FORMAT) 3. Encoding for transmission is going to be XML Based (Text) 4. Transmission protocol is going to be HTTP (Open Industry standard)
The uniqueness of XML web services is completely
based on open industry standards, as compared to DCOM and RMI. The Uniqueness comes because of XML standard implementation with HTTP Protocol.