Summary
Connection issue when Essbase Cloud Service now requires encrypted passwords - how to access from DV?
Content
Hi,
I am trying to set up a demo connecting from DV (OAC instance) against Essbase Cloud like last year. The connection from OAC DV instances is now not working anymore using DSN https://Essbase-IP-adress:9000/essbase/agent (trying different users/passwords and ports) - does somebody have similar experience and solved it? Any ideas, which steps need to be performed?
I try to follow these steps: https://docs.oracle.com/en/database/other-databases/essbase/19.3/essad/set-ssl-certificate.html - I am specifically wondering which self-signed certificate to provide (have no load balancer setup) and not sure if this is the root cause at all.
Background: Since March 2020, Essbase Cloud instances have encrypted passwords and https protocol. It looks like self-signed certificates are used and additional setup is required on Linux Server level in Essbase cloud. Can somebody confirm, that these steps here are important/ required for connection from DV? Or is the issue more in the OCI Firewall setup? I have similar connection issues with DVD (tested this to separate OAC issues from Essbase Cloud issues)
Any ideas and suggestions are welcome
Regards Rodian
Version
Essbase 19c (19.0 / 19.3)
Code Snippet
Failed to save the connection.
Invalid connect string / url to external source.