I finally have time to play with Oracle Analytics Cloud Enterprise Edition (OAC EE).
I have been interested in setting up my OAC BI instance to work off an Essbase Cloud cube.
So; First Things First...Download the latest version of the OBIEE Admin Tool that supports BICloud
At the time of this post it was 184.108.40.206.20
Keep an eye out for updates...
I have an Oracle Analytics Cloud Enterprise Edition instance that allows me to work with an RPD for Data Modeling instead of the built in data modeler that we know from BICS. The BICS Data Modeler does not let me connect to Essbase Cloud Service. I also have an Oracle Analytics Cloud Essbase Cloud Service. I need to make my Essbase Cloud Cubes available as subject areas in my OAC-BI instance.
The cube I will start with is the Sample.Basic from my Essbsae Cloud server.
So starting up the Admin Tool I need to create a new RPD. I selected 'No' for the Import Metadata because I like to create my Physical Layer one piece at a time.
In the Physical Layer I created a New Database...
Since I am connecting to an Essbase Cloud instance I selected the latest version of Essbase that is available in the list of Database Types,
Next I created the connection pool. I put the Public IP address for my Essbase Cloud Instance
I import the Essbase metadata by right clicking on connection pool
I authenticated to the Essbase Cloud instance and navigated to my Cube to import and started the Import. The process started and up popped a message.
So it was time to see what following the Import Metadata option from File menu after deleting everything in the Physical Layer.
I selected the available Connection Type - Essbase 9+
set my connection to the public IP
Once again navigated to my cube and imported it
This time it worked
And my cube shows up fine in the Physical Layer.
After renaming the Database, Connection Pool adjusting Dimension properties to suit my needs I followed same process as an on-prem cube in the RPD.
It is time to save all my work and like any good RPD Developer I click yes on the Global Consistency Checker.
And what do we have here...? The warning indicates that my Database Type is not correct.
I checked the Physical Layer properties of the database, I see that i have a couple more options than I did when I selected Import Metadata. I selected the most recent release version available in the list.
This time when I saved and allowed for Global Consistency Check I did not get any warnings or errors!
So it is time to submit an SR and deploy to the cloud! But that is topic for another post....