A data load IWS workflow solution, eagle_wrf_generic_load, has been created. This solution extracts ZIP-packed data from the archives of the sample eagle_wrf_generic_extract solution and routes it to the appropriate message streams. For each message stream, the inbound rule loads extracted records to the database based on the specific object type.
The eagle_wrf_generic_load solution replaces the old genericload solution.
The following diagram shows the steps in the sample data load IWS workflow solution.
In this section
On this page
Start the Data Load IWS Workflow Solution (Step 1)
You can start the eagle_wrf_generic_load solution in several ways:
Put a ZIP file directly into the data\msgcenter\msgcenter\in\RAW\eagle_ml-2-0_default_cm_ndfa\incoming folder.
The file name must match the EAGLE_ML mask defined as a default prefix in the sample data extract IWS solution.Send a Control Message specifying the ZIP file name and the archive location to the eagle_ml-2-0_default_cm_control_message stream.
Send a Control Message with Base64 encoded data to the eagle_ml-2-0_default_cm_control_message stream.
Unzip Archived Data Extracts (Step 2)
This step is performed by the eagle_ml-2-0_default_cm_ndfa and eagle_ml-2-0_default_cm_unpacker message streams.
Load Data Extracts to the Database (Step 3)
After the data extracts are unzipped, a sequence of loading processes is run for different object groups. Each loading process starts when all files for the previous processes (defined by the filename mask) are loaded.
Perform Post-Load Processing (Step 4)
Post-load processing is a reserved step for user customization (such as Nuggetizer). Its processing is controlled by the user-defined parameters (PostloadParam1..15) transformed into standard parameters to address specific post-load user requirements.
Post-load processing can be done only if the eagle_wrf_generic_load solution was started using the Control Message.
This section contains information about the following:
Add Comment