Loading Data Formats

1Integrate can handle spatial data from a number of sources such as an Oracle database, Esri Shapefiles or MapInfo Tab files.

PostGIS prerequisite (WebLogic only)

If you are planning on using PostGIS to read data, an additional driver is required:

postgresql-[version].jar

For specific versions, please refer to the Release Notes for your installation.

Installing the Driver

  1. Download the driver postgresql-[version].jar from the PostgreSQL website.

  2. In the bin directory of the 1Integrate WebLogic domain, create a file called setUserOverrides.cmd

  3. Edit the setUserOverrides.cmd file, adding the location of the postgresql driver as part of the PRE_CLASSPATH:

    set PRE_CLASSPATH=%locationOfTheDriver%\postgresql-[version].jar

  4. Restart all servers, including Admin Server and Node Manager for the pre-class path to be loaded.

Using FME

To access other formats such as DWG files or Esri Enterprise geodatabases, 1Integrate uses functionality from Safe Software's FME. To use this capability, you must have FME Desktop installed and available to 1Integrate, with an FME Desktop license available for use.

Note: In order to be editable, tables must have a primary key defined. You can read data from tables that do not have primary keys, but you will not be able to write data back to those tables.

To allow 1Integrate to access data that is only available via an FME license, use the following procedure, depending on your operating system:

ClosedConfigure FME on Windows

Note: The following steps are only necessary if FME has not already been added to the system or user’s PATH environment variable in Windows. However, when using WildFly with AdoptOpenJDK ensure the plugins path is defined, as detailed below.

Wildfly

On Windows, set the FME_HOME directory to the path in bin\standalone.conf.bat by adding the following lines to the top of the file:

Note: The .bat file is located in the 1Integrate directory e.g. \1Integrate[version]\wildfly[version]\bin

Using AdoptOpenJDK

Note: As of 1Integrate 2.7, 1Integrate only supports AdoptOpenJDK on WildFly installations. Please see the Release Notes for additional information.

@rem add FME to PATH

set PATH=[FME path];[FME path]/plugins;%PATH%

Where [FME path] is the location where FME is installed (e.g. C:\PROGRA~1\FME).

WebLogic

  1. Stop the WebLogic server(s).

  2. Create a new file called setUserOverrides.cmd within the bin directory of your domain, if it does not already exist (i.e.[domain name]/bin/setUserOverrides.cmd).

  3. Edit the contents of the file to contain the following:

    @rem add FME to PATH

    set PATH=[FME path];%PATH%

    Where [FME path] is the location where FME is installed (e.g. C:\PROGRA~1\FME).

  4. Alter the permissions on setUserOverrides.cmd to allow the WebLogic user to access the file.

  5. Start the WebLogic server(s).

ClosedConfigure FME on Linux

Wildfly

Set the FME_CORE directory to the LD_LIBRARY_PATH in bin/standalone.conf by adding the following lines to the top of the file:

# add FME to LD_LIBRARY_PATH

export LD_LIBRARY_PATH="[FME_CORE_PATH]:$LD_LIBRARY_PATH"

Where [FME_CORE_PATH] is the location of the fme/fmecore/ directory.

WebLogic

  1. Stop the WebLogic server(s).

  2. Create a new file called setUserOverrides.sh within the bin directory of your domain (i.e.[domain name]/bin/setUserOverrides.sh).

  3. Edit the contents of the file to contain the following:

    # add FME to LD_LIBRARY_PATH

    export LD_LIBRARY_PATH="[FME_CORE_PATH]:$LD_LIBRARY_PATH"

    Where [FME_CORE_PATH] is the location of the fme/fmecore/ directory.

  4. Alter the permissions on setUserOverrides.sh to allow the WebLogic user to execute the file (e.g. chmod 750 setUserOverrides.sh).

  5. Start the WebLogic server(s).

Esri Enterprise Geodatabase (only required for WebLogic installations)

The following changes need to be made to the setUserOverrides.cmd (Windows) or setUserOverrides.sh (Linux):

  • Add the SDEHOME path variable
  • Add the database client path to the PATH
Note:

SDEHOME must not contain spaces in the path. Make sure that short paths are enabled on the operating system (e.g. PROGRA~2) or copy the following dll files (from C:\Program Files (x84)\ArcGIS\DesktopV\bin64) to a location without spaces :

  • sde.dll
  • sg.dll
  • pe.dll
  • xerces_c3_1.dll

ClosedExample (Windows)

SQL Server Spatial Data (only required for WebLogic installations)

An additional driver is required in order for FME to read Microsoft SQL Server data.

ClosedConfigure SQL Server for spatial data support

  1. Download the following driver from Microsoft, and place it in an accessible location: sqljdbc4-[version].jar (for versioning, please see the release notes for your installation).

  2. In the bin directory of the 1Integrate WebLogic domain, create a file called setUserOverrides.cmd

  3. Edit the setUserOverrides.cmd file, adding the location of the sqljdbc driver as part of the PRE_CLASSPATH:

    @rem include the sqljdbc driver as part of the pre class path

    set PRE_CLASSPATH=%locationOfTheDriver%\sqljdbc4-[version].jar

    @rem set FME path as part of the path

    set PATH=C:\PROGRA~1\FME\;%PATH%

  4. Restart all servers, including Admin Server and Node Manager for the pre-class path to be loaded.