Hi,
as far as i know it is not possible to run Workspaces with a WorkspaceRunner on FME Server. With FME 2016 i even get a warning when I try to publish it. You would need a FME Desktop license/installation on your FME Server host. But even then you would have no control over the logfile, because the workspace runs out of the FME Server context.
You want to use the FMEServerJobSubmitter instead of the WorkspaceRunner and publish both workspaces to FME Server.
Then (depends on your exact settings of the JobSubmitter if you want to run it sychronously or asynchronously) the FME Server is fully aware of both jobs.
If you run it synchronously (Wait for job complete = Yes) the whole "second" logfile will be included in the log of your main workspace, if you do not wait the second job gets it's own job id.
Then you can view the log via the Server web UI or retrieve it with FMEServerLogFileRetriever programmatically.
Hi @ashertbrooks, If you are running the jobs on FME Server, I would recommend using the FME Server dedicated transformers ( FMEServerJobSubmitter, FMEServerJobWaiter and FMEServerLogFileRetriever)
Hope this helps.
Hi @ashertbrooks, If you are running the jobs on FME Server, I would recommend using the FME Server dedicated transformers ( FMEServerJobSubmitter, FMEServerJobWaiter and FMEServerLogFileRetriever)
Hope this helps.
Ha just a few seconds too late....
Hi,
as far as i know it is not possible to run Workspaces with a WorkspaceRunner on FME Server. With FME 2016 i even get a warning when I try to publish it. You would need a FME Desktop license/installation on your FME Server host. But even then you would have no control over the logfile, because the workspace runs out of the FME Server context.
You want to use the FMEServerJobSubmitter instead of the WorkspaceRunner and publish both workspaces to FME Server.
Then (depends on your exact settings of the JobSubmitter if you want to run it sychronously or asynchronously) the FME Server is fully aware of both jobs.
If you run it synchronously (Wait for job complete = Yes) the whole "second" logfile will be included in the log of your main workspace, if you do not wait the second job gets it's own job id.
Then you can view the log via the Server web UI or retrieve it with FMEServerLogFileRetriever programmatically.
I haven't been able to use FMEServerJobSubmitter because the name of the sub workspace being called is dynamic and will change depending on the input to the parent workspace, FMEServerJobSubmitter cannot use parameters to make the workspace being called dynamic.
I have been using workspaceRunner with success by calling workspaces that exist on a network path and the log does show it has executed correctly, I would just like to same level of detail that is shown for the parent workspace.
If you publish the parameter for the log file in the child workspace, you can create a separate log file for that workspace by defining the location and name in the WorkSpaceRunner.
If you publish the parameter for the log file in the child workspace, you can create a separate log file for that workspace by defining the location and name in the WorkSpaceRunner.
Thanks I will give that a go
