Skip to main content

OOW2011 - Announcing the Oracle Public Cloud

Until this Wednesday, Oracle`s statement was "use Oracle systems to build your own cloud", but this is changed drastically now! Starting November 1, Oracle does this for you. Just subscribe and within 20 minutes you are up and running in the brand new "Oracle Public Cloud".
So what do you get after this 20 minutes of waiting? It depends on what you ordered ;-). Within the Oracle Public Cloud (OPC), the following options are available:
- an Oracle Database Cloud Service
- a Java Cloud Service
- a Social Connect Cloud Service, based on WebCenter
- some Fusion Applications Cloud Services: CRM and HCM.

The Oracle Database Cloud Service
The Oracle Database runs on Exadata. Within a database you get your own schema(s) and tablespace(s), so while the database itself is shared with others, all data is partitioned and caged. To enhance security, Transparent Data Encryption will be switched on, and DataVault might also be used (still under consideration). You can connect to the database over http, rest and JDBC. You can order a small, medium or large service - ranging from 50 up to 250 GB storage space. The data transfer is limited to 6 times the storage.
When using this service it might be important where your data is stored (for instance when you don`t want to expose your data under the American Patriot Act). Therefore, next to the current datacenter in Austin (TX), an European center will be opened in Edinburgh, and more local centers are planned.
You can access the database via the APEX Listener, using RESTful web services. So any language that "speaks" REST, can use this service. Another option is to sign up for an APEX environment. Within a few minutes, you can start developing or deploying your APEX application in the cloud. Similar to, but in this environment you are allowed to run production applications!

The Oracle Java Cloud Service
With the Oracle Java Cloud Service (OJCS) you get your own - prebuilt - Oracle Virtual Machine on an ExaLogic server. This OVM contains one or more WebLogic 11g servers. Just like the database counterpart, this environment will be (almost) instantly available and easy to use and manage. When signing up, or later, you can associate your OJCS with an Oracle Database Cloud Service or a Fusion Application Cloud Service. There will be a pre-built integration with Fusion Apps.

When signing up for one or more of these services, you can have a onetime free trial for 30 days. After that trial period (or immediately if you like), you will be charged per month for the services you`re signed up for. Both the Java and the Oracle Cloud Service comes in small, medium and large - and it is possible to up or downgrade. According to Oracle the pricing will be "competitive" - whatever that may mean...
Before this all goes live, there will be an Early Access period.

Apart from the Cloud Services itself, also a lot of tools will be "cloud enabled". There will be cloud add-ons for Eclipse and JDeveloper, Enterprise Manager will get a Cloud Control feature and SQL Developer 3.1 will have cloud support as well for up- and downloading data (using REST web services or using the new "Data Pump for the cloud".

So who`s this all for? I think the small version of the services could be very interesting for setting up a development environment within minutes. No need to order hard- an software when starting a project, or to reserve your space in the "private cloud" of your own company.
The medium and large versions are targeted at test or production systems. But with the current size limit, only small and medium businesses - or isolated departmental applications, can use this. And therefore it`s not only a competitor for Google and Amazon, but also for the smaller hosting companies. But that will be dependent on the price...

More information an sign up - when the time is there - on!

Location:Ellis St,San Francisco,United States

1 comment

Popular posts from this blog

Showing a success message after closing a modal dialog

APEX 5 comes with Modal Dialogs out of the box. Very neat. Especially for adding and changing data. And to minimise the number of time a user has to click, it could be useful to add a "Close Dialog" process after the actual data processing. When the data processing fails, the Dialog stays on top showing the error. When data processing runs fine, the Dialog is closed ... without any confirmation. And this might be scary for a shaky user.

So how can we provide the user some feedback? On Page 4 of the Sample Dialog Application you can see one solution: up on a Dialog Closed Event on the parent page it does a redirect to refresh the parent page appending the success message of the "Close Dialog" process. This has two drawbacks. First, it probably refreshes more than necessary. And second, if you're using multiple layers of dialogs (dialogs that open other dialogs) the message appears in the "parent dialog".
As an alternative you could follow these steps: 1…

APEX 5 New Static File Features

In APEX 4 you could upload files - like CSS files, JavaScript files, Images and whatever else you like - into the APEX Repository. When you navigate to Shared Components, there is a Files section that offers three different options:
CSS Files are always uploaded (and changed !) for the whole Workspace. For Images and Static Files (usually JavaScript) you could choose whether they should be available for the whole Workspace or for a specific Application only. And if you had a lot of files - e.g. a lot of images - then you had to go through the upload process one-by-one. But that's usually a one time only thing. If you make changes to the CSS and JavaScript files - and that's a continuous process in development - then you had to delete the existing file and upload the new one. Over and over again. And meanwhile fighting the cache of the webserver and your browser.  And another irritating issue: You couldn't use relative references in your CSS or JavaScript files as they just…

Using LDAP for Authentication and Authorization within APEX

One of my current customers would like to use their LDAP (Microsoft Active Directory) server for authentication and authorization of APEX applications. Of course we tried to set up a standard LDAP Authenication that's available within APEX. But we couldn't get that to work. Maybe it has to do with the fact that the client stored their Users within Groups within Groups within .... . Or maybe it doesn't do a full tree walk in the directory. Or maybe it is just because it is Microsoft - and not Oracle Internet Directory (OID). So we moved to a custom Authentication using the DBMS_LDAP functions (and some examples from the Pro Oracle Application Express book and Tim Hall - a.k.a. Oracle Base).

One of the issues we encountered that we wanted to use the user's login name, like "jdoe" and not his full name ("John Doe"). And the login name is stored in the "sAMAccountName" attribute. But authenticating using just "jdoe" didn't work. …