Wiki source code of Reset H2 Database

Version 3.1 by Eva Torken on 2024/03/26 12:04

Show last authors
1 {{container}}
2 {{container layoutStyle="columns"}}
3 (((
4 eMagiz runtimes can run on local, on-premises servers. The main reason is that some systems are only accessible within the client's infrastructure. In such a scenario, the on-premises server must have a Docker installation before you can communicate between your on-premise server and eMagiz.
5
6 Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
7
8 == 1. Prerequisites ==
9
10 * Intermediate knowledge of the eMagiz platform
11
12 == 2. Key concepts ==
13 This microlearning centers on the reset of the H2 Database.
14 * The key aspects are:
15 ** When to use the H2 reset
16 ** How to use the H2 reset
17 ** Implications of resetting the H2 database.
18
19 == 3. H2 Database reset ==
20 (part on when to use)
21
22 === 3.1 Cloud ===
23 In short, the reset action can be described by the following:
24
25 * The reset of the H2 Database does the following:
26 ** Removes the H2 databases that are registered under the standard eMgaiz data folder
27 ** Re-adds the removed H2 databases
28 * With a reset, you start with a clean slate
29 ** H2 databases are emptied
30 [[image:Main.Images.Release Blog.WebHome@release-217-template-tango-remove-h2.png]]
31
32 To execute this action please navigate to Deploy -> Architecture. After you have done so you can access the context menu of a particular runtime (via a right mouse click), while in "Start Editing" mode, and select the option called "Reset H2". By pressing this button your executes all steps mentioned above.
33
34 === 3.2 On-premise ===
35
36 == 4. Key takeaways ==
37
38 *
39
40 == 5. Suggested Additional Readings ==
41
42 There are no suggested additional readings for this microlearning.)))
43 (((
44 {{toc/}}
45 )))
46 {{/container}}
47 {{/container}}