Batch Parser
Batch parser is for picking up batch exports from the file system. The typical use case is picking up batches from scanners.
Integration Connection
Configuration
-
Connection Name: This is a unique name given to the connector instance upon creation.
-
Description: A description of the connector to help identify it better.
-
Authentication Connection: Leave blank. This connection does not require authentication
Job Configuration
Batch Parser
-
Ingestion Location: Location to pick up files.
-
This can be a file path: /mnt/drop or a URI /service/pickup
-
File Pattern: Pattern for file matcher.
-
Example *.xml
-
-
Parser (Required): Select a parser type.
-
Pre Parse Commands: Command to be run before parsing the document.
-
This is meant for cases where you have zip files and need to decompress before processing.
-
-
Server And Port: Server and port for REST content retrieval.
-
Username: Username for REST content.
-
Password: Password for REST content.
Parser Formats
XML
<ROOT>
<INFO>
<DOCUMENT_NAME>
5012421.pdf
</DOCUMENT_NAME>
<COURIER_NAME>
M2M_DHR_20190703121505
</COURIER_NAME>
</INFO>
<DOCUMENT DOCUMENT_DATE="03/04/2019">
<INDEX_FIELDS>
<FIELD NAME="DOCUMENT_NUMBER" VALUE="501242" />
<FIELD NAME="ID_M3M" VALUE="DLP_501242_2019" />
</INDEX_FIELDS>
</DOCUMENT>
</ROOT>
API Keys
Batch Parser Connector: Read=true: Write=false: MIP=false
Repo (Read) Specs
Key |
Description |
Data Type |
---|---|---|
ingestion_directory | Ingestion Location | String |
file_pattern |
File Pattern |
String |
parser_class |
Parser Type |
String |
pre_parse_command |
Pre Parse Command |
String |
server_and_port |
Server And Port |
String |
user_name |
User Name |
String |
password |
Password |
String |
Looking to process unstructured data? We can help.