We’ve had a chance to play around with the Ingres/Alfresco bundle a bit more. One of the first things we did was install the WCM extension, which was easier than I imagined. Here are the steps:

  1. Download the WCM extension (zip or tarball) for Alfresco Community 2.1.0.
  2. Extract the archive into the installation directory for the bundle.
  3. Move wcm-bootstrap-context.xml to <install directory>/apache-tomcat/shared/classes/alfresco/extension.
  4. Edit virtual_alf.sh to set APPSERVER to the virtual-tomcat directory.
  5. If it isn’t already set, set JAVA_HOME.
  6. Start the bundle, and then the virtual Tomcat (using virtual_alf.sh).

In summary, installing WCM for the Ingres/Alfresco bundle is basically the same as installing it for any other installation of Alfresco. The only issue we’ve run into so far is that deployment won’t work. We’re investigating this.

By the way, I’m not actually typing this entry — I’m dictating it to a co-worker. I got into a bike accident and sprained my right wrist. It could have been worse; I was wearing my helmet. The moral of the story? Always practice bike safety. =)

Update (June 12, 2008): We managed to figure out what was causing the deployment problems. The RMI calls were failing due to a mis-configured hosts file. The final message in this thread on RMI in the Spring Framework ended up being the answer to the problem. A lot of time spent, but now we now that WCM can be installed to the bundle and that the major features work — we had a chance to try the virtualization features as well and they seemed to be working.

Special thanks to David Maier from Ingres for all of his help! =)

Tags: , , ,

This entry was posted on Tuesday, June 3rd, 2008 at 3:17 pm and is filed under Alfresco, Content Management. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.