Skip to main content

EECS - Oracle Exadata Express Cloud Service, Step 2

By
Once you get your services up and running, you can log into your domain - in this screenhot "smart4apex" - on the Oracle Cloud.
Then you'll end up in the "My Services" dashboard. As I have only one, my dashboard looks quite clean, showing just this widget:
Just a few remarks for the designers of this: I am very curious why there is an extra "(Number of ..." in the chart title. The same superflous text is also on another location on that page.
And, more intriguing, what would "0.0323 database instances" mean? 1/0.0323 = 31. So something like days? But February has 28 days...
It would make way more sense to just show here how many instances I had on those day (so, "1" al over the place...).
From this widget you can drill into the "Service Details", where you can set rules and alerts and see the (historical) status of your instance. Funny thing is, I noticed this:

These figures indicate, I have a storage limit of 23Gb. But my service is based on 20Gb. So I get 3Gb "for free"!
Probably that's (more or less) used by Oracle itself (SYS, APEX etc.). So if you buy 20Gb, you really get 20Gb to store your own data!
Now it is time to add some users to this instance. As we - as smart4apex - would like to use it as a development environment, I added all colleagues as a user. 
And i can assign Roles to every user. There is a standard list of roles defined. From the documentation I figured out that the first two are entitled to add or modify other users, but what the privileges and restrictions of the other three are, I still have to discover. What I do know is, if you just assign the "Database User" role to a user, you can log in to the My Services page, but if you try to use the Exadata Express service, you get an "Acces Denied" message. You need at least Database Developer or Database Administrator to access the APEX builder (more about that in a later post).
A nice feature is, you can upload a csv file to create multiple users and assign roles in batch. Saves you a lot of clicks....
And every user you create receives a nice welcome email with a temporary password and a login link. Once you use that link, and login you end up on a (rather outdated - ADF faces built) page of Oracle Identity Self Service to change your password and register three (!) challenge questions. That is a challenge in itself ;-)
Apart from the standard Roles, you can define "Custom Roles" and assign those to users. But any information about how to use these roles in an APEX application is welcome, as I couldn't find any documentation on this subject.

In the next post, I'll go into the database (in)side of the service and in the subsequent one, the APEX development environment of the Exadata Express Cloud Service (EECS).

Labels:

Comments

Post a Comment

Popular posts from this blog

How to create neatly formatted Excel documents using PL/SQL?

By
If there is a requirement to produce output from an application into Excel, you would probably create a CSV (Comma Separated File) with the data and start Excel to show the data - at least that's what I did...until now. The drawback of this solution is that you could only produce data and no nice layout. But Excel is also capable of opening HTML-files and using this you could create Excel files with data and magnificent layout! Let me give an example: 1. Create a procedure to show the data in formatted in an HTML table. CREATE OR REPLACE PROCEDURE display_emp_list IS v_emp_count NUMBER(5); v_empno NUMBER(8); v_ename VARCHAR2(50); v_job emp.job%TYPE; v_sal emp.sal%TYPE; v_bg_color VARCHAR2(10) := ''; CURSOR c_emp IS SELECT empno, initcap(ename), job, sal FROM emp ORDER BY ename; BEGIN SELECT COUNT(*) INTO v_emp_count FROM emp; owa_util.mime_header('application/ms-excel', FALSE); htp.p('Content...
21 comments
Read more

Refresh selected row(s) in an Interactive Grid

By
In my previous post I blogged about pushing changed rows from the dabatase into an Interactive Grid . The use case I'll cover right here is probably more common - and therefore more useful! Until we had the IG, we showed the data in a report (Interactive or Classic). Changes to the data where made by popping up a form page, making changes, saving and refreshing the report upon closing the dialog. Or by clicking an icon / button / link in your report that makes some changes to the data (like changing a status) and ... refresh the report.  That all works fine, but the downsides are: The whole dataset is returned from the server to the client - again and again. And if your pagination size is large, that does lead to more and more network traffic, more interpretation by the browser and more waiting time for the end user. The "current record" might be out of focus after the refresh, especially by larger pagination sizes, as the first rows will be shown. Or (even wors...
Post a Comment
Read more

APEX ReadOnly Pages - The easy way

By
If your Oracle APEX Application requires different types of access - full access or readonly - for different types of users, you can specify a Read Only Condition on Page level (or Region, Item, Button, etc.).  You can set an Authorization Scheme on Application level, so it'll be applied to all pages. So if you have an Authorization Scheme named 'User Can Access Page' defined by a PL/SQL function like this: return apex_authorization.user_can_access_page ( p_app_id  => :APP_ID , p_page_id => :APP_PAGE_ID , p_user    => :APP_USER );  then you can code all the logic in the database using the APEX Repository, your own tables or a combination to define whether a user has access to that page or not. But alas it is not possible to define something similar Application wide for a Read Only condition. You can specify an Authorization Scheme 'User has Read Only Access' using a similar signature as the one above and use that on each and e...
Post a Comment
Read more