FirstGen XML: Existing source

Adding a new XML entity to an existing source

Select radio button: To existing Source

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

Select Source Name from dropdown. This is the source that the new entity will be added to.

Entity Level: Specify level of data management

(see System Settings: Level Control)

The default level for the source will populate in the dropdown and this can be modified and applied to new entities.

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 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. Users are then able to choose Primary/Secondary XSDs that specify, validate, and enforce element structure. When Source or Sample Files are attached, appropriate metadata is extracted and applied to the environment. Sample XML files similarly prescribe and enforce metadata environment. XSDs and Sample XML files are uploaded from the user's local machine.

• XML File Path: Type in the exact file path to the (originating source) entity, ending with the exact file name and file format suffix. Select File Browser to explore Local Server directory for filepath to data.
• Primary XSD File: A primary XSD file will describe a parent (root) element at the highest level.
• Secondary XSD File: Additional XSD files describe additional child elements, typically one XSD for each namespace. Valid XSD metadata is mandatory for the environment to be setup.
• Sample XML file for validation: In the absence or XSDs or in addition to XSDs, a sample XML file can validate and enforce the schema of the XML structure.

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 caret icon to the left of the entity name to display and choose fields.

Qlik Catalog Internal file formatType

Options include:

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

Qlik Catalog Stored Format Type step is skipped for single server 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.