×
 
 

 

This documentation supports the 9.1 version of Remedy Action Request System.

To view the latest version, select the version from the Product version menu.

Remedy Action Request System 9.1 ... Configuring after installation BMC Remedy Mid Tier configuration Configuring the Cache Settings page

Using cache with multi-tenant mid tier

With the introduction of multi-tenancy in midtier, there are additional cache categories introduced to optimize the cache footprint by sharing common metadata across the AR System servers. This helps improve scalability and performance of mid tier instance while using mid tier in multi-tenant mode.

If you are running the mid tier in multi-tenant mode, use the Sync Cache option over the Flush Cache option to avoid removal of complete cache contents rather than just refreshing changed objects in the cache. For information on using the sync cache, see Using the sync cache option.

Note

Always use Sync Cache option to get any of your metadata changes reflected in mid tier. There should be no reason to use the Flush Cache option unless you see cache corruption (such as EOFException) in the mid tier logs due to an unclean shutdown or some other system issue. Using Flush cache hinders the mid tier performance as compared to using Sync cache and the performance-related issues multiply when running the mid tier in multi-tenant mode.

Was this page helpful? Yes No Submitting... Thank you
Last modified by Lelani Prevost on Nov 13, 2017
sync multi-tenancy mid_tier cache flush

Comments

Backing up the mid tier cache
Avoiding abrupt shutdown of the mid tier
© Copyright 1991-2021 BMC Software, Inc. © Copyright 1991-2021 BladeLogic, Inc.
Legal notices

Powered by Atlassian Confluence and Scroll Viewport

© Copyright 2005-2021 BMC Software, Inc. Use of this site signifies your acceptance of BMC’s Terms of Use . BMC, the BMC logo, and other BMC marks are assets of BMC Software, Inc. These trademarks are registered and may be registered in the U.S. and in other countries.