it is late in the evening of Sept. 29, 2017 or early in the morning of Sept. 30, 2017...Regardless...I cannot sleep!
I noticed that my Galaxy Note 8 updated my Oracle Synopsis App. I see that it is a 2.0 release...I am not one to read manuals and updates right off so I started looking around on the app to see what was new. The first thing that caught my eye was in the Settings. Something new stood out...Smart Lock on OAC
Well that really got me wondering...Can my Synopsis connect to my OAC instance and if so what can I access. So I went to the main screen and created a new project and there was an option to connect to OAC.
So I figured, in for a penny in for a pound. I tapped (because we all know you do not click on a tablet) and I got a sign on screen.
I provided my credentials and I was presented with a list of data sources. I had just created a data file named Kool Kart Dataset from a Data Flow I was working on and I noticed it was in my list.
Checking my Data Sources in OAC i see most of the same list...
The only difference is that my Subject Areas (the purple icons at the top of the list) are not listed in my Synopsis menu...This seems right since Synopsis seems top operate from a data file based on columns of Dimensions and Facts. So what happens if I try to load up one of the Essbase Connections...I tapped on Sample.Basic and...
Well that was educational.
So I tapped on my Kool Kart Dataset. And it loaded up into Synopsis with some quick analyses based on the data in the file.
While it did a pretty good job of interpreting the data in the data file it treated the Year column as a measure as indicated by it being displayed on the X-axis with Revenue and Number of Orders.
Well that is something to investigate further.
The ability to connect to OAC, display content in Synopsis is a huge leap forward in mobile analytics. Oh and by the way, did you know Synopsis is FREE...Look for it on Apple iTunes and Google Play.
Friday, September 29, 2017
Friday, August 18, 2017
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 220.127.116.11.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....