3 Migrate Your Oracle BI Cloud Service Instances

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

In most cases, after you restore the snapshot, you must modify your semantic model connections to get them to work in Oracle Analytics Cloud. The way you do this depends whether you used Data Modeler or BI Administration Tool to manage your semantic models in Oracle BI Cloud Service. Instructions on how to edit semantic model connections, together with other tasks you must do to complete migration are listed in the table.

Task	Description	More Information
Understand snapshot options	Understand what you can include or exclude when you take a snapshot.	Understand Snapshot Options
Check your target is ready for migration and take a backup	Verify that the required users and roles are available in your target service and take a snapshot in case you need to roll back.	Back Up Your Target Service Before Migration
Take a snapshot of the source	Capture the content you want to migrate on the source system.	Take a Snapshot on the Source
Download the snapshot locally	Download the snapshot that you want to migrate to your local file system.	Download the Snapshot
Import the snapshot to the target	Sign in to the target system and import the snapshot.	Import the Snapshot on the Target
Restore the snapshot content	Select the newly imported snapshot in the list of saved snapshots and restore the content in the snapshot. After restoring the snapshot you must perform additional tasks to complete the migration. For example, you must edit your semantic model connections, verify application role assignments, and more.	Restore the Snapshot on the Target
Edit semantic model connections for Data Modeler	(Mandatory if you use Data Modeler) Review, edit, and save all your database connections to activate them in Oracle Analytics Cloud. Reconfigure the Default Connection if you used this in Oracle BI Cloud Service.	Edit Semantic Model Connections for Data Modeler
Edit semantic model connections	(Mandatory if you use BI Administration Tool to manage semantic model connections for Oracle BI Cloud Service and you migrated your data from Oracle Cloud Infrastructure Classic to Oracle Cloud Infrastructure) Edit the semantic model .rpd file, add the new connection string, and then upload the updated semantic model to the target system.	Edit Connections in the .rpd File and Upload the Semantic Model
Migrate data files	Use the Data Migration utility to migrate and restore data files from another environment.	Migrate File-based Data
Verify application role assignments	Verify that users and groups in your target service have the correct application roles in Oracle Analytics Cloud.	Verify and Configure Service Settings
Reconfigure search crawl users	Change the name of the users configured to index semantic model content and catalog content.	Verify and Configure Service Settings
Verify and configure service settings	Verify various administrative settings on the target service.	Verify and Configure Service Settings
Activate deliveries	Enable deliveries to start delivering content from the target service.	Restore and Enable Delivery Schedules

Understand Snapshot Options

When you take a snapshot in Oracle BI Cloud Service you capture everything in your environment. When you restore the snapshot on Oracle Analytics Cloud you can restore everything in the target Oracle Analytics Cloud or only restore the content in the snapshot.

• Replace Everything - Replaces your entire environment using information in the snapshot.

  Any content type excluded from the snapshot is restored to its default state in the target environment, that is, "no content". For example, if you decided to set up a virus scanner before restoring the snapshot, the new virus scanner configuration is removed.

  There are some exceptions; if the snapshot doesn’t contain any file-based datasets, plug-ins, or extensions these items are left unchanged in Oracle Analytics Cloud.

• Replace Snapshot Content Only - Everything that's in the snapshot is restored. Any content type excluded from the snapshot remains unchanged in the target environment.

  For example, if you set up a virus scanner before restoring the snapshot, your virus scanner configuration remains.

• Custom - You select the content you want to restore. If you don’t want to restore certain content types, exclude them before you restore.

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.

Migrate Your Content

Capture the content you want to migrate in a snapshot and restore that snapshot on your target Oracle Analytics Cloud.

1. Sign-in to the source Oracle BI Cloud Service.
2. If you're using Data Modeler to build and manage semantic models, you must remove spaces from database connection names before you take your final snapshot.
   1. Navigate to Console, and click Connections.
   2. Check whether any of your connection names include a space.
   3. If required, edit connection names, removing all spaces, and save the connection.
   4. Allow some time for new names to refresh through the system before moving on to the next step.
3. Save the entire environment you want to migrate to a snapshot.
   1. Navigate to Console, click Snapshots and Models, and then New Snapshot.
   2. For Description, enter "Migrate content to Oracle Cloud Infrastructure" or something similar.
   3. Click OK.
4. Download the snapshot locally.
   1. Select the snapshot that you want to download.
   2. Click the Manage Snapshot menu, and select Download.
      You're asked to create a password for the snapshot. Don’t forget this password. You'll need this password when you upload the snapshot on the target system.
   3. Enter and confirm a password for the snapshot. The password must contain at least 8 characters.
   4. Click OK.

      The snapshot downloads as an Oracle Business Intelligence archive file (.bar).

5. Sign-in to the target Oracle Analytics Cloud and import the snapshot.
   See Import the Snapshot on the Target.
6. Restore the snapshot, and select Replace Everything.

   See Restore the Snapshot on the Target.

   After restoring the snapshot you must perform additional tasks to complete the migration. For example, you must reconfigure your semantic model connections, verify application and roles, very and configure various settings, and activate deliveries.

7. Edit your semantic model connections.
   See Edit Semantic Model Connections for Data Modeler or Edit Connections in the .rpd File and Upload the Semantic Model.
8. Migrate data files manually if the restore process fails to migrate them.
   See Migrate File-based Data.
9. Verify application role assignments and other system settings.
   See Verify and Configure Service Settings.
10. Activate deliveries.
    See Restore and Enable Delivery Schedules.

Edit Semantic Model Connections for Data Modeler

If you used Data Modeler in Oracle BI Cloud Service, you must make some updates to the database connection information you migrated to Oracle Analytics Cloud to get your semantic models to work in Oracle Analytics Cloud. For example, if you used the Default Connection in Oracle BI Cloud Service you must recreate this connection in Oracle Analytics Cloud. If you migrated any other database connections, you must activate these one-by-one to start using them in Oracle Analytics Cloud.

1. Sign-in to the target Oracle Analytics Cloud and navigate to Console.
2. Activate all the semantic model connections migrated to Oracle Analytics Cloud.
   1. Click Connections.
   2. Edit and save each connection migrated from Oracle BI Cloud Service to activate the connection.
      If the connection details have changed, you can edit these at the same time. For example, if you moved your data from a database on Oracle Cloud Infrastructure Classic to a database on Oracle Cloud Infrastructure.
3. If any of your semantic models used the Default Connection in Oracle BI Cloud Service, reconfigure this connection in Oracle Analytics Cloud to point to the database on Oracle Cloud Infrastructure that contains the data you migrated from Oracle Database Cloud Schema Service.
   1. Determine the connection string for the new database on Oracle Cloud Infrastructure.
   2. In Console, click Connections.
   3. Click Create, and specify the name as DefaultConnection or some other name if you prefer.
   4. Enter connection details for the new database.
      In Oracle Analytics Cloud, you can't include spaces in the connection name, so the connection name in Oracle Analytics Cloud (DefaultConnection) doesn’t exactly match the name in Oracle BI Cloud Service (Default Connection). This means you must reconfigure any semantic model using Default Connection to point to the new connection named here.
   5. In Data Modeler, change the connection for any semantic models that previously used Default Connection.
      See Open Data Modeler and Connect a Model to a Different Database.
   6. Validate, and publish any models that you change to synchronize the new connection. See Use Data Modeler.

Edit Connections in the .rpd File and Upload the Semantic Model

Sometimes you must reconfigure the database connection information inside your source semantic model .rpd file after you migrate to Oracle Analytics Cloud on Oracle Cloud Infrastructure. For example, this is required when you move your data from Oracle Cloud Infrastructure Classic to Oracle Cloud Infrastructure because the connect string for the new database is different. If you need to edit the semantic model .rpd file, you must upload the updated semantic model to Oracle Analytics Cloud immediately after content migration.

Note:

These instructions only apply if you used BI Administration Tool to manage semantic models in Oracle BI Cloud Service. If you use Data Modeler, you edit connection information for semantic models through Console.

1. Determine the connection string for the new database on Oracle Cloud Infrastructure.
2. If you haven’t done so already, 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.

3. Use the latest Model Administration Tool to open the semantic model .rpd file that you used in Oracle BI Cloud Service .
4. Navigate to the Physical Layer pane, select the database connection you want to edit, and open the Connection Pool dialog.
5. Edit the connection details In Data Source Name, to specify the new database on Oracle Cloud Infrastructure.
6. Save the changes to the semantic model .rpd file.
7. Upload the updated semantic model .rpd file to the target Oracle Analytics Cloud instance.
   Navigate to the Console, click Snapshots, click the Page menu, and then click Replace Data Model.

Migrate File-based Data

Users upload data files, such as spreadsheets, to Oracle BI Cloud Service to create datasets. When you migrate to a new Oracle Analytics Cloud environment, you can take this file-based data with you. Oracle Analytics Cloud offers a CLI utility (command-line interface) that enables you to move your data files to the new location. The snapshot CLI utility also moves any map-related plug-ins and extension files that users might upload for their data visualizations.

The CLI utility allows you to move data files directly from one environment to another in a single step. Or if you prefer, you can download your file-based data to a ZIP file and then upload the data files to your chosen environment in two separate steps.

1. Check your environment details.

   • Verify that the source Oracle BI Cloud Service and the target Oracle Analytics Cloud both include the latest update (5.3 or later). The CLI utility isn't available in earlier versions.

     If you're not sure, ask your Oracle representative.

   • Check that the source and target system are both up and running, and Oracle Analytics Cloud is configured with valid storage credentials.

   • Check your local environment. You need Java 1.8 or later to run the CLI utility.

   • Make sure you can access the source environment and the target Oracle Analytics Cloud from the local environment where you plan to run the CLI utility.

   • Verify the name and location of the snapshot that you downloaded earlier containing your file-based data. For example, /tmp/20190307095216.bar.
2. Download the CLI utility.
   1. In your target Oracle Analytics Cloud, click Console and then click Snapshots.
   2. Click the Page menu , select Migrate, then Download Data Migration Utility.
      Follow the instructions to save the migrate-oac-data.zip file locally.
3. Unzip migrate-oac-data.zip.

   The ZIP file contains three files:

   • migrate-oac-data.jar
   • config.properties
   • readme
4. If you want to migrate data files stored in your source environment directly to the target in a single step, configure the section [MigrateData] in config.properties.

   [MigrateData]
   # Migrate data files from a source Oracle BI Cloud Service environment (BICS) to a target Oracle Analytics Cloud environment.
       # Specify the source environment as Oracle BI Cloud Service.
         SOURCE_ENVIRONMENT=BICS
       # Source Oracle BI Cloud Service URL. For example: https://sourcehost.com:443 or http://sourcehost.com:9704
         SOURCE_URL=http(s)://<Source Oracle BI Cloud Service Host>:<Source Port> 

       # Name of a user with Administrator permissions in the source environment. For example: SourceAdmin
         SOURCE_USERNAME=<Source Administrator User Name>
       # Location of the source snapshot (.bar file). For example:  /tmp/20190307095216.bar
         BAR_PATH=<Path to Source Snapshot>
       # Target Oracle Analytics Cloud URL. For example: https://targethost.com:443 or http://targethost.com:9704
         TARGET_URL=http(s)://<Target Oracle Analytics Cloud Host>:<Target Port>
       # Name of a user with Administrator permissions in the target environment. For example: TargetAdmin
         TARGET_USERNAME=<Target Administrator User Name>

5. If you want to first download data files from your source Oracle BI Cloud Service to your local environment and subsequently upload the data files to the target Oracle Analytics Cloud environment, configure sections [DownloadDataFiles] and [UploadDataFragments] in config.properties.

   [DownloadDataFiles]
   #Download Data Files: Download data files from Oracle BI Cloud Service storage to a local repository
       # Specify the source environment as Oracle BI Cloud Service.
         SOURCE_ENVIRONMENT=BICS
       # Source Oracle BI Cloud Service URL. For example: https://sourcehost.com:443 or http://sourcehost.com:9704
         SOURCE_URL=http(s)://<Source Oracle BI Cloud Service Host>:<Source Port>

       # Name of a user with Administrator permissions in the source environment. For example: SourceAdmin
         SOURCE_USERNAME=<Source Administrator User Name>
       # Location of the source snapshot (.bar file). For example:  /tmp/20190307095216.bar
         BAR_PATH=<Path to Source Snapshot>
       # Local data file directory. Make sure you have enough space to download the data files to this directory. For example: /tmp/mydatafiledir 
         DATA_FRAGMENTS_DIRECTORY=<Data Files Directory>
        # Data fragment size. Data files are downloaded in fragments. Default fragment size is 500MB.
         MAX_DATA_FRAGMENT_SIZE_IN_MB=500

   [UploadDataFiles]
   #Upload data files: Upload data files to the target Oracle Analytics Cloud. 
       # Target Oracle Analytics Cloud URL. For example: https://targethost.com:443 or http://targethost.com:9704
         TARGET_URL=http(s)://<Target Oracle Analytics Cloud Host>:<Target Port>
       # Name of a user with Administrator permissions in the target environment. For example: TargetAdmin
         TARGET_USERNAME=<Target Administrator User Name>
       # Local directory containing the data files you want to upload. For example: /tmp/mydatafiledir
         DATA_FRAGMENTS_DIRECTORY=<Data Files Directory>
       # Location of the source snapshot (.bar file). For example:  /tmp/20190307095216.bar
         BAR_PATH=<Path to Source Snapshot>

6. Run the migrate-oac-data.jar file in your local environment.

   Syntax:

   migrate-oac-data.jar [-config configfile] [-d] [-help] [-m]  [-u]

   Where:

   • -config configfile : Name of the config.properties file

   • -d : Downloads data locally using information in config.properties

   • -help : Displays help

   • -m : Migrates data using source and target information in the config.properties file

   • -u : Uploads data using information in the config.properties file

   For example, to migrate data files in a single step:

   java -jar migrate-oac-data.jar -m -config config.properties

   For example, to download data files locally:

   java -jar migrate-oac-data.jar -d -config config.properties

   For example, to upload data files:

   java -jar migrate-oac-data.jar -u -config config.properties

7. Sign in to your target Oracle Analytics Cloud.
8. To expose the data files in Oracle Analytics Cloud, you must restore the snapshot that you used to migrate the rest of your content for a second time. This time, you must select the Custom restore option.
   1. Open the Console, and click Manage Snapshots.
   2. Select the snapshot containing your data files.
   3. Select the Custom restore option, and then select the option File-based data.
      Deselect all other options.
   4. Click Restore.
9. Verify that your data files are available.

Verify and Configure Service Settings

Many settings are migrated for you. Take some time to review various configuration options on the target Oracle Analytics Cloud and reconfigure settings, if required.

1. Sign-in to the target Oracle Analytics Cloud and navigate to Console.
2. Verify that all the application roles that you want are available and they're assigned to the correct users and roles.
   1. In Console, click Users and Roles.
   2. Click Application Roles.
   See Add Members to Application Roles.
3. Reconfigure search crawl users.
   The user name that is configured immediately after migration includes the tenancy prefix required for Oracle BI Cloud Service. You must remove the tenancy prefix because this isn’t required in Oracle Analytics Cloud.
   1. In Console, click Search Index.
   2. On the Data Model tab, click the Set User search icon for the User to Run Crawl As field, and select the name of a user with administrative permissions in Oracle Analytics Cloud.
      For example, you might change the user name from <Tenancy>.MyAdminUser to MyAdminUser. If you prefer, you can select the name of a different user.
   3. Click the Catalog tab, and repeat the steps to select a search crawl user for catalog content.
4. In Console, click Mail Server to verify your email server configuration.
   See Set Up an Email Server to Deliver Reports.
5. In Console, click Safe Domains to verify your safe domains are configured.
   See Register Safe Domains.
6. In Console, click Maps to verify map configuration for data visualizations.
   See Add Custom Map Layers.
7. In Console, click Extensions to verify your custom plug-ins and extensions.
   See Manage Custom Plug-ins.
8. In Console, click Virus Scanner to configure a virus scanner configuration.
   See Set Up a Virus Scanner.
9. In Console, click System Settings to verify and configure advanced options available on this page.
   See Configure Advanced Options.
10. In Classic Administration, click Manage Map Data to verify map configuration for analyses and dashboards.
    See Set Up Maps for Dashboards and Analyses.

Restore and Enable Delivery Schedules

When you restore content from a snapshot or migrate content from a different Oracle BI Cloud Service, delivery schedules defined for agents, analyses, and dashboards in the snapshot aren’t restored or activated right away in Oracle Analytics Cloud. 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.

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.
4. Select whether to restore and activate deliveries or restore deliveries only.

   • 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.

     • All existing delivery schedules are disabled.
     • New delivery schedules created for agents, analyses, and dashboards during the restore process are disabled.

     If you select this option you must manually enable delivery schedules for all agents, analyses, and dashboards.

5. Click Restore.

   Click OK to confirm.

6. 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.

7. To prevent clutter, delete any history or deliveries you don't want anymore. Click the Action menu for the delivery:

   • Delete History — Removes historical information that you don't want to see any more.

   • Delete Delivery — Deletes the delivery and all its history.