When one user checks out an element in Composer, that element is locked and cannot be edited by any other user. If that user has left the company or is out of the office and won't be back for some time, you may need to break that user's lock to regain control of the element.
Perhaps highly structured files, binary files, are candidates for this. In some situations, customers have mentioned the desire to "lock" a configuration file or certain properties files or xml files for tomcat, web servers and application servers to keep most users that work in the stream from changing these.
Unless Tracker is updated with valid license information or the evaluation period is extended, Tracker need to be uninstall and the machine need to be rebooted to get the Unlock functionality in Version Manager back. Attach Vantive defect number #1036137 for new cases.
This was solved by doing this: "open $DM_ROOT/webtools/tomcat/webapps/dimensions/WEB-INF/web. xml and reset the following: param-name "enable_fileops_if_no_metadata", param-value "true and restart Tomcat" What is the role/meaning/definition of the parm "enable_fileops_if_no_metadata"?
