Migrating EIS Models and Metaoutlines

The Integration Services catalog you want to migrate to Essbase Studio does not have to reside on the same machine as Essbase Studio. The Integration Services catalog can be anywhere in an Integration Services-supported database on your network.

Even if the Integration Services catalog resides on the same machine as Essbase Studio, you must nevertheless create an ODBC DSN to the Integration Services catalog. This DSN must point to the database where the Integration Services catalog resides.

Note:

These procedures are addressed to database administrators and those who have a thorough knowledge of relational database concepts, Integration Services, and the relational databases in their working environment.

  To migrate Integration Services models and metaoutlines from Integration Services to Essbase Studio:

  1. If you have not already done so, access the EIS Catalog Migration dialog box. See Accessing the EIS Catalog Migration Dialog Box.

  2. In the EIS Catalog DSN text box, enter the ODBC DSN which points to the Integration Services catalog you want to migrate.

    Note:

    If the ODBC DSN to the Integration Services catalog does not exist, you must create the ODBC DSN. If the Integration Services catalog does not reside on the same machine as Essbase Studio, you must create an ODBC DSN on the machine where the Essbase Studio client is running. This DSN must point to the database where the Integration Services catalog resides.

  3. In the User text box, enter the user name for the EIS catalog; for example, tbc.

  4. Enter your password for the EIS catalog.

  5. Click the Fetch Models button.

    Essbase Studio accesses the Integration Services catalog and lists the models and metaoutlines in the catalog. Metaoutlines are grouped under their respective models.

  6. In the Models and Data Sets column, select the Integration Services models and metaoutlines you want to migrate.

    Note:

    You can migrate multiple models and metaoutlines.

  7. Click in the Data Source Connection column and, from the drop-down list, select the target relational database.

    Note:

    The target relational database should match the Integration Services target data source.

    Optional: You can create a target data source by clicking New Data Source and entering the name of the data source.

    Note:

    If you are migrating multiple models, you must select a target relational database in Essbase Studio for each model you are migrating.

  8. Click in the Catalog column and, from the drop-down list, select an Integration Services catalog.

    Note:

    If your relational database is Oracle, selecting a catalog is not required.

  9. Click in the Schema column and, from the drop-down list, select a schema.

    Note:

    If you are migrating multiple models, you must select a schema for each model you are migrating.

  10. In the Select Folder text box, enter the target folder in Essbase Studio.

    Optional: Click the Browse button to quickly find the target folder.

    Optional: You can create a folder by entering the name of the folder in the Select Folder text box.

    Note:

    The target folders are also listed in the Metadata Navigator in Essbase Studio.

  11. Click the Migrate button.

    View the migration progress in the Progress Information dialog box.

  12. Optional: To cancel the migration:

    1. Press Cancel.

    2. Delete any objects that are present in the target directory you specified in step 10.

Your OLAP models and metaoutlines are migrated from the Integration Services catalog to the Essbase Studio catalog. When the migration is complete, the model is displayed in the Metadata Navigator. If you created a data source, the name of the data source is displayed in the Source Navigator.