Cq im Yasni Exposé von Lorenzo Peroni

Steve, Hopefully the following can answer some of your questions. In the simplest case, a CQ environment needs two application servers and one webserver. 1. The first application server is the CQ Author Instance where users enter content, developers develop templates etc. (though in real life you will want to separate content maintenance from development by having several environments, e.g. development, staging and production environments, but I am speaking of the simplest case here). 2. The second application server is the CQ Publish instance which is -- simplistically seen -- exactly the same as the CQ Author Instance minus the editing capabilities. The content is delivered here by "activating" it from the CQ Author Instance (of course some once-off configuration is required first); the templates are usually delivered via "packages". 3. The third server is the webserver, i.e. Apache or IIS, with the Dispatcher module added. The webserver/Dispatcher combination caches static content delivered by the CQ Publish Instance (such as finished HTML pages) for faster delivery. For dynamic content, you will need some special configuration or programming to prevent unwanted caching. In any case, the process is automatic (apart from a once-off configuration). You do not need to put content on the Dispatcher's web server. Setting up these three servers is covered very well on docs.day.com, but as it is often the case with complex software, there are some subtleties that can be time-consuming when you encounter them for the first time. You might want to try installing and configuring the "Playground" (delivered with the CQ software) on a separate environment before you tackle the production environment. The best way to reach that December 15 deadline, though, would be to call in outside help, either from Day themselves or from specialised CQ consulting firms in your area. Regards, Lorenzo _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ namics ag - ein Unternehmen der PubliGroupe Teufenerstrasse 19 9000 Sankt Gallen Switzerland Lorenzo Peroni Senior Consultant t +41 71 2286-758 m +41 79 4490565 f +41 71 2286-788 mailto:lorenzo.peroni@... http:/ /www.namics.com _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Die nächste namics-Fachtagung: » Alles, was Sie über Content Management Systems wissen müssen: 20.01.05, 13-17 Uhr Kostenlose Anmeldung unter http://www.namics.com/cms-fachtagung Fachs eminar von Comicro-Netsys AG: » Microsoft SharePoint Server - so wird er in der Adval Tech Gruppe genutzt: 26.01.05, 14:30 Uhr Kostenlose Anmeldung unter http://www.comicro.ch

Hello Leo, I can't be sure about 3.5.0, but here's how I did it in 3.5.4. In /c(Gefiltert);) the user somewhere else, e.g. a static error page. But there are no limits to what you can do, e.g. show a different error page for different URLs or even try a best-match algorithm to "guess" what the user wanted. I, for one, find it useful to catch URLs without ".html" or ending in "/" via the error handler, then redirect the user to the same page again with ".html" added. Have fun experimenting. Best regards Lorenzo _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ namics ag - ein Unternehmen der PubliGroupe Teufenerstrasse 19 9000 Sankt Gallen Schweiz Lorenzo Peroni Senior Consultant t +41 71 2286-758 m +41 79 4490565 f +41 71 2286-788 mailto:lorenzo.peroni@... http:/ /www.namics.com _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Fachseminar von Comicro-Netsys AG: » Microsoft SharePoint Server - so wird er in der Adval Tech Gruppe genutzt: 26.01.05, 14:30 Uhr Kostenlose Anmeldung unter: http://www.comicro.ch