LiveLabs Changes to Add ADB Developer Provisioning Instructions. (#310)

* Adding EL9 updates to the noVNC lab.

* General maintenance on the noVNC lab.

* Update 6-labs-setup-graphical-remote-desktop.md

* Updates to shared ADB provisioning instructions.

building-blocks/tasks/adb/provision-body-developer.md

@@ -0,0 +1,138 @@
+<!--
+    {
+        "name":"Provision Autonomous Database",
+        "description":"Provision an ADB. Use the `variables.json` file to update provisioning parameters, including database name, ECPUs, storage and more."
+    }
+-->
+1. Click **Create Autonomous Database** to start the instance creation process. The **Create Autonomous Database** page is displayed. Select the desired region and compartment. If you get a **Forbidden** message, that indicates you are in the wrong compartment.
+
+    <if type="livelabs">
+    ![Click Create Autonomous Database.](images/ll-adb-click-create-adb.png " ")
+    </if>
+
+    <if type="freetier">
+    ![Click Create Autonomous Database.](images/click-create-new-adb.png " ")
+    </if>
+
+2.  In the **Provide basic information for the Autonomous Database** section, specify the following:
+
+<if type="freetier">
+    - **Compartment**: Select the compartment you just created.
+    - **Display name**: Enter a memorable name for the database for display purposes. For this lab, use **[](var:db_display_name)**.
+    - **Database Name**: Use letters and numbers only, starting with a letter. Maximum length is 14 characters. (Underscores not supported.) For this lab, use **[](var:db_name)**.
+
+        ![Enter the required details.](./images/adb-create-screen-names.png =70%x*)
+
+    >**Note:** Ensure that you use the suggested database names as instructed in this step, and not those shown in the screenshots.
+</if>
+<if type="livelabs">
+    - **Compartment** - Use the default compartment created for you.
+    - **Display Name** - Enter a memorable name for the database for display purposes. For this lab, use **[](var:db_display_name)**.
+    - **Database Name** - Use letters and numbers only, starting with a letter. Maximum length is 14 characters. (Underscores not supported.) For this lab, use **[](var:db_name_livelabs)**. For example, if your assigned username for the workshop is **LL2252-USER**, then your database name will be something like **[](var:db_name_livelabs_example)**.
+
+    ![Enter the required details.](./images/adb-create-screen-names.png =70%x*)
+
+> **Note:** Ensure that you use the suggested database names as instructed in this step, and not those shown in the screenshots.
+</if>
+
+3. In the **Choose a workload type** section, choose a workload type. Select the workload type for your database from the following choices:
+
+    - **Data Warehouse**: Designed to support all standard SQL and business intelligence (BI) tools, and provides all of the performance of the market-leading Oracle Database in an environment that is tuned and optimized for data warehouse workloads
+    - **Transaction Processing**: Provides all of the performance of the market-leading Oracle Database in an environment that is tuned and optimized to meet the demands of a variety of applications, including: mission-critical transaction processing, mixed transactions and analytics, IoT, and JSON document store
+    - **JSON Database**: It is Oracle Autonomous Transaction Processing, but designed for developing NoSQL-style applications that use JavaScript Object Notation (JSON) documents. You can store up to 20 GB of data other than JSON document collections. There is no storage limit for JSON collections.
+    - **APEX**: It is a low cost, Oracle Cloud service offering convenient access to the Oracle APEX platform for rapidly building and deploying low-code applications
+
+    For this workshop, accept the **Data Warehouse** default selection.
+
+    ![Choose a workload type.](images/adb-create-screen-workload.png =70%x*)
+
+4. In the **Choose a deployment type** section, accept the **Serverless** default selection.
+
+    ![Choose a deployment type.](images/adb-create-screen-deployment-type.png =70%x*)
+
+5. In the **Configure the database** section, accept the default selections as follows:
+
+    - **Always Free** - Always Free databases are especially useful for development and trying new features. You can deploy an Always Free instance in an Always Free account or paid account. However, it must be deployed in the home region of your tenancy. The only option you specify in an Always Free database is the database version. For this lab, we recommend you leave **Always Free** turned off.
+    - **Developer** - Developer databases provide a great low cost option for developing apps with Autonomous Database. You have similar features to Always Free - but are not limited in terms of region deployments or the number of databases in your tenancy. Therefore, we will **turn on the Developer model** for this lab. You can upgrade your Developer Database to a full paid version later and benefit from greater control over resources, backups and more."
+    - **Choose database version** - Select **23ai** as the database version.
+    - **ECPU count** - Number of ECPUs for your service. For this lab, specify **[](var:db_ocpu)**. If you choose an Always Free database, you do not need to specify this option.
+    - **Storage (TB)** - Select your storage capacity in terabytes. For this lab, specify **[](var:db_storage)** of storage. Or, if you choose an Always Free database, it comes with 20 GB of storage.
+    - **Compute auto scaling** - For this lab, keep auto scaling enabled, to enable the system to automatically use up to three times more compute and IO resources to meet workload demand.
+    - **Storage auto scaling** - For this lab, there is no need to enable storage auto scaling, which would allow the system to expand up to three times the reserved storage.
+
+        > **Note:** You cannot scale up/down an Always Free or Developer autonomous database.
+
+        ![Choose the remaining parameters.](./images/provision-developer-adb-screen.png =65%x*)
+
+6. In the **Backup retention** section, you can either accept the default value or specify your own preferred backup retention days value. Accept the default 60 days default value.
+
+     ![Choose backup retention.](./images/choose-backup-retention.png =70%x*)
+
+7. In the **Create administrator** credentials section, specify the following:
+
+    - **Username:** This read-only field displays the default administrator username, **`ADMIN`**. _**Important:** Make a note of this **username** as you will need it to perform later tasks._
+    - **Password:** Enter a password for the **`ADMIN`** user of the service instance choice such as **`Training4ADW`**. _**Important:** Make a note of this **password** as you will need it to perform later tasks._
+    - **Confirm password:** Confirm your password.
+
+        > **Note:** The password must meet the following requirements:    
+            - Must be between 12 and 30 characters long and must include at least one uppercase letter, one lowercase letter, and one numeric character.    
+            - Cannot contain the username.    
+            - Cannot contain the double quote (") character.    
+            - Must be different from the last 4 passwords used.    
+            - Must not be the same password that you set less than 24 hours ago.
+
+        ![Enter password and confirm password.](./images/adb-create-screen-password.png =70%x*)
+
+8. In the **Choose network access** section, select one of the following options:
+    - For this lab, accept the default, **Secure access from everywhere**.
+    - If you want to allow traffic only from the IP addresses and VCNs you specify - where access to the database from all public IPs or VCNs is blocked, select **Secure access from allowed IPs and VCNs only** in the Choose network access area.
+    - If you want to restrict access to a private endpoint within an OCI VCN, select **Private endpoint access only** in the Choose network access area.
+    - If the **Require mutual TLS (mTLS) authentication** option is selected, mTLS will be required to authenticate connections to your Autonomous Database. TLS connections allow you to connect to your Autonomous Database without a wallet, if you use a JDBC thin driver with JDK8 or above. See the [documentation for network options](https://docs.oracle.com/en/cloud/paas/autonomous-database/adbsa/support-tls-mtls-authentication.html#GUID-3F3F1FA4-DD7D-4211-A1D3-A74ED35C0AF5) for options to allow TLS, or to require only mutual TLS (mTLS) authentication.
+
+        ![Choose the network access.](./images/adb-create-screen-choose-network.png =70%x*)
+
+9. In the **Choose a license and Oracle Database edition** section, accept the default selection, **This Database is provisioned with License included license type**.
+
+    >**Note:** Select the **Bring Your Own License (BYOL)** type when your organization has existing database licenses.
+
+    ![Choose a license.](./images/choose-license.png =70%x*)
+
+10. For this lab, do not provide a contact email address. The "Contact Email" field allows you to list contacts to receive operational notices and announcements as well as unplanned maintenance notifications.
+
+    ![Do not provide a contact email address.](images/adb-create-screen-contact-email.png "email")
+
+11. Click **Create Autonomous Database**.
+
+    ![Click Create Autonomous Database.](./images/click-create-adb.png =70%x*)
+
+12.  The **Autonomous Database details** page is displayed. The status of your ADB instance is **PROVISIONING**.
+
+    <if type="freetier">
+    ![Database Provisioning message.](./images/adb-create-provisioning-message.png " ")
+    </if>
+
+    <if type="livelabs">
+    ![Database Provisioning message.](./images/ll-adb-create-provisioning-message.png " ")
+    </if>
+
+    A **Check database lifecycle state** informational box is displayed. You can navigate through this tour or choose to skip it. Click **Skip tour**. A **Skip guided tour** dialog box is displayed. Click **Skip**.
+
+    In a few minutes, the instance status changes to **AVAILABLE**. At this point, your Autonomous Data Warehouse database instance is ready to use! Review your instance's details including its name, database version, ECPU count, and storage size.
+
+    <if type="livelabs">
+    ![Database complete message.](./images/ll-adb-create-complete-message.png " ")
+    </if>
+
+    <if type="freetier">
+    ![Database complete message.](./images/adb-create-complete-message.png " ")
+    </if>
+
+13. Click the **Autonomous Database** link in the breadcrumbs. The **Autonomous Database** page is displayed. The new Autonomous Database instance is displayed. In the following screen capture, the instance display name is **MyQuickStart**.
+
+    <if type="livelabs">
+    ![Database instance displayed.](./images/ll-adb-page.png " ")
+    </if>
+
+    <if type="freetier">
+    ![Database instance displayed.](./images/adb-instance-displayed.png " ")
+    </if>

building-blocks/tasks/adb/provision-body.md

@@ -28,7 +28,7 @@
 <if type="livelabs">
     - **Compartment** - Use the default compartment created for you.
     - **Display Name** - Enter a memorable name for the database for display purposes. For this lab, use **[](var:db_display_name)**.
-    - **Database Name** - Use letters and numbers only, starting with a letter. Maximum length is 14 characters. (Underscores not supported.) For this lab, use **[](var:db_name_livelabs)**. For example, if your assigned username for the workshop is **LL81481-USER**, then your database name will be something like **[](var:db_name_livelabs_example)**.
+    - **Database Name** - Use letters and numbers only, starting with a letter. Maximum length is 14 characters. (Underscores not supported.) For this lab, use **[](var:db_name_livelabs)**. For example, if your assigned username for the workshop is **LL2252-USER**, then your database name will be something like **[](var:db_name_livelabs_example)**.
 
     ![Enter the required details.](./images/adb-create-screen-names.png =70%x*)