Which of these is not one of the three core capabilities of FME Server?
Automation
Real-time
NoSQL Database
Self-serve
FME Server is many things - but it is not a NoSQL database!
I have a Server with two engines. Four users submit jobs at the same time. What happens?
Two jobs are processed. Two jobs are returned to their authors.
Two extra engines will fire up automatically to process all four jobs.
The four jobs will be processed simultaneously, sharing the two engines.
Two jobs are processed. The other two sit in a queue until an engine becomes free.
Yes, the server core keeps a queue of jobs and submits them as engines become available. Extra engines will not fire up, even if you do have spare licenses, and jobs will never be ignored just because no engine is currently available.
If I wanted to find out about workspaces stored in a repository - for example I'm building a tool to catalogue my workspaces - what is the best way to do it?
Use the FME Server REST API
Scrape the contents of the Server repository page
Get a file listing from the repository folder
Connect to the FME Server database to query it directly
The REST API is a quick, simple, and official method to query the workspace repositories. Querying the database directly is permissible, however, under no circumstances should you write into or update directly the contents of the database.
Which of these are good reasons for running engines on multiple operating systems at the same time? Pick all that apply.
A required format is only available on 32-bit or 64-bit, not both.
A required format is only available on Windows, or Linux, not both.
FME Desktop users author workspaces using a mix of Windows, Linux, and Mac platforms.
You want to process heavy-scale jobs on a more powerful platform.
Basically some formats are only available on certain platforms and so you may need to mix of operating systems to cover all your requirements. You may also want to redirect large-scale jobs to a more powerful platform. However, it doesn't matter what platform the workspace author used; their jobs will run on whatever system FME Server is based on.
A Project can be shared only in the following circumstances:
You must own the Project. Only the Project owner can share it.
You must be a user with permission to manage security. Only such a user can share a Project.
You can own the Project OR be a user with permission to manage security (i.e. you can be one or the other).
You cannot share a project once it has been imported to FME Server.
If you own the Project then you can share it. But if you have permission to manage security, then you can share any Project.
If you choose to export a Project to a Resources folder (rather than download it) then what additional capability do you gain?
The ability to trigger a notification topic on completion of the export.
The ability to export the FME license for the server.
The ability to remove all components of the project as they are exported.
The ability to change ownership of the components to your own user account.
When you choose to export to Resources, you'll see a Notification panel at the bottom of the export settings page. You can use that to select a topic to notify if the export succeeds or fails.
Checking the box to remove the contents of a Project removes all of the project components:
True
False
A Project can contain users and roles. The remove tool won't remove the user carrying out the removal, nor will it remove any role for which that user is part of. Also it won't remove components you don't have permission to remove.