FMEServerJobSubmitter

Features that submitted the requests to the server and successfully completed. This port is only visible when Wait for Jobs to Complete is Yes.

Features that submitted the requests to the server, but failed to complete successfully. This port is only visible when Wait for Jobs to Complete is Yes.

Features that successfully submitted the requests to the server. This port is only visible when Wait for Jobs to Complete is No.

A single feature which details which jobs were submitted and which succeeded. This feature contains the following list attributes: _submitted_job_ids{}, _succeeded_job_ids{}, and _failed_job_ids{}.

Features that failed to submit the requests to the server.

Specify a web connection to an FME Server. Web connections can be reused in multiple workspaces, and connection parameters are hidden in the workspace. For more information, see Using Web Connections.

When checked, you must specify the connection parameters to the FME Server manually. The connection parameters are visible in the workspace. To connect, specify:

FME Server URL

Enter a URL to access FME Server. You may need to contact your System Administrator for the URL.

Username and Password

Provide your FME Server credentials.

If this parameter is set to In Sequence, the transformer will submit each request as soon as it receives an initiating feature. If Wait for Jobs to Complete is Yes, the transformer will wait for the job to complete before processing the next feature.

If this parameter is set to In Parallel, the transformer will wait until all input features are received, then send all requests at the same time. If Wait for Jobs to Complete is Yes, the transformer will wait for all of the submitted jobs to complete.

If this parameter is set to Yes, then the transformer will wait until the job is completely processed by the server before proceeding. In this case, the initiating feature is output via the Succeeded port if the job successfully ran to completion, and will have these attributes added to it:

• _job_id: The integer ID the server assigned to this job.

Note: When Wait for Jobs to Complete is set to Yes, and multiple FMEServerJobSubmitter transformers are linked to manage the workflow of multiple jobs on the same FME Server, all jobs run as child processes of the same FME engine that is engaged by FME Server to run the first job. No other FME engine is engaged. As a result, child jobs do not appear in the FME Server job queue or job history, and do not have their own job_id's. Additionally, all job logs are included in the job log of the parent (controller) job. For more information, see "FME Server Workflow Management," at http://knowledge.safe.com/articles/How_To/FME-Server-Workflow-Management.

• _numFeaturesOutput: The number features that were output by the job.
• _priority: The priority assigned to the job.
• _requesterHost: The name of the machine hosting FME Workbench that submitted the job.
• _requesterResultPort: The port on the host machine through which results are returned.
• _status: Job status indicator; can be SUBMITTED, QUEUED, ABORTED, SUCCESS, FME_FAILURE, JOB_FAILURE or PULLED.
• _statusMessage: The translation result message.
• _timeFinished: The time the job finished .
• _timeRequested: The time the server received the job request.
• _timeStarted: The time the server started processing the job.

All times are in YYYYMMDDhhmmss format.

The feature will be output via the Failed port if the job did not run to completion, or to the <Rejected> port if the job could not be submitted, and will have these attributes added to it:

• _job_failure_type: Holds one of "Connection or Server Problem" or "Translation Failed". If the latter, then the following attributes will also have values; otherwise, they are empty.
• _numFeaturesOutput: The number features that were output by the job.
• _priority: The priority assigned to the job.
• _requesterHost: The name of the machine hosting FME Workbench that submitted the job.
• _requesterResultPort: The port on the host machine through which results are returned.
• _job_id: The integer ID the server assigned to this job.

Note: _job_id is included only if the job failure is related to an error during translation. If the job did not run due to a connection or server problem, then _job_id is not included.

• _status: Job status indicator; can be SUBMITTED, QUEUED, ABORTED, SUCCESS, FME_FAILURE, JOB_FAILURE or PULLED.
• _statusMessage: The error message returned from the server explaining why the request failed.
• _timeFinished: The time the job finished.
• _timeRequested: The time the server received the job request.
• _timeStarted: The time the server started processing the job.

If this parameter is set to No, the transformer will output the initiating feature as soon as the job is submitted to the server. In this case, the initiating feature is output via the Submitted port if the request was successfully submitted, and only the _job_id attribute will be added to it.  If the server could not be contacted or the job submission otherwise failed, then the feature is output via the <Rejected> port, and the _job_failure_type attribute will hold the "Connection or Server Problem" value.

Specify the FME Server repository that contains the workspace you want to run.

Specify the workspace to run for each feature that enters the transformer.

Any published parameters of the workspace to be run appear here. For each one, specify the value to pass when the workspace runs. To refresh the parameters from FME Server, click the refresh icon.

Defines the order in which the job will be executed on the server. The default is 100, the lowest priority possible.

If supplied, defines the tag associated with this workspace for use with FME Server’s Job Routing. No default value is specified.

For more information about Job Routing, please see the documentation here: https://docs.safe.com/fme/html/FME_Server_Documentation/Content/AdminGuide/Configure_Job_Routing.htm.

The time, in seconds, after which a job that is waiting in queue does not execute. If the job does not execute before this time is reached, it remains in the queue until it is ready to execute, but execution is not attempted. This directive is useful for time-sensitive jobs that you do not want to run after the specified time is exceeded.

The time, in seconds, a job will remain in the running state. This directive ensures that a job does not hang and block an FME Engine indefinitely. The minimum allowable value is 1.