Batch Parser

Batch parser is for picking up batch exports from the file system. The typical use case is picking up batches from scanners.

Connector Compatibility

Repo: No

Output: Yes

Content Service: No

Content Search: No

Manage In Place:

More info on connection types

Integration Connection

Every job requires an integration connection for both the source repository connection and the output connection. Also known as input an output connections. Their job is to query or crawl remote systems for files, folders, metadata, versions, and renditions. . In repo mode, it will retrieve list items and all of their relevant metadata from a list or library on the specified site. In output mode, the connection will write content and assign the mapped content type (from type mappings), or simply leave the new list item as a Document. Click here for more information on setting up an integration connection.

  1. Select integration and click on the new connection button.

  2. Enter the name and description of your connection.

  3. Select the connection type from the drop down list.

  4. Click Save on the Create Connection form.

  5. Click Save on the Edit Connection page.

There are no fields to configure in an integration connection.

Guide toIntegration connections

Job Configuration

A 3Sixty Job is the process of moving or syncing content (including versions, ACL's, metadata) from one CMS (content management system) to another. Add tasks to your job to have better control over how your data gets migrated. Click here for details on how to set up an integration job.

Guide to Integration jobs

  1. Select List Jobs under integration on the navigation menu or the dashboard

  2. Click the create job button

  3. In the New Job form

    1. Name the job

    2. Select Simple Migration from the job type drop down

    3. Select the Repository Connection

    4. Select the Output connection

    5. Select your Content Service Connection

      (Only required if you will be using Federation)

    6. Click Save to open the Edit Job page

    7. Fill in the configurations for the Repo and Output Configuration tabs

  4. Click save to save your new integration job

  1. Select Run and Monitor Jobs under Integration in the navigation menu

  2. Click the play button next to the job you want to run

  3. Click the refresh button to view your completed job status

    (Larger jobs will take longer to run)

Batch Parser Output Configuration

  • 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

Copy 
<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.