Page History

This page deals with importing and exporting data to and from the JCR. Magnolia provides functions to export data from a JCR workspace into a file, and to import data by file into a JCR workspace. This process is known as Bootstrapping. 

...

Bootstrap files

...

Many Magnolia content apps that store their data in JCR workspaces provide actions to import and export JCR data. Some examples: Pages app, Assets app, Contacts app, Categories app.

Additionally, the JCR Tools app allow you to operate on data in all Magnolia workspaces, including those where the Export and Import actions are not available in the workspace-specific app, for example in the Security app.  

Note that all the apps mentioned, including the JCR Tools app, rely on the default import and export actions defined in the module magnolia-ui-admincentral.

...

The Import and Export actions use the JCRImportCommand and JCRExportCommand commands. The commands are defined in the magnolia-ui-admincentral module and implemented in 

...

Exporting and importing from the JCR Tools app

The import and export tools in the JCR Tools app allow you to operate on data in all Magnolia workspaces, including those where the Export and Import actions are not available in the workspace-specific app, for example in the Security app.  

To export:

1. Select the Workspace where the content resides.
2. In Base path, type the path to the node to export.
3. Select Format: XML or YAML.
4. Select the type of Compression: None, ZIP or GZIP.
5. Click Execute.

...

The bootstrapping mechanism, directory location and management for Maven modules and light modules is different. See:

• Bootstrapping in Maven modules.
• Bootstrapping in light modules. 

...

You can execute Groovy scripts on a running instance to both export and import JCR data. This type of export or import only supports XML file format. See the Groovy module and Groovy app for information about how to execute Groovy scripts on a running Magnolia instance.

...

When importing bootstrap files, we recommend you use task classes, which can handle bootstrap files called from your module version handler. For an example about how to use the module version handler, see create version handler. Magnolia provides tasks to handle bootstrap files out of the box, see

...