Hi,

 

 

Just today I've created simple examples of the WorkspaceRunner for the other question. See this thread:

 

Creating a BATCH with multiple INPUTS (variables) to run a workbench that intersects LINES AND POLYGONS

 

http://fmepedia.safe.com/AnswersQuestionDetail?id=906a0000000cofsAAA

 

Takashi

---

Thankyou Takashi,

 

 

I have had a look at the examples you created.  However I have a few questions about them:

 

 

In runner1.fmw I don't understand exactly what the "Creator" transformer is for..

 

 

Also, did you define the destination feature type name manually as "admin_pt" in runner1.fmw or is it getting that from main.fmw?  Also, in main.fmw, what exactly is the ParameterFetcher transformer doing?  In summary - I'm confused as to where the destination feature type name originates from and how it connects up between the runner and the main workspaces.

 

 

Thanks

---

The WorkspaceRunner requires input feature(s). The Creator transformer in "runner1.fmw" creates a feature as the initiator for the first WorkspaceRunner. If there are no input features, the WorkspaceRunner does nothing.

 

 

The WorkspaceRunner runs the target workspace passing the published parameters.

 

I defined a published parameter named "DEST_FEATURE_TYPE_NAME" in "main.fmw", so you can pass any destination feature type name through the WorkspaceRunner.

 

 

The ParameterFetcher in "main.fmw" adds the parameter value (i.e. destination feature type name) to every feature as an attribute; it will be used as the fanout attribute in the writer.

 

 

This workflow is just an example based on imaginary scenario. Since you are using Dynamic Schema functionality in your workspace, it may not be necessary to pass the destination feature type name as a published parameter. But you will have to use some published parameters to achieve your own purpose.

 

 

Published parameters can be passed to the target workspace through the WorkspaceRunner at run-time. This might be the point to understand how the WorkspaceRunner works.

 

Takashi

---

thanks Takashi,

 

 

in regards to the Creator transformer - is it just an arbritrary file created to kick-start the workspace runner and is not actually required for processing?

---

Yes, the Creator is used only for "kick-start" the WorkspaceRunner in this case. The created feature will not be used for any other purpose.

 

 

Takashi

---

Assuming the Creator has lines on its output port, can I use the line feature and its attribute - one feature at a time - as part of my translation on the worker workspace? There is another reader in the translation that is translated with this feature fromt he main workspace. On each feature created by the Creator, an attribute named featureID is needed for the where clause parameter of the reader feature types inside the worker workspace, how do I implement this in the Main workspcae? On the Workspace Runner tranformer that paramater is looks  like this Parameter column:  "FEATUREID_TO_PROCESS" ; Value column: @VALUE(featureID). I tried creating a User parameter and used Apply to but without any success. Please help.

---