FMEServerJobSubmitter

Features that successfully submitted the requests to the server.

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.

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.

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 Server Job 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.

• output_datasets{}: A list attribute that is provided when Output Data Location (see below) is set to Temporary Folder.
  • output_datasets{}.name: The unique name for the dataset (for example, SHAPE_1). If multiple writers use the same format, the name will be unique for each writer.
  • output_datasets{}.format: The format name. The same name applies to all writers that output to the same format (for example, SHAPE for shapefile).
  • output_datasets{}.path: The physical location where the dataset is written. You can use this attribute as input to downstream transformers for further processing.
• _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 either did not run to completion, or the server could not be contacted, 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: 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 Succeeded 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 Failed port, and the _job_failure_type attribute will hold the "Connection or Server Problem" value.

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.

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.