File Library

Bernard Ash, EPM Clarity

Do you want to upgrade to FDMEE but you’re too afraid of the large number of FDM artifacts you have in FDM (locations, data load rules, import formats, validation rules, validation entities, etc.)? It would be very time-consuming and therefore expensive and error-prone to migrate all those artifacts from FDM to FDMEE. The bad news is that artifacts such as custom reports and VBScripts will not be migrated; you will have to convert those artifacts by hand. However, the vast majority of your standard artifacts such as locations, data load rules, import formats, mappings, etc. can be migrated using Oracle’s FDM to FDMEE migration utility that Oracle released last fall. The migration utility is implemented using ODI but with a little coaching; even if you don’t know ODI, you could take what would ordinarily be a six-month migration/“upgrade” effort and condense that into a one- to two-month effort. Also, if there is enough time, we could give you an introductory tutorial on how to convert VBScript to Jython and/or how to create a custom report in FDMEE. This will be a live, hands-on demo.