Skip to main content
Question

How to Retrieve a Published Parameter via a FMEServerJobSubmitter

  • November 2, 2018
  • 1 reply
  • 55 views

Forum|alt.badge.img

Hi, I´m currently struggling with retrieving a Published Parameter via a FMEServerJobSubmitter.

The Published Parameter is a Attribute Value, which I have run through a StringConcatentor. Either the parameter can´t be found, or I end up with the Parameter Name as textstring.

In short, what I´m trying to achive is to fetch the File-Name of each .txt I produce in one of my Workbenches. This is to allow my next workbench(Via a second FMEServerJobSubmitter) to find the files under the temp Folder. Everything is handled in one "Control"-Workbench.

I have also tried to fetch the file Name(path_rootname) via a Feature Reader, without any luck.

 

Overview of the "Control Workspace"

The first FMEServerJobSubmitter and Example issues with Published Parameters

According to the log in FME-Server, the File Name can´t be found. Please also see log-File().

I just can´t get my head around what to do. I´m sure some of you smart people have some super intelligent advice to share.

Some Guides I have read on the Topic

https://knowledge.safe.com/questions/39045/how-dio-i-set-a-user-parameter-in-attributecreator.html

https://knowledge.safe.com/articles/56071/fme-server-workflow-management-fme-server-2016.html

https://knowledge.safe.com/articles/1439/fme-server-workflow-management-1.html

 

Best Regards,

/Daniel

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.

1 reply

takashi
Celebrity
  • 7843 replies
  • November 2, 2018

I don't think schema features output from the <Schema> port of the FeatureReader would be necessary to perform the job. Try deleting the connection between the <Schema> port and the FMEServerJobSubmitter.