Develop a WSIF service

A Web Services Invocation Framework (WSIF) service is a Web service that uses WSIF.

To develop a WSIF service, develop the Web service (or use an existing Web service), then develop the WSIF client based on the WSDL document for that Web service.

There are also two pre-built WSIF Samples available for download from the Samples Central page of the DeveloperWorks WebSphere Web site...

For more information on using the pre-built Samples, see the documentation that is included in the download package.

To develop a WSIF service, complete the following steps...

  1. Develop the Web service.

    Use Web services tools to discover, create, and publish the Web service. You can develop Java bean, enterprise bean, and URL Web services. Use Web service tools to create skeleton Java code and a sample application from a WSDL document. For example, an enterprise bean can be offered as a Web service, using Remote Method Invocation over Internet Inter-Orb Protocol (RMI-IIOP) as the access protocol. Or you can use a Java class as a Web service, with native Java invocations as the access protocol.

    Use the WebSphere Studio Application Developer to create a Web service from a Java application, as described in its StockQuote service tutorial. The Java application that you use in this scenario returns the last trading price from the Internet Web site, given a stock symbol. Using the Web service wizard, you generate a binding WSDL document named StockQuoteService-binding.wsdl and a service WSDL document named StockQuoteService-service.wsdl from the bean. You then deploy the Web service to a Web server, generate a client proxy to the Web service, and generate a sample application that accesses the StockQuoteService through the client proxy. You test the StockQuote Web service, publish it using the IBM UDDI Explorer, and then discover the StockQuote Web service in the IBM UDDI Test Registry.

  2. Develop the WSIF client.The information you need to develop a WSIF client is provided in the following topics...

    The Address Book Sample is written for synchronous interaction. If you are using a JMS provider, your WSIF client might need to act asynchronously. WSIF provides two main features that meet this requirement...

    • A correlation service that assigns identifiers to messages so that the request can match up with the (eventual) response.

    • A response handler that picks up the response from the Web service at a later time.

    For more information, see the WSIF API topic WSIFOperation - Asynchronous interactions reference.


See Also

Using complex types
Using WSIF to invoke Web services
Using the WSIF providers
Using the JNDI
Interacting with the J2EE container in WAS
Running WSIF as a client