+11Hi.
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!
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?
+11Out 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.
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!
My hunch would be stale records in the system database, in particular look in following 3 tables in the FME Server database:
+6My hunch would be stale records in the system database, in particular look in following 3 tables in the FME Server database:
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!
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.
+6Hi @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
+2Another 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.
+6Another 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.
