Description:
This step sets the path to the output XML file.
Inputs
- filePath – input file path
- xmlRootName - XML root element name
- xmlNodeName - XML node element name
- variableOrGlobal - variable/global to hold the virtual file path
Returns
- None
Usage:
Prerequisite:
The ETL process engine service should be running to execute the ETL definitions.
Example:
Let’s build and execute the “clsInputXMLDef” example.
- Create a new definition named “clsInputXMLDef” and open it in designer mode.
- Drag “clsInputXML, clsTransformCase, and clsOutputXML” steps to the canvas.
- Connect the dots between the “clsInputXML” and other steps, as shown above.
- Define a variable or a global to hold the virtual path.
- Click the "clsInputXML" step to configure its "Required" properties. Provide a name for the step. Provide the path to the input XML file on the application server. Provide the XML node element name that contains all the data. Select the ETL data schema from the drop-down list. Note: The schema's column names should match those in the input file. Click the Save button. Click here to learn about the ETL Data Schema Designer.
- Click the "clsInputXML" step to view its "Optional" properties. Select the Show Schema button. The pop-up window displays the schema columns as shown below. This function helps to understand the schema at a glance.
- Click the "clsTransformCase" step to configure its "Required" properties. Enter the step name. Click the button to configure the transform list. Then click the Save button.
- Click the "clsTransformCase" step to configure the transform list. The configuration pop-up window appears. Click the Add Row (+) button to insert an empty row. Select the column name (string type) from the drop-down list. Select the case transformation type from the drop-down list. Click the Save button. You may add multiple rows for transformation using the Add Row button.
- Click the "clsOutputXML" step to configure its "Required" properties. Enter a name for the step. Enter the path to the output XML file on the application server. Click the Save button.
- Click the "clsOutputXML" step to configure its "Optional" properties. Enter the XML root element name. Enter the XML node name. Enter the variable or global reference to store the virtual output path. Click the Save button.
- The “Logging” configuration is necessary for documentation and also measures workflow progress and percent complete. This is achieved by configuring the step state and percent fields individually, as shown below. Configure the “Logging” using the following properties.
- Save the ETL definition, create a new instance, and then execute it. Render the ETL instance. Click the Items—Variables menu option to view the variable values. The “clsInputXML” step facilitates the transformation of the input file. The variable or global holds the output file’s virtual path as shown below.
- The input XML image is provided here for reference.
- The output XML image is provided here for reference.
Definition Sample:
You may download the sample definition(s) from the link provided and later import them (drag-and-drop) into your FlowWright ETL Definition (XML file) page.
Note: Please verify and complete the process steps for any missing configurations, such as file path references and database connections, after the import. Then, save the definition to confirm the changes.