Export in 3.0

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

loftux

The complete repository export has been disabled in 3.0. This feature has been useful for migrating from one db to another, not having to do any complex database migrations, instead bootstrapping the content.
So I thought that I instead use the export/import features. To list all the needed jars can be quite some work, so I made a script that outputs another script. Put this in a file in your Alfresco home folder, call it something like createexport.sh and make it executable.

#!/bin/sh
# Create Alfresco export script
# Peter Löfgren, Redpill Linpro

SCRIPTNAME="export.sh"
ALF_HOME=.
cd "$ALF_HOME"
APPSERVER="${ALF_HOME}/tomcat"

# Add the basics
echo "#!/bin/sh" > $SCRIPTNAME

# make the export dir
echo "if [ ! -d ./export ]; then" >> $SCRIPTNAME
echo "mkdir export" >> $SCRIPTNAME
echo "fi" >> $SCRIPTNAME

# Add Java options to script
echo "export JAVA_HOME=/usr/lib/jvm/java-6-sun" >> $SCRIPTNAME
#echo "export JAVA_OPTS='-Xms128m -Xmx1024m -XX:MaxPermSize=128m -server'" >> $SCRIPTNAME

# Add classpath to the script
echo -n "java -classpath $APPSERVER/webapps/alfresco/WEB-INF/classes/alfresco/module:"  >> $SCRIPTNAME
echo -n "$APPSERVER/shared/classes:"  >> $SCRIPTNAME
echo -n "$APPSERVER/webapps/alfresco/WEB-INF/classes:"  >> $SCRIPTNAME

# List all libs
for FILE in $APPSERVER/webapps/alfresco/WEB-INF/lib/*
do
    echo -n $FILE: >> $SCRIPTNAME
done
# This is to get your db jar, you may hav to include other locations
for FILE in $APPSERVER/lib/*
do
    echo -n $FILE: >> $SCRIPTNAME
done

# Add the final export commands
echo -n -e " org.alfresco.tools.Export -user admin -pwd admin -zip -dir export -verbose -store \0044\0061 \0044\0062"  >> $SCRIPTNAME‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

The created script is the used calling it with 2 parameters, the store to export and the export file name
./export.sh workspace://SpacesStore spacesstore.acp
The created export package is saved in a subfolder called export.
Edit the resulting script to meet your needs. My script probably adds more jars than needed, but this was easier than manually figuring out what jars to use.
To create an import script, just change to org.alfresco.tools.Import instead in a copy of your script, and tweak the import options (untested at this time).

Now some questions
The complete repository export also exported export_systeminfo.xml and export_models.acp, this does not map to any content stores as far as i can see. Are they necessary to achieve a migration from one db to another, i.e do a bootstrap?
Is it supported to export/import avm://sitestore? I've been able to export, I've not had time to test an import. I can see that it at least can not be part of a bootstrap job.

Regards
Peter Löfgren

mcmagnus

Hi

Thanks for the script Peter, but do you know why the complete export was removed? I see it's on its way back in again for Labs 3e.

I also see the function is there in Labs 3c, but importing it back again into the same version fails. Perhaps this is why it was removed in the first place?