FME Workspaces compatible with 1Exchange

There are number of requirements on the FME Workspace that are needed in order for an exchange to work.

1Exchange will run the Workspace and provide two parameters. Each of these will be set to a folder in FME Server Resources, within $(FME_SHAREDRESOURCE_DATA):

  • INPUT_FOLDER- This will be populated by 1Exchange.
  • OUTPUT_FOLDER- This will be populated by the FME Workspace.

INPUT_FOLDER

The Workspace can expect a number of files in the Input Folder, which will vary depending on whether you are downloading features or uploading changes. The INPUT_FOLDER is populated by 1Exchange.

ClosedInput: download features

Always Present:

  • job-metadata.xml - This is all of the metadata for a job as available in 1Plan (for information about 1Plan, please refer to Job Data Panel).

ClosedInput: Upload Changes

Always Present:

  • job-metadata.xml - This is all of the metadata for a job as available in 1Plan (for information about 1Plan, please refer to Job Data Panel).

  • Any changes that have been uploaded.

Note: This upload will not include the originally extracted data for reference.

OUTPUT_FOLDER

The Workspace can expect a number of files in the Output Folder, which will vary depending on whether you are downloading features or uploading changes. The OUTPUT_FOLDER is filled by FME Workspace.

ClosedOutput: download Features

Always Present:

  • summary.json - This will communicate the success of processes and any failures to 1Exchange. For more information about the summary.json file, please refer to FME summary.json Structure.

    Note: The summary.json is the only name that will be recognised and is case sensitive.

  • If successful, any features extracted in the format the Workspace is responsible for.

ClosedOutput: upload Changes

Always Present:

  • summary.json - This will communicate the success of processes and any failures to 1Exchange. For more information about the summary.json file, please refer to FME summary.json Structure.

    Note: The summary.json is the only name that will be recognised and is case sensitive.

Manual Conflict Resolution

Applying conflicted changes via an FME Server Workspace is not currently supported.

We recommend:

  • Adopting a strategy of avoiding conflicts in Oracle Workspaces if using an FME Workspace with 1Exchange.
  • Any FME download Workspace looks for the failureType parameter in the job metadata. If this is set to CONFLICT, trigger an FME Workspacefailure to indicate that an unexpected conflict has arisen.

Note: For further information about manual conflict resolution using FME with your 1SMS deployment, please contact 1spatial support.