Uploading Data Models from Oracle BI Enterprise Edition

Administrators can upload data models built with Oracle BI Enterprise Edition to Oracle Analytics Cloud. After uploading a data model file (.rpd) to the cloud, content authors can then build data visualizations, dashboards and analyses in the usual way.

Note:

Administrators can use snapshots to migrate content, as well as data models from Oracle BI Enterprise Edition. See Migrating Snapshot Data.

About Uploading Oracle BI Enterprise Edition Data Models to the Cloud

If you’ve already modeled your business data with Oracle BI Enterprise Edition, you don't need to start from scratch in Oracle Analytics Cloud. Ask an administrator to upload your data model file to Oracle Analytics Cloud and start exploring your data through visualizations, analyses, and dashboards.

Oracle Analytics Cloud lets you upload a data model file with:

  • One or more data models

  • Connections to one or more instances of Oracle Database Cloud Service

You’ll need to validate your data model file and configure database connection details in Oracle BI Enterprise Edition.

When your administrator uploads a data model file from Oracle Analytics Cloud, existing data models (if any) are deleted and replaced with content from the uploaded file and Data Modeler is disabled. Data models uploaded from the file become available to content authors through the Subject Areas pane.

If model changes are required, metadata developers can use Oracle BI Administration Tool to edit the data model in the cloud.

Note:

If you want to copy reports and dashboards built in Oracle BI Enterprise Edition to Oracle Analytics Cloud you can do that too. See Uploading Content from a Catalog Archive in Visualizing Data and Building Reports in Oracle Analytics Cloud.

Getting Your Data Model File Ready

Take some time to ready your data model (the RPD file) for the cloud.

  1. Verify that you’re using Oracle BI Enterprise Edition 11.1.1.6 or later.
  2. Validate the data model file (the RPD file).
    Run consistency checks using Consistency Check Manager in Oracle BI Administration Tool.
  3. Verify that the data model file includes connection details to Oracle Database Cloud Service.

    Review the connection pool settings from Oracle BI Administration Tool:

    • Data source name must contain the full connect string for the Oracle Database Cloud Service where data is stored.

      You can’t specify a net service names here.

    • Call interface must be Oracle Call Interface (OCI).

    If your data model file connects to multiple Oracle Database Cloud Service instances, ensure that the settings for each connection pool are correct.

  4. Disable subject areas that you don't want to expose or that don'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 Data Visualization.

  5. Back up your Oracle Analytics Cloud service, including the current data model, in case you need to restore this version.

When the data model is ready, you can upload it to Oracle Analytics Cloud.

Uploading Data Models from a File (.rpd) Using Console

Administrators can upload data models built with Oracle BI Enterprise Edition to Oracle Analytics Cloud. After migrating data models to the cloud, content authors can visualize data in the usual way.

When you upload data models from Oracle BI Enterprise Edition, you delete existing data model information in Oracle Analytics Cloud and replace it with content in the data model file (.rpd). The data models you upload become available to content authors as subject areas.

You can also upload data model files from a file (.rpd) using Oracle Analytics Developer Client Tool.

  1. Verify the data model file (.rpd) and associated database connections.
  2. In Oracle Analytics Cloud, click Console.
  3. Select Service Administration - Manage Snapshots.
  4. Take a snapshot of the current data model in case you need to restore this version.
  5. Click Replace Data Model.
  6. Click Browse and select the data model file (.rpd) that you want to upload.
  7. Enter the password for the file.
  8. Click OK.
  9. Go to the Home page, click Data, and then Data Sets to see the data models that you uploaded, available as subject areas.
  10. Optional: If the data model file includes permissions and data filters, create matching application roles in Oracle Analytics Cloud for the data security to work in the cloud.
    1. Create application roles with exactly the same names as those defined in Oracle BI Administration Tool.
    2. Assign users (and user roles) to the application roles as required.

About Editing Data Models Uploaded from Oracle BI Enterprise Edition

Administrators use Console to upload data models from Oracle BI Enterprise Edition to Oracle Analytics Cloud. Once a data model is uploaded, metadata developers use Oracle Analytics Developer Client Tool to edit and deploy the data model. Users can then start exploring data through visualizations, analyses, and dashboards.

Pre-requisites

Typical Workflow for Using BI Administration Tool to Edit Your Data Model

Note:

In addition to uploading the data model, you must copy analyses and dashboards built in Oracle BI Enterprise Edition to Oracle Analytics Cloud. See Uploading Content from a Catalog Archive in Visualizing Data and Building Reports in Oracle Analytics Cloud.

Downloading and Installing Oracle Analytics Cloud Developer Client Tool

Download the Oracle Analytics Cloud Developer Client Tool if you want to edit data models in the cloud. For example, you might want to update a data model that you previously migrated to Oracle Analytics Cloud (for example, from Oracle BI EE 11g).

  1. Download the latest Oracle Analytics Cloud Developer Client Tool.

    1. Navigate to:

      http://www.oracle.com/technetwork/middleware/oac/downloads/oac-tools-4392272.html

    2. Click Accept license agreement.

    3. To start the download, click the latest Oracle Analytics Developer Client Tool link.

      If you’re not sure which version to download, ask your Oracle Analytics Cloud administrator.

  2. Install Oracle Analytics Cloud Developer Client Tool.

    1. From the downloaded ZIP file, extract the oac_bi_client-<version number and timestamp>-win64.exe file.
    2. In the local download area, double-click the oac_bi_client-<version number and timestamp>-win64.exe file to start the installer.

    3. Follow the on-screen instructions.

To start Oracle Analytics Cloud Developer Client Tool, from the Windows Start menu, click Oracle Business Intelligence Client, click <BI Client Home Name> , and then click Administration.

Connecting to a Data Model in the Cloud

Whenever you open, publish, or upload a data model to the cloud using Oracle Analytics Developer Client Tool, you’re prompted to specify connection details for your Oracle Analytics Cloud instance.

  1. In Oracle Analytics Developer Client Tool, choose an option to connect to your Oracle Analytics Cloud instance.
    For example, click File, then Cloud, then either Open, Publish, or Upload.
  2. Enter connection information for Oracle Analytics Cloud.
    Option What to specify
    User The user name of an Oracle Analytics Cloud administrator (a user with the BIServiceAdministrator application role).
    Password The password for the specified user.
    Cloud Enter bootstrap.
    Host name The Oracle Analytics Cloud URL link address without the /dv/ui part at the end of the URL. For example, https://oac123456-oacppacm12345.uscom-central-1.oraclecloud.com.

    To obtain your Oracle Analytics Cloud URL link address, in Oracle Cloud My Services, navigate to your Oracle Analytics Cloud instance, click Manage this instance, and copy the link address for Oracle Analytics Cloud URL.

    Port number

    Specify 443 for Oracle Analytics Cloud deployed with Oracle Identity Cloud Service.

    Specify 80 for Oracle Analytics Cloud deployed without Oracle Identity Cloud Service.

    Note: Check with your cloud service administrator that this port number has been opened.

    SSL

    Select this option.

    For the Trust Store value, click Browse and select the default JDK key store that that is bundled with JRE:

    <BI client domain home>\oracle_common\jdk\jre\lib\security\cacerts

    Refer to the Java key store documentation for the default Password.

    Proxy

    If you’re deploying Oracle Analytics Developer Client Tool on a machine in a proxy-enabled network, select this option. Ask your network administrator for the proxy server URL and Port number.

Expect the initial connection to take from 3–15 minutes, depending on the repository size.

Editing a Data Model in the Cloud

Use Oracle Analytics Developer Client Tool to edit a data model in Oracle Analytics Cloud.

Before you start, upload your local data model RPD file to Oracle Analytics Cloud. See Uploading a Data Model to the Cloud.
  1. In Oracle Analytics Developer Client Tool, click File, then Cloud, then Open.
  2. Enter connection information for Oracle Analytics Cloud. See Connecting to a Data Model in the Cloud.
  3. Update your model.
    1. Make changes to the model, as required.
    2. To validate your changes, click Tools, Show Consistency Checker, and then click Check All Objects.
    3. To save the changes locally, click File, and then click Save.
  4. To upload your changes to Oracle Analytics Cloud, click File, Cloud, and then click Publish.
To refresh or discard your changes, use the File submenu:
  • Refresh – Use this option to refresh your data model with the latest updates. If another developer has modified the data model, then you’re prompted to initiate a merge.

  • Discard – Use this option to cancel any changes that you’ve made to the data model in the current session.

Uploading a Data Model to the Cloud

Use Oracle Analytics Developer Client Tool to upload a data model RPD file to Oracle Analytics Cloud.

  1. In Oracle Analytics Developer Client Tool, open your data model file (*.rpd).
  2. From the File menu, click Cloud, then click Upload.
  3. Enter connection information for Oracle Analytics Cloud. See Connecting to a Data Model in the Cloud.
To make further changes, you simply connect to the cloud data model directly. You don’t have to edit the local RPD file and upload again. See Editing a Data Model in the Cloud.
To refresh or discard your changes, use the File submenu:
  • Refresh – Use this option to refresh your data model with the latest updates. If another developer has modified the data model, then you’re prompted to initiate a merge.

  • Discard – Use this option to cancel any changes that you’ve made to the data model in the current session.

Troubleshooting Oracle Analytics Cloud Developer Client Tool

Here’s some tips on troubleshooting connection issues in Oracle Analytics Developer Client Tool when you’re connecting to Oracle Analytics Cloud.

Use these log files on the client machine:

  • BI_client_domain home\domains\bi\servers\obis1\logs\user_name_NQSAdminTool.log

  • BI_client_domain_home\domains\bi\clients\datamodel\logs\datamodel.log

This table describes some common connection issues and how you can resolve them.

Common Connection Issues Cause and Resolution

401: Unauthorized OR Authentication failure

The login credentials are invalid.

  • Make sure the user account exists.

  • Make sure you spelled the user name and password correctly.

  • Make sure the password doesn't contain an exclamation mark (!)

  • Make sure the user has the BI Service Administrator application role.

Error initializing TLS secure connection or Proxy exception: java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: Default, provider: SunJSSE, class: sun.security.ssl.SSLContextImpl$DefaultSSLContext)

OR

Error initializing TLS secure connection or Proxy exception: Remote host closed connection during handshake

This issue has multiple causes:

  • The connection points to a file which is not trust/key store.

  • The connection points to a trust/key store that doesn’t contain a certificate that can be used to verify the server certificate.

  • The trust store password is incorrect.

Use the default JDK key store located in: BI_client_domain_home\oracle_common\jdk\jre\lib\security\cacerts.

Connection failed, the server processes may be down, the host name, port number, service instance, or protocol (http/https) may be incorrect

This issue has multiple causes:

  • Make sure you’ve specified the correct host name and port number. See Connecting to a Data Model in the Cloud.

  • If the datamodel.log file reports Connection timed out, check whether the Oracle Analytics Developer Client Tool machine is in a proxy-enabled network. If it is, ask your network administrator for the proxy server and port, and specify these when you connect to your data model.

  • If you can’t diagnose a connection issue using the client side log files, check server side log files bi-lcm-rest.log.0 and bi_server1.out.

    For example, if the database user doesn’t have the BIServiceAdministrator application role, the bi_server1.out. file shows an error similar to:

    oracle.bi.restkit.security.auth.RequiredGroupAuthoriser> <BEA-000000> <Failed authorisation for user: weblogic>

Connecting to a Data Source Using an External Connection

Administrators can define database connections for data models using the Console in Oracle Analytics Cloud. If you want to use the same database connections in Oracle Analytics Cloud Developer Client Tool, you don’t have to re-enter the connection details. Instead, you refer to the database connections “by name” in the Connection Pool dialog.

If you haven't already done so, create the database connection in Console and note down its name. For example, MyCloudSalesDB. See Connecting to Data in an Oracle Cloud Database.
  1. In Oracle Analytics Cloud Developer Client Tool, navigate to the Physical Layer pane, and open the Connection Pool dialog.
  2. In Name, enter a name for the data source.
  3. Select the Externalize connection check box.
  4. In Connection name, enter the name of the database connection exactly as defined in Console (context-sensitive). For example, MyCloudSalesDB.

    Note:

    When you select Externalize connection, several options on this dialog don’t apply: Data source name, Shared Logon User Name and Password.