Skip to main content
Solved

file copy zip

  • November 13, 2014
  • 1 reply
  • 21 views

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

Best answer by takashi

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
View original
Did this help you find an answer to your question?
This post is closed to further activity.
It may be a question with a best answer, an implemented idea, or just a post needing no comment.
If you have a follow-up or related question, 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

takashi
Influencer
  • Best Answer
  • November 13, 2014
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

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings