Use this Quick Start to create an Oracle SOA Suite domain deployment in a Kubernetes cluster (on-premise environments) with the WebLogic Kubernetes Operator. Note that this walkthrough is for demonstration purposes only, not for use in production. These instructions assume that you are already familiar with Kubernetes. If you need more detailed instructions, refer to the Install Guide.
The Linux kernel supported for deploying and running Oracle SOA Suite domains with the operator is Oracle Linux 7 (UL6+) and Red Hat Enterprise Linux 7 (UL3+ only with standalone Kubernetes). Refer to the prerequisites for more details.
For this exercise, the minimum hardware requirements to create a single-node Kubernetes cluster and then deploy the soaosb (Oracle SOA Suite, Oracle Service Bus, and Enterprise Scheduler (ESS)) domain type with one Managed Server for Oracle SOA Suite and one for the Oracle Service Bus cluster, along with Oracle Database running as a container are:
| Hardware | Size |
|---|---|
| RAM | 32GB |
| Disk Space | 250GB+ |
| CPU core(s) | 6 |
See here for resource sizing information for Oracle SOA Suite domains set up on a Kubernetes cluster.
Use the steps in this topic to create a single-instance on-premise Kubernetes cluster and then create an Oracle SOA Suite soaosb domain type, which deploys a domain with Oracle SOA Suite, Oracle Service Bus, and Oracle Enterprise Scheduler (ESS).
For illustration purposes, these instructions are for Oracle Linux 7u6+. If you are using a different flavor of Linux, you will need to adjust the steps accordingly.
These steps must be run with the root user, unless specified otherwise.
Any time you see YOUR_USERID in a command, you should replace it with your actual userid.
Choose the directories where your Docker and Kubernetes files will be stored. The Docker directory should be on a disk with a lot of free space (more than 100GB) because it will be used for the Docker file system, which contains all of your images and containers. The Kubernetes directory is used for the /var/lib/kubelet file system and persistent volume storage.
$ export docker_dir=/u01/docker
$ export kubelet_dir=/u01/kubelet
$ mkdir -p $docker_dir $kubelet_dir
$ ln -s $kubelet_dir /var/lib/kubelet
Verify that IPv4 forwarding is enabled on your host.
Note: Replace eth0 with the ethernet interface name of your compute resource if it is different.
$ /sbin/sysctl -a 2>&1|grep -s 'net.ipv4.conf.docker0.forwarding'
$ /sbin/sysctl -a 2>&1|grep -s 'net.ipv4.conf.eth0.forwarding'
$ /sbin/sysctl -a 2>&1|grep -s 'net.ipv4.conf.lo.forwarding'
$ /sbin/sysctl -a 2>&1|grep -s 'net.ipv4.ip_nonlocal_bind'
For example: Verify that all are set to 1:
$ net.ipv4.conf.docker0.forwarding = 1
$ net.ipv4.conf.eth0.forwarding = 1
$ net.ipv4.conf.lo.forwarding = 1
$ net.ipv4.ip_nonlocal_bind = 1
Solution: Set all values to 1 immediately:
$ /sbin/sysctl net.ipv4.conf.docker0.forwarding=1
$ /sbin/sysctl net.ipv4.conf.eth0.forwarding=1
$ /sbin/sysctl net.ipv4.conf.lo.forwarding=1
$ /sbin/sysctl net.ipv4.ip_nonlocal_bind=1
To preserve the settings permanently: Update the above values to 1 in files in /usr/lib/sysctl.d/, /run/sysctl.d/, and /etc/sysctl.d/.
Verify the iptables rule for forwarding.
Kubernetes uses iptables to handle many networking and port forwarding rules. A standard Docker installation may create a firewall rule that prevents forwarding.
Verify if the iptables rule to accept forwarding traffic is set:
$ /sbin/iptables -L -n | awk '/Chain FORWARD / {print $4}' | tr -d ")"
If the output is “DROP”, then run the following command:
$ /sbin/iptables -P FORWARD ACCEPT
Verify if the iptables rule is properly set to “ACCEPT”:
$ /sbin/iptables -L -n | awk '/Chain FORWARD / {print $4}' | tr -d ")"
Disable and stop firewalld:
$ systemctl disable firewalld
$ systemctl stop firewalld
Note: If you have already installed Docker with version 19.03.1+ and configured the Docker daemon root to sufficient disk space along with proxy settings, continue to Install and configure Kubernetes.
Make sure that you have the right operating system version:
$ uname -a
$ more /etc/oracle-release
Example output:
Linux xxxxxxx 4.1.12-124.27.1.el7uek.x86_64 #2 SMP Mon May 13 08:56:17 PDT 2019 x86_64 x86_64 x86_64 GNU/Linux
Oracle Linux Server release 7.6
Install the latest docker-engine and start the Docker service:
$ docker_version="19.03.1.ol"
$ yum-config-manager --enable ol7_addons
$ yum install docker-engine-$docker_version
$ systemctl enable docker
$ systemctl start docker
Add your user ID to the Docker group to allow you to run Docker commands without root access:
$ /sbin/usermod -a -G docker <YOUR_USERID>
Check that your Docker version is at least 18.03:
$ docker version
Example output:
Client: Docker Engine - Community
Version: 19.03.1-ol
API version: 1.40
Go version: go1.12.5
Git commit: ead9442
Built: Wed Sep 11 06:40:28 2019
OS/Arch: linux/amd64
Experimental: false
Server: Docker Engine - Community
Engine:
Version: 19.03.1-ol
API version: 1.40 (minimum version 1.12)
Go version: go1.12.5
Git commit: ead9442
Built: Wed Sep 11 06:38:43 2019
OS/Arch: linux/amd64
Experimental: false
Default Registry: docker.io
containerd:
Version: v1.2.0-rc.0-108-gc444666
GitCommit: c4446665cb9c30056f4998ed953e6d4ff22c7c39
runc:
Version: 1.0.0-rc5+dev
GitCommit: 4bb1fe4ace1a32d3676bb98f5d3b6a4e32bf6c58
docker-init:
Version: 0.18.0
GitCommit: fec3683
Update the Docker engine configuration:
$ mkdir -p /etc/docker
$ cat <<EOF > /etc/docker/daemon.json
{
"group": "docker",
"data-root": "/u01/docker"
}
EOF
Configure proxy settings if you are behind an HTTP proxy:
### Create the drop-in file /etc/systemd/system/docker.service.d/http-proxy.conf that contains proxy details:
$ cat <<EOF > /etc/systemd/system/docker.service.d/http-proxy.conf
[Service]
Environment="HTTP_PROXY=http://REPLACE-WITH-YOUR-COMPANY-PROXY-HOST:PORT"
Environment="HTTPS_PROXY=http://REPLACE-WITH-YOUR-COMPANY-PROXY-HOST:PORT"
Environment="NO_PROXY=localhost,127.0.0.0/8,ADD-YOUR-INTERNAL-NO-PROXY-LIST,/var/run/docker.sock"
EOF
Note: On some hosts
/etc/systemd/system/docker.service.dmay not be available. Create this directory if it is not available.
Restart the Docker daemon to load the latest changes:
$ systemctl daemon-reload
$ systemctl restart docker
Verify that the proxy is configured with Docker:
$ docker info|grep -i proxy
Example output:
HTTP Proxy: http://REPLACE-WITH-YOUR-COMPANY-PROXY-HOST:PORT
HTTPS Proxy: http://REPLACE-WITH-YOUR-COMPANY-PROXY-HOST:PORT
No Proxy: localhost,127.0.0.0/8,ADD-YOUR-INTERNAL-NO-PROXY-LIST,/var/run/docker.sock
Verify Docker installation:
$ docker run hello-world
Example output:
Hello from Docker!
This message shows that your installation appears to be working correctly.
To generate this message, Docker took the following steps:
1. The Docker client contacted the Docker daemon.
2. The Docker daemon pulled the "hello-world" image from the Docker Hub.
(amd64)
3. The Docker daemon created a new container from that image which runs the
executable that produces the output you are currently reading.
4. The Docker daemon streamed that output to the Docker client, which sent it to your terminal.
To try something more ambitious, you can run an Ubuntu container with:
$ docker run -it ubuntu bash
Share images, automate workflows, and more with a free Docker ID:
https://hub.docker.com/
For more examples and ideas, visit:
https://docs.docker.com/get-started/
Add the external Kubernetes repository:
$ cat <<EOF | sudo tee /etc/yum.repos.d/kubernetes.repo
[kubernetes]
name=Kubernetes
baseurl=https://packages.cloud.google.com/yum/repos/kubernetes-el7-\$basearch
enabled=1
gpgcheck=1
repo_gpgcheck=1
gpgkey=https://packages.cloud.google.com/yum/doc/yum-key.gpg https://packages.cloud.google.com/yum/doc/rpm-package-key.gpg
exclude=kubelet kubeadm kubectl
EOF
Set SELinux in permissive mode (effectively disabling it):
$ export PATH=/sbin:$PATH
$ setenforce 0
$ sed -i 's/^SELINUX=enforcing$/SELINUX=permissive/' /etc/selinux/config
Export proxy and install kubeadm, kubelet, and kubectl:
### Get the nslookup IP address of the master node to use with apiserver-advertise-address during setting up Kubernetes master
### as the host may have different internal ip (hostname -i) and nslookup $HOSTNAME
$ ip_addr=`nslookup $(hostname -f) | grep -m2 Address | tail -n1| awk -F: '{print $2}'| tr -d " "`
$ echo $ip_addr
### Set the proxies
$ export NO_PROXY=localhost,127.0.0.0/8,ADD-YOUR-INTERNAL-NO-PROXY-LIST,/var/run/docker.sock,$ip_addr
$ export no_proxy=localhost,127.0.0.0/8,ADD-YOUR-INTERNAL-NO-PROXY-LIST,/var/run/docker.sock,$ip_addr
$ export http_proxy=http://REPLACE-WITH-YOUR-COMPANY-PROXY-HOST:PORT
$ export https_proxy=http://REPLACE-WITH-YOUR-COMPANY-PROXY-HOST:PORT
$ export HTTPS_PROXY=http://REPLACE-WITH-YOUR-COMPANY-PROXY-HOST:PORT
$ export HTTP_PROXY=http://REPLACE-WITH-YOUR-COMPANY-PROXY-HOST:PORT
### Install Kubernetes
$ VERSION=1.23.6-0
$ yum install -y kubelet-$VERSION kubeadm-$VERSION kubectl-$VERSION --disableexcludes=kubernetes
### Enable kubelet service so that it automatically restarts on reboot
$ systemctl enable --now kubelet
Ensure net.bridge.bridge-nf-call-iptables is set to 1 in your sysctl to avoid traffic routing issues:
$ cat <<EOF > /etc/sysctl.d/k8s.conf
net.bridge.bridge-nf-call-ip6tables = 1
net.bridge.bridge-nf-call-iptables = 1
EOF
$ sysctl --system
Disable swap check:
$ sed -i 's/KUBELET_EXTRA_ARGS=/KUBELET_EXTRA_ARGS="--fail-swap-on=false"/' /etc/sysconfig/kubelet
$ cat /etc/sysconfig/kubelet
### Reload and restart kubelet
$ systemctl daemon-reload
$ systemctl restart kubelet
From Kubernetes version v1.22 onward, kubeadm will default cgroup-driver to systemd. If your Docker is using cgroup driver as cgroupfs, set --cgroup-driver=cgroupfs for kubelet.
$ sed -i 's/^KUBELET_EXTRA_ARGS=.*/KUBELET_EXTRA_ARGS="--fail-swap-on=false --cgroup-driver=cgroupfs"/' /etc/sysconfig/kubelet
$ cat /etc/sysconfig/kubelet
### Reload and restart kubelet
$ systemctl daemon-reload
$ systemctl restart kubelet
Install Helm v3.3.4+.
a. Download Helm from https://github.com/helm/helm/releases.
For example, to download Helm v3.5.4:
$ wget https://get.helm.sh/helm-v3.5.4-linux-amd64.tar.gz
b. Unpack tar.gz:
$ tar -zxvf helm-v3.5.4-linux-amd64.tar.gz
c. Find the Helm binary in the unpacked directory, and move it to its desired destination:
$ mv linux-amd64/helm /usr/bin/helm
Run helm version to verify its installation:
$ helm version
version.BuildInfo{Version:"v3.5.4", GitCommit:"1b5edb69df3d3a08df77c9902dc17af864ff05d1", GitTreeState:"clean", GoVersion:"go1.15.11"}
Notes:
- These steps must be run with the
rootuser, unless specified otherwise!- If you choose to use a different CIDR block (that is, other than
10.244.0.0/16for the--pod-network-cidr=in thekubeadm initcommand), then also updateNO_PROXYandno_proxywith the appropriate value.
- Also make sure to update
kube-flannel.yamlwith the new value before deploying.- Replace the following with appropriate values:
ADD-YOUR-INTERNAL-NO-PROXY-LISTREPLACE-WITH-YOUR-COMPANY-PROXY-HOST:PORT
Create a shell script that sets up the necessary environment variables. You can append this to the user’s .bashrc so that it will run at login. You must also configure your proxy settings here if you are behind an HTTP proxy:
## grab my IP address to pass into kubeadm init, and to add to no_proxy vars
ip_addr=`nslookup $(hostname -f) | grep -m2 Address | tail -n1| awk -F: '{print $2}'| tr -d " "`
export pod_network_cidr="10.244.0.0/16"
export service_cidr="10.96.0.0/12"
export PATH=$PATH:/sbin:/usr/sbin
### Set the proxies
export NO_PROXY=localhost,.svc,127.0.0.0/8,ADD-YOUR-INTERNAL-NO-PROXY-LIST,/var/run/docker.sock,$ip_addr,$pod_network_cidr,$service_cidr
export no_proxy=localhost,.svc,127.0.0.0/8,ADD-YOUR-INTERNAL-NO-PROXY-LIST,/var/run/docker.sock,$ip_addr,$pod_network_cidr,$service_cidr
export http_proxy=http://REPLACE-WITH-YOUR-COMPANY-PROXY-HOST:PORT
export https_proxy=http://REPLACE-WITH-YOUR-COMPANY-PROXY-HOST:PORT
export HTTPS_PROXY=http://REPLACE-WITH-YOUR-COMPANY-PROXY-HOST:PORT
export HTTP_PROXY=http://REPLACE-WITH-YOUR-COMPANY-PROXY-HOST:PORT
Source the script to set up your environment variables:
$ . ~/.bashrc
To implement command completion, add the following to the script:
$ [ -f /usr/share/bash-completion/bash_completion ] && . /usr/share/bash-completion/bash_completion
$ source <(kubectl completion bash)
Run kubeadm init to create the master node:
$ kubeadm init \
--pod-network-cidr=$pod_network_cidr \
--apiserver-advertise-address=$ip_addr \
--ignore-preflight-errors=Swap > /tmp/kubeadm-init.out 2>&1
Log in to the terminal with YOUR_USERID:YOUR_GROUP. Then set up the ~/.bashrc similar to steps 1 to 3 with YOUR_USERID:YOUR_GROUP.
Note that from now on we will be using
YOUR_USERID:YOUR_GROUPto execute anykubectlcommands and notroot.
Set up YOUR_USERID:YOUR_GROUP to access the Kubernetes cluster:
$ mkdir -p $HOME/.kube
$ sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
$ sudo chown $(id -u):$(id -g) $HOME/.kube/config
Verify that YOUR_USERID:YOUR_GROUP is set up to access the Kubernetes cluster using the kubectl command:
$ kubectl get nodes
Note: At this step, the node is not in ready state as we have not yet installed the pod network add-on. After the next step, the node will show status as Ready.
Install a pod network add-on (flannel) so that your pods can communicate with each other.
Note: If you are using a different CIDR block than
10.244.0.0/16, then download and updatekube-flannel.ymlwith the correct CIDR address before deploying into the cluster:
$ wget https://raw.githubusercontent.com/flannel-io/flannel/v0.17.0/Documentation/kube-flannel.yml
$ ### Update the CIDR address if you are using a CIDR block other than the default 10.244.0.0/16
$ kubectl apply -f kube-flannel.yml
Verify that the master node is in Ready status:
$ kubectl get nodes
Sample output:
NAME STATUS ROLES AGE VERSION
mymasternode Ready control-plane,master 12h v1.23.6
or:
$ kubectl get pods -n kube-system
Sample output:
NAME READY STATUS RESTARTS AGE
pod/coredns-86c58d9df4-58p9f 1/1 Running 0 3m59s
pod/coredns-86c58d9df4-mzrr5 1/1 Running 0 3m59s
pod/etcd-mymasternode 1/1 Running 0 3m4s
pod/kube-apiserver-node 1/1 Running 0 3m21s
pod/kube-controller-manager-mymasternode 1/1 Running 0 3m25s
pod/kube-flannel-ds-6npx4 1/1 Running 0 49s
pod/kube-proxy-4vsgm 1/1 Running 0 3m59s
pod/kube-scheduler-mymasternode 1/1 Running 0 2m58s
To schedule pods on the master node, taint the node:
$ kubectl taint nodes --all node-role.kubernetes.io/master-
Congratulations! Your Kubernetes cluster environment is ready to deploy your Oracle SOA Suite domain.
Refer to the official documentation to set up a Kubernetes cluster.
Follow these steps to set up the source code repository required to deploy Oracle SOA Suite domains.
Pull the WebLogic Kubernetes Operator image:
$ docker pull ghcr.io/oracle/weblogic-kubernetes-operator:3.4.0
$ docker tag ghcr.io/oracle/weblogic-kubernetes-operator:3.4.0 oracle/weblogic-kubernetes-operator:3.4.0
Obtain the Oracle Database image and Oracle SOA Suite Docker image from the Oracle Container Registry:
a. For first time users, to pull an image from the Oracle Container Registry, navigate to https://container-registry.oracle.com and log in using the Oracle Single Sign-On (SSO) authentication service. If you do not already have SSO credentials, you can create an Oracle Account using: https://profile.oracle.com/myprofile/account/create-account.jspx.
Use the web interface to accept the Oracle Standard Terms and Restrictions for the Oracle software images that you intend to deploy. Your acceptance of these terms are stored in a database that links the software images to your Oracle Single Sign-On login credentials.
To obtain the image, log in to the Oracle Container Registry:
$ docker login container-registry.oracle.com
b. Find and then pull the Oracle Database image for 12.2.0.1:
$ docker pull container-registry.oracle.com/database/enterprise:12.2.0.1-slim
c. Find and then pull the prebuilt Oracle SOA Suite image 12.2.1.4 install image:
$ docker pull container-registry.oracle.com/middleware/soasuite:12.2.1.4
Note: This image does not contain any Oracle SOA Suite product patches and can only be used for test and development purposes.
Create a namespace opns for the operator:
$ kubectl create namespace opns
Create a service account op-sa for the operator in the operator’s namespace:
$ kubectl create serviceaccount -n opns op-sa
Use Helm to install and start the operator from the directory you just cloned:
$ cd ${WORKDIR}
$ helm install weblogic-kubernetes-operator charts/weblogic-operator \
--namespace opns \
--set image=oracle/weblogic-kubernetes-operator:3.4.0 \
--set serviceAccount=op-sa \
--set "domainNamespaces={}" \
--wait
Verify that the operator’s pod is running by listing the pods in the operator’s namespace. You should see one for the operator:
$ kubectl get pods -n opns
Verify that the operator is up and running by viewing the operator pod’s logs:
$ kubectl logs -n opns -c weblogic-operator deployments/weblogic-operator
The WebLogic Kubernetes Operator v3.4.0 has been installed. Continue with the load balancer and Oracle SOA Suite domain setup.
The WebLogic Kubernetes Operator supports these load balancers: Traefik, NGINX, and Apache. Samples are provided in the documentation.
This Quick Start demonstrates how to install the Traefik ingress controller to provide load balancing for an Oracle SOA Suite domain.
Create a namespace for Traefik:
$ kubectl create namespace traefik
Set up Helm for 3rd party services:
$ helm repo add traefik https://helm.traefik.io/traefik --force-update
Install the Traefik operator in the traefik namespace with the provided sample values:
$ cd ${WORKDIR}
$ helm install traefik traefik/traefik \
--namespace traefik \
--values charts/traefik/values.yaml \
--set "kubernetes.namespaces={traefik}" \
--set "service.type=NodePort" \
--wait
Create a namespace that can host Oracle SOA Suite domains:
$ kubectl create namespace soans
Use Helm to configure the operator to manage Oracle SOA Suite domains in this namespace:
$ cd ${WORKDIR}
$ helm upgrade weblogic-kubernetes-operator charts/weblogic-operator \
--reuse-values \
--namespace opns \
--set "domainNamespaces={soans}" \
--wait
Create Kubernetes secrets.
a. Create a Kubernetes secret for the domain in the same Kubernetes namespace as the domain. In this example, the username is weblogic, the password is Welcome1, and the namespace is soans:
$ cd ${WORKDIR}/create-weblogic-domain-credentials
$ ./create-weblogic-credentials.sh \
-u weblogic \
-p Welcome1 \
-n soans \
-d soainfra \
-s soainfra-domain-credentials
b. Create a Kubernetes secret for the RCU in the same Kubernetes namespace as the domain:
SOA1Oradoc_db1Oradoc_db1soainfrasoanssoainfra-rcu-credentials$ cd ${WORKDIR}/create-rcu-credentials
$ ./create-rcu-credentials.sh \
-u SOA1 \
-p Oradoc_db1 \
-a sys \
-q Oradoc_db1 \
-d soainfra \
-n soans \
-s soainfra-rcu-credentials
Create the Kubernetes persistence volume and persistence volume claim.
a. Create the Oracle SOA Suite domain home directory.
Determine if a user already exists on your host system with uid:gid of 1000:0:
$ sudo getent passwd 1000
If this command returns a username (which is the first field), you can skip the following useradd command. If not, create the oracle user with useradd:
$ sudo useradd -u 1000 -g 0 oracle
Create the directory that will be used for the Oracle SOA Suite domain home:
$ sudo mkdir /scratch/k8s_dir
$ sudo chown -R 1000:0 /scratch/k8s_dir
b. The create-pv-pvc-inputs.yaml has the following values by default:
domainsoainfrasoans/scratch/k8s_dirReview and update if any changes required.
$ cd ${WORKDIR}/create-weblogic-domain-pv-pvc
$ vim create-pv-pvc-inputs.yaml
c. Run the create-pv-pvc.sh script to create the PV and PVC configuration files:
$ cd ${WORKDIR}/create-weblogic-domain-pv-pvc
$ ./create-pv-pvc.sh -i create-pv-pvc-inputs.yaml -o output
d. Create the PV and PVC using the configuration files created in the previous step:
$ kubectl create -f output/pv-pvcs/soainfra-domain-pv.yaml
$ kubectl create -f output/pv-pvcs/soainfra-domain-pvc.yaml
Install and configure the database for the Oracle SOA Suite domain.
This step is required only when a standalone database is not already set up and you want to use the database in a container.
The Oracle Database Docker images are supported only for non-production use. For more details, see My Oracle Support note: Oracle Support for Database Running on Docker (Doc ID 2216342.1). For production, it is suggested to use a standalone database. This example provides steps to create the database in a container.
a. Create a database in a container:
$ cd ${WORKDIR}/create-oracle-db-service
$ ./start-db-service.sh -i container-registry.oracle.com/database/enterprise:12.2.0.1-slim -p none
Once the database is successfully created, you can use the database connection string oracle-db.default.svc.cluster.local:1521/devpdb.k8s as an rcuDatabaseURL parameter in the create-domain-inputs.yaml file.
b. Create Oracle SOA Suite schemas for the domain type (for example, soaosb).
To install the Oracle SOA Suite schemas, run the create-rcu-schema.sh script with the following inputs:
-s <RCU PREFIX>-t <SOA domain type>-d <Oracle Database URL>-i <SOASuite image>-n <Namespace>-q <SYSDBA Database password>-r <Schema password>-c <Comma-separated variables>-l <Timeout limit in seconds. (optional). (default: 300)>For example:
$ cd ${WORKDIR}/create-rcu-schema
$ ./create-rcu-schema.sh \
-s SOA1 \
-t soaosb \
-d oracle-db.default.svc.cluster.local:1521/devpdb.k8s \
-i container-registry.oracle.com/middleware/soasuite:12.2.1.4 \
-n default \
-q Oradoc_db1 \
-r Oradoc_db1 \
-c SOA_PROFILE_TYPE=SMALL,HEALTHCARE_INTEGRATION=NO
Now the environment is ready to start the Oracle SOA Suite domain creation.
The sample scripts for Oracle SOA Suite domain deployment are available at ${WORKDIR}/create-soa-domain/domain-home-on-pv. You must edit create-domain-inputs.yaml (or a copy of it) to provide the details for your domain.
Update create-domain-inputs.yaml with the following values for domain creation:
domainType: soaosbinitialManagedServerReplicas: 1$ cd ${WORKDIR}/create-soa-domain/domain-home-on-pv/
$ cp create-domain-inputs.yaml create-domain-inputs.yaml.orig
$ sed -i -e "s:domainType\: soa:domainType\: soaosb:g" create-domain-inputs.yaml
$ sed -i -e "s:initialManagedServerReplicas\: 2:initialManagedServerReplicas\: 1:g" create-domain-inputs.yaml
$ sed -i -e "s:image\: soasuite\:12.2.1.4:image\: container-registry.oracle.com/middleware/soasuite\:12.2.1.4:g" create-domain-inputs.yaml
Run the create-domain.sh script to create a domain:
$ cd ${WORKDIR}/create-soa-domain/domain-home-on-pv/
$ ./create-domain.sh -i create-domain-inputs.yaml -o output
Create a Kubernetes domain object:
Once the create-domain.sh is successful, it generates output/weblogic-domains/soainfra/domain.yaml, which you can use to create the Kubernetes resource domain to start the domain and servers:
$ cd ${WORKDIR}/create-soa-domain/domain-home-on-pv
$ kubectl create -f output/weblogic-domains/soainfra/domain.yaml
Verify that the Kubernetes domain object named soainfra is created:
$ kubectl get domain -n soans
NAME AGE
soainfra 3m18s
Once you create the domain, the introspect pod is created. This inspects the domain home and then starts the soainfra-adminserver pod. Once the soainfra-adminserver pod starts successfully, the Managed Server pods are started in parallel.
Watch the soans namespace for the status of domain creation:
$ kubectl get pods -n soans -w
Verify that the Oracle SOA Suite domain server pods and services are created and in Ready state:
$ kubectl get all -n soans
Configure Traefik to manage ingresses created in the Oracle SOA Suite domain namespace (soans):
$ helm upgrade traefik traefik/traefik \
--reuse-values \
--namespace traefik \
--set "kubernetes.namespaces={traefik,soans}" \
--wait
Create an ingress for the domain in the domain namespace by using the sample Helm chart:
$ cd ${WORKDIR}
$ export LOADBALANCER_HOSTNAME=$(hostname -f)
$ helm install soa-traefik-ingress charts/ingress-per-domain \
--namespace soans \
--values charts/ingress-per-domain/values.yaml \
--set "traefik.hostname=${LOADBALANCER_HOSTNAME}" \
--set domainType=soaosb
Verify the created ingress per domain details:
$ kubectl describe ingress soainfra-traefik -n soans
Get the LOADBALANCER_HOSTNAME for your environment:
$ export LOADBALANCER_HOSTNAME=$(hostname -f)
Verify the following URLs are available for Oracle SOA Suite domains of domain type soaosb:
Credentials:
username: weblogic
password: Welcome1
http://${LOADBALANCER_HOSTNAME}:30305/console
http://${LOADBALANCER_HOSTNAME}:30305/em
http://${LOADBALANCER_HOSTNAME}:30305/servicebus
http://${LOADBALANCER_HOSTNAME}:30305/soa-infra
http://${LOADBALANCER_HOSTNAME}:30305/soa/composer
http://${LOADBALANCER_HOSTNAME}:30305/integration/worklistapp
http://${LOADBALANCER_HOSTNAME}:30305/ess
http://${LOADBALANCER_HOSTNAME}:30305/EssHealthCheck