Skip to main content
Archived

Desktop to Server: Workspace/transformer batched publishing tool

Related products:FME Flow
  • February 21, 2016
  • 1 reply
  • 8 views

geosander

I'm proposing a tool/wizard that could publish a whole bunch of workspaces and/or custom transformers to FME Server at once. This could be a separate tool, but it could also be integrated into FME Workbench. Preferably though, it would be a standalone application that also accepts a command line. This way, you can hook it up to a SVN/Git repository for instance, so whenever you commit, all the stuff you created also gets published to the desired repository on FME Server.

It would be nice if this tool had a "recursive" option, so that it checks if custom transformers contain some other custom transformers and publish these "dependencies" as well. Right now, FME does warn me for missing transformers whenever I publish, but it doesn't check inside these transformers.

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

geosander
Forum|alt.badge.img+7
  • Author
  • February 21, 2016

I'm specifically asking for this, because I have a lot of custom transformers that belong to a bunch of workspaces that share the same environment/repository.

 

For some reason, whenever I publish a workspace from FME Desktop and tell it to copy a bunch of custom transformers into the same repository, only the workspace gets published. The transformers are only copied to FME Server if I store them as a Resource (e.g. Engine > Transformers). This is not what I want, because then all repositories (e.g. development, production) use the same custom transformers (yes, I could use different transformer versions, but that is more difficult to manage). The only way to make sure that they end up in the proper repository now, is by publishing each custom transformer 1 by 1 - which is a rather tedious exercise...

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