Select the configuration property and click Edit to make the change to the action Click Save.

8-20 Oracle Fusion Middleware Security and Administrators Guide for Web Services Figure 8–10 Overriding a Policy Configuration Property

3. Enter the override value in the Value field for the property and click Apply.

The property is overridden on a per-attachment basis. For example, assume that you have not changed the value of the keystore.sig.csf.key property for the oraclewss10_message_protection_ service_policy and that it is still blank. If Web service A attaches the oraclewss10_ message_protection_service_policy and overrides the keystore.sig.csf.key property to be sigkey, the keystore.sig.csf.key property has a value of sigkey only for the oraclewss10_message_protection_service_policy attached to Web service A. For all other policies, keystore.sig.csf.key uses the value you configure as part of setting up the keystore for message protection, as described in Configuring Keystores for Message Protection on page 10-8. Overriding Configuration Properties When Attaching a Policy Using WLST When you attach a policy that has an overridable property, you can override the existing value using the setWebServicePolicyOverride command. To do so, use the following procedure.

1. Attach the policy to the service as described in

Attaching a Policy to a Web Service Using WLST on page 8-5.

2. Use the setWebServicePolicyOverride command to override policy

properties. setWebServicePolicyOverrideapplication,moduleOrCompName,moduleType, serviceName,portName,policyURI,properties Note: This procedure applies to Oracle Infrastructure Web services only. Attaching Policies to Web Services 8-21 You can override the properties listed in Table 8–1 and Table 8–2 , and user-defined properties as described in Configuring User-Defined Client- or Server-Side Override Properties on page 8-25. For example, to override the keystore.sig.csf.key property in the oraclewss10_message_protection_service_policy policy, use the following command: wls:wls-domainserverConfigsetWebServicePolicyOverride wls_domainAdminServerJaxwsejb30ws,jaxwsejb, web,WsdlConcreteService,WsdlConcretePort, oraclewss10_message_protection_service_ policy,[keystore.sig.csf.key,sigkey] 3. For ADF and WebCenter applications, restart the Web service application. You do not need to restart a SOA composite. For more information about this WLST command and its arguments, see Web Services Custom WLST Commands in WebLogic Scripting Tool Command Reference. Attaching Client Policies Permitting Overrides The policy configuration override feature allows you to specify certain Web service client configuration information on a per-client basis, in addition to, or in lieu of setting it globally for any attachment of the policy. This targeting of configuration information limits the number of distinct policies you need to maintain. You can define a single policy, and specify a default value for a configuration value. Rather than creating multiple policies with slightly varied configurations, you could use the same generic policy and override specific values to meet your requirements. For example, the oraclewss_http_token_client_policy policy is one example of a policy that includes the csf-key property, which has a default value of basic.credentials. The value signifies a key that maps to a usernamepassword. It might happen that you will always use the same key value any time you attach this policy to any number of Web service clients. In this case, you can specify the key value on the oraclewss_http_token_client_policy policy Configurations page and have it apply to every instance. However, you also have the option to override this key value on a per-client basis. Notes: If the policy that you specify is not attached to the port, an error message is displayed andor an exception is thrown. If you set the properties argument to None, then all policy overrides are removed. 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.