XSD Connector

How to configure and run the XSD connector (Desktop mode only) for importing XML schema (.xsd) structures into a NoSQL source — object mapping, path/error-handling parameters, and release history.

2 min read

This article describes how XSD connector works.

This connector is available in the following modes:

Desktop mode ✅SaaS Online mode ❌

Connector scope

An XSD file describes the structure and metadata of an XML file.

The connector allows you to import objects into a NoSQL source from one or more XSD files (.xsd file) stored in a directory accessible by the connector.

The extracted objects and their correspondences are detailed in the following table:

XSD ObjectDataGalaxy ObjectComments
SchemaDocumentSchema defined by the XSD file or the file name
Element / AttributeFieldObject properties If the property is a complex object containing child properties, a Sub-Structure will be created in DataGalaxy

Step 1 : Installation

  • Extract the connector archive in the directory of your choice
  • Download the XSD plug-in from the portal and copy it into the /lib directory of the connector

Step 2 : Run XSD connector

  • After starting the connector, access to Dictionary connectors:
  • If it has been correctly installed, the XSD plug-in appears in the list
  • The following information is requested:
ParameterMandatoryDescription
PathYesPath to the directory that contains the XSD files (.xsd files)
Ignore errorsNoOption to ignore the presence of badly structured files or files that cannot be interpreted, in order to continue processing when an error is detected. When unchecked, the presence of an error file blocks the import process (default operation).

Once this information is filled in, you can test the connection and start the import.

Technical information

Link to XSD documentation: https://www.w3.org/TR/xmlschema11-1/

Releases

DatePlugin VersionDataGalaxy releaseDesktop Connector version (minimum)Description
29/09/20265.0.1v3.423.06.2.2New internal implementation
16/07/20244.0.0v3.59.05.0.1Migrated from java 11 to java 17

Read more

Related articles

Was this page helpful?