WQS Sample application for Production use

[unknown-user]

Hi All,

We are evaluating WQS sample application for a Production usage. So far it looks promising, however, we are not sure if it can be  used in a Production environment. Following are few questions that we have.

a) How is authentication &authorization handled in WQS?
b) Can it support a SSO with passthru authentication against alfresco repository?
c) How will role based content work? We have users from different teams using the site for whom the content needs to be served differently.
d) Is there anything special needed to be done for a mobile access. I know its site specific, but is there any limitation from WQS implementation perspective?
e) How about the performance especially with the dynamic assets and cron jobs getting executed against the repository.

Any thoughts/suggestions are appreciated.

Thanks for your help

[resplin]

Here are the information I can provide.

a) How is authentication &authorization handled in WQS?
b) Can it support a SSO with passthru authentication against alfresco repository?
c) How will role based content work? We have users from different teams using the site for whom the content needs to be served differently.

WQS is generally used for use cases that do not require login. It is a great tool for publicly publishing content that is authored using Alfresco Share. I have not previously tried to use WQS for role based content or limited access content. Instead I would pull content from a real web portal front-end like Liferay, or a custom site built with a web framework like Django.

d) Is there anything special needed to be done for a mobile access. I know its site specific, but is there any limitation from WQS implementation perspective?

I am not aware of anything special than needs to be done. The default templates look pretty good on a mobile device and you can customize the templates to be fully responsive if you would like.

e) How about the performance especially with the dynamic assets and cron jobs getting executed against the repository.

WQS performs pretty well under load. Some of our customers are running large sites using it. If necessary, WQS can be scaled using a cluster of read-only Alfresco repos to handle responses to dynamic requests. Proper caching on the front-end is also often used to manage load.

I know we have a few customers using Web Quick Start in production. The team at Tribloom (http://www.tribloom.net/) have done most of the implementations that I am aware of. I would recommend contacting them for further information. I know they sometimes answers questions in the forums as well.

[mccarthymp]

a) How is authentication &authorization handled in WQS?

The short answer is, it isn't. There is no built in authentication to WQS. It was designed to be more of a web site than a web application. You could certainly add authentication to WQS if you like, it "talks" to the repository using CMIS.

b) Can it support a SSO with passthru authentication against alfresco repository?

That's a good question. You probably could make that work after solving a). I would suggest looking at Share SSO as the solution for WQS should be similar.

c) How will role based content work? We have users from different teams using the site for whom the content needs to be served differently.

This should work fine as long as you have users who can authenticate. Alfresco will only provide the results that the user has access to.

d) Is there anything special needed to be done for a mobile access. I know its site specific, but is there any limitation from WQS implementation perspective?

This would all be done with CSS. You can modify the CSS for any of the themes specifically for mobile.

e) How about the performance especially with the dynamic assets and cron jobs getting executed against the repository.

You can configure how frequently the repository is checked for dynamic asset updates. We have never had any issue with it although the websites have not been large.