Pages: 1
Author Topic: Avoid / clean temporary folders for remote document customisation  (Read 2233 times)

Posts: 6

« on: February 27, 2015, 10:49:07 AM »

We found out XMetal is creatiing a lot of temporary folder (20 located in user's temporary directory) when loading a document referencing a remote customisation.

These are some details about our context :
- XMetaL Author Enterprise 7 is used
- XML document edited spécify a dct.xsd file in root element
- in the XMETAL catalog file : SYSTEM "dct.xsd" "https://ourserver:443/document/dct.xsd"
- the schema and customisation files associated are located at https://ourserver:443/document/

All the edition and customisation process is working fine but we noticed that many temp directories (sometime 20 per doc, sometime less) are created by Xmetal each time we open one document. For example : [user temp directory]/11916/ourserver/document.

We noticed that these directories are often empty and are not garbaged when exiting Xmetal or closing the doc.
We also that, some user encounter the error message "Unable to save customisation to [directry path]".

Thanks to help us with this point.
« Last Edit: March 01, 2015, 10:17:15 AM by bk » Logged

Posts: 265

« Reply #1 on: March 01, 2015, 12:37:18 PM »

Sounds like it might be your CMS connector that is creating the temp files and not cleaning up.

That being said, here is a similar problem i posted about nearly 4 years ago:,1550.0.html
Derek Read
Program Manager (XMetaL)

Posts: 2621

« Reply #2 on: March 02, 2015, 04:58:48 PM »

If the schema is being hosted on a server and referenced using HTTP or HTTPS it needs to be downloaded to your local machine's drive by XMetaL Author before it is loaded. XMetaL Author functions similarly to a web browser in this case (and it actually uses Windows APIs that are similar) and it places all the downloaded files into your %temp% directory.

There are two options I can think of if you are having issues.

1. Use the standard Windows disk cleanup tool to clean up the temp folder (for all applications) from time to time:

2. Distribute your customizations (XSD + CSS + CTM + MCR and any other files) locally to avoid the need for XMetaL Author to download them from your server each time a document that references them is edited. See the following for details on how XMetaL Author locates schemas and associated customizations:

If a CMS system is being used (as gcrews suggests) and it is designed to work with XMetaL Author Enterprise (through what we call a "connector" and what some CMS vendors refer to as a "bridge") then the CMS will either be designed to distribute the files XMetaL Author Enterprise requires for a particular XML document type to a location XMetaL can find it on your local machine's drive, or the CMS will expect those files to already be in place on the local drive (and essentially do nothing to aid with their deployment). If you are using a CMS check with the vendor for instructions and a description of the expected behaviour.
« Last Edit: March 02, 2015, 05:01:02 PM by Derek Read » Logged
Pages: 1
Jump to: