Artifact shapes identify data flow patterns. The IWS Toolbox includes the following artifact shapes:
Data
EJM Task Response
EJM Run Task
A description of each artifact shape follows.
On this page
| Table of Contents |
|---|
| Anchor | ||||
|---|---|---|---|---|
|
The Data artifact shape allows you to indicate how a data payload is passed into the workflow from outside and transferred between the workflow steps.
The following diagram shows several use cases for the Data artifact.
You can use the Data artifact as a data entry point. In this case it is necessary to provide a file mask. In the run window during the test, you can select the file name to use. The default location for the files at run time is tpe/data/msgcenter/cmw/in
There is a Bundle-based check box in the Properties sheet of the Begin shape. If the workflow is bundle-based, then the data file should be delivered to the incoming folder of eagle_ml-2-0_default_cm_ndfa stream.
Another use case is to indicate how data should be moved from one shape to another. In most cases, adjacent shapes do not have to be connected by a Data artifact, but such a connection is absolutely necessary if you want to pass data to a distant shape, or to multiple shapes at once.
| Anchor | ||||
|---|---|---|---|---|
|
You can use the EJM Task Response artifact only to pass the execution result message (Task Status Response, also known as RTR) from one step to another.
The latter step is responsible for parsing the XML Format and extracting necessary information from it.
| Anchor | ||||
|---|---|---|---|---|
|
You can use the EJM Run Task artifact in a similar manner to the EJM Task Response artifact, but it is only available in the workflows built with a deprecated "MC stream cascading" framework.
You can check what framework your workflow is based on by opening the Solution Properties box. To do so, in the Solution Explorer pane, right-click the name of the solution, and then click Properties.
