topic Re: Exporting content into remote JackRabbit in Alfresco Archive

Exporting content into remote JackRabbit

legolas — Fri, 03 Nov 2006 15:15:39 GMT

Hi all,Let me first apologise if I ask a question that has already been raised and answered here, I am a newbie on Alfresco and JCR, searched this forum but didn't find the answer to my question/problem.I have written an Action that gets triggered when content arives in a published folder.This actio

Re: Exporting content into remote JackRabbit

davidc — Fri, 03 Nov 2006 15:34:59 GMT

Obviously, I would prefer if you were importing from Jackrabbit to Alfresco.

Although, JSR-170 specifies a standard API, it does enforce a standard model. And that's the problem here.

Re: Exporting content into remote JackRabbit

legolas — Fri, 03 Nov 2006 15:50:31 GMT

First of all thanks for your quick answer.

Obviously, I would prefer if you were importing from Jackrabbit to Alfresco.

Well we would like to use Alfresco as our main CMS implementation, but a lightweight repository on the published side, some portlets and other stuff, thereby physically seperating the author repository from the published repository. That's why this export needs to be done.

Although, JSR-170 specifies a standard API, it does enforce a standard model. And that's the problem here.

I was under the impression that the exportSystemView method would export a complete view of the system including the NodeType's and NameSpace definitions.

If this is not the case, is there a way to accomplish this?

Re: Exporting content into remote JackRabbit

davidc — Fri, 03 Nov 2006 16:02:14 GMT

As per the spec, the systemView does not export node type definitions.
Unfortunately, there's no standard way of registering node types. That should come in JSR-283 (next update of JSR-170).

So, the only solution is to define equivalent namespaces and node types using the mechanism provided by Jackrabbit.

As for wanting a light-weight published repository, I'm interested in why you prefer Jackrabbit.

Re: Exporting content into remote JackRabbit

legolas — Sat, 04 Nov 2006 07:11:05 GMT

We (I adviced) carefully selected alfresco based on requirements, such as JCR compliancy, workflow, etc.
We don't need/want jBPM on the published node, this is the final target of the workflow.
Neither do we want author components on the published node.

JackRabbit is AFAIK, the only released repository only implementation, Jeceira is at quite an early stage.

Where can I find the model def's in alfresco?

I think I just need to make sure the same def's end up in jackrabbit as well.

Thanks,
Marcel

Re: Exporting content into remote JackRabbit

davidc — Mon, 06 Nov 2006 11:29:51 GMT

You will find Alfresco model definitions in

<config_dir>/alfresco/model

In particular, contentModel.xml contains the spaces/files model used by the Alfresco web client.

Re: the lightweight "released" repository. This is an interesting discussion. I gather from your comments that you perceive Alfresco to be heavier weight than Jackrabbit because it has built-in support for "authoring" such as rules, versioning, workflow etc. Am I correct in my assumption?

It's possible to switch off the 'author' capability, revealing a vanilla storage and retrieval repository, however, our own benchmarking indicates this is not necessary. Alfresco will suit your published repository even with all the extra functionality.

Re: Exporting content into remote JackRabbit

legolas — Mon, 06 Nov 2006 13:09:42 GMT

Thanks for the information.

It's possible to switch off the 'author' capability, revealing a vanilla storage and retrieval repository, however, our own benchmarking indicates this is not necessary. Alfresco will suit your published repository even with all the extra functionality.

We did not do any loadtesting just yet. but I reckon that the memory consumption will be a lot higher than a stripped version of alfresco.
Besides, a preferably level one only repository also prevents developers from trying to bypass the overall architecture.

Stripping down alfresco might ease up the synchronization between the CMS and the published repository.
Is stripping down alfresco documented somewhere on the wiki? I did do a brief search but couldn't find it.

Thanks,
Marcel