finding the actual output filename of printmap function
this is the url that is displayed when the user opened a pdf created from the printmap workflow, but i do not think this is the actual file that can be attached to an email. Where and how do I determine what the actual path to the output file is so I can attach it to an email. email?
Jeff
-
Jeff,
I had a similar issue when trying to present my GPService with a file to be used in a model on my GP Server. The "Create Temp File" activity creates a .DAT file in a hidden folder on your C:\ called C:\ProgramData\Latitude Geographics\Temp . It then uses a GUID system to create essentially job folders, which store references to these DAT files that contain the data of the file itself. My GP service was looking for a reference to a GPX file, but since the URL doesn't actually contain the link to the file itself, my GPService was failing. I don't think I got an answer in that thread, so I had to move on to plan B.
Instead of using the Create Temp File activity, I used the "Write File" activity and had it write to a location that had write permissions for the "Essentials" user and was a virtual directory, so that it could be accessed on the web. In this case, I used the Resources folder of my Site/Viewer C:\Program Files (x86)\Latitude Geographics\Geocortex Essentials\[your instance]\REST Elements\Sites\[your site]\Viewers\[your viewer]\VirtualDirectory\Resources\ . This is not ideal, because it's not "managed", however it is the virtual directory for your viewer and does give web access to files stored on your Essentials server. I have yet to set up an event to delete these files after a period of time. This could be done by a scheduled task, etc.
I'm sure I left out some key details on the inner workings of the Essentials temp files. Maybe someone can better explain how this process works, so I can go back to using temp files for use in my GP service URL.
0 -
Hi All,
Erik's description of the Temp Files directory is pretty accurate. I would caution anyone from actually trying to access the content of this directory programmatically or from a workflow. The inner workings of Temp Files is an internal concern of the software. We may chose to to alter the structure of the ProgramData folder (we've done this a few times in the past). Also in a distributed deployment of Essentials this directory is only present on the AppplicationServices machine. The only supported/reliable way to access these temp files is via the URL.
If you need to access a temp file (for example: to include it as an email attachment) you can use the Web Request activity to download it and get the bytes.
--Ryan
0 -
yes - it was to tricky for me, so i just email them the link and they can bring it up easy enough. thats easier to do and I don't have to write custom code.
J
0
Please sign in to leave a comment.
Comments
3 comments