How to run Confluence Data Center with an embedded H2 database for testing purposes
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
From Feb 2, 2021 (server end of sale date) you will only be able to generate Data Center evaluation licenses. This means the Confluence Setup Wizard won’t include an option to use an embedded H2 database.
The purpose of this article is to explain how to run non-clustered (single node) Confluence Data Center installations with an embedded H2 database for testing and app development purposes. You can run an H2 database using existing automated tooling through Atlassian Maven Plugin Suite (AMPS).
Solution
Run the AMPS SDK.
You can pass parameters on the command line in the form:
atlas-run-standalone --product confluence
AMPS will use the latest stable version of Confluence. If the <confluence-home>/confluence.cfg.xml file includes an H2 database URL, Confluence will start an H2 instance.
Here are some useful parameters:
Parameter | Description | Example |
|---|---|---|
| Specify the version of the product to run (default is RELEASE) |
|
| The HTTP port for the servlet container |
|
| The AJP port for the servlet container |
|
| Comma-delimited list of plugin artifacts in GROUP_ID:ARTIFACT_ID:VERSION form, where version can be ommitted, defaulting to LATEST |
|
| Comma-delimited list of lib artifacts in GROUP_ID:ARTIFACT_ID:VERSION form, where version can be ommitted, defaulting to LATEST |
|
| Comma-delimited list of bundled plugin artifacts in GROUP_ID:ARTIFACT_ID:VERSION form, where version can be ommitted, defaulting to LATEST |
|
View more parameters
Parameter | Description | Example |
|---|---|---|
| Container to run in (default is tomcat6x) |
|
| Application context path (include the leading forward slash) |
|
| Version to use for data resources (default is RELEASE) |
|
| Additional JVM arguments if required |
|
| Log4j properties file |
|
| The product to launch with the plugin |
|
| Version of the Atlassian REST module to use |
|
| Version of SAL to use |
|
| Host name of the application server (default is localhost) |
|
Note: different SDK releases offer different parameters.
Was this helpful?