Developing a custom parser module
About the abstract parse method
After you implement the abstract parse method, the parser receives the full name (of the file to parse) as the first parameter and returns a DataSetList object containing data that has been extracted.
For example: The ETL is configured to access a Secure File Transfer Protocol (SFTP) folder and select files that match a certain pattern. The ETL framework will copy the selected files via SFTP to the local ETL engine disk and then, it will sequentially call the parse method of the defined custom parser for each file. This means that the ETL will:
- Call the parse method for the first file.
- Populate the output dataset with the result.
- Call the parse method for the second file.
- Append the result to the dataset, and so on.
After parsing each file and depending on configuration, the ETL framework will rename or move the parsed file.
Consider the following example:
Full example code
Here you can download the full code of the example presented: pm.
To develop a custom parser module
- Creating-a-custom-parser-module
- Editing-parser-code
- Activating-a-custom-parser-module
- (Optional) To store your ETL code in a secure location and share the code, see Saving-a-copy-of-an-Integration-Studio-project.
- (Optional) To debug the custom parser module, see Debugging-a-custom-parser-or-extractor-module.
Where to go from here
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*