in black and white
Main menu
Home About us Share a book
Biology Business Chemistry Computers Culture Economics Fiction Games Guide History Management Mathematical Medicine Mental Fitnes Physics Psychology Scince Sport Technics

Network services investment guide - Gaynor M.

Gaynor M. Network services investment guide - wiley publishing , 2003. - 322 p.
ISBN 0-471-21475-2
Download (direct link): networkservicesinvestment2003.pdf
Previous << 1 .. 89 90 91 92 93 94 < 95 > 96 97 98 99 100 101 .. 128 >> Next

Users of soap services care only about adherence to the standard, performance of the service, and quality of the data from the service not the server platform. The implementation details of soap services are unimportant to the consumer because the loose coupling between client and server hides how they work. The architecture of an organization's soap services is independent of the choice of development environment and implementation platform, which implies that as far as users go, the choice of development environments is not the critical factor the design of the system is.
The architecture of an organization's soap services is related to the value these services have to the firm because this architecture is what determines the effectiveness of a firm's integration of their business logic. The degree of modularity these services exhibit (as explained later in this chapter) is one main factor in this value [11]. Fine-grained modularity provides more value because soap service consumers are able to pick and choose the services they need at a finer level. Firms sharing information most efficiently with those needing it have a strategic advantage over firms with less efficient information distribution. This ability to disseminate information quickly and efficiently is related to the architecture of the soap services.
Before going into a more detailed discussion of the value of soap service architecture, the reader needs a better understanding of the standards used to build soap services and how they fit together.
SOAP Service Tutorial
This section is a primer on the technology of soap services. Its goal is not to teach how to create soap services, but rather, to help the reader understand
Web Applications and Services 227
enough of the framework to apply soap service technology when solving business problems. This tutorial will help in understanding the next section describing the value of modularity and interchangeability of soap services. It introduces Extensible Markup Language (XML), which is fast becoming the language of the Internet, and Simple Object Access Protocol (SOAP), which holds the XML-encoded content. It explores how the interface of a soap service is defined with Web Service Description Language (WSDL), and how these interface definitions are registered, which allows users to discover them with Universal Description, Discovery, and Integration (UDDI). This combination of XML, SOAP, WSDL, and UDDI is a powerful set of tools that gives users tremendous flexibility in the services they can specify.
An analogy between a paper-based inventory check and the electronic soap service version is presented next. Suppose company A is interested in knowing if company B has 100 widgets. To accomplish this goal, someone at company A might print out a request (asking if company B has 100 widgets), place this request in an envelope, address the envelope, and then mail it. When this envelope arrives at company B, it is opened, and the content is removed and read. Next, a response is printed out and placed in an envelope, which is sent to company A. When the envelope arrives at company A, it is opened and the answer read. This simple process illustrates the intuitive idea behind how a soap service would perform this task. Table 12.2 maps these actions into their equivalent action as a soap service.
Table 12.2 Intuitive View of Soap Services
Print out the request for Create an XML document with the
checking inventory. correct structure.
Place the request in an envelope. Place the XML document in a SOAP
Send the envelope to company B. Use HTTP to send company B the SOAP
A person opens and looks at the A computer opens the SOAP envelope
inventory request. and processes the inventory request.
A person creates a response A computer generates an XML answer to
to the request. the inventory request.
The answer is placed in an envelope The XML answer is placed inside a SOAP
and sent back to company A. envelope and sent to company A.
The envelope is received by company The SOAP envelope is opened, and the
A and opened, and the answer is read. XML document is removed and
processed by the computer.
228 Chapter 12
In the preceding example, this soap service is a paperless, electronic version of a business transaction reporting on the inventory of a particular item, as illustrated in Figure 12.2. The XML document is analogous to the paper request, as is the SOAP envelope to a paper envelope. The SOAP envelope contains meta information about this XML message.
Previous << 1 .. 89 90 91 92 93 94 < 95 > 96 97 98 99 100 101 .. 128 >> Next