1. Invoke the Administration Console in your browser using the following URL:

   http://[host]:[port]/console
   

   where:

   • host refers to the computer on which WebLogic Server is running.

   • port refers to the port number on which WebLogic Server is listening (default value is 7001).

2. Select the web service in the Deployments table that you would like to test. For more information, see "How Web Services Are Displayed in the Administration Console" in Understanding WebLogic Web Services for Oracle WebLogic Server.
3. Select the Testing tab and click the Test Point link next to the web service endpoint that you want to test.
4. When prompted, enter the login credentials for the Web Services Test Client.
5. Follow the procedure described in "Test a Web Service" in Oracle WebLogic Server Administration Console Online Help.

1. Click in the upper-right corner of the Web Services Test Client.
2. Click General in the navigation pane.
3. Enter the proxy host in the Http Proxy Host field.
4. Enter the proxy port in the Http Proxy Port field.
5. Click Submit.

<domain-directory>/tmp/WSTestPageWorkDir

1. Click in the upper-right corner of the Web Services Test Client.
2. Click General in the navigation pane.
3. Edit the Current Working Home field to reflect the desired working home directory.
4. Click Submit.

1. Click in the upper-right corner of the Web Services Test Client.
2. Click Choose File.
3. Navigate to the test case file, and click Open.

   Click Import.

Access the Test Web Service page to test RESTful web services.

1. Access the Test Web Service page using one of the methods described in Section 5.3.1, "Accessing a Web Service for Testing."
2. Click Parse WSDL or WADL.

   If the WADL is secured with HTTP Basic Authentication, click HTTP Basic Auth Option for WSDL or WADL Access and enter the username and password before parsing the WADL.

   Figure 5-8 Test Web Service Page for a WADL

   
   

   
   Description of "Figure 5-8 Test Web Service Page for a WADL"

   
   
3. Select the resource and method type to be tested. The Method field displays the corresponding HTTP method for the selected resource path in the Resource field

   If the WADL has multiple resources methods, these fields are available as drop-down menus, as shown in Figure;5–8. If the WADL has only one resource and method, these fields are read-only.

   Note:

   Only the GET and POST methods are supported in this release. (Other methods are ignored if they are present in the WADL.)

4. Select the MIME media type that you want to use for the test request from the Representation Media Type for Request menu. The available types, if one exists, are determined from the WADL.
5. Select the MIME media type that you want to use for the test response from the Representation Media Type for Response menu. The available types, if one exists, are determined from the WADL. The following media types are supported in this release:

   • application/xml

   • application/json

   • text/plain

   • text/xml

   • application/x-www-form-urlencoded

6. Select the Request tab if it is not already selected.
7. In the Security section, the options are OWSM Security Policies, HTTP Basic Authentication, and None. The default is None. For more information, see "Testing Security" on page;5‐31.
8. In the HTTP Header section you can add, modify, or delete HTTP headers to pass request information to a RESTful web service. For more information, see "Testing HTTP Headers" on page;5‐37.
9. In the Input Arguments section, enter the input arguments for the RESTful web service in the Value fields. The parameters and type and the required input values, are determined from the WADL. The Style column enables you to visualize REST services with input parameters of the following, different styles:

   • Template: Parameters that parameterize the path to a REST request. (RESOURCE level only).

   • Matrix: Parameters that define parameters to be added to the actual path of the resource, but preceding the query string.

   • Query: Parameters that are appended to the path of the URL when submitting a request (most common parameter type). For example, you typically see them added to the path after the ‘?' in a GET HTTP request or as a Key value pair in the request body of the POST and PUT request as part of HTML form submit.

   • Header: Parameters that are added to the out-going headers of a HTTP request.

   Style values are determined by your Resource and Method menu selections.

   Select Tree View or Raw View to toggle between a hierarchical list of input parameters and the raw data view, where you can provide input directly to the request Header and Body sections.

   Note:

   Tree View is available only for GET methods.

10. Click Test Web Service to initiate the test.

    The test results appear in the Response tab upon completion. A message and an icon indicates the status of the response: a green flag for success, a red flag for failure, and a yellow flag for not yet executed.

    If the test is successful, the Test Status field indicates Request Successfully received, with the green flag, and the response time is displayed, as shown in Figure;5–9.

    Figure 5-9 Successful Test for a WADL

    
    

    
    Description of "Figure 5-9 Successful Test for a WADL"

    
    

    Only the Raw View is available on the Response tab, which will display the entire response from the request invocation.

    If the test fails, an error message is displayed. For example, Figure;5–10 shows an error resulting from a type error.

11. 
    

    Figure 5-10 Data Validation Error

    
    

    
    Description of "Figure 5-10 Data Validation Error"

    
    

Only a subset of the OWSM predefined policies is available, and you can configure only the attributes presented for those policies. All of the other policy attributes use the policy defaults. For example, you cannot enable Secure Conversation, change the message security algorithm suite, and so forth.

Non-security policies and policies not supported by the test function are shown as read-only and cannot be selected. If a service has service policies whose corresponding client policies are not supported, including copies, those policies are shown as read only. This means that copies you made of the predefined policies are not directly listed and are available only through the Advanced option.

For example, assume that your web service has a copy of the oracle/wss11_message_protection_service_policy policy attached, and you have made a copy of the oracle/wss11_message_protection_client_policy. The test client displays both the oracle/wss11_message_protection_client_policy and oracle/wss11_message_protection_client_policy_copy policies, but the oracle/wss11_message_protection_client_policy_copy policy is unavailable and grayed out.

You can choose one of two approaches:

• If for testing purposes the predefined oracle/wss11_message_protection_client_policy policy satisfies your requirements, select the oracle/wss11_message_protection_client_policy.

  The JKS Keystore Location and JKS Keystore Password fields are required and presented on the page. Enter the location and password and click Load Keys.

• If you want to use your own oracle/wss11_message_protection_client_policy_copy policy:

  1. Select Advanced.

  2. Enter the policy URI, in this case oracle/wss11_message_protection_client_policy_copy.

  3. For message protection and SSL policies, the JKS Keystore Location and JKS Keystore Password properties are required.

     Enter the JKS keystore location and password values using the full property names from "Client Policy Configuration Properties That Can Be Overridden at Design Time" in Securing Web Services and Managing Policies with Oracle Web Services Manager:

     oracle.wsm.security.util.SecurityConstants.ClientConstants.WSS_KEYSTORE_LOCATION
     oracle.wsm.security.util.SecurityConstants.ClientConstants.WSS_KEYSTORE_PASSWORD

The options available when you select OWSM Security Policies differ slightly, depending on whether you are testing a SOAP web service or a RESTful web service.

The options for a SOAP web service are shown in Figure 5–11. The options for a RESTful web service are shown in Figure 5–12, with the Advanced Options field selected to display all of the available fields.

Figure 5-11 OWSM Security Policies Test Options for SOAP Web Services

Description of "Figure 5-11 OWSM Security Policies Test Options for SOAP Web Services"

Figure 5-12 OWSM Security Policies Test Options for RESTful Web Services

Description of "Figure 5-12 OWSM Security Policies Test Options for RESTful Web Services"

To test the web service security using OWSM security policies:

1. Select the policies with which you want to test the service. The policies available differ, depending on whether you are testing a SOAP web service or a RESTful web service.

   • Selecting Policies for Testing a SOAP Web Service

     From the Compatible Client Policies list, which displays the compatible client policies as specified in the WSDL, select the client policy to test.

     Alternatively, to perform a negative test on the endpoint, you can select a non-compatible policy, or All from the Other Client Policies list.

   • Selecting Policies for Testing a RESTful Web Service

     From the Client Policies list, select the client policy to test.

   The Configuration Properties required by the selected policy are indicated with an asterisk (*). For example:

   • For username_token and http_token policies, the Username and Password fields are required; for SAML policies only the Username field is required.

   • For message protection and SSL policies, the JKS Keystore Location and JKS Keystore Password fields are required. (The KSS keystore is not supported.)

2. Provide values for the required fields as determined by the policy.

   If the JKS Keystore Location and JKS Keystore Password fields are required by the policy, enter the location and password of a user-created keystore that is NFS accessible and click Load Keys. The associated keystore fields under Advanced Options are populated with the aliases specified in the keystore.

   For more information about creating a keystore, see "Generating Private Keys and Creating the Java Keystore" in Securing Web Services and Managing Policies with Oracle Web Services Manager.

3. Click Advanced Options. Additional keystore alias and SAML properties fields are displayed. Properties required by the selected policies are indicated with an asterisk. Enter the required values, or provide override values in the applicable fields.

This option requires Username and Password credentials that are inserted into the HTTP transport header. The username and password must exist and be valid for the WebLogic Server.

The options available when you select the Advanced option are shown in Figure 5–13.

Figure 5-13 Advanced Test Options

Description of "Figure 5-13 Advanced Test Options"

The Advanced option allows you to use a custom policy, including a copy of a predefined policy, to test the web service security. To do so:

1. Specify the URI of the custom policy in the Policy URI field. For example, oracle/wss11_message_protection_client_policy_copy. This field is required.

2. Specify any configuration overrides for the policy in the Name and Value fields.

   For username_token and http_token policies, Username and Password properties are required; for SAML policies only the username property is required.

   For message protection and SSL policies, the JKS Keystore Location and JKS Keystore Password properties are required. (The KSS keystore is not supported.)

   To add properties, click Add and provide the name/value pair for the configuration override. To delete a property, select it in the table and click Delete.

   Note:

   Properties must be specified using the full name of each property, for example oracle.wsm.security.util.SecurityConstants.ClientConstants.WSS_KEYSTORE_LOCATION. For a complete list of property names for properties that can be overridden, see "Overriding Client Policy Configuration Properties at Design Time" in Securing Web Services and Managing Policies with Oracle Web Services Manager.

   All of the other policy attributes use the policy defaults. For example, if you enabled Secure Conversation or changed the message security algorithm suite, those policy values are used.

The following OWSM client security policies SOAP services are supported by the test function. Copies of these predefined policies are not directly listed and are available only through the Advanced option.

• oracle/wss_http_token_client_policy

• oracle/wss_http_token_over_ssl_client_policy

• oracle/wss_saml_token_bearer_over_ssl_client_policy

• oracle/wss_saml_token_over_ssl_client_policy

• oracle/wss_saml20_token_bearer_over_ssl_client_policy

• oracle/wss_saml20_token_over_ssl_client_policy

• oracle/wss_username_token_client_policy

• oracle/wss_username_token_over_ssl_client_policy

• oracle/wss10_message_protection_client_policy

• oracle/wss10_saml_token_with_message_integrity_client_policy

• oracle/wss10_saml_token_with_message_protection_client_policy

• oracle/wss10_saml_token_with_message_protection_ski_basic256_client_policy

• oracle/wss10_saml20_token_with_message_protection_client_policy

• oracle/wss10_username_id_propagation_with_msg_protection_client_policy

• oracle/wss10_username_token_with_message_protection_client_policy

• oracle/wss10_username_token_with_message_protection_ski_basic256_client_policy

• oracle/wss10_x509_token_with_message_protection_client_policy

• oracle/wss11_message_protection_client_policy

• oracle/wss11_saml_token_identity_switch_with_message_protection_client_policy

• oracle/wss11_saml_token_with_message_protection_client_policy

• oracle/wss11_saml20_token_with_message_protection_client_policy

• oracle/wss11_username_token_with_message_protection_client_policy

• oracle/wss11_x509_token_with_message_protection_client_policy

The following OWSM client security policies for RESTful services are supported by the test function:

• oracle/http_basic_auth_over_ssl_client_policy

• oracle/http_saml20_token_bearer_client_policy

• oracle/http_saml20_token_bearer_over_ssl_client_policy

• oracle/wss_http_token_client_policy

• oracle/http_jwt_token_client_policy

• oracle/http_jwt_token_over_ssl_client_policy