Expand the test option sections by clicking the plus sign + next to the section

12-4 Oracle Fusion Middleware Security and Administrators Guide for Web Services 12. In the HTTP Transport section, the test mechanism uses the WSDL to determine whether a SOAP action is available to test. If available, specify whether you want send the request with the SOAP action HTTP header. For more information, see Enabling HTTP Transport Options on page 12-6.

13. In the Additional Test Options section, select the Enable Stress Test option if you

want to invoke the Web service multiple times simultaneously. If you select this option, you can also provide values for the stress test options, or accept the defaults. For more information, see Stress Testing the Web Service Operation on page 12-7. 14. In the Input Arguments section, enter the input arguments for the Web service in the Value fields. The parameters and type, and the required input values, are determined from the WSDL. Select Tree View or XML View to toggle between a hierarchical list of input parameters and the XML content.

15. Click Test Web Service to initiate the test.

The test results appear in the Response tab upon completion. If the test is successful, the Test Status field indicates Request Successfully received and the response time is displayed, as shown in Figure 12–3 . Figure 12–3 Successful Test Note: This section is not available when testing RESTful Web services. Note: When running SOA composite tests, the Response tab will indicate whether a new composite was generated. You can also click the Launch Flow Trace button to open the Flow Trace window, where you can view the flow of the message through various composite and component instances. Testing Web Services 12-5 If the test fails, an error message is displayed. For example, Figure 12–4 shows an error resulting from a type error in the var-Int parameter. In this particular instance, string data was entered when an int was expected. Figure 12–4 Data Validation Error Editing the Input Arguments as XML Source You can view the input arguments in a user-friendly form, or you can edit the XML source code directly. If you edit the XML source directly, you must enter valid XML. Use the drop-down list in the Input Arguments section of the page to toggle between Tree View and XML View. Enabling Authentication You can use the Test Web Service Page to test policies that use username tokens to authenticate users. The security setting is not determined from a policy in the WSDL; you can specify the type of token you want to test. The default is None. If you do specify a username and password, they must exist and be valid. The password must be passed in plain text. Authentication credentials may be supplied in the request by selecting one of the options in the Security section of the page Figure 12–5 . Select one of the following: ■ WSS Username Token – A WS-Security SOAP header is inserted. Username is required, and password is optional. ■ HTTP Basic Auth – Username and password credentials are inserted in the HTTP transport header. Both the username and password are required. ■ Custom Policy – A custom policy can be used to authenticate the user. You must specify the URI for the policy. The username and password are optional. ■ None – No credentials are included. Note: The results on the Response tab are a simplified version of the standard Web service results. Note: Only policies that expect a username and password are supported by the test function, including custom policies. Policies that require certificates or other tokens are not supported. You cannot use this page to test a Web service with a message protection policy. Note: When testing RESTful Web services, because the SOAP protocol is not used, the only security options are HTTP Basic Authentication or None.