CODEWITHSUNDEEP
alfrescoalfresco-sharealfresco-webscriptsalfresco-enterprise
pappu_kutty
pappu_kutty

Reputation: 2488

Alfresco data export and import

we have to export alfresco data and import into another repository, and not necessarily backup/restore process. we are aiming for script which can be run and extract data on some conditions, set of files, with all its metedata.

i have got below link, which talks about same, but it is old , and things cant be done like versions of the file, condition based extract.

https://www.ibm.com/developerworks/cn/xml/x-cmis2/index.html

i would like to know any approaches available for extract and import of the alfresco data into other repositories..

Upvotes: 0

Views: 1489

Answers (1)

Jeff Potts
Jeff Potts

Reputation: 10538

There is nothing out-of-the-box that will do this. The replication sub-system is not suitable for frequent replication of more than a small handful of nodes.

So, you will have to write a custom solution or look at third-party solutions that can do this. Simflofy is one example. Another example is the Parashift Alfstream module.

If you would like to develop this yourself, I suggest you do something like:

  1. Write code to export one or more files to the file system. This should be storage that is shared between the source and all target repositories.
  2. Alongside each file, write a "manifest" file that descries the file's metadata, including custom properties and property values. You should use the same format that the Bulk File System Import Tool expects when doing an import.
  3. Add a message to a queue that describes where the exported data is sitting and where it needs to be imported.
  4. In the target repository, write a listener that is subscribe to the queue.
  5. When the listener gets a message it can initiate a Bulk File System Import in the target system. The BFSIT will import the files and set the metadata as described in the manifest file you generated in Step 2.
  6. Optionally, the target system can place another message on the queue acknowledging that the import has been performed, which the source repo can then pick up to complete the task.

Some people have been successful using Apache Camel for this, but it is not strictly necessary.

Upvotes: 3

Related Questions