To import data you first have to create an import definition. The import definition advices the Application Server where it can find the data to be imported and how this data shall be processed during import.
Import definitions can be created on-the-fly or can be persisted as import templates for repeated execution.
Import templates are import definitions that are persisted on the Application Server in the context of a domain. You will typically create import templates when you intend to repeatedly execute that import definition with different or changed data sources.
Import templates can either be private or public. Private import templates are visible only for the user who created them. Public import templates are visible to all users who have domain permission Read (0) on the domain the import template is associated with. To create modify or delete public import definitions users must have the Manage import definitions (20) permission.
Setting |
Description |
Settings for stored import definitions (only used when persisting the import definition as stored import definition) |
|
Name |
Name of the import definition. This can be empty for on-the-fly imports. |
Grouping path |
The path that can be used by clients to display stored import definitions in a tree-like structure. |
Description |
Description of the import definition. |
Private |
If set the stored import definition will be private to the user who created it. |
Origin domain |
The domain that the stored import definition is associated with. Note that an import definition might be associated with one domain, but might still import data for another domain. |
Table 1: Settings for import templates
An import definition will always import data into one specific domain. I.e. if the import creates new features those features will always belong to the same domain, if the import searches for existing features to update it will only search in that domain (see Feature matching for more details).
An import definition consists of:
•Specification of import type
•Name and description of the import definition (only for stored import definitions)
•Specification of import sources (e.g. files, databases)
•Specification of common settings (settings available for all imports disregarding the import type, General import settings for more details)
•Specification of import settings specific to the chosen import type
•Specification of the import sources from which data is imported
