This topic provides relevant supplemental information about Web services-related topics. The following topics provide extended reference information about Web services:
This topic includes information about developing Web services that based on the J2EE and Java API for XML-based remote procedure call (JAX-RPC) specifications.
This topic provides information about key Web sites that discuss performance best practices.
This topic is an overview about UDDI and information about the UDDI Java API.
This topic includes a look into the Apache Software Foundation and its maintenance of WSIF.
This topic provides information about the WS-Notification standards that enable "publish and subscribe" messaging for Web services.
This topic is an overview about the WS-I Basic Profile.
This topic is an overview about SOAP, information about the SOAP syntax and processing rules.
This topic provides a roadmap to security, the WS-Security specification, best practices, a profile of the OASIS Security Assertion Markup Language (SAML) and more.
This topic is the Samples Gallery for WebSphere Application Server and Samples Central for UDDI and WSIF.
The information resides on IBM and non-IBM Internet sites, whose sponsors control the technical accuracy of the information.
These links are provided for convenience. Often, the information is not specific to an IBM WebSphere Application Server product, but is useful all or in part for understanding the product. When possible, links are provided to technical papers and Redbooks that supplement the broad coverage of the release documentation with in-depth examinations of particular product areas.
This publication describes the new concept of Web services from various perspectives. It presents the major building blocks on which Web services rely. Well-defined standards and new concepts are presented and discussed.
This article focuses on the benefits and challenges of building Web services applications. Web services might be an evolutionary step in designing distributed applications, however, the technology is not without problems. Outlined are the difficulties developers face in creating a truly workable distributed system of Web services. This article also outlines author Graham Glass's plan for building peer-to-peer Web applications.
This document describes the SOAP with Attachments API for Java (SAAJ) and how this API provides a standard way to send XML documents over the Internet from the Java platform.
This document describes the J2EE specification.
This document reviews the JAX-RPC specification which enables Java technology developers to develop SOAP-based interoperable and portable Web services.
This article is a detailed overview of Web Services Description Language (WSDL), which includes programming specifications.
This article is a detailed overview of the UDDI registry.
This article is about using WSDL with UDDI. Although it is based on the UDDI Registry in WebSphere Application Server V5, it remains a useful description of the recommended approach for use of WSDL with UDDI.
This article is an introduction to the new features in UDDI V3.
This article is a detailed overview of SOAP, which includes the programming specifications.
This document specifies the syntax and processing rules of a SOAP header entry to carry digital signature information within a SOAP 1.1 Envelope
This document describes a proposed model for addressing security within a Web service environment. It defines a comprehensive Web services security model that supports, integrates, and unifies several popular security models, mechanisms, and technologies, including both symmetric and public key technologies. You can enable a variety of systems to securely interoperate in a platform and language-neutral manner. It also describes a set of specifications and scenarios that show how these specifications can be used together.
The Web Services Security (WS-Security) specifications describe enhancements to SOAP messaging to provide the quality of protection through message integrity, message confidentiality, and single message authentication. Use these mechanisms to accommodate a wide variety of security models and encryption technologies. The WS-Security specification also provides a general-purpose mechanism for associating security tokens with messages. Additionally, the specification describes how to encode binary security tokens. Specifically, the specification describes how to encode X.509 certificates and Kerberos tickets, as well as how to include opaque encrypted keys. It also includes extensibility mechanisms that can be used to further describe the characteristics of the credentials that are included with a message.
This document specifies the syntax and processing rules of a SOAP header entry to carry digital signature information within a SOAP 1.1 envelope
This document describes clarifications, enhancements, best practices, and errata of the WS-Security specification.
This document proposes a set of standards for SOAP extensions that are used to increase message confidentiality.
This document describes the support for multiple token formats, trust domains, signature formats, and encyrption technologies.
This document provides a short description of the Certification Path API.
This document specifies XML digital signature processing rules and syntax. XML signatures provide integrity, message authentication, or signer authentication services for data of any type, whether it is located within the XML that includes the signature or elsewhere.
This specification describes a method for generating a physical representation or the canonical form of an XML document that accounts for the permissible changes.
Canonical XML [XML-C14N] specifies a standard serialization of XML that, when applied to a subdocument, includes the subdocument ancestor context including all of the namespace declarations and attributes in the "xml:"namespace.
This document specifies a process for encrypting data and representing the result in XML.
This document specifies an XML Signature decryption transform that enables XML Signature applications to distinguish between those XML encryption structures that are encrypted before signing, and must not be decrypted, and those that are encrypted after signing, and must be decrypted, for the signature to validate.