fix xrefs to WDT and WIT (#2358)

* fix xrefs to WDT and WIT

* change links to point to releases pages

Author: rosemarymarano

documentation/3.2/content/_index.md

@@ -11,7 +11,7 @@ You can:
 * Supply WebLogic domain configuration using:
   * _Domain in PV_: Locates WebLogic domain homes in a Kubernetes PersistentVolume (PV). This PV can reside in an NFS file system or other Kubernetes volume types.
   * _Domain in Image_: Includes a WebLogic domain home in a container image.
-  * _Model in Image_: Includes [WebLogic Server Deploy Tooling](https://github.com/oracle/weblogic-deploy-tooling) models and archives in a container image.
+  * _Model in Image_: Includes [WebLogic Server Deploy Tooling](https://oracle.github.io/weblogic-deploy-tooling/) models and archives in a container image.
 * Configure deployment of WebLogic domains as a Kubernetes resource (using a Kubernetes custom resource definition).
 * Override certain aspects of the WebLogic domain configuration; for example, use a different database password for different deployments.
 * Start and stop servers and clusters in the domain based on declarative startup parameters and desired states.

documentation/3.2/content/faq/newbie.md

@@ -36,7 +36,7 @@ When using the operator, each deployed domain is specified by a domain resource
 
 Multiple deployments of the same domain are supported by specifying a unique `domain-uid` string for each deployed domain and specifying a different domain resource. The `domain-uid` is in turn used by the operator as the name-prefix and/or label for the domain's Kubernetes resources that the operator deploys for you. The WebLogic configuration of a domain's deployments optionally can by customized by specifying configuration overrides in the domain resource -- which, for example, is useful for overriding the configuration of a data source URL, user name, or password.
 
-The operator does not specify how a WebLogic domain home configuration is created. You can use WLST, REST, or a very convenient new tool called [WebLogic Server Deploy Tooling](https://github.com/oracle/weblogic-deploy-tooling) (WDT). WDT allows you to compactly specify WebLogic configuration and deployments (including JMS, data sources, applications, authenticators, and such) using a YAML file and a ZIP file (which include the binaries). The operator [samples]({{< relref "/samples/simple/_index.md" >}}) show how to create domains using WLST and using WDT.
+The operator does not specify how a WebLogic domain home configuration is created. You can use WLST, REST, or a very convenient new tool called [WebLogic Server Deploy Tooling](https://oracle.github.io/weblogic-deploy-tooling/) (WDT). WDT allows you to compactly specify WebLogic configuration and deployments (including JMS, data sources, applications, authenticators, and such) using a YAML file and a ZIP file (which include the binaries). The operator [samples]({{< relref "/samples/simple/_index.md" >}}) show how to create domains using WLST and using WDT.
 
 
 **Q:** Is the Administration Server required? Node Manager?

documentation/3.2/content/samples/simple/azure-kubernetes-service/model-in-image.md

@@ -202,7 +202,7 @@ The sample includes a predefined archive directory in `/tmp/mii-sample/archives/
 The archive top directory, named `wlsdeploy`, contains a directory named `applications`, which includes an ‘exploded’ sample JSP web application in the directory, `myapp-v1`. Three useful aspects to remember about WDT archives are:
   - A model image can contain multiple WDT archives.
   - WDT archives can contain multiple applications, libraries, and other components.
-  - WDT archives have a [well defined directory structure](https://github.com/oracle/weblogic-deploy-tooling/blob/master/site/archive.md), which always has `wlsdeploy` as the top directory.
+  - WDT archives have a [well defined directory structure](https://oracle.github.io/weblogic-deploy-tooling/concepts/archive/), which always has `wlsdeploy` as the top directory.
 
 The application displays important details about the WebLogic Server instance that it’s running on: namely its domain name, cluster name, and server name, as well as the names of any data sources that are targeted to the server.
 

documentation/3.2/content/samples/simple/domains/model-in-image/_index.md

@@ -30,7 +30,7 @@ description: "Sample for supplying a WebLogic Deploy Tooling (WDT) model that th
 
 This sample demonstrates deploying a Model in Image [domain home source type]({{< relref "/userguide/managing-domains/choosing-a-model/_index.md" >}}). Unlike Domain in PV and Domain in Image, Model in Image eliminates the need to pre-create your WebLogic domain home prior to deploying your Domain YAML file. Instead, Model in Image uses a WebLogic Deploy Tooling (WDT) model to specify your WebLogic configuration.
 
-WDT models are a convenient and simple alternative to WebLogic Scripting Tool (WLST) configuration scripts and templates. They compactly define a WebLogic domain using YAML files and support including application archives in a ZIP file. The WDT model format is described in the open source, [WebLogic Deploy Tooling](https://github.com/oracle/weblogic-deploy-tooling) GitHub project, and the required directory structure for a WDT archive is specifically discussed [here](https://github.com/oracle/weblogic-deploy-tooling/blob/master/site/archive.md).
+WDT models are a convenient and simple alternative to WebLogic Scripting Tool (WLST) configuration scripts and templates. They compactly define a WebLogic domain using YAML files and support including application archives in a ZIP file. The WDT model format is described in the open source, [WebLogic Deploy Tooling](https://oracle.github.io/weblogic-deploy-tooling/) GitHub project, and the required directory structure for a WDT archive is specifically discussed [here](https://oracle.github.io/weblogic-deploy-tooling/concepts/archive/).
 
 For more information on Model in Image, see the [Model in Image user guide]({{< relref "/userguide/managing-domains/model-in-image/_index.md" >}}). For a comparison of Model in Image to other domain home source types, see [Choose a domain home source type]({{< relref "/userguide/managing-domains/choosing-a-model/_index.md" >}}).
 
@@ -146,5 +146,5 @@ For more information, see the [Cannot pull image FAQ]({{<relref "/faq/cannot-pul
 
 For references to the relevant user documentation, see:
  - [Model in Image]({{< relref "/userguide/managing-domains/model-in-image/_index.md" >}}) user documentation
- - [Oracle WebLogic Server Deploy Tooling](https://github.com/oracle/weblogic-deploy-tooling)
- - [Oracle WebLogic Image Tool](https://github.com/oracle/weblogic-image-tool)
+ - [Oracle WebLogic Server Deploy Tooling](https://oracle.github.io/weblogic-deploy-tooling/)
+ - [Oracle WebLogic Image Tool](https://oracle.github.io/weblogic-image-tool/)

documentation/3.2/content/samples/simple/domains/model-in-image/initial.md

@@ -55,7 +55,7 @@ The sample includes a predefined archive directory in `/tmp/mii-sample/archives/
 The archive top directory, named `wlsdeploy`, contains a directory named `applications`, which includes an 'exploded' sample JSP web application in the directory, `myapp-v1`. Three useful aspects to remember about WDT archives are:
   - A model image can contain multiple WDT archives.
   - WDT archives can contain multiple applications, libraries, and other components.
-  - WDT archives have a [well defined directory structure](https://github.com/oracle/weblogic-deploy-tooling/blob/master/site/archive.md), which always has `wlsdeploy` as the top directory.
+  - WDT archives have a [well defined directory structure](https://oracle.github.io/weblogic-deploy-tooling/concepts/archive/), which always has `wlsdeploy` as the top directory.
 
 {{%expand "If you are interested in the web application source, click here to see the JSP code." %}}
 

documentation/3.2/content/samples/simple/domains/model-in-image/prerequisites.md

@@ -44,6 +44,7 @@ weight: 1
    {{< rawhtml >}}
    <a name="resume"></a>
    {{< /rawhtml >}}
+
 1. Make sure an operator is set up to manage namespace `sample-domain1-ns`. Also, make sure a Traefik ingress controller is managing the same namespace and listening on port 30305.
 
    For example, follow the same steps as the [Quick Start](https://oracle.github.io/weblogic-kubernetes-operator/quickstart/) guide up through the [Prepare for a domain]({{< relref "/quickstart/prepare.md" >}}) step.
@@ -141,7 +142,7 @@ weight: 1
    If you prefer, you can create your own base image and then substitute this image name in the WebLogic Image Tool `--fromImage` parameter throughout this sample. For example, you may wish to start with a base image that has patches applied. See [Preparing a Base Image]({{< relref "/userguide/base-images/_index.md" >}}).
      {{% /notice %}}
 
-1. Download the latest [WebLogic Deploy Tooling](https://github.com/oracle/weblogic-deploy-tooling) (WDT) and [WebLogic Image Tool](https://github.com/oracle/weblogic-image-tool) (WIT) installer ZIP files to your `/tmp/mii-sample/model-images` directory. Both WDT and WIT are required to create your Model in Image container images.
+1. Download the latest [WebLogic Deploy Tooling](https://github.com/oracle/weblogic-deploy-tooling/releases) (WDT) and [WebLogic Image Tool](https://github.com/oracle/weblogic-image-tool/releases) (WIT) installer ZIP files to your `/tmp/mii-sample/model-images` directory. Both WDT and WIT are required to create your Model in Image container images.
 
    ```shell
    $ cd /tmp/mii-sample/model-images
@@ -180,7 +181,7 @@ weight: 1
    has a version of WDT in its `--type wdt --version latest` location, then the
    `cache addInstaller` command would fail.
    For more information about the WIT cache, see the
-   [WIT Cache documentation](https://github.com/oracle/weblogic-image-tool/blob/master/site/cache.md).
+   [WIT Cache documentation](https://oracle.github.io/weblogic-image-tool/userguide/tools/cache/).
 
    These steps will install WIT to the `/tmp/mii-sample/model-images/imagetool` directory,
    plus put a `wdt_latest` entry in the tool's cache which points to the WDT ZIP file installer.

documentation/3.2/content/samples/simple/tanzu-kubernetes-service/_index.md

@@ -215,7 +215,7 @@ The sample includes a predefined archive directory in `/tmp/mii-sample/archives/
 The archive top directory, named `wlsdeploy`, contains a directory named `applications`, which includes an ‘exploded’ sample JSP web application in the directory, `myapp-v1`. Three useful aspects to remember about WDT archives are:
   - A model image can contain multiple WDT archives.
   - WDT archives can contain multiple applications, libraries, and other components.
-  - WDT archives have a [well defined directory structure](https://github.com/oracle/weblogic-deploy-tooling/blob/master/site/archive.md), which always has `wlsdeploy` as the top directory.
+  - WDT archives have a [well defined directory structure](https://oracle.github.io/weblogic-deploy-tooling/concepts/archive/), which always has `wlsdeploy` as the top directory.
 
 The application displays important details about the WebLogic Server instance that it’s running on: namely its domain name, cluster name, and server name, as well as the names of any data sources that are targeted to the server.
 

documentation/3.2/content/userguide/base-images/_index.md

@@ -92,14 +92,14 @@ Additional information about using this image is available in the Oracle Contain
 
 The Oracle WebLogic Server Kubernetes Operator and WebLogic Server 12.2.1.3.0 image requires patch 29135930.
 This patch has some prerequisite patches that will also need to be applied. The WebLogic Server 12.2.1.4.0 image does not require any patches. To create and customize the WebLogic Server image,
-and apply the required patches, use the [WebLogic Image Tool](https://github.com/oracle/weblogic-image-tool).
+and apply the required patches, use the [WebLogic Image Tool](https://oracle.github.io/weblogic-image-tool/).
 
-To use the Image Tool, follow the [Setup](https://github.com/oracle/weblogic-image-tool/blob/master/README.md#setup) instructions
-and [Quick Start](https://github.com/oracle/weblogic-image-tool/blob/master/site/quickstart.md) Guide.
+To use the Image Tool, follow the [Setup](https://oracle.github.io/weblogic-image-tool/quickstart/setup/) instructions
+and [Quick Start](https://oracle.github.io/weblogic-image-tool/quickstart/quickstart/) Guide.
 
 To build the WebLogic Server image and apply the patches:
 
-1. Add the Server JRE and the WebLogic Server installer to the [`cache` command](https://github.com/oracle/weblogic-image-tool/blob/master/site/cache.md).
+1. Add the Server JRE and the WebLogic Server installer to the [`cache` command](https://oracle.github.io/weblogic-image-tool/userguide/tools/cache/).
 
     ```shell
     $ imagetool cache addInstaller \
@@ -113,7 +113,7 @@ To build the WebLogic Server image and apply the patches:
     --version=12.2.1.4.0 \
     --path=/home/acmeuser/wls-installers/fmw_12.2.1.4.0_wls_Disk1_1of1.zip
     ```
-2. Use the [Create Tool](https://github.com/oracle/weblogic-image-tool/blob/master/site/create-image.md)
+2. Use the [Create Tool](https://oracle.github.io/weblogic-image-tool/userguide/tools/create-image/)
 to build the image and apply the patches.
 
     For the Create Tool to download the patches, you must supply your My Oracle Support credentials.
@@ -140,7 +140,7 @@ You can also create an image with the WebLogic domain inside the image.
 are provided that demonstrate how to create the image using either:
 
 * WLST to define the domain, or
-* [WebLogic Deploy Tooling](https://github.com/oracle/weblogic-deploy-tooling) to define the domain.
+* [WebLogic Deploy Tooling](https://oracle.github.io/weblogic-deploy-tooling/) to define the domain.
 
 In these samples, you will see a reference to a "base" or `FROM` image.  You should use an image
 with the mandatory patches installed as this base image.  This image could be either
@@ -157,14 +157,14 @@ including keys and credentials that are used to access external resources
 
 #### Patch WebLogic Server images
 
-Use the [WebLogic Image Tool](https://github.com/oracle/weblogic-image-tool) (WIT) to patch
+Use the [WebLogic Image Tool](https://oracle.github.io/weblogic-image-tool/) (WIT) to patch
 WebLogic Server images with quarterly Patch Set Updates (PSUs), which include security fixes, or with one-off patches.
 
-Use either the WIT [`create`](https://github.com/oracle/weblogic-image-tool/blob/master/site/create-image.md) or
-[`update`](https://github.com/oracle/weblogic-image-tool/blob/master/site/update-image.md) command, however,
+Use either the WIT [`create`](https://oracle.github.io/weblogic-image-tool/userguide/tools/create-image/) or
+[`update`](https://oracle.github.io/weblogic-image-tool/userguide/tools/update-image/) command, however,
 patching using the `create` command results in a smaller WebLogic Server image size. Note that you will need to
 download the WebLogic Server 12.2.1.4.0 installer and JDK installer prior to running the `create` command. For details, see
-the WIT [Quick Start](https://github.com/oracle/weblogic-image-tool/blob/master/site/quickstart.md) guide.
+the WIT [Quick Start](https://oracle.github.io/weblogic-image-tool/quickstart/quickstart/) guide.
 
 Example: Create an image named `sample:wls` with the WebLogic Server 12.2.1.4.0 slim installer, JDK 8u291, a slim version of the Oracle Linux 7 container image,
 and latest PSU and recommended CPU and SPU patches applied.
@@ -181,12 +181,12 @@ to update the running domain differs depending on the [domain home source type](
 difference between the domain home source types is the location of the domain home:
 
 * Domain in PV: The container image contains the JDK and WebLogic Server binaries. The domain home is located in a Persistent Volume (PV).
-* Model in Image: The container image contains the JDK, WebLogic Server binaries, and a [WebLogic Deployment Tooling](https://github.com/oracle/weblogic-deploy-tooling) (WDT) installation, WDT model file, and application archive file.
+* Model in Image: The container image contains the JDK, WebLogic Server binaries, and a [WebLogic Deployment Tooling](https://oracle.github.io/weblogic-deploy-tooling/) (WDT) installation, WDT model file, and application archive file.
 * Domain in Image: The container image contains the JDK, WebLogic Server binaries, and domain home.   
 
 For Domain in PV, the operator can apply the update to the running domain without modifying the patched container image. For Model in Image (MII) and Domain in Image,
 before the operator can apply the update, the patched container images must be modified to add the domain home or a
-WDT model and archive. You use WebLogic Image Tool (WIT) [Rebase Image](https://github.com/oracle/weblogic-image-tool/blob/master/site/rebase-image.md)
+WDT model and archive. You use WebLogic Image Tool (WIT) [Rebase Image](https://oracle.github.io/weblogic-image-tool/userguide/tools/rebase-image/)
 to update the Oracle Home of the original image using the patched Oracle Home from a patched container image.
 
 In all three domain home source types, you edit the [Domain Resource]({{< relref "/userguide/managing-domains/domain-resource#domain-resource-attribute-references" >}})
@@ -202,7 +202,7 @@ of the WebLogic domain to update the Oracle Home of the servers.
 For information on server restarts, see [Restarting]({{< relref "/userguide/managing-domains/domain-lifecycle/restarting.md" >}}).
 
 ##### Model in Image
-Use the WIT [`rebase`](https://github.com/oracle/weblogic-image-tool/blob/master/site/rebase-image.md) command
+Use the WIT [`rebase`](https://oracle.github.io/weblogic-image-tool/userguide/tools/rebase-image/) command
 to update the Oracle Home for an existing image with the model and archive files in the image using the patched Oracle Home from a
 patched container image. Then, the operator performs a [rolling update]({{< relref "/userguide/managing-domains/domain-lifecycle/restarting#overview" >}})
 of the domain, updating the Oracle Home of each server pod.
@@ -221,7 +221,7 @@ $ imagetool rebase --tag mydomain:v2 --sourceImage mydomain:v1 --targetImage ora
 Then, edit the Domain Resource image reference with the new image name/tag (`mydomain:2`).
 
 ##### Domain in Image
-Use the WIT [`rebase`](https://github.com/oracle/weblogic-image-tool/blob/master/site/rebase-image.md) command to update the Oracle Home
+Use the WIT [`rebase`](https://oracle.github.io/weblogic-image-tool/userguide/tools/rebase-image/) command to update the Oracle Home
 for an existing domain image using the patched Oracle Home from a patched container image. Then, the operator performs a
 [rolling update]({{< relref "/userguide/managing-domains/domain-lifecycle/restarting#overview" >}}) of the domain,
 updating the Oracle Home of each server pod.

documentation/3.2/content/userguide/cicd/tools.md

@@ -8,7 +8,7 @@ description: "Tools that are available to build CI/CD pipelines."
 
 #### WebLogic Deploy Tooling (WDT)
 
-You can use several of the [WDT tools](https://github.com/oracle/weblogic-deploy-tooling)
+You can use several of the [WDT tools](https://oracle.github.io/weblogic-deploy-tooling/)
 in a CI/CD pipeline. For example, the
 `createDomain` tool creates a new domain based on a simple model, and
 `updateDomain` (and `deployApps`) uses the same model concept to update
@@ -30,7 +30,7 @@ that you supply a domain home.
 Other than the tools themselves, there are three components to the WDT tools:  
 
 - *The Domain Model* - Metadata model describing the desired domain.  
-  The metadata domain model can be written in YAML or JSON and is documented [here](https://github.com/oracle/weblogic-deploy-tooling/blob/master/site/model.md).
+  The metadata domain model can be written in YAML or JSON and is documented [here](https://oracle.github.io/weblogic-deploy-tooling/concepts/model/).
 - *The Archive ZIP* - Binaries to supplement the model.  
   All binaries needed to supplement the model must be specified in an archive
   file, which is just a ZIP file with a specific directory structure. Optionally,