NextGen XML: New source

Adding a new XML entity to a new source

Select radio button: To new Source

This will kick off the Add Data wizard to create a new source and define a new entity within the source.

Source Connection

Choose Connection: Choose a source connection that will connect to an external XML source on the required protocol (XML ingest is supported for ADLS, FTP, HDFS, KAFKA, LOCALFILE, S3, SFTP, WASB, WASBS) This example uses XML connection type to a file source using LOCALFILE protocol.

Add New Source Name: Configurable. This is the Source that the new Entity will be added to.

Default Entity Level: Specify data management level

(see AdministrationSystem Settings: Level Control)

Select Source Hierarchy: Configurable. Choose from dropdown.

Inbound Protocol: Pre-defined Inbound Protocol auto-populates for the selected Source Connection

Base Directory: Pre-defined. This is the directory where data will be stored in File System. [This value is specified in core_env property: localfile.base.dir.source.connection. This property limits access and browsing to subdirectories of the specified location.]

Groups: Select Group(s) requiring access from the dropdown options. At least one group must be added for the data to be discoverable.

Click Next.

File Format

File Path:  Enter the file path to the (originating external  source) entity, ending with the file name and file format suffix. The external source in this example is stored at the local host running the application.

Data Format Specification: XML Filepath is required.

• XML File Path: Type in the exact file path to the (originating source) xml, ending with the exact file name and file format suffix. Select the file browser to explore local server directory for file path to data.

Select Next

Select Entities & Fields

The elements described within the XSDs display; this step allows the user to select the entities to generate (with ability to rename). To select fields for the entities, expand the arrow to the left of the entity name to display and choose fields.

Data Catalog Stored Format Type

Options include:

• AVRO
• ORC
• ORC_ALL_STRING
• PARQUET
• PARQUET_ALL_STRING
• TEXT_TAB_DELIMITED

Qlik Catalog Stored Format Type step is skipped for single node environments where Stored Format Type is always TEXT_TAB_DELIMITED.

Load Data to the Entity(s). Once the Entity has been saved, navigate to Entities screen in Source to load the data.

Select Load from the More dropdown.