Skip to main content
  • EN
Hello,

 

 

I have following situation:

 

- Master workspace A (including 1 FMEServerJobSubmitter for Workspace B)

 

- Workspace B containing a linked custom transformer

 

 

Workspace B generates the actual output (GML). The output location can not be defined by me because of a known issue (decision of Safe). Workspace A moves the data from the default location (based on attribute output_datasets{}.path) to the desired location. When doing this I would also like to zip the GML file.

 

This is possible when the Destination File Copy Directory is like ...\\result.zip

 

Both the actual output name should be set by an attribute like ...\\attributA.zip

 

In order to do that I create attributes filecopy_source_dataset, filecopy_dest_Dataset and filecopy_dest_filename

 

But by doing this, the created zip file is corrupt.It seems that just the extention "zip" is added but the data is not zipped.

 

 

Is there a way to move and zip a file and define the zip name based on an attribute?

 

 

Thanks,

 

Rob
Hi Rob,

 

 

I encountered a similar situation a few months ago. I had thought the zip archiving could be controlled with filecopy_dest_dataset, but it didn't work in fact.

 

At that time, I created another workspace having a WorkspaceRunner as a workaround.

 

The workspace does:

 

- create a dataset path ending with ".zip" based on a feature attribute value,

 

- pass it to the "Destination File Copy Directory" parameter of the File Copy writer in the main workspace, through the WorkspaceRunner.

 

FYI.

 

 

Takashi

Reply


Community Stats

30,108
Posts
114,295
Replies
37,744
Members
Terms & ConditionsCookie settings
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.