Hello @Lars I Nielsen​ ,

This is a new option in FME Server 2021+ for managing FME Server engines and queues.

Engines can now be assigned to queues based on either engine properties or engine names. Engine properties by default are the OS, the build of the FME Server, the license type, etc. Users are also able to add their own engine properties. When an FME Engine connects to FME Server, it reports information to the FME Server Core and that’s what we see exposed here.

I don't believe these system-created properties can be deleted from the FME Server Web UI.

Please see our blog for an introduction to Analyzing Job Statistics in FME Server. A tutorial series on Queue Control will also be available online in the near future.

@Lars I Nielsen​ - Could you please elaborate on why you would like to delete them? Is it just a part of clean-up since you do not use them at all or do you have any other concerns? The engine properties are only used in queue control and are not involved in any other FME Server operation.

In general, I don't want a lot of automatically added information cluttering up the interface. It's unnecessary and confusing. That's why I want to delete the unnecessary tags, like "version", "os" and "server name".

I get how assigning specific repositories to specific queues is beneficial, and how "free" queues can be used to cater for special circumstances, but I cannot fathom how the new "properties" are to be used.

Apparently I can create a new "custom property" (in "engine assignment"), but what is it good for ?

And what are the differences in usage between "job routing" and "engine assignment" ? They seem to facilitate the same, but are still somewhat different.

Are the any good examples available ?

Thanks for providing the reason for deleting these engine properties. At this point, these system-created properties cannot be deleted from the FME Server Web UI.

Please see this document for an introduction to queue control -http://docs.safe.com/fme/2021.0/html/FME_Server_Documentation/WebUI/Queue-Control.htm

When creating a new Engine Assignment Rule Property, if Engine Property "Custom" is specified, you can enter a Property exactly as it appears on the Engines page sthe system-created properties]. You can then create a rule with this custom property as it would then become available as a choice in the "Rule" drop-down. For example, to specify any dynamic engine on a server called "WHISTLER" (a Custom property), create a rule as Dynamic AND "WHISTLER".

I also found this Safe Software webinar that might be helpful to understand the queue control components - https://www.safe.com/webinars/fme-server-2021-0-at-scale-advanced-job-control/

On the "Table of content" on the demo page, you can go to "Advanced job control" to jump to the demos.

We do have a detailed tutorial series on Queue Contol coming up soon.

Thanks for the link, I'll look into it asap.

A quick question though: Creating a custom property named "WHISTLER" automagically ties this property to a server called "WHISTLER" ?

Yes, I believe it should work if the custom property created [in this case WHISTLER] is exactly as the engine properties appear on the Engines page. So for your case, you should be able to create custom properties like "22434", "WIN64" and "FME-SERVER003_Engine1"