In this blog post I will setup a Java Cloud Service, which is Oracles PAAS service for delivering WebLogic Application Server, . Setting up a Java Cloud Service infrastructure means the following:
Setup a Database Cloud Service
Setup a Java Cloud Service including a Loadbalance feature. This will result in a basic Oracle Traffic Domain and a WebLogic Domain for your applications to be deployed on.
Setup a Java Cloud Service
To setup a Java Cloud Service, you will setup a complete basic WebLogic Application Server domain. For this you need to set up:
Database Cloud Service
In my cloud console I first followed the process of setting up a database Cloud Service
Clicking on the Database Cloud Service Console, create a service
Next,you fill in some requested details
Last screen some advanced details. Don't forget to tick create Storage Container
Service Name: Service Name of the database
Key: You can generate a keypair in the console, or if you have done so, select you public key
BackupDestination: Should be both Cloud and Local for Java Cloud Service
Cloud Storage Container: Must be in the right naming format: Storage-<your identity domain/<storage container name ( name is free to choose>)
PDB leave it to the default
After a while, you have a database up and running .
Accessing the database can be done in a view ways:
- Through DB/EM Console; just the familiar way of doing it
To access these console, you need to enable the predefined access rules
The Java Cloud Service
Second, the Java Cloud can be setup, which is a relative easy part. From your Cloud Dashboard you can click the Java Cloud Service Icon, open the Service console
and Create Service.
Also inhere a very straight forward process:
Finally, when all details are filled in:
Think about accessing consoles, otherwise they're inaccessible, but later we will have to secure them more with OTD
Also enable a local loadbalancer, it will cost more but gives more control
After creation, you get 2 domains:
Your application domain
The Oracle Traffic Director Domain
Here's where the basic setup ends. Afterwards you can access your environments as if it's in you companies infrastructure. I deployed an MDB testapplication which generates lots of JMS Messages and CPU cycles.
Later on, in part 2 I will dive more into the multitenancy story, to share resources and do isolation.