Skip to main content
Question

fme flow automation: how to run a workspace (name decided at runtime) if it exists?

  • December 9, 2024
  • 4 replies
  • 41 views

bdotfdotfme
Contributor
Forum|alt.badge.img+3

I am sure that there is a solution within fme flow automation, but meanwhile I am pulling my hair for not finding it…


The scenario:

Through a directory watcher triggered automation, I import the content of a variety of geopackage files into postgis tables with corresponding names. This part runs well.

For some of these tables, I have ElasticSearch indices, which have to be rebuilt after table import. For the indexing, I have a repo on the flow server named Elastic-Indexer, and therein are workspaces with names corresponding to some of the tables. (n.b. not all tables have corresponding indexer workspaces)

Now I try to build up a dynamic system that gets notified with the schema.tablename after import and runs - if it exists - a workspace with a matching name from the Elastic-Indexer repository.

 

My first idea was to read the workspace names from that repository and call the workspace if the name matches, but a) I was not able to read the workspace names and b) this solution looks clunky when we have dynamic workspaces available in flow automations.

Any hint - also for a good tutorial on using dynamic workspaces - would be highly appreciated.

---Markus

 

4 replies

redgeographics
Celebrity
Forum|alt.badge.img+49

Does it have to be a dynamic workspace name? Why not a generic workspace name and then use a parameter to indicate the table you want to process?


bdotfdotfme
Contributor
Forum|alt.badge.img+3
  • Author
  • Contributor
  • December 10, 2024

Unfortunately the index creation can be very different in terms of concatenating fields and such, depending on the underlying table.
One possibility would be to use a lookup table for this. But the maintenance of this table then is an additional task.


redgeographics
Celebrity
Forum|alt.badge.img+49

But the maintenance of this table then is an additional task.

So is maintaining multiple workspaces...

Okay, so how about this: keep your separate workspaces but use a single one, with the table name as parameter, to trigger them using either an FMEFLowJobSubmitter or an API call.


bdotfdotfme
Contributor
Forum|alt.badge.img+3
  • Author
  • Contributor
  • December 18, 2024

Finally I managed to solve this with a flow automation.

But: the documentation is insufficient to non-existing, especially if you have , like me, to use a localized GUI!


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