Web Services A Manager's Guide

Summary

- Written by the author who Enterprise Systems Journal noted for her uncanny ability to apply technology to create new solutions. - Helps identify scenarios and applications where Web services can provide the best ROI for your company - Foreword by Brown and Hagel, bestselling Web services authors of "Out of the Box "

Author Biography

Anne Thomas Manes, a leading authority on Web services technology, is a research director with the Burton Group, where she leads research on application platform strategies. In 2002, she was named by NetworkWorld as one of the 50 most powerful networking professionals and was also listed among the 2001 Power 100 IT Leaders by Enterprise Systems Journal. She served as chief technology officer at Systinet, the Web services infrastructure company, and as director of market innovation at Sun Microsystems. She is currently a member of the editorial board of Web Services Journal and a participant in Web services standards development efforts at JCP, W3C, OASIS, WS-I and UDDI.

0321185773AB04022003

Foreword	p. xv
Preface	p. xxiii
Acknowledgments	p. xxvii
The Application Integration Crisis
Hershey's Integration Nightmare	p. 2
Integration Helps Your Business	p. 3
All Applications Require Integration	p. 4
Calculating Return on Investment	p. 5
Application Integration Is Hard	p. 6
Approaches to Application Integration	p. 7
Building Integration Hooks	p. 9
Exposing Interfaces Across the Network	p. 11
Middleware Styles	p. 13
Traditional Middleware Blues	p. 16
Pervasiveness and Heterogeneity	p. 16
Total Cost of Ownership	p. 18
Extending Integration to Work Across the Internet	p. 20
Using the Internet as an Integration Platform	p. 21
Using Web Services for Integration	p. 22
Web Services Have Tactical and Strategic Value	p. 23
Web Services Basics
What Is a Web Service?	p. 27
Why Web Services?	p. 28
Defining "Web" and "Service"	p. 29
Building Services	p. 32
Web Evolution	p. 33
Defining Characteristics of Web Services	p. 35
Understanding the Scope of Web Services	p. 35
Web Services Business Models	p. 37
Google	p. 38
Kinko's	p. 39
Amazon	p. 40
UPS	p. 41
T-Mobile	p. 41
Internal Integration	p. 43
Executive Summary	p. 44
Web Services Technologies
The Web	p. 48
The Web Versus Other Networks	p. 50
XML	p. 50
XML Schema	p. 53
XSLT	p. 54
XML Versus Other Data Representations	p. 55
SOA	p. 57
WSDL, UDDI, and SOAP	p. 59
Description (WSDL)	p. 60
Advertising and Discovery (UDDI)	p. 65
Communication (SOAP)	p. 70
Extending SOAP	p. 73
SOAP Versus Other Communication Systems	p. 76
Other Web Service Technologies	p. 77
@ebXML	p. 78
Executive Summary	p. 80
Standardizing Web Services Technologies
The History of SOAP	p. 84
Challenges with SOAP 1.1	p. 85
WS-I	p. 86
W3C and OASIS	p. 88
The History of WSDL	p. 88
Challenges with WSDL 1.1	p. 89
The History of UDDI	p. 92
UDDI Business Registry	p. 93
Private UDDI Registries	p. 95
Programming Standards for Web Services	p. 97
Java Standards for SOAP	p. 99
Java Standards for WSDL	p. 101
Java Standards for UDDI	p. 101
Executive Summary: Status Check	p. 102
Advanced Web Services Standards
Web Services Security Standardization Efforts	p. 105
Confidentiality and Integrity	p. 107
Authentication and Authorization	p. 110
Using XML Security in Web Services	p. 115
Web Services Management Standardization Efforts	p. 117
Transactions, Orchestration, and Choreography	p. 122
Transactions	p. 123
Orchestration and Choreography	p. 126
Reliability	p. 130
Portlets and Interactive Applications	p. 132
Other Advanced Efforts	p. 133
The Promise of Web Services
Web Services Hype	p. 135
Super-powered PDA	p. 136
Software-as-a-Service	p. 137
Dynamic Discovery of Business Partners	p. 140
Enabling Dynamic Discovery	p. 142
Dynamic Binding	p. 147
What Makes Web Services Special	p. 150
Web Services Adoption	p. 151
Clear Benefits	p. 153
Truth in Hype	p. 154
When to Use Web Services
Bell Ringers	p. 158
Heterogeneous Integration	p. 158
Unknown Client Environment	p. 159
Multichannel Client Formats	p. 160
Other Web Services Applications	p. 162
Point-to-Point Integration	p. 162
Consolidated View	p. 163
Managing Legacy Assets	p. 165
Reducing Duplicative Applications	p. 165
Managing Portal Initiatives	p. 167
B2B Electronic Procurement	p. 170
Trading Partner Network	p. 171
Software-as-a-Service	p. 172
When Not to Use Web Services	p. 174
Executive Summary	p. 177
Web Services Infrastructure
Core Products	p. 180
Web Services Platforms	p. 181
Web Services Management Extensions	p. 206
Infrastructure-Level Web Services	p. 210
Associated Products	p. 214
Evaluation Guidelines
Characterizing Your Project	p. 219
Making the Initial Cut	p. 221
Language and Operating System	p. 221
Selecting a Java Platform	p. 222
Licensing and Support Issues	p. 224
Evaluating Your Requirements	p. 226
Performance and Scalability	p. 226
Standards Support and Interoperability	p. 227
Extensibility Features	p. 229
Security	p. 231
Tools	p. 234
UDDI Registries	p. 236
Platform Considerations	p. 237
Standards Support	p. 239
User Interfaces	p. 240
Administration and Management	p. 241
Security	p. 242
Executive Summary	p. 244
Base Your Selection on Project Requirements	p. 244
Charting Your Course	p. 246
Web Services Product List
.NET Platform	p. 249
COM Platform	p. 250
Portable C and C++ Platforms	p. 251
Java Platforms	p. 252
J2EE Platforms	p. 252
J2SE Platforms	p. 255
J2ME and KVM Platforms	p. 258
Other Languages and Platforms	p. 259
Scripting Languages	p. 259
Programming Languages	p. 261
UDDI Registry Servers	p. 262
Embedded UDDI Registries	p. 263
Standalone UDDI Registries	p. 264
Requirements Questionnaire
Operating Platform Attributes	p. 267
Client Platform Attributes	p. 267
Licensing Requirements	p. 267
Performance and Scalability Requirements	p. 268
Extensibility Features	p. 268
Security Requirements	p. 268
Developer Preferences	p. 269
UDDI Requirements	p. 269
Glossary	p. 271
Index	p. 307
Table of Contents provided by Ingram. All Rights Reserved.

Supplemental Materials

What is included with this book?

The New copy of this book will include any supplemental materials advertised. Please check the title of the book to determine if it should include any access cards, study guides, lab manuals, CDs, etc.

The Used, Rental and eBook copies of this book are not guaranteed to include any supplemental materials. Typically, only the book itself is included. This is true even if the title states it includes any access cards, study guides, lab manuals, CDs, etc.

Excerpts

This book provides an overview of Web services. Its purpose is to help you make more informed decisions about adopting Web services in your company.Unlike most books you'll find on the subject, this guide is written for managers and not for engineers. I've tried to limit the use of computer jargon and acronyms. I don't assume 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 the 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.Information about Web services standards and vendor products is current as of this writing. I will publish periodic status updates on my Web site. Please visit http://www.bowlight.net .If you're planning a Web services project, you should read this book thoroughly. If you want only a basic introduction to Web services, read the first two chapters. If you already feel comfortable with the basics and you want 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 drilling down into specific sections.I've found it impossible to discuss this technology without using some jargon and acronyms. To minimize confusion, I include a number of Executive Summaries of key concepts throughout the book. I also provide a Glossary, which has definitions for all terms that appear inboldfacethroughout the book. Book OutlineChapter 1, The Application Integration Crisis, identifies the motivation behind Web services. In nearly every survey taken during the past 10 years, managers consistently list application integration as one of the top three technology issues facing business. Application integration provides both tactical and strategic value to a business. From a tactical perspective, application integration improves operational efficiency, resulting in reduced costs. From a strategic perspective, application integration enables better access to information, allowing decision makers to make better decisions. Unfortunately, most businesses have a hodgepodge of application systems, developed using different technologies and running on a variety of platforms. It is hard to integrate heterogeneous systems. The issue becomes much more challenging when a business tries to integrate its systems with those of its partners, suppliers, and customers. Web services technology addresses this challenging issue.Chapter 2, Web Services Basics, provides a basic explanation of Web services in business terms. It contains 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 also explore Web services business models using case studies.Chapter 3, Web Services Technologies, is the most technical chapter in the book. I provide an overview of the core technologies that support Web services, including the Web, XML, and 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.