This topic introduces you to using Web services. WebSphere Application Server supports Web services that are developed and implemented based on a variety of Java programming models. Use Web services when operating across a variety of platforms, including the J2EE 1.4 and non-J2EE platforms.
The WebSphere Application
Server V6.1 Feature Pack for Web Services supports the Java API for XML Web
Services (JAX-WS) programming model. JAX-WS is a new programming model that
simplifies application development through support of a standard, annotation-based
model to develop Web services applications and clients.
For a detailed list of the
new specifications and functions released in the Feature Pack for Web Services
product, as well as functionality that is not supported, read about what is
new in the Feature Pack for Web Services.
For a detailed list of the Web services specifications supported by the application server, read about specifications and API documentation.
Implementing Web services applications is an easy way to integrate application systems together within or outside your business infrastructure that function as stand-alone systems. For example, your customer information database is a stand-alone application, but you want your accounting application to access the customer data. You can create a Web service for the customer database and then enable the accounting application as a Web service client. The accounting application can now access the customer information. By implementing a Web service, these two applications can share information in an efficient way.
Because Web services are easily applied to existing applications and information technology assets, you can develop, deploy and recompose new solutions quickly to address new opportunities. As Web services become more popular, the pool of services grows, promoting development of more robust models of just-in-time application and business integration over the Internet.
You can use Web services applications with the application server by following the steps provided: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 the product, 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 Universal Description, Discovery and Integration (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 application server, the procedure call is a Java API for XML-based remote procedure call (JAX-RPC), or, when the Feature Pack for Web Services is installed, the procedure call is a JAX-WS procedure call. Either of these procedure call types retrieves the price list. The WSDL file also specifies the Universal Resource Locator (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.
Using 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.
The
Feature Pack for Web Services provides Samples that demonstrate JAX-WS-based
Web services using many of the new functions and standards supported in this
Feature Pack. The Feature Pack for Web Services Samples are available with
installation of the Feature Pack. The Samples demonstrate the simple message
exchange patterns using both synchronous and asynchronous invocation of Web
services in SOAP 1.1 and SOAP 1.2 environments. The Samples are composed with
Web service standards such as WS-Addressing (WS-A) , WS-Reliable Messaging
(WS-RM), and WS-Secure Conversation (WS-SC), and enable you to perform a broad
range of interoperability tests. The samples demonstrate the use of JavaBeans
artifacts and static service endpoints and proxy-based clients. Additionally,
a Sample is provided that demonstrates Message Transmission Optimization Mechanism
(MTOM). To learn more about these Samples, see the Samples readme located
in the app_server_root/samples/lib/WebServicesSamples directory.
Read about installing the Samples using the administration console to learn
how to install these Samples onto an application server that has been augmented
with a Web services profile.
In this information ...Subtopics
Related concepts
Related tasks
Related reference
| IBM Redbooks, demos, education, and more |