Page Comparison

...

The quickstart ships with two initialization files:
<jboss-dir>/server/default/data/bedework/dumprestore/initbedework.xml
<jboss-dir>/server/default/data/bedework/dumprestore/initbedework-sparse.xml

The "initbedework“initbedework.xml" xml” data contains a basic calendar structure, many categories, two calendar suites, and the handful of users & groups that allow the quickstart demonstration to run. It is a good starting point for most deployments.

The "“-sparse" sparse” version contains no events, no categories, no locations, no contacts, and the barest of calendar structures.  It is a good starting point if you want to build up a system from scratch.

...

Bedework uses the JMX console built into JBoss to dump and restore data.  In the default quickstart distribution, you get to the JMX console by navigating to "JMX Console" “JMX Console” from the root of the JBoss server at http://localhost:8080/ or by directly visiting http://localhost:8080/jmx-console/

...

1. With Bedework running, go to the JMX console: http://localhost:8080/jmx-console/
2. Select "org“org.bedework" bedework” from the "Object “Object Name Filter" Filter” menu to the left of the page.
3. Select "service“service=DumpRestore"DumpRestore”
4. You will be presented with a form allowing you to manage the dump/restore process.
5. The "DataOut" “DataOut” attribute tells Bedework where to put the file.  By default, this is in <jboss-dir>/server/default/data/bedework/dumprestore/
6. If you've changed any attributes, click "Apply Changes"“Apply Changes”
7. Click "Invoke" “Invoke” for the "dumpData" “dumpData” operation.
8. You should find a file with a name similar to "bwdata20100205T130857“bwdata20100205T130857.xml" xml” in your DataOut directory.

...

1. Stop the Bedework system if running.
2. Delete (or rename) the following directories
   1. <jboss-dir>/server/default/data/bedework/derby
   2. <jboss-dir>/server/default/data/activemq
   3. <jboss-dir>/server/default/data/activemq-data
   4. <jboss-dir>/server/default/data/bedework/lucene
3.  Start the Bedework system.  The first three directories above should be recreated, and you should see an error in the log "Schema “Schema 'SA' does not exist"exist”, which is Derby complaining about not finding the Bedework schema that you've just removed.
4. Go to the JMX console: http://localhost:8080/jmx-console/
5. Select "org“org.bedework" bedework” from the "Object “Object Name Filter" Filter” menu to the left of the page.
6. Select "service“service=DumpRestore"DumpRestore”
7. You will be presented with a form allowing you to manage the dump/restore process.  The "DataIn" “DataIn” attribute should point at the xml datafile you wish to restore.  By default, this is the initbedework.xml file. 
8. Initialize the schema:
   1. Set the attribute "Export" “Export” to True
   2. Set the attribute "Create" “Create” to True
   3. Click "Apply Changes" “Apply Changes” to set the values.
   4.  Click "Invoke" “Invoke” for the "schema" “schema” operation.
9. Restore the data:
   1. Navigate back to the DumpRestore service (click "Back “Back to MBean"MBean”)
   2. Click "Invoke" “Invoke” for the "restoreData" “restoreData” operation.
      

To create an empty system:

...