Ordinarily all cache tuning information are found in the Portal tuning guides below at the bottom of the page . The documentation usually contain the recommended cache sizes and lifetime as well as how/where to set. WSSECUREMAP is not one of them . There is the description but not how to set it even though it must be stated you probably may not need to tune this cache often

Here is how and where to tune it

WSSecureMap is the DynaCache used for Security Attribute Propagation. This cache should be created with DynaCache default size of 2000. The DynaCache default could be changed but that would affect all caches created with the DynaCache default.

1. If you wish to change only the size of WSSecureMap, you can use following 2 custom properties:

2. The lifetime of entries cannot be configured. Entries in this cache remain valid until the Subject contained in the entry is no longer valid. This is usually the LTPA timeout which defaults to 2 hours. If you have any problem ( Ex: WSSecureMap is not working as expected)

If you have any issues with this cache, Open a support pmr with the Security Mustgather http://www-01.ibm.com/support/docview.wss?uid=swg21470063

We have encountered an issue with the export of the theme policies when doing the Portal Server migration from V. 6.0.x or 6.1.0.x to V. 7.0.x. The error is encountered when running the portal-post-upgrade task on their target server. Normally the target server exports the theme policies from the source environment and then copies it to a file. However in the failing case the export of the policy fails with the following exception:[exec] action-update-theme-policy-wp.theme.customizer:
[exec] Wed May 25 12:42:26 EDT 2011
[exec] [copy] Copying 1 file to /opt/ts/WPS/7.0/DevPortal/ConfigEngine/config/work
[exec] [copy] Copying 1 file to /opt/ts/WPS/7.0/DevPortal/ConfigEngine/config/work