Configuring the Host WebLogic Server Instance for the Asynchronous Web Service

Invoking a Web Service Using Asynchronous Request-Response 2-3 When you invoke the StockQuoteClientService Web service, which in turn invokes the StockQuoteService Web service, the second invoke will be asynchronous rather than synchronous.

2.3 Configuring the Host WebLogic Server Instance for the Asynchronous Web Service

Configuring the WebLogic Server instance on which the asynchronous Web service is deployed involves configuring JMS resources, such as JMS servers and modules, that are used internally by the Web services runtime. You can configure these resources manually or you can use the Configuration Wizard to extend the WebLogic Server domain using a Web services-specific extension template. Using the Configuration Wizard greatly simplifies the required configuration steps; for details, see Configuring Your Domain For Web Services Features in Getting Started With JAX-RPC Web Services for Oracle WebLogic Server. If you prefer to configure the resources manually, perform the following steps. 3 Update your build.xml file to compile the JWS file that implements the StockQuoteClientServic e . You will add a clientgen child element to the jwsc Ant task so as to automatically generate the asynchronous flavor of the Web service operations you are invoking. See Section 2.5, Updating the build.xml File When Using Asynchronous Request-Response . 4 Run the Ant target to build the StockQuoteClientServic e . For example: prompt ant build-clientService 5 Deploy the StockQuoteClientServic e Web service as usual. See Deploying and Undeploying WebLogic Web Services in Getting Started With JAX-RPC Web Services for Oracle WebLogic Server. Notes: Alternatively, you can use WLST to configure the resources. For information about using WLST to extend the domain, see Configuring Existing Domains in Oracle WebLogic Scripting Tool. A domain that does not contain Web Services resources will still boot and operate correctly for non-Web services scenarios, and any Web Services scenario that does not involve asynchronous request and response. You will, however, see INFO messages in the server log indicating that asynchronous resources have not been configured and that the asynchronous response service for Web services has not been completely deployed. Table 2–1 Cont. Steps to Use Asynchronous Request-Response Step Description 2-4 Programming Advanced Features of JAX-RPC Web Services for Oracle WebLogic Server

2.4 Writing the Asynchronous JWS File