Skip to main content
Solved

Can we place workspaces directly into the repository directory instead of publishing to server

  • February 18, 2020
  • 3 replies
  • 19 views

nag
Contributor
Forum|alt.badge.img
  • Contributor
  • 41 replies

Hello Team,

Can we place workspaces directly into the repository directory instead of publishing to server? I tried doing this but workbenches were not reflecting in the server. Can somebody clarify whether the process i followed was correct? If yes then why newly placed workbeches are not reflecting in the server?

Thanks in advance...

Best answer by david_r

Simply replacing an existing .fmw file in the repository directory should work, but of course only for non-running instances of the workspace (do be careful about circumventing the publishing wizard, however, as it does quite a few things for you to assure that the workspace runs smoothly on the server).

You cannot add a new workspace to FME Server this way, however, since simply copying the workspace into the folders doesn't create the necessary entries in the internal database. It is necessary to use the publishing wizard the first time.

Starting with FME Server 2020 you will be able to drag-and-drop new or replacement workspaces directly into the FME Server GUI.

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.

3 replies

david_r
Celebrity
  • 8392 replies
  • Best Answer
  • February 18, 2020

Simply replacing an existing .fmw file in the repository directory should work, but of course only for non-running instances of the workspace (do be careful about circumventing the publishing wizard, however, as it does quite a few things for you to assure that the workspace runs smoothly on the server).

You cannot add a new workspace to FME Server this way, however, since simply copying the workspace into the folders doesn't create the necessary entries in the internal database. It is necessary to use the publishing wizard the first time.

Starting with FME Server 2020 you will be able to drag-and-drop new or replacement workspaces directly into the FME Server GUI.


nag
Contributor
Forum|alt.badge.img
  • Author
  • Contributor
  • 41 replies
  • February 18, 2020

Simply replacing an existing .fmw file in the repository directory should work, but of course only for non-running instances of the workspace (do be careful about circumventing the publishing wizard, however, as it does quite a few things for you to assure that the workspace runs smoothly on the server).

You cannot add a new workspace to FME Server this way, however, since simply copying the workspace into the folders doesn't create the necessary entries in the internal database. It is necessary to use the publishing wizard the first time.

Starting with FME Server 2020 you will be able to drag-and-drop new or replacement workspaces directly into the FME Server GUI.

Thank you for the information @david_r


Forum|alt.badge.img+2
  • 364 replies
  • February 19, 2020

Thank you for the information @david_r

Hi @nag,

 

 

@david_r is correct, the publish wizard will be registering the workspace and any auxiliary components with FME Server and the database so that it can run correctly, so adding a workspace to a repository won't work.

 

 

Replacing an existing .fmw is what the fme engine will run at runtime, however I do not recommend this and if there were issues running it on fme server we (support) would require you to publish using the wizard. Any changes to the workspace that would change how FME Server interacts with the workspace: connections, parameters, custom transformers etc could likely not work correctly from just copy + pasting an updated workspace.