Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

FDM to FDMEE migration utility

1,395 views

Published on

Can you save time using the FDM to FDMEE migration utility?

Published in: Technology
  • Be the first to comment

  • Be the first to like this

FDM to FDMEE migration utility

  1. 1. www.123olap.com
  2. 2. www.123olap.com Future Webinars  We have a large amount of webinar / training content available related to :  Essbase  FDMEE and Jython  OBIEE  HFM  DRM  If you’d like to receive a notification when we schedule webinars, please notify bash@epmclarity.com.
  3. 3. www.123olap.com Introductions  Bernard Ash - EPMClarity.com  EPM Gurus – 15+ years and counting  123Olap.com – premier Hyperion training provider:  Rudy Zucca, Eric Eriksen, Matthias Wohlen  Experienced and renowned consultants, NOT just trainers.  Konvergence.com  With Essbase or Without. EPM and Beyond.  Cloud or On-Prem.  Come find out about the “Save Essbase!” revolution.
  4. 4. www.123olap.com FDM to FDMEE Migration Utility
  5. 5. www.123olap.com What will we cover?  What version of the utility should I use? As of July 1, the latest version is 1.1.  When is it a good idea to use the Migration Utility? Can it really save time?  What will it migrate?  What will it NOT migrate?  Mapping considerations  Does it work on SQL server installations?  Do I have to know ODI to use it?  Migrate more than one FDM Classic application.
  6. 6. www.123olap.com Is it a Good Idea?  When is it a good idea to use the Migration Utility?  Can it really save time?  What will it migrate? - The migration utility is almost always faster than doing a migration (rewrite) and always less error-prone. - How many of each class of artifacts do you have ? Locations, Import Formats, Rules, Validation Entities, Check Rules, Sources, Targets, etc. - The migration utility will bring all these artifacts over for you. For large implementations, it could take 6 months or more to move over all the requisite artifacts which is tedious and very error-prone.
  7. 7. www.123olap.com What will it migrate? - Create the integration with the Target - Period and Category Mappings - Locations - Import Formats - Validation Entities and Validation Rules - Logic Groups - Mapping - Data - Data Load Rules - Integration Options
  8. 8. www.123olap.com What will it NOT migrate?  User Security  Object Security  Scripts of all kinds, including those in check reports.  Custom Reports  Control Group Locations  Task Flows  Certifications & Assessments
  9. 9. www.123olap.com Do we have to convert to Jython?  You will have to convert VBScript to Jython manually. No, there is currently no wizard for this.  Technically, this is how it is supposed to work in FDMEE 11.1.2.4 (see table below): Jython VBScript Import Jython ONLY NOT SUPPORTED Mapping Jython & SQL NOT SUPPORTED Event Supported Supported Custom Supported Supported
  10. 10. www.123olap.com Conversion to Jython -All or Nothing.  You want to convert to Jython b/c :  You will spend more time trying to use poorly documented VBScript syntax in FDMEE than you would just writing the Jython. It is a different object model in FDMEE than it was in FDM.  Most if not all docs and forums for FDMEE are in Jython, NOT VBScript.  Very few if any people are doing anything in VBScript in FDMEE  For maintenance, you don’t want you administrators (or consultants) to have to support more than one standard.  VBScript is old technology
  11. 11. www.123olap.com Documentation Oracle: http://docs.oracle.com/cd/E57185_01/e pm.1112/fdm_migration.pdf Pay close attention to the concept of source and target and note that FDMC stands for FDM Classic
  12. 12. www.123olap.com Mapping Considerations 1. Compared to FDM Classic, the Multi Dimension mapping type handles the most common reason to use mapping scripts and is more efficient. This can elminate the need for existing FDM Scripts. 2. Multi-star mappings not supported in FDMEE. For example - *.* 3. •Mapping scripts can be in SQL or Jython. Since Jython runs one row at a time, SQL is much better for performance.
  13. 13. www.123olap.com Prerequisites  SQL Server - Not by any means a showstopper but this utility works with less troubleshooting if your FDM and FDMEE repositories were and are in Oracle  ODI – Yes, it helps to know ODI but it’s not a showstopper if you aren’t an ODI expert.
  14. 14. www.123olap.com Migrating from Multiple Applications  Duplicate names FDMEE does not allow duplicate names for key artifacts. In the case you have multiple FDM applications (which could use the same name for an artifact), the migration utility lets you add a prefix to FDM artifacts. This way, you will avoid duplication issues during migration and it’s easier to keep track of where each migrated artifact came from.  For example, if you have two FDM applications both having a location called “US_West”, you can use a prefix which create in FDMEE two artifacts: one named ”Prefix1_US_West” and the other “Prefix2_US_West”.
  15. 15. www.123olap.com Delimiters – watch out  File delimiters FDMEE just supports comma (,), pipe (|), exclamation (!), colon (:), semi-colon (;) and tab. Any other delimiter used in legacy FDM will be converted to comma (,). Watch out! this change will force modifications in source files as well.
  16. 16. www.123olap.com Let’s Do the Migration  And when we’re done with the migration, let’s do a little Jython scripting in Eclipse.
  17. 17. www.123olap.com Migration Utility Steps 1. Install ODI Studio a) You need a 32 bit JDK b) Download ODI client installer – ODI Studio 11.1.1.7- don't try to install ODI Studio from EPM installer, it fails. I still keep the full ODI 11.1.1.7 installer. I think Oracle just keeps last 11g release which is 11.1.1.9. If you don't have the original installer files, I would suggest you raise a SR with oracle so they can provide you with the links to download it. c) Need Master and Work Repository connection information – contact DBA. This should already be set up if you have FDMEE installed b/c FDMEE uses ODI under the covers. 2. Install Migration Utility Scenarios into ODI client (see details on next slide) 3. Have legacy FDM repository copied into new world (not required but easier) 4. Configure Topology for Source (legacy) and Target (new FDMEE repository) 5. Run Migration Utility Scenarios 6. Check logs in Operator
  18. 18. www.123olap.com Introductions  Bernard Ash - EPMClarity.com  EPM Gurus – 15+ years and counting  123Olap.com – premier Hyperion training provider:  Rudy Zucca, Eric Eriksen, Matthias Wohlen  Experienced and renowned consultants, NOT just trainers.  Konvergence.com  With Essbase or Without. EPM and Beyond.  Cloud or On-Prem.  Come find out about the “Save Essbase!” revolution.
  19. 19. www.123olap.com

×