WMD ID: 11249 & 11371 | Minor changes to specify the exact shape that…

… use must select (#453)

* New folder for a new LiveLab

Created a new folder with placeholder text for a new LiveLab

* Added instructions to integrate MicroTx lib files

* Instructions

Updated image, instructions to run the sample app, integrate TMM files with sample app, and update the YAML file.

* Updated tags and tasks

Restructured the content.

* Changes to manifest file

* Purchase and sale of stocks

* replaced XA sample app with Banking and Trading app

* updated intro

* uncomment lines without going through details

* incorporated feedback

* Updated images for ATP instances

* Self QA

Fixed issues that were identified during self QA.

* updated links to tasks within page

* Self QA checks

* More self QA changes

* added lab 2

* MTRM-1123

Incorporated feedback received from the QA team.

* Incorporated feedback

Incorporated feedback received from the LiveLabs team

* Update screenshots for Lab 4

Added screenshots for Lab 4: ATP-S instance from the latest OCI console

* Chunked data and incorporated feedback

Broke down the long lab of running the app into two smaller labs and incorporated feedback received from Anoosha.

* Minor change in Lab number

* minor updates to the prerequisites

* Update link to common image

* Optional task to enable txn history

* resized images

resized images and minor text updates

* Updated link to the ZIP file

* Updated a link

* Updated a link

* Updates for changes to the image

Bharath has made changes to the image. I have updated the text accordingly.

* changes for updated image

* Changes to the stock broker app

* Comments incorporated to Lab 1

* Incorporated review comments and updated images

* Changes to the Stock Broker app

* Incorporated feedback rxd from Bharath

* Incorporated Shivanshu's feedback

* Update integrate-microtx-lib-files.md

* Update integrate-microtx-lib-files.md

* Specify shape to select

A specific shape has to be selected.

* minor change

---------

Co-authored-by: ZackaryRice <128171922+ZackaryRice@users.noreply.github.com>

microtx-xa-stock-broker-app/introduction/introduction.md

@@ -6,7 +6,7 @@ As organizations rush to adopt microservices architecture, they often run into p
 
 In this workshop, you will learn how to use MicroTx to maintain data consistency across several microservices by deploying and running a Bank and Stock-Trading application. This application contains several microservices and it uses distributed, two-phase commit transaction (XA). It is very simple to use MicroTx. After installing MicroTx, you only need to integrate the MicroTx libraries with your application code to manage transactions. In this workshop, you will learn how you can integrate the MicroTx client libraries with the Bank and Stock-Trading application. During the transaction, each microservice also makes updates to a resource manager to track the change in the amount and stocks. When you run the Bank and Stock-Trading application, you will be able to see how MicroTx ensures consistency of transactions across the distributed microservices and their resource managers. You will also integrate MicroTx with the Kubernetes ecosystem by using tools, such as Kiali and Jaeger, to visualize the flow of requests between MicroTx and the microservices.
 
-### About the Bank and Stock-Trading application
+### About the Bank and Stock-Trading Application
 
 The Bank and Stock-Trading application demonstrates how you can develop microservices that participate in a distributed transaction while using MicroTx to coordinate the requests. You can use the application to withdraw or deposit an amount, as well as buy and sell stocks. Since financial applications that move funds require strong global consistency, the application uses XA transaction protocol.
 
@@ -41,7 +41,7 @@ In this workshop, you will learn how to:
 
 This lab assumes you have:
 - An Oracle Cloud account
-- 4 OCPU and 24 GB memory available in your Oracle Cloud account to run the Bank and Stock-Trading application.
+- At least 4 OCPUs, 24 GB memory, and 128 GB of bootable storage volume is available in your Oracle Cloud Infrastructure tenancy to run the Bank and Stock-Trading application.
 
 Let's begin! If you need to create an Oracle Cloud account, click **Get Started** in the **Contents** menu on the left. Otherwise, if you have an existing account, click **Lab 1**.
 

microtx-xa-stock-broker-app/setup-compute/setup-compute-novnc-ssh.md

@@ -19,6 +19,7 @@ For more information about Terraform and Resource Manager, please see the append
 This lab assumes you have:
 - An Oracle Cloud account
 - SSH Keys (optional)
+- At least 4 OCPUs, 24 GB memory, and 128 GB of bootable storage volume is available in your Oracle Cloud Infrastructure tenancy to run the Bank and Stock-Trading application.
 - You have completed:
     - Lab: Prepare Setup
 
@@ -32,7 +33,7 @@ Your options are:
 ## Task 1A: Create Stack:  Compute + Networking
 1. Identify the ORM stack zip file downloaded in *Lab: Prepare Setup*
 2. Log in to Oracle Cloud
-3.  Open up the hamburger menu in the top left corner.  Click **Developer Services**, and choose **Resource Manager > Stacks**. Choose the compartment in which you would like to install the stack. Click **Create Stack**.
+3. Open up the hamburger menu in the top left corner.  Click **Developer Services**, and choose **Resource Manager > Stacks**. Choose the compartment in which you would like to install the stack. Click **Create Stack**.
 
   ![Select Stacks](https://oracle-livelabs.github.io/common/images/console/developer-resmgr-stacks.png " ")
 
@@ -72,16 +73,9 @@ Your options are:
 
     Depending on the quota you have in your tenancy you can choose from standard Compute shapes or Flex shapes. Please visit the Appendix: Troubleshooting Tips for instructions on checking your quota
 
-    - **Use Flexible Instance Shape with Adjustable OCPU Count?:** Keep the default as checked (unless you plan on using a fixed shape)
-    - **Instance Shape:** Keep the default or select from the list of Flex shapes in the dropdown menu (e.g *VM.Standard.E4.Flex*).
-    - **Instance OCPUS:** Enter 3 to provision an instance with 3 OCPUs.
-
-      If don't have the required quota for Flex Shapes or you prefer to use fixed shapes, follow the instructions below.  Otherwise, skip to the next step.
-
-    - **Use Flexible Instance Shape with Adjustable OCPU Count?:** Unchecked
-    - **Instance Shape:** Accept the default shown or select from the dropdown. e.g. VM.Standard2.2
-
-  ![Use fixed shapes](./images/fixed-shape.png " ")
+    - **Use Flexible Instance Shape with Adjustable OCPU Count?:** Keep the default as checked.
+    - **Instance Shape:** Select VM.Standard.E4.Flex. 
+    - **Instance OCPUS:** Enter 4 to provision an instance with 4 OCPUs. This provisions a VM with 4 OCPUs and 24GB memory.
 
 7. For this section we will provision a new VCN with all the appropriate ingress and egress rules needed to run this workshop.  If you already have a VCN, make sure it has all of the correct ingress and egress rules and skip to the next section.
     - **Use Existing VCN?:** Accept the default by leaving this unchecked. This will create a **new VCN**.
@@ -151,16 +145,9 @@ If you just completed Task 1A, please proceed to Task 2.  If you have an existin
 
     Depending on the quota you have in your tenancy you can choose from standard Compute shapes or Flex shapes. Please visit the Appendix: Troubleshooting Tips for instructions on checking your quota
 
-    - **Use Flexible Instance Shape with Adjustable OCPU Count?:** Keep the default as checked (unless you plan on using a fixed shape)
-    - **Instance Shape:** Keep the default or select from the list of Flex shapes in the dropdown menu (e.g *VM.Standard.E4.Flex*).
-    - **Instance OCPUS:** Accept the default shown. e.g. (**4**) will provision 4 OCPUs and 64GB of memory. You may also elect to reduce or increase the count by selecting from the dropdown. e.g. `[2-24]`. Please ensure you have the capacity available before increasing.
-
-    If don't have the required quota for Flex Shapes or you prefer to use fixed shapes, follow the instructions below.  Otherwise, skip to the next step.
-
-    - **Use Flexible Instance Shape with Adjustable OCPU Count?:** Unchecked
-    - **Instance Shape:** Accept the default shown or select from the dropdown. e.g. VM.StandardE2.2
-
-  ![Use fixed shapes](./images/fixed-shape.png " ")
+    - **Use Flexible Instance Shape with Adjustable OCPU Count?:** Keep the default as checked.
+    - **Instance Shape:** Select VM.Standard.E4.Flex. 
+    - **Instance OCPUS:** Enter 4 to provision an instance with 4 OCPUs. This provisions a VM with 4 OCPUs and 24GB memory.
 
 7. For this section we will an existing VNC.  Please make sure it has all of the correct ingress and egress rules otherwise go back to *Task 1A* and deploy with a self-contained VCN.
     - **Use Existing VCN?:** Check to select.