I created a process to rename and resize jpgs in workbench, and able to select multiple jpgs or directory to run my process, but I am not able to make the process do this when I upload to FME server.
Thanks,
Chad
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, 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.
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.
@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.