Assuming that Java has been installed, the importer can be executed from command line: 

java -jar <<path to importer jar>> <<path to parameterization xml file>>


java -jar "D:\Projects\Politie\4-Import\HippoImporter\hippoimporter.jar" "D:\Projects\Politie\4-Import\current\project.xml"

Parameterization xml

The parametrization xml file serves as a base for the functionality of importer. In this file the necessary parameters must be defined. 

It consists of three sections: Jobs, Settings and Content Settings.


The Jobs element describes the specific execution of the importer in a collection of sequential Job elements. These Job elements specify the consecutive tasks that the importer has to perform. The importer supports the following types of jobs: 


Tests local database connectivity.


<Job type="db_test"/>


Tests the CMS connection by trying to find a node with the specified UUID in the identifier attribute.


<Job type="test_job">
<Param name="identifier">eb2146a4-4bc5-437b-be5a-b057f4975aaa</Param>


Cleans the importer’s local database table.


<Job type="clear_db"/>


Deletes the nodes from the Hippo repository according to the database table. Be careful using this job, do not delete content that should not be erased!


<Job type="delete_nodes"/>


Creates the nodes in the Hippo repository according to one structure xml specified in the <Param name="filename"> element. This job also validates the structure xml.


<Job type="create_nodes">
<Param name="filename">./samples/xml/Images_Structure.xml</Param>
<Param name="resourceXmlPath">./samples/xml/</Param>
<Param name="contentType">Resource</Param>
<Param name="recurse">true</Param>
<Param name="resolve">false</Param>
<Param name="overwrite_nodes">True</Param>


Some type of jobs allow customization via child elements of the form:

<Param name=NAME>VALUE</Param>

Some possibilities:


If set to true then the name attribute of <Input/> elements in the content xml (see below) will be used as is. If set to false (or omitted) then the importer will preprocess these attributes to valid JCR technical node names.


The settings element of the parameterization file contains settings that are required to start the importer and some other parameters used during the execution of the jobs. 

The settings can be divided in three sub-sections:

  1. Database settings for the database that is used by the importer to record all the nodes that it creates
  2. Hippo repository connection settings
  3. Important external parameters

Content Settings

In the ContentSettings tag several default properties and mixins can be configured for different node types. 

The importer supports the following defaults:

Hippo mirrors parameterization

Parameterize other hippo mirrors (???)

Default mixins

Defaults mixins that should be added to each node upon creation.

<CustomNode> defaults (???).

Folder defaults

Default properties and mixins that should be added to a folder of the specified type.

Folder type defaults

Additional default properties for folders based on the hippostd:foldertype property value (???).

Resource defaults

Default primary type, properties and mixins that should be added to any resource.

Input defaults

Default properties and mixins that should be added to all input elements (i.e. sub-nodes of handle node).

Continue to: Example of a parameterization xml file