WMS ID 4602

build-ords-apis-in-adb/2-build-ords-apis/build-ords-apis.md

@@ -45,7 +45,7 @@ Estimated Lab Time: 25 minutes
 
 6. The definiton for the PL/SQL procedure will be visible in the SQL Worksheet. This produre expects the following parameters: `p_emp_name`, `p_dept_code` (associated with a `dept_id`), and `comments`. It then inserts these values into the `Employee` table.
 
-    ![Reviewing the PLSQL Procedure in the worksheet](./images/5-plsql-definition-in-sql-worksheet.png " ")
+    ![Reviewing the PLSQL Procedure in the worksheet](./images/5-plsql-procedure-definition-in-sql-worksheet.png " ")
 
 7. Next, you'll insert a new row into the `Employee` table, using this procedure. Take note of one of the available, valid Department Codes: `EN003, FN002, HR001, IT007, LG006, LG009, MK005, OP010, SA004, SP008`.
 
@@ -81,23 +81,23 @@ Estimated Lab Time: 25 minutes
 
     ![Click hamburger then rest](./images/11-click-hamburger-then-rest.png " ")
 
-2. You are now in the **REST** Workshop. Here is where you build and test your ORDS APIs. Click the **AUTOREST** card.
+2. Welcome to the **REST** Workshop. Click the **AUTOREST** card.
 
     ![Click the autorest card](./images/12-click-the-autorest-card.png " ")
 
 3. This is the table you AutoREST-enabled in a previous lab. Before you continue, take a look at the resources available to you (these apply to all of your modules). Right-click the kebab menu, then select **Export OpenAPI**.
 
     ![Export OpenAPI on the project table](./images/13-autorest-table-project-export-open-api.png " ")
 
-4. You'll see a downloadable version of your API in the OpenAPI specification. This makes it easy for you to review, and share definitions. 
+4. You'll see a downloadable version of your API in the OpenAPI specification. This makes it easy for you to review, and share your API definitions. 
 
     ![The downloadable OpenAPI Export](./images/14-open-api-export-download.png " ")
 
 5. Close the Export OpenAPI slider, click the kebab menu again and select **OpenAPI View**. 
 
     ![The OpenAPI view on Project table](./images/15-openapi-view-on-project.png " ")
 
-6. You will see an in-browser testing dashboard based on the OpenAPI specification. Here you can test your APIs without having to log into, or open a separate application. When satisfied, click the **Modules** tab at the top of the REST Workshop page. 
+6. You'll see an in-browser testing dashboard based on the OpenAPI specification. Here you can test your APIs without having to log into, or open a separate application. When satisfied, click the **Modules** tab at the top of the REST Workshop page. 
 
     ![OpenAPI view dashboard](./images/16-open-api-view-dashboard.png " ")
 
@@ -205,8 +205,8 @@ Estimated Lab Time: 25 minutes
     <copy>
         DECLARE
         L_SQLCODE PLS_INTEGER;
-    BEGIN
-        DEMO_USER.PR_ADD_AND_ASSIGN_EMPLOYEE(
+    BEGIN -- Optionally use a fully-qualified name like [SCHEMA].PR_ADD_AND_ASSIGN_EMPLOYEE();
+        PR_ADD_AND_ASSIGN_EMPLOYEE(
             P_EMP_NAME  => :EMP_NAME,
             P_DEPT_CODE => :DEPT_CODE,
             P_COMMENTS  => :COMMENTS
@@ -272,35 +272,37 @@ Estimated Lab Time: 25 minutes
 
     > **NOTE:** The values have already been included in the sample Anonymous Block snippet, but simply clicking the Handler Parameter name will place the parameter value at the current location of your cursor.
 
-8. Now, you can test this new POST API. From the Handler's kebab menu, select **Get cURL command**, then the **+ plus** button of the curl Command modal. A Substitutions modal will appear. Enter in values for `EMP_NAME`, `DEPT_CODE`, `COMMENTS`, and check Null for the `response_status` and `response_message`. Be sure to review and select valid values for the `DEPT_CODE`. Once finished, click **OK**.
+8. Now, you can test this new POST API. From the Handler's kebab menu, select **Get cURL command**, then the **+ plus** button of the curl Command modal. 
 
     ![Retrieving the curl command](./images/42-getting-the-post-curl.png " ")
 
     ![clicking the plus button](./images/27-press-plus-button-get.png " ")
 
+9. A Substitutions modal will appear. Enter in values for `EMP_NAME`, `DEPT_CODE`, `COMMENTS`, and check Null for the `response_status` and `response_message`. Be sure to review and select valid values for the `DEPT_CODE` (Valid values: `EN003`, `FN002`, `HR001`, `IT007`, `LG006`, `LG009`, `MK005`, `OP010`, `SA004`, `SP008`). Once finished, click **OK**.
+
     ![Adding substitution details](./images/43-entering-substitution-details.png " ")
 
-9. Copy the curl command into a clipboard, and remove the `response_status` and `response_message` key:value pairs, and the no-longer-required comma. Then, paste the updated command in a Terminal window and execute the curl command.
+10. Copy the curl command into a clipboard, and remove the `response_status` and `response_message` key:value pairs, and the no-longer-required comma. Then, paste the updated command in a Terminal window and execute the curl command.
 
     ![Copying the post request](./images/44-clicking-copy-for-post.png " ")
 
     ![Empty key value pairs](./images/44-1-empty-key-value-pairs.png " ")
 
     ![Empty key value pairs removed](./images/44-2-key-value-pairs-removed.png " ")
 
-10. You should see the success response message in your terminal. 
+11. You should see the success response message in your terminal. 
 
     ![Reviewing the response in terminal](./images/45-response-in-terminal.png " ")
 
-11. You can also perform a simple query to review that latest INSERT using the following code snippet: 
+12. You can also perform a simple query to review that latest INSERT using the following code snippet: 
 
     ```sql
     <copy>Select * from Employee where emp_name='The name you used in the POST request';</copy>
     ```
 
     ![Querying the latest insert in sql worksheet](./images/46-querying-latest-post-in-sql-worksheet.png " ")
 
-12. And that's it, you've just successfully created your first two custom ORDS APIs. But you've probably noticed, no security? Continue to the next lab to learn more about securing your ORDS APIs.
+13. And that's it, you've just successfully created your first two custom ORDS APIs. But you've probably noticed, no security? Continue to the next lab to learn more about securing your ORDS APIs.
 
 You may now [proceed to the next lab](#next).
 
@@ -309,7 +311,7 @@ You may now [proceed to the next lab](#next).
 ### Author
 
 - Jeff "el jefe" Smith, Distinguished Product Manager
-- Chris Hoina, Senior Product Manager
+- Chris Hoina, Lead Principal Product Manager
 
 ### Last Updated By/Date
 

build-ords-apis-in-adb/3-secure-endpoints/secure-endpoints.md

@@ -91,26 +91,21 @@ Estimated Lab Time: 10 minutes
 
      ![Description Field](./images/11-create-oauth-client-definition.png " ")
 
-4. Previously you created a Privilege, which includes (enumerates) a Role. Here, you can optionally assign the OAuth Client either the `my.test.role` role, the `my.test.priv` privilege, or both (although in this case, a bit redundant).
+4. **Roles** Select the previously created role: `my.test.role` (or your unique role, if it differs).
 
-      Selecting *only* the Role is acceptable, since the Privilege you created includes this Role. Since your `records.module` is protected by the same Privilege, this is a valid approach. 
+    ![choose-roles-tB](./images/12-create-oauth-client-roles.png " ")
 
-      **Roles**
-      - **Roles:** `my.test.role` (or your unique role, if it differs)
+5. **Privileges** Next, choose the privilege: `my.test.priv` (or your unique privilege, if it differs).
+
+    ![choose-ouath-privs](./images/13-create-oauth-client-privs.png " ")
 
-         ![choose-roles-tB](./images/12-create-oauth-client-roles.png " ")
+5. Click the **Create** button when complete. 
 
     Alternatively, you can simply assign the Privilege directly. And since that Privilege enumerates the Role, this is valid as well. 
 
       **Privileges**
       - **Roles:** `my.test.role` (or your unique role, if it differs)
 
-         ![choose-ouath-privs](./images/13-create-oauth-client-privs.png " ")
-
-5. Choose an approach, and click the **Create** button when complete. 
-
-## Task 4: Testing the OAuth2.0 client
-
 1. After clicking **Create**, a Client Secret modal will appear. Copy the Secret Client value to your clipboard or a text editor. 
 
     ![Copy my client secret](./images/14-my-oauth-client-secret.png " ")
@@ -142,7 +137,7 @@ Estimated Lab Time: 10 minutes
 
     > ![Obtaining-the-bearer-token-part-one](./images/17-obtaining-the-bearer-token-part-one.png " ")
 
-4. Execute your cURL command; you will recieve a valid Access Token. In this example, you can use the `GET` endpoint that you created in **Lab 2, Task 3: Building an ORDS GET API** as your target endpoint.
+4. Execute your cURL command; you will receive a valid Access Token. In this example, you can use the `GET` endpoint that you created in **Lab 2, Task 3: Building an ORDS GET API** as your target endpoint.
 
     ![Obtaining-the-bearer-token-part-two](./images/18-obtaining-the-bearer-token-part-two.png " ")
 
@@ -171,7 +166,7 @@ You may now [proceed to the next lab](#next).
 ### Author
 
 - Jeff Smith, Distinguished Product Manager
-- Chris Hoina, Senior Product Manager
+- Chris Hoina, Lead Principal Product Manager
 
 ### Last Updated By/Date
 

build-ords-apis-in-adb/4-workshop-scripts/create_department_table.sql

@@ -1,23 +1,23 @@
-CREATE TABLE "DEMO_USER"."DEPARTMENT" 
+CREATE TABLE "DEPARTMENT" 
    (	"DEPT_ID" NUMBER GENERATED BY DEFAULT AS IDENTITY MINVALUE 1 MAXVALUE 9999999999999999999999999999 INCREMENT BY 1 START WITH 1 CACHE 20 NOORDER  NOCYCLE  NOKEEP  NOSCALE , 
 	"DEPT_CODE" VARCHAR2(5 BYTE) COLLATE "USING_NLS_COMP", 
 	"ESTABLISHED" DATE, 
 	"DETAILS" JSON
    )  DEFAULT COLLATION "USING_NLS_COMP" ;
 
-CREATE UNIQUE INDEX "DEMO_USER"."DEPT_CODE_UK" ON "DEMO_USER"."DEPARTMENT" ("DEPT_CODE") 
+CREATE UNIQUE INDEX "DEPT_CODE_UK" ON "DEPARTMENT" ("DEPT_CODE") 
   ;
 
-CREATE UNIQUE INDEX "DEMO_USER"."DEPT_ID_PK" ON "DEMO_USER"."DEPARTMENT" ("DEPT_ID") 
+CREATE UNIQUE INDEX "DEPT_ID_PK" ON "DEPARTMENT" ("DEPT_ID") 
   ;
 
-CREATE UNIQUE INDEX "DEMO_USER"."DEPARTMENT_DEPT_CODE_UQ" ON "DEMO_USER"."DEPARTMENT" (UPPER("DEPT_CODE")) 
+CREATE UNIQUE INDEX "DEPARTMENT_DEPT_CODE_UQ" ON "DEPARTMENT" (UPPER("DEPT_CODE")) 
   ;
 
-ALTER TABLE "DEMO_USER"."DEPARTMENT" MODIFY ("DEPT_ID" NOT NULL ENABLE);
+ALTER TABLE "DEPARTMENT" MODIFY ("DEPT_ID" NOT NULL ENABLE);
 
-ALTER TABLE "DEMO_USER"."DEPARTMENT" MODIFY ("DEPT_CODE" CONSTRAINT "DEPT_CODE_NN" NOT NULL ENABLE);
+ALTER TABLE "DEPARTMENT" MODIFY ("DEPT_CODE" CONSTRAINT "DEPT_CODE_NN" NOT NULL ENABLE);
 
-ALTER TABLE "DEMO_USER"."DEPARTMENT" ADD CONSTRAINT "DEPT_ID_PK" PRIMARY KEY ("DEPT_ID")
+ALTER TABLE "DEPARTMENT" ADD CONSTRAINT "DEPT_ID_PK" PRIMARY KEY ("DEPT_ID")
   USING INDEX  ENABLE;
 

build-ords-apis-in-adb/4-workshop-scripts/create_employee_table.sql

@@ -1,25 +1,25 @@
-CREATE TABLE "DEMO_USER"."EMPLOYEE" 
+CREATE TABLE "EMPLOYEE" 
    (	"EMP_ID" NUMBER GENERATED BY DEFAULT AS IDENTITY MINVALUE 1 MAXVALUE 9999999999999999999999999999 INCREMENT BY 1 START WITH 1 CACHE 20 NOORDER  NOCYCLE  NOKEEP  NOSCALE , 
 	"EMP_NAME" VARCHAR2(100 BYTE) COLLATE "USING_NLS_COMP", 
 	"DEPT_ID" NUMBER, 
 	"COMMENTS" CLOB COLLATE "USING_NLS_COMP"
    )  DEFAULT COLLATION "USING_NLS_COMP" ;
 
-CREATE UNIQUE INDEX "DEMO_USER"."EMP_ID_PK" ON "DEMO_USER"."EMPLOYEE" ("EMP_ID") 
+CREATE UNIQUE INDEX "EMP_ID_PK" ON "EMPLOYEE" ("EMP_ID") 
   ;
 
-CREATE INDEX "DEMO_USER"."EMP_DEPARTMENT_IX" ON "DEMO_USER"."EMPLOYEE" ("DEPT_ID") 
+CREATE INDEX "EMP_DEPARTMENT_IX" ON "EMPLOYEE" ("DEPT_ID") 
   ;
 
-ALTER TABLE "DEMO_USER"."EMPLOYEE" MODIFY ("EMP_ID" NOT NULL ENABLE);
+ALTER TABLE "EMPLOYEE" MODIFY ("EMP_ID" NOT NULL ENABLE);
 
-ALTER TABLE "DEMO_USER"."EMPLOYEE" MODIFY ("EMP_NAME" CONSTRAINT "EMP_NAME_NN" NOT NULL ENABLE);
+ALTER TABLE "EMPLOYEE" MODIFY ("EMP_NAME" CONSTRAINT "EMP_NAME_NN" NOT NULL ENABLE);
 
-ALTER TABLE "DEMO_USER"."EMPLOYEE" MODIFY ("DEPT_ID" CONSTRAINT "EMP_DEPT_ID_NN" NOT NULL ENABLE);
+ALTER TABLE "EMPLOYEE" MODIFY ("DEPT_ID" CONSTRAINT "EMP_DEPT_ID_NN" NOT NULL ENABLE);
 
-ALTER TABLE "DEMO_USER"."EMPLOYEE" ADD CONSTRAINT "EMP_ID_PK" PRIMARY KEY ("EMP_ID")
+ALTER TABLE "EMPLOYEE" ADD CONSTRAINT "EMP_ID_PK" PRIMARY KEY ("EMP_ID")
   USING INDEX  ENABLE;
 
-ALTER TABLE "DEMO_USER"."EMPLOYEE" ADD CONSTRAINT "FK_EMPLOYEE_DEPT" FOREIGN KEY ("DEPT_ID")
-	  REFERENCES "DEMO_USER"."DEPARTMENT" ("DEPT_ID") ENABLE;
+ALTER TABLE "EMPLOYEE" ADD CONSTRAINT "FK_EMPLOYEE_DEPT" FOREIGN KEY ("DEPT_ID")
+	  REFERENCES "DEPARTMENT" ("DEPT_ID") ENABLE;
 

build-ords-apis-in-adb/4-workshop-scripts/create_procedure.sql

@@ -1,4 +1,4 @@
-CREATE OR REPLACE EDITIONABLE PROCEDURE "DEMO_USER"."PR_ADD_AND_ASSIGN_EMPLOYEE" (
+CREATE OR REPLACE EDITIONABLE PROCEDURE "PR_ADD_AND_ASSIGN_EMPLOYEE" (
       p_emp_name  IN VARCHAR2,
       p_dept_code IN VARCHAR2,
       p_comments  IN CLOB

build-ords-apis-in-adb/4-workshop-scripts/create_project_table.sql

@@ -1,25 +1,25 @@
-CREATE TABLE "DEMO_USER"."PROJECT" 
+CREATE TABLE "PROJECT" 
    (	"PROJ_ID" NUMBER GENERATED BY DEFAULT AS IDENTITY MINVALUE 1 MAXVALUE 9999999999999999999999999999 INCREMENT BY 1 START WITH 1 CACHE 20 NOORDER  NOCYCLE  NOKEEP  NOSCALE , 
 	"PROJ_NAME" VARCHAR2(100 BYTE) COLLATE "USING_NLS_COMP", 
 	"DEPT_ID" NUMBER, 
 	"IS_ACTIVE" BOOLEAN
    )  DEFAULT COLLATION "USING_NLS_COMP" ;
 
-CREATE UNIQUE INDEX "DEMO_USER"."PROJ_ID_PK" ON "DEMO_USER"."PROJECT" ("PROJ_ID") 
+CREATE UNIQUE INDEX "PROJ_ID_PK" ON "PROJECT" ("PROJ_ID") 
   ;
 
-CREATE INDEX "DEMO_USER"."PROJ_DEPARTMENT_IX" ON "DEMO_USER"."PROJECT" ("DEPT_ID") 
+CREATE INDEX "PROJ_DEPARTMENT_IX" ON "PROJECT" ("DEPT_ID") 
   ;
 
-ALTER TABLE "DEMO_USER"."PROJECT" MODIFY ("PROJ_ID" NOT NULL ENABLE);
+ALTER TABLE "PROJECT" MODIFY ("PROJ_ID" NOT NULL ENABLE);
 
-ALTER TABLE "DEMO_USER"."PROJECT" MODIFY ("PROJ_NAME" CONSTRAINT "PROJ_NAME_NN" NOT NULL ENABLE);
+ALTER TABLE "PROJECT" MODIFY ("PROJ_NAME" CONSTRAINT "PROJ_NAME_NN" NOT NULL ENABLE);
 
-ALTER TABLE "DEMO_USER"."PROJECT" MODIFY ("DEPT_ID" CONSTRAINT "PROJ_DEPT_ID_NN" NOT NULL ENABLE);
+ALTER TABLE "PROJECT" MODIFY ("DEPT_ID" CONSTRAINT "PROJ_DEPT_ID_NN" NOT NULL ENABLE);
 
-ALTER TABLE "DEMO_USER"."PROJECT" ADD CONSTRAINT "PROJ_ID_PK" PRIMARY KEY ("PROJ_ID")
+ALTER TABLE "PROJECT" ADD CONSTRAINT "PROJ_ID_PK" PRIMARY KEY ("PROJ_ID")
   USING INDEX  ENABLE;
 
-ALTER TABLE "DEMO_USER"."PROJECT" ADD CONSTRAINT "FK_PROJECT_DEPT" FOREIGN KEY ("DEPT_ID")
-	  REFERENCES "DEMO_USER"."DEPARTMENT" ("DEPT_ID") ENABLE;
+ALTER TABLE "PROJECT" ADD CONSTRAINT "FK_PROJECT_DEPT" FOREIGN KEY ("DEPT_ID")
+	  REFERENCES "DEPARTMENT" ("DEPT_ID") ENABLE;
 

build-ords-apis-in-adb/4-workshop-scripts/oauth_client.sql

@@ -1,5 +1,6 @@
+
 -- Generated by ORDS REST Data Services 26.2.3.r2371104
--- Schema: DEMO_USER  Date: Thu Sep 17 07:11:13 2026 
+-- Schema: ORDSDEMO  Date: Tue Sep 29 08:10:52 2026 
 --
 
 DECLARE
@@ -14,24 +15,39 @@ BEGIN
 
   ORDS.CREATE_ROLE(
       p_role_name=> 'my.test.role');
+  l_roles(1) := 'my.test.role';
+
+  ORDS.DEFINE_PRIVILEGE(
+      p_privilege_name => 'my.test.priv',
+      p_roles          => l_roles,
+      p_patterns       => l_patterns,
+      p_modules        => l_modules,
+      p_label          => 'my.test.priv',
+      p_description    => 'my.test.priv',
+      p_comments       => NULL); 
+
+  l_roles.DELETE;
+  l_modules.DELETE;
+  l_patterns.DELETE;
+
 
   ORDS_SECURITY.IMPORT_CLIENT(
-      p_name             => 'my_test_oauth_client',
-      p_client_id        => 'rP9btP7w5Md72r6iEK3Tog..',
+      p_name             => 'my.oauth.client',
+      p_client_id        => 'qMdpq2WHzkzd1aPHawTmvw..',
       p_grant_type       => 'client_credentials',
-      p_owner            => 'DEMO_USER',
-      p_description      => 'my_test_oauth_client',
+      p_owner            => 'ORDSDEMO',
+      p_description      => 'my.oauth.client',
       p_origins_allowed  => NULL,
       p_redirect_uri     => NULL,
-      p_support_email    => 'my_email@example.com',
-      p_support_uri      => 'https://www.my-company.com/support',
+      p_support_email    => 'test@email.com',
+      p_support_uri      => 'https://example.com',
       p_token_duration   => NULL,
       p_refresh_duration => NULL,
       p_code_duration    => NULL,
-      p_privilege_names  => NULL);
+      p_privilege_names  => 'my.test.priv');
 
    ORDS_SECURITY.GRANT_CLIENT_ROLE(
-      p_client_name     => 'my_test_oauth_client',
+      p_client_name     => 'my.oauth.client',
       p_role_name => 'my.test.role');
 COMMIT;
 EXCEPTION