Task overview: Implement Web services applications
IBM WAS supports the JAX-WS and JAX-RPC model. JAX-WS extends JAX-RPC model and supports annotations.
For Web services based on Apache SOAP, to implement Web Services for Java EE specification, migrate client applications.
- Develop Web services from existing WSDL files using JAX-WS.
- Develop Web services applications using JAX-WS.
- Develop and deploy JAX-WS Web services clients
- Develop Web services applications from existing WSDL files with JAX-RPC.
- Develop Web services applications with JAX-RPC.
- Develop and deploy JAX-RPC Web services clients
- Enable Web services through service integration technologies
- Use the WS-Addressing
- Create stateful Web services using the WSRF.
- Use WS-Transaction policy to coordinate transactions or business activities for Web services.
- Use WS-Policy to exchange policies in a standard format.
- Assemble Web services.
- Deploy Web services.
- Administer deployed Web services.
- Secure Web services.
- Manage policy sets using the admin console.
- Secure Web services applications using message level security.
- Publish the WSDL file.
- Monitor the performance of Web services applications.
- Troubleshoot Web services.
Example
The following example illustrates how a business might use Web services.
The owner of a flower shop wants to start receiving orders from customers through the Web. This owner starts the process by finding wholesale flower suppliers, pricing WAS ND, and completing contracts for future flower orders.
Using Web services, the flower shop owner can find wholesale flower suppliers. One way to find new suppliers is to use a UDDI registry to search for potential suppliers. When the suppliers are chosen, the registry sends back information on how to contact the flower distributors that meet the criteria of the flower shop owner.
The flower shop owner can request price lists from each of the suppliers by obtaining a WSDL file for each potential supplier. The WSDL can be downloaded from the Web page of the supplier, received through e-mail, or retrieved from the UDDI registry entry of the supplier.
The WSDL describes the procedure call. When using the appserver, the procedure call is a JAX-RPC or a JAX-WS procedure call. Either of these procedure call types retrieves the price list. The WSDL file also specifies the URL, where the request is sent.
The flower shop owner now has to compare the prices received from each supplier, decide which suppliers to do business with, and make arrangements for future orders to fill. The flower shop can now sell merchandise through the Web by using Web services to communicate with suppliers for the best prices and complete the ordering processes. The merchandise price lists need publishing to the Web site and a mechanism is needed for customers to order flowers.
The Web services clients of the flower supplier are deployed on the flower shop server. When a customer makes a transaction to purchase flowers through the Web, the order is sent to the supplier through the procedure call. The supplier responds by sending a confirmation with the order number and shipping date. The suppliers maintain the inventory and the flower shop owner handles billing and customer order management.
Similarly, the flower shop catalog can be composed automatically from the catalogs of each supplier. If the supplier delivers directly to the customer, then the order tracking inquiries can pass directly to the order tracking system of the supplier. The supplier can also use Web services to send invoices for orders by the flower shop. Processes that previously required forms to fill manually, and fax or mail, can now be done automatically, saving labor costs for both the flower shop and the supplier.
Use Web services is beneficial because a much larger inventory is made available to the flower shop. No merchandise maintenance overhead exists, and the flower shop can offer their customers products that they otherwise might not have. Selling flowers through the Web increases capital for the flower shop without overhead of another store or resources invested into additional products.
For a more detailed scenario, see Web services scenario: Overview which tells the story of a fictional online garden supply retailer, Plants by WebSphere, and how they incorporated the Web services concept.
Refer to the Samples Gallery for additional Samples that demonstrate JAX-WS and JAX-RPC Web services.
Service-oriented architecture
Web services
Plan to use Web services
Web services migration scenarios: JAX-RPC to JAX-WS and JAXB
Web services migration best practices
Use JAXB for XML data binding
Use handlers in JAX-WS Web services
Running an unmanaged Web services JAX-WS client
Running an unmanaged Web services JAX-RPC client
Use HTTP to transport Web services
Use SOAP over Java Message Service to transport Web services
Add assured delivery to Web services through WS-ReliableMessaging
Use WS-Transaction policy to coordinate transactions or business activities for Web services
Use WS-Policy to exchange policies in a standard format
Assemble Web services applications
Deploy Web services applications onto appservers
Administer deployed Web services applications
Making deployed Web services applications available to clients
Create a monitor for WAS for WSDM resources (deprecated)
Secure Web services applications at the transport level
Authenticate Web services clients using HTTP basic authentication
Manage policy sets
Testing Web services-enabled clients
Monitor the performance of Web services applications
Tuning WS-Security for V7.0 applications
Secure Web services applications using message level security
Troubleshooting Web services
WAS roles and goals
Related concepts
Web Services for Java EE specification
JAX-RPC
WSDL
JAX-WS
JAXB
SOAP
SOAP with Attachments API for Java interface
Message Transmission Optimization Mechanism
Web Services-Interoperability Basic Profile
RMI-IIOP using JAX-RPC
WS-I Attachments Profile
Overview: Online garden retailer Web services scenarios
Web services approach to a service-oriented architecture
Web services business models supported
Related tasks
Set the Kerberos token for WS-Security
Example: Installing a Web Services Sample with the console
Enable Web services through service integration technologies
Use WS-Notification for publish and subscribe messaging for Web services
Related
IBM proprietary SOAP over JMS protocol (deprecated)
Specifications and API documentation
Related information
Web services hints and tips: JAX-RPC vs JAX-WS
Web services hints and tips: JAX-RPC vs JAX-WS Part 2