Pre-Requisites:

– WebLogic Domain hosted in a Kubernetes environment.

Here is an example of creating a WebLogic Server Domain using WebLogic Kubernetes Operator in OCNE:

Link: https://blogs.oracle.com/blogbypuneeth/post/weblogic-server-deployment-in-a-kubernetes-cluster-using-weblogic-kubernetes-operator-wko

– Install WebLogic Remote Console:

https://blogs.oracle.com/blogbypuneeth/post/exploring-weblogic-remote-console

 

Quick Commands: (Run the following commands to configure IngressRoute in your Kubernetes Environment – required for WebLogic Remote Console)

kubectl apply -f https://raw.githubusercontent.com/TheLearnLoop/blogbypuneeth/main/traefik-pathrouting-1.yaml –namespace sample-domain1-ns

Run the following command to confirm the ‘/management’ URL is accessible:

curl –user weblogic:Welcome1 http://localhost:30305/management/weblogic/latest/domainRuntime?fields=name\&links=none ; echo

You should now be able to connect to WebLogic on Kubernetes environment via WebLogic Remote Console.

 

Let’s have a look at the steps in detail:

 

I have a Kubernetes cluster created using OCNE 1.7 and I used WebLogic Kubernetes Operator to install a sample WebLogic Domain.

Lets have a look at the pods and Ingress Routes already present in this environment:

List the pods:

kubectl get po -A

 List the IngressRoutes created:

kubectl get IngressRoutes -A

 Check the port mapping in Traefik:

kubectl get services -n traefik

 

k1

We see that there are two IngressRoutes created and one of these is for ‘/console’. Let’s do a curl and check if it works:

curl http://<host>:30305/console

k21

 

We should be able to access the console from an external machine using http://<host>:30305/console, but you would get a 404 when you try to connect to WebLogic via WebLogic Remote Console.

k3

 

You can also test this using:

curl http://<host>:30305/management

Exec into the WebLogic Admin Server pod and try the management url again to confirm that it is an issue with Ingress Route.

curl http://localhost:7001/management

 You wil see a 401 instead of a 404 error page. 

curl –user weblogic:xxx http://localhost:7001/management/weblogic/latest/serverRuntime?fields=name\&links=none ; echo

And confirm that you see the following output:

{“name”: “admin-server”}

 

k2

WebLogic Remote Console uses WLS REST API to connect to WebLogic Domain and an ingress route has to be configured to allow traffic to ‘/management’

“The Administration Server uses REST to communicate with itself and its Managed Servers. When REST communication is blocked, the Monitoring perspective of WebLogic Remote Console can neither report accurate information on the statuses or statistics of Managed servers nor perform most management tasks. Also, the Edit perspective cannot create or remove deployments.”

Lets create a new IngressRoute:

kubectl apply -f https://raw.githubusercontent.com/TheLearnLoop/blogbypuneeth/main/traefik-pathrouting-1.yaml –namespace sample-domain1-ns

 

k23

 

traefik-pathrouting-1.yaml :
apiVersion: traefik.containo.us/v1alpha1
kind: IngressRoute
metadata:
  annotations:
    kubernetes.io/ingress.class: traefik
  name: traefik-pathrouting-1
  namespace: sample-domain1-ns
spec:
  routes:
  – kind: Rule
    match: PathPrefix(`/`)
    services:
    – kind: Service
      name: sample-domain1-admin-server
      namespace: sample-domain1-ns
      port: 7001

Run the following command to confirm that the IngressRoute for ‘/management’ URL is successfully configured :

curl –user weblogic:<password> http://localhost:30305/management/weblogic/latest/domainRuntime?fields=name\&links=none ; echo

k24

You should now be able to connect to WebLogic domain on Kubernetes Environment using WebLogic Remote Console:

k25