add files for WMS ID#11004 and WMS ID#11650 (#68)

* Update to 1.3.2

* Update to Verrazzano 1.3.2

* lower case

* Lowercase complete

* QA Complete

* manifest.json updated

* Introduction link updated

* Revert "Introduction link updated"

This reverts commit 852a83a.

* Intro link

* Update Title

* Initial Project

* Update HOL Support

* Update jdk

* Update as per free tier

* Update Cluster creation

* Update Verrazzano to 1.4.1

* fixed indentation and image issue

* remove redundant instruction

* Update Verrazzano 1.4.2

* OOW feedback added

* VZ CLI Installation

* remove persistence volume

* alternate-version fixed

* Set initial version

* Feedback version 1

* upgrade to Helidon 4.0.0-Alpha5

* Modify the output

* Final

* Add comment

* Final code

* walkthrough video added

* new version helidon verrazzano

* Quaterly QA Verrazzano workshop

* lint checker suggestion

* Update to Verrazzano 1.5.2

* Tomcat-verrazzano version 2

* Link to object storage added

* Enhanced cluster

* Title changed

* Quarterly QA

* lint-checker suggestion

* Quarterly QA

* Grammer fix

* unnecessary files removed

* Update to WKTUI 1.5.2

* springboot lab added

* ready for publish

* Helidon DevOps workshop added

* Update help section

* Dev_Ops_Image changed

Dev_Ops_Image changed

* QA completed

* Quarterly QA

* Verrazzano version update

* WMS ID#11409

* Link updated

* Add support lab

* Update Verrazzano and OKE Version

* Added walkthrough video for cloud world HOL

* modify lab title

* add time in wktui

* add ocw folder for wktui

* Update introduction.md

* Update the Helidon and WKTUI workshop

* Update Sandbox manifest

* Fix workshop link WKTUI

* WeLogicForOKEWorkshop added

* workshop folder changed

* Cluster name changed

* wktui-hpa added

* Update manifest.json

* Update to 4.0.3

* Lab 4 updated

* Update build-run.md

* Helidon Virtual thread 4.0.5

* Update zip location

* update jdk arm

* OSMS configuration added

* change helidon version to 3.2.8

* DevOps update to JDK21

* autoscale initial

* New

* add files for ocw

* Fixed typo and grammer error

weblogic-toolkit-ui/access-application-ocw/access-application-ocw.md

@@ -0,0 +1,81 @@
+# Test the Application Deployment
+
+## Introduction
+
+### About WebLogic Remote Console
+
+The WebLogic Remote Console is a lightweight, open-source console that you can use to manage your WebLogic Server domain running anywhere, such as on a physical or virtual machine, in a container, Kubernetes, or in the Oracle Cloud. The WebLogic Remote Console does not need to be colocated with the WebLogic Server domain.
+
+You can install and run the WebLogic Remote Console anywhere, and connect to your domain using WebLogic REST APIs. You simply launch the desktop application and connect to the Administration Server of your domain. Or, you can start the console server, launch the console in a browser and then connect to the Administration Server.
+
+The WebLogic Remote Console is fully supported with WebLogic Server 12.2.1.3, 12.2.1.4, and 14.1.1.0.
+
+**Key Features of the WebLogic Remote Console**
+
+* Configure WebLogic Server instances and clusters
+* Create or modify WDT metadata models
+* Configure WebLogic Server services, such as database connectivity (JDBC), and messaging (JMS)
+* Deploy and un-deploy applications
+* Start and stop servers and applications
+* Monitor server and application performance
+
+In this lab, we access the application **opdemo** and verify the successful migration of an offline on-premise domain. we also verify the load-balancing between managed server pods. Later, we use WebLogic Remote Console, to verify the successful deployment of resources of the test-domain in the Kubernetes environment.
+
+Estimated Time: 10 minutes
+
+Watch the video below for a quick walk-through of the lab.
+[Testing Application Deployment](videohub:1_1khcsrbq)
+
+### Objectives
+
+In this lab, you will:
+
+* Access the Application through the Browser.
+* Explore the WebLogic Domain using WebLogic Remote Console.
+
+
+## Task 1: Access the Application through the Browser
+
+In this task, we access the **opdemo** application. We click on the refresh icon to make multiple requests to the application, to verify load-balancing between two managed server pods.
+
+1. click the link for **opdemo** and then add **?dsname=testDatasource** as shown below
+ ```bash
+    <copy>?dsname=testDatasource</copy>
+ ```
+ ![Open Application](images/open-application.png)
+ ![modify url](images/modify-url.png)
+
+
+2. If you click on the Refresh icon, You can see load balancing between two managed server pods.
+ ![Show Loadbalancing](images/show-load-balancing.png)
+
+
+## Task 2: Explore WebLogic Domain on Kubernetes Cluster using WebLogic Remote Console
+
+In this task, we explore the WebLogic Remote Console. We create a connection to **Admin Server** in the Remote Console and verify the resources in the WebLogic Domain. This verifies the successful migration of an on-premise domain into the Oracle Kubernetes Cluster. 
+
+1. To open WebLogic Remote Console, Click on **Activities**, type **WebLogic** in search box and click on the **WebLogic Remote Console** Icon.
+ ![open remote](images/open-remote.png)
+
+2. In the **Kiosk** and Select **KubeEnv** and click **icon** for settings as shown.
+ ![Admin Server Connection](images/adminserver-connection.png)
+
+3. Enter the **IP** you copied in last lab and click **OK**.<br>
+ ![Connection Details](images/connection-details.png)
+
+4. Click on **Edit Tree** icon, then Select **Services** -> **Data Sources**. You can observe the same Datasouce, which we had seen in the on-premise domain.
+ ![Verify Datasources](images/verify-datasources.png)
+
+5. To display what servers are running in your domain. Click on **Monitoring Tree** Icon as shown then select **Environment** -> **Servers**. You can see we have **Admin Server** and 2 Managed Server pods running. 
+ ![Running Servers](images/running-server-status.png)
+
+6. Click on **admin-server**, you can see WebLogic Version is **12.2.1.4.0**. 
+ ![Server Status](images/wls-version.png)
+
+
+
+## Acknowledgements
+
+* **Author** -  Ankit Pandey
+* **Contributors** - Sid Joshi , Maciej Gruszka, 
+* **Last Updated By/Date** - Ankit Pandey, July 2024

weblogic-toolkit-ui/create-image-ocw/create-image-ocw.md

@@ -0,0 +1,75 @@
+# Create an Auxiliary Image and Push it into the Oracle Container Image Registry
+
+## Introduction
+
+**Primary Image** - The image containing the Oracle Fusion Middleware software. It is used as the basis of all containers that run WebLogic Servers for the domain.
+
+**Auxiliary Image** - The image that supplies the WebLogic Deploy Tooling software and the model files. At runtime, the auxiliary image’s content is merged with the primary image’s content.
+ ![Image Structure](images/image-structure.png)
+
+In this Lab, we use the WebLogic server **12.2.1.4-slim-ol8** image as the Primary Image. Also, we create an auxiliary image and push it to the Oracle Container Image Registry repository using the pre-generated authentication token. 
+
+Estimated Time: 10 minutes
+
+Watch the video below for a quick walk-through of the lab.
+[Creation of Images for the OKE on OCI](videohub:1_y5o56oe5)
+
+### Objectives
+
+In this lab, you will:
+
+* Create an Auxiliary Image and push the image to Oracle Cloud Container Image Registry.
+
+## Task 1: Prepare the Auxiliary Image and Push the Auxiliary Image  
+
+In this task, we are creating an Auxiliary image, which we will push to the Oracle Cloud Container Registry.
+
+1. Click **Image**. For the Primary Image, we will use the below **weblogic Image**. So leave default values under the **Primary Image** section as shown 
+
+ ```bash
+    <copy>container-registry.oracle.com/middleware/weblogic:12.2.1.4-slim-ol8</copy>
+ ```
+ ![Primary Image](images/primary-image.png)
+    > **For your information only:**<br>
+    > The primary image is the one used for running the domain. One primary image can be reused for hundreds of domains. The primary image contains the OS, JDK, and FMW software installations.
+
+2. Click **Auxiliary Image** tab in Image section. To create the **Auxiliary Image Tag**, we need the following information:
+
+    * Endpoint for the Region
+    * Tenancy Namespace
+    * OCIR Registry Name
+
+    > We have prefilled the values for you. You need to replace **tag** with your username. For example, user1/user2. 
+ ![image tag](images/image-tag.png)
+
+
+5. We have prefilled the values for **Auxiliary Image Registry Push Username** and **Auxiliary Image Registry Push Password**.
+ ![Auxiliary Image Details](images/auxiliary-image-details.png)
+
+7. Click **Create Auxiliary Image**.
+ ![Create Auxiliary Image](images/create-auxiliary-image.png)
+
+8. As we already prepared the model in the previous lab, so click on **No**.
+ ![Prepare Model](images/prepare-model.png)
+
+9. Select **Downloads** folder where we want to save **WebLogic Deployer** and click **Select** as shown.
+ ![WDT Location](images/wdt-location.png)
+
+10. Once Auxiliary images is successfully created, On **Create Auxiliary Image Complete** window, click **Ok**.
+ ![Auxiliary Created](images/auxiliary-created.png)
+    > **For your information only:**<br>
+    > An auxiliary image is domain-specific. The auxiliary image contains the data that defines the domain.
+
+11. Click **Push Auxiliary Image** to push the image in the repository inside your Oracle Cloud Container Image Registry.
+ ![Push Auxiliary](images/push-auxiliary.png)
+
+12. Once image is successfully pushed, On **Push Image Complete** window, click **Ok**. 
+ ![Auxiliary Pushed](images/auxiliary-pushed.png)
+
+
+
+## Acknowledgements
+
+* **Author** -  Ankit Pandey
+* **Contributors** - Sid Joshi , Maciej Gruszka
+* **Last Updated By/Date** - Ankit Pandey, July 2024

weblogic-toolkit-ui/create-model-ocw/create-model-ocw.md

@@ -0,0 +1,146 @@
+# Modify a WKT UI Project and Create a Model file
+
+## Introduction
+
+In this lab, we explore the on-premise WebLogic domain. We navigate through the administration console to view the deployed application, data sources and servers in *test-domain*. we also open the pre-created *`ocw_project.wktproj`*, which already have pre-filled values for *Project Settings* section. Then we create the model file, by introspecting of an offline on-premise domain. At last, we validate the model and prepare the model to be deployed on Oracle Kubernetes Cluster (OKE).
+
+Estimated Time: 15 minutes
+
+Watch the video below for a quick walk-through of the lab.
+[Creation of Model for the OKE on OCI](videohub:1_qdch3qqg)
+
+### Objectives
+
+In this lab, you will:
+
+* Explore the on-premise WebLogic domain **test-domain**.
+* Open the base WKT project.
+* Introspection of an offline on-premise domain.
+* Validate and prepare the model. 
+
+### Prerequisites
+
+To run this lab, you must have:
+* Access to noVNC Remote Desktop.
+
+## Task 1: Explore on-premise domain
+
+In this task, we navigate through the resources in on-premise **test-domain** using the WebLogic Administration console.
+
+1. On the left side, click **Arrow Icon**. 
+ ![copy clipboard](images/copy-clipboard.png)
+ > **Important**- You can see the **Clipboard**, for copy and paste between the host machine and remote desktop, we use the **Clipboard**. For example, if you want to copy from the host machine and want to paste it inside the remote desktop, you need to first paste in the clipboard, then you can paste it into the remote desktop. Again click on **Arrow Icon** to hide the **Settings** option.
+
+2. Click **Activities** and then Click the icon for **terminal** as shown below.
+ ![open terminal](images/open-terminal.png)
+
+3. Copy and paste the below command in the terminal to start the **on-premise WebLogic Admin Server**.
+ ```bash
+    <copy>cd ~/Oracle/Middleware/Oracle_Home/user_projects/domains/test_domain/bin/
+    ./startWebLogic.sh</copy>
+ ```
+ ![start server](images/start-server.png)
+
+3. Click **Activities** and then type **Firefox** in search box. Click the icon for **Firefox**.
+ ![open firefox](images/open-firefox.png)
+
+4. Copy and paste the below URL in the browser to open Admin Console and enter **weblogic/Welcome1%** as `Username/Password`, then click **Login**. 
+ ```bash
+    <copy>http://localhost:7001/console</copy>
+ ```
+ ![Login Admin Console](images/login-admin-console.png)
+
+5. To view available servers, expand **Environment** and click **Servers**. You can see, that we have one dynamic cluster with 5 managed servers. 
+ ![View Servers](images/view-servers.png)
+
+6. To view the datasources, expand **Services** and click **Data Sources**.
+ ![View Datasources](images/view-datasources.png)
+
+7. To view the deployed application, click **Deployment**. You can see, that we have **opdemo** as a deployed application.
+ ![View Deployments](images/view-deployments.png)
+
+## Task 2: Opening the base WKT UI Project
+
+For simplicity of lab, we created **`ocw_project.wktproj`**, which preset the location of docker, Java, Oracle Home, and Primary Image Tag. In this task, we open the **`ocw_project.wktproj`** project.
+
+1. Click **Activities** and then type **WebLogic** in search box. Click the icon for **WebLogic Kubernetes Toolkit UI**.
+ ![Open WKTUI](images/open-wktui.png)
+
+2. To open **ocw_project.wktproj** project, click **File** -> **Open Project**. 
+ ![Open Project](images/open-project.png)
+
+3. Click **Home** in left side, then choose **ocw_project.wktproj** and click **Open Project**.
+ ![Project Location](images/project-location.png)
+
+4. Enter **welcome1** as **Password** and then click **Unlock**.
+ ![unlock](images/un-lock.png)
+
+5. Review **Project Settings** and read more about it in the notes below.
+
+    > **For your information only:**<br>
+    > As **Credential Story Policy**, we select **Store in Native OS Credentials Store**. It means the credentials (like for WebLogic Server and data sources) are only stored on the local machine.<br>
+    > For **Where would you like the target Oracle Fusion Middleware domain to live?**, we select **Created in the container from the model in the image**. In this case, the set of model-related files is added to the image. So when the WebLogic Kubernetes Operator domain object is deployed, its inspector process runs and creates the WebLogic Server domain inside a running container on the fly.<br>
+ ![Project Settings](images/project-settings.png)
+    > As **Kubernetes Environment Target Type**, we select **WebLogic Kubernetes Operator**. This means you want this domain to be deployed in Kubernetes managed by the WebLogic Kubernetes Operator. These settings also determine what sections and their associated actions within the application, to display.<br>
+    > we also specify the location for **JAVA HOME** and **ORACLE_HOME**. WebLogic Kubernetes Toolkit UI uses this directory when invoking the WebLogic Deployer Tooling and WebLogic Image Tool. <br>
+    > To build new images, inspect images and interact with image repositories, the WKT UI application uses an image build tool, which defaults to docker.<br>
+ ![Kubernetes Cluster Type](images/kubernetes-cluster-type.png)
+
+
+
+
+## Task 3: Introspection of an Offline on-premise domain 
+
+In this task, we perform introspection of an on-premise domain, which creates a model file consisting of the domain configuration.
+
+1. In WebLogic Kubernetes Toolkit UI, Click **Model** -> **Code View**.
+ ![Model](images/click-model.png)
+
+2. Click **File** -> **Add Model** -> **Discover Model(offline)**.
+ ![Discover Model](images/discover-model.png)
+
+3. Click Open folder **icon** to open the **Domain Home**.
+ ![Open Domain Hom](images/open-domain-home.png)
+
+4. In the Home folder, navigate to **`/home/opc/Oracle/Middleware/Oracle_Home/user_projects/domains/`** directory and select **test-domain** folder then  click **Select**. Click **OK**.
+ ![Navigate Location](images/navigate-location.png)
+ ![Specify Location](images/specify-location.png)
+    > If you look in the console, you will see that this invokes the WebLogic Deployer Tool to introspect the domain configuration in offline mode. 
+
+5. You can see the window as shown below, at the end, you will have a model ready for you.
+ ![View Model](images/view-model.png)
+
+    > The result of this WDT introspection are the model(a metadata representation of your domain configuration), placeholder, where you can specify the values (like a password for datasource) and application in the application archive.
+
+## Task 4: Validate and Prepare Model 
+
+In this task, we validate the model and prepare the model to be deployed on Oracle Kubernetes Cluster (OKE).
+
+1. To validate the model, click **Validate Model**.
+ ![Validate Model](images/validate-model.png)
+    > **For your information only:**<br>
+    > Validate model invokes the WDT [Validate Model Tool](https://oracle.github.io/weblogic-deploy-tooling/userguide/tools/validate/), which validates that the model and its related artefacts are well-formed and provides help on the valid attributes and subfolder for a particular model location.
+
+2. Once you see **Validate Model Complete** window, click **Ok**.
+ ![Validate Complete](images/validate-complete.png)
+
+3. To prepare the model, to be deployed on the Kubernetes cluster, click **Prepare Model**
+ ![Prepare Model](images/prepare-model.png)
+    > **For your information only:**<br>
+    > Prepare model invokes the WDT [Prepare Model Tool](https://oracle.github.io/weblogic-deploy-tooling/userguide/tools/prepare/) to modify the model to work in a Kubernetes cluster with WebLogic Kubernetes Operator or Verrazzano installed.<br>
+    > Prepare Model does the following:
+    * Removes model sections and fields that are not compatible with the target environment.
+    * Replaces endpoint values with model tokens that reference variables.
+    * Replaces credential values with model tokens that reference either a field in a Kubernetes secret or a variable.
+    * Provides default values for fields displayed in the application’s variable, variable overrides, and secret editors.
+    * Extracts topology information to the application that it uses to generate the resource file used to deploy the domain.
+
+4. Once you see **Prepare Model Complete** window,click **Ok**.
+ ![Prepare Complete](images/prepare-complete.png)
+
+
+## Acknowledgements
+
+* **Author** -  Ankit Pandey
+* **Contributors** - Sid Joshi , Maciej Gruszka, 
+* **Last Updated By/Date** - Ankit Pandey, July 2024

weblogic-toolkit-ui/deploy-domain-ocw/deploy-domain-ocw.md

@@ -0,0 +1,61 @@
+# Deploy WebLogic Domain to Oracle Kubernetes Cluster (OKE)
+
+## Introduction
+
+In this lab, we deploy the WebLogic Domain to the Kubernetes cluster. Here we also specify the replica for the cluster.
+
+Estimated Time: 10 minutes
+
+Watch the video below for a quick walk-through of the lab.
+[Deploy WebLogic Domain to OKE Cluster](videohub:1_wz94de1l)
+
+### Objectives
+
+In this lab, you will:
+
+* Deploy the WebLogic Domain to the Kubernetes Cluster.
+
+## Task 1: Deploy the WebLogic Domain to the Oracle Kubernetes Cluster
+
+In this task, we deploy the Kubernetes custom resource for the WebLogic domain to the Kubernetes Cluster.
+
+1. Click **WebLogic Domain**. For **Define the Operator Domain**, we have prefilled value for you. 
+ ![operator domain](images/operator-domain.png)
+
+2. For **Primary Image**, we have prefilled the value with WebLogic **12.2.1.4-slim-ol8**. 
+ ![primary image](images/primary-image.png)
+
+3. For **Auxiliary Image**, leave the default value.
+ ![auxiliary image](images/auxiliary-image.png)
+
+
+4. In **Clusters** section, we have set the **Replicas** value to **2**. 
+
+
+5. In the Datasources section, double click to edit **passwords** for two datasource. You can give **tiger** as the password in both the datasources. Once done, click **Deploy Domain**.
+ ![Datasoure Password](images/datasource-password.png)
+    > This deploys WebLogic Domain test-domain to Kubernetes namespace **test-domain-ns**.
+
+6. Once you see **WebLogic Domain Deployment to Kubernetes Complete** window, Click **OK**.
+ ![Deployment Complete](images/deployment-complete.png)
+
+7. Go back to terminal, Click **Activities** and select the **Terminal** window. Copy the following command and paste it terminal. You should see a similar output, where the pod for introspector runs first then for the Admin Server and later pods for the managed server go in the **Running** state.
+
+ ````bash
+    <copy>kubectl get pods -n test-domain-ns -w</copy>
+ ````
+
+ ![Pod Status](images/pod-status.png)
+
+8. You can also get the domain status through **WebLogic Kubernetes Toolkit UI**. Go back to **WebLogic Kubernetes Toolkit UI** and click **Get Domain Status**.
+ ![Domain Status](images/domain-status.png)
+
+9. In the Domain Status window, Scroll down to see the status of all server pods then click **OK**.
+ ![Server Status](images/server-status.png)
+
+
+## Acknowledgements
+
+* **Author** -  Ankit Pandey
+* **Contributors** - Sid Joshi , Maciej Gruszka, 
+* **Last Updated By/Date** - Ankit Pandey, July 2024