You are here: FME Server Reference Manual > FME Server Services > Transformation Services > Job Submitter Service

Job Submitter Service

The Job Submitter service accepts and runs workspace job requests.

This service is requested using a URL or a form. For example,

http://<host>/fmejobsubmitter/<repository>/<workspace>.fmw?<parameters>

The resulting web page indicates whether the job submission was successful. If the job was submitted successfully, the FME Server transformation results are shown.

Service Specific Request Parameters

Name	Value	Description
opt_responseformat	xml \| json Default: xml	Defines the language of the response. The text must be all lowercase.
opt_geturl	The URL to a dataset	The URL of the source dataset to be used for transformation.
opt_showresult	true \| false	It indicates whether the XML/JSON responses from these three services include the FME transformation result. The default value is true if this parameter is not present.
opt_servicemode	sync \| async	Toggle between synchronous and asynchronous modes of the service.
opt_requesteremail	comma-separated e-mail addresses	Addresses to which the notification e-mail messages are sent.

Notification Manager Support

This service supports the nm_jobsuccess_topic and nm_jobfailure_topic directives. For more information, see Notification Manager Directives.

Using Remote Data During a Request

Using data from HTTP POST body as Reader dataset

This web service can receive data and override source dataset via HTTP POST. The content of the POST request body will be saved to a temporary file which will be used as the Reader dataset of the workspace. If there is more than one reader in the workspace, then you will need to indicate which reader will use the temporary file. You indicate your choice when publishing the workspace by editing the service registration.

Using data from HTTP GET as Reader dataset

This web service can receive data and override Reader dataset via HTTP GET. The dataset should be specified as a URL and passed to service by 'opt_geturl' parameter. Both HTTP and FTP URLs are supported. If there is more than one reader in the workspace, then you will need to indicate which reader will use the temporary file. You indicate your choice when publishing the workspace by editing the service registration.

For example here is a service request that uses a remote KMZ dataset:

http://localhost/fmejobsubmitter/Test/Viewer.fmw?opt_geturl=http://data.vancouver.ca/download/kml/elementary_school_boundaries.kmz

Response Elements

If the response format is specified as XML or JSON, a service response may contain the elements shown in the following table.

Element	Child Elements	Value	Description
statusInfo	message	message string	service failure message
	status	success \| failure	service status
	mode	sync \| async	service mode
fmeTransformationResult	fmeServerResponse	FME Server response properties	FME Server response
fmeTransformationResult	fmeEngineResponse	FME Engine response properties	FME Engine response
email	none	E-mail addresses	Requesters’ e-mail addresses
jobID	none	job ID	The current job identifier