Skip to main content
I have a scenario with 3 chained workspaces on FME Desktop. Ie the user starts workspace 1, which starts workspace 2, which starts workspace 3. Workspace3 uses data (from a large textfile) that is generated in workspace.

 

 

At the end the user gets some files created in workspace 2 (PDF and TXT) and some files generated in workspace 3 (TIF).

 

 

When I try to port this to FMEServer I struggle to send links to the files to download between multiple workspaces. Any workaround to this issue? I can not make 1 workspace instead of 3, due to the fact that I have to process completely different based on the writing to PDF / TXT from workspace 2.
Have you tried what I call the "Dave" method - after Dave Campans who came with it?

 

http://fmepedia.safe.com/articles/How_To/Chain-Jobs-in-FME-Server

 

 

Although I think I understand the problem - you want it all packaged up in one zip file for the file download?
Hi Ken!

 

 

Thanks for the swift reply. Although I though I have watched all the FMEPedia-articles I havent looked at this one. After looking at it shortly it might help me in the right direction.

 

 

A comment to your last paragraph - to clear my goal: There is a mylonglogfile.txt generated when Workspace2 is finished. I want to READ this (by using the AttributeFileReader) in Workspace3. Is this more clear?

 

 

A simplified approach would be:

 

 

Workspace1.fmw:

 

-Creator

 

-AttributeCreator(myParam='hello from WS1')

 

-AttributeFileWriter(myParam, to file mylonglogfile_TODAYSDATEANDTIME_UNIQUE.txt)

 

-Workspacerunner(Worspace2.fmw)

 

 

Workspace2.fmw

 

-Creator

 

-AttributeFileReader(mylonglogfile_TODAYSDATEANDTIME_UNIQUE.txt)

 

-CustomTransformerToAddText(replace 'hello from WS1' with "hello from WS2')

 

-WRITER (mylonglogfile_TODAYSDATEANDTIME_UNIQUE.txt) and send link to user
@KenAtSafe Would be nice to have som very complex FMEServer examples on todays and tomorrows Webinar!
I've had success with the "Dave" method (thanks Dave) but it is a nasty thing to manage, trace errors, etc.  A more elegant method would be much appreciated.

 

 

I've found the Recorder and Player transformers useful to pass data between workspaces after the initial read.  I hope that helps.
Thanks Andy!

Reply