Enterprise Administration > File Vaulting and Replication > Replication > Understanding Replication > Editing Replication Properties
  
Editing Replication Properties
Editing properties is an essential activity in configuring content replication. If you are not setting properties through a graphical user interface or in a mapping file, you must add or edit properties with the xconfmanager utility. For more information, see Using the xconfmanager Utility.
The following list describes the properties that are most relevant to replication, categorized by their area of influence. All of these properties are present in all wt.properties files on master and remote sites, but many of the properties are relevant only to master site or remote site servers. Some of the properties control the placement or behavior of log files, which can be important in troubleshooting.
If you have not planned the details of the content replication sites, you may not be able to provide correct values for some properties until you have completed the setup process.
Master and Remote Site Properties
The following table shows the properties that you can set on master sites, remote sites, or both.
Property
Master Site
Remote Site
Description
wt.fv.master.verboseProperties
X
Prints master service properties when the method server starts.
wt.fv.master.verbose
X
Verbose setting for master service. Prints to the method server log file.
wt.fv.purgeNotReplicatedItemOlderThan
X
Specifies the time period for which files that did not replicate properly become unreferenced. The default value is 2 days. Values less than 2 days will be ignored.
wt.fv.master.replicatePrevCleanedObjects
X
If set to false, prevents files that were cleaned up by using the automated cleanup options from being replicated. The default setting is true.
wt.fv.revaultQuerySize
X
Specifies the maximum number of objects to be replicated and retrieved in one query to the database.
wt.fv.replica.verbose
X
Prints replica service properties when the method server starts.
wt.fv.replicationFileSizeThreshold
X
Specifies the minimum file size to be eligible for replication.
wt.fv.master.moveItemsBetweenReplicaVaults
X
X
Specifies one copy of content on remote site.
wt.fv.master.millisecsToWait
X
Specifies the duration of the delay before the master site resends replica configuration information.
wt.fv.master.siteConfigDeliveryAttempts
X
Specifies the number of times the master site attempts to resend the replica configuration information.
wt.fv.master.replicationThreadCount
X
Specifies the number of threads for replication. You can use this property to optimize replication performance for very large data sets. The default value is 1.
The property wt.fv.master.replicationThreadCount controls the number of threads in thread pool and the entries that can be submitted to the thread pool. The maximum entries in thread pool can be twice the threads in thread pool. The thread pool is designed to process the batch and not an individual item. If the items to be replicated are more than wt.fv.revaultQuerySize (default value 1000), then improvement can be seen after increasing number of threads.
* 
The wt.fv.replicationFileSizeThreshold property may not appear in the file, but it nonetheless exists and is effective. For an explanation of this property, see Replication and Windchill Visualization Service.
About the moveItemsBetweenReplicaVaults Property
When content replication is configured, the replication process from the master site to the remote sites is performed in several steps.
Before objects are delivered to the remote sites, the following two queries take place:
• Windchill determines which objects must be moved between replica vaults. Moving objects between replica vaults occurs when:
◦ The corresponding WTObject has been moved from one domain to another.
◦ The life cycle state of the object has changed.
◦ The replication rules have been modified.
• Windchill determines which objects must be replicated from the master site to the remote sites. Only objects that have been replicated are moved. Objects that were created with the preference set to replica are not moved unless they also exist on the master site.
The first query can be very time consuming. You can use the wt.fv.master.moveItemsBetweenReplicaVaults property to disable the first query. If the wt.fv.master.moveItemsBetweenReplicaVaults property is set to true, objects can be copied between vaults on the same remote site. If the target vault is on the same site as the upload vault, the content file is duplicated in the cache vault and not removed unless you reset replication or reset undelivered replication items through the Vault Configuration window. Set this property to false to improve site performance.
* 
PTC recommends one vault per remote site for content replication, and two vaults per remote site for upload caches. Only one vault is actively used at any point in time.
Basic Properties
The following properties affect content replication as well as other functions. (This is in contrast to the properties in the �Master and Remote Site Properties� table above, which have a more limited effect.) For example, the roles of sender and receiver are related to content.
* 
If you are not setting properties through a graphical user interface or in a mapping file, you add or edit properties with the xconfmanager utility. For more information, see Using the xconfmanager Utility.
Property
Sender
Receiver
Explanation
wt.intersvrcom.security.charsetForSigning
X
X
Specifies the character set to be used for signing URLs with non-ASCII characters in a cross-platform environment. The recommended value is ISO-8859-1.
This property applies only in a cross-platform environment, such as when some of the nodes in a cluster or the master and remote sites are on different operating systems. PTC does not recommend using a cross-platform environment.
wt.intersvrcom.security.graceTimePeriod
X
X
If the difference between the time that the URL is signed at the sender site and the time that it is received at the receiver site is more than the number of seconds set in this property, the signed URL will be invalid. The default value is 300 (seconds).
* 
To limit potential security risks, PTC recommends that you configure the default timeout setting to the minimum required to complete download requests. You can determine the minimum value by analyzing the data size of the download requests and the potential network latency considerations.
wt.intersvrcom.security.URLAuthentication
X
X
The default setting is true. Do not set to false unless the system is in debug mode.
wt.intersvrcom.security.useProxyForClients
X
The default setting is true. This value must be set to true if the sender connects to the internet through a proxy.
wt.intersvrcom.ultraLight
X
X
Set during the installation process; do not alter. The default setting is false.
wt.intersvrcom.verbose
X
X
Set during the installation process; do not alter. The default setting is false.
wt.wrmf.verbose
X
The default setting is false.
wt.wrmf.delivery.deleteDeliveredItem
X
If set to true, all delivered shipping objects are deleted from the database. The default setting is true.
wt.wrmf.transport.httptransport.supportInterruption
X
If set to true, upload or download processes resume the HTTP connection that was interrupted due to an IOException, such a temporary network problem. This is useful for uploading or downloading large content files. The default setting is true.
wt.wrmf.transport.outbox.pipe.<1, 2, or 3>
X
Sets a transportation type. See this property in the wt.properties file for the values that you can set.
wt.wrmf.delivery.TrackingNumberGenerator
X
Used internally by the WRMF package.