Available as of today, these services now also includes:
- Oracle SQL Developer Web
- Oracle REST Data Services for RESTful Services and SODA
From your Autonomous Database Service Console, you can launch SQL Developer Web for managing and working your Oracle Database. Run queries, create tables, generate schema diagrams, and much more.
SQL Developer is a mature desktop offering servicing more than 5,000,000 Oracle professionals around the world, and now it’s primary features are also available directly in your browser.
An Overview of SQL Developer Web
Accessing SQL Developer Web
Navigate to your Autonomous Database Service Console. Then, open the Development page, and you’re find the REST Data Services section. There you will find links for both APEX and SQL Developer Web.
This will open the application, and you will be prompted for a database user name and password.
It’s all about the worksheet.
While SQL Developer Web has many compelling features, the biggest impact to your everyday experience with the Oracle Autonomous Database will be your ability to immediately start working with your instance via SQL and PL/SQL – directly in your browser via the SQL Worksheet.
Help and Getting Started
In the Worksheet and Modeler screens, you’ll find a Binoculars button which launched a guide tour of that portion of the application.
And of course there is also the in-app Help and Documentation.
Using APEX for the first time in Autonomous?
Yes, there’s also APEX support! When you click on the APEX link in the Console, you’ll get to here:
And now you you’ll want to go into the admin pages…
Click that box, and you’ll be into your administration pages where you can create your first workspace and assign it to a schema.
These pages should look familiar…
So you’re saying, well how do I create a new schema for my APEX application workspace?
Try SQL Developer Web!
Adding a new Oracle user, accessible by SQL Developer Web
Adding a user is adding a user, just like you’ve always done in an Oracle Database. Create the user, grant the CONNECT and whatever other privs they will need.
Now I have for example a new schema (THATJEFFSMITH)for my APEX Workspace.
If I want to login as that new user using SQL Developer Web, I’ll need to REST Enable it:
--run this code as user THATJEFFSMITH, in say SQL Developer on your desktop BEGIN ords.enable_schema ( p_enabled =>; TRUE, p_schema => 'THATJEFFSMITH', p_url_mapping_type => 'BASE_PATH', p_url_mapping_pattern => 'tjs', p_auto_rest_auth => TRUE ); COMMIT; END; / --or, logged in as ADMIN in SQL Developer Web, run this code: BEGIN ords_admin.enable_schema ( p_enabled => TRUE, p_schema => 'THATJEFFSMITH', p_url_mapping_type => 'BASE_PATH', p_url_mapping_pattern => 'tjs', p_auto_rest_auth => TRUE ); COMMIT; END; /
If you run this above code, you’ll be able to login to SQL Developer Web. Just mind that the URL will look have to look like this…
Note that I have /tjs/ in the URL? That’s the p_url_mapping_pattern. If you go to the same URL but with /admin/ in the link and try to login as THATJEFFSMITH/password, I’m going to get a bad user/password.
So make sure the url mapping pattern you include when REST enabling your schema is used in your url to login to your database when using SQL Developer Web.