copying data / moving data from one jackrabbit repository to another

[hanasaki <ha...@hanaden.com>]

I have several clients data in a single repository.  Due to growth, the
data of some of the customers needs to be moved to a new jcr repository
on a different server.  how can this be done?

any "mv" command to prune part of a tree?

Re: copying data / moving data from one jackrabbit repository to another

[Jukka Zitting <ju...@gmail.com>]

Hi,

On 3/25/07, hanasaki <ha...@hanaden.com> wrote:
> Does the export / import take care of things like base64 encoding
> binaries/images into CData sections?

Yes. The only things not included in a system view export are the node
type definitions and version histories of the exported content tree.
Otherwise a system view export contains everything you need to
recreate the content tree in another repository.

> Hmmm anything like a "federated" system that looks logically as one and
> does referals like LDAP?

A "federated" JCR Repository would be a very cool thing to have.

A simplistic implementation would just compose a number of Repository
instances (local or remote) under a single Repository facade that
would route login() calls based on some workspace naming convention.
This would of course not support operations like copy() or clone() or
have global namespaces, node types, or version histories.

BR,

Jukka Zitting

Re: copying data / moving data from one jackrabbit repository to another

[hanasaki <ha...@hanaden.com>]

Does the export / import take care of things like base64 encoding
binaries/images into CData sections?

Hmmm anything like a "federated" system that looks logically as one and
does referals like LDAP?

Jukka Zitting wrote:
> Hi,
> 
> On 3/24/07, hanasaki <ha...@hanaden.com> wrote:
>> I have several clients data in a single repository.  Due to growth, the
>> data of some of the customers needs to be moved to a new jcr repository
>> on a different server.  how can this be done?
> 
> Depending on the amount of data you're talking about, using a system
> view XML export is probably the most portable mechanism of moving
> content from one repository to another.
> 
> If the amount of content is too much for the XML export/import, you
> could also consider a custom migration tool that copies the content
> from one repository to another over JCR-RMI.
> 
> BR,
> 
> Jukka Zitting

Re: copying data / moving data from one jackrabbit repository to another

[Jukka Zitting <ju...@gmail.com>]

Hi,

On 3/24/07, hanasaki <ha...@hanaden.com> wrote:
> I have several clients data in a single repository.  Due to growth, the
> data of some of the customers needs to be moved to a new jcr repository
> on a different server.  how can this be done?

Depending on the amount of data you're talking about, using a system
view XML export is probably the most portable mechanism of moving
content from one repository to another.

If the amount of content is too much for the XML export/import, you
could also consider a custom migration tool that copies the content
from one repository to another over JCR-RMI.

BR,

Jukka Zitting