Select WebLogic Domain Web Services Platform Policy Configuration.

14-18 Oracle Fusion Middleware Security and Administrators Guide for Web Services Because the Policy Manager is security enabled, the csf-key specifies the java.naming.security.principal and java.naming.security.credentials when using the JNDI URL to look up a Policy Manager.

c. Click OK.

For more information on storing, retrieving, and deleting credentials, see Adding Keys and User Credentials to the Credential Store on page 10-17

6. Select the Policy Cache tab.

7. To modify the policy cache property for Web service endpoints, select it and then click Edit. In the Edit Property window, you can edit the Value field to change the default amount for each property. a. cache.tolerance – Amount of time in milliseconds between refreshes of the policy cache. This ensures that the policy set retrieved from the Web service endpoint policy cache is the most current version that is, it has not exceeded the cache.tolerance value. If it is determined that the policy set is stale, the updated policy set is retrieved from the Oracle WSM Policy Manager and refreshed in the Web service endpoint policy cache. The default is 60000 milliseconds 1 minute. Note: The refresh delay amount for Web service endpoints is aggregated with the value of the cache.refresh.repeat property if any on the Policy Accessor tab for the Oracle WSM Policy Manager. Therefore, you should verify whether this additional value produces the desired refresh delay when combined with the cache.refresh.repeat amount. For more information, see Configuring Web Service Policy Retrieval on page 14-18.

b. To add another property, click Add, and in the Add Property window, specify

the necessary values.

c. Click OK.

8. To modify an existing property, select it and then click Edit.

9. To delete an existing property, select it and then click Delete.

10. Click Apply to apply the property updates.

Configuring Web Service Policy Retrieval The Policy Accessor tab also enables you to configure the retrieval of Oracle WebLogic Web service policies from a repository. This includes specifying the repository accessor type for example, classpath, local, or remote, repository location JARs, directory, or host and port, account information for a remote repository, retry logic for high availability, and cache tuning. 1. Access the Platform Policy Configuration page, as described in Configuring Platform Policy Properties on page 14-15.

2. Select the Policy Accessor tab.

3. Click Add to add a policy retrieval property.

4. Use the following table to specify the available property names and values in the Add Property window: Advanced Administration 14-19

5. To modify an existing property, select it and then click Edit.

6. To delete an existing property, select it and then click Delete.

7. Click Apply to apply the property updates.

Table 14–3 Properties in Add Property Window Element Description java.naming.provider.url JNDI URL that specifies the location of a running Oracle WSM Policy Manager in another domain. By default, this property is not specified. If this property is not specified, Oracle WSM auto-discovery attempts to look up the Policy Manager in the same domain. jndi.lookup.csf.key If the location of the Oracle WSM Policy Manager is provided in the java.naming.provider.url property, the jndi.lookup.csf.key provides credential configuration. Because the Oracle WSM Policy Manager is security enabled, the jndi.lookup.csf.key specifies the java.naming.security.principal and java.naming.security.credentials when using the JNDI URL to look up a Oracle WSM Policy Manager. By default, this property is not specified. You should configure this property when: ■ You want to specify an explicit account to connect with the Oracle WSM Policy Manager rather than the system account, OracleSystemUser, that is used by Oracle WSM by default. ■ The Authentication Provider and LDAP directory that is configured does not support system accounts used by Oracle WebLogic, but which Oracle WSM relies on by default. Therefore, a different account in the LDAP directory must be used. ■ There is no concept of default system accounts in a particular application server, and so the system cannot rely on system accounts. For more information on modifying the default user, see Modifying the Default User on page 14-23. cache.refresh.initial Number of milliseconds to wait before initial cache refresh. The default is 600000 milliseconds 10 minutes. cache.refresh.repeat Number of milliseconds to wait between cache refreshes. The default is 600000 milliseconds 10 minutes. missing.retry.delay Number of milliseconds to wait before trying to retrieve a missing document. The default is 15000 milliseconds. usage.record.delay Number of milliseconds to wait before sending usage data. The default is 30000 milliseconds. failure.retry.count Number of times to retry after communication failure. The default is 2 retry attempts. failure.retry.delay Number of milliseconds to wait between retry attempts. The default is 5000 milliseconds. oracle.wsm.policymanager.a ccessor.IRepositoryAccessor Type of repository accessor class. The supported value is remote Java EE.