Build secure Web services with transport-level security using IBM®
Rational® Application Developer V7 and IBM WebSphere® Application
Server V6.1. Follow this three-part series for step-by-step instructions about
how to develop Web services and clients, configure HTTP basic authentication,
and configure HTTP over SSL (HTTPS). This first part of the series walks you
through building a Web service for a simple calculator application. You
generate and test two different types of Web services clients: a Java™
Platform, Enterprise Edition (Java EE) client and a stand-alone Java client.
You also handle user-defined exceptions in Web services.
The current emphasis on Service-Oriented Architectures (SOA) has put the
spotlight on Web services, but it's easy to get lost in all the information
being bandied about. This first in a series of tutorials on the major Web
services specifications describes the basic concepts of Web services and SOAP.
You'll learn how to build a SOAP server and client.
Using Java API for XML Web Services (JAX-WS) technology to design and develop
Web services yields many benefits, including simplifying the construction of
Web services and Web service clients in Java, easing the development and
deployment of Web services, and speeding up Web services development. This
tutorial walks you through how to do all of this and more by developing a
sample order-processing application that exposes its functionality as Web
services. After going through this tutorial, you'll be able to apply these
concepts and your newly acquired knowledge to develop Web services for your
application using JAX-WS technology.
Part 1 and Part 2 of this three-part tutorial series showed you how to
develop Web services and clients, and configure HTTP basic authentication. In
this final installment, you create a self-signed certificate, key store, trust
store, and Secure Sockets Layer (SSL) configuration using the IBM WebSphere
Administrative Console. Then you configure HTTPS for your Web services and Web
services client, and test HTTPS Web services from both a Java Platform,
Enterprise Edition (Java EE) client and a stand-alone Java client.
Service-Oriented Architecture (SOA) is the next step in software development,
leveraging XML technologies and Web services that went before. This best
practices tutorial teaches you how to use SOA techniques in system design
effectively. Use this tutorial, along with the other educational resources
listed below, to help prepare for IBM Certified SOA Solution Designer
certification.
Part 1 of this tutorial series gave you step-by-step instructions for
building a Web service for a simple calculator application. You generated Web
services and tested two different types of Web services clients—a Java
Platform, Enterprise Edition (Java EE) client and a stand-alone Java
client—and handled user-defined exceptions in Web services. This
second installment in the three-part series shows you how to configure HTTP
basic authentication for your Web services and Web services client, and
monitor the HTTP basic authentication information using the TCP/IP
monitor.
This tutorial, Part 4 of the Understanding Web services specifications series, explains the concepts behind WS-Security and related standards
such as XML Signature, which combine to make security in the Web services
world not just possible, but practical.
Build secure Web services using transport-level security (HTTPS) with IBM
Rational Application Developer Version 6.0.1.1 and later. In Part 1 of this
series, you will build Web services for a calculator application. You will
generate and test two different types of Web services clients: a J2EE client
and a J2SE client.
In Part 2 of this series, we configure HTTPS for a Web services application.
We create a self-signed certificate using iKeyman and configure SSL settings
using IBM WebSphere Admin Console. Finally, we test HTTPS Web services from
both a Java 2 Enterprise Edition (J2EE) and Java 2 Platform, Standard Edition
(J2SE) client.
This tutorial, Part 5 of the Understanding Web services specifications series, explains the concepts behind WS-Policy and related standards,
such as WS-SecurityPolicy, which provide a means to specify possible
configurations of a Web service, and also to enforce defined security and
authentication.
A Web Services Description Language (WSDL) binding style can be RPC or
document. The use can be encoded or literal. How do you determine which
combination of style and use to use? The author describes the WSDL and SOAP
messages for each combination to help you decide.
This article discusses the highlights of service-oriented modeling and
architecture; the key activities that you need for the analysis and design
required to build a Service-Oriented Architecture (SOA). The author stresses
the importance of addressing the techniques required for the identification,
specification and realization of services, their flows and composition, as
well as the enterprise-scale components needed to realize and ensure the
quality of services required of a SOA.
Web Services Description Language (WSDL) is a new specification to describe
networked XML-based services. It provides a simple way for service providers
to describe the basic format of requests to their systems regardless of the
underlying protocol (such as SOAP or XML) or encoding (such as Multipurpose
Internet Messaging Extensions). WSDL is a key part of the effort of the
Universal Description, Discovery and Integration (UDDI) initiative to provide
directories and descriptions of such on-line services for electronic business.
This article provides a brief background and technical introduction to WSDL.
Knowledge of XML and XML Namespaces is required and some familiarity with XML
Schemas and SOAP is useful.
In this article, IBM developer Bertrand Portier describes the different types
of Java Web services clients and explains how to write portable, vendor
independent code. There are two families of Web services clients in the Java
world: unmanaged and J2EE container-managed clients. The article starts by
briefly describing the Web services invocation process and the Web services
standards for Java environments. The two families of Java Web services clients
are then described, including their similarities and differences for the two
steps they need to perform: service lookup and access.
In the Deploying Web services with WSDL series, Bilal will explore all major
technical aspects of creating, deploying, and publishing Web
services—from Web Services Markup Language (WSDL), to SOAP, and
Universal Description Discovery and Integration (UDDI) registries. Part 1
focuses on WSDL authoring: You will learn how to manually create a WSDL
interface, and then compare your effort with the output of a WSDL authoring
tool.
A structured approach or analysis and design method is required to craft SOAs
of quality. As none of the existing approaches met the authors requirements on
recent SOA projects, they suggest combining elements from well-established
practices such as OOAD, EA, and BPM, complementing them with innovative
elements upon demand.
The Apache Axis2 Web services framework was designed from the start to
support multiple XML data-binding approaches. The current release provides
full support for XMLBeans and JiBX data binding, as well as the custom Axis
Data Binding (ADB) approach developed specifically for Axis2. This article
shows you how to use these different data bindings with Axis2 and explains why
you might prefer one over the others for your application.
Get an introduction to the new architecture of Axis2, and learn how to deploy and consume Web services using Axis2. This is the first installment of a two-part series about developing Web services using the Axis2 runtime. Axis2 is the next generation of Apache Axis SOAP runtime.
Java developers who are interested in getting started with Web services
should check out the Java Web Services Developers Pack (WSDP). In this
article, James McCarthy takes you on a quick tour of this package. You'll
learn what the tools in this package can do for you, and find out which
components are just for testing and which are ready for production use
as-is.
