How to setup a Custom Vanity URL for Essbase 19c Marketplace Instance without Load Balancer

June 8, 2020 | 1 minute read
Veera Raghavendra Rao Koka
Consulting Member of Technical Staff
Text Size 100%:

How to setup a Custom Vanity URL for Essbase 19c Marketplace Instance without Load Balancer

 

Tested on Essbase 19c marketplace Instance Version: 19.3.0.2.0, Build: 362

 

Action Summary:

For a Vanity URL we need to decide on the DNS Name.

Generate Private Key and Certificate Signing Request (CSR) for the required DNS Name.

Get the CSR file signed by a Well Known Public Certification Authority (CA) like VeriSign, DigiCert, GoDaddy, etc.

Once the CSR is signed by a CA, we should be having the below files:

1. Signed DNS Named (for Apache Server) SSL Certificate.

2. CA Intermediate Certificate (If multiple intermediate certificates exist, we need all of them).

3. CA Root Certificate.

Upload the above mentioned files and the Private Key on to the Essbase Instance VM and perform the config steps.

Map the Essbase Marketplace Instance VM Public IP Address to the desired DNS Name in the DNS Server to be recognized over the Internet.

NOTE: If Private IP is used while creating Essbase MP Instance, set the Private IP Address to the DNS Name in the Customer’s DNS Server so that the DNS Name is resolved to the IP in the Intranet.

Change the Essbase URL in the IDCS Confidential Application to the DNS Named URL

Access Essbase URL using the new DNS Name

 

Details are in the attached Document link

how_to_setup_a_custom_vanity_url_for_essbase_19c_marketplace_instance_without_load_balancer

Veera Raghavendra Rao Koka

Consulting Member of Technical Staff

Oracle Analytics Service Excellence, CEAL Team


Previous Post

Identify High Value Opportunities on your Transformation Journey

John Hagerty | 4 min read

Next Post


Enhance Your Data Preparation Using Oracle Analytics

Philippe Lions | 9 min read