Export in 3.0

loftux — Wed, 07 Jan 2009 10:32:15 GMT

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

Re: Export in 3.0

mcmagnus — Wed, 21 Jan 2009 14:26:53 GMT

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?

Re: Export in 3.0

ganesh_boil — Mon, 11 May 2009 04:54:46 GMT

Hi Loftux ,
thanks for ur script.
But i'm just getting confusion with it. Can you provide the details to execute this script on windows machine.
My environment is :

Alfresco labs 3.0 with inbuilt DB (derby)
OS: Windows

Please provide the steps to execute this script in windows machine. So that it will be more helpful than this.

Thanks for your support.

Re: Export in 3.0

loftux — Mon, 11 May 2009 18:36:25 GMT

Unfortunately I do not have access to a Windows environment to create an equivalent windows script.
So the one I created only runs on linux.

Re: Export in 3.0

mjdinsmore — Tue, 05 Oct 2010 13:14:42 GMT

Thanks for the script. Should this standalone script/tool work better than the built-in export tool that's in Alfresco 2.1? By that, I mean does it work more reliably than the web interface tool (<i>I know it uses the same codebase</i>)? If I run the tool on a small space it works fine, but if I run it on a larger one, it will just quit on me (I haven't profiled it yet to see if it's memory constraints or some other problem). I suppose the standalone tool might be easier to debug when problems arise

In the meantime, I'll try to figure out why it fails to run for me – it's giving me a RMI port already bound exception. Should this be run on a different machine than the Alfresco server?


8:07am dinsmore@foobar # ./export.sh workspace://myspace myspace.acp
Alfresco Repository Exporter
log4j:WARN No appenders could be found for logger (org.springframework.core.CollectionFactory).
log4j:WARN Please initialize the log4j system properly.
The following error has occurred:
Error creating bean with name 'serverConnector' defined in class path resource [alfresco/core-services-context.xml]: Invocation of init method failed; nested exception is java.io.IOException: Cannot bind to URL [rmi://localhost:50500/alfresco/jmxrmi]: javax.naming.NameAlreadyBoundException: alfresco/jmxrmi [Root exception is java.rmi.AlreadyBoundException: alfresco/jmxrmi]
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'serverConnector' defined in class path resource [alfresco/core-services-context.xml]: Invocation of init method failed; nested exception is java.io.IOException: Cannot bind to URL [rmi://localhost:50500/alfresco/jmxrmi]: javax.naming.NameAlreadyBoundException: alfresco/jmxrmi [Root exception is java.rmi.AlreadyBoundException: alfresco/jmxrmi]
Caused by: java.io.IOException: Cannot bind to URL [rmi://localhost:50500/alfresco/jmxrmi]: javax.naming.NameAlreadyBoundException: alfresco/jmxrmi [Root exception is java.rmi.AlreadyBoundException: alfresco/jmxrmi]
   at javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConnectorServer.java:804)
   at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:417)
   at org.springframework.jmx.support.ConnectorServerFactoryBean.afterPropertiesSet(ConnectorServerFactoryBean.java:168)
   at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1118)
   at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1085)
   at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:429)
   at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:250)
   at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:141)
   at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:247)
   at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:161)
   at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:270)
   at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:346)
   at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:92)
   at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:77)
   at org.alfresco.util.ApplicationContextHelper.getApplicationContext(ApplicationContextHelper.java:55)
   at org.alfresco.tools.Tool.initialiseRepository(Tool.java:246)
   at org.alfresco.tools.Tool.start(Tool.java:212)
   at org.alfresco.tools.Export.main(Export.java:65)
Caused by: javax.naming.NameAlreadyBoundException: alfresco/jmxrmi [Root exception is java.rmi.AlreadyBoundException: alfresco/jmxrmi]
   at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:122)
   at com.sun.jndi.toolkit.url.GenericURLContext.bind(GenericURLContext.java:208)
   at javax.naming.InitialContext.bind(InitialContext.java:400)
   at javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:625)
   at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:412)
   … 16 more
Caused by: java.rmi.AlreadyBoundException: alfresco/jmxrmi
   at sun.rmi.registry.RegistryImpl.bind(RegistryImpl.java:123)
   at sun.rmi.registry.RegistryImpl_Skel.dispatch(Unknown Source)
   at sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.java:386)
   at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:250)
   at sun.rmi.transport.Transport$1.run(Transport.java:159)
   at java.security.AccessController.doPrivileged(Native Method)
   at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
   at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)
   at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790)
   at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649)
   at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
   at java.lang.Thread.run(Thread.java:619)
   at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:255)
   at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:233)
   at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:359)
   at sun.rmi.registry.RegistryImpl_Stub.bind(Unknown Source)
   at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:120)
   … 20 more

27.507u 0.937s 0:17.08 166.4%   0+0k 0+0io 38pf+0w

‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Re: Export in 3.0

loftux — Tue, 05 Oct 2010 13:35:13 GMT

I know I ran this locally (on the same server), so it should work. But its been a while since.

topic Re: Export in 3.0 in Alfresco Archive

Export in 3.0

Re: Export in 3.0

Re: Export in 3.0

Re: Export in 3.0

Re: Export in 3.0

Re: Export in 3.0