You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs-source/spring/content/_index.md
+3-13
Original file line number
Diff line number
Diff line change
@@ -4,13 +4,11 @@ description: "Spring and Spring Boot"
4
4
keywords: "spring springboot microservices development oracle backend"
5
5
---
6
6
7
-
Oracle Backend for Spring Boot and Microservices allows developers to build microservices in Spring Boot and provisions a "backend as a service" with
8
-
Oracle Database and other infrastructure components that operate on multiple clouds. Oracle Backend for Spring Boot and Microservices vastly simplifies the task of
9
-
building, testing, and operating microservices platforms for reliable, secure, and scalable enterprise applications.
7
+
Oracle Backend for Spring Boot and Microservices allows developers to build microservices in Spring Boot and provisions a "backend as a service" with Oracle Database and other infrastructure components that operate on multiple clouds. Oracle Backend for Spring Boot and Microservices vastly simplifies the task of building, testing, and operating microservices platforms for reliable, secure, and scalable enterprise applications.
10
8
11
9
12
-
{{< hint type=[warning] icon=gdoc_fire title="Version 1.1.3 (production) released March, 2024" >}}
13
-
Oracle Backend for Spring Boot and Microservices Version 1.1.3 is now generally available and suitable for production use. This version supports and recommends Spring Boot 3.2.x, Spring 6.1 and Spring Cloud 2023.0.0, with limited backwards compatibility for Spring Boot 2.7.x.
10
+
{{< hint type=[warning] icon=gdoc_fire title="Version 1.2.0 (production) released June, 2024" >}}
11
+
Oracle Backend for Spring Boot and Microservices Version 1.2.0 is now generally available and suitable for production use. This version supports and recommends Spring Boot 3.2.x, Spring 6.1 and Spring Cloud 2023.0.x, with limited backwards compatibility for Spring Boot 2.7.x.
There are a number of demonstrations (videos) and hands-on labs (Live Lab) that show how to use Oracle Backend for Spring Boot and Microservices (Spring Boot) and
8
-
Oracle Backend for Parse Platform (Parse Platform).
7
+
There are a number of demonstrations (videos) and hands-on labs (Live Lab) that show how to use Oracle Backend for Spring Boot and Microservices (Spring Boot).
9
8
10
9
## Prerequisites
11
10
12
-
*[Deployed Oracle Backend for Spring Boot and Microservices](../setup/) (and Parse Platform)
11
+
*[Deployed Oracle Backend for Spring Boot and Microservices](../setup/).
13
12
14
13
## Introduction Video
15
14
@@ -30,14 +29,13 @@ Watch this video for more information.
30
29
[In this workshop (~ 2 hours)](https://bit.ly/CloudBankOnOBaaS), you learn how to build Microservices using Spring Boot and deploy
31
30
them to the Oracle Backend for Spring Boot and Microservices. You learn about accessing the database using the Java Persistence API (JPA), service
32
31
discovery, exposing services with the API Gateway, managing transactions across Microservices, workflow, and using observability tools
33
-
to monitor your services and diagnose issues. You also learn about building a web and mobile user interface for your services using
34
-
Flutter and Parse Platform.
32
+
to monitor your services and diagnose issues.
35
33
36
34
If you have already deployed Oracle Backend for Spring Boot and Microservices, you can skip Lab 1 (Provision an Instance).
37
35
38
36
## More Learning
39
37
40
-
There are more channels to learn about Oracle Backend for Spring Boot and Microservices (and Parse Platform):
38
+
There are more channels to learn about Oracle Backend for Spring Boot and Microservices:
Copy file name to clipboardExpand all lines: docs-source/spring/content/setup/_index.md
+91-22
Original file line number
Diff line number
Diff line change
@@ -54,9 +54,6 @@ resources:
54
54
- name: oci-stack-byodb-options
55
55
src: "oci-stack-byodb-options.png"
56
56
title: "Bring your Own Database Options - Standard Edition"
57
-
- name: oci-stack-parse-options
58
-
src: "oci-stack-parse-options.png"
59
-
title: "Parse Server Options"
60
57
- name: oci-stack-app-name
61
58
src: "oci-stack-app-name.png"
62
59
title: "Compartment, Application and Edition"
@@ -116,6 +113,93 @@ You must meet the following prerequisites to use Oracle Backend for Spring Boot
116
113
- Oracle Backend for Spring Boot and Microservices command-line interface (oractl). [Download oractl](https://github.com/oracle/microservices-datadriven/releases).
117
114
-[OPTIONAL]Oracle Backend for Spring Boot and Microservices VS Code Extension. [Download VS Code Extension](https://github.com/oracle/microservices-datadriven/releases).
118
115
116
+
## OCI policies
117
+
118
+
The following policies needs to be in place to be able to install Oracle Backend for Spring Boot and Microservices. Top level and their dependencies listed.
119
+
120
+
### Oracle Container Engine for Kubernetes
121
+
122
+
```text
123
+
Allow group `<group-name>` to manage cluster-family in `<location>`
124
+
├── Allow group `<group-name>` to inspect compartments in `<location>`
125
+
├── Allow group `<group-name>` to read virtual-network-family in `<location>`
126
+
├── Allow group `<group-name>` to use network-security-groups in `<location>`
127
+
├── Allow group `<group-name>` to use private-ips in `<location>`
128
+
├── Allow group `<group-name>` to use subnets in `<location>`
129
+
├── Allow group `<group-name>` to use vnics in `<location>`
130
+
├── Allow group `<group-name>` to manage cluster-node-pools in `<location>`
131
+
├── Allow group `<group-name>` to manage instance-family in `<location>`
132
+
└── Allow group `<group-name>` to manage public-ips in `<location>`
133
+
```
134
+
135
+
### VCN
136
+
137
+
```text
138
+
Allow group `<group-name>` to manage vcns in `<location>`
139
+
├── Allow group `<group-name>` to manage route-tables in `<location>`
140
+
├── Allow group `<group-name>` to manage-security-lists in `<location>`
141
+
├── Allow group `<group-name>` to manage-dhcp-options in `<location>`
142
+
143
+
144
+
Allow group `<group-name>` to manage vcns in `<location>`
145
+
Allow group `<group-name>` to manage route-tables in `<location>`
146
+
Allow group `<group-name>` to manage security-lists in `<location>`
147
+
Allow group `<group-name>` to manage dhcp-options in `<location>`
148
+
Allow group `<group-name>` to manage nat-gateways in `<location>`
149
+
Allow group `<group-name>` to manage service-gateways in `<location>`
150
+
Allow group `<group-name>` to manage network-security-groups in `<location>`
151
+
Allow group `<group-name>` to manage subnets in `<location>`
152
+
```
153
+
154
+
### Container Registry
155
+
156
+
```text
157
+
Allow group `<group-name>` to manage repos in `<location>`
158
+
```
159
+
160
+
### Object Storage
161
+
162
+
```text
163
+
Allow group `<group-name>` to read objectstorage-namespaces in `<location>`
164
+
Allow group `<group-name>` to manage objects in `<location>`
165
+
└── Allow group `<group-name>` to manage buckets in `<location>`
166
+
```
167
+
168
+
### Autonomous Database
169
+
170
+
```text
171
+
Allow group `<group-name>` to manage autonomous-database-family in `<location>`
172
+
```
173
+
174
+
### Vault
175
+
176
+
If you deploy Oracle Backend for Spring Boot and Microservices **STANDARD** edition you need the following policies.
177
+
178
+
```text
179
+
Allow group `<group-name>` to manage vaults in `<location>`
180
+
Allow group `<group-name>` to manage keys in `<location>`
181
+
```
182
+
183
+
#### Additional Vault
184
+
185
+
To allow Container Engine for Kubernetes to access Vault via Groups:
186
+
187
+
```text
188
+
Allow group `<group-name>` to manage policies in `<location>`
189
+
Allow group `<group-name>` to manage tag-namespaces in `<location>`
190
+
Allow group `<group-name>` to manage dynamic-groups in `<location>`
191
+
Allow group `<group-name>` to manage secret-family in `<location>`
192
+
```
193
+
194
+
### Oracle Resource Manager
195
+
196
+
```text
197
+
Allow group `<group-name>` to read orm-template in `<location>`
198
+
Allow group `<group-name>` to use orm-stacks in `<location>`
199
+
└── Allow group `<group-name>` to manage orm-jobs in `<location>`
200
+
Allow group `<group-name>` to manage orm-private-endpoints in `<location>`
201
+
```
202
+
119
203
## Summary of Components
120
204
121
205
Oracle Backend for Spring Boot and Microservices setup installs the following components:
@@ -137,10 +221,7 @@ Oracle Backend for Spring Boot and Microservices setup installs the following co
137
221
| OpenTelemetry Collector | 0.101.0 | Collects process and export telemetry data. |
138
222
| Oracle Database Observability Exporter | 1.2.1 | Exposes Oracle Database metrics in standard Prometheus format. |
139
223
| Oracle Database Operator | 1.0 | Helps reduce the time and complexity of deploying and managing Oracle databases. |
140
-
| Oracle Database storage adapter for Parse (optional) | 1.0.0 | Enables the Parse Server to store data in Oracle Database. |
141
224
| Oracle Transaction Manager for Microservices | 23.4.2 | Manages distributed transactions to ensure consistency across Microservices. |
142
-
| Parse Server (optional) | 6.3.0 | Provides backend services for mobile and web applications. |
143
-
| Parse Dashboard (optional) | 5.2.0 | Provides web user interface for managing the Parse Server. |
@@ -189,27 +270,15 @@ To set up the OCI environment, process these steps:
189
270
190
271
**WARNING:** Deletion or expiration of the token will result in the failure to pull images later. Also you must have one free OCI auth token (note that the maximum is two per user). You can *NOT* use someone elses token.
1. If you check the checkbox *Enable Parse Platform* in the **Parse Server** section a Parse Server will be installed. Fill in the following for the Parse Server:
202
-
203
-
-`Application ID` (optional) : Leave blank to auto-generate.
204
-
-`Server Master Key` (optional) : Leave blank to auto-generate.
205
-
-`Dashboard Username` : The user name of the user to whom access to the dashboard is granted.
206
-
-`Dashboard Password` (optional) : The password of the dashboard user (a minimum of 12 characters). Leave blank to auto-generate.
207
-
-`Enable Parse S3 Storage` : Check the checkbox to enable Parse Server S3 Adaptor and create a S3 compatible Object Storage Bucket.
1. 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):
214
283
215
284
-`APISIX Administrator Password` (optional) : Leave blank to auto-generate.
0 commit comments