You are here: Basic Steps > 2. Data Stores > Schema Mapping > Input Connection

Input Connection

Note: The Data Engineer role is required in order to configure Input Details (see Roles).

The Input Details tab of the Data Stores page is used to configure a connection to an external data store, from which you want to import data into 1Integrate.

Once the Input Details have been entered, Schema Mapping must be performed (see Input Mapping).

Enter Input Connection Details

Navigate to the Data Stores page.
From the Navigation Pane, select the data store to be configured.
Open the Input Details tab.
Select the required Data Store Type from the drop-down menu.

Note: Different parameters will appear depending on which Data Store Type is selected.
Enter the details for your selected Data Store Type.
Click Save.
Click Test Connection to verify the data can be accessed.

Input Details Parameters

When setting up an Input Connection, the Data Store Type you select will determine which parameters appear.

The following tables detail the parameters required for each available Data Store Type.

MapInfo TAB (MFAL)

Parameter	Description
Source Files (.tab)	Enter the location of your file, or click Upload to navigate to the file on your network. A .zip archive can be uploaded if more than one file is required.
Coordinate Reference System	Required if the data store will be used in a session that will write data to Oracle. This value is the Spatial Reference Identifier (SRID) in the form SRID=[NNNN], where [NNNN] is the Oracle SRID. Note: When data is read from FME and written to Oracle, if no Oracle-specific SRID is defined, the Oracle data store will attempt to find one corresponding to the EPSG code. EPSG codes are a standard way to describe geospatial coordinate system and are maintained by the European Petroleum Survey Group.
Import FME Log File	Click if you want to import log information from FME.
Allow invalid geometries	Select to enable automatic validation.
Fix ring direction and inclusion errors	Selecting this option will, where possible, correct polygons that do not correctly identify which rings form the outer boundary and which are holes or that have rings that do not conform to the OGC standard for clockwise/anti-clockwise direction.
Encoding
Clip to envelope
FME table password
Exposed attributes

Oracle

Parameter	Description
Username	Schema containing the required data.
Password	Password for the selected Username.
Net Service Name	The identifier with which Oracle or JBoss identifies this database.
Host	The name of the machine in which the metadata store is created.
Port	The port number of the host.
Service Name	The Oracle system ID (SID).
JNDI Location
Schema Name
Allow Invalid Geometries	Select to enable automatic validation.
Scale for Coordinate Data

Comma Separated Value (CSV)

Parameter	Description
Source Files (.csv, .gz, .txt)	Enter the location of your file, or click Upload to navigate to the file on your network. A .zip archive can be uploaded if more than one file is required.
Coordinate Reference System	Required if the data store will be used in a session that will write data to Oracle. This value is the Spatial Reference Identifier (SRID) in the form SRID=[NNNN], where [NNNN] is the Oracle SRID. Note: When data is read from FME and written to Oracle, if no Oracle-specific SRID is defined, the Oracle data store will attempt to find one corresponding to the EPSG code. EPSG codes are a standard way to describe geospatial coordinate system and are maintained by the European Petroleum Survey Group.
Import FME Log File	Click if you want to import log information from FME.
Allow invalid geometries	Select to enable automatic validation.
Fix ring direction and inclusion errors	Selecting this option will, where possible, correct polygons that do not correctly identify which rings form the outer boundary and which are holes or that have rings that do not conform to the OGC standard for clockwise/anti-clockwise direction.
Field names specified in file
Field separator
Encoding (e.g. UTF-8)
Field names after header
Skip lines
Skip footer
Strip quotes
Duplicate delimeters

Esri Shape

Parameter	Description
Source Files (.shp)	Enter the location of your file, or click Upload to navigate to the file on your network. A .zip archive can be uploaded if more than one file is required.
Coordinate Reference System	Required if the data store will be used in a session that will write data to Oracle. This value is the Spatial Reference Identifier (SRID) in the form SRID=[NNNN], where [NNNN] is the Oracle SRID. Note: When data is read from FME and written to Oracle, if no Oracle-specific SRID is defined, the Oracle data store will attempt to find one corresponding to the EPSG code. EPSG codes are a standard way to describe geospatial coordinate system and are maintained by the European Petroleum Survey Group.
Import FME Log File	Click if you want to import log information from FME.
Allow invalid geometries	Select to enable automatic validation.
Fix ring direction and inclusion errors	Selecting this option will, where possible, correct polygons that do not correctly identify which rings form the outer boundary and which are holes or that have rings that do not conform to the OGC standard for clockwise/anti-clockwise direction.
Convert attribute names to upper case
Treat measures as elevation
Encoding
Clip to envelope
Dissolve holes
Trim preceding spaces
Exposed attributes

Bentley MicroStation Design (V8)

Parameter	Description
Source Files (.pos, .fc1, .dgn)	Enter the location of your file, or click Upload to navigate to the file on your network. A .zip archive can be uploaded if more than one file is required.
Coordinate Reference System	Required if the data store will be used in a session that will write data to Oracle. This value is the Spatial Reference Identifier (SRID) in the form SRID=[NNNN], where [NNNN] is the Oracle SRID. Note: When data is read from FME and written to Oracle, if no Oracle-specific SRID is defined, the Oracle data store will attempt to find one corresponding to the EPSG code. EPSG codes are a standard way to describe geospatial coordinate system and are maintained by the European Petroleum Survey Group.
Import FME Log File	Click if you want to import log information from FME.
Allow invalid geometries	Select to enable automatic validation.
Fix ring direction and inclusion errors	Selecting this option will, where possible, correct polygons that do not correctly identify which rings form the outer boundary and which are holes or that have rings that do not conform to the OGC standard for clockwise/anti-clockwise direction.
Units mode
Units of Resolution (UOR) scale
Global origin of X in Units of Resolution (UOR)
Global origin of Y in Units of Resolution (UOR)
Global origin of Z in Units of Resolution (UOR)
Number of sub units per master unit
Number of Units of Resolution (UOR) per sub unit
Expand cells
Expand unnamed cells
Preserve cell inserts
Preserve unnamed cell inserts
Tag as text
Preserve curves
Elevation shift factor
Curve vertices
Trim down tags
Split multi-text
Explode dimension element
Read external reference files
Read external reference files to first level
Read external reference parent model
Read external references as elements
Explode multi-line
Read deleted elements
Schema include MSLINKS
Schema include FRAMME

Microsoft SQL Server Spatial

Parameter	Description
Source Database	The location of the data store.
Coordinate Reference System	Required if the data store will be used in a session that will write data to Oracle. This value is the Spatial Reference Identifier (SRID) in the form SRID=[NNNN], where [NNNN] is the Oracle SRID. Note: When data is read from FME and written to Oracle, if no Oracle-specific SRID is defined, the Oracle data store will attempt to find one corresponding to the EPSG code. EPSG codes are a standard way to describe geospatial coordinate system and are maintained by the European Petroleum Survey Group.
Import FME Log File	Click if you want to import log information from FME.
Allow invalid geometries	Select to enable automatic validation.
Fix ring direction and inclusion errors	Selecting this option will, where possible, correct polygons that do not correctly identify which rings form the outer boundary and which are holes or that have rings that do not conform to the OGC standard for clockwise/anti-clockwise direction.
Command timeout
Retrieve all schemas
Import host name
Import username
Import password
WHERE clause
Clip to envelope
Read cache size
Assume one SRID per column
Exposed attributes
Input spatial type is geography (default: geometry)
Input spatial column name