Create and Configure an Oracle SOA Suite Domain

Prepare for an Oracle SOA Suite domain.
1. Create a namespace that can host Oracle SOA Suite domains. Label the namespace with weblogic-operator=enabled to manage the domain.
```
kubectl create namespace soans
kubectl label namespace soans weblogic-operator=enabled
```
2. Create the Kubernetes persistence volume and persistence volume claim.
  1. 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
```
  2. The create-pv-pvc-inputs.yaml has the following values by default:
    - baseName: domain
    - domainUID: soainfra
    - namespace: soans
    - weblogicDomainStoragePath: /scratch/k8s_dir
    Review and update if any changes required.
```
cp create-pv-pvc-inputs.yaml create-pv-pvc-inputs-domain.yaml
      vi create-pv-pvc-inputs-domain.yaml
```
  3. Run the create-pv-pvc.sh script to create the PV and PVC configuration files using updated `create-pv-pvc-inputs-domain.yaml`:
```
cd ${WORKDIR}/create-weblogic-domain-pv-pvc
./create-pv-pvc.sh -i create-pv-pvc-inputs-domain.yaml -o output-domain
```
  4. Create the PV and PVC using the configuration files created in the previous step:
```
kubectl create -f  output-domain/pv-pvcs/soainfra-domain-pv.yaml
kubectl create -f  output-domain/pv-pvcs/soainfra-domain-pvc.yaml
```
3. Install 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. You can refer to [here to create an Oracle Database service in a Kubernetes. In this guide we will be using Single Instance Database on Kubernetes using helm chart to provision the Database without using an Oracle Database Operator.
  1. Clone the Oracle Database GitHub repository:
```
cd ${WORKDIR}
git clone https://github.com/oracle/docker-images.git
cd docker-images/OracleDatabase/SingleInstance/helm-charts
```
  2. Oracle database data files and configurations are stored at the /opt/oracle/oradata path of the container. Storage Class for Persistent Volume Claims has to be configured to keep the data persistence across deployments. If persistence is not desired, then you can skip the below steps and override the persistence to null using –set option. Follow the below steps to create the required Storage Class for Persistent Volume Claims:
    1. Create a directory used for database persistence.
      sudo mkdir /scratch/k8s_dir_db sudo chown -R 54321 /scratch/k8s_dir_db
    2. Update the create-pv-pvc-inputs.yaml for creating the Persistent Volume with below values:
      
      baseName: db
      
      namespace: default
      
      weblogicDomainStorageSize: 100Gi
      
      weblogicDomainStoragePath: /scratch/k8s_dir_db
      
      cd ${WORKDIR}/create-weblogic-domain-pv-pvc cp create-pv-pvc-inputs.yaml create-pv-pvc-inputs-db.yaml sed -i -e "s/baseName: domain/baseName: db/g" create-pv-pvc-inputs-db.yaml sed -i -e "s/namespace: soans/namespace: default/g" create-pv-pvc-inputs-db.yaml sed -i -e "s/k8s_dir/k8s_dir_db/g" create-pv-pvc-inputs-db.yaml sed -i -e "s/10Gi/100Gi/g" create-pv-pvc-inputs-db.yaml
    3. Run the create-pv-pvc.sh script to create the PV configuration file using updated create-pv-pvc-inputs-db.yaml:
      cd ${WORKDIR}/create-weblogic-domain-pv-pvc ./create-pv-pvc.sh -i create-pv-pvc-inputs-db.yaml -o output-db
      
      Note:
      Do not create the PVC because helm charts use the StorageClass name and create the PVC.
    4. The above script creates for both PV and PVC, but we will be only using PV configuration file created in previous step:
      kubectl create -f output-db/pv-pvcs/soainfra-db-pv.yaml
      
      Create a database in a container using the helm-charts::
      cd ${WORKDIR}/docker-images/OracleDatabase/SingleInstance/helm-charts helm install db19c \ --set persistence.storageClass=soainfra-db-storage-class \ --set imagePullPolicy=IfNotPresent \ oracle-db
      
      Verify the logs for database deployment until shows the message “DATABASE IS READY TO USE”:
      kubectl logs deployment.apps/db19c-oracle-db -f
      
      Get the password of the SYS user:
      kubectl get secret db19c-oracle-db -o jsonpath={.data.oracle_pwd} | base64 --decode; echo
      The helm-chart creates the required service to access the database using connection string db19c-oracle-db.default.svc.cluster.local:1521/ORCLPDB1 which will be used as an rcuDatabaseURL parameter in the create-domain-inputs.yaml file. In case you have used different Helm release name or configuration parameters for creating the database update the connection string accordingly.
      
      Create Oracle SOA Suite schemas for the domain type (for example, soaosb).
      
      Create a secret that contains the database’s SYSDBA username and password.
      
      kubectl -n default create secret generic oracle-rcu-secret \ --from-literal='sys_username=sys' \ --from-literal='sys_password=REPLACE-WITH-SYS-PASSWORD' \ --from-literal='password=REPLACE-WITH-SCHEMA-PASSWORD'
      
      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>
      
      -c <Name of credentials secret containing SYSDBA username and password and RCU schema owner password>
      
      -r <Comma-separated variables>
      
      -l <Timeout limit in seconds. (optional). (default: 300)>
      
      For example:
      
      ccd ${WORKDIR}/create-rcu-schema ./create-rcu-schema.sh \ -s SOA1 \ -t soaosb \ -d db19c-oracle-db.default.svc.cluster.local:1521/ORCLPDB1 \ -i container-registry.oracle.com/middleware/soasuite:14.1.2.0-<17 or 21>-<ol8 or ol9>-<tag> \ -n default \ -b EBR \ -c oracle-rcu-secret \ -r SOA_PROFILE_TYPE=SMALL,HEALTHCARE_INTEGRATION=NO
    5. Create Kubernetes secrets required for domain creation.
      
      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
      
      Create a Kubernetes secret for the RCU in the same Kubernetes namespace as the domain:
      
      Schema user : SOA1
      
      Schema password : REPLACE-WITH-SCHEMA-PASSWORD
      
      DB sys user password : REPLACE-WITH-SYS-PASSWORD
      
      Domain name : soainfra
      
      Domain Namespace : soans
      
      Secret name : soainfra-rcu-credentials
      
      cd ${WORKDIR}/create-rcu-credentials ./create-rcu-credentials.sh \ -u SOA1 \ -p REPLACE-WITH-SCHEMA-PASSWORD \ -a sys \ -q REPLACE-WITH-SYS-PASSWORD \ -d soainfra \ -n soans \ -s soainfra-rcu-credentials
      
      Now the environment is ready to start the Oracle SOA Suite domain creation.
Create an Oracle SOA Suite domain.
1. 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: soaosb
  - initialManagedServerReplicas: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\:release-version:image\: container-registry.oracle.com/middleware/soasuite\:14.1.2.0-<17 or 21>-<ol8 or ol9>-<tag>:g" create-domain-inputs.yaml
```
2. 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
```
3. 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
```
4. Verify that the Kubernetes domain object named soainfra is created:
```
kubectl get domain -n soans
NAME       AGE
soainfra   3m18s
```
5. 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
```
6. 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 access Oracle SOA Suite domain services.

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

Verify that you can access the Oracle SOA Suite domain URL.

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/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