topic Standalone tomcat in Alfresco Archive

Standalone tomcat

boneill — Mon, 29 Nov 2010 05:38:20 GMT

Hi everyone,We have WCMQS up and running and have created our own site called seed with sections and collections mapped for our website. It all works fine if our surf (wcmqs webapp clone) webapp is installed on the alfresco tomcat instance. I have installed a tomcat 6 version as a standalone versi

Re: Standalone tomcat

bremmington — Mon, 29 Nov 2010 08:55:00 GMT

The configuration you need to override is described in the WQS Developer Guide here: http://wiki.alfresco.com/wiki/Web_Quick_Start_Developer_Guide#Configuring_the_API

Please would you let me know if this provides the answer? If not then I'll try to clarify it.

Re: Standalone tomcat

boneill — Mon, 29 Nov 2010 09:30:44 GMT

Hi,

Thanks for the fast reply. I am running an additional tomcat instance (tomcatseed) on the same server as the repository. So the alfresco tomcat instance is still referenceable via http://localhost:8080/alfresco. The entries in the wcmqs-api.properties are below which is as is out of the box. So I am assuming that the tomcatseed tomcat instance should be able to pick everything up as defined in the alfresco tomcat instance. :

/tomcatseed/webapps/seed/WEB-INF/classes/alfresco/wcmws-api.properies

#
# WCM QS configuration properties
#
wcmqs.api.alfresco=http://localhost:8080/alfresco
wcmqs.api.user=admin
wcmqs.api.password=admin

wcmqs.api.alfresco.cmis=%{wcmqs.api.alfresco}/service/cmis
wcmqs.api.alfresco.webscript=%{wcmqs.api.alfresco}/service/api/

#Type of asset factory to use. Either "cmis" or "webscript" (case-sensitive)
wcmqs.api.assetFactoryType=webscript
#wcmqs.api.assetFactoryType=cmis

The seed webapp is still not resolving a connection back to the alfresco tomcat repository to get its data. Is there anything else I need in the tomcatseed tomcat server.

Regards

Brian

Re: Standalone tomcat

bremmington — Mon, 29 Nov 2010 10:49:09 GMT

If your Alfresco tomcat instance is running on port 8080 then this config should work. What exactly are you seeing? Have you changed the host/port metadata on the website nodes in Alfresco ("Quick Start Editorial" and "Quick Start Live")?

Re: Standalone tomcat

boneill — Mon, 29 Nov 2010 12:09:20 GMT

Hi Brian,

I changed the port in the live version to use point 9090 which now matches the editorial version (as you suggested). Do both the live and editorial versions need to have the same port configured? I restarted tomcat a couple of times after doing this and then it suddenly just started working. Is there some caching going on in the surf or webscripts that needs to be cleared when you set the port or change the webapp context. Seems funny it just started to work.

Regards

Brian

Re: Standalone tomcat

bremmington — Mon, 29 Nov 2010 12:34:15 GMT

No, there's no need for editorial and live to be on the same port (or host). There is a cache of websites in the web app, but the logic is that if a request misses the cache then the cache is reloaded. This is done because it is deemed unlikely that a request would end up hitting the WQS web app "by accident", so it's worth checking that the repo hasn't been updated.

I'm not sure what would have caused it to start working suddenly, but I'm glad that it has

Re: Standalone tomcat

boneill — Mon, 29 Nov 2010 21:38:59 GMT

Brian,

Thanks once again for your help and explanations. As you said, at least it now working.

Regards