Mastering Mid Tier Cache Management for Optimal BMC Remedy Performance

In the realm of IT Service Management (ITSM) and enterprise application support, particularly with platforms like BMC Remedy, performance is paramount. Users expect seamless, snappy interactions, and any lag can quickly translate into frustration and reduced productivity. At the heart of achieving this responsiveness for web-based access to BMC Remedy applications lies the efficient management of the Mid Tier’s cache.

For those of you managing BMC Remedy environments, understanding the Mid Tier’s caching mechanisms isn’t just a technical detail; it’s a critical skill. It’s the difference between a system that hums along beautifully and one that stutters. This article aims to demystify Mid Tier cache management, offering practical insights, real-world scenarios, and even some tips to help you shine in interviews.

Understanding the Mid Tier: Your Bridge to BMC Remedy

Before we dive deep into caching, let’s quickly recap what the Mid Tier is. Think of it as the sophisticated intermediary, the digital diplomat, between your users’ web browsers and the powerful BMC AR System server. It translates user requests from the web into a language the AR System server understands, and then it takes the server’s responses and presents them in a user-friendly format back to the browser.

Essentially, the Mid Tier:

• Enables Web Access: It’s what allows your users to interact with BMC Remedy applications directly from their web browsers, no desktop client required for many functions.
• Acts as a Client to AR System: It makes requests to the AR System server to fetch data, submit changes, and execute business logic.
• Acts as a Server to the Browser: It serves up the web pages, JavaScript, CSS, and other front-end assets that users see and interact with.

This dual role is where caching becomes so crucial. The Mid Tier needs to be efficient in both fetching information from the AR System and serving it up to users. Caching is its primary tool for achieving this speed.

The Power of the Cache: Why It Matters

Imagine the AR System server as a vast library. Every time a user requests a specific book (a form definition, a piece of configuration, a piece of metadata), the Mid Tier would have to go all the way to the library, find the exact book, and bring it back. This is inefficient, especially if multiple users want the same book. This is where caching comes in.

The Mid Tier caches frequently accessed information (like form definitions, view definitions, active links, filters, etc.) locally. When a user requests something that’s already in the cache, the Mid Tier can serve it up almost instantly, bypassing the need to query the AR System server. This dramatically reduces latency and improves the user experience. It’s like having a personal assistant who keeps the most requested books right at your desk.

Navigating the Mid Tier Configuration Tool

To effectively manage your Mid Tier’s cache, you need to know how to access and use its configuration interface. The Mid Tier Configuration Tool is your central hub for all things Mid Tier, including cache settings.

You can typically access it through your web browser using a URL similar to this:

http://[hostName]:[port]/[contextPath]/shared/config/config.jsp

For BMC Remedy, a common example looks like:

http://localhost:8080/arsys/shared/config/config.jsp

Within this tool, you’ll find sections dedicated to configuring various aspects of the Mid Tier, including:

• AR System server information (hostnames, ports, etc.)
• Security settings (passwords, authentication)
• Cache policy information
• Web services configurations

Specifically, for cache-related settings, you’ll often find options accessible via a URL like:

http://localhost:8080/arsys/shared/config/config_cache.jsp

This dedicated cache configuration page is where you’ll make the critical decisions about how your Mid Tier handles its data.

Cache Modes: Production vs. Development

This is arguably the most critical decision you’ll make regarding Mid Tier cache. The choice between Production Cache Mode and Development Cache Mode has profound implications for system stability, performance, and administrative operations. Let’s break them down.

Production Cache Mode: The Default for Performance

When you install BMC Remedy, the Mid Tier usually defaults to Production Cache Mode. This is not by accident; it’s designed for environments where end-user performance is the absolute top priority.

Key Characteristics of Production Cache Mode:

• Designed for High User Loads: This mode is ideal when you have a large number of application users concurrently accessing BMC Remedy. It ensures their operations are not delayed by administrative tasks.
• Non-Disruptive Administrative Operations: The magic of this mode is how it handles administrative operations (like clearing the cache, deploying changes, or updating configurations). When an administrative operation is initiated, the AR System server doesn’t lock out other users. Instead, it creates a temporary, administrative copy of its cache. This allows other users to continue working with the existing, shared cache seamlessly while the administrative changes are being prepared or applied.
• Definition Change Check Interval: A crucial setting here is the Definition Change Check Interval. In Production mode, this value is typically set to GREATER than 0. This interval dictates how often the Mid Tier checks the AR System server for any definition changes (e.g., new forms, modified fields). If changes are detected, the Mid Tier will eventually update its cache.
• Sync Cache Feature: The Sync Cache feature is also available and functional in this mode. This allows administrators to manually “sync” or refresh the cache from the AR Server on demand, ensuring that the Mid Tier reflects the latest changes without waiting for the defined interval.

When to use Production Cache Mode:

• Any production environment with active end-users.
• Environments where administrators need to make frequent changes without impacting user sessions.
• Situations where minimizing user-facing downtime is paramount.

Real-world Example: Imagine your support desk agents are actively using BMC Remedy to manage tickets. An administrator needs to deploy a new workflow. In Production Cache Mode, the agents will not experience any interruption. The administrator initiates the cache refresh, and the Mid Tier handles it in the background, ensuring agents can continue their critical work without being kicked off or seeing their system freeze.

Development Cache Mode: For Focused Administration

Development Cache Mode, as the name suggests, is geared more towards development and testing phases where administrative activities might be more frequent and user impact during those periods is less of a concern.

Key Characteristics of Development Cache Mode:

• Administrative Operations Lock Out Users: Unlike Production mode, administrative operations in Development mode *do* cause the shared cache to be locked. Other users attempting to access that cache will be temporarily denied access until the administrative operation is complete.
• Waiting for Operations to Complete: The Mid Tier administrator thread must wait for all current users accessing the cache to finish their operations before it can proceed with making changes.
• Impacted by Long-Running Tasks: This mode is particularly sensitive to long-running processes like escalations, BMC Atrium Integration Engine jobs, or complex queries. If these operations are active when an administrator tries to make a change, the administrator’s operation will be significantly delayed, potentially leading to extended downtime for other users.
• Definition Change Check Interval: In Development mode, the Definition Change Check Interval is set to 0. This means the Mid Tier will not automatically check for definition changes from the AR Server. Changes only occur when an administrator manually clears or syncs the cache.
• Sync Cache Feature Unavailable: The Sync Cache feature is explicitly not available in this mode.

When to use Development Cache Mode:

• Development or testing environments where you are making frequent changes and users are few or non-existent.
• Periods of scheduled maintenance where you can afford to temporarily restrict user access.
• Situations where you need to be absolutely certain that no background processes interfere with an administrative cache update.

Real-world Example: A developer is building a new application module in a test environment. They need to deploy a series of form and workflow changes. They switch the Mid Tier to Development Cache Mode. While they are making these changes, any testers who happen to be logged in might be temporarily locked out. Once the developer is finished and clears the cache, the testers can resume. This mode ensures the developer has exclusive control during their update window.

NOTE: For in-depth details on these and other Mid Tier configuration options, always refer to the official BMC Remedy AR System documentation, particularly the sections on configuration after installation. These guides are your definitive source of truth.

Practical Cache Management: How to Configure and Maintain

Now that we understand the ‘why’ and ‘what’, let’s get to the ‘how’. Effective cache management involves both initial setup and ongoing maintenance.

Accessing and Modifying Cache Settings

As mentioned, the primary tool is the Mid Tier Configuration Tool. After navigating to the appropriate cache configuration URL (e.g., http://localhost:8080/arsys/shared/config/config_cache.jsp), you’ll see options to:

• Select Cache Mode: Toggle between Production and Development modes.
• Set Definition Change Check Interval: This is crucial for Production mode. A value of 0 disables the automatic check, while a positive integer specifies the interval in seconds. For example, setting it to 300 means the Mid Tier checks every 5 minutes.
• Configure Cache Size: While not explicitly detailed in the provided references, other cache parameters might exist here or in related configuration files that govern how much data the cache can hold.

After making changes, remember to click “Save” or “Apply” and typically, you’ll need to restart the Mid Tier service for these changes to take full effect.

When and How to Clear/Sync the Cache

The need to clear or sync the cache often arises after administrative changes or when you suspect stale data is causing issues.

• Production Mode: Use the Sync Cache button within the Mid Tier Configuration Tool. This forces the Mid Tier to fetch the latest definitions from the AR System server. You can also manually clear the cache by restarting the Mid Tier service, but ‘Sync Cache’ is generally the preferred, less disruptive method for production.
• Development Mode: Clearing the cache is a more manual process. Often, simply restarting the Mid Tier service will accomplish this. The Sync Cache feature is unavailable here.

Changing the Configuration Password

The configuration password is an important security measure. You can change it through several methods:

1. Mid Tier Configuration Tool (Web Browser): This is the most common and recommended method.
   1. Navigate to the Mid Tier Configuration Tool overview page: http://[hostName]:[port]/arsys/shared/config/config_overview.jsp
   2. Look for a section related to “Configuration Password” or “Security Settings.”
   3. You’ll typically be prompted to enter the current password and then the new password twice.
   4. Save your changes. You may need to restart the Mid Tier service.
2. ar.cfg file: The AR System server’s configuration file (ar.cfg) can also store password-related information. However, for Mid Tier configuration passwords, this is less common than using the web tool directly. If you need to modify it here, ensure you understand the exact parameter and format. Caution: Directly editing configuration files requires extreme care to avoid introducing errors. Always back up the file before making changes.
3. User Tool: While the User Tool is primarily for end-users and administrators interacting with AR System forms, certain administrative password changes might be accessible through its interface, especially if they relate to AR System server-level credentials. However, for the *Mid Tier’s specific configuration password*, the web tool is the direct path.

Best Practice: Always use the Mid Tier Configuration Tool for Mid Tier-specific settings like its configuration password. It’s designed for this purpose, is less error-prone, and provides immediate feedback.

Troubleshooting Common Cache Issues

Even with careful management, you might encounter problems. Here are some common issues and how to address them:

Interview Relevance: Showcasing Your Cache Expertise

Understanding Mid Tier cache management is a common topic in interviews for BMC Remedy administrators and support roles. Being able to articulate these concepts clearly demonstrates your practical knowledge and your ability to optimize system performance.

Conclusion

Mastering Mid Tier cache management is not just about knowing where to click; it’s about understanding the underlying principles that drive performance in your BMC Remedy environment. By leveraging Production Cache Mode for your users, carefully managing the Definition Change Check Interval, and knowing when and how to sync or clear the cache, you can ensure a responsive, stable, and efficient experience for everyone.

Remember to always consult the official BMC documentation for the most accurate and up-to-date information. With this knowledge, you’re well-equipped to optimize your Mid Tier and keep your BMC Remedy applications running at their best.