Incredibly Simple Things You Can Do in FDMEE – Tip 4

Tip 4 – Using Lifecycle Management

Want to save a file back up of FDMEE for disaster recovery purposes? Need to synchronize your FDMEE apps across environments? FDMEE makes this easy with Lifecycle Management.

Lifecycle Management – commonly referred to as “LCM” – provides a mechanism for migrating application content across environments and even operating systems. You can access Lifecycle Management via Shared Services.

  1. In Shared Services, navigate to your FDMEE application.
  2. Select your FDMEE application to display a list of migration artifacts.
  3. Choose your artifacts and click the Export button to name and generate your LCM package.
  4. When the export is complete, your LCM package (a collection of XML files) will appear in the File System group in Shared Services.
  5. From there, you can download the LCM zip file to a network share.
FDMEE and Lifecycle Management

FDMEE and Lifecycle Management







  1. Hi,

    One thing I’ve noticed is that the LCM actually is doing a merge when you import across environment. I don’t want that to happen, as it leaves old mappings in our Test system, which should get replaced with the new ones from the Production system.

    Do you know a way around this? Meaning do an LCM import wiping out existing mappings?

    • Good question. Currently, there isn’t a replace mode for importing data load mappings via LCM.

      Suggestion # 1 – In FDMEE, you can delete all of the data load mappings for a particular dimension before using LCM to refresh the dimension.

      Suggestion # 2 – You can use the importmapping Windows batch/ UNIX shell script to import data load mappings from a flat file. The importmapping script has a replace mode.


Submit a Comment

Your email address will not be published. Required fields are marked *