Extensible Markup Language XML the base language for WSDL and SOAP XML is not

Extensible markup language xml the base language for

This preview shows page 6 - 8 out of 16 pages.

Extensible Markup Language (XML) , the base language for WSDL and SOAP. XML is not needed explicitly in the development of web services. HyperText Transfer Protocol (HTTP) , a common carrier for sending SOAP messages between web service client systems and service implementations. We need to have a basic understanding of how a web server processes the HTTP POST/GET requests. 1.4 W eb Service’s Role in System Integration If you are sure that your application and its consuming applications, local or remote, are all based on the Windows platform, then Microsoft .NET remoting ( - us/library/ms973857.aspx ), part of Microsoft COM+, is the best technology for system integration because it is customized for the Windows platform. On the other hand, if you are sure that your
Image of page 6
University of Ontario Institute of Technology INFR 4660: Web Services and eBusiness Security application and its consuming applications, local or remote, are all based on the Java platform, then Java Remote Method Invocation over IIOP, RMI-IIOP (), is the best technology for system integration because it is customized for the Java platform. Since 1990 the industry consortium Object Management Group (OMG, ), including over 200 major companies worldwide, developed the sophisticated distributed object model/technology CORBA and API standards for heterogeneous system integration in various application domains. While CORBA supports more advanced services than web services, it is too aggressive and heavy and thus not successful in business. Since early 2000s the major IT companies, including Microsoft, IBM and Sun (now part of Oracle), acknowledged that no single platform/technology could dominate in all domains, and started to define the common open-specification for a simpler system integration technology based on existing technologies HTTP and XML. Web service’s main objectives are simplicity and wide acceptance, not performance. Fundamentally, web services support remote method invocation where the two communicating computers may be separated by the Internet, based on different hardware and software platforms (computer architecture and operating system respectively), and implemented with different programming languages. The direct consumers of web services are programs, not people. The main strength of web services include 1. It supports method invocation across heterogeneous systems. 2. It is not a proprietary technology and therefore inexpensive to adopt. 3. It requires minimal programming in its adoption. 4. Systems don’t need to install special software for consuming different web services. The client system only needs to have the generic web service toolkit and XML library for its specific platform. 5. Applications access the remote web services through port 80 which is reserved for the web and normally not blocked by enterprise firewalls, so web service deployment is very simple.
Image of page 7
Image of page 8

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture