Migrating FDM Metadata/ Data Between Environments

The goal of this document is to go over the steps to migrate FDM applications from one environment to another. These steps assume the application already exists in the target environment.

There are two steps used to migrate FDM application metadata and data from one environment to another.

  1. Migrate the Metadata/Mapping From One Environment to Another

To perform this process, FDM Workbench is used to export the metadata from the source environment and the workbench is used to import the metadata in the target environment.

a)   From the source environment, choose File/Export, give the export file a name, choose a location
to save the file to and click on the “Save” button.
b)   In the Metadata screen, click the “Select All” button, or check the individual items needed, and click on the “Options” tab (if you need to export mappings).
c)   Check the “Export Maps with Locations” checkbox and click “OK”.
⮚   This will generate the metadata export file to import into the target environment.
d)   Login to the application in the target environment and choose File/Import.
e)   Select the export file generated from the source environment and click “Open”.
f)   Select the items to import or “Select All” and click on the “Options” tab.
g)   Check the “Import Maps with Locations” checkbox and click “OK”.
⮚   This will import all metadata and mapping into the application.
  1. Copy the Application Data

There are two methods for this step that can be used. A database copy can be performed from the source to target database, or the FDM application folder can be copied from source to target server.

Method 1.

a) Have a database administrator make a backup of the source and target FDM application database.
b) Have a database administrator copy the data from the source application database to the target application database.

Method 2.

a) Map the FDM application folder of the target server from the source server.
b) Copy the FDM application data folder from the source environment to the mapped folder in the destination environment, overwriting or merging files.

Benjamin Johnson

Senior IT Consultant – The EGP Family of Companies