You can perform the following from the Run Workspace page:
- Run a workspace directly from this page.
- Share a workspace as an "app" that is run from a browser, or as a webhook that is integrated with third-party software.
Note: Workspace templates cannot be run from FME Server.
To Run a Workspace
- The repository to which the workspace belongs.
- The workspace you want to run.
- An FME Server service that the workspace is registered to run.
- Optionally, an e-mail address to deliver results. This option allows you to receive e-mail notification when the translation is complete, rather than wait for a completion message on this page.
Note: To receive e-mail, the following FME Server email subscribers must be properly configured: DataDownload_Email_JobFailure, DataDownload_Email_JobSucess, JobSubmitter_Email_JobFailure, JobSubmitter_Email_JobSuccess. For more information, see Monitoring FME Server Events from Topics.
If any published parameters represent data files, this page allows you to upload files to FME Server, making use of the Data Upload Service behind the scenes. This service works in conjunction with the Data Download, Data Streaming, and Job Submitter services to upload files.
Note: Any "Feature Types to Read" published parameters that contain spaces must be enclosed in double quotes. For example, "Bus Routes".
Note: Resources connections to Amazon Web Services (AWS) S3 buckets cannot be accessed.
Job Queue (optional): The job queue in which to run the job. The specified queue overrides the queue of the repository to which the workspace belongs. If not specified, the job is placed in the job queue of the repository.
Queued Job Expiry Time (optional): The length of time after which a job that is waiting in queue does not execute. If the job does not execute before this time is reached, it remains in the queue until it is ready to execute, but execution is not attempted. This directive is useful for time-sensitive jobs that you do not want to run after the specified time is exceeded.
Running Job Expiry Time (optional): The time a job will remain in the running state. This directive is used to ensure that a job does not hang and block an FME Engine indefinitely. The minimum allowable value is 1.
Run Until Cancelled (optional): If checked, the job runs continuously, even after a server shutdown or crash, until it is explicitly canceled.
- As an "app" that is run from a browser, and allows users to configure any published parameters.
- Through a webhook that can be integrated with third-party software to programmatically run the workspace according to the published parameters configured on the Run Workspace page.
Once created, you can access the token on the API Tokens tab of the Token Management page.
- Click Share this workspace.The Share <repository/workspace> page opens.
- If required, edit the Name, Description, and Expiration of the token.
- User Can Upload: If the workspace uses the Data Upload Service, this setting allows users to upload temporary files that are used to run the workspace.
- Additional Permissions: FME Server generates a token that does not require logging in, and is configured with the minimal set of permissions to run the workspace. However, if this setting appears, other permissions may still be required. You may need to further test and adjust the given permissions.
- Access: Access the Jobs page to view the jobs you have run, or cancel any of your jobs that are currently running or in queue.
- Manage: Access and manage the jobs of all users. You can:
- Cancel any job that is currently running.
- Remove the history of jobs that were previously run.
- Manage Job Queues. (Also requires Manage permission in Engines & Licensing.)
- Create: Create workflows.
- Write: View, edit and remove a workflow.
- Access: Access the Schedules page.
- Create: Create schedules.
- Allow: Edit or delete a schedule.
- Access: Access the Repositories page.
- Create: Create repositories.
- Download: Download workspaces and other repository items from FME Server into Workbench.
- Read: View repository information.
- Publish: Publish workspaces and other items to the repository from Workbench.
- Run: Run repository workspaces from FME Server.
- Remove: Remove a repository, or remove items from a repository.
- Access: Access the Publications page.
- Create: Create Notification Service Publications.
- Read: View information about a publication.
- Write: Edit a publication.
- Remove: Delete a publication.
- Access: Access the Subscriptions page.
- Create: Create Notification Service Subscriptions.
- Read: View information about a subscription.
- Write: Edit a subscription.
- Remove: Delete a subscription.
- Access: Access the Topics page.
- Create: Create topics.
- Read: View information about a topic.
- Write: Edit a topic.
- Publish: Publish notifications to a topic.
- Remove: Delete a topic.
- Access: Access the Resources page.
- Create: Create connections to network resources.
- Access: Read and download a file.
- List: List the folders and files of a resource.
- Write: Write to files.
- Upload: Upload files.
- Remove: Delete files.
- Access: Access the Projects page.
- Create: Create projects.
- Read: View information about a project.
- Write: Edit a project.
- Delete: Delete a project, or delete items from a project.
- Manage: Configure engines and licensing, except job queues (requires Manage permission in Jobs).
- Click OK. Two URLs appear under Workspace Sharing:
- FME Server App: Enables users to run the workspace from a browser and configure any published parameters.
- Web Service URL: A webhook that enables integrating the workspace with third-party software to programmatically run the workspace. The webhook runs according to the published parameters configured on the Run Workspace page.
To update the published parameters on the Run Workspace page, click Change Parameters, update as required, and click Share this workspace to generate a new webhook.
Click the Copy icons to copy either or both URLs.
Note: The following is a complete list of permissions in FME Server. Under Additional Permissions, only the minimal additional permissions that may be required to run the workspace display. After the token is generated, you can configure additional permissions for it on the Token Management page.
Note: Automations requires additional permissions. You are prompted to grant any additional permissions that are required.
Note: Access permission is not required to run a workspace. Only Run permission on the applicable repository is required (see below).
Note: Users must also have Allow permission on the applicable service (see Services) when running workspaces.
Note: You must uncheck all five permissions to completely remove a role from membership with a repository.
Individual Resource connections (top-level folders):
Note: Access or Create permission is not required to have Read/Write/Delete permission on individual projects. These tasks can still be accomplished with the REST API.
To return to the Run Workspace page, click Run Workspace on the breadcrumb at top.
Note: You can access the token that was created for these URLs on the API Tokens tab of the Token Management page.
Published Parameters: Details of any published parameters.
The resulting web page indicates whether the job submission was successful.
To Unregister a Service from a Workspace
To unregister a service from a workspace, use FME Workbench to "republish" the workspace to FME Server. On the "Register Workspace Services" page of the "Publish to FME Server Wizard," unselect the service you want to unregister. For more information, see the FME Workbench help.
To Unregister a Workspace from a Repository
To unregister a workspace from a repository, use FME Workbench to "republish" the workspace to FME Server. On the "Register Workspace Services" page of the "Publish to FME Server Wizard," unselect all the FME Server Web Services. Although the workspace is still considered "published," it is no longer visible in FME Server. For more information, see the FME Desktop Help.