Cache Server-side Configurations
NCache uses a centralized configuration management system to streamline server-side infrastructure settings. This section provides a detailed guide to the three primary configuration categories utilized by NCache Servers to manage cluster registration, WAN replication, and node-level security. These configurations ensure high availability and data integrity across your distributed caching environment.
The cache configuration file contains information regarding all registered caches/clusters. It configures all levels of caches. For modules that need to read the configurations, first it trys to find the config.ncconf file in the application folder. If it doesn't find the config.ncconf in the application folder, it then reads the configuration from the installation folder.
The bridge configuration file contains information regarding all registered bridges. The configuration of all created bridges is stored in a single bridge.ncconf file. The user can change the configuration of a bridge either from the settings of the bridge in the NCache Management Center or from the bridge.ncconf file.
The security configuration file keeps security information that is used by a server node for calling clients. Alachisoft.NCache.Security.dll at the server node is required to provide security services to all clients. Whatever information is required by the assembly, for managing security-related issues, etc., is present in the security.ncconf file. Similarly, users can manage their TLS settings through tls.ncconf.
In This Section
Cache Config
Explains the config.ncconf file that contains information regarding all registered caches/clusters.
Bridge Config
Explains the bridge.ncconf file that contains information regarding bridges.
Security Config
Helps enable NCache security through the security.ncconf file.
TLS Config
Helps enable NCache TLS through the tls.ncconf file.
Monitoring Config
Helps enable NCache monitoring through the monitoring.ncconf file.
Emails Template
Helps enable NCache email alerts through the emails-template.xml file.