Can I control the directories FME uses for temporary files
From Fmepedia
 |
Archive Material This section contains information from an older set of FAQs that has been deemed useful enough to be retained. |
(Note: This information has been more recently presented on this page).
Depending on the factories, input, and output formats involved, FME may create temporary disk files to cache some results as it does its processing. For example, the ReferenceFactory caches "Referencees" to disk until they are needed, the ClippingFactory caches "clippee" features until the clipper arrives, and design file output caches features when computing optimal seed file parameters.
In any case, these files can sometimes grow quite large. You may want to control the directory where these files are created if the default location is tight on disk space. FME decides which directory to use based on these environment variables (in the order shown):
- FME_TEMP
- TEMP
First, FME_TEMP is checked. If it is not present, then TEMP is used. If either environment variable is set, its value is taken as the name of the temporary directory to use for temporary files that FME may create during its run. If neither is set, the C:\temp is used on Windows systems, and /tmp is used on UNIX systems.
The FMEGUI creates temporary mapping files in the directory pointed to by the TEMP environment variable, if set. Otherwise, C:\temp is used.
If anyone is using the SAIF format, this format behaves differently (for historical reasons). SAIF also uses temporary files as it reads/writes, but that module uses the environment variables...
- STK_TMPDIR
- TMPDIR
...in the order shown to figure out what temporary directories the SAIF writer/reader will use when they run.
