Peer-to-Peer Server Configuration Using Discovery URL
Before peer-to-peer server configuration using discovery URL, ensure that your system meets all of the requirements.
Ensure the following requirements:
- 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.
- 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 Discovery 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) For example, tcp://10.20.30.41:50000 tcp://10.20.30.42:50000 tcp://10.20.30.43:50000
For example, tcp://10.20.30.41:50000 tcp://10.20.30.42:50000 tcp://10.20.30.43:50000
For example, tcp://10.20.30.41:50000 tcp://10.20.30.42:50000 tcp://10.20.30.43: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
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 SEEDER from the drop-down list. Select LEECH from the drop-down list. Select SEEDER from the drop-down list.
Copyright © Cloud Software Group, Inc. All rights reserved.