NonStop Systems Introduction for H-Series RVUs

The Application Server Environment
NonStop Systems Introduction for H-Series RVUs—540083-001
3-33
Web Services Architecture
database. The solution: implement the NonStop TS/MP server class as a Web service
so that it can be readily accessed by other components that require that service.
For another example, consider a company that has these business systems, each
performing a different part of the business process:
•
One system manages materials requirement planning.
•
Another system manages materials inventory control.
•
A third system manages the distribution process.
•
A fourth system manages customer orders.
•
Yet another system keeps track of customer information.
Meanwhile, a completely different system generates sales forecasts. To coordinate the
process of building products to fulfill customer orders, these systems need to share
information. Without the ability to share and route information, the process breaks
down. But all these systems run on different platforms and are implemented using
different programming languages. How can these systems communicate and share
information? The answer: implement each of these systems as a Web service.
NonStop systems provide the best possible platform for Web services. The
fundamental advantages of fault tolerance, high performance, scalability, and reliability
are critical to providing Web services to a wide variety of clients.
Web Services Architecture
What follows is a simplified description of the key components of a typical Web
services architecture. The description is intended for illustrative purposes, to highlight
the key concepts and components of a typical Web service architecture. Figure 3-20
gives a simplified view of a basic Web services architecture.
Figure 3-20. Web Services Architecture
NonStop
SOAP
SOAP Server
(Services Provider)
SOAP/XML
(using HTTP)
Client
(Service Requester)
UDDI Registry
Services
Describe service (using WSDL)
Locate service
vst015.vsd