20.4.2: Updated patch metadata for imagetool documentation

20.4.2: Updated patch metadata for imagetool doc

Author: sbattagi

OracleSOASuite/kubernetes/imagetool-scripts/README.md

@@ -0,0 +1,4 @@
+### Create or update an Oracle SOA Suite Docker image using the Oracle WebLogic Image Tool
+
+For the release 20.4.2, follow the instructions in this [document](https://oracle.github.io/fmw-kubernetes/soa-domains/create-or-update-image/#create-an-image) to create or update an Oracle SOA Suite Docker image using the Oracle WebLogic Image Tool.
+

OracleSOASuite/kubernetes/imagetool-scripts/buildArgs

@@ -4,6 +4,6 @@ create
 --version=12.2.1.4.0
 --tag=%BUILDTAG%
 --pull
---installerResponseFile %DOCKER_REPO%/OracleFMWInfrastructure/dockerfiles/12.2.1.4.0/install.file,%DOCKER_REPO%/OracleSOASuite/dockerfiles/12.2.1.4.0/install/soasuite.response,%DOCKER_REPO%/OracleSOASuite/dockerfiles/12.2.1.4.0/osb.response
+--installerResponseFile %DOCKER_REPO%/OracleFMWInfrastructure/dockerfiles/12.2.1.4/install.file,%DOCKER_REPO%/OracleSOASuite/dockerfiles/12.2.1.4/install/soasuite.response,%DOCKER_REPO%/OracleSOASuite/dockerfiles/12.2.1.4/install/osb.response
 --additionalBuildCommands %DOCKER_REPO%/OracleSOASuite/imagetool/12.2.1.4.0/additionalBuildCmds.txt
---additionalBuildFiles %DOCKER_REPO%/OracleSOASuite/dockerfiles/12.2.1.4.0/container-scripts
+--additionalBuildFiles %DOCKER_REPO%/OracleSOASuite/dockerfiles/12.2.1.4/container-scripts

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

@@ -60,7 +60,7 @@ please consult this table of contents:
 
 If you wish to view documentation for an older version, please see 
 
-* [Version 20.3.3]({{< relref "/20.3.3/soa-domains/" >}})
+* [Version 20.3.3](https://oracle.github.io/fmw-kubernetes/20.3.3/soa-domains/)
 
 #### Additional reading
 

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

@@ -11,7 +11,7 @@ Learn how to deploy Oracle SOA Suite and Oracle Service Bus composite applicatio
 
 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.
 
-Place the SOA/OSB composite project at a share location (for example at `/share/soa-deploy`) mounted at `/soacomposites` inside container.
+Place the SOA/OSB composite project at a share location (for example at `/share/soa-deploy`) mounted at `/composites` inside container.
 Make sure to provide `oracle` user *( uid: 1000 and gid: 1000)* permission to directory `/share/soa-deploy`, so that it is accessible and writable inside the container.
 
 ```
@@ -75,7 +75,7 @@ Before creating a Kubernetes pod, make sure that the Oracle SOA Suite Docker ima
 
    d) Apply the YAML:
       ```
-      $ kubectl apply apply -f soadeploy-pvc.yaml
+      $ kubectl apply -f soadeploy-pvc.yaml
       ```
 
 
@@ -98,7 +98,7 @@ Before creating a Kubernetes pod, make sure that the Oracle SOA Suite Docker ima
           - name: M2_HOME
             value: /u01/oracle/oracle_common/modules/org.apache.maven_3.2.5
           command: ["/bin/bash", "-c", "echo 'export PATH=$PATH:$M2_HOME/bin' >> $HOME/.bashrc; sleep infinity"]
-          imagePullPolicy: Always
+          imagePullPolicy: IfNotPresent
           volumeMounts:
           - name: mycomposite
             mountPath: /composites
@@ -127,20 +127,20 @@ Set up proxy details for Maven to pull dependencies from the internet.
    If your environment is not running behind a proxy, then skip this step. Otherwise, replace `REPLACE-WITH-PROXY-HOST`, `REPLACE-WITH-PROXY-PORT` and the value for `nonProxyHosts` attribute per your environment and create the `settings.xml`:
 
    ```
-      $ mkdir $HOME/.m2
-      $ cat <<EOF > $HOME/.m2/settings.xml
-      <settings>
-      <proxies>
-      <proxy>
-      <active>true</active>
-      <protocol>http</protocol>
-      <host>REPLACE-WITH-PROXY-HOST</host>
-      <port>REPLACE-WITH-PROXY-PORT</port>
-      <nonProxyHosts>soainfra-cluster-soa-cluster|soainfra-adminserver</nonProxyHosts>
-      </proxy>
-      </proxies>
-      </settings>
-      EOF
+   $ mkdir $HOME/.m2
+   $ cat <<EOF > $HOME/.m2/settings.xml
+   <settings>
+   <proxies>
+   <proxy>
+   <active>true</active>
+   <protocol>http</protocol>
+   <host>REPLACE-WITH-PROXY-HOST</host>
+   <port>REPLACE-WITH-PROXY-PORT</port>
+   <nonProxyHosts>soainfra-cluster-soa-cluster|soainfra-adminserver</nonProxyHosts>
+   </proxy>
+   </proxies>
+   </settings>
+   EOF
    ```
 
 #### For Oracle SOA Suite composite applications

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

@@ -15,7 +15,7 @@ You can create T3/T3S channels and the corresponding Kubernetes service to expos
 
 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 Managed Servers manually.
+If you miss enabling `exposeAdminT3Channel` during domain creation, follow these steps to create a T3 channel for Administration Server manually.
 
 ![Exposing SOA Managed Server T3 Ports](/fmw-kubernetes/images/soa-domains/ExposeSOAMST3.png)