Monday, February 28, 2011

Configuring Alfresco Community Edition for OpenOffice Document Transforms

this is for alfresco version 3.4.d

have been getting an error similar to the following after configuring a rule in alfresco for converting documents from MS formats to Open Document formats:

Failed to run Actions due to error: 02050010 Transformer for 'application/msword' source mime type and 'application/pdf' target mime type was not found. Operation can't be performed

since I'm now having to dig for the second time on this, figured I'd write it down.

See the following pages:

http://wiki.alfresco.com/wiki/Setting_up_OpenOffice_for_Alfresco (most details)
http://wiki.alfresco.com/wiki/Repository_Configuration (location of the .properties file)

the long and the short of it is this:

find the location of the "alfresco-global.properties" file

[root@OPS5-Alfresco ~]# locate alfresco-global.properties
/opt/alfresco-3.4.d/tomcat/shared/classes/alfresco-global.properties

if you open this file, look for the following line:

ooo.enabled=false

change to true using your favorite editor (vi, nano, etc)
restart alfresco

service alfresco restart (bounces tomcat and mysql)

to know when the alfresco system is up, use "tail -f /opt/alfresco-3.4.d/tomcat/logs/catalina.<date>.log" and look for the line:

INFO: Server startup in 136056 ms

this will confirm that when alfresco starts, OpenOffice will be started with the service and able to convert documents.  Happy uploading!

1 comment:

  1. Hi there, found your blog while having some issues with an Alfresco 3.4.d Community Edition. You seem to be playing around with alfresco also quite a bit so I hope to find some answers here which I can not find anywhere on the badly supported alfresco forum.
    We are running an Alfresco instance (3.4.d) and try to run a bulk import of 140.000 files via FTP or CMIS but no matter how much memory we assign to the JVM (tried up to 5G) we always run either into Out Of Memory exceptions or the Alfresco service just doesn't react anymore after a certain time. It seems the lucene indexing just grabs more and more memory and finally causes the JVM to die.

    We tried running Alfresco in CentOS 5.6 and Windows Server 2008 R2, in both OS we manage to kill Alfresco after sending in about 5000 files via CMIS webservice interface (10 Threads) or about 20000 files via 10 FTP threads.

    Any ideas would be highly appreciated

    ReplyDelete