Naming and version updates (#956)

Author: andytael

cloudbank-v4/pom.xml

@@ -8,7 +8,7 @@
     <parent>
         <groupId>org.springframework.boot</groupId>
         <artifactId>spring-boot-starter-parent</artifactId>
-        <version>3.3.3</version>
+        <version>3.3.4</version>
         <relativePath/> <!-- lookup parent from repository -->
     </parent>
 

docs-source/cloudbank/content/_index.md

@@ -3,17 +3,14 @@ archetype = "home"
 title = "CloudBank AI"
 +++
 
-Welcome to CloudBank AI - an on-demand, self-paced learning resource you can use
-to learn about developing microservices with [Spring Boot](https://spring.io/projects/spring-boot)
-and [Spring Cloud Oracle](https://github.com/oracle/spring-cloud-oracle)
-and deploying, running and managing them with [Oracle Backend for Spring Boot and Microservices](https://bit.ly/oraclespringboot).
+Welcome to CloudBank AI - an on-demand, self-paced learning resource you can use to learn about developing microservices with [Spring Boot](https://spring.io/projects/spring-boot)
+and [Spring Cloud Oracle](https://github.com/oracle/spring-cloud-oracle) and deploying, running and managing them with [Oracle Backend for Microservices and AI](https://bit.ly/OracleAI-microservices).
 
 You can follow through from beginning to end, or you can start at any module that you are interested in.
 
 ### What you will need
 
-To complete the modules you will somewhere to run Oracle Backend for Spring Boot and Microservices.
-The instructions in the Module 1 provide three alternatives: 
+To complete the modules you will somewhere to run Oracle Backend for Microservices and AI. The instructions in the Module 1 provide three alternatives:
 
 - Locally in a container - you will need a container platform like Docker Desktop, Rancher Desktop, Podman Desktop or similar.
   This option is recommended only if you have at least 64GB of RAM.  With less memory this option will probably be too slow.
@@ -32,45 +29,23 @@ but you will have a better overall experience if you use one.  We recommend Visu
 
 CloudBank contains the following modules:
 
-* **Module 1: Provision the Backend**
-  This module guides you through provisioning an instance of the backend using
-  Oracle Cloud Infrastructure (OCI) or on your local machine using Docker Compose.
-* **Module 2: Preparing your Development Environment**  
-  This module guides you through setting up your development environment including
-  and IDE and a toolchain to build and test your applications.
-* **Module 3: Build the Account Microservice**  
-  This module walks you through building your very first microservice using Spring Boot.
-  It assumes no prior knowledge of Spring Boot, so its a great place to start if you
-  have not used Spring Boot before. This module demonstrates how to build a service
-  with a *synchronous* API implemented as REST endpoints using Spring Web MVC, and how to
-  store data in Oracle Database using Spring Data JPA.
-* **Module 4: Build the Check Processing Microservices**  
-  In this module, you will build microservices that use *asynchronous* messaging
-  to communicate using Spring JMS and Oracle Transactional Event Queues. It introduces
-  service discovery using Eureka Service Registry (part of [Spring Cloud Netflix](https://spring.io/projects/spring-cloud-netflix)) 
-  and [Spring Cloud OpenFeign](https://spring.io/projects/spring-cloud-openfeign).
-* **Module 5: Manage Saga Transactions across Microservices**  
-  This module introduces the Saga pattern, a very important pattern that helps us
-  manage data consistency across microservices. We will explore the Long Running
-  Action specification, one implementation of the Saga pattern, and then build
-  a Transfer microservice that will manage funds transfers using a saga.  
-* **Module 6: Building the CloudBank AI Assistant using Spring AI**
-  This modules introduces [Spring AI](https://github.com/spring-projects/spring-ai)
-  and explores how it can be used to build a CloudBank AI Assistant (chatbot) that will
-  allow users to interact with CloudBank using a chat-based interface.
-* **Module 7: Deploying the full CloudBank Application using the CLI**  
-  In this module, you will learn how to deploy the full CloudBank application
-  to Oracle Backend for Spring Boot and Microservices using the CLI.
-  If you prefer to use an IDE, skip this module and go to module 6 instead.
-* **Module 8: Deploying the full CloudBank Application using the IDE plugins**  
-  In this module, you will learn how to deploy the full CloudBank application
-  to Oracle Backend for Spring Boot and Microservices using one of the
-  IDE plugins - for Visual Studio Code or IntelliJ.  
-* **Module 9: Explore the Backend Platform**  
-  This module will take you on a guided tour through the Oracle Backend for
-  Spring Boot and Microservices platform. You will learn about the platform
-  services and observability tools that are provided out-of-the-box.
-* **Module 10: Cleanup**
-  This module demonstrates how to clean up any resources created when
-  you provisioned an instance of Oracle Backend for Spring Boot and Microservices
-  on Oracle Cloud Infrastructure (OCI) or on your local machine using Docker Compose.  
+- **Module 1: Provision the Backend**
+  This module guides you through provisioning an instance of the backend using Oracle Cloud Infrastructure (OCI) or on your local machine using Docker Compose.
+- **Module 2: Preparing your Development Environment**  
+  This module guides you through setting up your development environment including and IDE and a toolchain to build and test your applications.
+- **Module 3: Build the Account Microservice**  
+  This module walks you through building your very first microservice using Spring Boot. It assumes no prior knowledge of Spring Boot, so its a great place to start if you have not used Spring Boot before. This module demonstrates how to build a service with a *synchronous* API implemented as REST endpoints using Spring Web MVC, and how to store data in Oracle Database using Spring Data JPA.
+- **Module 4: Build the Check Processing Microservices**  
+  In this module, you will build microservices that use *asynchronous* messaging to communicate using Spring JMS and Oracle Transactional Event Queues. It introduces service discovery using Eureka Service Registry (part of [Spring Cloud Netflix](https://spring.io/projects/spring-cloud-netflix)) and [Spring Cloud OpenFeign](https://spring.io/projects/spring-cloud-openfeign).
+- **Module 5: Manage Saga Transactions across Microservices**  
+  This module introduces the Saga pattern, a very important pattern that helps us manage data consistency across microservices. We will explore the Long Running Action specification, one implementation of the Saga pattern, and then build a Transfer microservice that will manage funds transfers using a saga.  
+- **Module 6: Building the CloudBank AI Assistant using Spring AI**
+  This modules introduces [Spring AI](https://github.com/spring-projects/spring-ai) and explores how it can be used to build a CloudBank AI Assistant (chatbot) that will allow users to interact with CloudBank using a chat-based interface.
+- **Module 7: Deploying the full CloudBank Application using the CLI**  
+  In this module, you will learn how to deploy the full CloudBank application to Oracle Backend for Microservices and AI using the CLI. If you prefer to use an IDE, skip this module and go to module 6 instead.
+- **Module 8: Deploying the full CloudBank Application using the IDE plugins**  
+  In this module, you will learn how to deploy the full CloudBank application to Oracle Backend for Microservices and AI using one of the IDE plugins - for Visual Studio Code or IntelliJ.  
+- **Module 9: Explore the Backend Platform**  
+  This module will take you on a guided tour through the Oracle Backend for Microservices and AI platform. You will learn about the platform services and observability tools that are provided out-of-the-box.
+- **Module 10: Cleanup**
+  This module demonstrates how to clean up any resources created when you provisioned an instance of Oracle Backend for Microservices and AI on Oracle Cloud Infrastructure (OCI) or on your local machine using Docker Compose.

docs-source/cloudbank/content/account/_index.md

@@ -4,8 +4,4 @@ title = "Account Microservice"
 weight = 3
 +++
 
-This module walks you through building your very first microservice using Spring Boot.
-It assumes no prior knowledge of Spring Boot, so its a great place to start if you
-have not used Spring Boot before. This module demonstrates how to build a service
-with a *synchronous* API implemented as REST endpoints using Spring Web MVC, and how to
-store data in Oracle Database using Spring Data JPA.
+This module walks you through building your very first microservice using Spring Boot. It assumes no prior knowledge of Spring Boot, so its a great place to start if you have not used Spring Boot before. This module demonstrates how to build a service with a *synchronous* API implemented as REST endpoints using Spring Web MVC, and how to store data in Oracle Database using Spring Data JPA.

docs-source/cloudbank/content/account/create-project.md

@@ -14,7 +14,7 @@ Create a project to hold your Account service.  In this lab, you will use the Sp
 
 1. Select the Spring Boot Version
 
-   You will be presented with a list of available Spring Boot versions. Choose **3.2.2** (or the latest 3.2.x version available).
+   You will be presented with a list of available Spring Boot versions. Choose **3.3.4** (or the latest 3.3.x version available).
 
   ![Specify Spring Boot version](../images/obaas-spring-init-2.png " ")
 

docs-source/cloudbank/content/account/deploy.md

@@ -7,7 +7,7 @@ weight = 9
 
 1. Prepare the data source configuration for deployment
 
-    Update the data source configuration in your `src/main/resources/application.yaml` as shown in the example below.  This will cause the service to read the correct database details that will be injected into its pod by the Oracle Backend for Spring Boot and Microservices.
+    Update the data source configuration in your `src/main/resources/application.yaml` as shown in the example below.  This will cause the service to read the correct database details that will be injected into its pod by the Oracle Backend for Microservices and AI.
 
     ```yaml
     datasource:
@@ -100,21 +100,21 @@ weight = 9
 
 1. Prepare the backend for deployment
 
-    The Oracle Backend for Spring Boot and Microservices admin service is not exposed outside the Kubernetes cluster by default. Oracle recommends using a **kubectl** port forwarding tunnel to establish a secure connection to the admin service.
+    The Oracle Backend for Microservices and AI admin service is not exposed outside the Kubernetes cluster by default. Oracle recommends using a **kubectl** port forwarding tunnel to establish a secure connection to the admin service.
 
     Start a tunnel using this command in a new terminal window:
 
     ```shell
     $ kubectl -n obaas-admin port-forward svc/obaas-admin 8080
     ```
 
-    Get the password for the `obaas-admin` user. The `obaas-admin` user is the equivalent of the admin or root user in the Oracle Backend for Spring Boot and Microservices backend.
+    Get the password for the `obaas-admin` user. The `obaas-admin` user is the equivalent of the admin or root user in the Oracle Backend for Microservices and AI backend.
 
     ```shell
     $ kubectl get secret -n azn-server  oractl-passwords -o jsonpath='{.data.admin}' | base64 -d
     ```
 
-    Start the Oracle Backend for Spring Boot and Microservices CLI (*oractl*) in a new terminal window using this command:
+    Start the Oracle Backend for Microservices and AI CLI (*oractl*) in a new terminal window using this command:
 
     ```shell
     $ oractl
@@ -133,7 +133,7 @@ weight = 9
     oractl:>
     ```
 
-    Connect to the Oracle Backend for Spring Boot and Microservices admin service using the `connect` command. Enter `obaas-admin` and the username and use the password you collected earlier.
+    Connect to the Oracle Backend for Microservices and AI admin service using the `connect` command. Enter `obaas-admin` and the username and use the password you collected earlier.
 
     ```shell
     oractl> connect
@@ -143,7 +143,7 @@ weight = 9
     oractl:>
     ```
 
-    Create a database "binding" by tunning this command.  Enter the password (`Welcome1234##`) when prompted.  This will create a Kubernetes secret in the `application` namespace called `account-db-secrets` which contains the username (`account`), password, and URL to connect to the Oracle Autonomous Database instance associated with the Oracle Backend for Spring Boot and Microservices.
+    Create a database "binding" by tunning this command.  Enter the password (`Welcome1234##`) when prompted.  This will create a Kubernetes secret in the `application` namespace called `account-db-secrets` which contains the username (`account`), password, and URL to connect to the Oracle Autonomous Database instance associated with the Oracle Backend for Microservices and AI.
 
     ```shell
     oractl:> bind --app-name application --service-name account
@@ -156,10 +156,10 @@ weight = 9
 
 1. Deploy the account service
 
-    You will now deploy your account service to the Oracle Backend for Spring Boot and Microservices using the CLI.  You will deploy into the `application` namespace, and the service name will be `account`.  Run this command to deploy your service, make sure you provide the correct path to your JAR file.  **Note** that this command may take 1-3 minutes to complete:
+    You will now deploy your account service to the Oracle Backend for Microservices and AI using the CLI.  You will deploy into the `application` namespace, and the service name will be `account`.  Run this command to deploy your service, make sure you provide the correct path to your JAR file.  **Note** that this command may take 1-3 minutes to complete:
 
     ```shell
-    oractl:> deploy --app-name application --service-name account --artifact-path /path/to/accounts-0.0.1-SNAPSHOT.jar --image-version 0.0.1
+    oractl:> deploy --app-name application --service-name account --artifact-path /path/to/accounts-0.0.1-SNAPSHOT.jar --image-version 0.0.1 --java-version ghcr.io/oracle/graalvm-native-image-obaas:21
     uploading: /Users/atael/tmp/cloudbank/accounts/target/accounts-0.0.1-SNAPSHOT.jar
     building and pushing image...
 
@@ -169,7 +169,7 @@ weight = 9
     oractl:>
     ```
 
-    > What happens when you use the Oracle Backend for Spring Boot and Microservices CLI (*oractl*) **deploy** command? When you run the **deploy** command, the Oracle Backend for Spring Boot and Microservices CLI does several things for you:
+    > What happens when you use the Oracle Backend for Microservices and AI CLI (*oractl*) **deploy** command? When you run the **deploy** command, the Oracle Backend for Microservices and AI CLI does several things for you:
 
     * Uploads the JAR file to server side
     * Builds a container image and push it to the OCI Registry

docs-source/cloudbank/content/account/expose.md

@@ -91,5 +91,5 @@ Now that the account service is deployed, you need to expose it through the API
     }
     ```
 
-    Your service is deployed in the Oracle Backend for Spring Boot and Microservices environment and using the Oracle Autonomous Database instance associated with the backend.
+    Your service is deployed in the Oracle Backend for Microservices and AI environment and using the Oracle Autonomous Database instance associated with the backend.
 

docs-source/cloudbank/content/account/images/obaas-spring-init-2.png

@@ -20,7 +20,7 @@ In this lab, you will:
 * Prepare objects in the Oracle Database using SQLcl
 * Use Spring Data JPA to allow your microservice to use the data in the Oracle database
 * Create REST services to allow clients to perform create, read, update, and delete operations on accounts
-* Deploy your microservice into the backend (Oracle Backend for Spring Boot and Microservices)
+* Deploy your microservice into the backend (Oracle Backend for Microservices and AI)
 
 ### Prerequisites (Optional)
 

docs-source/cloudbank/content/account/intro.md

@@ -5,11 +5,11 @@ weight = 4
 +++
 
 
-Oracle Backend for Spring Boot and Microservices includes Spring Admin which provides a web user interface for managing and monitoring Spring applications.
+Oracle Backend for Microservices and AI includes Spring Admin which provides a web user interface for managing and monitoring Spring applications.
 
 1. Connect to Spring Admin
 
-   Oracle Backend for Spring Boot and Microservices does not expose management interfaces outside the Kubernetes cluster for improved security.  Oracle recommends you access these interfaces using **kubectl** port forwarding, which creates an encrypted tunnel from your client machine to the cluster to access a specific service in the cluster.
+   Oracle Backend for Microservices and AI does not expose management interfaces outside the Kubernetes cluster for improved security.  Oracle recommends you access these interfaces using **kubectl** port forwarding, which creates an encrypted tunnel from your client machine to the cluster to access a specific service in the cluster.
 
    Open a tunnel to the Spring Admin server using this command:
 

docs-source/cloudbank/content/backend/admin.md

@@ -4,7 +4,7 @@ title = "Explore APISIX API Gateway"
 weight = 6
 +++
 
-Oracle Backend for Spring Boot and Microservices includes APISIX API Gateway to manage which services are made available outside the Kubernetes cluster.  APISIX allows you to manage many aspects of the services' APIs including authentication, logging, which HTTP methods are accepted, what URL paths are exposed, and also includes capabilities like rewriting, filtering, traffic management and has a rich plugin ecosystem to enhance it with additional capabilities.  You can manage the APISIX API Gateway using the APISIX Dashboard.
+Oracle Backend for Microservices and AI includes APISIX API Gateway to manage which services are made available outside the Kubernetes cluster.  APISIX allows you to manage many aspects of the services' APIs including authentication, logging, which HTTP methods are accepted, what URL paths are exposed, and also includes capabilities like rewriting, filtering, traffic management and has a rich plugin ecosystem to enhance it with additional capabilities.  You can manage the APISIX API Gateway using the APISIX Dashboard.
 
 1. Access the APISIX Dashboard