span8
span4
span8
span4
Ideabysander··workspacesFME Servercustom transformersworkbench
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.
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 samerepository, only the workspace gets published.The transformers are only copied to FME Server if I store them as aResource(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...
Share your great idea, or help out by voting for other people's ideas.
View a snapshot of a workspace from FME Server
Activity log | audit trail | activity history | traceability
Drag and drop workspaces between folders
Ability to Mount S3 Bucket as a Drive from Within FME Server Resources
Configure a global / system wide running job expiry time for all jobs
Configure a set running job expiry time for each workspace (vs.each run/scheduled job)
© 2020 Safe Software Inc |Legal