X

Best Practices from Oracle Development's A‑Team

Deploying Oracle Analytics Cloud Remote Data Gateway in a Remote Private Subnet

Last validated February 14, 2020 for OAC 5.5 and RDG 5.5

Introduction

The latest releases of Oracle Analytics Cloud (OAC) now include the new Remote Data Gateway (RDG) for accessing databases that are not otherwise accessible by OAC.

This post is a step-by-step guide to installing and configuring RDG in a remote region's private subnet on Oracle Cloud Infrastructure (OCI). The term Remote is used here to denote a different region e.g. OAC in Phoenix (PHX) and the DB and RDG in Ashburn (ASH). Although connectivity is simple over the internet, ensuring private connectivity is more complex and is the subject of this post.

The official documentation for RDG is Connect to On-premises Data Sources and Known Issues.

The technique described in this post uses the concept of Remote Peering Across Regions. The official documentation is Here

This post is one of the strategies noted in the companion blog Deploying Remote Data Gateway in Oracle Analytics Cloud for Data Visualization

Validations

  • February 14, 2020 for OAC 5.5 and RDG 5.5

  • December 13, 2019 with OAC 5.4 and RDG 5.4

Versions

  • Oracle Analytics Cloud version 105.4x

  • MacBook Pro OS 10.13.6 

  • Windows Server R12 Compute Instance

  • Linux 7.7 Compute Instance

Topics

  • Before You Begin

  • Downloading Remote Data Gateway

  • Preparing to Install Remote Data Gateway

  • Preparing to Configure Remote Data Gateway

  • Preparing to Configure Remote Data Gateway

 Before You Begin

The prerequisites listed in this section require a detailed and functioning knowledge of the Oracle Cloud Infrastructure Networking components. It is beyond the scope of this blog to detail all the requirements. Presented is a list of the requirements with links to the official Oracle documentation.

Reviewing Supported Data Sources and Operating Systems

Ensure your data source is supported by following the instructions in Supported Data Sources.

Ensure your operating system is supported by viewing the list at OAC Downloads.

Common Prerequisites

Deploying RDG requires the following common items:

All Platforms

Credentials and Privileges to install software on the RDG host.

Database connection information and credentials for validating the installation.

For Linux and Windows Servers

The IP address or host name where RDG is to be installed.

For Linux

A Graphical User Interface or alternatives such as VNC and X11 Note: If using X11, both the bastion and RDG host must be configured.

SSH Utilities to access Linux

For Windows

The Microsoft Remote Desktop (RDP) utility for accessing remote Windows servers.

Initial OCI Components

The initial state has these components. Links to relevant documentation are provided. The following figure shows the initial components:

ASHBURN

  • Compartment to contain a Virtual Cloud Network (VCN) Here 

  • Compartment Policies to Manage Resources Here

  • VCN Here 

  • Regional Private Subnet Here

  • Network Security Group (NSG) or Security List associated with the private subnet to control traffic at the packet level Here

  • Supported Private Database Cloud Instance Here

  • Ingress rule allowing ingress to DB listener port (default 1521) in the above NSG / Security List

PHOENIX

  • OAC instance

  • Associated IDCS instance (this may be in another region).

Additional OCI Components

The figure below shows the additional components required.

ASHBURN

  • DRG Attached to the VCN Here

  • Remote Peering Connection (RPC) associated with the DRG for peering with the remote region. Remote Peering Connection

  • NAT Gateway allowing traffic to an IDCS if it is in a different region than OAC. Here

  • Private Subnet Route Table Routing Traffic to either the NAT Gateway or to the DRG Here

  • Compute Instance in the Private Subnet Hosting RDG Here

  • Additional Ingress Rule in the above NSG / Security List allowing traffic to port 3389 (Remote Desktop) if using a Windows host. 

  • Additional Ingress Rule in the above NSG / Security List allowing traffic to port 8080 (RDG Configuration) if using a Linux host.

  • Compute Firewall Rule allowing ingress to Port 8080 if using a Linux host. A-Team Blog Reference

PHOENIX

  • Compartment to contain a Virtual Cloud Network Here 

  • Compartment Policies to Manage Resources Here

  • VCN to accommodate a Service Gateway (SG) and a Dynamic Routing Gateway (DRG) Here  Note: The Regional VCN CIDR blocks must not overlap.

  • Service Gateway for private traffic into the Oracle Services Network and OAC. For additional detail regarding Service Gateway visit Service Gateway for OAC Remote Data Gateway in a Private Subnet

  • Dynamic Routing Gateway (DRG) for traffic to and from the remote region Here

  • DRG Attached to the VCN Here

  • Remote Peering Connection (RPC) associated with the DRG for peering with the remote region. Remote Peering Connection

  • Route Table Routing Traffic from the DRG to the SG Here

  • Route Table Routing Traffic from the SG to the DRG Here

 Downloading Remote Data Gateway

Go to the Oracle Technical Network (OTN) site, https://www.oracle.com/technetwork/middleware/oac/downloads/index.html, accept the license agreement, choose the desired platform, and download the installer zip file.

 Installing Remote Data Gateway

The steps for all platforms are documented in Install Data Gateway.

Additionally, the Internet section of this blog may be used for reference:  Deploying Oracle Analytics Cloud Remote Data Gateway in a Private Subnet

 Configuring Remote Data Gateway

After the installation, follow the steps in Completing the Deployment of Remote Data Gateway for OAC to configure RDG.

After RDG is configured and the connection validated, the following shows the operation architecture.

The Process:

  • RDG initiates the connection to OAC via the Remote Peering Connections and the Service Gateway

  • User connects to OAC which may include authenticating with IDCS 

  • User issues a query

  • OAC passes the query to RDG via the RDG connection

  • RDG passes the query to the database.

  • Database returns the data to RDG

  • RDG passes the result data to OAC via the RDG connection.

 Summary

This post described installing and configuring RDG in a remote region's private subnet on Oracle Cloud Infrastructure (OCI). An example used is with OAC in Phoenix (PHX) and the DB and RDG in Ashburn (ASH).

For other posts relating to analytics and data integration visit http://www.ateam-oracle.com/dayne-carley

 

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.Captcha