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

the semantic web a gide to the future of XML, Web Services and Knowledge Management - Daconta M,C.

Daconta M,C. the semantic web a gide to the future of XML, Web Services and Knowledge Management - Wiley publishing , 2003. - 304 p.
ISBN 0-471-43257-1
Download (direct link): thesemanticwebguideto2003.pdf
Previous << 1 .. 23 24 25 26 27 28 < 29 > 30 31 32 33 34 35 .. 116 >> Next

Figure 4.1 gives a graphical view of that definition, shown as layers. Relying on the foundation of XML for the technologies of Web services, and using HTTP as the underlying protocol, the world of Web services involves standard protocols to achieve the capabilities of access, description, and discovery.
Figure 4.2 shows these technologies in use in a common scenario. In Step 1, the client application discovers information about Web Service A in a UDDI registry. In Step 2, the client application gets the WSDL for Web Service A from the UDDI registry to determine Web Service A's API. Finally, in Steps 3 and 4, the client application communicates with the Web service via SOAP, using the API found in Step 2. We'll get more into the details of these technologies later in the chapter.
Understanding Web Services
(UDDI, ebXML registries)
(HTTP, SMTP, other protocols)
Figure 4.1 The basic layers of Web services.
Our example scenario in Figure 4.2 shows the basics of client and Web service interaction. Because of these processes, such as discovery, the client application can automate interactions with Web services. Web services provide common standards for doing business and software integration—complementing a user-driven, manual navigation architecture to one where automated business process can be the focus.
It is important to understand that Web services can be completely independent of the presentation, or the graphical user interface (GUI) of applications. Instead, Web services send data in XML format, and applications can add style and formatting when they receive the data. An example of a Web service could be a "driving directions finder" Web service that provides the capability to get text-based car directions from any address to any address, listing the driving
Chapter 4
distances and estimated driving times. The service itself usually provides no graphics; simply speaking XML messages to a client application. Any application, such as a program created in UNIX, a Microsoft Windows application, a Java applet, or server-side Web page, can take the information received from that application and style it to provide graphics and presentation. Because only XML data is sent back and forth, any front-end application that understands XML can speak to the Web service. Because a Web service does not need to focus on presentation styling, the focus for creating them is purely on business logic, making it easier to reuse Web services as software components in your enterprise.
Separating business logic from presentation is commonly known in software engineering as the Model-View-Controller (MVC) paradigm. Web services support this paradigm. Shown in Figure 4.3, the user interface details (the view) and business logic (the model) are separated in two different components, while the component layer between them (the controller) facilitates communication. This paradigm, which has had much success in software engineering, makes sense because it solves business problems. When a business decides to create a Web service, the application integrator/developer can simply focus on the business logic when designing and developing the Web service. Because the presentation is separate, the client application can present the information to the user in many different ways. This is an important concept because many browsers make it easier for you by offloading this processing with style sheets, using XSL Transformations (XSLT).
Figure 4.2 A common scenario of Web services in use.
Facilitates Communication between View & Model
Styles the User Interface
Provides Business Logic of the Application
Figure 4.3 The Model-View-Controller paradigm.
In this introductory section, we have provided you with a definition of Web services and given you a taste of the technologies involved. The next sections discuss the business case for Web services, some of the technical details, and a vision for Web services in the future.
You've heard the hype. If you haven't already adopted a Web services-based strategy, you're probably wondering the following:
■■ Do Web services solve real problems? What problems do Web services solve?
■■ Is there really a future for Web services? That is, will this market continue to grow? Will Web services really play a big part in the next generation of the Web—or are we drowning in technology hype?
■■ How can I use Web services? Where exactly can my business focus to take advantage of the technology?
These questions are so fundamental that you should ask them about any candidate technology. In this section we examine each of these.
What problems do Web services have the ability to solve? Many businesses suffer from integration problems in our fast-paced world of ever-changing technologies, market conditions, and business relationships. It is vital to be able to have your internal systems communicate with your partner's internal systems, and databases. Rapid and easy integration facilitates and empowers your business processes. Yet businesses frequently experience many problems in this area. Because of different database languages, different communication protocols, and different ways of expressing problems in languages understood by computers, integrating systems is extremely difficult.
Previous << 1 .. 23 24 25 26 27 28 < 29 > 30 31 32 33 34 35 .. 116 >> Next