Migrate from Oracle BI Enterprise Edition

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.

Sign-in to the target Oracle Analytics Cloud.
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.
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

If you use Oracle Oracle BI Enterprise Edition 11g, Oracle recommends that you export your content to Oracle Analytics Server and then use a snapshot to migrate your content to Oracle Analytics Cloud.

For more information, see:

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.

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.
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
```
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:

Download the latest client tools for Oracle Analytics Cloud and the .rpd file from Oracle BI Enterprise Edition that you want to migrate.
1. Download and install the latest client tools for Oracle Analytics Cloud from:
  
  http://www.oracle.com/technetwork/middleware/oac/downloads/oac-tools-4392272.html
  
  For instructions, see Download and Install Oracle Analytics Client Tools.
2. Download the latest .rpd file from Oracle BI Enterprise Edition.
Use the latest Model Administration Tool to open the .rpd file you want to migrate.
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.
Delete unused database connections that you don't need anymore.
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).
Review any semantic model or session variables.
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.
Use Consistency Check Manager to run a global consistency check.
Save the changes to your .rpd file.
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

If you haven't done so already, migrate content from Oracle Oracle BI Enterprise Edition 11g to Oracle Analytics Server and then use a snapshot to import the content to Oracle Analytics Cloud.

For more information, see:

Import Content from Oracle BI EE 12c

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

Sign-in to Oracle Analytics Cloud.
Click Console.
Click Snapshots.
Import the BAR file.
1. Click the Page 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.
Restore the content.
1. Select the snapshot that you just uploaded.
2. Click Snapshot Actions and select Restore.
3. For Restore, select Custom and then deselect Data Model and Subject Areas.
4. Click Restore.
Upload the modified semantic model .rpd file.
1. Click the Page 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.

Sign-in to the target Oracle Analytics Cloud and navigate to Console.
Click Users and Roles, and verify all the application roles that you want are available on the Application Roles page.
See Add Members to Application Roles.
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.
Click Mail Server to configure the email server you want to use for deliveries.
See Set Up an Email Server to Deliver Reports.
Click Extensions to verify or upload plug-ins and extensions for any custom visualization types or custom data actions that you need.
See Manage Custom Plug-ins.
Click Virus Scanner to configure the virus scanner you want to use.
See Set Up a Virus Scanner.
Click Safe Domains to verify or register domains that are safe to use with Oracle Analytics Cloud.
See Register Safe Domains.
Click Maps to verify or upload custom map layers and backgrounds for data visualizations.

See Add Custom Map Layers.
Verify the map configuration for analyses and dashboards on the Manage Map Data page (Classic Administration).
See Set Up Maps for Dashboards and Analyses.
Reconfigure usage tracking, if required.

See Track Usage.

Restore and Enable Delivery Schedules

When you restore content from a snapshot or migrate content from a different environment, delivery schedules defined for agents, analyses, and dashboards in the snapshot aren’t restored or activated right away. When you’re ready to restore deliveries on your system, you can decide whether to enable or disable delivery schedules on your system. This is useful as you might not want to immediately start delivering content.

For example, if you're restoring a production environment, you probably want to restart deliveries as soon as possible. Whereas in a test environment, you might prefer to disable deliveries after restoration and activate them at a later date.

In the Oracle Analytics Home page, click the Navigator, and then click Console.
Click Monitor Deliveries.
To restore deliveries, click the Action menu for the page and select Restore Deliveries.
Select whether to restore and activate deliveries or restore deliveries only. Select one of the following:
- Maintain Delivery Schedule Status
  
  All delivery schedules maintain their status (enabled or disabled).
  - Existing delivery schedules remain unchanged.
  - New delivery schedules created during the restore process inherit the schedule status that’s defined in the corresponding agent, analysis or dashboard.
  For example, this option is useful when you restore deliveries in a production environment where you want deliveries to be active immediately.
- Disable Delivery Schedules for New Deliveries
  
  Delivery schedules that are created during the restore process for agents, analyses, and dashboards are disabled. Existing delivery schedules remain unchanged.
  
  For example, this option is useful when you restore deliveries in a test environment where you don’t need to activate deliveries immediately.
- Disable All Delivery Schedules And Delete All History (Not recommended)
  
  All delivery schedules are disabled during the restore process and any delivery history is deleted.
  - Existing delivery schedules are disabled.
  - New delivery schedules created for agents, analyses, and dashboards during the restore process are disabled.
  - Historical delivery details no longer available.
  This option is not recommended. If you do select this option, you must manually enable delivery schedules for all agents, analyses, and dashboards.
Click Restore.
To activate a delivery, click the Action menu for the delivery, and select Enable.

To activate multiple deliveries at once, select Shift + click or Ctrl + click to select all the deliveries you want to activate, then right-click and select Enable.

If necessary, click Edit to redefine the delivery schedule.