Skip to main content
Question

Workbench parameters best practice when using c# and REST interface

  • September 21, 2020
  • 2 replies
  • 43 views

r_huesken
Contributor
Forum|alt.badge.img+5

I need to pass quite a few parameters (10+) to my workbenches running on FME server. The jobs are started though a call to the FME SERVER rest API, from a c# application.

I'm considering 2 options:

1) specify each parameter individually, which requires some additional coding in c# when calling the workspace.

2) specify a single JSON parameter, which combines the values of all parameters. Passing parameters to the workbench will be more generic, since the set of parameters may be organised in a class and (de)serialized when required.

 

What would be the pros and cons of both methods?

 

2 replies

anhphuongt
Forum|alt.badge.img
  • September 21, 2020

Hi r_huesken,

What I usually do is getting the list of all the parameters for each workspace and fill these parameters individually, then run the workspace.

I think it is better that way because you can run preexisting workspace without modifications . Also if someone want to run the workspace directly on FME Server without using your C# application it would be simpler for them then trying to construct a JSON manually to run the workspace.

 

 

 


r_huesken
Contributor
Forum|alt.badge.img+5
  • Author
  • Contributor
  • September 22, 2020
anhphuongt wrote:

Hi r_huesken,

What I usually do is getting the list of all the parameters for each workspace and fill these parameters individually, then run the workspace.

I think it is better that way because you can run preexisting workspace without modifications . Also if someone want to run the workspace directly on FME Server without using your C# application it would be simpler for them then trying to construct a JSON manually to run the workspace.

 

 

 

Thanks, useful suggestion.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings