Centralized Cache Server Configuration

In the Centralized Cache Server topology, two or more TIBCO MDM servers run with ActiveSpaces LEECH, and a dedicated AS-Agent runs as a Seeder. For example:

For example:

Centralized Cache Server

Ensure the following:

  • Metaspace name and Discovery URL List contain listen URL of all nodes.
  • Any port, supported by ActiveSpaces can be used for these members. If two members are on the same host or IP address, the port must be different for both the members.
  • Any member can use any distribution role. However, at least one SEEDER that starts first should be available.

To configure Centralized Cache Server, specify the following properties in Configurator:

Centralized Cache Server Configuration
Property Name Member1 Member2 AS-Agent1 AS-Agent2
AS Meta Space Name Type
(com.tibco.cim.cache.as.metaspace) 
For example,
cim_ms_prod
 
For example,
cim_ms_prod
 
For example,
cim_ms_prod
 For example, 
cim_ms_prod
AS unicast discovery URLs
(com.tibco.cim.cache.as.discoveryurl) For example, tcp://10.20.30.41:50000 
tcp://10.20.30.42:50000
tcp://10.20.30.43:50000
tcp://10.20.30.44:50000
 For example, tcp://10.20.30.41:50000 
tcp://10.20.30.42:50000
tcp://10.20.30.43:50000
tcp://10.20.30.44:50000
 For example, tcp://10.20.30.41:50000 
tcp://10.20.30.42:50000
tcp://10.20.30.43:50000
tcp://10.20.30.44:50000
 For example, tcp://10.20.30.41:50000 
tcp://10.20.30.42:50000
tcp://10.20.30.43:50000
tcp://10.20.30.44:50000
AS Listen URL
(com.tibco.cim.cache.as.listenurl)

(Optional)

For example, tcp://10.20.30.41:50000 For example, 
tcp://10.20.30.42:50000
 For example, 
tcp://10.20.30.43:50000
 For example, 
tcp://10.20.30.44:50000
AS Unicast URL
(com.tibco.cim.cache.as.unicasturl )        
AS Multicast URL
(com.tibco.cim.cache.as.multicasturl)        
AS Member Distribution Role
(com.tibco.cim.cache.as.distributionrole) Select LEECH from the drop-down list. Select LEECH from the drop-down list. SEEDER SEEDER