Installation Guides › Implementation Guide › Performance Tuning › Web Tier Performance › Reduce Traffic between Your Agents and the Policy Server › Resource Cache

Resource Cache

Each SOA Security Manager Agent uses a resource cache to store the following information it receives from the Policy Server temporarily:

• Whether a resource is protected
• Any additional response attributes included in the policy

The Agent searches the resource cache to determine if a resource is protected before contacting the Policy Server. If the resource exists in the cache, traffic to the Policy Server is reduced because the Agent does not make an IsProtected call to the Policy Server.

Two Agent configuration parameters affect the resource cache. Consider the following as you plan your SOA Security Manager deployment:

Resource Cache Timeout

We recommend basing the timeout interval of the Agent resource cache on the results of your capacity planning tests. A timeout interval that is too small limits the effectiveness of the resource cache. The value of the ResourceCacheTimeout parameter in your Agent configuration determines the timeout interval of the resource cache.

Resource Cache Size

We recommend using a resource cache that is 10 percent larger than the largest number of URIs that you expect users to request. If you are protecting an application that uses dynamic URLs (such as URLs with query strings) consider using the IgnoreQueryData parameter instead of adjusting the size of the resource cache. The value of the MaxResourceCacheSize agent configuration parameter determines the size of the resource cache.

Note: For more information, see the [set the wcc variable for your book].