• WAS v8.5 > End-to-end paths > Web services

    Tasks: Implement web services applications

    Use web services applications to integrate application systems within or outside the business infrastructure functioning as a stand-alone systems. For example, our customer information database is a stand-alone application, but we want our accounting application to access the customer data. We can create a web service for the customer database and then enable the accounting application as a web service client.

    Steps...

    1. Plan to use web services.

    2. Migrate existing web services.

      IBM WAS supports the JAX-WS and JAX-RPC. JAX-WS extends JAX-RPC. Annotations, SOAP 1.2, and SOAP MTOM support are only available within JAX-WS 2.x and JAXB 2.x. Best practice is to migrate a JAX-RPC based web services to JAX-WS and JAXB. For web services based on Apache SOAP, migrate v4.0 and v5.0 (before v5.0.2) client applications.

    3. Develop JAX-WS...

      1. Develop from existing WSDL files
      2. Develop
      3. Develop clients
      4. Use WS-Addressing SPI
      5. Enable through service integration technologies
      6. Create stateful web services using the Web Services Resource Framework.
      7. Use WS-Transaction policy to coordinate transactions or business activities for web services.
      8. Use WS-Policy to exchange policies in a standard format.

    4. Develop JAX-RPC...

      1. Develop from existing WSDL files
      2. Develop
      3. Develop clients

    5. Assemble...

      1. Assemble web services.
      2. Deploy Web services.
      3. Administer deployed web services.

    6. Secure...

      1. Manage policy sets .
      2. Review standards and programming models for web services message-level security.

    7. Administer...

      1. Publish the WSDL file.
      2. Monitor the performance of web services applications.
      3. 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 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 about 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 email, 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 JAX-RPC or 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 using web services to communicate with suppliers for the best prices and complete the ordering processes. The merchandise price lists need publishing to the website 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 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 the information for the 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 section of the Information Center for additional Samples that demonstrate JAX-WS and JAX-RPC web services.


    Related concepts:

  • Service-oriented architecture
  • Web services
  • Web Services for Java EE specification
  • JAX-RPC
  • WSDL
  • JAX-WS
  • JAXB
  • SOAP
  • SOAP with Attachments API for Java interface
  • Message Transmission Optimization Mechanism
  • Overview: Online garden retailer web services scenarios
  • WS-I Basic Profile
  • RMI-IIOP using JAX-RPC
  • WS-I Attachments Profile
  • Overview of standards and programming models for web services message-level security
  • Web services approach to a service-oriented architecture
  • Web services business models supported in SOA


    Related

  • Planning to use web services
  • Migrating Apache SOAP web services to JAX-RPC web services based on Java EE standards
  • Implement web services applications with JAX-WS
  • Implement web services applications from existing WSDL files with JAX-WS
  • Implement static JAX-WS web services clients
  • Use JAXB for XML data binding
  • Use handlers in JAX-WS web services
  • Run an unmanaged web services JAX-WS client
  • Implement web services applications with JAX-RPC
  • Implement web services applications from existing WSDL files with JAX-RPC
  • Implement JAX-RPC web services clients
  • Run an unmanaged web services JAX-RPC client
  • Use HTTP to transport web services
  • Use SOAP over JMS to transport web services
  • Develop applications that use Web Services Addressing
  • Create stateful web services using the Web Services Resource Framework
  • 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 application servers
  • Administer deployed web services applications
  • Make 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
  • Monitoring the performance of web services applications
  • Tune Web Services Security for v8.5 applications
  • Configure the Kerberos token for Web Services Security
  • Troubleshooting web services
  • Example: Installing a web services sample with the console
  • Enable web services through the service integration bus
  • Use WS-Notification for publish and subscribe messaging for web services


    Reference:

  • Web services migration scenarios: JAX-RPC to JAX-WS and JAXB
  • Web services migration best practices
  • IBM proprietary SOAP over JMS protocol (deprecated)
  • API documentation
  • WAS roles and goals


    Related information:

    Web services hints and tips: JAX-RPC vs JAX-WS

    Web services hints and tips: JAX-RPC vs JAX-WS Part 2


    +

    Search Tips   |   Advanced Search