X

Best Practices from Oracle Development's A‑Team

Connecting to Essbase 19c using a Load Balancer

Last Validation: November 13, 2020 for Essbase 19c 19.3.0.3.4.1

Introduction

This post details the steps required to connect Oracle Analytics Cloud (OAC) to a private Essbase 19c Marketplace instance in Oracle Cloud Infrastructure (OCI) using a public load balancer. Both Data Visualization (DV) and RPD connections are described. This method bypasses the need for Remote Data Gateway (RDG) or Remote Data Connector (RDC).

Note: This is an exception to the rule that OAC connections to private data sources require RDG or RDC.

For additional details on OAC, visit the Analytics Cloud page. For additional details on Essbase 19c, visit the Administering Oracle Essbase page.

Validations

November 13, 2020 for Essbase 19c 19.3.0.3.4.1

August 31, 2020 for OAC 5.7

Topics

Before You Begin

Creating an OAC DV Connection

Creating an OAC RPD Connection

 Before You Begin

Before connecting OAC to Essbase 19c, you must deploy Essbase using the OCI Marketplace as described in the link above. This post assumes the load balancer, Essbase, and optionally a private OAC are deployed into the same VCN.

The connection architecture is shown below.

Using the Essbase Resource Manager Stack to Deploy a Load Balancer 

If the original deployment of the OCI Resource Manager Stack did not include a load balancer, you can simply edit the stack, select the public load balancer option and reapply the stack. Everything already deployed remains the same and only   balancer is deployed. The new Essbase URLs using the load balancer IP address are provided at the bottom of the resource stack's apply log.

Updating the IDCS Confidential Application for the Load Balancer 

If you deployed a load balancer as noted in the section above, then the IDCS post-deployment step must be performed again to use the load balancer URLs as described in Modify the Confidential Identity Cloud Service Application. 

Updating the SSL Certificate

If the deployed load balancer is still configured with the default self-signed demo SSL certificate, you must complete the Essbase 19c post-deployment step for setting up a trusted certificate authority as described in Set Up the SSL Certificate. OAC requires the certificate be signed with a trusted certificate authority.

Confirming Access to Essbase via the Load Balancer

The Essbase Marketplace stack provisions the load balancer in a public subnet specified in the stack variables. Ensure there is an ingress rule in the public subnet's security list or in a Network Security Group to allow traffic into port 443. For more information visit Security Rules

Before connecting from OAC, use a browser to ensure you can connect to Essbase via the load balancer. Enter an URL in the format. 

https://<Load Balancer Public IP>/essbase e.g. https://140.xxx.xxx.29/essbase

Confirming the Health of the Load Balancer

 If you were unsuccessful connecting to Essbase, connect to the OCI console and navigate to Networking > Load Balancers. Ensure your region and compartment are correct and check that the overall health is OK. If it is not, ensure that the appropriate security rules and routings for the public and private subnets are correct.

 Creating an OAC DV Connection

Connect to the OAC homepage and create an Essbase data connection using the Essbase load balancer URL.

 

 Creating an OAC RPD Connection

Use the OAC Developer Client Tool to create or open an RPD. 

Set the physical database Database Type to Essbase 11. (This is the only type I tested).

Set the connection pool Essbase Server to the Essbase load balancer URL used to confirm access to Essbase via the load balancer above.

Complete the RPD development as necessary, save the RPD, and then either publish it to OAC or replace it in OAC depending on how you opened the RPD.

 Summary

You can now create DV and RPD connections to a private Essbase 19c using a load balancer.

This post detailed the steps required to connect Oracle Analytics Cloud to a private Essbase 19c Marketplace instance in Oracle Cloud Infrastructure using a public load balancer. Both Data Visualization (DV) and RPD connections were described.

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