3 Migrate from Oracle BI Enterprise Edition

When your target environment is ready, capture the information you want to migrate and copy it to Oracle Analytics Cloud.

Task Description More Information
Check your target is ready for migration and take a backup Verify that the required users and groups are available in your target service and take a snapshot in case you need to roll back. Back Up Your Target Service Before Migration

Export content from the source

Delete any old content in Oracle BI Enterprise Edition that you don't need anymore and then capture the content you want to migrate to Oracle Analytics Cloud.

Export Content from Oracle BI EE 11g

Export Content from Oracle BI EE 12c

Edit database connections and clean up your semantic model .rpd file

Update connection strings in your semantic model .rpd file and remove the content you don't want to migrate.

Clean Up and Reconfigure Your Semantic Model .rpd File

Import content on the target

Sign in to the target system and import the content.

Import Content from Oracle BI EE 11g

Import Content from Oracle BI EE 12c

Reconfigure service settings Verify various administrative settings on the target service.

Configure Service Settings

Activate deliveries

Disable deliveries in Oracle BI Enterprise Edition and start delivering content from the target service.

Restore and Enable Delivery Schedules

Back Up Your Target Service Before Migration

Verify that your target Oracle Analytics Cloud is ready for migration and then take a snapshot in case you need to roll back the service to its pre-migration state.

  1. Sign-in to the target Oracle Analytics Cloud.
  2. Verify that the users and roles you imported are available.
    1. Navigate to Console, and click Users and Roles.
    2. Click the Users tab and then the Roles tab to verify the users and roles.
  3. Take a backup of the target Oracle Analytics Cloud.
    1. Navigate to Console, and click Snapshots.
    2. Click Create Snapshot.
    3. For description, enter "Snapshot before content migration" or something similar.
    4. Select Everything, and then click Create.

Export Your Content

The way you export content from Oracle BI Enterprise Edition depends whether you're migrating from Oracle BI Enterprise Edition 11g or Oracle BI Enterprise Edition 12c.

Export Content from Oracle BI EE 11g

Delete old content in your catalog and semantic model .rpd file and then use the Oracle BI Enterprise Edition 11g migration utility to capture the content you want to migrate to Oracle Analytics Cloud.

  1. In Oracle BI Enterprise Edition, delete old content in your catalog and semantic model .rpd file.

    Oracle recommends that you delete old content before you migrate to Oracle Analytics Cloud. Migration is the perfect time to audit your content and delete any folders and content that you don't need anymore.

  2. Download the Oracle Analytics Cloud migration utility.
    1. In Oracle Analytics Cloud, navigate to Console, and then click Snapshots.
    2. Click the Page menu Page menu , select Migrate, then Download BI EE 11g Migration Utility. Follow the instructions to save the migration-tool.jar file locally.
  3. Copy the JAR file for the migration utility that you just downloaded to your Oracle BI Enterprise Edition 11g environment.
  4. In your Oracle BI Enterprise Edition 11g environment, run the migration-tool.jar file:

    Usage:

    java -jar migration-tool.jar out oracle_home domain_home instance_home_optional export_jar_location

    For example:

    java -jar migration-tool.jar out /u01/app/oracle/bi /u01/app/instance/domains/example.com/myDomain /u01/app/instance/BIInstance /tmp/myBIEE11gContentBundle.jar
    The tool exports your content to a JAR file. In this example, the file is named myBIEE11gContentBundle.jar.

Export Content from Oracle BI EE 12c

Delete old content in your catalog and semantic model .rpd file and then use the WLST command exportarchive to capture the content you want to migrate to Oracle Analytics Cloud in a BAR file.

Note:

When you run this command, Oracle BI Enterprise Edition goes into maintenance mode to limit write-access during the export process.

  1. In Oracle BI Enterprise Edition, delete old content in your catalog and semantic model .rpd file.

    Oracle recommends that you delete old content before you migrate to Oracle Analytics Cloud. Migration is the perfect time to audit your content and delete any folders and content that you don't need anymore.

  2. Run the WLST command exportarchive.sh.
    Use the syntax:
    [DOMAIN_HOME]/bitools/bin/exportarchive.sh <service instance key> <export directory>

    Where:

    • service instance key - Typically, the service instance key is ssi.
    • export directory - Destination directory for the BAR file you want to export.
    For example:
    [DOMAIN_HOME]/bitools/bin/exportarchive.sh ssi /tmp
  3. Navigate to the export directory to locate the BAR file named ssi.bar.
    The BAR file is exported to a sub-directory under the export directory that you specified. For example, if you specified/tmp, you'll find the BAR file under a sub-directory with a name similar to this:
    /tmp/1599066229133/ssi.bar

Clean Up and Reconfigure Your Semantic Model .rpd File

You must reconfigure data source connection information and clean up your semantic model .rpd file before you migrate content from Oracle BI Enterprise Edition to Oracle Analytics Cloud.

  • Reconfigure connections to your data.
  • Remove objects you no longer need or don't want to migrate to Oracle Analytics Cloud.
  • Remove or disable objects that Oracle Analytics Cloud doesn’t support. If you have done so already, read Feature Availability and Comparison.

To edit the semantic model .rpd file:

  1. Download the latest Developer Client Tool for Oracle Analytics Cloud and the .rpd file from Oracle BI Enterprise Edition that you want to migrate.
    1. Download and install the latest Developer Client Tool for Oracle Analytics Cloud from:
    2. Download the latest .rpd file from Oracle BI Enterprise Edition.
  2. Use the latest Developer Client Tool to open the .rpd file you want to migrate.
  3. Update database connection information.
    If you configured Data Gateway to enable access to your on-premise database or you moved your data to an Oracle Cloud database you need to reconfigure your database connections.
    1. Navigate to the Physical Layer pane, select the database connection you want to edit, and open the Connection Pool dialog.
    2. Edit the connection details In Data Source Name.

      If your .rpd file connects to multiple databases, ensure that the settings for each connection pool are correct.

  4. Delete unused database connections that you don't need anymore.
  5. Clean up initialization block information:
    1. Verify that initialization blocks point to the correct data source.
    2. Disable or delete unused initialization blocks that you don't need anymore.
    3. Remove any initialization blocks for authentication and authorization (set values for USER, ROLES or GROUP session variables).
  6. Review any semantic model or session variables.
  7. Disable subject areas that you don't want to expose in Oracle Analytics Cloud or that won't have a working connection.

    If connection information is missing, users see the message Fetch subject areas failed error when they view subject areas in Oracle Analytics Cloud.

  8. Use Consistency Check Manager to run a global consistency check.
  9. Save the changes to your .rpd file.
  10. Make a note of the password that you set for the .rpd file.

Import Your Content

The way you import content from Oracle BI Enterprise Edition depends whether you're migrating from Oracle BI Enterprise Edition 11g or Oracle BI Enterprise Edition 12c.

Import Content from Oracle BI EE 11g

Upload the JAR file containing the content you want to migrate to Oracle Analytics Cloud.

  1. Upload your Oracle BI Enterprise Edition 11g bundle and restore the content on Oracle Analytics Cloud.
    1. In Oracle Analytics Cloud, navigate to Console and click Snapshots.
    2. Click the Page menu Page menu , select Migrate, then Upload and Restore BI EE11g Migration Bundle.
    3. Click Select to navigate to the migration bundle (JAR file) containing the content you want to migrate.
    4. Enter the password for the semantic model .rpd file included in the JAR file.
      It's important to enter the correct password here. Content migration fails if the password you enter doesn’t match the password required to access the semantic model.
    5. Click Upload and Restore.

    Allow a few minutes for the content to upload and refresh through your system. The time it takes depends on the size of your content bundle. Sign out, then sign back in after approximately 15 or 20 minutes to see the new content and inherit newly restored application roles, if any.

  2. Upload the updated semantic model .rpd file to Oracle Analytics Cloud.
    1. Navigate to Console and click Snapshots.
    2. Click the Page menu Page actions menu and select Replace Data Model.
    3. Use Select to locate the semantic model .rpd file that you want to upload.
    4. Enter the password for the file.
    5. Click Replace.
  3. Verify that the content you uploaded is available.

Import Content from Oracle BI EE 12c

Import and restore the BAR file you exported from Oracle BI Enterprise Edition on Oracle Analytics Cloud.

  1. Sign-in to Oracle Analytics Cloud.
  2. Click Console.
  3. Click Snapshots.
  4. Import the BAR file.
    1. Click the Page menu Page actions menu and select Import.
    2. Use Select to locate the BAR file (.bar) that you want to upload.
    3. Enter the snapshot password.
      This is the password that you set for the semantic model .rpd file. Or the default password Admin123.
  5. Restore the content.
    1. Select the snapshot that you just uploaded.
    2. Click Snapshot Actions Snapshot actions menu and select Restore.
    3. For Restore, select Custom and then deselect Data Model and Subject Areas.
    4. Click Restore.
  6. Upload the modified semantic model .rpd file.
    1. Click the Page menu Page actions menu and select Replace Data Model.
    2. Use Select to locate the semantic model .rpd file that you want to upload.
    3. Enter the password for the file.
    4. Click Replace.

Configure Service Settings

Take some time to review various settings on the target Oracle Analytics Cloud and configure as required.

  1. Sign-in to the target Oracle Analytics Cloud and navigate to Console.
  2. Click Users and Roles, and verify all the application roles that you want are available on the Application Roles page.
  3. Click System Settings, then verify and configure these advanced settings as required.

    In Oracle Analytics Cloud, you can configure only the properties that are exposed on this page; you can't customize any other property values manually or otherwise.

    See Configure Advanced Options.
  4. Click Mail Server to configure the email server you want to use for deliveries.
  5. Click Extensions to verify or upload plug-ins and extensions for any custom visualization types or custom data actions that you need.
  6. Click Virus Scanner to configure the virus scanner you want to use.
  7. Click Safe Domains to verify or register domains that are safe to use with Oracle Analytics Cloud.
  8. Click Maps to verify or upload custom map layers and backgrounds for data visualizations.
  9. Verify the map configuration for analyses and dashboards on the Manage Map Data page (Classic Administration).
  10. Reconfigure usage tracking, if required.

Restore and Enable Delivery Schedules

When you restore content from a snapshot or migrate content from a different environment, delivery information is restored but it isn’t activated right away. Initially, restored deliveries are disabled. Click the Edit option to re-activate them.

  1. In the Oracle Analytics Home page, click the Navigator, and then click Console.
  2. Click Monitor Deliveries.
  3. To restore deliveries, click the Action menu for the page and select Restore Deliveries.
    Click OK to confirm. Recently restored deliveries display Disabled icon Disabled.
  4. To activate a delivery, click the Action menu for the delivery, and select Enable.

    If necessary, click Edit to redefine the delivery schedule.