Configuring Solace Cache on the Designated Router

This section describes how to configure and manage Solace Cache on a Solace event broker that is acting as the Designated Router for the Solace Cache facility.

Operating Limits

The global operating limits for Solace Cache are listed in the table below.

Performance limits such as maximum cache request rates and maximum message rates depend on several factors:

• the messaging patterns and sizes used
• the number of Solace Cache Instances used for load balancing
• the server hardware where Solace Cache Instances have been deployed.

For guidance on the expected performance of Solace Cache in your application environment, contact Solace.

Feature	Global Limit	100-tier Limit
Maximum number of Solace Cache Instances on an event broker	1024	256
Maximum number of cached messages per cached topic	unlimited	unlimited
Maximum number of Solace Cache Instances per Cache Cluster	16	16
Maximum number of Cache Clusters per Distributed Cache	64	32
Maximum number of Solace Cache Instances supported by the Designated Router across all Message VPNs	1024	256
Maximum number of Cache Clusters per Designated Router	256	32
Maximum number of Distributed Caches per Designated Router	256	32
Maximum number of configured topics per Cache Cluster	1000	100
Maximum number of cached topics per Cache Instance	unlimited	unlimited

High-Level Steps for Configuring Solace Cache

The following steps show how to configure the main Solace Cache components on the Solace Cache Designated Router through the Solace Event Broker CLI. The exact steps required vary depending on your network conditions and preferred configuration.

If you want to use the Global Caching feature, so that client applications can request messages that are cached on remote Distributed Caches, you must provide additional configuration information when you configure Cache Clusters or modify Solace Cache Instance configuration files. For more information, see Global Caching.

1. Unlock the Solace Cache feature on the Designated Router.

   See Installing and Uninstalling Solace Cache.

2. Configure a new or an existing Message VPN.

   See Configuring Message VPNs for Caching.

3. Configure a Distributed Cache in the Message VPN.

   See Configuring Distributed Caches.

4. Configure one or more Cache Clusters within the Distributed Cache.

   See Configuring Cache Clusters.

5. Add subscriptions for the topics that the Cache Clusters will listen for.

   See Assigning Topics to Cache Clusters.

6. Configure one or more Solace Cache Instances within the Cache Clusters.

   See Configuring Solace Cache Instances.

7. Modify a copy of the Solace Cache configuration file (included with the installation package) for each Solace Cache Instance to add the appropriate configuration parameters for communicating with the event broker host. Save each modified configuration file to the Linux system or event broker that the Solace Cache Instance will run on.

   This file provides the Solace Cache Instance with configuration information when the Solace Cache service is invoked in the following step. For more information, see Customizing Solace Cache Configuration Files.

   If you intend to use the Global Caching feature, review and modify, as necessary, the Global cache request delay and Global cache request time-out parameters. For more information, see Global Caching.

8. Follow the steps described within the README file (included with the Solace Cache installation package), to install and run the Solace Cache service script on the Linux system or event broker with the modified configuration file.
9. Enable the created Solace Cache Instances.

   See Configuring Solace Cache Instances.

10. Enable the created Cache Clusters.

    See Enabling and Disabling Cache Clusters.

11. Enable the created Distributed Cache.

    See Enabling and Disabling Distributed Caches.

12. If the Auto Start Mode was not enabled for the Solace Cache Instances you created, run the start Admin EXEC command at the Distributed Cache level to put all the Solace Cache Instances under the Designated Cache into service. See Performing Solace Cache Administrative Tasks.