Skip to main content
Question

Removing an FME Server resource folder


dms2
Contributor
Forum|alt.badge.img+11
  • Contributor

Hi.

I added 2 new resource folders to FME Server 2020. I simply defined the shared resources by adding the corresponding lines to fmeServerConfig.txt and FmeEngineConfig.txt files, restarted FME Server services and voilà.

Now I need to remove one of these resources from FME Server but removing them from the config files and restarting FME Server takes no effect. It still appears in the resource list.

Did I miss any step? Is there anything else I should do?

Thanks!

9 replies

david_r
Evangelist
  • May 19, 2020

Out of curiosity, why was it necessary to manually add the resources in the configuration files, rather than in the GUI?

Did you try removing the resources in the FME Server GUI as well?


dms2
Contributor
Forum|alt.badge.img+11
  • Author
  • Contributor
  • May 19, 2020
david_r wrote:

Out of curiosity, why was it necessary to manually add the resources in the configuration files, rather than in the GUI?

Did you try removing the resources in the FME Server GUI as well?

We prefer having this kind of customizations stored in a file. And also this way new resources are like any other 'system' resource, not editable nor removable, so you cannot 'mistakenly' remove the resource in the GUI.

So using the GUI to remove the resource is not an option.

 


david_r
Evangelist
  • May 19, 2020
dms2 wrote:

We prefer having this kind of customizations stored in a file. And also this way new resources are like any other 'system' resource, not editable nor removable, so you cannot 'mistakenly' remove the resource in the GUI.

So using the GUI to remove the resource is not an option.

 

Interesting arguments, thanks for sharing!


david_r
Evangelist
  • May 19, 2020

My hunch would be stale records in the system database, in particular look in following 3 tables in the FME Server database:

  • fme_sharedres
  • fme_sharedres_type
  • fme_sharedres_props

roberto
Contributor
Forum|alt.badge.img+6
  • Contributor
  • November 14, 2020
david_r wrote:

My hunch would be stale records in the system database, in particular look in following 3 tables in the FME Server database:

  • fme_sharedres
  • fme_sharedres_type
  • fme_sharedres_props

Hi @david_r​ ,

I also faced the same issue. I found two records in the pstgresql db related to a resource that, removed from the fmeserverconfig file, still exists in the GUI. Is it safe to delete the two records (fme_sharedres and fme_sharedres_props tables)? We are working with configuration file instead of GUI because in the 2020.1 we found a bug that makes not possible to display files content.

Thanks!

 


david_r
Evangelist
  • November 16, 2020
roberto wrote:

Hi @david_r​ ,

I also faced the same issue. I found two records in the pstgresql db related to a resource that, removed from the fmeserverconfig file, still exists in the GUI. Is it safe to delete the two records (fme_sharedres and fme_sharedres_props tables)? We are working with configuration file instead of GUI because in the 2020.1 we found a bug that makes not possible to display files content.

Thanks!

 

It's impossible for me to say, unfortunately, it's a bit of a black box. Once you're manually manipulating these tables all bets are off.

I recommend you do a complete backup of the the entire FME Server installation before touching the contents, just in case.


roberto
Contributor
Forum|alt.badge.img+6
  • Contributor
  • November 16, 2020
roberto wrote:

Hi @david_r​ ,

I also faced the same issue. I found two records in the pstgresql db related to a resource that, removed from the fmeserverconfig file, still exists in the GUI. Is it safe to delete the two records (fme_sharedres and fme_sharedres_props tables)? We are working with configuration file instead of GUI because in the 2020.1 we found a bug that makes not possible to display files content.

Thanks!

 

Thanks. Sure a complete backup is a good suggestion. I hope the bug will be solved soon in order to avoid working on the fmeserverconfig file.

regards

Roberto


afavaccio
Forum|alt.badge.img+2
  • November 17, 2020

Another workaround is to update the 'is updatable' field to true in the FME Server database "fme_sharedres" table and then delete the shared resource from Web UI.

Of course as david_r said do a complete backup before proceding.


roberto
Contributor
Forum|alt.badge.img+6
  • Contributor
  • November 17, 2020
afavaccio wrote:

Another workaround is to update the 'is updatable' field to true in the FME Server database "fme_sharedres" table and then delete the shared resource from Web UI.

Of course as david_r said do a complete backup before proceding.

Thanks @afavaccio​ ,

it works and resource can then be removed from the GUI.


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