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
{{ message }}
This repository was archived by the owner on Apr 1, 2025. It is now read-only.
A relational database is used to store stream definitions and deployment info.
4
+
Spring Cloud Skipper provides schemas for *MariaDB*, *MySQL*, *Oracle*, *PostgreSQL*, *Db2*, *SQL Server*, and *H2*. The schema is automatically created when the server starts.
5
+
6
+
NOTE: The JDBC drivers for *MariaDB*, *MySQL* (via the _MariaDB_ driver), *PostgreSQL*, *SQL Server* are available without additional configuration. To use any other database you need to put the corresponding JDBC driver jar on the classpath of the server as described <<#add-custom-driver,here>>.
7
+
8
+
To configure a database the following properties must be set:
9
+
10
+
* `spring.datasource.url`
11
+
* `spring.datasource.username`
12
+
* `spring.datasource.password`
13
+
* `spring.datasource.driver-class-name`
14
+
15
+
The `username` and `password` are the same regardless of the database. However, the `url` and `driver-class-name` vary per database as follows.
|[.small]#jdbc:mariadb://${db-hostname}:${db-port}/${db-name}?allowPublicKeyRetrieval=true&useSSL=false&autoReconnect=true&permitMysqlScheme#{empty}footnote:[SSL is disabled in this example, adjust accordingly for your environment and requirements]
@@ -220,131 +220,31 @@ You can find more information on the deployment properties that you can configur
220
220
[[skipper-database-configuration]]
221
221
== Database configuration
222
222
223
-
A relational database is used to store stream and task definitions as well as the state of tasks that have been run.
224
-
Spring Cloud Skipper provides schemas for *H2*, *MySQL*, *Oracle*, *PostgreSQL*, *Db2*, and *SQL Server*. The schema is automatically created when the server starts.
223
+
include::configuration-database.adoc[]
225
224
226
-
By default, Spring Cloud Skipper offers an embedded instance of the *H2* database.
227
-
The *H2* database is good for development purposes but is not recommended for production use.
225
+
[#add-custom-driver]
226
+
==== Adding a Custom JDBC Driver
227
+
To add a custom driver for the database (for example, Oracle), you should rebuild the Skipper Server and add the dependency to the Maven `pom.xml` file.
228
+
You need to modify the maven `pom.xml` of `spring-cloud-skipper` module.
229
+
There are GA release tags in GitHub repository, so you can switch to desired GA tags to add the drivers on the production-ready codebase.
228
230
229
-
NOTE: *H2* database in Server Mode is not supported, only Embedded Mode.
231
+
To add a custom JDBC driver dependency for the Spring Cloud Skipper server:
230
232
231
-
The JDBC drivers for *MySQL* (through the MariaDB driver), *PostgreSQL*, *SQL Server*, and embedded *H2* are available without additional configuration.
232
-
If you are using any other database, then you need to put the corresponding JDBC driver jar on the classpath of the server.
233
+
. Select the tag that corresponds to the version of the server you want to rebuild and clone the github repository.
234
+
. Edit the spring-cloud-skipper-server/pom.xml and, in the `dependencies` section, add the dependency for the database driver required. In the following example , an Oracle driver has been chosen:
233
235
234
-
The database properties can be passed as environment variables or command-line arguments to the Skipper Server.
235
-
236
-
==== MySQL
237
-
238
-
The following example shows how to define a MySQL database connection using MariaDB driver.
0 commit comments