A recent Gartner Group "Perspective" on Web services implementations states:
"The Web services vision will be less than optimal if it is not introduced as a complete vision for dealing with aspects such as services registry, messaging, trading-partner specifications and industry standards." Source: http://mass25.mbinteractive.com/mass/bedemir.dll/b12100720=1. "Web Services: Software as Service Comes Alive," Daryl Plummer, October 2001. Used by Permission. |
In other words, far more is involved in building a Web services architecture than the "basic" architecture described in the previous section. A number of companies including BEA, Hewlett-Packard, IBM, Microsoft, Sun, and others have combined various development tools, application accelerators, specialized applications, and integration services to offer a more complete Web services architecture than described above. These environments contain additional architectural elements that are useful in building very robust, user-friendly Web services environments for small, medium, and large enterprises.
The example presented here is based on IBM's WebSphere product set (Figure 1-3). It is a particularly robust Internet application server environment, though not the only such solution available on the market today. Microsoft, BEA, HP, Oracle, Sun, and others have competitive products (though potentially not as broad as IBM's offering from a cross-platform integration perspective). All of these vendors and more will be covered in greater depth later in this book.
Source: Derived from http://www-4.ibm.com/cgibin/software/track3.cgi?file=/software/info/websphere/products/index.html&S_TACT=100AWW10&S_CMP=campaign. Used by Permission.
Sidebar 1-1 |
The preceding section described how a basic Web services architecture can be built by settling on a common presentation format, using common program-to-program protocols over a common network (the Internet). Figure 1-3 illustrates how IBM extends its Web services architecture by including a wealth of systems software, development tools, Web tools (for personalization and presentation), integration tools, and utilities, as well as application development environments and applications (such as Lotus Domino) that can be tuned or modified to work in a Web services mode.
Other elements also help to create a "complete" Web services environment, including:
Systems management and security.
The user experience (including personalization, portal graphics).
Support for multiple device types (PDAs, smart phones, other mobile devices, desktops, workstations) using various interfaces (such as data-to-voice) for information presentation/relay.
Business process management/workflow (Web services can be implemented without paying attention to workflow and business process management software, but, to support hundreds or thousands of Web services sessions, Web services implementers should consider using business process management programs and tools in order to maximize the effectiveness and efficiency of Web-based applications).
Integration (not only between disparate systems but also between application environments).
The IBM WebSphere example used in this section (similar in architectural structure to products of Microsoft and other companies) illustrates that implementing a complete Web services environment involves a lot more than just servicing requests for application services from requestor applications!