Configuring the Source WebLogic Server Instance

3-8 Programming Advanced Features of JAX-RPC Web Services for Oracle WebLogic Server

3.4 Configuring the Source WebLogic Server Instance

Configuring the WebLogic Server instance on which the client Web service is deployed involves configuring JMS and store and forward SAF resources. 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. 5 Create a store and forward SAF agent. You can use an existing one if you do not want to create a new one. When you create the SAF agent: ■ Set the Agent Type field to Both to enable both sending and receiving agents. ■ Be sure to target the SAF agent by clicking Next on the first assistant page to view the Select targets page rather than clicking Finish. Clustering Considerations: ■ If you are using reliable messaging within a cluster, you must target the SAF agent to the cluster. See Create Store-and-Forward agents in Oracle WebLogic Server Administration Console Help. 6 Tune your domain environment, as required. Optional Review Tuning Heavily Loaded Systems to Improve Web service Performance in Performance and Tuning for Oracle WebLogic Server. 7 Restart the server. In order for the configuration changes to take effect, you must restart the server, as described in Starting and Stopping Servers in Managing Server Startup and Shutdown 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 3–3 Cont. Steps to Configure the Destination WebLogic Server Instance Manually Step Description Using Web Services Reliable Messaging 3-9

3.5 Creating the Web Service Reliable Messaging WS-Policy File