This documentation supports the 20.02 version of Remedy Action Request (AR) System.

To view an earlier version, select the version from the Product version menu.

Cache Settings parameters

The following table lists the parameters for the Cache Settings page of Mid Tier Configuration Tool.

Cache settings

Sync in cluster

Indicates whether you want the cache to be synced automatically on a group of mid tiers.

If the check box is:

  • Selected — The cache will be synced periodically and simultaneously across all mid tiers in a group.
  • Cleared (default) — The cache will be synced automatically at the interval that you specify in the Definition Change Check Interval field.

For more information about this option, see Knowledge Base article ID 000030484.

Resource Check Interval (Seconds)The time limit (in seconds) for which resources (such as images, .css files, and JavaScript files) can be used. The default value is 86400 seconds. If a user closes a form and opens it again within the specified expiry time, the image is cached and is not downloaded again. This helps increase the performance of BMC Remedy Mid Tier.
Enable Cache Persistence

Specifies whether forms cached in memory are written to files for faster retrieval. If the check box is:

  • Selected — Forms cached in memory are written to files. This option enables faster retrieval of forms when the server is restarted.
  • Cleared — Forms cached in memory are not written to files.

AR System forms can be stored on disk only after Enable Cache Persistence is selected. AR System forms loaded before the Enable Cache Persistence is selected are not saved to disk. For more information, see About the Persistent Cache option.

Backup DirectoryFull path of the directory where good cache backup exists. For more information, see Backing up the mid tier cache.
Flush CacheRemoves all items from the caches that BMC Remedy Mid Tier maintains. The next time the mid tier needs those objects, the most up-to-date versions are retrieved from the AR System server.
Sync CacheFor the selected servers, clears the cache only for the objects that have been changed. For more information, see Using the sync cache option.
Preload (button in the Action column) Triggers the preload process for the specified AR System server.
Preload (column)

Describes the preload status. The values are as follows:

  • Disabled —  if preload is turned OFF from AR Server Settings page for the specified server.
  • Not Running – if preload is turned ON from AR Server Settings page while the BMC Remedy Mid Tier is running.
  • Running (displays a progress bar) — if preload is in progress because of BMC Remedy Mid Tier startup, or because you started preload by clicking the Preload button from the Cache Settings page.
  • Completed — if preload has completed successfully.
  • Aborted — if preload was aborted because of some error. For example, preload was aborted because the AR System server is not reachable, or has restarted, or has timed out. The BMC Remedy Mid Tier logs contain more about the failure.

For more information, see AR Server Settings parameters.

Sync StatusDescribes the sync status. The values are as follows:
  • Disabled —  if the Perform Check checkbox  is unchecked from the Edit AR Server page of the AR Server Settings page.
  • Not Started — the default state.
  • Starting — the intermittent state when Sync Cache button is clicked.
  • Running —  if sync operation is in progress.
  • Completed - <timestamp> - if sync operation has completed successfully, and has deleted some metadata from the cache because of the changes detected on AR System server.
  • Nothing To Sync - <timestamp> - if sync operation has completed successfully, but there are no changes to the metadata changes on the AR System server.
  • Failed — if some errors occurred during the sync operation. The BMC Remedy Mid Tier logs contain details about the failure.
Was this page helpful? Yes No Submitting... Thank you