5-4 Oracle Fusion Middleware Third-Party Application Server Guide
a.
In the Name field, enter the JNDI provider URL property as java.naming.provider.url.
b.
In the Value field, enter the URL for the server on which the policy manager is running. For example:
corbaloc:iiop:hostname:rmiport where hostname specifies the DNS name or IP address of the WebSphere
server and rmiport specifies the port number on which the policy manager is running.
c. Click OK.
6. Click Add to define a corresponding csf-key credential property.
If the location of the Oracle WSM Policy Manager is provided in the java.naming.provider.url property, the jndi.lookup.csf.key provides
the credential configuration.
In the Add New Configure Property window, specify the following values:
a.
In the Name field, enter the name of the JNDI provider’s csf-key credential property as jndi.lookup.csf.key.
b.
In the Value field, enter the csf-key credentials. 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.
For example, using the sample provided in Configuring a Default
Administrative User from the LDAP Directory on page 5-1, the
administrative user is orcladmin and the csf-key is orcladmin-csf-key.
c. Click OK.
Figure 5–2 shows the Policy Accessor tab with the
java.naming.provider.url and jndi.lookup.csf.key property settings.
Note: The csf-key that you specify in this step must match the
csf-key specified for the Policy Manager administrative user in the credential store. For more information about adding an Oracle WSM
Policy Manager administrative user to the credential store, see Configuring a Default Administrative User from the LDAP
Directory on page 5-1.
Managing Web Services on IBM WebSphere 5-5
Figure 5–2 Policy Accessor Property Settings
For information about additional properties you can set on the Policy Accessor tab, see Configuring Web Service Policy Retrieval in Oracle Fusion Middleware
Security and Administrators Guide for Web Services.
7. Optionally, select the Policy Cache tab.
The Policy Cache tab allows you to tune the behavior of the policy cache delay for Web service endpoints, which can help to avoid network calls and increase
performance when fetching policies from a remote Oracle WSM Policy Manager.
8. To modify an existing policy cache property, select it and then click Edit. In the
Edit Policy Cache Property window, you can edit the Value field to change the default amount for the property.
You may want to edit the following property:
■
cache.tolerance – 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.
9. To add another property, click Add, and in the Add New Policy Cache Property
window, specify the necessary values.
10. To delete an existing property, select it and then click Delete.
11. Click Apply to apply the property updates.
5.3 Differences and Restrictions When Developing Web Services Applications on IBM WebSphere
