Reply to: How to prevent DITA-OT copy to user directory?February 5, 2009 at 12:37 am
You can do this by changing the following file:
That file should contain the following setting:
dita_ot_per_user_version = 1
Changing the value to any higher value than the current one will cause the DITA OT to be redeployed the next time output is generated.
So, because you are deploying new files already you should be able to include an updated copy of this file in your manifest. To remove the need to keep track of the last value I would suggest using the date in the form yyyymmdd (or if you plan to do more than one deployment per day you might include the time as well: yyyymmddHHmm). Note that this value is treated simply as an integer to compare with the previous integer and is not an actual date, so pick your format beforehand and stick to it. You could also simply use 1, 2, 3, if you don't mind keeping track of that.
I'm attaching a screenshot of what the user will see if you change the value to 20090121.
Making XMetaL Author Enterprise compatible with Vista forced us to make some changes. In 5.1 and earlier we deployed and ran the DITA OT inside Program Files. On Vista by default (and for Limited Users on XP) this folder is locked down tightly. Once a product has been installed it should not write anything to this folder and the DITA OT writes inside its own sub folders. So, we still install to Program Files, but the first time you generate output a copy of the DITA OT is deployed to the current Windows user's per-user folder (which can be in various locations depending on your version of Windows and how your IT people have set things up). This also means that IT staff (network admins) can deploy XMetaL Author Enterprise once on a machine (for all users) while different users that log into that same physical computer will each have their own separate copy of the DITA OT automatically deployed.