Questions
Here are the answers to the questions in this chapter.
| Miss Vector says... |
|
Hi, I'm Miss Vector, FME schoolteacher. I'll be here now and then to test you on your new FME Server knowledge. For now, answer me this: Which of these is not one of the three core capabilities of FME Server?
1. Automation 2. Real-Time 3. NoSQL Database 4. Self-Serve FME Server is many things - but it is not a NoSQL database! |
| Miss Vector says... |
|
I have an FME Server with two engines. Four users submit jobs at the same time. What happens?
1. Two jobs are processed. Two jobs are returned to their authors. 2. Two extra engines will fire up automatically to process all four jobs. 3. The four jobs will be processed simultaneously, sharing the two engines. 4. 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. |
| Miss Vector says... |
|
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?
1. Use the FME Server REST API 2. Scrape the contents of the Server repository page 3. Get a file listing from the repository folder 4. 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. |
| Miss Vector says... |
|
Which of these are good reasons for running engines on multiple operating systems at the same time? Pick all that apply.
1. A required format is only available on 32-bit or 64-bit, not both. 2. A required format is only available on Windows, or Linux, not both. 3. FME Desktop users author workspaces using a mix of Windows, Linux, and Mac platforms 4. 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. |
| Miss Vector says... |
|
I copy a workspace into a resources folder using the upload tool. What then?
1. I can run it by browsing the resources, selecting the workspace, and clicking run 2. I can run it through the Manage > Workspaces menu tools 3. I can run it by calling it with the FMEServerJobSubmitter transformer in FME Desktop 4. I can't run it because it's not properly published to a repository Basically, if you don't publish the workspace properly, you aren't able to have Server run it. |
| Miss Vector says... |
|
Uploading an entire folder of files come with what restriction?
1. Folder upload only works on certain web browsers 2. Folder upload requires the folders to be zipped into a single file 3. Folder upload only works on Windows C: drive (not D:, E:, etc) 4. Folder upload requires FME Desktop to be installed on the computer being uploaded from Folder upload works in Chrome, but not in Firefox, Internet Explorer, or any other web browser. |
| Miss Vector says... |
|
What exactly are the entries in the resources cleanup dialog?
1. They are simply shortcuts to workspaces in the utilities category that I can run on demand 2. They are simply shortcuts to scheduling tasks that run at the described interval 3. They are specific tasks that FME Server runs once a day to help in system maintenance 4. They are specific tasks triggered when the system is low on resources These are their own set of tasks, separate to anything defined as a schedule or utility workspace. They are run once a day and remove any specified file older than the set time. However, #4 is partially correct. When the system's free disk space reaches specified minimum levels, FME Server will trigger a critical level cleanup event, in which all enabled cleanup tasks execute; the difference being it will disregard the Remove Files Older Than setting. |
| Miss Vector says... |
|
If I want one user to have a higher level of access to other users in the same role (say I wish to let an FME author be able to manage engines) what must I do?
1. Simply select that user from the user list and set the manage engine policy to yes 2. Promote that role to superuser status so that the user has a higher level of security 3. Create a new role with manage engines = yes and move that user to it 4. Create a new role with manage engines = yes and add that user to it as well as the original role Security policy is set per role, not per user. You could create a new role (AuthorsWithEngines?) and move that user to it, but - and this is the point - a user can have multiple roles. Our author can remain in the author role, but also be assigned to a new role that allows engine management. |