span8
span4
span8
span4
Previous:FME Server 亚搏在线Workflow Management
This example demonstrates how to use a controller workspace for utilizing multiple FME Engines.Using this method,you can run a series of jobs on multiple engines and perform downstream processing from within a single workspace.
In 2017.1,we have a couple of new features in theFMEServerJobSubmitterwhich now eliminates the need for the FMEServerJobWaiter transformer,and enable you to use as many engines as are available.In particular there are a two parameters in the transformer which dictate the behavior:
WARNING:If you have 1 engine,Submit Jobsis set toParallelandWait for Jobs to Completeis set toYes,FME Server will deadlock,and you will have to manually stop the queue and jobs to free the engine.
Submit Jobs: | |||
Parallel | Sequential | ||
Wait for Jobs to Complete: | Yes |
Waits for all jobs to enter the transformer and then submits them at once.Sending features out of the transformer when they have all finished. *This will allow FME Server to use as many engines as available,but if you only have one engine all child jobs will be stuck in queue. |
Waits for the job to complete and feature to be released before submitting the next job.This combination will spin up a sub engine to process the child workspaces *Use this setting if you want to use one engine for both the child and parent workspace. |
No | Waits for all jobs to enter the transformer,提交一次,and releases features as soon as they are completed. | Submits a jobs as soon as it has been received and releases features as soon as they are submitted. |
The other new feature to note is the Summary Port.You can now use this to supply information to an FMEServerEmailGenerator so messages can be sent with information about the jobs submitted.The summary port acts as a blocking transformer and will only release a feature when all the jobs are completed with a fail or success status.
multiplejobsubmittersallengines.fmw
In this scenario involvingallengines.fmw,we would be using a FMEServerJobSubmitter with the Submit Jobs as Parallel and Wait for jobs to complete to Yes.
This scenario uses the multiplejobsubmittersallengines.fmw to submit jobs to new engines so you can utilize the full potential of FME Server.There are several assumptions of this workspace though 1) It's assuming you want to submit different jobs with different parameters 2) you want to be informed when the jobs are completed so you can process something that is dependent on it.
A)Multiple FMEServerJobSubmitters are need here so the unique parameters and workspaces can be accounted for.
B) The FMEServerJobSumbitters Submit Jobs parameter must be set asParalleland Wait for jobs to complete toNo.Even though we want to wait to find the status of the jobs,because the FMEServerJobSumbitters are blocking transformers they will not let anything else process in the workspace until they have completed the feature.
C) (Optional)The AttributeCreators create an attribute of holding the workspace name so jobs can be filtered accordingly after the FMEServerJobSubmitter.
D) FeatureHolder: This step allows all the jobs to be accumulated before passing them into the FMEServerJobWaiter.If they were not accumulated the triggering of the FMEServerJobWaiter may cause a FMEServerJobSubmitter to wait until the feature holder has finished when we want the jobs sent out as quickly as possible.
E) FMEServerJobWaiter: This will poll the server to find out when the job has completed and its status.
F) (Optional) Next we find the status of the Jobs and cancel the process if a job has failed.
Dealing with the output (2 options):
G) Aggregator: The aggregator has two functions 1) to accumulate all the features before releasing a feature and 2) To reduce the number of features so we can initiate a new process one time.
or
H) TestFilter to filter by Workspace so you can initiate different processes for different jobs.
In order to be notified of problems with the 亚搏在线workflow,you can set up the controller workspace (allengines.fmw,and multiplejobsubmittersallengines.fmw) to publish to a topic on failure,and add an email subscription.See our tutorial series onemail in FME Serverfor more information - specifically,sending an email when a workspace completes.
You can also automate the initiation of the workspace by using the Notification service - perhaps to watch a directory for changes,or to respond to an incoming email attachment.This way,FME Server can automatically load new data into your database,process it,create web map tiles and upload them to a hosting location,such as Amazon S3.
FME Server 亚搏在线Workflow Management
FME Server 亚搏在线Workflow Management (FME Server 2016)
Part 2 - Create & Deploy a Project
Part 3 - Deploy changes (update)
Part 5 - Deploy changes (delete)
FME Server 亚搏在线Workflow Management (FME Server 2014)
Workspace with FMEServerJobSubmitter Fails with Licensing Error
Part 1 - Create a 亚搏在线Workflow
Directory Watch Publisher with Idle Time Delay (Advanced) (2017)
© 2019 亚搏在线Safe Software Inc |Legal