WorkspaceRunner
Runs an additional FME Workbench workspace on the local computer by spawning a new FME process. This transformer is useful for batch processing, especially in conjunction with the Directory and File Reader.
Input Ports
This transformer runs the specified workspace for each feature that enters through the Input port. Any published parameters of the specified workspace will be given values as specified in the transformer, or taken from attributes of the feature which enters it.
Output Ports
If the Wait for Job to Complete parameter is set to Yes, then the initiating feature is output through this port if the job successfully completed. If the Wait for Job to Complete parameter is set to No, the initiating feature is output through this port if the request was successfully submitted, though whether or not the workspace completes is unknown in this case.
If the new FME process could not be spawned, the feature will be output via the Failed port, and the _failure_message attribute will hold the reason for the failure.
If the Wait For Job to Complete parameter is set to No, and a value is given for the Maximum Number of Concurrent Processes, then the Summary port will output a feature with the attributes _proc_count and _processes{}.
The _proc_count attribute will contain the total number of processes executed by the WorkspaceRunner. The _processes{} attribute is a list of the process Ids. If the Wait For Job to Complete parameter is set to Yes, then Summary features will still have a _proc_count, but will not have a _processes{} attribute.
Parameters
Browse to select the additional workspace to run, or select an attribute that contains the full name and path of the workspace to run.
If this parameter is set to Yes, then the transformer will wait until the workspace has finished running. In this case, the initiating feature is output via the Succeeded port if the job successfully ran to completion.
The initiating feature will be output via the Failed port if the workspace did not run to completion, and will have a _failure_message attribute added to it that contains the error message returned from the FME that ran the workspace.
If this parameter is set to No, the transformer will output the initiating feature as soon as an FME has been spawned off to do the translation. In this case, the initiating feature is output via the Succeeded port if the request was successfully submitted.
To limit further the number of concurrent workspaces a WorkspaceRunner runs, use the Maximum Number of Concurrent Processes parameter. WorkspaceRunner will limit the number of concurrently executing workspaces to the value specified. This helps prevent the system from being overloaded with an excessive number of simultaneous processes. If specified, this parameter value must be an integer in the range 1-7. For example, if the value is set to 2, then WorkspaceRunner can only start two additional child FME processes.
Usage Notes
Publishing to FME Server: Publishing a workspace that includes this transformer is not recommended. The transformer will try to start an FME outside of FME Server to run the workspace, and this FME will require an additional license. Consider using FMEServerJobSubmitter instead.
Editing Transformer Parameters
Using a set of menu options, transformer parameters can be assigned by referencing other elements in the workspace. More advanced functions, such as an advanced editor and an arithmetic editor, are also available in some transformers. To access a menu of these options, click beside the applicable parameter. For more information, see Transformer Parameter Menu Options.
Transformer Categories
Related Transformers
There is a also an FMEServerJobSubmitter that will submit jobs to be run on an FME Server.
Search FME Knowledge Center
Search for samples and information about this transformer on the FME Knowledge Center.