Policy Server Administration Guide › Cache Management › Configure Caches

Previous Topic: Cache Management Overview

Next Topic: Flush Caches

Configure Caches

You can view the refresh status of Policy Server caches and disable or enable cache flushing through the FSS Administrative UI or through three smpolicysrv command-line options. By using these options to suspend and resume cache flushing, you can resolve policy evaluation issues. These commands are issued by the central administration Policy Server to all secondary Policy Servers.

Note: Because Policy Server commands are processed according to a thread management model, changes to the cache status are not visible in the smps.log file immediately.

To manage cache status through the FSS Administrative UI

  1. Log in to the FSS Administrative UI.
  2. From the menu bar, select Tools, Manage Cache.

    The SOA Security Manager Cache Management dialog opens.

  3. View the cache status in the Cache updates group box:

    Disabled: Cache flushing is disabled.

    Enabled: Cache flushing is enabled.

  4. (Optional) Click the Enable/Disable button and OK to modify the cache status.

To manage cache status through the Command Line Interface

  1. Open a command prompt.

    Important! If you are running a SOA Security Manager utility or executable on Windows Server 2008, be sure to open the command–line window with Administrator permissions, even if you are logged into the system as an Administrator. For more information, see the release notes for your SOA Security Manager component.

  2. Enter one of the following commands:
    smpolicysrv -disablecacheupdates

    Disables cache flushing.

    smpolicysrv -enablecacheupdates

    Enables cache flushing.

    smpolicysrv -statuscacheupdates

    Reports the refresh status of Policy Server caches to the log file: smps.log.

    Disabled: Cache flushing is disabled.

    Enabled: Cache flushing is enabled.

Note: On Windows systems, do not run the smpolicysrv command from a remote desktop or Terminal Services window. The smpolicysrv command depends on inter-process communications that do not work if you run the smpolicysrv process from a remote desktop or Terminal Services window.