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.
3. Edit this file using either Notepad, Notepad ++, or an XML editor. 4. Locate the following section: <parameter name="PasswordResetURL" Type="xsd:anyURI">Caution-http://localhost/tmtrack/tmtrack.dll?LoginPage&Template=loginreset</parameter>
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"?
