Skip to main content
Solved

Is there a way I can publish multiple workbenches on FME server

  • September 3, 2019
  • 7 replies
  • 100 views

Is there a way I can publish multiple workbenches on FME server

Best answer by nic_ran

As itay and oscard have both mentioned, the FME Server REST API allows you to publish workspaces but you do need to have an understanding of all the requirements for publishing a workspace (such as registering services, etc.).

If you're not familiar with the intricacies of publishing a workspace to Server, then I'd suggest just using Workbench and publishing one at a time. If you have other requirements (such as automated deployment in a DEV environment), then looking into the REST API capabilities might be worthwhile.

If your requirement is to push multiple workspaces between FME Server environments (e.g. dev -> prod) then you should look at FME Server Projects.

Nic

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.

7 replies

oscard
Influencer
Forum|alt.badge.img+22
  • Influencer
  • 344 replies
  • September 3, 2019

Maybe using the API?

 

 

https://docs.safe.com/fme/html/FME_REST/apidoc/v3/index.html#

 

 

No idea if there is a method for what you are asking, though.

itay
Supporter
Forum|alt.badge.img+18
  • Supporter
  • 1442 replies
  • September 3, 2019

I agree with @oscard, the API is the way to go. You can create repositories and upload specific workspaces into them.


nic_ran
Contributor
Forum|alt.badge.img+16
  • Contributor
  • 218 replies
  • Best Answer
  • September 4, 2019

As itay and oscard have both mentioned, the FME Server REST API allows you to publish workspaces but you do need to have an understanding of all the requirements for publishing a workspace (such as registering services, etc.).

If you're not familiar with the intricacies of publishing a workspace to Server, then I'd suggest just using Workbench and publishing one at a time. If you have other requirements (such as automated deployment in a DEV environment), then looking into the REST API capabilities might be worthwhile.

If your requirement is to push multiple workspaces between FME Server environments (e.g. dev -> prod) then you should look at FME Server Projects.

Nic


david_r
Celebrity
  • 8394 replies
  • September 5, 2019

Maybe using the API?

 

 

https://docs.safe.com/fme/html/FME_REST/apidoc/v3/index.html#

 

 

No idea if there is a method for what you are asking, though.

I agree, but just know that this solution isn't encouraged / offically supported by Safe, as the publishing wizard in FME Desktop apparently does quite a few things in addition to just pushing the workspace to the API.


itay
Supporter
Forum|alt.badge.img+18
  • Supporter
  • 1442 replies
  • September 5, 2019

I agree, but just know that this solution isn't encouraged / offically supported by Safe, as the publishing wizard in FME Desktop apparently does quite a few things in addition to just pushing the workspace to the API.

true, but its just a matter of understanding the extra steps needed to register the workspaces to a service and security issues.

I have migrated a couple of hundreds workspaces that way without too much issues.


runneals
Supporter
Forum|alt.badge.img+28
  • Supporter
  • 322 replies
  • September 5, 2019

true, but its just a matter of understanding the extra steps needed to register the workspaces to a service and security issues.

I have migrated a couple of hundreds workspaces that way without too much issues.

Then there's always the fact that since it's not documented/supported, that it can change version to version, but I suspect that it wouldn't be very likely to as it's pretty important functionality


  • Author
  • 1 reply
  • September 8, 2019

Thanks for the input, I will check and get back.