Output Connection

The output details connection is used when copying data to a new set of tables or classes in the external data source.

Note: Output mapping is only used for Copy To tasks in a session. If using a Commit task then the inverse of the input mapping is used and the output mapping is ignored.

The Copy Input Details button can be used to copy existing details from the Input Details tab.

When data has been written to a data store type other than Oracle or SQL, the results will be available to download by clicking Download for the Destination Files.

When data is read from Oracle and written to FME, if no FME coordinate system is defined, the FME data store will attempt to find one corresponding to the EPSG code. You can specify the CRS to be used in the FME Coordinate Reference System field in the Output Details of any FME data store. It should be set to the short name of an FME coordinate system such as BritishNatGrid. In most cases, it should not be necessary to specify the coordinate system.

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

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

Enter Output Connection Details

  1. Navigate to the Data Stores page.

  2. From the Navigation Pane, select the data store to be configured.

  3. Open the Output Details tab.

  4. Select the required Data Store Type from the drop-down menu.

    Note: Different parameters will appear depending on which Data Store Type is selected.

  5. Enter the details for your selected Data Store Type.
  6. Click Save.
  7. Click Test Connection to verify the data can be accessed.

Output Details Parameters

When setting up an Output 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.

ClosedAutodesk AutoCAD DWG/DXF

ClosedBentley MicroStation Design (V8)

ClosedComma Separated Value (CSV)

ClosedEsri Enterprise Geodatabase

Note: In order to use the Esri Enterprise Geodatabase datastore format, ArcMap (64-bit) and FME Desktop Esri Edition must be installed and a licence for each available on the machine(s) running 1Integrate (and all session queues). For full details, see the FME knowledge centre.

Parameter Description
Destination Database

The name of the database.

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.

Export FME Log File Download the FME log file created during export (to help identify any errors).
Reverse coordinate axis order (y, x) Reverse the x and y co-ordinate values.
Connection File Select a connection file (.sde) to be used to connect to the Esri Enterprise Geodatabase.
Dataset The name of the dataset from which features will be retrieved.
Server The name of the Geodatabase server used to read data from the dataset.
Instance Name

The name of the Enterprise Geodatabase instance.

Note: The typical value for systems with a single ArcSDE instance is esri_sde8.

User ID User ID of the Enterprise Geodatabase user.
Password Password for the User ID.
Persistent Connection Select to keep a connection open and save the processing time required to make and break a database connection.
Commit Transactions After Write

Specifies whether to commit transactions at the end of each write operation.

Note: Only valid when the versioning type is set to "transactions".

ClosedEsri File Geodatabase

ClosedEsri Shape

ClosedMapInfo Tab

ClosedMicrosoft SQL Server Spatial

ClosedOracle

ClosedPostGIS