Another day in the clouds - Oracle Java Cloud Service.

Last Friday I have started my journey into Oracle Public Cloud. I have written a post about Oracle Database Service. This night I have spent on exploring WebLogic PaaS, which is called Oracle Java Cloud Service. Web GUI is very similar, which means after choosing Java Service we could see step by step wizard.

STEP 1. In Subscription step we should choose virtual image vs full blown Oracle Java Cloud Service. This last one will include scaling up capabilities, patching automation and backup feature. Additionally we should choose hourly or monthly counted billing:

STEP 2. In the next step we should decide which version should be provisioned. Unfortunately we have only two - WLS 11g and WLS 12cR1. I have written here about recently published WLS 12cR2 with support for Java EE 7. I hope it will be soon available also in the cloud:

STEP 3. Here, in this third step we should decide which edition of WLS we would like to work with. We have options for Standard, Enterprise and Enterprise with Coherence.

STEP 4. In the step called Details we will have a lot of options to be choosen or fields to  be fulfilled. It is the most critical step, where number of nodes within the cluster could be defined. Also we should define configuration database instance where cluster will store all necessary metadata. Finally we could configure load balancer which will be placed between WLS farm and public Internet. For backup purpose we should also define Oracle Storage Service Container which should be created before WLS with the set of RESTful commands.

STEP 5. In last step of the wizard we have summarized page of planned configuration. Now we can click Create button to start the provisioning process.

STEP 6. Creation process is rather long - plenty of minutes and we could go for one or more coffees :-) 

STEP 7. After longer period of time we could see the success of the creation - domain, 1x managed server, 1x admin server, load balancer and database:

STEP 8. After clicking on content endpoint we can see sample app deployed on and available via load balancer:

STEP 9. On the other hand we could manage the PaaS via standard Weblogic Console or WLST scripts:

STEP 10. For Load Balancer which is Oracle Traffic Director we could use the console:

As you can see it is very easy to start with. I am pretty sure it will be choosen by many customers in the near future. I promise to write down how the scale-out is working. :-)

That is all for tonight. Stay tuned :-)

lukasz.feldman@redstk.com

PS. Read here about scale-out of Oracle Java Cloud Service :-)