![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
• repo.master—Optional. Default is no value, in that case, the server does not perform load balancing.The repo.master property must be set to either the host name or the IP address of the administration server you want to use as the primary server. The property is set during installation and can be changed by editing this file.
During domain creation, repo.master is set to the hostname of the server. When secondary servers are added, it is given the value "255.255.255.255".As a side effect of enabling fault tolerance, a small _RVFT message is sent out once a second. If you started running in fault tolerant mode, but then wish to use only one server, you can disable fault tolerance by commenting out the repo.master property in the configuration (.tra) file. In that case, the _RVFT message is no longer sent.
If you comment out repo.master, you cannot add secondary servers until you have manually removed the comment.
• If the repo.isMaster property is set true, it overrides the repo.master property to allow the primary server to be specified in a cluster environment.
• repo.state—Optional. Defaults to READ_WRITE.You can set this property explicitly to READ_ONLY to have a primary server come up in that state upon startup.repo.state will not effect Local deployment on a Database based domain, but will block RV or HTTP deployment on a Database based domain. Secondary servers should have the values set to the same as the primary server. This property should not be READ_ONLY unless the primary can lead to synchronization problems.
repo.state should not be used with file based domains and EMS based domains.
• repo.prefixRegionalSubject—Optional. Default is no value.The repo.prefixRegionalSubject property specifies a prefix for the TIBCO Rendezvous subject. In load balancing mode, this prefix is used to consider servers with that prefix preferred servers for read operations.
• repo.updateSecondaryServerPersistentStore—Optional. Defaults to true.The repo.updateSecondaryServerPersistentStore property only applies to secondary servers. It determines whether or not secondary servers working in load balancing mode write data into their persistent backend. If the backend is shared by the primary server and this secondary server, this property should be set to false. If this property is set to true, the secondary server will update not only its cache but also its backend whenever it synchronizes a change with the primary server. Currently this property is ignored by secondary servers that use a database backend. Default value for this property is false.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |