Configuring Your Servers for Asynchronous Web Service Invocation

3-6 Programming Advanced Features of JAX-WS Web Services for Oracle WebLogic Server

3.3 Configuring Your Servers for Asynchronous Web Service Invocation

To support asynchronous Web service invocation, you need to configure the features defined in the following table on the servers to which the Web service and client are deployed. 6 Deploy the Web service client. See Deploying and Undeploying WebLogic Web Services in Getting Started With JAX-WS Web Services for Oracle WebLogic Server. 7 Monitor the Web service client. You can monitor runtime information for clients that invoke Web services asynchronously, such as number of invocations, errors, faults, and so on, using the Administration Console or WLST. See Section 3.9, Monitoring Asynchronous Web Service Invocation . Note: This step is not required if you are programming the Web service client using the standard JAX-WS RI implementation and synchronous transport, as described in Section 3.7, Using the JAX-WS Reference Implementation . Table 3–4 Configuration for Asynchronous Web Service Invocation Feature Description Persistence Web service persistence is used to save the following types of information: ■ Client identity and properties ■ SOAP message, including its headers and body ■ Context properties required for processing the message at the Web service or client for both asynchronous and synchronous messages The MakeConnection transport protocol makes use of Web service persistence as follows: ■ Web service persistence configured on the MC Receiver Web service persists response messages that are awaiting incoming MakeConnection messages for the MakeConnection anonymous URI to which they are destined. Messages are persisted until either they are returned as a response to an incoming MakeConnection message or the message reaches the maximum lifetime for a persistent store object, resulting in the message being cleaned from the store. ■ Web service persistence configured on the MC Initiator Web service client is used with the asynchronous client handler feature to recover after a VM restart. You can configure Web service persistence using the Configuration Wizard to extend the WebLogic Server domain using a Web services-specific extension template. Alternatively, you can configure the resources required for these advanced features using the Oracle WebLogic Administration Console or WLST. For information about configuring Web service persistence, see Section 6.3.3, Configuring Web Service Persistence for Web Service Clients . For information about the APIs available for persisting client and message information, see Section 3.8, Propagating Request Context to the Response . Table 3–3 Cont. Steps to Invoke Web Services Asynchronously Step Description Invoking Web Services Asynchronously 3-7

3.4 Building the Client Artifacts for Asynchronous Web Service Invocation