1Exchange Configuration

1Exchange can make use of FME Server and Snowflake products to publish and import data. FME Server is the default deployment and is available for users with or without the Snowflake products configured.

FME Server

If using FME Server to export and import data from the Oracle database, the mapping between the Oracle schema and required data formats is defined by a Workspace. This Workspace is deployed within FME Server and is referenced from a 1Exchange Exchange policy.

Snowflake

1Exchange can also make use of two Snowflake components to publish and import GML data:

  • GO Publisher which is responsible for exporting from an Oracle feature schema to a GML file
  • GO Loader is responsible for loading the changed GML data back into the Oracle schema

If using GO Loader and GO Publisher to import and export GML data from the Oracle database, the mapping between the Oracle schema and GML is defined by a Product. These Products must be configured before installing [1SMS.

     Note: The translation files for each product must be stored next to the Installation file before installing 1SMS. If not, conflicts cannot be resolved.

     Note: In this instance, a Product refers to a configuration file that defines the way that data is published and imported using GO Loader and GO Publisher.

URL Locations

The 1Exchange administration page is available at: http:\\[host]:[port]/1exchange/admin/

The SOAP web service is located at: http://[host]:[port]/1exchange/soap/ExchangeService?WSDL

The REST web service is located at: http://[host]:[port]/1exchange/rest

Security Settings

To increase security, you can control which media types (MIME types) and file extensions are allowed to be uploaded. By default, the values are set to a wildcard (*) which allows any type.

ClosedSpecify a whitelist

  1. In the 1Exchange administration page, select the Security Settings icon from the toolbar:

    The 1Exchange admin buttons with the Security Settings icon highlighted.

  2. From here you can enter one item per line into the designated box to create a whitelist:

    • File Extensions

      E.g:

      zip

      jpg

      jpeg

    • Media Types (MIME types)

      E.g:

      application/zip

      image/jpeg

      text/plain

     Note: If you are trying to restrict any text file types, e.g. JSON, XML, TXT, be aware that the Media Type must be defined as text/plain, or these files will be rejected. Subsequently, you may decide to restrict the type of text files uploaded by defining extension types in the File Extensions Whitelist e.g. .JSON,.CSV,.XML

     Warning: Files can only be uploaded if both the extension AND Media Type is allowed from the respective whitelists. Specifying a * (wildcard) in either list means that any value is accepted.

     Note: If you want to place restrictions on file size, this must be configured in your application server:

  • For WebLogic this is a server setting in the WebLogic console.
  • In WildFly, this is maintained by editing the domain.xml.