Hi Jarek, The dump and import commands provided by the standalone jar work fine. I generate an XML, then I import it in the new repository using the new configuration.
Thanks, Tarek On Mon, Dec 22, 2014 at 1:44 PM, Tarek Jarraya <[email protected]> wrote: > Hi Jarek, > > Thanks a lot. > > I am trying to do it with another manner: I start the standalone as webdav > client when connected I am using the commands dump and import. > > I will update you what is the result. > > Thanks, > Tarek > > On Mon, Dec 22, 2014 at 1:30 PM, Jaroslaw Marek <[email protected]> > wrote: >> >> Hi Tarek, >> You could try to use jackrabbit-standalone.jar as described here [1]. You >> would export from the old repository and then import to the new repository >> with new configuration. >> >> Cheers, >> Jarek >> >> [1] http://jackrabbit.apache.org/standalone-server.html#StandaloneServer- >> Backupandmigration >> >> >> On 22.12.2014 10:28, Tarek Jarraya wrote: >> >>> Hi All, >>> >>> I use Jackrabbit v 2.8 with webapp deployment mode. >>> >>> I am using the default generated configuration: >>> - For the FileSystem, I am using LocalFileSystem. >>> - For the datastore, I am using FileDataStore >>> - For the workspace, I am using LocalFileSystem >>> and DerbyPersistenceManager. Same thing for Versioning. >>> >>> Currently, the repository contains a lot of documents. Now, I want to >>> migrate to full database storage with MySQL (FileSystem, DataStore, >>> workspace, versioning). I have the correct configuration file for that. >>> >>> My question, how to migrate all the repository content to the new >>> configuration? because if apply the new configuration I will loose the >>> link >>> to all stored documents. >>> >>> Thanks for your help. >>> >>> Tarek >>> >>> >>
