When testng UD6/CMtool Driver with eChange Man the following problems were observed, that we were unable to find reference to in the associated manuals.
Must re-boot server after installation
Scripts are not run if code is checked from Development into Production using Send Home, and the code had not changed. This leads to extraneous records in the INUSE file that need to be manually removed. March Hare do not consider this a major problem since we would expect users to usually promote from Development to QA, which will correct the INUSE file records (by placing a script in the QA Area)
XML files are not removed from an area if a script is run, but the script cannot remove the file itself. March Hare do not consider this a major problem since as long as the inuse file is updated the extra files will be ignored. When the same file is demoted to development at a later point, eChange Man gives the user the ability to overwrite the old file.
If you double click on an XML file when Internet Explorer 5 is installed, eChange Man opens up IE5 to display the file. Unfortunately it copies the file to the TEMP directory to display it. In the XML file, the references to the stylesheet are relative to its current location. This in turn means that IE5 cannot find the stylesheet, so it fails to display it.
To resolve this issue, first double click on the XSL file (e.g.: components.xsl), then the ud6logo.gif file, then the file that you wish to view. This copies the stylesheet to the temp directory until it is cleared by another process.
