"This book performs a valuable service for managers seeking to harness the business potential of Web services technology. Bringing a real practitioner's experience to the task, Anne carefully walks managers through the fundamentals of Web services technology. She does a superb job of helping managers understand this technology so that they can move with sure footing and avoid potentially harmful stumbles along the way."
--From the Foreword by John Hagel III and John Seely Brown
Written for business and technology managers, Web Services: A Manager's Guide illuminates the potential of Web services for application integration. It describes the essentials of supporting technologies and shows how they can be built into a Web services infrastructure that is high-performance, robust, and cost-effective.
Realistic in approach, this book offers a readable definition of Web services and non-technical explanations of key technologies and standards. The author explores the scenarios and applications that would benefit most from Web services and offers guidelines for making an informed decision about which Web services products are right for your company's needs.
You will find detailed coverage of the following topics:
With this book in hand, you will have a clear understanding of Web services, what the technology can do for your organization, and the direction in which you should be heading. Margin content summaries enable time-constrained managers to locate and absorb needed information quickly. Case studies illustrate the benefits of adopting Web services and also reveal pitfalls to avoid.
Download the Sample Chapter related to this title.
About the Author.
1. The Application Integration Crisis.
Hersheys integration nightmare.
Integration helps your business.
All applications require integration.
Calculating return on investment.
Application integration is hard.
Approaches to application integration.
Building integration hooks.
Exposing interfaces across the network.
Traditional Middleware Blues.
Pervasiveness and heterogeneity.
Total cost of ownership.
Extending integration to work across the Internet.
Using the Internet as an integration platform.
Using Web services for integration.
Web services have tactical and strategic value.
What is a Web service?
Why Web services?
Defining “Web” and “Service”.
Defining characteristics of Web services.
Understanding the scope of Web services.
Web services business models.
The Web versus other networks.
XML versus other data representations.
WSDL, UDDI, and SOAP.
Advertising and Discovery (UDDI).
SOAP versus other communication systems.
Other Web service technologies.
The history of SOAP.
Challenges with SOAP 1.1.
W3C and OASIS.
The history of WSDL.
Challenges with WSDL 1.1.
The history of UDDI.
UDDI Business Registry.
Private UDDI registries.
Programming standards for Web services.
Java standards for SOAP.
Java standards for WSDL.
Java standards for UDDI.
Executive summary: status check.
Web services security standardization efforts.
Confidentiality and integrity.
Authentication and authorization.
Using XML security in Web services.
Web services management standardization efforts.
Transactions, Orchestration, and Choreography.
Portlets and interactive applications.
Other advanced efforts.
Web services hype.
Dynamic discovery of business partners.
Enabling dynamic discovery.
Domain-specific industry standards.
What makes Web services special.
Web services adoption.
Truth in hype.
Unknown client environment.
Multi-channel client formats.
Other Web services applications.
Managing legacy assets.
Reducing duplicative applications.
Managing portal initiatives.
B2B electronic procurement.
Trading partner network.
Software as a service.
When not to use Web services.
Web Services Platforms.
Web services management extensions.
Infrastructure-level Web services.
Characterize your project.
Making the initial cut.
Language and operating system.
Selecting a Java platform.
Licensing and support issues.
Evaluating your requirements.
Performance and scalability.
Standards support and interoperability.
Administration and management.
Base your selection on project requirements.
Charting your course.
Portable C and C++ Platforms.
J2ME and KVM platforms.
Other languages and platforms.
UDDI Registry Servers.
Embedded UDDI Registries.
Standalone UDDI Registries.
Operating platform attributes.
Client platform attributes.
Performance and scalability requirements.
This guide provides an overview of Web services. The purpose of the guide is to help you make more informed decisions about adopting Web services within your company.
Unlike most books you’ll find on the subject, this guide is written for managers, not engineers. I’ve tried to limit the use of computer jargon and acronyms. I don’t make any assumptions that you know how to write software. I do assume that you are familiar with the way businesses use software.
I present the technology in business terms. I’ve tried to cut through the hype by presenting both the advantages and disadvantages of this technology. My goal is to help you understand how Web services can benefit your business. I’ve identified tactical and strategic projects in which Web services offer the greatest advantages. You will find the information in this book helpful when trying to cost-justify a project.
It seems that nearly every hardware and software vendor is touting a Web services strategy. I’ve made an effort to present the technology in a completely vendor-neutral fashion. I also provide some guidelines that you can use to help you evaluate and select a Web services technology provider.
I completed this book in February 2003. The information about Web services standards efforts and vendor products is current as of that date. I will publish periodic status updates on my Web site. Please visit http://www.bowlight.net.
If you’re planning a Web service project, you should read this book thoroughly. If you only want a basic introduction to Web services, just read the first two chapters. If you already feel comfortable with the basics and you want some more specific information about Web services applications or vendor offerings, you can read selective chapters. You can also skim the book by scanning the “fast track” summary in the outer margin, and then selectively drill down into specific sections.
I’ve found it impossible to discuss this technology without using some jargon and acronyms. To minimize confusion, I provide a number of executive summaries of key concepts throughout the book. I also provide a glossary, which provides definitions for all terms that appear in boldface throughout the book.
Chapter 2: Web Services Basics. This chapter provides a basic explanation of Web services in business terms. It provides an overview of what Web services are and why you might want to use them. I explain how Web services technology is different from previous integration technologies. I explore Web services business models, using case studies as examples.
Chapter 3: Web Services Technologies. This chapter is the most technical chapter in the book. I provide an overview of the core technologies that support Web services, including the Web, XML, the Service Oriented Architecture (SOA). I then look at WSDL, UDDI, and SOAP, the three most popular technologies used to implement the SOA. I explain how these technologies can make your application systems much more powerful and flexible.
Chapter 4: Standardizing Web Services Technologies. This chapter recounts the history of SOAP, WSDL, and UDDI, and it explores the efforts underway to define formal industry standards. Although many people view SOAP, WSDL, and UDDI as formal standards, they were developed by private companies. Now these technologies are being standardized by W3C and OASIS. Another organization, WS-I, is defining guidelines for Web services interoperability.
Chapter 5: Advanced Web Services Standards. This chapter looks at the current standardization efforts to define advanced features for Web services, such as security, management, transactions, and portal integration. Some efforts, including security and portal integration are making great headway. Other efforts are less far along.
Chapter 6: The Promise of Web Services. This chapter dispels the hype around Web services. It examines some of the more popular science fiction stories told to explain the promise of Web services and recasts them into something a bit more realistic. Then it focuses on the progress in the industry that is helping to make these promises come true.
Chapter 7: When to Use Web Services. This chapter explores the scenarios and applications that would benefit most from using Web services. Each of these scenarios is illustrated using a case study.
Chapter 8: Web Services Infrastructure. This chapter examines the software products that you can use to build Web services. It seems as if every software vendor now provides a product that “supports” Web services. But what does that mean? This chapter categorizes the various types of products and explains how they work together and how they fit into your existing IT infrastructure. This chapter also provides a comparison between Java and .NET.
Chapter 9: Evaluation Guidelines. This chapter provides basic guidelines that a business manager should follow when evaluating Web services products. Chances are high that you will use different products for different applications. You should choose products based on the requirements of each application.
Appendix A: Web Services Vendors. This appendix provides a listing of the most popular Web services products, categorized by product type and supported environments.
Appendix B: Evaluation Questionnaire. This appendix provides a list of questions that should help you identify your application requirements during your evaluation.
Glossary: The Glossary defines all the terms that appear in boldface.
Download the Foreword related to this title.
Download the Index
file related to this title.