Peer-to-Peer Server Configuration Using Multicast URL

Before peer-to-peer server configuration using multicast URL, ensure that your system meets all of the requirements.

Ensure the following requirements:

  • Metaspace name and Multicast URL must be the same for 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 must be available and that should start first.
    Peer-to-Peer Server Configuration Using Multicast URL
    Property Name Member1 Member2 Member3
    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
    AS unicast discovery URLs
(com.tibco.cim.cache.as.discoveryurl) Not Required Not Required Not Required
    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
    AS Unicast URL
(com.tibco.cim.cache.as.unicasturl ) Not Required Not Required Not Required
    AS Multicast URL
(com.tibco.cim.cache.as.multicasturl ) For example, tibpgm://12348 For example, tibpgm://12348 For example, tibpgm://12348
    AS Member Distribution Role
(com.tibco.cim.cache.as.distributionrole) Select SEEDER from the drop-down list. Select LEECH from the drop-down list. Select SEEDER from the drop-down list.