Enhancing the File Server User Experience
The following functions help with the user experience when the File Servers are configured and in use:
• Site Monitor—This is a daemon thread which, at Windchill-defined intervals, pings all File Server sites and holds the ping status in the master site. The following property specifies the interval between each replica ping:
wt.intersvrcom.sitePingIntervalInMinutes
The monitor is present on every method server on the system, and the result of each ping is stored in the cache. Method servers check the ping results before each attempt to ping the File Server sites. If the existing pings are recent enough, they skip the next ping.
• Automatic Mount Validation—This feature, similar to Site Monitor, validates mounts by folder, file, or site. It enables mount validation in clustered environments and on File Server sites.
You can also validate a mount through the Vault Configuration window by selecting an object, such as site, vault, or folder, from the tree in the left pane and then clicking Validate.
|
|
If there is at least one mount that has not been created yet, a warning message appears.
|
When you validate a mount from the Vault Configuration window, the system does the following:
1. The system sends all of the data needed for the mount validation to the File Server site.
2. The system on the File Server site validates all of the existing mounts related to the selected object.
3. The system sends the validation status to the master site.
4. The system on the master site updates the status of all the mounts related to the selected object to Valid or Does not exist.
5. The system updates the Last Status Update Time timestamp for all the mounts related to the selected object.
• Manage quarantined files—You can identify quarantined files, remove files from quarantine, and manage the frequency of quarantine notifications.
Any content that Windchill deems corrupted is marked as quarantined. Quarantined content is content that Windchill has found to be corrupted or defective in some way. This content cannot participate in revaulting or replication until it is removed from quarantine.
For quarantined objects, the folder must be accessible; it is not necessary for the content to be accessible. This helps to avoid quarantining files for folders that are not mounted. When revaulting and replication process take place, quarantined objects are automatically filtered out and not included in the process.
The dedicated property wt.content.QuarantinedContentManager collects data about currently quarantined files or removes a subset of these files from the quarantine.
To generate reports for all quarantined content in the system and store them in a file, use the following command:
java wt.content.QuarantinedContentManager [-reportAllQuarantined][<file>]
To remove the quarantine flag from all content that is currently in quarantine, use the following command:
java wt.content.QuarantinedContentManager [-UnQuarantineAll]
A separate log is also created with a record for each quarantined file. This log includes details about why each object is quarantined.
Windchill administrators can sign up for email notification of quarantined content. The wt.content.QuarantineNotifyIntervalHours property specifies the interval, in hours, at which an administrators who subscribe to the JMX quarantine notification receive a notification of content quarantine events. The default value is 24 hours, which means that a notification about quarantine events is sent out, at most, once in a 24-hour period. If you set the value of this property to 0, a notification is sent out for each quarantined event.
