Add Clustered Caches to the Bridge
You can add multiple existing clustered caches to an NCache Bridge to enable WAN Replication. These caches must already be configured on local or remote servers before being added. Integrating multiple clusters into a Bridge helps ensure high availability and disaster recovery. Each cache can be configured in Active or Passive mode. Please follow these steps to add a cache to your Bridge.
Using the NCache Management Center
Important
Please ensure your Bridge is stopped.
Launch the NCache Management Center by browsing to http://localhost:9801 or
<server-ip>:9801.In the left navigation bar, click on the Bridges. It will open up a list of pre-existing Bridges.
Method 1: Select the Bridge and click on
button.Method 2: From the list, select the Bridge Name and go to View Details.

A new page will open up containing the Bridge configuration and details.
Go to the Bridge Caches section on this page and click on
.

- Enter the Server Node IP containing the clustered cache and click Next.

- A list containing all the registered caches appears on the screen. Select the clustered cache to be added to the Bridge and click Next.

- After the selection of the cache, a new page opens up showing Bridge cache(s) settings. Choose the Cache Mode (i.e., Active or Passive) for this Bridge configuration, as well as specify the Environment which will distinguish the caches if they have the same names. Click Finish.

- The selected cache will be successfully added to the Bridge and will be displayed under the Bridge Caches section.

- Add the second cache for this Bridge using the same steps mentioned above.
Using PowerShell
The Add-BridgeCache cmdlet enables users to add an existing clustered cache to a specified NCache Bridge.
- This command adds an existing clustered cache named defaultCache to the Bridge defaultBridge running on 20.200.20.11. The cache name will now be defaultCache.WestCoast using Port 9817.
Add-BridgeCache -Name defaultBridge -Server 20.200.20.11 `
-CacheName defaultCache -CacheServer 20.200.20.12 `
-Environment WestCoast -Port 9817
- This command adds an existing clustered cache named defaultCache to the Bridge defaultBridge running on 20.200.20.11. The cache name will now be defaultCache.WestCoast. The mode of the Bridge is set as Active.
Add-BridgeCache -Name defaultBridge -Server 20.200.20.11 `
-CacheName defaultCache -CacheServer 20.200.20.12 `
-Environment WestCoast -Mode Active
- This command adds an existing clustered cache named defaultCache to the Bridge defaultBridge running on 20.200.20.11. The cache name will now be defaultCache.WestCoast using security credentials.
Add-BridgeCache -Name defaultBridge -Server 20.200.20.11 `
-CacheName defaultCache -CacheServer 20.200.20.12 `
-Environment WestCoast -Credentials(Get-Credential john_smith)
- This command adds defaultCache on 20.200.20.12 to defaultBridge on 20.200.20.11 under the US environment, using mutual TLS (mTLS). It runs from a machine where NCache is not installed and uses
C:\certs\client.pemto authenticate the machine running the cmdlet. The-TlsCertPasswordparameter decrypts the certificate’s password-protected private key. Omit this parameter if the private key is not encrypted.
Add-BridgeCache -Name defaultBridge -Server 20.200.20.11 `
-CacheName defaultCache -Environment US `
-CacheServer 20.200.20.12 -TlsCertPath "C:\certs\client.pem" `
-TlsCertPassword "clientKeyPassword"
- This command adds clustered cache defaultCache to Bridge defaultBridge as defaultCache.WestCoast. It configures the load balancer IP addresses for both the cache server and the Bridge server.
Add-BridgeCache -Name defaultBridge -CacheName defaultCache `
-Environment WestCoast -LoadBalancedCacheServer 20.200.20.11 `
-LoadBalancedBridgeServer 20.200.20.12 -LoadBalancerEnabled
See Also
Create Bridge
Configure Conflict Resolver
Change Cache Synchronization Modes
Remove Cache from Bridge