span8
span4
span8
span4
Hello,
I am using a FME Server 2014 SP1 with two engines and the corresponding FME Desktop version.We designed a process,which should trigger other workspaces in a specified order,but the complete process should run on only one engine,which is,according to thetutorial,possible and which I could confirm (see list point #4 below).
For doing so,we have used the FMEServerJobSubmitter Transformer.Actually our process is very similar to the following tutorial (at least in regard to the technical aspects)https://knowledge.亚搏在线safe.com/articles/1413/fme-serve...
Since we are running different services,we need a Job Routing Configuration,which we have realized within theFMEServerConfig.txt:
TM_DEFAULT_TAG=default TM_QUEUE_TYPE=DEFAULT# Assign tagTM_REPOSITORY_2=internalProcesses:internalProcessesTagTM_ENGINE_1=Host_Engine1:defaultTM_ENGINE_2=Host_Engine2:internalProcessesTag
Using this config,every workspace in the the "internalProcesses"-repository gets the tag "internalProcessesTag".Following,the engine "Host_Engine1" is responsible for every job with the tag "internalProcessesTag".All other jobs get the "default"-tag,so Host_Engine1 is completely reserved for this purpose.
To ensure that the problem is not caused by our custom workbench,I've followed the above mentioned tutorial,published the defined workbenches to my FME Server.Working with this configuration,I have observed the following circumstances and problems:
TM_DEFAULT_TAG=default TM_QUEUE_TYPE=DEFAULT# Assign tagTM_REPOSITORY_1=internalProcesses:internalProcessesTag# TM_ENGINE_1=Host_Engine1:defaultTM_ENGINE_2=Host_Engine2:internalProcessesTag
So...are there any known limitations in regard to the combination of FMEServerJobSubmitter and a active JobRouting Configuration?
For #2,I think you may have an issue
If you have a parent/controller workspace in FME Server (at 2014) calling FMEServerJobSubmitter that is calling child processes,this will run as one process (not many) and so you don't even need to deal with job routing.
However you mention that you get the first called job in the queue and never starts (basically because the first job is waiting for a response and never getting it because the job is queued).This make me think that the url you are calling in not what FME Server thinks it is called and therefore thinks its a external FME Server.So if you set your server up as < servername > but the url is something different (e.g.www.gofme.com) then it will submit a new job;if they are both the same it will run under the same job.
If that is the case,change the FMEServerJobSubmitter to call the < servername > and try this again.
Hi @schlomm,@mark2cat亚搏在线safe,
Thanks for the post,this is somewhat under documented,for as far I can see,this is only documented infmeServerConfig.txt.
Regards.
Helmoet.
Hello@schlomm
The answer to your final question is yes,thereisa limitation re the FMEServerJobSubmitter and job routing.The answer comes from our training manual at:
The information is regarding where the master workspace is run...
Interestingly [...] the initial/control workspace can be run on either FME Desktop (e.g.Workbench) or FME Server.The FMEServerJobSubmitter works on both platforms.
However,there's a difference.On FME Desktop the control workspace runs immediately,but each child job executed by an FMEServerJobSubmitter transformer is submitted to the FME Server queue and may have to wait for an engine.On FME Server - if you have Wait for Job to Complete = Yes - it's the reverse: the control workspace is submitted to the queue,but each child job executed by an FMEServerJobSubmitter bypasses the queue and runs immediately.
This means that on Desktop the child processes are affected by the FMEServerJobSubmitter Job Priority and Job Tag parameters.But on Server (when Wait for Job = Yes) those parameters are ignored because the child processes are run immediately and not queued.In short,those FMEServerJobSubmitter parameters only apply when the call comes from FME Desktop,because only then are the jobs queued.
That seems to me to be the limitation you are describing (in points 1 and 2).I have to say that I don't know of how to work around that.For that information you would be best to get in touch with our support team and ask them.You can contact them throughhttp://亚搏在线safe.com/support
I hope this information is useful,even if it's probably not moved you much further forward in terms of a solution.
Regards
Mark
Mark Ireland
Product Evangelist
亚搏在线Safe Software Inc.
Hello@mark2cat亚搏在线safe,
Thanks for your answer.These are helpful information!However this unfortunately does not solve my problem,but I will get in contact with our local support.Two last questions:
Thanks a lot,
Dominik
Why does my workspace on FME Server hang when using the FMEServerJobSubmitter?1 Answer
Is there any step by step guide to upgrade FME 2014 to 2016.2.1?2 Answers
FME Server Job hold and resubmit 1 hour later1 Answer
Run a Workspace with external resources2 Answers
FMEServerJobSubmitter job with HTTPCaller can't connect to service1 Answer
© 2019 亚搏在线Safe Software Inc |Legal