The Xml Summarizer Executor can be configured using the Aspire Admin UI from the Workflow page and by clicking the workflow where the component will be used.

Step 1. Launch Aspire and Open the Content Source Management Page.

Launch Aspire (if it's not already running). See:

• Launch Control

• Browse to: http://localhost:50505 and then open the Workflows Page. For details on using the Aspire UI, please refer to this page: Aspire UI.

Step 2. Add or select a Workflow.

• Add a new workflow or open an existing workflow.
• For this step, please refer to the Workflow Introduction.

Step 3. Add the Xml Summarizer Executor to the Workflow.

• Select the event for which you want to add the Xml Summarizer Executor to, from the Event combo.
• To add the component, drag the Xml Summarizer Executor from the Rules Section on the right side of the screen and drop it below the Workflow Event to the left side of the screen. This will automatically open the Xml Summarizer Executor window for the configuration of the component.

Step 3a. Specify a description for the application.

 In the top section of the Xml Summarizer Executor configuration window, specify the description for the application.

Step 3b. Specify the executor configuration.

1. Root Node: The root node which contains the sub-jobs to publish. If not specified, the root node of the entire XML tree is considered to be the root node.
2. Character Encoding: The character encoding of the XML file to be read, if not UTF-8.
3. Cleanse: Enable if you want to clean the XML content from non-readable characters (.i.e ASCII code 15).
4. Honor DTD: Enable if you want to fetch XML's DTD.
5. Limit nested structures to flatten: Enable to limit how many levels in a nested structures should be flattened.
   1. Maximum nested level: The maximum nested level to be flatten.
6. Limit the number of arrays entries to process: Enable to limit how many entries in array structures should be processed.
   1. Maximum number of entries: The maximum number of array entries to process.
7. Debug: Debug messages will be enabled
8. Add Schema: If enabled, the table schema will be added to the processed columns.
9. Use Temp File: Enable to download the content stream to a temporary file before processing it.
10. Thread Pool: The number of threads to use for parallel processing.
11. Processed Rows Log Frequency: The frequency for reporting the processed rows.
12. Use row sampling: Enable to process only a random sample of the table rows. This option could increase the memory usage.
    1. Minimum of samples to gather: The minimum of randoms samples that will be gathered from the table.
    2. Maximum of samples to gather: The Maximum of randoms samples that will be gathered from the table.
    3. Minimum percentage to process: The minimum percentage of the total rows to process from table.
    4. Limit the number of rows to read: Enable to limit how many rows from the table will be read.
       1. Maximum number of rows to read: The maximum of row from the table that will be read.
13. Use row filter: Check to filter the rows to process.
    1. Use groovy file: Enable to use a groovy file to filter the rows.
       1. Groovy Script Path: The path of the groovy script that contains the filter logic.  It must return a boolean value, if true, the row will be filtered.
       2. Filter Script: Script used to filter the rows. It must return a boolean value, if true, the row will be filtered.