Reset H2 Database

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.

Should you have any questions, please get in touch with academy@emagiz.com.

1. Prerequisites

• Intermediate knowledge of the eMagiz platform

2. Key concepts

This microlearning centers on the reset of the H2 Database.

• The key aspects are:
  • When to use the H2 reset
  • How to use the H2 reset
  • Implications of resetting the H2 database. 

3. H2 Database reset

(part on when to use)

3.1 Cloud

In short, the reset action can be described by the following:

• The reset of the H2 Database does the following:
  • Removes the H2 databases that are registered under the standard eMgaiz data folder
  • Re-adds the removed H2 databases
• With a reset, you start with a clean slate
  • H2 databases are emptied

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.

3.2 On-premise

When the H2 Database of an on-premise runtime needs to be reset the action needed is different. Here, the only action needed is to reset the runtime.

For more information on resetting a runtime, please check out the following microlearning:

• Reset runtime

4. Key takeaways

5. Suggested Additional Readings

There are no suggested additional readings for this microlearning.