In the Service Home page, click the Properties tab. In the Atomic Transaction Version field, select the version of the Web service

Administering Web Services 6-23 Specify values for the itemProperties argument as described in the following table. For example, to configure atomic transactions for the TaskService_pt Web service endpoint of the defaultSimpleApproval[1.0] SOA composite application, use the following command: wls:soa-infraserverConfigsetWebServiceConfiguration soa-infra,defaultSimpleApproval[1.0],soa,client, TaskService_pt,[wsat.flowOption,MANDATORY,wsat.version, DEFAULT] To verify the settings, use the listNone,None,true command: wls:soainfraserverConfiglistWebServicesNone,None,true soainfrasoa_server1soa-infra: compositeName=defaultSimpleApproval[1.0], moduleType=soa, serviceName=client enableTestPage: true enableWSDL: true TaskService_pt http:myhost:8001soa-infraservicesdefaultSimpleApproval1.0client enable: true enableREST: false enableSOAP: true maxRequestSize: -1 loggingLevel: NULL wsat.flowOption: MANDATORY wsat.version: DEFAULT No policies attached; endpoint is not secure. Note: To configure Web service atomic transactions for SOA references, you use the setWebServiceClientStubProperty command. For additional information, see Configuring the Web Service Client on page 6-27. Table 6–1 SOA Web Service Atomic Transaction WLST Configuration Properties Property Description Valid Values wsat.flowOption Atomic transaction flow option ■ NEVER – Do not export transaction coordination context. This is the default. ■ SUPPORTS – Export transaction coordination context if transaction is available. ■ MANDATORY – Export coordination context. An exception is thrown if there is no active transaction. wsat.version Atomic transaction version ■ WSAT10 ■ WSAT11 ■ WSAT12 ■ DEFAULT—If you specify DEFAULT, all three versions are accepted. Note: The listWebServices command output does not include details on SOA components, including policy attachments. 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.