In the last post, I covered provisioning an Oracle Exadata Express instance. Now we have one up and running let’s click the Service Instance URL and see what the dashboard looks like.
In my case the format of the URL in the Service Console (and emails) was in the format –
For for example if you created –
Identity domain: foobarcorp
Data Center Location: EMEA
then you might get a URL like:
I like this format, since it’s entirely logical. I remember using the DBaaS service when it was first available and it seemed to me that the URL’s were far from logical (I noticed pretty quickly that newer instances got more logical URL’s, but some of our early instances stuck with the original format).
Ok, so lets click on that URL (note my real URL, not the made up one above which certainly won’t work!)
I immediately see this –
A couple of things to note –
- It’s HTTPS by default (great!)
- You can only access that page if you’re logged into your Cloud Account (i.e. it’s not visible to the Public Internet-at-large yet)
The one that intrigues me straight-away is access to SQL Workshop and App Builder, which are both part of Oracle APEX.
If I click on SQL Workshop, it takes me right into it (no need to re-authenticate since I’m already logged into my Cloud Account so it knows who I am).
Now the really interesting thing here is right down in the bottom right corner, it shows us the installed APEX version –
Application Express 5.1.1.00.08
That’s the latest and greatest (at the time of writing), so that’s fantastic. I haven’t read anything so far on what the upgrade options are going to be once new versions of APEX are released (that would be interesting to know). But hey, at least it’s the latest version with all the nice features like Interactive Grid etc.
So let’s jump into SQL Commands and run a quick query to see what objects are installed:
So just the typical EMP / DEPT tables and a DEMO app / package, nothing unexpected.
One key thing I noticed, take a look at the schema name it lists
Urgh…that’s clearly generated and non-human-friendly.
To be honest I didn’t spot when I was provisioning the schema that I wasn’t prompted for a schema name to use. However for those of you with good memories one of the options right back in the first screenshot above was the ability to create a new schema.
Ok, now let’s try jumping into App Builder (which is part of APEX), clicking the link on the main dashboard takes me to the familiar App Builder interface:
Notice the Sample Database Application is already pre-installed. I wanted to know if this application was available to anyone without having to be authenticated to the Cloud Account (i.e. could anyone on the internet access it?).
Running the application gave me the (very familiar to me) Sample Application –
So I fired up Google Chrome in Incognito mode from another laptop and tried to access the application directly using the same URL –
Hmmm, so by default you need to be logged into the Oracle Cloud to access your APEX applications. How can we change that?
I went looking in the Authentication Scheme for the Application and sure enough it was set to a new type of Authentication – ‘Oracle Cloud Identity Management’, which makes sense.
I created a new Authentication Scheme based on APEX Accounts and enabled it and retried accessing the application from another browser:
Success – the application is now visible to anyone on the internet!
In the next post we’ll explore how to connect to the Instance remotely via SQLcl