Cache Client Settings
This section describes step-by-step instructions on how to add or remove client nodes in a clustered cache, create or remove client cache and configure client specific settings. A client node is the one from where clustered cache can be initialized to make API calls.
Configuring Client Node Settings
You can configure settings specific to client node as well.
Using NCache Manager
Click on a client machine IP address in Cache Explorer for a cache to open client related settings of this client node.
On Main tab you can configure Connection Timeout, Connection Retries, Retry Interval and Client Request Timeout.
All values are in seconds. A brief description of each attribute is given is given in NCache Manager alongside each attribute.
Using the Settings tab, you can:
Enable/disable client load balancing using the checkbox Enable Client Load Balancing,
Specify Server Priority for this client,
Change Sync Mode of client cache to either Optimistic or Pessimistic.
Using the Security tab, you can specify Primary and Secondary user credentials, i.e., User Id and Password. These credentials will be used when this cache is initialized from this client node.
At the Backing Source tab, you can select the default Read-Thru and/or Write-Thru providers, only if these providers are configured for the cache.
Apply configuration changes by right clicking on the cache name in Cache Explorer and select Apply Configuration option.
You might get prompted with a dialog box upon these changes, asking whether to reload or overwrite the cache config file. For more detail maintaining data integrity, refer to this chapter.
Manually Editing NCache Configuration
Make sure the cache is stopped before making any configuration changes.
In client.ncconf of the server node, add the following information under the
<ncache-server connection-retries="5" retry-connection-delay="0" retry-interval="1" command-retries="3" command-retry-interval="0.1" client-request-timeout="90" connection-timeout="5" port="9800"/> <cache id="demoClusteredCache" load-balance="True" enable-client-logs="False" log-level="error"> <server name="220.127.116.11"/> </cache>
Repeat this step for all client nodes.