Quarterly QA for Workshop with WMS ID#11515 (#77)

* 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

* modify operator

* add sandbox details

* change prepare-setup

* image type changed

* modify Load threashold

* dry run feedback included

* Tenancy and compartment name screenshot modified

* ingress-updated

* wktui lab md files updated

* screenshot updated

* changes with command line

* update URL

* Update numbering

* quarterly qa

* quarterly qa

weblogic-toolkit-ui-hpa/configure-prometheus/configure-prometheus.md

@@ -20,9 +20,11 @@ In this lab, you will:
 
 
 
-1. In the terminal, copy and paste the following command to view the files we have downloaded for this workshop.
+1. In the terminal, copy and paste the following command to download the files we need for this workshop.
     ```bash
-    <copy>cd ~/hpa-demo/
+    <copy>curl -O https://objectstorage.uk-london-1.oraclecloud.com/p/-0WCMgxMeZ2w53UvRuto62ejubzxr3mP6yxU36CDk7-uYr7m1jKh4RtH7az-Jwe6/n/lrv4zdykjqrj/b/ankit-bucket/o/hpa-demo.zip
+    unzip hpa-demo.zip
+    cd ~/hpa-demo/
     ls -ltra</copy>
     ```
 
@@ -89,14 +91,15 @@ In this task, we add the prometheus datasource in the Grafana and later we impor
     ![add datasource](images/add-datasource.png)
 
 4. Click **Prometheus** as datasource.
+    ![click prometheus](images/click-prometheus.png)
 
 5. Enter **http://prometheus-server:80** as URL and click **Save & test** as shown below.
     ![prometheus url](images/prometheus-url.png)
 
 6. In Grafana, click **dashboard icon** -> **Import** as shown below.
     ![click dashboard](images/click-dashboard.png)
 
-7. Click **Upload JSON file** and then select the **weblogic-server-dashboard.json** file from **~/hpa-demo** folder as shown below. Click **Open**.
+7. Click **Upload JSON file** and then select the **weblogic_dashboard.json** file from **~/hpa-demo** folder as shown below. Click **Open**.
     ![upload json](images/upload-json.png)
 
 8. Click **Import** to import the WebLogic Server Dashboard.
@@ -105,6 +108,15 @@ In this task, we add the prometheus datasource in the Grafana and later we impor
 9. You will be able to view the WebLogic Server data in WebLogic Server Dashboard as shown below. 
     ![weblogic dashboard](images/weblogic-dashboard.png)
 
+10. Click drop down near to **Heap Usage** and click **Edit**.
+    ![heap usage](images/heap-usage.png)
+
+11. Go to **Field** variable and change its value to **Numeric Fields**. Click **Apply**.
+    ![change number](images/change-number.png)
+
+12. Do the same for **Running Time** and **Open Sockets** and you will have the output similar to below.
+    ![final dashboard](images/final-dashboard.png)
+
 You may now proceed to the next lab.
 
 ## Acknowledgements

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

@@ -19,7 +19,7 @@ In this lab, you will:
 ## Task 1: Configure kubectl (Kubernetes Cluster CLI) to connect to Oracle Kubernetes Cluster
 In this Task, we creats the configuration file *.oci/config* and *.kube/config* in */home/opc* directory. This configuration file allow us to access Oracle Kubernetes Cluster (OKE) from this virtual machine.
 
-1. Click *Activities* and type *Firefox* in search box. Click on the icon for *Firefox*.
+1. Click *Activities* and click on the icon for *Firefox*.
     ![open firefox](images/open-firefox.png)
 
 2. Open the url [https://cloud.oracle.com](https://cloud.oracle.com). Enter your *Cloud Account Name* and then your credential for Oracle Cloud Account and click *Sign In*.
@@ -34,7 +34,7 @@ In this Task, we creats the configuration file *.oci/config* and *.kube/config*
 5. Select *Local Access* and then click on *Copy* as shown.
     ![Local Access](images/local-access.png)
 
-6. Go back to terminal and open a new tab.
+6. Click **Activites**  and open **Terminal**..
 
 7. Paste the copied command in the new tab. For *Do you want to create a new config file?*, Type *y* then press *Enter*. For *Do you want to create your config file by logging in through a browser?*, Type *y* then press *Enter*.
     ![OCI Config](images/oci-config.png)
@@ -53,72 +53,65 @@ In this Task, we creats the configuration file *.oci/config* and *.kube/config*
 
 In this task, we are creating an Auxiliary image, which we will push to the Oracle Cloud Container Registry.
 
-**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.
+**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. For Primary Image, we will use the below **12.2.1.4-slim-ol8** from [oracle container registry](http://container-registry.oracle.com) Image.
 
 **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)
 
 
-
-1. Click *Image*. For Primary Image, we will use the below *weblogic:12.2.1.3-ol8* from [oracle container registry](http://container-registry.oracle.com) Image.So leave default values under *Primary Image* section as shown 
-
-    ![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. To create the Auxiliary Image Tag, we need the following information:
+1. Click **Image** -> **Auxiliary Image** tab. To create the Auxiliary Image Tag, we need the following information:
 
     * End point for the Region
     * Tenancy Namespace
 
     ![click auxiliary](images/click-auxiliary.png)
 
 
-3. Locate the *Endpoint for Your Region*. Refer to the table documented at this URL [https://docs.oracle.com/en-us/iaas/Content/Registry/Concepts/registryprerequisites.htm#Availab](https://docs.oracle.com/en-us/iaas/Content/Registry/Concepts/registryprerequisites.htm#Availab). In the example shown, the endpoint for the region is *US East(Ashburn)* (as the region name) and its endpoint is **iad.ocir.io**. Locate the endpoint for your own *Region Name* and save it in the text file. You will also need it for the next lab.
+2. Locate the *Endpoint for Your Region*. Refer to the table documented at this URL [https://docs.oracle.com/en-us/iaas/Content/Registry/Concepts/registryprerequisites.htm#Availab](https://docs.oracle.com/en-us/iaas/Content/Registry/Concepts/registryprerequisites.htm#Availab). In the example shown, the endpoint for the region is *US East(Ashburn)* (as the region name) and its endpoint is **iad.ocir.io**. Locate the endpoint for your own *Region Name* and save it in the text file. You will also need it for the next lab.
 
     ![region name](images/region-name.png " ")
     ![end points](images/end-point.png " ")
 
     >Now you have both the tenancy namespace and endpoint for your region.
  
 
-4. In lab 2, you already noted the tenancy namespace in your text file. If not, then for finding the Namespace of the tenancy, select the *Hamburger Menu* -> *Developer Services* -> *Container Registry*, as shown. Select the repository you created, you will find the Namespace as shown.
+3. In lab 2, you already noted the tenancy namespace in your text file. If not, then for finding the Namespace of the tenancy, select the *Hamburger Menu* -> *Developer Services* -> *Container Registry*, as shown. Select the repository you created, you will find the Namespace as shown.
     ![Tenancy Namespace](images/tenancy-namespace.png)
 
-5. Now you have both the Tenancy Namespace and Endpoint for your region. Copy the following command and paste it in your text file. Then replace the `END_POINT_OF_YOUR_REGION` with the endpoint of your region name, `NAMESPACE_OF_YOUR_TENANCY` with your tenancy's namespace. 
+4. Now you have both the Tenancy Namespace and Endpoint for your region. Copy the following command and paste it in your text file. Then replace the `END_POINT_OF_YOUR_REGION` with the endpoint of your region name, `NAMESPACE_OF_YOUR_TENANCY` with your tenancy's namespace. 
 
     ````bash
     <copy>END_POINT_OF_YOUR_REGION/NAMESPACE_OF_YOUR_TENANCY/test-model-your_first_name:v1</copy>
     ````
 
 > For example, in my case Auxiliary Image tag is `iad.ocir.io/tenancynamespace/test-model-ankit:v1`.
 
-6. In step 4, you also determined the tenancy namespace.
+5. In step 4, you also determined the tenancy namespace.
 Enter the  Auxiliary Image Registry Push Username as follows: `NAMESPACE_OF_YOUR_TENANCY`/`YOUR_ORACLE_CLOUD_USERNAME`. <br>
 * Replace `NAMESPACE_OF_YOUR_TENANCY` with your tenancy's namespace
 * Replace `YOUR_ORACLE_CLOUD_USERNAME` with your Oracle Cloud Account user name and then copy the replaced username from your text file and paste it in the *Auxiliary Image Registry Push Username*.
 > For example, in my case **Auxiliary Image Registry Push Username** is `tenancynamespace/[email protected]`.
 * For Password, copy and paste the Authentication Token from your text file(or wherever you saved it) and paste it in the **Auxiliary Image Registry Push Username**.
     ![Auxiliary Image Details](images/auxiliary-image-details.png)
 
-7. Click *Create Auxiliary Image*.
+6. Click *Create Auxiliary Image*.
     ![Create Auxiliary Image](images/create-auxiliary-image.png)
 
-8. As we already prepared the model in Lab 2, so click on *No*.
+7. As we already prepared the model in Lab 2, 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.
+8. 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*.
+9. 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 repository inside your Oracle Cloud Container Image Registry.
+10. Click *Push Auxiliary Image* to push the image in 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*. 
+11. Once image is successfully pushed, On *Push Image Complete* window, click *Ok*. 
     ![Auxiliary Pushed](images/auxiliary-pushed.png)
 
 You may now proceed to the next lab.

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

@@ -26,11 +26,11 @@ To run this lab, you must have:
 
 In this task, we navigate through the resources in on-premise *test-domain* using WebLogic Administration console.
 
-1. On left side, click *Arrow Icon*. 
-    ![Clipboard](images/clipboard-setup.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 first, then you can paste it in remote desktop. Again click on *Arrow Icon* to hide the *Settings* option.
 
-2. Click on  *Oracle WebLogic Server* tab and enter *weblogic/Welcome1%* as `Username/Password`, then click *Login*. You can see, we have WebLogic Server version *12.2.1.3.0*.   
+1. Click **Activities** and select the **Mozila Firefox**  as shown below.
+    ![click admin](images/click-admin.png)
+
+2. Click on  **Local WLS** bookmark and we have saved the password for you, so click *Login*. You can see, we have WebLogic Server version *12.2.1.4.0*.   
     ![Login Admin Console](images/login-admin-console.png)
 
 3. To view available servers, expand *Environment* and click *Servers*. You can see, we have one dynamic clusters with 5 managed servers. 
@@ -46,13 +46,13 @@ In this task, we navigate through the resources in on-premise *test-domain* usin
 
 For simplicity of lab, we created *`base_project.wktproj`*, which preset the location of docker, Java, Oracle Home, Primary Image Tag. In this task, we open  *`base_project.wktproj`* project.
 
-1. Click *Activities* and then type **WebLogic** in search box. Click the icon for *WebLogic Kubernetes Toolkit UI*.
+1. Click *Activities* and click the icon for *WebLogic Kubernetes Toolkit UI*.
     ![Open WKTUI](images/open-wktui.png)
 
 2. To open *base_project.wktproj* project, click *File* -> *Open Project*. 
     ![Open Project](images/open-project.png)
 
-3. Click *Downloads* in left side, then choose *base_project.wktproj* and click *Open Project*.
+3. Click *Home* in left side, then choose *base_project.wktproj* and click *Open Project*.
     ![Project Location](images/project-location.png)
 
     > **For your information only:**<br>
@@ -92,49 +92,7 @@ In this task, we perform introspection of an on-premise domain, which creates a
     > The result of this WDT introspection are model(a metadata representation of your domain configuration), placeholder, where you can specify the values (like password for datasource) and application in the application archive.
 
 
-## Task 5: Modify the model file to add wls-exporter
-
-In this task, we are going to download the source code for this workshop. This source code consist **wls-exporter.war** and updated **opdemo.war**. 
-
-1. To open terminal, click on **Activities** and select the **Terminal**.
-    ![open terminal](images/open-terminal.png)
-
-2. Copy and paste the following command to the terminal to download the source code. This source code contains the configuration file which setup the required resources for this workshop.
-    ```bash
-    <copy>curl -O https://objectstorage.uk-london-1.oraclecloud.com/p/2pF_MrYsfO9OtWWoLyKJReXNLn-U07FbuB-saUQJFb9AFE-bDgaXwIhnkKNSAl0C/n/lrv4zdykjqrj/b/ankit-bucket/o/hpa-demo.zip
-    unzip ~/hpa-demo.zip
-    cd ~/hpa-demo/</copy>
-    ```
-
-    ![download source](images/download-source.png)
-
-3. In WKTUI, copy and paste the following configuration below the opdemo as shown in the screenshot.
-    ```bash
-    <copy>wls-exporter:
-            SourcePath: wlsdeploy/applications/wls-exporter.war
-            ModuleType: war
-            Target: cluster_1,admin-server</copy>
-    ```
-
-    ![add wls-exporter](images/add-wlsexporter.png)
-
-4. In WKTUI, in the **archive.zip** section, select the **opdemo.war** and click **-** to remove the **opdemo.war** file.
-    ![remove opdemo](images/remove-opdemo.png)
-
-5. In WKTUI, in the **archive.zip** section, click **+** icon to add the **wls-exporter.war** by select the following options and click **OK**.
-
-    **Archive Entry Type:**         select **Application**.</br>
-    **File system type to add:**    select **File**.</br>
-    **Application Archive File:**   select the **wls-exporter.war** file from **~/hpa-demo** folder.
-
-    ![add wls](images/add-wls.png)
-
-6. Similarly, add the updated **opdemo.war** file from **~/hpa-demo/** folder as shown in screenshot.
-    ![update opdemo](images/update-opdemo.png)
-
-    > Updated **opdemo.war** have session limit of 2 minutes, which is requied to demonstrate the cluster scaling.
-
-## Task 5: Validate and Prepare Model 
+## 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).
 

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

@@ -16,39 +16,45 @@ In this lab, you will:
 
 In this task, we deploy the Kubernetes custom resource for the WebLogic domain to Kubernetes Cluster.
 
-1. Scroll down, enter the following in Primary Image section, Enter *domain-secret* as *Image Pull Secret Name*, and Use Oracle account username and password in *Image Registry Pull Username* and *Image Registry Pull Password*. Enter your Oracle email id in *Image Registry Pull Email Address*. These are the same credential which you used to accept license for *weblogic* images in Oracle Container Registry.
+1. Click **WebLogic domain** and copy and paste the following image tag in **Primary Image Tag** as shown.
+    ```bash
+    <copy>container-registry.oracle.com/middleware/weblogic:12.2.1.4-slim-ol8</copy>
+    ```
+    ![enter primary tag](images/enter-primary.png)
+
+2. Scroll down, enter the following in Primary Image section, Enter *domain-secret* as *Image Pull Secret Name*, and Use Oracle account username and password in *Image Registry Pull Username* and *Image Registry Pull Password*. Enter your Oracle email id in *Image Registry Pull Email Address*. These are the same credential which you used to accept license for *weblogic* images in Oracle Container Registry.
     ![Primary Image Details](images/primary-image-details.png)
     > **For your information only:**<br>
     > We are pulling the image from the Oracle Container Registry, so we are specifying the credential, which we used to accept the license agreement for WebLogic Server Images.
 
 
-2. Scroll down, in Auxiliary Image section, uncheck the box for **Specify Auxiliary Image Pull Credentials**.
+3. Scroll down, in Auxiliary Image section, uncheck the box for **Specify Auxiliary Image Pull Credentials**.
 
-3.  In *Clusters* section, click on *Edit* icon as shown.
+4.  In *Clusters* section, click on *Edit* icon as shown.
     ![Cluster Resize](images/cluster-resize.png)
 
-4. Enter *2* as *Replicas* and then Click *OK*. The size of replica decides the number of managed server in the *Running* state after successfull deployment of WebLogic Domain to Kubernetes cluster.
+5. Enter *2* as *Replicas* and then Click *OK*. The size of replica decides the number of managed server in the *Running* state after successfull deployment of WebLogic Domain to Kubernetes cluster.
     ![Cluster Replicas](images/cluster-replicas.png)
 
-5. In Datasources section, double click to edit *passwords* for two datasource. You can give *tiger* as password in both the datasources. Once done, click *Deploy Domain*.
+6. In Datasources section, double click to edit *passwords* for two datasource. You can give *tiger* as password in both the datasources. Once done, click *Deploy Domain*.
     ![Datasoure Password](images/datasource-password.png)
     > This deploy WebLogic Domain test-domain to Kubernetes namespace *test-domain-ns*.
 
-6. Once you see *WebLogic Domain Deployment to Kubernetes Complete* window, Click *OK*.
+7. 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 the similar output, where pod for introspector run first then for the Admin Server and later pods for managed server goes in the *Running* state.
+8. Go back to terminal, Click *Activities* and select the *Terminal* window. Copy the following command and paste it terminal. You should see the similar output, where pod for introspector run first then for the Admin Server and later pods for managed server goes 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*.
+9. 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 Domain Status window, Scroll down to see status of all server pods then click *OK*.
+10. In Domain Status window, Scroll down to see status of all server pods then click *OK*.
     ![Server Status](images/server-status.png)
 
 You may now proceed to the next lab.