I am also trying to carry over jpeg attributes to a jpeg writer.
Chad
In order to help you, a little more information about what exactly is not working when you put it on the server would help.
I need to be able to have the published parameter able to select multiple files at one time. When I upload the process to server you can only select one file at a time. In workbench you can select multiple files at once. I was also wanting to see if it is possible to attach the attributes of the source jpeg (it has original data, camera make and model, etc). FME reads the attributes I attach to writer but it will not write them out.
Chad
They would upload them manually, as needed. It is set up as a user paramter.
CK
@tbs_gis_team, I believe I am having the similar question. Did you ever find a solution?
It is possible to zip the files before uploading to FMEserver. However, that is not ideal in my situation, dynamically zipping up files in a web application is a bit problematic and time consuming...
Hi, why not use the Directory watch publication protocol on a resource location or a network location? this way uploading the files is just a matter of copying them.
Hi, why not use the Directory watch publication protocol on a resource location or a network location? this way uploading the files is just a matter of copying them.
Great idea, @itay! I think we can write a service for uploading file to a resource location where the directory watch publisher will trigger the workspace that transforms the data to the back-end database.
Great idea, @itay! I think we can write a service for uploading file to a resource location where the directory watch publisher will trigger the workspace that transforms the data to the back-end database.
Just be aware that the directory watcher (depending on the fme server) has done known issues and most of the times an inetrmediate filtering step is necessary.