Separating WQS Editorial and Live into different nodes

[nwywong]

I have imported the web quick start, which has an editorial and live sites. The sites are virtually separated but physically located on the same server. Can I physically separate them into different nodes?

[leonardo_celati]

I am not sure I understood correctly, because they already are different nodes. So I am trying to interpret your question.

1) if you are using WCMQS web app, or any other cmis/webscript app and you mean if they can be located at different URL, the answer is yes. Juts go to the web site folder and change the host name and port.

2) if you mean that you want to pass from the default configuration:

WebSiteRoot
                +—AlfrescoWebQuickStart
                                         +— editorial
                                         +—publishing
‍‍‍‍‍‍

to this configuration:

WebSiteRoot
               +— editorial
               +—publishing
‍‍‍‍‍

The answer is yes. If you have question regarding this, well, just ask.

3) if you mean that the editorial and publishing folder can be located on different Alfresco Installation, I think you cannot do this, with the default wcmqs mechanism, unless you rewrite some part of the code.

[nwywong]

Thanks for your reply.
In fact, I am meaning somewhat like your third point. I would like to have the traditional DEV, UAT & Production concept, and separate the non-production environment and production environment to two different servers - after the folder / its files are reviewed in the UAT environment, it is being published to the production environment.

[leonardo_celati]

Ok, so I am thinking about <a href="http://wiki.alfresco.com/wiki/FTR">FTR</a>.
You can use it for transferring files to a remote (or local) file system, or via replication to another Alfresco Instance. I am using to transfer all the static content such as CSS, JS or images to a remote Apache Http folder.

However, at this point I suppose that remote Alfresco doesn't need a WCMQS, but instead you could prepare a few Web Scripts or CMIS services that serve content.