The Java Cloud Service (JCS) in the Oracle Public Cloud allows me to deploy Java EE applications such as JAX-RS and JAX-WS REST and SOAP Web Services, Servlet | JSP | JSF Web Applications, EJB and JMS artifacts and ADF applications to the public cloud and make them accessible to developers, testers and end users anywhere in the world. For components to be deployed to the JCS – I have to do nothing special (!) during development or deployment: anything that runs on premises will run in JCS.
In this article, I will describe some of my initial experiences with JCS: what did I have to do to get going the first time – from having nothing more but a (trial) subscription to JCS to deploying and running my first Java EE application on JCS. I thought this would be a very long article with a large number of tips and tricks and with deeply technical steps. I felt some reluctance to even get going – feeling a little daunted by a new world full of new terminology. As it turned out – this is not a long article and it certainly does not contain a lot of tips. My initial reluctance was misplaced. JCS is just WebLogic – hosted on a different machine than my laptop and with a different provisioning interface. The amount of cloud terminology is limited (cloud account, identity domain, service instance is probably the bulk of it – along with simple tooling: dashboard, service console). JCS builds on three other Oracle Public Cloud Services that we need to be aware of: DBaaS (Database), Compute Cloud Service and Storage Cloud Service.
You do not need guidance from me for all the steps you need to go through. I worked with an excellent tutorial on Oracle Help Center – Getting Started with Oracle Java Cloud Service – and I heartily recommend you do the same.
The steps (described in this tutorial) that you need to go through in order to have your first Java EE application running are:
- (do: 5 minutes | then wait: days up to months) Get a [Trial] Subscription to the Oracle Java Cloud Service – for your Oracle account (the same one you use for OTN and any other interaction with Oracle); an Oracle Java Cloud Service trial environment or purchased subscription comes with Oracle IaaS Public Cloud Services, which provides you access to Storage CS and Compute CS – both of which underpin the JCS instance;
Note: Database Cloud Service is a prerequisite of Java Cloud Service and is priced separately. When you request provisioning of an instance of JCS, you need to specify the DBaaS instance that it should make use of. Read my previous article on DBaaS to get going with the Oracle Database as a Service offering and prepare a database instance.
- (do: 5 minutes) Associate the [trial]subscription with an existing or a new Oracle Public Cloud account (and thereby to an identity domain)
- (do: 5 minutes) Generate SSH keys (you can reuse the SSH key pair you may already have created to get going with Oracle DBaaS) Read the complete article here.
For regular information become a member in the WebLogic Partner Community please visit: http://www.oracle.com/partners/goto/wls-emea ( OPN account required). If you need support with your account please contact the Oracle Partner Business Center.