Skip to main content
Solved

FME_SERVER_DEST_DIR

  • January 17, 2014
  • 1 reply
  • 103 views
tino
Supporter
Forum|alt.badge.img+26
Hi,

 

 

i just noticed that if i have more than one writer in my workspace and choose only the output of one for the DataDownload- or DataStreaming-Service only this output gets written to FME_SERVER_DEST_DIR. The other writers write their output to the default, in the workspace file configured path.

 

How do I avoid conflicting file access with concurrent user session for such a workspace?

 

I need a unique filepath for a temporary file in my workspace which should not be included in the download/streaming output. I could use a private python parameter which generates a filename (e.g. with a timestamp) or i could perhaps utilize the UUIDGenerator to achive unique filenames...

 

Or I could use the FME_SERVER_DEST_DIR parameter and extract the unique part of it to use it e.g. in %TEMP%.

 

 

But perhaps FME Server has some variable/function i could use directly?

Best answer by kathyross

I'd recommend a combination of a Timestamper and RandomNumberGenerator transformer for forward compatibility purposes in case in future FME Server releases the variable / function (if such exists) changes name.
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

1 reply

K
Forum|alt.badge.img+4
  • kathyross
  • Best Answer
  • February 3, 2014
I'd recommend a combination of a Timestamper and RandomNumberGenerator transformer for forward compatibility purposes in case in future FME Server releases the variable / function (if such exists) changes name.

Community Stats

32,154
Posts
122,043
Replies
39,812
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.