SOA 21.3.2 release and wcsites latest documentation (#70)

Author: sbattagi

OracleSOASuite/kubernetes/README.md

@@ -7,7 +7,7 @@ The WebLogic Kubernetes operator (the “operator”) supports deployment of Ora
 * `soaosb`: Deploys a domain with SOA, Oracle Enterprise Scheduler (ESS), and Oracle Service Bus
 
 ***
-The current supported production release is [21.2.2](https://github.com/oracle/fmw-kubernetes/releases).
+The current supported production release is [21.3.2](https://github.com/oracle/fmw-kubernetes/releases).
 ***
 
 In this release, Oracle SOA Suite domains are supported using the “domain on a persistent volume”

docs-source/content/soa-domains/_index.md

@@ -1,11 +1,11 @@
 ---
 title: "Oracle SOA Suite"
 date: 2019-02-23T16:43:45-05:00
-description: "The Oracle WebLogic Kubernetes operator (the “operator”) supports deployment of Oracle SOA Suite components such as Oracle Service-Oriented Architecture (SOA), Oracle Service Bus, and Oracle Enterprise Scheduler (ESS). Follow the instructions in this guide to set up these Oracle SOA Suite domains on Kubernetes."
+description: "The Oracle WebLogic Kubernetes Operator (the “operator”) supports deployment of Oracle SOA Suite components such as Oracle Service-Oriented Architecture (SOA), Oracle Service Bus, and Oracle Enterprise Scheduler (ESS). Follow the instructions in this guide to set up these Oracle SOA Suite domains on Kubernetes."
 weight: 3
 ---
 
-The WebLogic Kubernetes operator (the “operator”) supports deployment of Oracle SOA Suite components such as Oracle Service-Oriented Architecture (SOA), Oracle Service Bus, and Oracle Enterprise Scheduler (ESS). Currently the operator supports these domain types:
+The WebLogic Kubernetes Operator (the “operator”) supports deployment of Oracle SOA Suite components such as Oracle Service-Oriented Architecture (SOA), Oracle Service Bus, and Oracle Enterprise Scheduler (ESS). Currently the operator supports these domain types:
 
 * `soa`       : Deploys a SOA domain with Oracle Enterprise Scheduler (ESS)
 * `osb`       : Deploys an Oracle Service Bus domain
@@ -25,7 +25,7 @@ The operator has several key features to assist you with deploying and managing
 
 #### Current production release
 
-The current production release for the Oracle SOA Suite domains deployment on Kubernetes is [21.2.2](https://github.com/oracle/fmw-kubernetes/releases). This release uses the WebLogic Kubernetes operator version [3.2.1](https://github.com/oracle/weblogic-kubernetes-operator/releases/tag/v3.2.1).
+The current production release for the Oracle SOA Suite domains deployment on Kubernetes is [21.3.2](https://github.com/oracle/fmw-kubernetes/releases). This release uses the WebLogic Kubernetes Operator version [3.2.1](https://github.com/oracle/weblogic-kubernetes-operator/releases/tag/v3.2.1).
 
 
 #### Recent changes and known issues
@@ -58,13 +58,14 @@ please consult this table of contents:
 
 To view documentation for an earlier release, see:
 
+* [Version 21.2.2](https://oracle.github.io/fmw-kubernetes/21.2.2/soa-domains/)
 * [Version 21.1.2](https://oracle.github.io/fmw-kubernetes/21.1.2/soa-domains/)
 * [Version 20.4.2](https://oracle.github.io/fmw-kubernetes/20.4.2/soa-domains/)
 * [Version 20.3.3](https://oracle.github.io/fmw-kubernetes/20.3.3/soa-domains/)
 
 #### Additional reading
 
-Oracle SOA Suite domains deployment on Kubernetes leverages the WebLogic Kubernetes operator framework.
+Oracle SOA Suite domains deployment on Kubernetes leverages the WebLogic Kubernetes Operator framework.
 * To develop an understanding of the operator, including design, architecture, domain life cycle management, and configuration overrides, review the [operator documentation](https://oracle.github.io/weblogic-kubernetes-operator).
 * To learn more about the Oracle SOA Suite architecture and components, see [Understanding Oracle SOA Suite](https://docs.oracle.com/en/middleware/soa-suite/soa/12.2.1.4/develop/introduction-building-applications.html#GUID-AED865D0-2FFF-4243-B8C5-473F8572D6F0).
 * To review the known issues and common questions for Oracle SOA Suite domains deployment on Kubernetes, see the  [frequently asked questions]({{< relref "/soa-domains/faq.md" >}}).

docs-source/content/soa-domains/adminguide/configure-load-balancer/_index.md

@@ -7,6 +7,6 @@ pre: "<b> </b>"
 description: "Configure different load balancers for Oracle SOA Suite domains."
 ---
 
-The WebLogic Kubernetes operator supports ingress-based load balancers such as Traefik, NGINX (kubernetes/ingress-nginx), and Voyager. It also supports Apache web tier load balancer.
+The WebLogic Kubernetes Operator supports ingress-based load balancers such as Traefik, NGINX (kubernetes/ingress-nginx), and Voyager. It also supports Apache web tier load balancer.
 
 {{% children style="h4" description="true" %}}

docs-source/content/soa-domains/adminguide/configure-load-balancer/apache.md

@@ -20,7 +20,7 @@ Follow these steps to set up the Apache web tier as a load balancer for an Oracl
 
 #### Build the Apache web tier image
 
-Refer to the [sample](https://github.com/oracle/docker-images/tree/master/OracleWebLogic/samples/12213-webtier-apache), to build the Apache web tier Docker image.
+Refer to the [sample](https://github.com/oracle/docker-images/tree/main/OracleWebLogic/samples/12213-webtier-apache), to build the Apache web tier Docker image.
 
 #### Create the Apache plugin configuration file
 

docs-source/content/soa-domains/adminguide/configure-load-balancer/nginx.md

@@ -184,7 +184,7 @@ Follow these steps to set up NGINX as a load balancer for an Oracle SOA Suite do
 1. Create an ingress for the domain in the domain namespace by using the sample Helm chart. Here path-based routing is used for ingress. Sample values for default configuration are shown in the file `${WORKDIR}/charts/ingress-per-domain/values.yaml`. By default, `type` is `TRAEFIK` , `sslType` is `NONSSL`, and `domainType` is `soa`. These values can be overridden by passing values through the command line or can be edited in the sample file `values.yaml`.   
 If needed, you can update the ingress YAML file to define more path rules (in section `spec.rules.host.http.paths`) based on the domain application URLs that need to be accessed. Update the template YAML file for the NGINX load balancer located at `${WORKDIR}/charts/ingress-per-domain/templates/nginx-ingress.yaml`.
 
-    > Note: See [here](https://github.com/oracle/fmw-kubernetes/blob/v21.2.2/OracleSOASuite/kubernetes/ingress-per-domain/README.md#configuration) for all the configuration parameters.
+    > Note: See [here](https://github.com/oracle/fmw-kubernetes/blob/v21.3.2/OracleSOASuite/kubernetes/ingress-per-domain/README.md#configuration) for all the configuration parameters.
 
    ```bash
     $ cd ${WORKDIR}

docs-source/content/soa-domains/adminguide/configure-load-balancer/traefik.md

@@ -157,7 +157,7 @@ Sample values for default configuration are shown in the file `${WORKDIR}/charts
 By default, `type` is `TRAEFIK`, `sslType` is `NONSSL`, and `domainType` is `soa`. These values can be overridden by passing values through the command line or can be edited in the sample file `values.yaml` based on the type of configuration (NONSSL, SSL, and E2ESSL).  
 If needed, you can update the ingress YAML file to define more path rules (in section `spec.rules.host.http.paths`) based on the domain application URLs that need to be accessed. The template YAML file for the Traefik (ingress-based) load balancer is located at `${WORKDIR}/charts/ingress-per-domain/templates/traefik-ingress.yaml`.
 
-> Note: See [here](https://github.com/oracle/fmw-kubernetes/blob/v21.2.2/OracleSOASuite/kubernetes/ingress-per-domain/README.md#configuration) for all the configuration parameters.
+> Note: See [here](https://github.com/oracle/fmw-kubernetes/blob/v21.3.2/OracleSOASuite/kubernetes/ingress-per-domain/README.md#configuration) for all the configuration parameters.
 
 1. Install `ingress-per-domain` using Helm for `NONSSL` configuration:
 

docs-source/content/soa-domains/adminguide/configure-load-balancer/voyager.md

@@ -96,7 +96,7 @@ Follow these steps to set up Voyager as a load balancer for an Oracle SOA Suite
 
 1. Create an ingress for the domain in the domain namespace by using the sample Helm chart. Here path-based routing is used for ingress. Sample values for default configuration are shown in the file `${WORKDIR}/charts/ingress-per-domain/values.yaml`. By default, `type` is `TRAEFIK` , `sslType` is `NONSSL`, and `domainType` is `soa`. These values can be overridden by passing values through the command line or can be edited on the sample file `values.yaml`.
 
-    > Note: See [here](https://github.com/oracle/fmw-kubernetes/blob/v21.2.2/OracleSOASuite/kubernetes/ingress-per-domain/README.md#configuration) for all the configuration parameters.
+    > Note: See [here](https://github.com/oracle/fmw-kubernetes/blob/v21.3.2/OracleSOASuite/kubernetes/ingress-per-domain/README.md#configuration) for all the configuration parameters.
 
    If needed, you can update the ingress yaml file to define more path rules (in the `spec.rules.host.http.paths` section) based on the domain application URLs that need to be accessed. You need to update the template yaml file for the Voyager (ingress-based) load balancer located at `${WORKDIR}/charts/ingress-per-domain/templates/voyager-ingress.yaml`
 

docs-source/content/soa-domains/adminguide/deploying-composites/deploy-using-maven-ant.md

@@ -7,7 +7,7 @@ pre : "<b>b. </b>"
 description: "Deploy Oracle SOA Suite and Oracle Service Bus composite applications using the Maven and Ant based approach in an Oracle SOA Suite deployment."
 ---
 
-Learn how to deploy Oracle SOA Suite and Oracle Service Bus composite applications using the Maven and Ant based approach in an Oracle SOA Suite in WebLogic Kubernetes operator environment.
+Learn how to deploy Oracle SOA Suite and Oracle Service Bus composite applications using the Maven and Ant based approach in an Oracle SOA Suite in WebLogic Kubernetes Operator environment.
 
 Before deploying composite applications, we need to create a Kubernetes pod in the same cluster where the Oracle SOA Suite domain is running, so that composite applications can be deployed using the internal Kubernetes Service for the Administration Server URL.
 

docs-source/content/soa-domains/adminguide/deploying-composites/supportJDEV.md

@@ -4,18 +4,18 @@ date: 2019-02-22T15:44:42-05:00
 draft: false
 weight: 1
 pre : "<b>a. </b>"
-description: "Deploy Oracle SOA Suite and Oracle Service Bus composite applications from Oracle JDeveloper to Oracle SOA Suite in the WebLogic Kubernetes operator environment."
+description: "Deploy Oracle SOA Suite and Oracle Service Bus composite applications from Oracle JDeveloper to Oracle SOA Suite in the WebLogic Kubernetes Operator environment."
 ---
 
-Learn how to deploy Oracle SOA Suite and Oracle Service Bus composite applications from Oracle JDeveloper (running outside the Kubernetes network) to an Oracle SOA Suite instance in the WebLogic Kubernetes operator environment.
+Learn how to deploy Oracle SOA Suite and Oracle Service Bus composite applications from Oracle JDeveloper (running outside the Kubernetes network) to an Oracle SOA Suite instance in the WebLogic Kubernetes Operator environment.
 
 {{% notice note %}}
 Use JDeveloper for development and test environments only. For a production environment, you should deploy using Application Control and WLST methods.
 {{% /notice %}}
 
 ### Deploy Oracle SOA Suite and Oracle Service Bus composite applications to Oracle SOA Suite from JDeveloper
 
-To deploy Oracle SOA Suite and Oracle Service Bus composite applications from Oracle JDeveloper, the Administration Server must be configured to expose a T3 channel. The WebLogic Kubernetes operator provides an option to expose a T3 channel for the Administration Server using the `exposeAdminT3Channel` setting during domain creation, then the matching T3 service can be used to connect. By default, when `exposeAdminT3Channel` is set, the WebLogic Kubernetes operator environment exposes the  `NodePort` for the T3 channel of the `NetworkAccessPoint` at `30012` (use `t3ChannelPort` to configure the port to a different value).
+To deploy Oracle SOA Suite and Oracle Service Bus composite applications from Oracle JDeveloper, the Administration Server must be configured to expose a T3 channel. The WebLogic Kubernetes Operator provides an option to expose a T3 channel for the Administration Server using the `exposeAdminT3Channel` setting during domain creation, then the matching T3 service can be used to connect. By default, when `exposeAdminT3Channel` is set, the WebLogic Kubernetes Operator environment exposes the  `NodePort` for the T3 channel of the `NetworkAccessPoint` at `30012` (use `t3ChannelPort` to configure the port to a different value).
 
 If you miss enabling `exposeAdminT3Channel` during domain creation, follow [Expose a T3/T3S Channel for the Administration Server]({{< relref "/soa-domains/adminguide/enablingt3#expose-t3t3s-for-administration-server" >}})  to expose a T3 channel manually.
 
@@ -32,15 +32,15 @@ If you miss enabling `exposeAdminT3Channel` during domain creation, follow [Expo
    $ kubectl get service soainfra-adminserver-external -n  soana-o jsonpath='{.spec.ports[0].nodePort}'
    ```
 
-1. Oracle SOA Suite in the WebLogic Kubernetes operator environment is deployed in a *Reference Configuration domain*. If a SOA project is developed in Classic mode JDeveloper displays a Mismatch notification in the Deploy Composite Wizard.  By default, JDeveloper is in Classic mode. To develop SOA projects in Reference Configuration mode, you must manually enable this feature in JDeveloper:
+1. Oracle SOA Suite in the WebLogic Kubernetes Operator environment is deployed in a *Reference Configuration domain*. If a SOA project is developed in Classic mode JDeveloper displays a Mismatch notification in the Deploy Composite Wizard.  By default, JDeveloper is in Classic mode. To develop SOA projects in Reference Configuration mode, you must manually enable this feature in JDeveloper:
    a. From the File menu, select **Tools**, then **Preferences**.
    b. Select **Reference Configuration Settings**.
    c. Select **Enable Reference Configuration settings in adapters**.
 
     ![Enable Reference Configuration](/fmw-kubernetes/images/soa-domains/JDEV_Reference_Config_Settings.png)
 
 
-1. JDeveloper needs to access the Servers during deployment. In the WebLogic Kubernetes operator environment, Administration and Managed Servers are pods and cannot be accessed directly by JDeveloper. As a workaround, you must configure the reachability of the Managed Servers:
+1. JDeveloper needs to access the Servers during deployment. In the WebLogic Kubernetes Operator environment, Administration and Managed Servers are pods and cannot be accessed directly by JDeveloper. As a workaround, you must configure the reachability of the Managed Servers:
 
    {{% notice note %}} The Managed Server T3 port is not exposed by default and opening this will have a security risk as the authentication method here is based on a userid/password. It is not recommended to do this on production instances.
    {{% /notice %}}

docs-source/content/soa-domains/adminguide/enablingT3.md

@@ -13,7 +13,7 @@ Oracle strongly recommends that you do not expose non-HTTPS traffic (T3/T3s/LDAP
 
 You can create T3/T3S channels and the corresponding Kubernetes service to expose the T3/T3S protocol for the Administration Server and Managed Servers in an Oracle SOA Suite domain.
 
-The WebLogic Kubernetes operator provides an option to expose a T3 channel for the Administration Server using the `exposeAdminT3Channel` setting during domain creation, then the matching T3 service can be used to connect. By default, when `exposeAdminT3Channel` is set, the WebLogic Kubernetes operator environment exposes the  `NodePort` for the T3 channel of the `NetworkAccessPoint` at `30012` (use `t3ChannelPort` to configure the port to a different value).
+The WebLogic Kubernetes Operator provides an option to expose a T3 channel for the Administration Server using the `exposeAdminT3Channel` setting during domain creation, then the matching T3 service can be used to connect. By default, when `exposeAdminT3Channel` is set, the WebLogic Kubernetes Operator environment exposes the  `NodePort` for the T3 channel of the `NetworkAccessPoint` at `30012` (use `t3ChannelPort` to configure the port to a different value).
 
 If you miss enabling `exposeAdminT3Channel` during domain creation, follow these steps to create a T3 channel for Administration Server manually.