We’re excited to announce the availability of new consumption-based pricing options for Oracle WebLogic Server for Oracle Cloud Infrastructure Container Engine for Kubernetes (Oracle WebLogic Server for OKE). See my earlier blog post describing Oracle WebLogic Server for OKE, and the functionality provided. We have created new Oracle WebLogic Server for OKE listings in the Oracle Cloud Marketplace that enable you to quickly provision an Oracle WebLogic Server domain on Kubernetes, and to use preconfigured CI/CD pipelines to develop and deploy WebLogic Server applications using Oracle’s Universal Credits model (UCM).
The listings we are announcing today are the following:
Quickly create Oracle WebLogic Server configuration on OKE
You can easily find all the Oracle WebLogic Server listings available in the Oracle Marketplace by typing the word “WebLogic” in the search bar. To find only the Oracle WebLogic Server for OKE listings, you can enter “oke” into the search bar.
After selecting the listing that fits your needs, and after accepting the terms and conditions, all you need to do is provide some parameters and within minutes your instance will be ready to go:
The Oracle WebLogic Server for OKE components
Oracle WebLogic Server for OKE will create or configure the resources required for having a secure environment that follows best practices for running WebLogic Server on OKE clusters. It uses the WebLogic Kubernetes Toolkit to support WebLogic on Kubernetes. It provides, out of the box, a Jenkins controller configured to run inside your OKE cluster and launch Jenkins agents on demand to build and test your domain. NginX is configured as an ingress controller and is front-ended by a public load-balancer to access deployed applications, and by a private load-balancer to access the Oracle WebLogic Server and Jenkins administrative consoles. A bastion host is provisioned in a public subnet to enable access to private resources, such as an Administrative host that is created with all the required tools for you to manage your instance configuration. A File Storage Service is created and mounted across the different components so you can easily create component configurations that require a persistent volume.
Now let’s talk about the Node pools.
Oracle WebLogic Server for OKE creates two node pools in the OKE cluster. The first, the WebLogic node pool, is configured to run pods that use images containing WebLogic binaries. The second, the non-WebLogic node pool, is configured to run pods that use images that do not contain WebLogic binaries. Separate node pools are created so that you will be charged for the entitlement to use WebLogic software only on the OCPUs associated with the WebLogic node pool. You will not be charged for the entitlement to use WebLogic software on the non-WebLogic node pool.
Here are the pods that are configured to run in each node pool after provisioning is completed:
Getting StartedTo get started you will need an Oracle Cloud account. If you do not already have an Oracle Cloud Account, go here to create a new Free Tier account. See the tutorial Get Started with Oracle WebLogic Server for OKEFor more information on Oracle WebLogic Server for OKE, review our product documentation. Then go to the Oracle Cloud Marketplace and test out the new way to run your Oracle WebLogic Server applications in Oracle Cloud.