Developing web service applications
You can develop and publish web service applications, which are modular applications that
implement a services oriented architecture (SOA). These topics explain how to create and deploy web
services, how to implement web service security, and how to test and validate web
services.
Learn about web service applications
Web services are self-contained, modular applications that can be described, published, located, and invoked over a network. They implement a services oriented architecture (SOA), which supports the connecting or sharing of resources and data in a very flexible and standardized manner. Services are described and organized to support their dynamic, automated discovery and reuse.
SOAP
SOAP (formerly known as Simple Object Access Protocol) is a lightweight protocol for the exchange of information in a decentralized, distributed environment. A SOAP message is a transmission of information from a sender to a receiver. SOAP messages can be combined to perform request/response patterns.
Java API for XML based web services
Java API for XML-based web services (JAX-WS), which is also known as JSR-224, is the next generation web services programming model that extends the foundation provided by the Java API for XML-based RPC (JAX-RPC) programming model. Using JAX-WS, developing web services and clients is simplified with greater platform independence for Java applications by the use of dynamic proxies and Java annotations. The web services tools included in this product support JAX-WS 2.0, 2.1, and 2.2.
JAXB
Java Architecture for XML Binding (JAXB), which is also known as JSR-222, is a Java technology that provides an easy and convenient way to map Java classes and XML schema for simplified development of web services. JAXB leverages the flexibility of platform-neutral XML data in Java applications to bind XML schema to Java applications without requiring extensive knowledge of XML programming. The tools included in this workbench implement JAXB 2.0, 2.1, and 2.2 standards.
Known problems and limitations for web service applications
Various known problems and limitations apply when you are working with web service applications and WebSphere Developer Tools. Issues include, among others, problems when you use a secured WebSphere Application Server and when you use the web services wizards.
Developing JAX-RS applications
You can develop Java API for RESTful web services (JAX-RS) applications so that you can create Representational State Transfer (REST) services quickly.
Tools for web services development
Configuring a workspace for web services development
Although you can begin web services development immediately upon creating a workspace, you might find it convenient to configure your workspace to optimize your development experience.
Developing web services and clients
You can create web services and clients by using the web services wizards, annotations, Ant tasks, or command-line tools.
Web services: Editing, assembling, and securing tasks
After you create a web service or client, you can do various assembly tasks, such as editing the web service deployment descriptors, adding handlers, and enabling security.
Creating and editing JAX-WS web service handlers
You can add JAX-WS logical or protocol handlers to intercept inbound and outbound messages to or from web services and their clients. You can select from any currently available JAX-WS web services and clients and start the Handler Creation Wizard. In the wizard, you provide the class name of the handler, the handler name, and an optional display name, and specify the type of handler. When finished, the wizard generates the skeleton handler code and updates the applicable deployment descriptor.
Merged skeleton files for web services updates
After you create a web service, you might want to change it. Although you cannot automatically propagate all your changes to all the required files, to retain your changes while you update the web service, you can merge a generated skeleton file. You can then regenerate your web service, and your changes remain intact.
Securing web services
Web services security for WebSphere Application Server is based on the OASIS web services security (WSS) Version 1.0 specification, the Username token Version 1.0 profile, and the X.509 token Version 1.0 profile. These standards and profiles address how to provide protection for messages that are exchanged in a web service environment.
Deploying web services
Deploying a web service involves creating the code that makes your web service available to others. You can deploy a project, an EAR file, or an application client. If you created a web service by using the web services wizards, the deployment code is generated automatically.
Testing and validating web services
After you create a web service or client, you can test it using sample JSPs, the web services Explorer, or the Generic Service Client. You can also test the SOAP traffic that is passed by the service.