Best Practices from Oracle Development's A‑Team
-
/ A-Team Chronicles
August 6, 2020
Connecting Oracle Analytics Cloud to Autonomous Database on Dedicated Exadata Infrastructure
Note: Private Access Channel is now available in Oracle Analytics and is recommended by Oracle for new connections to private data sources. For more information on the feature and the data sources it supports refer to:
Connect to Private Data Sources Through a Private Access Channel
Supported Data Sources
A-Team Chronicles Private Access Channel Series
Last Validation: February 12, 2021 for OAC 5.9
Introduction
This post details the steps required to create data connections in Oracle Analytics Cloud (OAC) for Autonomous Database on Dedicated Exadata Infrastructure (ADB-D) using Remote Data Gateway (RDG). Data connections are used for Data Visualization (DV) data sets. Note: As with shared ADBs private instances may not be used with OAC console or replication connections for RDG.
ADB refers to both Autonomous Data Warehouse and Autonomous Transaction Processing databases.
ADB-D runs on a private subnet, hence an OAC Remote Data Gateway (RDG) is required for connectivity
For additional details on ADB-D, visit Using Oracle Autonomous Data Warehouse on Dedicated Exadata Infrastructure. For additional details on OAC, visit the Analytics Cloud page.
Refer here for a post on creating RPD connections to an ADB-D.
Validations
August 5, 2020 for OAC 105.7
May 19, 2020 for OAC 105.6
April 27, 2020 for OAC 105.5
Topics
Before You Begin
Creating an ADB-D TCPS Data Connection
Creating an ADB-D TCP Data Connection
Before You Begin
Before creating ADB-D connections, you must have an ADB-D wallet zip file, credentials for an ADB-D schema owner and Remote Data Gateway (RDG) deployed and connected to OAC.
Obtaining an ADB-D Wallet Zip File
Refer here for the steps to obtain an ADB-D Wallet Zip File.
Obtaining ADB Credentials
If you provisioned ADB, use those credentials (username and password) or obtain the credentials from an ADB administrator.
Choosing an ADB-D Connection Type
Dedicated ADBs databases differ from Shared ADBs in that they offer TCP services as well as the TCPS services found in Shared ADBs. For more information refer to Predefined Database Service Names for Autonomous Data Warehouse Dedicated Databases
TCP services may be used without a wallet file e.g. cwallet.sso. This is useful when connecting with a client that does not support the use of wallets. These services are named like <ADB-D name>_low e.g. dcadwdprv_low
TCPS services require the wallet file. These are the service types found in Shared ADBs. These services are named like <ADB-D name>_low_tls e.g. dcadwdprv_low_tls
Providing Access To and From Remote Data Gateway
RDG connects to an ADB-DB using TCP ports specified in the tnsnames.ora file found in the download client credentials zip file.
These ports need to be opened for egress in the RDG subnet via a Security List or a Network Security Group (NSG). Refer here for more information on Security Lists and here for NSGs.
Likewise, they need to be opened for ingress in the ADB-D subnet.
Domain Name System
DNS provides a worldwide, distributed directory service for translating FQDNs to their associated numerical IP address. The default DNS in OCI provides resolution for resource names within the same VCN. Refer here for a post describing various DNS scenarios and the components necessary to resolve ADB names outside of your VCN.
Networking Gateways
A networking gateway is required to connect to ADBs residing outside of RDG's VCN. Refer here for a post describing various gateway scenarios and the components necessary for network traffic between resources in different VCNs.
Deploying Remote Data Gateway
RDG is required by OAC to access most private databases including an ADB-D. Refer here for various deployment strategies.
Creating an ADB-D TCPS Data Connection
Data connections are used to create DV data sets.
Connect to your OAC instance or click Home to return to the DV home page
Click Create
Click Connection
Click an ADB-D connection type
Complete the connection details and click Save.
Provide a Connection Name and optionally a Description.
Click Select and choose the Client Credentials zip file to download from the ADB-D. The cwallet.sso file is extracted from the zip file by OAC and shown in the window.
Use the Username e.g. Admin and Password specified when the ADB-D instance was created or a different Schema's credentials.
Note: Choose a Service Name ending with _tls. Choose a Service Name ending with _tls from the drop-down list provided.
Check the Use Remote Data Connectivity box.
Click Save.
Creating an ADB-D TCP Data Connection
Use the Oracle Database connection type for these connections.
Click Home to return to the DV home page
Click Create
Click Connection
Click the Oracle Database connection type.
Complete the connection details and click Save.
Provide a Connection Name and optionally a Description.
Change the Connection Type to Advanced.
NOTE: The connect descriptor used below is obtained from the tnsnames.ora file in the unzipped ADB-D wallet zip file obtained above. Ensure to use a service where the PROTOCOL=TCP
The Connection String uses the format jdbc:oracle:thin:@<TNS Connect Descriptor> e.g.
Leave the Client Wallet field blank.
Use the Username e.g. Admin and Password specified when the ADB-D instance was created or a different Schema's credentials.
Check the Use Remote Data Connectivity box.
Click Save.
Summary
You can now create DV data sets from these connections.
This post detailed the steps required to create data connections in Oracle Analytics Cloud (OAC) for Autonomous Database on Dedicated Exadata Infrastructure.
For other posts relating to analytics and data integration visit http://www.ateam-oracle.com/dayne-carley