How to run Confluence Data Center with an embedded H2 database for testing purposes

Still need help?

The Atlassian Community is here for you.

Ask the community


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

Purpose

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

  1. Download and Install the AMPS SDK
  2. Run the AMPS SDK.
    1. 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

versionSpecify the version of the product to run (default is RELEASE)1.0
http-portThe HTTP port for the servlet container8080
ajp-portThe AJP port for the servlet container7412
pluginsComma-delimited list of plugin artifacts in GROUP_ID:ARTIFACT_ID:VERSION form, where version can be ommitted, defaulting to LATEST

groupId:artifactId::version

lib-plugin

Comma-delimited list of lib artifacts in GROUP_ID:ARTIFACT_ID:VERSION form, where version can be ommitted, defaulting to LATEST

groupId:artifactId:version

bundled-pluginsComma-delimited list of bundled plugin artifacts in GROUP_ID:ARTIFACT_ID:VERSION form, where version can be ommitted, defaulting to LATEST

groupId:artifactId:version

View more parameters

Parameter

Description

Example

containerContainer to run in (default is tomcat6x)

tomcat6x

context-path

Application context path (include the leading forward slash)

/myapp

data-versionVersion to use for data resources (default is RELEASE)RELEASE

jvmargs

Additional JVM arguments if required

-Xmx=512m

log4j

Log4j properties file

test/log4j.properties

productThe product to launch with the pluginjira
rest-versionVersion of the Atlassian REST module to use1.0
sal-versionVersion of SAL to use2.0.11
serverHost name of the application server (default is localhost)

localhost

Note: different SDK releases offer different parameters.

Learn how to work with the SDK


DescriptionExplain how to run non-clustered (single node) Confluence Data Center installations with an embedded H2 database for testing and app development purposes. 
ProductConfluence
Last modified on Mar 17, 2021

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.