In the Atomic Transaction Flow Option field, select whether the transaction Click Apply.

6-24 Oracle Fusion Middleware Security and Administrators Guide for Web Services For more information about this WLST command, see Web Services Custom WLST Commands in WebLogic Scripting Tool Command Reference. Setting the Size of the Request Message The maximum size of the request message to the Web service can be configured using the procedures provided in the following sections. Using Fusion Middleware Control To set the size of the request message:

1. Navigate to the Web Service Endpoint page, or the Service Home page for SOA

composites, as described in Viewing the Details for a Web Service Endpoint on page 6-7.

2. Click the Configuration tab. For SOA composites, click the Properties tab.

3. Set the Maximum Request Size and the Unit of Maximum Request Size and click

Apply . Figure 6–8 Setting Size of Request Message -1 sets no limit to the size of the message. Or, you can set a maximum limit to the message by entering a number in the text box and selecting the unit of measurement. 4. For ADF and WebCenter applications, restart the Web service application. You do not need to restart a SOA composite. Note: The procedures described in this section apply to Oracle Infrastructure Web services and providers only. Note: If you set the Maximum Request Size to -1, indicating that there is no maximum request size, then the Unit of Maximum Request Size setting is irrelevant and defaults to bytes. Administering Web Services 6-25 Using WLST To set the size of a request message for a Web service endpoint port, use the setWebServiceConfiguration command. Set the maxRequestSize property of the itemProperties argument to the desired value. Enter a long integer to set the maximum value, or -1 to set no limit to the size of the message. The default is -1. The procedure for using this command is described in Using WLST in Configuring the Web Service Endpoint on page 6-12. For example, to specify that there is no message limit size for the WsdlConcretePort, use the following command: wls:wls-domainserverConfig setWebServiceConfiguration wls-domainAdminServerjaxwsejb30ws,jaxwsejb,web,WsdlConcreteService, WsdlConcretePort,[maxRequestSize,-1] For more information about this WLST command, see Web Services Custom WLST Commands in WebLogic Scripting Tool Command Reference. Configuring Asynchronous Web Services When you invoke a Web service synchronously, the invoking client application waits for the response to return before it can continue with its work. In cases where the response returns immediately, this method of invoking the Web service might be adequate. However, because request processing can be delayed, it is often useful for the client application to continue its work and handle the response later on. By calling a Web service asynchronously, the client can continue its processing, without interrupt, and will be notified when the asynchronous response is returned. For information about developing asynchronous Web services, see Developing Asynchronous Web Services in Oracle Fusion Middleware Concepts Guide for Oracle Infrastructure Web Services. The following procedure describes how to configure your deployed asynchronous Web services. You can also configure asynchronous Callback client, as described in Configuring Asynchronous Web Service Callback Clients on page 6-30. To configure asynchronous Web services: 1. Navigate to the Web Services Summary page. 2. In the Web Service Details section of the page, click on the plus + for the Web service to display the Web service endpoints if they are not already displayed.

3. Click the name of the endpoint of the asynchronous Web service to navigate to the

Web Service Endpoint page. Note: You need to wait approximately 30 seconds or the equivalent of the configured Graceful Shutdown Timeout time between stopping and restarting the application. During this time, the server is allowing all global transactions to complete before shutting down the application. If you do not wait the configured Graceful Shutdown Timeout time, then the application will not be restarted appropriately and you will not be able to access it. To avoid waiting the graceful shutdown timeout period, you can restart the application twice. 6-26 Oracle Fusion Middleware Security and Administrators Guide for Web Services For an asynchronous Web service, the Asynchronous flag at the top of the page is set to True. Review the following flags, which provide more information about the asynchronous Web service: ■ Transaction Enabled for Request Queue—Flag that specifies whether transactions are enabled on the request queue. ■ Using Response Queue—Flag that specifies whether a response queue is being used. If set to false, then the response is sent directly to the Web service client, without being stored. ■ Transaction Enabled for Response Queue—Flag that specifies whether transactions are enabled on the response queue. These flags are configured at design time. For more information, see Developing Asynchronous Web Services in Oracle Fusion Middleware Concepts Guide for Oracle Infrastructure Web Services.

4. From the Web Service Endpoint page, click the Configuration tab.

5. Under the Asynchronous Web Service section of the page, you can set the configuration properties defined in Table 6–2 .

6. Click Apply.

7. For ADF and WebCenter applications, restart the Web service application. You do not need to restart a SOA composite. Note: The configuration properties defined in Table 6–2 appear and are valid only for asynchronous Web services. Table 6–2 Configuration Properties for Asynchronous Web Services Configuration Property Description JMS Request Queue Connection Factory Name Name of the connection factory for the JMS request queue. The default JMS connection factory, weblogic.jms.XAConnectionFactory, provided with the base domain is used by default. JMS Request Queue Name Name of the request queue. The following queue is used by default: oracle.j2ee.ws.server.async.DefaultRequestQueue. JMS Response Queue Connection Factory Name Name of the connection factory for the JMS response queue. The default JMS connection factory, weblogic.jms.XAConnectionFactory, provided with the base domain is used by default. JMS Response Queue Name Name of the request queue. The following queue is used by default: oracle.j2ee.ws.server.async.DefaultResponseQueue. JMS System User The user that is authorized to use the JMS queues. By default, this property is set to OracleSystemUser. Note: For most users, the OracleSystemUser is sufficient. However, if you need to change this user to another user in your security realm, you can do so using the instructions provided in Changing the JMS System User for Asynchronous Web Services on page 14-26.