+26According to the transformer documentation:
I am using FME Server 2017.0.0.2
I have a workspace using 1 FMEServerJobSubmitter (with wait set to Yes).
Why do I see the child job as a separate job (with its own job ID)?
This is resulting in two separate log files (and I would like just 1 log file).
Has this changed in the newer versions?
+26I did a test using the 2016 and 2017 FMEServerJobSubmitters (both running a child workspace twice using FMEServerJobsubmitter transformers with Wait set to Yes).
The 2016 workspace runs as 1 job (108), the 2017 workspace runs as 3 separate jobs (105, 106 and 107).
+59Hi @erik_jan
Yes I think this did change in 2017. The idea is to allow the Server to run multiple jobs simultaneously (assuming there are multiple engines).
However, there is a parameter in the transformer that controls this.
When set to In Sequence it should run as it did before.
So... if you find that the default is not In Sequence, or an old workspace with one of those transformers is running in parallel, do let us know. I think that would be a bug. We should always respect backwards compatibility.
Also let us know if you are using In Sequence and somehow it is not working as it did before.
If you contact our support team, you could quote these numbers to them as a reference: PR#51727 and PR#73601 - that way they will be able to look up what has changed.
I hope that helps to answer your question
Mark
+26Hi @erik_jan
Yes I think this did change in 2017. The idea is to allow the Server to run multiple jobs simultaneously (assuming there are multiple engines).
However, there is a parameter in the transformer that controls this.
When set to In Sequence it should run as it did before.
So... if you find that the default is not In Sequence, or an old workspace with one of those transformers is running in parallel, do let us know. I think that would be a bug. We should always respect backwards compatibility.
Also let us know if you are using In Sequence and somehow it is not working as it did before.
If you contact our support team, you could quote these numbers to them as a reference: PR#51727 and PR#73601 - that way they will be able to look up what has changed.
I hope that helps to answer your question
Mark
When was that "Submit Jobs" added?
These are the settings for 2017.0 (build 17259, and same till 17291):
+59When was that "Submit Jobs" added?
These are the settings for 2017.0 (build 17259, and same till 17291):
+26
I doubt that will work as the Wrapper workspace is running on the Server too and is calling the child workspaces. I am afraid this will only work with a Desktop and Server upgrade to 2017.1 (and we have 4 Desktop and 4 Server installs).
+26
+59OK, so looks like there are two different things going on there.
Firstly there was this change in 2017.0 - the transformer is calling jobs in a different way and this is resulting in different logs. This is what you are experiencing.
Secondly there is this update in 2017.1 - which is not directly related to what you are experiencing, but is an enhancement you might want to check out in .1
So, FME is now producing separate logs for child workspaces. It's an intentional decision I believe, not a fault. The best thing I think we could do is improve handling of jobs in the interface, so that you can navigate from the parent to the child log more easily. I believe there's already an idea for job handling that you can comment on and vote up, eg: https://knowledge.safe.com/idea/21471/fme-server-job-listing-gui-improvements.html?smartspace=ideas-fme-server
I guess you could also set the log location in the workspaces, and append to the same file. Could be done with a published parameter (maybe job ID?) so that could be a workaround?
Regards
Mark
+26OK, so looks like there are two different things going on there.
Firstly there was this change in 2017.0 - the transformer is calling jobs in a different way and this is resulting in different logs. This is what you are experiencing.
Secondly there is this update in 2017.1 - which is not directly related to what you are experiencing, but is an enhancement you might want to check out in .1
So, FME is now producing separate logs for child workspaces. It's an intentional decision I believe, not a fault. The best thing I think we could do is improve handling of jobs in the interface, so that you can navigate from the parent to the child log more easily. I believe there's already an idea for job handling that you can comment on and vote up, eg: https://knowledge.safe.com/idea/21471/fme-server-job-listing-gui-improvements.html?smartspace=ideas-fme-server
I guess you could also set the log location in the workspaces, and append to the same file. Could be done with a published parameter (maybe job ID?) so that could be a workaround?
Regards
Mark
My issue is, that we are using a FMEServerLogFileRetriever to get the log information and append all logs to be emailed. Formerly we could use the one _job_ID attribute to do so.
Now all jobs (wrapper and children) have their own _job_ID and their own log files).
As a work-around we consider gathering each log file after the FMEServerJobsubmitter (but we have a lot of workspaces that need to be changed, because of this change in functionality).
Erik
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
