The [data The data load IWS solution can be started by sending a Control Message to the eagle_ml-2-0_default_cm_control_message stream. In this Control Message, you can specify various required, optional, and default parameters.
Info |
---|
...
In the Control Message, elements <messageId>, <correlationId>, and <businessTaskId> must be unique. Resending a file with the same values in these elements will result in an error. |
...
Expand | ||
---|---|---|
|
...
| |||||
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
Anchor | ||||
---|---|---|---|---|
|
...
Info |
---|
Parameter names are case-sensitive. |
The following table lists parameters that must be defined in each Control Message file used for the data load.
Parameter | Example of Value | Comments |
---|---|---|
ActionType | EXECUTE | Constant value to start all workflows. |
StreamName | eagle_ml-2-0_default_cm_execwkfl | Constant value for all extracts. The name of the message stream to which data is sent from the Control Message stream. This stream runs the workflow. |
WorkflowName | eagle_wrf_generic_load | Constant value for the load process. |
The following table lists required parameters to start the data load workflow with the WorkflowData parameter.
Parameter | Example of |
---|
Value | Comments |
---|---|
WorkflowData | EAGLE_ML_DATA_2.zip |
Name of the archive to be loaded. |
NOTE: This must be unique |
DeliveryMethod | FILE or FTP |
Location of the archive to be loaded, if the FILE method is specified. |
:) [Default value: cmw\in]. If the FTP method is used, the archive should be in the FTP directory that is specified by the parameter (:FTP_FILES_LOCATION |
:) [Default value: CMW/inbound]. |
The following two parameters are required to start the data load workflow with Base64 data:
Parameter | Example of Value | Comments |
---|---|---|
WorkflowData |
|
| Name of the archive to be loaded. MC: WorkflowData+ |
Data
WorkflowData is not ignored it is used when process creates file from base64 text. MC2: WorkflowData | ||||||
Data |
|
| Archive data in Base64 format |
...
Anchor | ||||
---|---|---|---|---|
|
Info |
---|
...
Parameter names are case-sensitive. |
The following table lists optional parameters for the data load workflow.
Parameter | Example of Value | Default Value | Comments |
---|---|---|---|
LoadSendNotification | 1 or 0 | 1 | The same logic is used for SendNotification, but this option can only be applied to extracts within the workflow. |
...
LocalFileFolder | in/RAW/eagle_ml-2-0_default_cm_ndfa/incoming/ | Launches a simple EJM process which takes the file specified in WorkflowData parameter and puts it into the target directory specified in LocalFileFolder parameter. The file can be stored b64-encoded. MC/MC2 supported. |
Anchor | ||||
---|---|---|---|---|
|
Info |
---|
...
Parameter names are case-sensitive. |
The following table lists default parameters for the data load workflow.
Parameter | Comments |
---|---|
SendNotification | For more |
[{+}http://eagle.helpdocsonline.com/ejm-jobs-notifications+
ReplyDeliveryMethod
ACKDeliveryMethod
CustomReplyLocation
CustomAckLocation
...
information, see the EJM Job Notifications Overview page in the EagleML wiki. | |
ReplyDeliveryMethod | |
ACKDeliveryMethod | |
CustomReplyLocation | |
CustomAckLocation |