From ef8042463c898db26e57293587044da2039a4924 Mon Sep 17 00:00:00 2001 From: Mark Nelson Date: Fri, 30 Aug 2024 15:47:30 -0400 Subject: [PATCH] publish cb4 updates (#927) Signed-off-by: Mark Nelson --- cloudbank/404.html | 26 +-- cloudbank/account/cr-accounts/index.html | 44 ++--- cloudbank/account/create-project/index.html | 92 +++++----- cloudbank/account/deploy/index.html | 68 +++---- cloudbank/account/expose/index.html | 64 +++---- cloudbank/account/extra-endpoints/index.html | 44 ++--- cloudbank/account/first-service/index.html | 44 ++--- cloudbank/account/index.html | 44 ++--- cloudbank/account/intro/index.html | 44 ++--- cloudbank/account/jpa/index.html | 52 +++--- cloudbank/account/prepare-database/index.html | 44 ++--- cloudbank/backend/admin/index.html | 56 +++--- cloudbank/backend/apisix/index.html | 60 +++---- cloudbank/backend/config/index.html | 48 ++--- cloudbank/backend/database/index.html | 68 +++---- cloudbank/backend/eureka/index.html | 48 ++--- cloudbank/backend/grafana/index.html | 60 +++---- cloudbank/backend/index.html | 44 ++--- cloudbank/backend/intro/index.html | 44 ++--- cloudbank/backend/jaeger/index.html | 56 +++--- cloudbank/backend/k8s/index.html | 44 ++--- cloudbank/categories/index.html | 44 ++--- cloudbank/check/check-processing/index.html | 92 +++++----- cloudbank/check/create-queues/index.html | 44 ++--- cloudbank/check/create-testrunner/index.html | 92 +++++----- cloudbank/check/index.html | 44 ++--- cloudbank/check/intro/index.html | 44 ++--- cloudbank/check/learn/index.html | 56 +++--- cloudbank/check/test/index.html | 44 ++--- cloudbank/check/update-account/index.html | 44 ++--- cloudbank/cleanup/index.html | 44 ++--- cloudbank/cleanup/intro/index.html | 44 ++--- .../cleanup/uninstall-free-trial/index.html | 76 ++++---- cloudbank/cleanup/uninstall-local/index.html | 44 ++--- cloudbank/cleanup/uninstall-mp/index.html | 64 +++---- cloudbank/css/format-print.css | 4 +- cloudbank/css/print.css | 2 +- cloudbank/css/swagger.css | 4 +- cloudbank/css/variant.css | 2 +- cloudbank/deploy-cli/build/index.html | 44 ++--- cloudbank/deploy-cli/create-routes/index.html | 56 +++--- cloudbank/deploy-cli/deploy/index.html | 44 ++--- cloudbank/deploy-cli/get-code/index.html | 44 ++--- cloudbank/deploy-cli/index.html | 44 ++--- cloudbank/deploy-cli/intro/index.html | 44 ++--- cloudbank/deploy-cli/verify/index.html | 44 ++--- cloudbank/deploy-ide/build/index.html | 44 ++--- cloudbank/deploy-ide/get-code/index.html | 44 ++--- cloudbank/deploy-ide/index.html | 44 ++--- cloudbank/deploy-ide/intro/index.html | 44 ++--- cloudbank/deploy-ide/using-vscode/index.html | 168 +++++++++--------- cloudbank/devenv/db-access/index.html | 68 +++---- cloudbank/devenv/ide-plugin/index.html | 60 +++---- cloudbank/devenv/ide/index.html | 52 +++--- cloudbank/devenv/index.html | 44 ++--- cloudbank/devenv/intro/index.html | 44 ++--- cloudbank/devenv/jdk/index.html | 44 ++--- cloudbank/devenv/kubectl-config/index.html | 44 ++--- cloudbank/devenv/kubectl/index.html | 44 ++--- cloudbank/devenv/maven/index.html | 44 ++--- cloudbank/devenv/oractl/index.html | 44 ++--- cloudbank/devenv/sqlcl/index.html | 44 ++--- cloudbank/index.html | 44 ++--- cloudbank/index.search.js | 12 +- cloudbank/more/credits/index.html | 44 ++--- cloudbank/provision/index.html | 44 ++--- cloudbank/provision/index.xml | 4 +- .../provision/install-free-trial/index.html | 79 ++++---- cloudbank/provision/install-local/index.html | 64 +++---- cloudbank/provision/install-mp/index.html | 125 ++++++------- cloudbank/provision/intro/index.html | 57 +++--- cloudbank/saga/business-logic/index.html | 44 ++--- cloudbank/saga/dao/index.html | 44 ++--- cloudbank/saga/deploy/index.html | 44 ++--- cloudbank/saga/deposit/index.html | 92 +++++----- cloudbank/saga/index.html | 44 ++--- cloudbank/saga/intro/index.html | 44 ++--- cloudbank/saga/learn-lra/index.html | 48 ++--- cloudbank/saga/learn/index.html | 44 ++--- cloudbank/saga/prepare/index.html | 44 ++--- cloudbank/saga/test/index.html | 44 ++--- cloudbank/saga/transfer-service/index.html | 92 +++++----- cloudbank/saga/withdraw-service/index.html | 44 ++--- cloudbank/springai/index.html | 50 +++--- cloudbank/tags/index.html | 44 ++--- 85 files changed, 2128 insertions(+), 2145 deletions(-) diff --git a/cloudbank/404.html b/cloudbank/404.html index 14d5ea6e8..556f2e7ea 100644 --- a/cloudbank/404.html +++ b/cloudbank/404.html @@ -17,24 +17,24 @@ 404 Page not found :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/account/create-project/index.html b/cloudbank/account/create-project/index.html index f94956dd6..c7670f83f 100644 --- a/cloudbank/account/create-project/index.html +++ b/cloudbank/account/create-project/index.html @@ -29,24 +29,24 @@ In Visual Studio Code, press Ctrl+Shift+P (Cmd+Shift+P on a Mac) to access the command window. Start typing “Spring Init” and you will see a number of options to create a Spring project, as shown in the image below."> Create Project :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/account/deploy/index.html b/cloudbank/account/deploy/index.html index 8bfe840f8..6ceca6974 100644 --- a/cloudbank/account/deploy/index.html +++ b/cloudbank/account/deploy/index.html @@ -33,24 +33,24 @@ When you deploy the application to the backend, you want it to register with the Eureka Service Registry so that it can be discovered by other services including the APISIX API Gateway, so that we can easily expose it outside the cluster."> Deploy Account Service :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/account/expose/index.html b/cloudbank/account/expose/index.html index caa930eb8..e2f007806 100644 --- a/cloudbank/account/expose/index.html +++ b/cloudbank/account/expose/index.html @@ -33,24 +33,24 @@ $ kubectl get secret -n apisix apisix-dashboard -o jsonpath='{.data.conf\.yaml}' | base64 -d | grep 'password:' Access the APISIX Dashboard"> Expose using APISIX :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/account/extra-endpoints/index.html b/cloudbank/account/extra-endpoints/index.html index 1ca02388a..bf820d88e 100644 --- a/cloudbank/account/extra-endpoints/index.html +++ b/cloudbank/account/extra-endpoints/index.html @@ -29,24 +29,24 @@ Add a new method to your AccountController.java class that responds to the HTTP GET method. This method should accept a customer ID as a path variable and return a list of accounts for that customer ID. If no accounts are found, return an empty body and set the HTTP Status Code to 204 (No Content)."> Extra Account Endpoints :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/account/first-service/index.html b/cloudbank/account/first-service/index.html index 52b75ff67..d3352a040 100644 --- a/cloudbank/account/first-service/index.html +++ b/cloudbank/account/first-service/index.html @@ -33,24 +33,24 @@ package com.example.accounts.controller; public class AccountController { } Add the RestController annotation Add the RestController annotation to this class to tell Spring Boot that we want this class to expose REST services."> Implement First Service :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/account/index.html b/cloudbank/account/index.html index 05bcfc71e..6192bec30 100644 --- a/cloudbank/account/index.html +++ b/cloudbank/account/index.html @@ -21,24 +21,24 @@ Account Microservice :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/account/intro/index.html b/cloudbank/account/intro/index.html index fd1fe0981..1ac4fb3a3 100644 --- a/cloudbank/account/intro/index.html +++ b/cloudbank/account/intro/index.html @@ -33,24 +33,24 @@ Objectives In this lab, you will:"> Introduction :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/account/jpa/index.html b/cloudbank/account/jpa/index.html index b62c8deae..31fbd7e9b 100644 --- a/cloudbank/account/jpa/index.html +++ b/cloudbank/account/jpa/index.html @@ -25,24 +25,24 @@ To add Spring Data JPA and the Oracle Database drivers to your project, open the Maven POM (pom."> Use Spring Data JPA :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/account/prepare-database/index.html b/cloudbank/account/prepare-database/index.html index 359d20168..e5c9dce75 100644 --- a/cloudbank/account/prepare-database/index.html +++ b/cloudbank/account/prepare-database/index.html @@ -29,24 +29,24 @@ $ kubectl -n application get secret DBNAME-db-secrets -o jsonpath='{.data.db\.password}' | base64 -dIf you don’t know the name of the database, execute the following command and look for the line DBNAME-db-secrets."> Prepare Database Objects :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/backend/admin/index.html b/cloudbank/backend/admin/index.html index 4c286e62e..9309670a8 100644 --- a/cloudbank/backend/admin/index.html +++ b/cloudbank/backend/admin/index.html @@ -29,24 +29,24 @@ 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."> Explore Spring Admin :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/backend/apisix/index.html b/cloudbank/backend/apisix/index.html index 3defaa49b..eecaf54a3 100644 --- a/cloudbank/backend/apisix/index.html +++ b/cloudbank/backend/apisix/index.html @@ -21,24 +21,24 @@ Explore APISIX API Gateway :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/backend/config/index.html b/cloudbank/backend/config/index.html index 186806fc5..de436f77a 100644 --- a/cloudbank/backend/config/index.html +++ b/cloudbank/backend/config/index.html @@ -21,24 +21,24 @@ Explore Spring Config Server :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/backend/database/index.html b/cloudbank/backend/database/index.html index 3a956942d..1756bf517 100644 --- a/cloudbank/backend/database/index.html +++ b/cloudbank/backend/database/index.html @@ -29,24 +29,24 @@ In the OCI Console, in the main (“hamburger”) menu navigate to the Oracle Database category and then Oracle Autonomous Database. Make sure you have the correct region selected (in the top right corner) and the compartment where you installed Oracle Backend for Spring Boot and Microservices (on the left hand side pull down list)."> Explore Oracle Autonomous Database :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/backend/eureka/index.html b/cloudbank/backend/eureka/index.html index cd544130f..edba3521a 100644 --- a/cloudbank/backend/eureka/index.html +++ b/cloudbank/backend/eureka/index.html @@ -21,24 +21,24 @@ Explore Eureka Service Registry :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/backend/grafana/index.html b/cloudbank/backend/grafana/index.html index 20b8f19f9..1bbcda25e 100644 --- a/cloudbank/backend/grafana/index.html +++ b/cloudbank/backend/grafana/index.html @@ -33,24 +33,24 @@ $ kubectl -n grafana get secret grafana -o jsonpath='{.data.admin-password}' | base64 -d fusHDM7xdwJXyUM2bLmydmN1V6b3IyPVRUxDtqu7Start the tunnel using this command."> Explore Grafana :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/backend/index.html b/cloudbank/backend/index.html index 9abceb7aa..54fbdb0ab 100644 --- a/cloudbank/backend/index.html +++ b/cloudbank/backend/index.html @@ -21,24 +21,24 @@ Explore the Backend :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/backend/intro/index.html b/cloudbank/backend/intro/index.html index 74f510bc0..983894811 100644 --- a/cloudbank/backend/intro/index.html +++ b/cloudbank/backend/intro/index.html @@ -37,24 +37,24 @@ Review the components of the Oracle Backend for Spring Boot and Microservices Explore how microservice data is stored in the Oracle Autonomous Database Learn about the Spring Admin user interface Learn about Spring Eureka Service Registry Learn about APISIX API Gateway Learn about Spring Config Server Learn about the observability tools included in Oracle Backend for Spring Boot and Microservices Learn about the tracing tools included in Oracle Backend for Spring Boot and Microservices Prerequisites This module assumes you have:"> Introduction :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/backend/jaeger/index.html b/cloudbank/backend/jaeger/index.html index 5be13d232..e1db65826 100644 --- a/cloudbank/backend/jaeger/index.html +++ b/cloudbank/backend/jaeger/index.html @@ -33,24 +33,24 @@ $ kubectl -n observability port-forward svc/jaegertracing-query 16686Open a web browser to http://localhost:16686 to view the Jaeger web user interface."> Explore Jaeger :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/backend/k8s/index.html b/cloudbank/backend/k8s/index.html index bb5d47878..03d80c8f7 100644 --- a/cloudbank/backend/k8s/index.html +++ b/cloudbank/backend/k8s/index.html @@ -29,24 +29,24 @@ Kubernetes resources are grouped into namespaces. To see a list of the namespaces in your cluster, use this command, your output will be slightly different:"> Explore Kubernetes :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/categories/index.html b/cloudbank/categories/index.html index bf50b346d..c2b90c13c 100644 --- a/cloudbank/categories/index.html +++ b/cloudbank/categories/index.html @@ -17,24 +17,24 @@ Categories :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/check/check-processing/index.html b/cloudbank/check/check-processing/index.html index 85944824a..6c6d628a2 100644 --- a/cloudbank/check/check-processing/index.html +++ b/cloudbank/check/check-processing/index.html @@ -25,24 +25,24 @@ Create a new Java Project for the checks service. In the Explorer of VS Code open Java Project and click the plus sign to add a Java Project to your workspace."> Create the Check Processing Microservice :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/check/create-queues/index.html b/cloudbank/check/create-queues/index.html index 5bde6390a..c4aefca31 100644 --- a/cloudbank/check/create-queues/index.html +++ b/cloudbank/check/create-queues/index.html @@ -25,24 +25,24 @@ ```sql grant execute on dbms_aq to account; grant execute on dbms_aqadm to account; grant execute on dbms_aqin to account; commit; ``` Now connect as the account user and create the queues by executing these statements (replace [TNS-ENTRY] with your environment information)."> Create Queues in the Database :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/check/create-testrunner/index.html b/cloudbank/check/create-testrunner/index.html index 76308d613..7b3d9967b 100644 --- a/cloudbank/check/create-testrunner/index.html +++ b/cloudbank/check/create-testrunner/index.html @@ -37,24 +37,24 @@ Specify 3."> Create the Test Runner Microservice :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/check/index.html b/cloudbank/check/index.html index 382a44af5..04134c65a 100644 --- a/cloudbank/check/index.html +++ b/cloudbank/check/index.html @@ -21,24 +21,24 @@ Check Processing :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/check/intro/index.html b/cloudbank/check/intro/index.html index 8fccb33fd..49f9f9868 100644 --- a/cloudbank/check/intro/index.html +++ b/cloudbank/check/intro/index.html @@ -21,24 +21,24 @@ Introduction :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/check/learn/index.html b/cloudbank/check/learn/index.html index d93a7bf96..81b8cda1c 100644 --- a/cloudbank/check/learn/index.html +++ b/cloudbank/check/learn/index.html @@ -25,24 +25,24 @@ In this lab, we will assume that customers can deposit a check at an Automated Teller Machine (ATM) by typing in the check amount, placing the check into a deposit envelope and then inserting that envelope into the ATM."> Learn about the scenario :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/check/test/index.html b/cloudbank/check/test/index.html index 912abb8ae..c7912f81b 100644 --- a/cloudbank/check/test/index.html +++ b/cloudbank/check/test/index.html @@ -33,24 +33,24 @@ ```shell $ curl -i -X POST -H 'Content-Type: application/json' -d '{"accountId": 2, "amount": 256}' http://localhost:8084/api/v1/testrunner/deposit HTTP/1."> Test the end-to-end flow :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/check/update-account/index.html b/cloudbank/check/update-account/index.html index df8aba2f8..7ac830705 100644 --- a/cloudbank/check/update-account/index.html +++ b/cloudbank/check/update-account/index.html @@ -25,24 +25,24 @@ Create the Journal model Create a new Java file in src/main/java/com/example/accounts/model called Journal.java. In this class you can define the fields that make up the journal. Note that you created the Journal table in the previous lab. You will not use the lraId and lraState fields until a later lab."> Add Journal to the Account service :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/cleanup/index.html b/cloudbank/cleanup/index.html index c80ceb15e..6ac8d664b 100644 --- a/cloudbank/cleanup/index.html +++ b/cloudbank/cleanup/index.html @@ -21,24 +21,24 @@ Cleanup :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/cleanup/intro/index.html b/cloudbank/cleanup/intro/index.html index 0347cdb26..51c379c15 100644 --- a/cloudbank/cleanup/intro/index.html +++ b/cloudbank/cleanup/intro/index.html @@ -37,24 +37,24 @@ Clean up your instance of the Oracle Backend for Spring Boot and Microservices and other resources you created during this Live module Prerequisites This module assumes you have:"> Introduction :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/cleanup/uninstall-free-trial/index.html b/cloudbank/cleanup/uninstall-free-trial/index.html index b2e61a2f9..e87004cb0 100644 --- a/cloudbank/cleanup/uninstall-free-trial/index.html +++ b/cloudbank/cleanup/uninstall-free-trial/index.html @@ -37,24 +37,24 @@ Navigate to the Compute Instances page by clicking on the link on the home page of the OCI Console or opening the main menu using the “hamburger” icon ( ) in the top left corner of the console and searching for “instance”:"> OCI Free Tier Cleanup :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/cleanup/uninstall-local/index.html b/cloudbank/cleanup/uninstall-local/index.html index 5a9172749..9d8abe656 100644 --- a/cloudbank/cleanup/uninstall-local/index.html +++ b/cloudbank/cleanup/uninstall-local/index.html @@ -37,24 +37,24 @@ docker rm obaas "> Local cleanup :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/cleanup/uninstall-mp/index.html b/cloudbank/cleanup/uninstall-mp/index.html index 7b5fc1b8b..b54ab5923 100644 --- a/cloudbank/cleanup/uninstall-mp/index.html +++ b/cloudbank/cleanup/uninstall-mp/index.html @@ -33,24 +33,24 @@ Make sure you choose the Compartment where you installed Oracle Backend for Spring Boot and Microservices. Click on the Stack Name (which will be different from the screenshot)"> OCI Marketplace Uninstall :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/css/format-print.css b/cloudbank/css/format-print.css index e8b125d2c..9eca6359f 100644 --- a/cloudbank/css/format-print.css +++ b/cloudbank/css/format-print.css @@ -1,5 +1,5 @@ -@import "theme-relearn-light.css?1724866676"; -@import "chroma-relearn-light.css?1724866676"; +@import "theme-relearn-light.css?1725045071"; +@import "chroma-relearn-light.css?1725045071"; #R-sidebar { display: none; diff --git a/cloudbank/css/print.css b/cloudbank/css/print.css index b2d5daf8e..8918ede29 100644 --- a/cloudbank/css/print.css +++ b/cloudbank/css/print.css @@ -1 +1 @@ -@import "format-print.css?1724866676"; +@import "format-print.css?1725045071"; diff --git a/cloudbank/css/swagger.css b/cloudbank/css/swagger.css index 335a3c99b..b5c0654ad 100644 --- a/cloudbank/css/swagger.css +++ b/cloudbank/css/swagger.css @@ -1,7 +1,7 @@ /* Styles to make Swagger-UI fit into our theme */ -@import "fonts.css?1724866676"; -@import "variables.css?1724866676"; +@import "fonts.css?1725045071"; +@import "variables.css?1725045071"; body{ line-height: 1.574; diff --git a/cloudbank/css/variant.css b/cloudbank/css/variant.css index f9db38227..ca9e4ad85 100644 --- a/cloudbank/css/variant.css +++ b/cloudbank/css/variant.css @@ -1,4 +1,4 @@ -@import "variables.css?1724866676"; +@import "variables.css?1725045071"; html { color-scheme: only var(--INTERNAL-BROWSER-theme); diff --git a/cloudbank/deploy-cli/build/index.html b/cloudbank/deploy-cli/build/index.html index dbf865276..2a4ecdfa9 100644 --- a/cloudbank/deploy-cli/build/index.html +++ b/cloudbank/deploy-cli/build/index.html @@ -33,24 +33,24 @@ [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary for CloudBank 0.0.1-SNAPSHOT: [INFO] [INFO] CloudBank .......................................... SUCCESS [ 0.916 s] [INFO] account ............................................ SUCCESS [ 2.900 s] [INFO] checks ............................................. SUCCESS [ 1.127 s] [INFO] customer ........................................... SUCCESS [ 1.106 s] [INFO] creditscore ."> Build CloudBank :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/deploy-cli/create-routes/index.html b/cloudbank/deploy-cli/create-routes/index.html index cbbd3e7ef..5f8cdb607 100644 --- a/cloudbank/deploy-cli/create-routes/index.html +++ b/cloudbank/deploy-cli/create-routes/index.html @@ -33,24 +33,24 @@ kubectl -n apisix get configmap apisix -o yamlLook for the key: information in the admin_key section and save it."> Create APISIX routes :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/deploy-cli/deploy/index.html b/cloudbank/deploy-cli/deploy/index.html index 70aaaa388..2bc53c69a 100644 --- a/cloudbank/deploy-cli/deploy/index.html +++ b/cloudbank/deploy-cli/deploy/index.html @@ -37,24 +37,24 @@ Start a tunnel using this command:"> Deploy CloudBank :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/deploy-cli/get-code/index.html b/cloudbank/deploy-cli/get-code/index.html index cd85ae825..13975dda8 100644 --- a/cloudbank/deploy-cli/get-code/index.html +++ b/cloudbank/deploy-cli/get-code/index.html @@ -37,24 +37,24 @@ The source code for the CloudBank application will be in the microservices-datadriven directory you just created, in the cloudbank-v32 subdirectory."> Get the sample code :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/deploy-cli/index.html b/cloudbank/deploy-cli/index.html index 7dd1bc1b3..98711c843 100644 --- a/cloudbank/deploy-cli/index.html +++ b/cloudbank/deploy-cli/index.html @@ -21,24 +21,24 @@ Deploy with the CLI :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/deploy-cli/intro/index.html b/cloudbank/deploy-cli/intro/index.html index 50d045e41..18b7874bf 100644 --- a/cloudbank/deploy-cli/intro/index.html +++ b/cloudbank/deploy-cli/intro/index.html @@ -21,24 +21,24 @@ Introduction :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/deploy-cli/verify/index.html b/cloudbank/deploy-cli/verify/index.html index c3ba806cd..8733c2898 100644 --- a/cloudbank/deploy-cli/verify/index.html +++ b/cloudbank/deploy-cli/verify/index.html @@ -33,24 +33,24 @@ NAME READY STATUS RESTARTS AGE account-65cdc68dd7-k5ntz 1/1 Running 0 8m2s checks-78c988bdcf-n59qz 1/1 Running 0 42m creditscore-7b89d567cd-nm4p6 1/1 Running 0 38m customer-6f4dc67985-nf5kz 1/1 Running 0 41s testrunner-78d679575f-ch4k7 1/1 Running 0 33m transfer-869d796755-gn9lf 1/1 Running 0 27m Verify the all the Cloud Bank services deployed"> Verify the deployment :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/deploy-ide/build/index.html b/cloudbank/deploy-ide/build/index.html index 69a0d6498..9bd47bfd1 100644 --- a/cloudbank/deploy-ide/build/index.html +++ b/cloudbank/deploy-ide/build/index.html @@ -33,24 +33,24 @@ [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary for cloudbank 0.0.1-SNAPSHOT: [INFO] [INFO] cloudbank .......................................... SUCCESS [ 0.972 s] [INFO] account ............................................ SUCCESS [ 2.877 s] [INFO] customer ........................................... SUCCESS [ 1.064 s] [INFO] creditscore ........................................ SUCCESS [ 0.922 s] [INFO] transfer ."> Build CloudBank :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/deploy-ide/get-code/index.html b/cloudbank/deploy-ide/get-code/index.html index 238067934..b8b1388be 100644 --- a/cloudbank/deploy-ide/get-code/index.html +++ b/cloudbank/deploy-ide/get-code/index.html @@ -37,24 +37,24 @@ The source code for the CloudBank application will be in the microservices-datadriven directory you just created, in the cloudbank-v32 subdirectory."> Get the sample code :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/deploy-ide/index.html b/cloudbank/deploy-ide/index.html index e9788cd82..cbb6f992c 100644 --- a/cloudbank/deploy-ide/index.html +++ b/cloudbank/deploy-ide/index.html @@ -21,24 +21,24 @@ Deploy with an IDE :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/deploy-ide/intro/index.html b/cloudbank/deploy-ide/intro/index.html index 07d6be900..614d807e9 100644 --- a/cloudbank/deploy-ide/intro/index.html +++ b/cloudbank/deploy-ide/intro/index.html @@ -25,24 +25,24 @@ If you already have completed the module Deploy the full CloudBank Application using the CLI You can skip Task 1 and Task 2."> Introduction :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/deploy-ide/using-vscode/index.html b/cloudbank/deploy-ide/using-vscode/index.html index 6cfbeb5da..c5c79ee41 100644 --- a/cloudbank/deploy-ide/using-vscode/index.html +++ b/cloudbank/deploy-ide/using-vscode/index.html @@ -29,24 +29,24 @@ The Oracle Backend fo Spring Boot and Microservices VS Code plugin will ask to specify the Kubernetes config file full path as shown here:"> Using the VS Code plugin :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/devenv/db-access/index.html b/cloudbank/devenv/db-access/index.html index 10dc7fcc3..4e9ec2e1c 100644 --- a/cloudbank/devenv/db-access/index.html +++ b/cloudbank/devenv/db-access/index.html @@ -37,24 +37,24 @@ Make sure that you have the right compartment selected and click on the database name."> Database Access :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/devenv/ide-plugin/index.html b/cloudbank/devenv/ide-plugin/index.html index c45b0cdd2..9d1ee993f 100644 --- a/cloudbank/devenv/ide-plugin/index.html +++ b/cloudbank/devenv/ide-plugin/index.html @@ -21,24 +21,24 @@ Install IDE Plugin :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/devenv/ide/index.html b/cloudbank/devenv/ide/index.html index be237f4ee..e6d478877 100644 --- a/cloudbank/devenv/ide/index.html +++ b/cloudbank/devenv/ide/index.html @@ -25,24 +25,24 @@ Spring Boot Extension Pack Extension Pack for Java Oracle Developer Tools Note: It is possible to use other Integrated Development Environments however all the instructions in this Livemoduleare written for and tested with Visual Studio Code, so we recommend that you use it for this Live Lab."> Install IDE :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/devenv/index.html b/cloudbank/devenv/index.html index f8ace1089..5ace0a863 100644 --- a/cloudbank/devenv/index.html +++ b/cloudbank/devenv/index.html @@ -21,24 +21,24 @@ Developer Environment :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/devenv/intro/index.html b/cloudbank/devenv/intro/index.html index 917efe31b..d63713dc4 100644 --- a/cloudbank/devenv/intro/index.html +++ b/cloudbank/devenv/intro/index.html @@ -33,24 +33,24 @@ Windows 10 or 11, preferably with Windows Subsystem for Linux 2 macOS (11 or later recommended) on Intel or Apple silicon Linux, e.g., Oracle Linux, Ubuntu, etc. The following tools are recommended for a development environment:"> Introduction :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/devenv/jdk/index.html b/cloudbank/devenv/jdk/index.html index 2ccc79aaa..72d828cb0 100644 --- a/cloudbank/devenv/jdk/index.html +++ b/cloudbank/devenv/jdk/index.html @@ -37,24 +37,24 @@ export JAVA_HOME=$HOME/jdk-21.0.3 export PATH=$JAVA_HOME/bin:$PATH Verify the installation"> Install JDK :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/devenv/kubectl-config/index.html b/cloudbank/devenv/kubectl-config/index.html index 3bb8ddc9d..fc53f891d 100644 --- a/cloudbank/devenv/kubectl-config/index.html +++ b/cloudbank/devenv/kubectl-config/index.html @@ -21,24 +21,24 @@ Configure Kubectl :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/devenv/kubectl/index.html b/cloudbank/devenv/kubectl/index.html index 25368a02e..e8bae04d1 100644 --- a/cloudbank/devenv/kubectl/index.html +++ b/cloudbank/devenv/kubectl/index.html @@ -29,24 +29,24 @@ Install kubectl from the Kubernetes website."> Install Kubectl and OCI CLI :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/devenv/maven/index.html b/cloudbank/devenv/maven/index.html index 901ca4e5e..51a44a553 100644 --- a/cloudbank/devenv/maven/index.html +++ b/cloudbank/devenv/maven/index.html @@ -37,24 +37,24 @@ Decompress the archive in your chosen location, e.g., your home directory and then add it to your path (the exact version of maven might differ in your environment):"> Install Maven :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/devenv/oractl/index.html b/cloudbank/devenv/oractl/index.html index 7d5c678e1..7a3784ae0 100644 --- a/cloudbank/devenv/oractl/index.html +++ b/cloudbank/devenv/oractl/index.html @@ -37,24 +37,24 @@ To install the CLI, you just need to make sure it is executable and add it to your PATH environment variable."> Install CLI :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/devenv/sqlcl/index.html b/cloudbank/devenv/sqlcl/index.html index 2ebf6e95d..1caa20741 100644 --- a/cloudbank/devenv/sqlcl/index.html +++ b/cloudbank/devenv/sqlcl/index.html @@ -33,24 +33,24 @@ export PATH=/path/to/sqlcl:$PATH "> Install SQLcl :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/index.html b/cloudbank/index.html index 86f6cd7e9..9966bcb1e 100644 --- a/cloudbank/index.html +++ b/cloudbank/index.html @@ -29,24 +29,24 @@ CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/index.search.js b/cloudbank/index.search.js index 073f7ec40..075472f66 100644 --- a/cloudbank/index.search.js +++ b/cloudbank/index.search.js @@ -57,7 +57,7 @@ var relearn_search_index = [ }, { "breadcrumb": "CloudBank \u003e Provision an Instance", - "content": "This module walks you through the steps to provision an instance of the Oracle Backend for Spring Boot and Microservices.\nEstimated Time: 30 minutes\nAbout Oracle Backend for Spring Boot and Microservices Oracle Backend for Spring Boot and Microservices allows developers to build microservices in Spring Boot and provision a backend as a service with the Oracle Database and other infrastructure components that operate on multiple clouds. This service vastly simplifies the task of building, testing, and operating microservices platforms for reliable, secure, and scalable enterprise applications.\nThis module provides three options for running the environment:\nLocally 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. In a compute instance in an Oracle Cloud Free Tier account. You can sign up for an Oracle Cloud Free Tier account here. This account will include enough free credits to run CloudBank. In a commercial Oracle Cloud tenancy. If you have a commercial tenancy with sufficient capacity and privileges, you can run the full production-sized installation. This can be installed from the OCI Marketplace using the instructions in Module 1. Check the instructions for a more detailed list of requirements. Regardless of which option you choose, the remainder of the modules will be virtually identical.\nObjectives In this lab, you will:\nProvision an instance of Oracle Backend for Spring Boot and Microservices, either locally or in the cloud. Prerequisites This module assumes you have either:\nAn Oracle Cloud account in a tenancy with sufficient quota and privileges to create: An OCI Container Engine for Kubernetes cluster, plus a node pool with three worker nodes A VCN with at least two public IP’s available A public load balancer An Oracle Autonomous Database - Shared instance At least one free OCI Auth Token (note that the maximum is two per user), or An Oracle Cloud Free Tier account, or A local machine with enough memory (64GB recommneded) to run the environment locally. ", + "content": "This module walks you through the steps to provision an instance of the Oracle Backend for Spring Boot and Microservices.\nEstimated Time: 30 minutes\nAbout Oracle Backend for Spring Boot and Microservices Oracle Backend for Spring Boot and Microservices allows developers to build microservices in Spring Boot and provision a backend as a service with the Oracle Database and other infrastructure components that operate on multiple clouds. This service vastly simplifies the task of building, testing, and operating microservices platforms for reliable, secure, and scalable enterprise applications.\nThis module provides three options for running the environment:\nLocally 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. In a single compute instance in either an Oracle Cloud Free Tier account or any commercial OCI Cloud tenancy. You can sign up for an Oracle Cloud Free Tier account here. This account will include enough free credits to run CloudBank. You can also use this option to run a lightweight, single compute instance environment in any Oracle Cloud tenancy. The full production-sized installation from OCI Marketplace in a commercial Oracle Cloud tenancy. If you have a commercial tenancy with sufficient capacity and privileges, you can run the full production-sized installation. This can be installed from the OCI Marketplace using the instructions in Module 1. Check the instructions for a more detailed list of requirements. Regardless of which option you choose, the remainder of the modules will be virtually identical.\nObjectives In this lab, you will:\nProvision an instance of Oracle Backend for Spring Boot and Microservices, either locally or in the cloud. Prerequisites This module assumes you have either:\nAn Oracle Cloud account in a tenancy with sufficient quota and privileges to create: An OCI Container Engine for Kubernetes cluster, plus a node pool with three worker nodes A VCN with at least two public IP’s available A public load balancer An Oracle Autonomous Database - Shared instance At least one free OCI Auth Token (note that the maximum is two per user), or An Oracle Cloud Free Tier account, or A local machine with enough memory (64GB recommended) to run the environment locally. ", "description": "This module walks you through the steps to provision an instance of the Oracle Backend for Spring Boot and Microservices.\nEstimated Time: 30 minutes\nAbout Oracle Backend for Spring Boot and Microservices Oracle Backend for Spring Boot and Microservices allows developers to build microservices in Spring Boot and provision a backend as a service with the Oracle Database and other infrastructure components that operate on multiple clouds. This service vastly simplifies the task of building, testing, and operating microservices platforms for reliable, secure, and scalable enterprise applications.", "tags": [], "title": "Introduction", @@ -129,8 +129,8 @@ var relearn_search_index = [ }, { "breadcrumb": "CloudBank \u003e Provision an Instance", - "content": "This option allows you to run Oracle Backend for Spring Boot and Microservices in a containerized environment on your local machine. This option is recommended if you do have enough free capacity on your local machine to run the environment, a minimum of 64GB RAM and 80GB free disk are recommneded. This option provides an environment with adequeate resources for development and testing, but is not suitable for a production-sized deployment or performance testing.\nNote: You only need to choose one of the three deployment options - local, OCI Free Tier or OCI Marketplace.\nPrerequisites\nThe following prerequisites are required to run the local environment:\nA container runtime environment such as Docker Desktop, Rancher Desktop or Podman Desktop. The ability to run a BASH script, or to read one and run equivalent commands in your environment. 64GB RAM and 80GB free disk space. Download the required files\nIf you have not already done so, clone the Microservices Data-Driven GitHub repository:\ngit clone https://github.com/oracle/microservices-datadriven Change into the directory with the local environment files:\ncd microservices-datadriven/cloudbank-v4/local-environment Start the environment\nRun the provided script to start the environment, including a Kubernetes cluster in a container (using k3s), Oracle Backend for Spring Boot and Microservices and an Oracle Database instance inside that cluster.\n./obaas.sh It will take approximately six to ten minutes (depending on the size of your machine) for all of the containers to reach ready/running state. You can watch the progress using this command:\nwatch KUBECONFIG=$(pwd)/k3s_data/kubeconfig/kubeconfig.yaml kubectl get pod -A Note: You will need to provide the KUBECONFIG variable as shown, or export it in your shell, each time you wish to run a kubectl command to access the cluster.\nWhen the environment is fully started, the output will appear similar to this:\nVerify access to web user interfaces\nOn your local machine, open a browser and navigate to the Spring Operations Center.\nLog in using the pre-defined user obaas-admin and password Welcome-12345.\nNote: Since this is a development environment with no DNS name, it is configured with self-signed certificates. Your browser will warn you about the connection security.\nIf you are using Chrome, click on the Advanced link and then the Proceed to localhost (unsafe) link. If you are using a different browser, perform the equivalent actions.\nThe Spring Operations Center main dashboard will appear similar to this:", - "description": "This option allows you to run Oracle Backend for Spring Boot and Microservices in a containerized environment on your local machine. This option is recommended if you do have enough free capacity on your local machine to run the environment, a minimum of 64GB RAM and 80GB free disk are recommneded. This option provides an environment with adequeate resources for development and testing, but is not suitable for a production-sized deployment or performance testing.", + "content": "This option allows you to run Oracle Backend for Spring Boot and Microservices in a containerized environment on your local machine. This option is recommended if you do have enough free capacity on your local machine to run the environment, a minimum of 64GB RAM and 80GB free disk are recommended. This option provides an environment with adequate resources for development and testing, but is not suitable for a production-sized deployment or performance testing.\nNote: You only need to choose one of the three deployment options - local, OCI Free Tier or OCI Marketplace.\nPrerequisites\nThe following prerequisites are required to run the local environment:\nA container runtime environment such as Docker Desktop, Rancher Desktop or Podman Desktop. The ability to run a BASH script, or to read one and run equivalent commands in your environment. 64GB RAM and 80GB free disk space. Download the required files\nIf you have not already done so, clone the Microservices Data-Driven GitHub repository:\ngit clone https://github.com/oracle/microservices-datadriven Change into the directory with the local environment files:\ncd microservices-datadriven/cloudbank-v4/local-environment Start the environment\nRun the provided script to start the environment, including a Kubernetes cluster in a container (using k3s), Oracle Backend for Spring Boot and Microservices and an Oracle Database instance inside that cluster.\n./obaas.sh It will take approximately six to ten minutes (depending on the size of your machine) for all of the containers to reach ready/running state. You can watch the progress using this command:\nwatch KUBECONFIG=$(pwd)/k3s_data/kubeconfig/kubeconfig.yaml kubectl get pod -A Note: You will need to provide the KUBECONFIG variable as shown, or export it in your shell, each time you wish to run a kubectl command to access the cluster.\nWhen the environment is fully started, the output will appear similar to this:\nVerify access to web user interfaces\nOn your local machine, open a browser and navigate to the Spring Operations Center.\nLog in using the pre-defined user obaas-admin and password Welcome-12345.\nNote: Since this is a development environment with no DNS name, it is configured with self-signed certificates. Your browser will warn you about the connection security.\nIf you are using Chrome, click on the Advanced link and then the Proceed to localhost (unsafe) link. If you are using a different browser, perform the equivalent actions.\nThe Spring Operations Center main dashboard will appear similar to this:", + "description": "This option allows you to run Oracle Backend for Spring Boot and Microservices in a containerized environment on your local machine. This option is recommended if you do have enough free capacity on your local machine to run the environment, a minimum of 64GB RAM and 80GB free disk are recommended. This option provides an environment with adequate resources for development and testing, but is not suitable for a production-sized deployment or performance testing.", "tags": [], "title": "Install locally", "uri": "/microservices-datadriven/cloudbank/provision/install-local/index.html" @@ -201,7 +201,7 @@ var relearn_search_index = [ }, { "breadcrumb": "CloudBank \u003e Provision an Instance", - "content": "This option allows you to run Oracle Backend for Spring Boot and Microservices in a containerized environment inside a single OCI Compute Instance. This option is good if you do not have enough free capacity on your local machine to run the environment, and if you do not have or want to use the resources required for a full production-sized deployment. This option provides an environment with adequate resources for development and testing, but minimizes the resource usage and costs.\nNote: You only need to choose one of the three deployment options - local, OCI Free Tier or OCI Marketplace.\nGet an Oracle Cloud Free Tier account\nIf you do not already have one, you can obtain an Oracle Cloud Free Tier account as follows:\nOpen a browser and navigate to the Oracle Cloud Free Tier signup page. Complete the requested details and click on the Verify email button. You will receive an email from “Oracle Cloud” with instructions on how to verify your email address. On the Account Information page, enter the requested details. When completed, click on the Start my free trial button. You will need to wait a few minutes while your account is created and set up. When the set up is completed, you will see the login page. You will also receive an email confirmation. Log in to your new account. You may be asked to configured secure verification. Copy the custom compute image\nChoose a compartment in the drop down box on the left hand side of the OCI Console.\nNote: If you use or plan to use this OCI Cloud account for other purposes as well, Oracle recommends creating compartments to simplify management. You can create a compartment by navigating to the Compartments page in the Identity section of OCI Console. You can use the root compartment if you wish, but it is not generally recommended.\nNavigate to the Custom Instances page by opening the main menu using the “hamburger” icon ( ) in the top left corner of the console and searching for “image”:\nClick on the Import image button.\nChoose the option to Import from an Object Storage URL and provide the following URL in the Object Storage URL field:\nhttps://objectstorage.us-ashburn-1.oraclecloud.com/p/oSwRpU_9v5NGzkJ-P0qKzT1ZN-Y9lJZu1aXO_2N-rkGdJs-hKJt10bRk9TxsCceF/n/maacloud/b/cloudbank-public/o/obaas-1.3.0-2 (Important) Under Image type choose the OCI option.\nClick on the Import image button to start the import.\nNote: that it might take approximately 10 to 15 minutes to complete the import. You can see the progress on the Custom image details page that will be displayed.\nCreate a compute instance\nChoose a compartment in the drop down box on the left hand side of the OCI Console.\nNote: If you use or plan to use this OCI Cloud account for other purposes as well, Oracle recommends creating compartments to simplify management. You can create a compartment by navigating to the Compartments page in the Identity section of OCI Console. You can use the root compartment if you wish, but it is not generally recommended.\nNavigate to the Compute Instances page by clicking on the link on the home page of the OCI Console or opening the main menu using the “hamburger” icon ( ) in the top left corner of the console and searching for “instance”:\nCreate a Compute Instance by clicking on the Create instance button.\nEnter a name for the instance, for example obaas-instance.\nScroll down to the Image and shape section and click on the Change Image button to edit the details.\nIn the image source, choose the option for My ../images and choose the image the you imported in the previous step.\nNote: The image will not show up until the import is completed.\nClick on the Select image button to confirm your choice.\nClick on the Change shape button to choose the shape of your instance. Oracle recommends 2 OCPUs and 32 GB of memory to run this CloudBank environment.\nClick on the Select shape button to confirm your choice.\nLeave the default values in the Primary VNIC Section. By doing so a virtual network and subnets will be created for you.\nIn the SSH Keys section, make sure you provide SSH keys so you can log into your instance. You may provide an existing public key if you have one, or generate new keys.\nClick on the Create button to create the instance. The instance and the virtual network will be started, this will take a few moments.\nStart Oracle Backend for Spring Boot and Microservices\nNote the Public IP Address of your newly created instance in the Instance access section of the Instance details page that is displayed.\nLog into the compute instance using SSH, for example:\nssh -i \u003cpath and filename of private key\u003e -L 1443:localhost:443 ubuntu@207.211.186.88 You will need to use the IP address of your instance in this command. Note that the example command also creates a port forward so that you will be able to access various Web UI’s from your local machine.\nYou will be asked to confirm the authenticity of your SSH keys, enter yes.\nThe environment will start automatically, including a Kubernetes cluster in a container (using k3s), Oracle Backend for Spring Boot and Microservices and an Oracle Database instance inside that cluster. It will take approximately six minutes for all of the containers to reach ready/running state. You can watch the progress using this command:\nwatch kubectl get pod -A Note: Should you require access to it, the kubeconfig file for your cluster is located at this location:\n/home/ubuntu/obaas/k3s_data/kubeconfig/kubeconfig.yamlWhen the environment is fully started, the output will appear similar to this:\nVerify access to web user interfaces\nOn your local machine, open a browser and navigate to the Spring Operations Center.\nLog in using the pre-defined user obaas-admin and password Welcome-12345.\nNote: Since this is a development environment with no DNS name, it is configured with self-signed certificates. Your browser will warn you about the connection security.\nIf you are using Chrome, click on the Advanced link and then the Proceed to localhost (unsafe) link. If you are using a different browser, perform the equivalent actions.\nThe Spring Operations Center main dashboard will appear similar to this:", + "content": "This option allows you to run Oracle Backend for Spring Boot and Microservices in a containerized environment inside a single OCI Compute Instance. This option is good if you do not have enough free capacity on your local machine to run the environment, and if you do not have or want to use the resources required for a full production-sized deployment. This option provides an environment with adequate resources for development and testing, but minimizes the resource usage and costs.\nNote: You only need to choose one of the three deployment options - local, OCI Free Tier or OCI Marketplace.\nYou can also use this approach in any regular commercial Oracle Cloud Tenancy - just skip the first step and start at step 2!\nGet an Oracle Cloud Free Tier account\nIf you do not already have one, you can obtain an Oracle Cloud Free Tier account as follows:\nOpen a browser and navigate to the Oracle Cloud Free Tier signup page. Complete the requested details and click on the Verify email button. You will receive an email from “Oracle Cloud” with instructions on how to verify your email address. On the Account Information page, enter the requested details. When completed, click on the Start my free trial button. You will need to wait a few minutes while your account is created and set up. When the set up is completed, you will see the login page. You will also receive an email confirmation. Log in to your new account. You may be asked to configured secure verification. Copy the custom compute image\nChoose a compartment in the drop down box on the left hand side of the OCI Console.\nNote: If you use or plan to use this OCI Cloud account for other purposes as well, Oracle recommends creating compartments to simplify management. You can create a compartment by navigating to the Compartments page in the Identity section of OCI Console. You can use the root compartment if you wish, but it is not generally recommended.\nNavigate to the Custom Instances page by opening the main menu using the “hamburger” icon ( ) in the top left corner of the console and searching for “image”:\nClick on the Import image button.\nChoose the option to Import from an Object Storage URL and provide the following URL in the Object Storage URL field:\nhttps://objectstorage.us-ashburn-1.oraclecloud.com/p/oSwRpU_9v5NGzkJ-P0qKzT1ZN-Y9lJZu1aXO_2N-rkGdJs-hKJt10bRk9TxsCceF/n/maacloud/b/cloudbank-public/o/obaas-1.3.0-2 (Important) Under Image type choose the OCI option.\nClick on the Import image button to start the import.\nNote: that it might take approximately 10 to 15 minutes to complete the import. You can see the progress on the Custom image details page that will be displayed.\nCreate a compute instance\nChoose a compartment in the drop down box on the left hand side of the OCI Console.\nNote: If you use or plan to use this OCI Cloud account for other purposes as well, Oracle recommends creating compartments to simplify management. You can create a compartment by navigating to the Compartments page in the Identity section of OCI Console. You can use the root compartment if you wish, but it is not generally recommended.\nNavigate to the Compute Instances page by clicking on the link on the home page of the OCI Console or opening the main menu using the “hamburger” icon ( ) in the top left corner of the console and searching for “instance”:\nCreate a Compute Instance by clicking on the Create instance button.\nEnter a name for the instance, for example obaas-instance.\nScroll down to the Image and shape section and click on the Change Image button to edit the details.\nIn the image source, choose the option for My ../images and choose the image the you imported in the previous step.\nNote: The image will not show up until the import is completed.\nClick on the Select image button to confirm your choice.\nClick on the Change shape button to choose the shape of your instance. Oracle recommends 2 OCPUs and 32 GB of memory to run this CloudBank environment.\nClick on the Select shape button to confirm your choice.\nLeave the default values in the Primary VNIC Section. By doing so a virtual network and subnets will be created for you.\nIn the SSH Keys section, make sure you provide SSH keys so you can log into your instance. You may provide an existing public key if you have one, or generate new keys.\nClick on the Create button to create the instance. The instance and the virtual network will be started, this will take a few moments.\nStart Oracle Backend for Spring Boot and Microservices\nNote the Public IP Address of your newly created instance in the Instance access section of the Instance details page that is displayed.\nLog into the compute instance using SSH, for example:\nssh -i \u003cpath and filename of private key\u003e -L 1443:localhost:443 ubuntu@207.211.186.88 You will need to use the IP address of your instance in this command. Note that the example command also creates a port forward so that you will be able to access various Web UI’s from your local machine.\nYou will be asked to confirm the authenticity of your SSH keys, enter yes.\nThe environment will start automatically, including a Kubernetes cluster in a container (using k3s), Oracle Backend for Spring Boot and Microservices and an Oracle Database instance inside that cluster. It will take approximately six minutes for all of the containers to reach ready/running state. You can watch the progress using this command:\nwatch kubectl get pod -A Note: Should you require access to it, the kubeconfig file for your cluster is located at this location:\n/home/ubuntu/obaas/k3s_data/kubeconfig/kubeconfig.yamlWhen the environment is fully started, the output will appear similar to this:\nVerify access to web user interfaces\nOn your local machine, open a browser and navigate to the Spring Operations Center.\nLog in using the pre-defined user obaas-admin and password Welcome-12345.\nNote: Since this is a development environment with no DNS name, it is configured with self-signed certificates. Your browser will warn you about the connection security.\nIf you are using Chrome, click on the Advanced link and then the Proceed to localhost (unsafe) link. If you are using a different browser, perform the equivalent actions.\nThe Spring Operations Center main dashboard will appear similar to this:", "description": "This option allows you to run Oracle Backend for Spring Boot and Microservices in a containerized environment inside a single OCI Compute Instance. This option is good if you do not have enough free capacity on your local machine to run the environment, and if you do not have or want to use the resources required for a full production-sized deployment. This option provides an environment with adequate resources for development and testing, but minimizes the resource usage and costs.", "tags": [], "title": "Install in OCI Free Tier", @@ -281,8 +281,8 @@ var relearn_search_index = [ }, { "breadcrumb": "CloudBank \u003e Provision an Instance", - "content": "The Oracle Backend for Spring Boot and Microservices can be installed from OCI Marketplace.\nNote: You only need to choose one of the three deployment options - local, OCI Free Tier or OCI Marketplace.\nAccess the Oracle Cloud Infrastructure Marketplace listing\nOpen the OCI Marketplace listing, as shown in the image below:\nClick on the Get App button.\nLog into your Oracle Cloud Infrastructure account\nYou will be taken to a Sign-In page. Choose they type of account you have and click on the Sign In button. If you did not create an account in the Get Started lab, you can do so now using the Sign Up button.\nSign in to your account as you normally do, using Single Sign-On or Direct Sign-In.\nChoose the region and compartment\nIn the next screen you can choose the region using the pull down in the top right hand corner, and then choose the compartment you want to install into.\nReview the terms and restrictions, and then click on the checkbox to accept them. Then, click on Launch Stack,\nNote: This version of CloudBank is tested with version 1.3.0. Earlier versions may not contain all features used and you may see errors.\nReview the Create Stack page\nReview the details on the Create Stack page. You may wish to update the Name or add tags. When you are ready, click on Next.\nIn the Backend as A Service Section, fill in the following configuration variables as needed and select Next:\nCompartment : Select the compartment where you want to install Oracle Backend for Spring Boot and Microservices. Application Name (optional) : A random pet name that will be used as the application name if left empty. Edition : Select COMMUNITY Edition. Standard edition will give more options for the installation but those are not required or used in this LiveLab. Existing Authorization Token : Leave blank. If you check the checkbox Set Administrator Passwords in the Administrator Passwords section you have the option to fill in the following passwords (if not they are autogenerated):\nAPISIX Administrator Password (optional) : Leave blank to auto-generate. Grafana Administrator Password (optional) : Leave blank to auto-generate. ORACTL Administrator Password (optional) : Leave blank to auto-generate. This is the password for the obaas-admin user. ORACTL User Password (optional) : Leave blank to auto-generate. This is the password for the obaas-user user. In the Kubernetes Cluster Options. fill in the following for the OKE Clusters Options:\nPublic API Endpoint? : For the Live Lba you must check the checkbox Public API Endpoint API Endpoint Access Control : Enter the CIDR block you want to give access to the Control Plane API. Leave the default value 0.0.0.0/0. Node Pool Workers : The number of Kubernetes worker nodes (virtual machines) attached to the OKE cluster. Leave the default value of 3. Node Pool Worker Shape : The shape of the node pool workers. Leave the default Shape value. Node Workers OCPU : The initial number of Oracle Compute Units (OCPUs) for the node pool workers. Leave the default value of 2. NOTE: Oracle recommends that you set Control Plane Access Control to be as restrictive as possible\nIn the Load Balancers Options section, leave the default values.\nEnable Public Load Balancer : This option allows access to the load balancer from the internet (public IP). If not selected, access can only be from a private VCN. Public Load Balancer Access Control : Enter the CIDR block you want to give access to the Load Balancer. Default (and not recommended) is 0.0.0.0/0. Public Load Balancer Ports Exposed : The ports exposed from the load balancer. Minimum bandwidth : The minimum bandwidth that the load balancer can achieve. Maximum bandwidth : The maximum bandwidth that the load balancer can achieve. NOTE: Oracle recommends that you set Public Load Balancer Access Control to be as restrictive as possible.\nIn the Database Options section, leave the default values.\nAutonomous Database Compute Model : Choose either ECPU (default) or OCPU compute model for the ADB. Leave the default value of ECPU Autonomous Database Network Access : Choose the Autonomous Database network access. Leave the default value of SECURE_ACCESS ADB Access Control : Comma separated list of CIDR blocks from which the ADB can be accessed. This only applies if SECURE_ACCESS was chosen. Leave default value of 0.0.0.0/0. Autonomous Database ECPU Core Count : Choose how many ECPU cores will be elastically allocated. Leave default value of 2. Allow Autonomous Database OCPU Auto Scaling : Enable auto-scaling for the ADB ECPU core count (x3 ADB ECPU). Leave the default value of un-checked. Autonomous Database Data Storage Size : Choose ADB Database Data Storage Size in gigabytes. Leave the default value of 20GB. Autonomous Database License Model : The Autonomous Database license model. Leave the default value of LICENSE_INCLUDED. Create an Object Storage Bucket for ADB? : Leave the default value of un-checked. NOTE: Oracle recommends that you restrict by IP or CIDR addresses to be as restrictive as possible.\nClick Next to review your choices.\nComplete the Review page\nReview the details on the Review page. Check the box next to Run Apply. When you are ready, click on Create.\nReview the apply screen\nThe stack will now be applied. On the Apply screen (see below) you can monitor the progress of the installation in the Logs box. The installation should take about 30 minutes to complete. This includes the time needed to create your Oracle Autonomous Database instance, your Oracle Container Engine for Kubernetes cluster and install the various components of the stack into the Kubernetes cluster.\nNote: While you are waiting for the installation to complete is a great time to start setting up your development environment (see the next lab). You can come back here where you are done to check the installation completed successfully.\nVerify the installation Check the logs for errors\nScroll down to the bottom of the log to see the outcome. If there was an error during installation, details will be included at the end of the log. The most common errors are due to insufficient quota for some resource. If you get an error about insufficient quota, you may need to clean up unused resources or request a quota increase for the affected resource. Once you have done that, navigate back to the stack details (for example, using the breadcrumbs) and click on the Apply to try again.\nWhen the installation completes normally, the end of the log should look something like this:\nApply complete! Resources: 77 added, 0 changed, 0 destroyed. Outputs: adb_ip = \"Secured Access\" adb_name = \"KATYDIDDB\" apisix_admin_password = \u003csensitive\u003e grafana_admin_password = \u003csensitive\u003e kubeconfig_cmd = \"oci ce cluster create-kubeconfig --cluster-id ocid1.cluster.oc1... --region us-ashburn-1 --token-version 2.0.0 --kube-endpoint PUBLIC_ENDPOINT --file $HOME/.kube/config\" oractl_admin_password = \u003csensitive\u003e oractl_user_password = \u003csensitive\u003eTo get the sensitive information you need to click on the Application Information tab, and click on unlock or show to display the values:\nNote: Keep a copy of the values, you will need these in later labs.\nVerify you can access the Kubernetes cluster\nIn later labs, you will look at various resources in Kubernetes. You will need a Kubernetes configuration file to access the cluster. For now, accessing the cluster from OCI Cloud Shell will be sufficient to verify the installation.\nOpen the OCI Cloud Shell by clicking on the icon next to the region in the top right corner of the console and then clicking on Cloud Shell.\nRun the command provided at the end of your installation log or the information from the Application Information tab,to obtain the Kubernetes configuration file. The command will be similar to this:\noci ce cluster create-kubeconfig --cluster-id ocid1.cluster.oc1.i..... --region us-ashburn-1 --token-version 2.0.0 --kube-endpoint PUBLIC_ENDPOINT --file $HOME/.kube/configCheck that you can access the cluster using this command:\n$ kubectl get pods -n obaas-admin NAME READY STATUS RESTARTS AGE graalvm-compiler-79988b886c-hgw68 1/1 Running 0 10m obaas-admin-66599b65-vb662 1/1 Running 0 10m soc-ui-5dbd6f9cb4-kjdj8 0/1 Running 0 10mYour output will be slightly different, but you should see one pod listed in the output. This is enough to confirm that you have correctly configured access to the Kubernetes cluster.\nVerify you can connect to the APISIX API Gateway\nYou will need to provide the correct IP address for the API Gateway in your backend environment. You can find the IP address using this command, you need the one listed in the EXTERNAL-IP column:\n$ kubectl -n ingress-nginx get service ingress-nginx-controller NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE ingress-nginx-controller LoadBalancer 10.123.10.127 EXTERNAL-IP 80:30389/TCP,443:30458/TCP 13dNow use this command (with your IP address in the column EXTERNAL-IP) to make a request to the API Gateway. You should receive a response with an HTTP Status Code 404 (Not Found) and an error message in JSON format as shown below. Don’t worry about the 404, you will deploy some services soon, but this test is enough to know the API Gateway started up successfully:\n$ curl -i http://\u003cEXTERNAL-IP\u003e\u003e HTTP/1.1 404 Date: Wed, 01 Mar 2023 19:21:08 GMT Content-Type: application/json Transfer-Encoding: chunked Connection: keep-alive Vary: Origin Vary: Access-Control-Request-Method Vary: Access-Control-Request-Headers {\"timestamp\":\"2023-03-01T19:21:08.031+00:00\",\"status\":404,\"error\":\"Not Found\",\"path\":\"/\"} ", - "description": "The Oracle Backend for Spring Boot and Microservices can be installed from OCI Marketplace.\nNote: You only need to choose one of the three deployment options - local, OCI Free Tier or OCI Marketplace.\nAccess the Oracle Cloud Infrastructure Marketplace listing\nOpen the OCI Marketplace listing, as shown in the image below:\nClick on the Get App button.\nLog into your Oracle Cloud Infrastructure account\nYou will be taken to a Sign-In page.", + "content": "The Oracle Backend for Spring Boot and Microservices can be installed from OCI Marketplace.\nNote: You only need to choose one of the three deployment options - local, OCI Free Tier or OCI Marketplace.\nThis option installs a “production-sized” environment which includes an Oracle Compute Engine for Kubernetes (“OKE”) cluster and an Oracle Autonomous Database instance. If you want to use a smaller, development/test-sized environment that only requires a single OCI Compute Instance, please use the “Free Tier” option instead.\nAccess the Oracle Cloud Infrastructure Marketplace listing\nOpen the OCI Marketplace listing, as shown in the image below:\nClick on the Get App button.\nLog into your Oracle Cloud Infrastructure account\nYou will be taken to a Sign-In page. Choose they type of account you have and click on the Sign In button. If you did not create an account in the Get Started lab, you can do so now using the Sign Up button.\nSign in to your account as you normally do, using Single Sign-On or Direct Sign-In.\nChoose the region and compartment\nIn the next screen you can choose the region using the pull down in the top right hand corner, and then choose the compartment you want to install into.\nReview the terms and restrictions, and then click on the checkbox to accept them. Then, click on Launch Stack,\nNote: This version of CloudBank is tested with version 1.3.0. Earlier versions may not contain all features used and you may see errors.\nReview the Create Stack page\nReview the details on the Create Stack page. You may wish to update the Name or add tags. When you are ready, click on Next.\nIn the Backend as A Service Section, fill in the following configuration variables as needed and select Next:\nCompartment : Select the compartment where you want to install Oracle Backend for Spring Boot and Microservices. Application Name (optional) : A random pet name that will be used as the application name if left empty. Edition : Select COMMUNITY Edition. Standard edition will give more options for the installation but those are not required or used in this LiveLab. Existing Authorization Token : Leave blank. If you check the checkbox Set Administrator Passwords in the Administrator Passwords section you have the option to fill in the following passwords (if not they are autogenerated):\nAPISIX Administrator Password (optional) : Leave blank to auto-generate. Grafana Administrator Password (optional) : Leave blank to auto-generate. ORACTL Administrator Password (optional) : Leave blank to auto-generate. This is the password for the obaas-admin user. ORACTL User Password (optional) : Leave blank to auto-generate. This is the password for the obaas-user user. In the Kubernetes Cluster Options. fill in the following for the OKE Clusters Options:\nPublic API Endpoint? : For the Live Lba you must check the checkbox Public API Endpoint API Endpoint Access Control : Enter the CIDR block you want to give access to the Control Plane API. Leave the default value 0.0.0.0/0. Node Pool Workers : The number of Kubernetes worker nodes (virtual machines) attached to the OKE cluster. Leave the default value of 3. Node Pool Worker Shape : The shape of the node pool workers. Leave the default Shape value. Node Workers OCPU : The initial number of Oracle Compute Units (OCPUs) for the node pool workers. Leave the default value of 2. NOTE: Oracle recommends that you set Control Plane Access Control to be as restrictive as possible\nIn the Load Balancers Options section, leave the default values.\nEnable Public Load Balancer : This option allows access to the load balancer from the internet (public IP). If not selected, access can only be from a private VCN. Public Load Balancer Access Control : Enter the CIDR block you want to give access to the Load Balancer. Default (and not recommended) is 0.0.0.0/0. Public Load Balancer Ports Exposed : The ports exposed from the load balancer. Minimum bandwidth : The minimum bandwidth that the load balancer can achieve. Maximum bandwidth : The maximum bandwidth that the load balancer can achieve. NOTE: Oracle recommends that you set Public Load Balancer Access Control to be as restrictive as possible.\nIn the Database Options section, leave the default values.\nAutonomous Database Compute Model : Choose either ECPU (default) or OCPU compute model for the ADB. Leave the default value of ECPU Autonomous Database Network Access : Choose the Autonomous Database network access. Leave the default value of SECURE_ACCESS ADB Access Control : Comma separated list of CIDR blocks from which the ADB can be accessed. This only applies if SECURE_ACCESS was chosen. Leave default value of 0.0.0.0/0. Autonomous Database ECPU Core Count : Choose how many ECPU cores will be elastically allocated. Leave default value of 2. Allow Autonomous Database OCPU Auto Scaling : Enable auto-scaling for the ADB ECPU core count (x3 ADB ECPU). Leave the default value of un-checked. Autonomous Database Data Storage Size : Choose ADB Database Data Storage Size in gigabytes. Leave the default value of 20GB. Autonomous Database License Model : The Autonomous Database license model. Leave the default value of LICENSE_INCLUDED. Create an Object Storage Bucket for ADB? : Leave the default value of un-checked. NOTE: Oracle recommends that you restrict by IP or CIDR addresses to be as restrictive as possible.\nClick Next to review your choices.\nComplete the Review page\nReview the details on the Review page. Check the box next to Run Apply. When you are ready, click on Create.\nReview the apply screen\nThe stack will now be applied. On the Apply screen (see below) you can monitor the progress of the installation in the Logs box. The installation should take about 30 minutes to complete. This includes the time needed to create your Oracle Autonomous Database instance, your Oracle Container Engine for Kubernetes cluster and install the various components of the stack into the Kubernetes cluster.\nNote: While you are waiting for the installation to complete is a great time to start setting up your development environment (see the next lab). You can come back here where you are done to check the installation completed successfully.\nVerify the installation Check the logs for errors\nScroll down to the bottom of the log to see the outcome. If there was an error during installation, details will be included at the end of the log. The most common errors are due to insufficient quota for some resource. If you get an error about insufficient quota, you may need to clean up unused resources or request a quota increase for the affected resource. Once you have done that, navigate back to the stack details (for example, using the breadcrumbs) and click on the Apply to try again.\nWhen the installation completes normally, the end of the log should look something like this:\nApply complete! Resources: 77 added, 0 changed, 0 destroyed. Outputs: adb_ip = \"Secured Access\" adb_name = \"KATYDIDDB\" apisix_admin_password = \u003csensitive\u003e grafana_admin_password = \u003csensitive\u003e kubeconfig_cmd = \"oci ce cluster create-kubeconfig --cluster-id ocid1.cluster.oc1... --region us-ashburn-1 --token-version 2.0.0 --kube-endpoint PUBLIC_ENDPOINT --file $HOME/.kube/config\" oractl_admin_password = \u003csensitive\u003e oractl_user_password = \u003csensitive\u003eTo get the sensitive information you need to click on the Application Information tab, and click on unlock or show to display the values:\nNote: Keep a copy of the values, you will need these in later labs.\nVerify you can access the Kubernetes cluster\nIn later labs, you will look at various resources in Kubernetes. You will need a Kubernetes configuration file to access the cluster. For now, accessing the cluster from OCI Cloud Shell will be sufficient to verify the installation.\nOpen the OCI Cloud Shell by clicking on the icon next to the region in the top right corner of the console and then clicking on Cloud Shell.\nRun the command provided at the end of your installation log or the information from the Application Information tab,to obtain the Kubernetes configuration file. The command will be similar to this:\noci ce cluster create-kubeconfig --cluster-id ocid1.cluster.oc1.i..... --region us-ashburn-1 --token-version 2.0.0 --kube-endpoint PUBLIC_ENDPOINT --file $HOME/.kube/configCheck that you can access the cluster using this command:\n$ kubectl get pods -n obaas-admin NAME READY STATUS RESTARTS AGE graalvm-compiler-79988b886c-hgw68 1/1 Running 0 10m obaas-admin-66599b65-vb662 1/1 Running 0 10m soc-ui-5dbd6f9cb4-kjdj8 0/1 Running 0 10mYour output will be slightly different, but you should see one pod listed in the output. This is enough to confirm that you have correctly configured access to the Kubernetes cluster.\nVerify you can connect to the APISIX API Gateway\nYou will need to provide the correct IP address for the API Gateway in your backend environment. You can find the IP address using this command, you need the one listed in the EXTERNAL-IP column:\n$ kubectl -n ingress-nginx get service ingress-nginx-controller NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE ingress-nginx-controller LoadBalancer 10.123.10.127 EXTERNAL-IP 80:30389/TCP,443:30458/TCP 13dNow use this command (with your IP address in the column EXTERNAL-IP) to make a request to the API Gateway. You should receive a response with an HTTP Status Code 404 (Not Found) and an error message in JSON format as shown below. Don’t worry about the 404, you will deploy some services soon, but this test is enough to know the API Gateway started up successfully:\n$ curl -i http://\u003cEXTERNAL-IP\u003e\u003e HTTP/1.1 404 Date: Wed, 01 Mar 2023 19:21:08 GMT Content-Type: application/json Transfer-Encoding: chunked Connection: keep-alive Vary: Origin Vary: Access-Control-Request-Method Vary: Access-Control-Request-Headers {\"timestamp\":\"2023-03-01T19:21:08.031+00:00\",\"status\":404,\"error\":\"Not Found\",\"path\":\"/\"} ", + "description": "The Oracle Backend for Spring Boot and Microservices can be installed from OCI Marketplace.\nNote: You only need to choose one of the three deployment options - local, OCI Free Tier or OCI Marketplace.\nThis option installs a “production-sized” environment which includes an Oracle Compute Engine for Kubernetes (“OKE”) cluster and an Oracle Autonomous Database instance. If you want to use a smaller, development/test-sized environment that only requires a single OCI Compute Instance, please use the “Free Tier” option instead.", "tags": [], "title": "Install from OCI Marketplace", "uri": "/microservices-datadriven/cloudbank/provision/install-mp/index.html" diff --git a/cloudbank/more/credits/index.html b/cloudbank/more/credits/index.html index a2d918e0b..54efde507 100644 --- a/cloudbank/more/credits/index.html +++ b/cloudbank/more/credits/index.html @@ -25,24 +25,24 @@ Credits :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/provision/index.html b/cloudbank/provision/index.html index c6cc88ee2..f60b36646 100644 --- a/cloudbank/provision/index.html +++ b/cloudbank/provision/index.html @@ -21,24 +21,24 @@ Provision an Instance :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/provision/index.xml b/cloudbank/provision/index.xml index 78a6dc466..deda17e95 100644 --- a/cloudbank/provision/index.xml +++ b/cloudbank/provision/index.xml @@ -19,7 +19,7 @@ https://oracle.github.io/microservices-datadriven/cloudbank/provision/install-local/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://oracle.github.io/microservices-datadriven/cloudbank/provision/install-local/index.html - This option allows you to run Oracle Backend for Spring Boot and Microservices in a containerized environment on your local machine. This option is recommended if you do have enough free capacity on your local machine to run the environment, a minimum of 64GB RAM and 80GB free disk are recommneded. This option provides an environment with adequeate resources for development and testing, but is not suitable for a production-sized deployment or performance testing. + This option allows you to run Oracle Backend for Spring Boot and Microservices in a containerized environment on your local machine. This option is recommended if you do have enough free capacity on your local machine to run the environment, a minimum of 64GB RAM and 80GB free disk are recommended. This option provides an environment with adequate resources for development and testing, but is not suitable for a production-sized deployment or performance testing. Install in OCI Free Tier @@ -33,7 +33,7 @@ https://oracle.github.io/microservices-datadriven/cloudbank/provision/install-mp/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://oracle.github.io/microservices-datadriven/cloudbank/provision/install-mp/index.html - The Oracle Backend for Spring Boot and Microservices can be installed from OCI Marketplace. Note: You only need to choose one of the three deployment options - local, OCI Free Tier or OCI Marketplace. Access the Oracle Cloud Infrastructure Marketplace listing Open the OCI Marketplace listing, as shown in the image below: Click on the Get App button. Log into your Oracle Cloud Infrastructure account You will be taken to a Sign-In page. + The Oracle Backend for Spring Boot and Microservices can be installed from OCI Marketplace. Note: You only need to choose one of the three deployment options - local, OCI Free Tier or OCI Marketplace. This option installs a “production-sized” environment which includes an Oracle Compute Engine for Kubernetes (“OKE”) cluster and an Oracle Autonomous Database instance. If you want to use a smaller, development/test-sized environment that only requires a single OCI Compute Instance, please use the “Free Tier” option instead. \ No newline at end of file diff --git a/cloudbank/provision/install-free-trial/index.html b/cloudbank/provision/install-free-trial/index.html index 31b0d60eb..f9513c280 100644 --- a/cloudbank/provision/install-free-trial/index.html +++ b/cloudbank/provision/install-free-trial/index.html @@ -19,26 +19,26 @@ - + Install in OCI Free Tier :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/provision/install-local/index.html b/cloudbank/provision/install-local/index.html index 64d322d71..07428916a 100644 --- a/cloudbank/provision/install-local/index.html +++ b/cloudbank/provision/install-local/index.html @@ -5,40 +5,40 @@ - + - + - + - + Install locally :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/provision/install-mp/index.html b/cloudbank/provision/install-mp/index.html index 83b60b5da..3d399134a 100644 --- a/cloudbank/provision/install-mp/index.html +++ b/cloudbank/provision/install-mp/index.html @@ -7,62 +7,46 @@ +This option installs a “production-sized” environment which includes an Oracle Compute Engine for Kubernetes (“OKE”) cluster and an Oracle Autonomous Database instance. If you want to use a smaller, development/test-sized environment that only requires a single OCI Compute Instance, please use the “Free Tier” option instead."> +This option installs a “production-sized” environment which includes an Oracle Compute Engine for Kubernetes (“OKE”) cluster and an Oracle Autonomous Database instance. If you want to use a smaller, development/test-sized environment that only requires a single OCI Compute Instance, please use the “Free Tier” option instead."> +This option installs a “production-sized” environment which includes an Oracle Compute Engine for Kubernetes (“OKE”) cluster and an Oracle Autonomous Database instance. If you want to use a smaller, development/test-sized environment that only requires a single OCI Compute Instance, please use the “Free Tier” option instead."> - +This option installs a “production-sized” environment which includes an Oracle Compute Engine for Kubernetes (“OKE”) cluster and an Oracle Autonomous Database instance. If you want to use a smaller, development/test-sized environment that only requires a single OCI Compute Instance, please use the “Free Tier” option instead."> + Install from OCI Marketplace :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/provision/intro/index.html b/cloudbank/provision/intro/index.html index 9a3ce8201..ee441ace0 100644 --- a/cloudbank/provision/intro/index.html +++ b/cloudbank/provision/intro/index.html @@ -27,26 +27,26 @@ - + Introduction :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/saga/business-logic/index.html b/cloudbank/saga/business-logic/index.html index f62a26abe..e7c772b0f 100644 --- a/cloudbank/saga/business-logic/index.html +++ b/cloudbank/saga/business-logic/index.html @@ -25,24 +25,24 @@ The deposit service will be responsible for depositing funds into accounts. It will be an LRA participant, and so it will need to implement the LRA lifecycle actions like complete, compensate, and so on. A significant amount of the logic will be shared with the withdrawal service, so you will also create a separate class for that shared logic, following the Data Access Object pattern, to keep the business layer separate from the persistence layer."> Implement business logic :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/saga/dao/index.html b/cloudbank/saga/dao/index.html index 8710cc8b3..03e6bd89d 100644 --- a/cloudbank/saga/dao/index.html +++ b/cloudbank/saga/dao/index.html @@ -21,24 +21,24 @@ Create a Data Access Object :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/saga/deploy/index.html b/cloudbank/saga/deploy/index.html index 4c066b123..f99bb9702 100644 --- a/cloudbank/saga/deploy/index.html +++ b/cloudbank/saga/deploy/index.html @@ -25,24 +25,24 @@ Note: You already created the Kubernetes secrets necessary for the account service to access the Oracle Autonomous Database in a previous module, and the transfer service does not need access to the database. You also created the journal table that is needed by the update account application in the previous module."> Deploy services :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/saga/deposit/index.html b/cloudbank/saga/deposit/index.html index edb37946d..b9a081301 100644 --- a/cloudbank/saga/deposit/index.html +++ b/cloudbank/saga/deposit/index.html @@ -25,24 +25,24 @@ Create the Deposit service and scaffold methods Create a new directory in src/main/java/com/example/accounts called services and in that directory create a new Java file called DepositService."> Create the Deposit service :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/saga/index.html b/cloudbank/saga/index.html index 22aad4b7c..4b68612c5 100644 --- a/cloudbank/saga/index.html +++ b/cloudbank/saga/index.html @@ -21,24 +21,24 @@ Manage Sagas :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/saga/intro/index.html b/cloudbank/saga/intro/index.html index aa50689c1..865c3eaa2 100644 --- a/cloudbank/saga/intro/index.html +++ b/cloudbank/saga/intro/index.html @@ -37,24 +37,24 @@ Learn about the Saga pattern Learn about the Long Running Action specification Add new endpoints to the Account service for deposits and withdrawals that act as LRA participants Create a Transfer service that will initiate the LRA Prerequisites This module assumes you have:"> Introduction :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/saga/learn-lra/index.html b/cloudbank/saga/learn-lra/index.html index 887575866..6b6dd9530 100644 --- a/cloudbank/saga/learn-lra/index.html +++ b/cloudbank/saga/learn-lra/index.html @@ -25,24 +25,24 @@ In this module, you will explore the Long Running Action model."> Learn about Long Running Actions :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/saga/learn/index.html b/cloudbank/saga/learn/index.html index de2ae64b0..e7fdedb49 100644 --- a/cloudbank/saga/learn/index.html +++ b/cloudbank/saga/learn/index.html @@ -25,24 +25,24 @@ Database per service The Database per service pattern is a generally accepted best practice which dictates that each service must have its own “database” and that the only way other services can access its data is through its public API. This helps to create loose coupling between services, which in turn makes it easier to evolve them independently and prevents the creation of a web of dependencies that make application changes increasingly difficult over time."> Learn about the Saga pattern :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/saga/prepare/index.html b/cloudbank/saga/prepare/index.html index 363e15670..edd23daf5 100644 --- a/cloudbank/saga/prepare/index.html +++ b/cloudbank/saga/prepare/index.html @@ -29,24 +29,24 @@ ```xml <dependency> <groupId>com.oracle.microtx.lra</groupId> <artifactId>microtx-lra-spring-boot-starter</artifactId> <version>23.4.2</version> </dependency> ``` Update the Spring Boot application configuration file Update your Account service’s Spring Boot configuration file, application."> Prepare the Account service :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/saga/test/index.html b/cloudbank/saga/test/index.html index 522fad6e8..e369c32f9 100644 --- a/cloudbank/saga/test/index.html +++ b/cloudbank/saga/test/index.html @@ -29,24 +29,24 @@ > **Note**: If you prefer, you can create a route in the APISIX API Gateway to expose the service. The service will normally only be invoked from within the cluster, so you did not create a route for it."> Run LRA test cases :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/saga/transfer-service/index.html b/cloudbank/saga/transfer-service/index.html index fe7b8e019..382934219 100644 --- a/cloudbank/saga/transfer-service/index.html +++ b/cloudbank/saga/transfer-service/index.html @@ -25,24 +25,24 @@ Create a new Java Project for the transfer service. In the Explorer of VS Code open Java Project and click the plus sign to add a Java Project to your workspace."> Create the Transfer service :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/saga/withdraw-service/index.html b/cloudbank/saga/withdraw-service/index.html index 0545a48d4..9458f8411 100644 --- a/cloudbank/saga/withdraw-service/index.html +++ b/cloudbank/saga/withdraw-service/index.html @@ -29,24 +29,24 @@ ```java package com.example.accounts.services; import com.example.accounts.model.Account; import com.example.accounts.model.Journal; import com.oracle.microtx.springboot.lra.annotation.AfterLRA; import com.oracle.microtx.springboot.lra.annotation.Compensate; import com.oracle.microtx.springboot.lra.annotation.Complete; import com.oracle.microtx.springboot.lra.annotation.LRA; import com."> Create the Withdrawal service :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/springai/index.html b/cloudbank/springai/index.html index b65813a46..61b0ca8bc 100644 --- a/cloudbank/springai/index.html +++ b/cloudbank/springai/index.html @@ -21,24 +21,24 @@ CloudBank AI Assistant :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + + diff --git a/cloudbank/tags/index.html b/cloudbank/tags/index.html index 31953d2c0..1b9128b65 100644 --- a/cloudbank/tags/index.html +++ b/cloudbank/tags/index.html @@ -17,24 +17,24 @@ Tags :: CloudBank - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - + + + + + + - - - + + +