We’re excited to announce that Oracle WebLogic Server for Oracle Cloud Infrastructure Container Engine for Kubernetes (WebLogic Server for OKE) is now available through the Oracle Cloud Marketplace. Configuring Oracle WebLogic Server on OKE has never been so easy and fast. Within minutes you can generate an Oracle WebLogic Server configuration on OKE and on top of that you will get a Jenkins controller configured for OKE and CI/CD pipeline jobs to support Oracle WebLogic Server life cycle management operations.
The Oracle WebLogic Server for OKE topology
In each configuration you create, you will get:
- An OKE cluster deployed in a private subnet with two node pools.
- A File Storage Service that is shared across pods.
- An Administrative host deployed in a private subnet to easily access the following:
- The OKE cluster
- Logs of Oracle WebLogic Server domain
- Jenkins home configuration
- Helper scripts to manage your domain
- The shared File System.
- A bastion host deployed in a public subnet to access the resources deployed in the private subnet.
- An Internal load balancer to access the Jenkins console and Oracle WebLogic Server Administrative Console
- An External load balancer to access the Oracle WebLogic Server cluster.
The OKE deployments
The following applications are installed in the Kubernetes cluster using Helm:
- Jenkins CI. Configured to run as a pod in the non-WebLogic node pool, the Jenkins home configuration is stored in the shared File System. The Jenkins agents are configured to run as pods in the WebLogic node pool and are created on demand.
- NginX. The ingress controller is configured to run in the non-WebLogic node pool. As part of this module the required ingress rules are configured to route the requests coming from the internal Load Balancer to the administrative consoles.
- WebLogic Kubernetes Operator. The operator is configured to run in the non-WebLogic node pool
The Jenkins CI/CD pipeline Jobs
The first time you login to the Jenkins console you will be prompted to create the first admin user.
Out of the box you get the following Jenkins pipeline jobs:
- sample-app: Example job to deploy the sample-app application.
- jdk-patch: Use this job to quickly install a new JDK into the existing image.
- opatch-update: Use this job to install individual Oracle WebLogic Server patches.
- update-domain: Provide the WebLogic Deploy Tooling files to update your existing domain.
- rebase-full-install: Use this job to generate an image with a custom JDK, WebLogic binaries and patches.
- test-and-deploy-domain-job: This job is automatically run at the end of the other five jobs to test and deploy the domain.
These pipelines jobs use the WebLogic Kubernetes Toolkit to create the domain configuration and domain image that are used to run the WebLogic domain in the OKE cluster. The WebLogic Kubernetes domain model currently supported is Domain Home in Image. We are actively evaluating support for the Model in Image domain model as well.
To 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 OKE. For more information on Oracle WebLogic Server for Oracle Cloud Infrastructure Container Engine for Kubernetes, review our product documentation. Then go to the Oracle Cloud Marketplace and test out a new way to run your Oracle WebLogic Server applications in Oracle Cloud.