Skip to main content
Archived

Allow ALL FMEServerJobSubmitter parameters to be fed by attributes and allowable

Related products:Transformers
  • June 1, 2016
  • 3 replies
  • 43 views

aarcra
Contributor

***Note from Migration:***

Original Title was: Allow ALL FMEServerJobSubmitter parameters to be fed by attributes and allowable exposing of those paramaters


I would like to read a spreadsheet and dynamically feed things like Workspace Name, repository, Tags, Output Dataset ("As Specified in Workspace and Parameters" as an option/whats already been published to server), etc. into a FMEServerJobSubmitter.


I don't want to set up a single jobsubmitter for every workbench I need run. This helps with looping failed jobs until successful among other things.

Hidden parameters of the FME Server Job parameters that we need less hard-coded control of:

#! <XFORM_PARM PARM_NAME="USERNAME" PARM_VALUE="me"/>

#! <XFORM_PARM PARM_NAME="SERVER_PORT" PARM_VALUE="0"/>

#! <XFORM_PARM PARM_NAME="PARAMETER_TYPES" PARM_VALUE="STRING,STRING,STRING,STRING,STRING"/>

#! <XFORM_PARM PARM_NAME="SUBSECTION" PARM_VALUE="SERVER_JOB_SUBMITTER"/>

#! <XFORM_PARM PARM_NAME="PRIORITY" PARM_VALUE="100"/>

#! <XFORM_PARM PARM_NAME="BLOCKING" PARM_VALUE="No"/>

#! <XFORM_PARM PARM_NAME="REPOSITORY" PARM_VALUE="Waste Management"/>

#! <XFORM_PARM PARM_NAME="DATASET_OVERRIDE" PARM_VALUE="As Specified in Workspace and Parameters"/>

#! <XFORM_PARM PARM_NAME="XFORMER_NAME" PARM_VALUE="Hand_block_number"/>

#! <XFORM_PARM PARM_NAME="WORKSPACE_NAME" PARM_VALUE="Hand_block_number.fmw"/>

#! <XFORM_PARM PARM_NAME="SERVER_NAME" PARM_VALUE="coevdfme1:8081"/>

#! www.arcgis.com,SourceDataset_GEODATABASE_FILE, cepcad01 micrdata GIS Data Hand.gdb,DestDataset_ARCGISONLINEFEATURES, www.arcgis.com,DestDataset_ARCGISONLINEFEATURES_6, www.arcgis.com,DestDataset_ARCGISONLINEFEATURES_5, www.arcgis.com"/>

#! <XFORM_PARM PARM_NAME="TM_TAG" PARM_VALUE=""/>

#! <XFORM_PARM PARM_NAME="PASSWORD" PARM_VALUE="fme_decrypt(thanks for looking ;) )"/>

Please please please let me be able to expose these attributes after submitting a job and then consume them in another Submitting bench :)

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

3 replies

If I understand this idea correctly, I am all for it but I would also like to have the option to look somewhere other than a spreadsheet, like a database table.


donatsafe
Safer
Forum|alt.badge.img+4
  • Safer
  • June 7, 2016

Hmmmm, Interesting. How do folks feel about if we define a JSON structure that specifies everything. We would then build some helper transformers to build the JSON. Of course the JSON could be built directly as well. Other ideas?


I think that JSON is fine because I can still "store the source" somewhere else, and then translate it to JSON.