FME Server

The FME Server Data Store invokes a named FME Workspace deployed on an FME Server, accessible by your 1Integrate deployment.

By utilising FME Workspaces you can employ the wider format support of the deployed FME Server, and subsequently leverage these capabilities in 1Integrate.

The Workspaces can invoke any transformer, but must include at least one writer that writes data out into a format that 1Integrate supports.

Read and Write Support

Read	Write		FME Desktop Required
Read	Commit	Copy To	FME Desktop Required
			1

Data Support

Your Workspace writer must output in one of the formats listed below where the FME parameter "Description" and "Short Name" are mapped to their corresponding 1Integrate Data Store.

Geometry support in 1Integrate will depend on the format chosen. Select the 1Integrate Data Store in the table below to see the data support information and the File Data Store Parameters available.

FME Writer "Description"	FME Writer "Short Name"	1Integrate Data Store
CSV (Comma Separated Value)	CSV2	Delimiter Separated Values (DSV)
Esri Geodatabase (File Geodb Open API)	FILEGDB	Esri File Geodatabase
Esri Geodatabase (File Geodb)	GEODATABASE_FILE	Esri File Geodatabase
Esri Shapefile	SHAPEFILE	Esri Shapefile
Mapinfo TAB (MAPINFO)	MAPINFO	MapInfo Tab
OGC GeoPackage	OGCGEOPACKAGE	OGC GeoPackage

Key Information

The following should be taken into consideration:

A 1Integrate Data Store can only consume one FME workspace writer. To access multiple writers, use multiple Data Stores.
At a minimum, the Run and Read permissions are required to be set on the FME Repository for the user account being used to access FME server (as configured in the Username and Password parameters below).
You will not be able to manually stop a 1Integrate session that is opening data from an FME server while there are no available FME Server engines. If a timeout has been set the session will stop when the timeout period ends.
When publishing, ensure the Data Streaming service is enabled, with all writers you want to consume from 1Integrate included.
Be aware ESRI Shape files cannot be consumed by FME's "Generic (Any Format)" reader when provided through 1Integrate. Use the Esri Shapefile specific reader format if Esri Shapefiles need to be consumed.
You may need to routinely clean-up the FME Server location into which your source files are being stored.
By default 1Integrate will always assume a 2D geometry is to be read.

Use the Read Geometries As parameter value that best represents the data set you will be consuming. If you do not select an option, excess geometries will be discarded and errors will occur for non-spatial classes.

Note: Each FME Server Data Store can only support a single Read Geometries As selection. For example XYZM data would need two FME Server Data Stores, one with XYZ and one with XYM options selected.

FME Workspace Set-up

The workspace should consist of the following items, performing actions in the following order:

(Optional) A Reader or FeatureReader to ingest the file uploaded by 1Integrate.
(Optional) Transformers to perform the actions in FME.
(Required) A Writer in a format supported by 1Integrate, see Data support for more.

Note: You cannot use a FeatureWriter to write out to 1Integrate.

Example: Ingesting Point Cloud data into 1Integrate

In this example you have a Point Cloud data set, which does not have conventional 1Integrate Data Store support.

For this, you would need to ingest the Point Cloud data into your FME workspace, utilise FME transformers to convert the data into a supported 1Integrate format such as OGC Geopackage, and then a use a writer to output the correct format.

The workspace may look as follows:

A Point Cloud reader e.g. PCD .
A transformer, to convert the point cloud into points and multipoints that can be exported out into GeoPackage e.g. PointCloudCoercer.
An OGC GeoPackage writer e.g. OGCGEOPACKAGE.

Parameters

Read and Commit

Parameter	Description
FME Server URL	The URL for your FME Server.
FME Repository Name	The Repository name in your FME Server containing the workspace you want to invoke.
FME Workspace Name	The workspace name in your FME Server. You must specify the workspace to use regardless of if there are multiple workspaces or only one present. Note: The name must match those listed in your FME Server, e.g.: `My_Workspace_1.fmw`.
FME Writer Name (Optional)	The name of the writer that you are using in the workspace. The following writer names, taken from the FME Short Name parameter, are supported for each writer type: Note: When specifying the writer a number must be included at the end of the name, in the format `SHORTNAME_$N`. DSV = `CSV2_1` Esri File Geodatabase (Open API Writer) = `FILEGDB_1` Esri File Geodatabase (FME Writer) = `GEODATABASE_FILE_1` Esri Shapefile = `SHAPEFILE_1` MapInfo Tab = `MAPINFO_1` OGC Geopackage = `OGCGEOPACKAGE_1` In a workspace with more than one writer present, specify the writer you wish to use. For example, the second OGC Geopackage writer added would be `"OGCGEOPACKAGE_2`" Note: By default, the first writer that 1Integrate detects (which is always the first writer created on the workspace) will be used for the specified workspace.
Username	FME Server username.
Password	FME Server Password.
Source File	The optional input file to upload to the FME Workspace. Note: This could be the file to be transformed by the workspace into a file based Data Store that 1Integrate can read. See Data Support for more information on these formats.
FME Workspace Source Data Parameter	This is required when the FME workspace expects to read from a file, if no file is to be uploaded, leave blank. When set, this needs to be the published Parameter Identifier of the FME Workspace parameter that 1Integrate should upload the data to, prior to invoking the Workspace.
Upload to FME Server Resources	Select to upload to the Resources folder on the FME server. If selected, the upload will be made to the location set in the FME Source Data Location or, if there is no value provided, to the default location. By default any uploads will be sent to a temporary directory inside the `$(FME_SHAREDRESOURCE_SYSTEM)`. If unchecked, uploads are made to the workspace itself, with the file being accessible only through the REST API. Your workspace should have the credentials embedded to access this.
FME Source Data Location	If no location is selected, the default location will be used.
FME Workspace Additional Parameters	Pass in additional FME Workspace parameters with a comma separated list e.g.: `parameter_1=15,parameter_2=17` Example: Maximum Records In a published workspace a parameter exists named `MAX_RECORD_PER_CLASS`, which indicates how many items are transformed per class. In this example you have decided you want to restrict this to a single item. To make use of this parameter you would have to set the following string as an FME Workspace Additional Parameters: `MAX_RECORD_PER_CLASS=1`.
File Data Store Parameters	If you have additional 1Integrate file Data Store parameters, you can pass these in here. Note: The parameters must match those of the 1Integrate parameters for the Data Store in question. Example: FME Workspace producing a DSV file The DSV Data Store in question has a header line you need to skip and that the file has a "geometry" field with WKT XYZM, data where the Z coordinate is not required. For this, you could set the following parameters: `Number of header lines to skip=1,Spatial data fields=geometry,Spatial data type=WKT,"For X, Y, Z, M data"=IGNORE_Z`.
Coordinate Reference System	This parameter can be used to specify a Coordinate Reference System (CRS) code of the input data. This will not re-project the data, but allows its current CRS to be defined (e.g to enable multiple data stores to open where one does not have a CRS defined). Note: Coordinate Reference System parameters are required in a session that will write data to Oracle. See Coordinate Reference System for more information on when this is required.
Read Geometries As	Set the correct dimensions to be read by 1Integrate from the FME workspace. Note: A single Data Store will read only the geometries you select and any additionally held data will be lost. You cannot mix geometric and non-geometric data.
Request Timeout in Seconds	Set a timeout value in seconds for requests to the FME Server. If a request reaches this threshold the open data task will fail, and in return will fail the session.