Skip to content

Latest commit

 

History

History
123 lines (113 loc) · 5.38 KB

04-wls-domain.md

File metadata and controls

123 lines (113 loc) · 5.38 KB
Raw

Running a WebLogic Domain

The WebLogic Server Kubernetes Operator has detailed documentation about creating domains, including important considerations and different options to consider. For more information, see Manage WebLogic Domains. To integrate with Prometheus, the only extra step needed is to install the wls-exporter web application to WebLogic Servers/clusters.

In this step, we provide scripts that create a demonstration domain.

Set Proxy Before Run

In the following scripts, we use wget to download the WebLogic Deploy Tool archive from GitHub. If you are behind a proxy, you need to configure the proxy settings properly. One approach is to use proxy variables:

export http_proxy=http://proxy_host:proxy_port
export https_proxy=$http_proxy

Verify that the download with wget works correctly.

wget https://github.com/oracle/weblogic-deploy-tooling/releases/download/release-2.4.2/weblogic-deploy.zip \
-O /dev/null

Build the Domain Image

We provide a script wrapper build.sh to help you do this.
See the script usage:

usage: ./build.sh domainName adminUser adminPwd mysqlUser mysqlPwd

Build a domain image.

cd demo-domains/domainBuilder
./build.sh domain1 weblogic welcome1  wluser1 wlpwd123
cd ../..

A Docker image domain1-image:1.0 will be created. Note that the database name is the same as the domain name.

The domain configuration is burned into the image. What's in the domain configuration?

  • One data source, one JDBC store, one JMS server, and a JMS module. All the resources are deployed to the cluster.
  • Two web applications deployed to cluster: test-webapp and wls-exporter.

Deploy the Domain Resource

Create namespace weblogic

kubectl create ns weblogic
kubectl label ns weblogic weblogic-operator=enabled

Create a secret for the WebLogic administrative credential.

kubectl -n weblogic create secret generic domain1-weblogic-credentials \
      --from-literal=username=weblogic \
      --from-literal=password=welcome1

Deploy the domain resource. The resource is deployed to the weblogic namespace.

kubectl apply -f demo-domains/domain1.yaml

Now the operator will detect this new domain resource and run a WebLogic domain based on it.

Verification

Wait until the three WebLogic Server pods are running and ready.

kubectl get pod -l weblogic.domainName=domain1 -n weblogic

output

NAME                       READY   STATUS    RESTARTS   AGE
domain1-admin-server       1/1     Running   0          32h
domain1-managed-server-1   1/1     Running   0          32h
domain1-managed-server-2   1/1     Running   0          32h

Check the generated services.

kubectl get service -l weblogic.domainName=domain1 -n weblogic

output

NAME                            TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)                          AGE
domain1-admin-server            ClusterIP   None             <none>        30012/TCP,7001/TCP               32h
domain1-admin-server-external   NodePort    10.109.88.166    <none>        30012:30703/TCP,7001:30701/TCP   32h
domain1-cluster-cluster-1       ClusterIP   10.107.190.137   <none>        8001/TCP                         32h
domain1-managed-server-1        ClusterIP   None             <none>        8001/TCP                         32h
domain1-managed-server-2        ClusterIP   None             <none>        8001/TCP                         32h

You can access the WebLogic Server Administration Console from your browser at http://<hostname>:30701/console.

Check the WebLogic Runtime Metrics

The exported metrics are plain text and human-readable. We can use curl or similar tools to check the metrics.

Let's deploy the curl tool.

kubectl apply -f ./util/curl.yaml

Wait until the curl pod is running.

kubectl get pod curl -n weblogic

output

NAME   READY   STATUS    RESTARTS   AGE
curl   1/1     Running   5          1h

Access the metrics of managed-server-1.

kubectl exec curl -n weblogic -- curl http://weblogic:welcome1@domain1-managed-server-1:8001/wls-exporter/metrics

Access the metrics of managed-server-2.

kubectl exec curl -n weblogic -- curl http://weblogic:welcome1@domain1-managed-server-2:8001/wls-exporter/metrics

output

wls_server_admin_server_listen_port{location="managed-server-1"} 7001
wls_server_open_sockets_current_count{location="managed-server-1"} 8
wls_server_state_val{location="managed-server-1"} 2
wls_servlet_execution_time_average{location="managed-server-1",app="bea_wls_cluster_internal",name="managed-server-1_/bea_wls_cluster_internal",servletName="FileServlet"} 0
...
wls_webapp_config_deployment_state{location="managed-server-1",app="bea_wls_cluster_internal",name="managed-server-1_/bea_wls_cluster_internal"} 2
...
wls_datasource_active_connections_average_count{name="Generic1"} 2
...
wls_jms_bytes_current_count{jmsruntime="managed-server-1.jms",jmsserver="JMSServer1@managed-server-1"} 360324
wls_jms_bytes_high_count{jmsruntime="managed-server-1.jms",jmsserver="JMSServer1@managed-server-1"} 360324
...

All the metric names start with "wls_" and the metric names of different components have different prefixes which match what we configured in the exporter configuration.

Next: Setting up Prometheus