What I rather suspect based on our own experience that when someone gets involved developing a portal, they keep a log or journal documenting the experience. At least that we did because at certain times you can run into a problem and once it gets resolved, you write it down out of fear of forgetting what it was you did to fix it. These type of notes are really not in a ready to use form or organized for publishing. My notes kind of look like a blog.
I would envision not a book for beginners or even advanced developers because one really needs to be fairly welled healed in architecture and design when it comes to integration of open source products at this level. When I look at my notes, they do not document the Apache, Tomcat or MySQL. It documents that space between each package and our approach was of course to take the path of least resistance. For example, once we had Jetspeed running and a base set of portlets, we integrated Zope as our CMS. We tested this out thoroughly and then stopped to do the necessary administration and configuration to make the entire enterprise portal run securely. This means we had to rebuild Apache with mod_jk among a number of other things and in order to do this the documentation is found to be distributed all over the place with respect to Tomcat, Zope, etc. A very time consuming task to run it down let alone read it. The actual deployment of open source packages are made easy by the community. I guess you have to define what a "beginner" is at this level of work as most folks I have worked with can get the packages deployed without much trouble, but the real test of your skill is following through on your architect's specification is to integrate. This is where the real risk happens to be because so many times you post on a news group only to find out that no has tried to do a certain configuration before. When you stop and look at how many different ways people are building Jetspeed portals, there are probably more configurations than there are Linux distros. But the most common base consisting of Apache, Tomcat, Jetspeed, MySQL, Velocity/JSP etc., could be considered the beginners section of a book. Beyond that my wish list of content probably is not going to be the same as yours. I ended up architecting an integration of Zope and most recently including Zope Products such as Squishdot and Silva. The unanswered questions that makes one apprehensive about investing the time and money into such a combination of packages such as "will the ZServer and Zope database live happily with everything else" or "what code if any is going to be required on the back-end". Zope is more complex because most of the things that you can think of that are needed come in the form of Zope Product add-ons. I would say these things are the intermediate level of skill that a book should support. Unfortunately, another company might be building an entirely different implementation of CMS and publishing and so my list is irrelevant for them. Monitoring the Zope news groups you see book requests coming from the opposite direction. They typically are wondering what type of portals could host or support their implementation. An advance section of a book may address things like scalability such as Tomcat clustering, migration to higher end hardware platforms, performance and rigorous quality assurance testing. It would be nice if there was one on-line location where people could post or share their journals through taxonomy or ontology representing all the open source packages used in the deployment. It would seem more useful to me as I do not have the time to take the notes and write them up for a formal publication. At some point we are going to have to formally document our implementation because some customers are going to want it in-house and when we do that, the journal is going to be a key point of reference that tells me why we did the things the way we did. Cheers, John Wubbel Securitydirector, LLC On Sat, 2004-01-10 at 09:51, karthikeyan wrote: > I think the free download, accompanying document, method of > installation, seeing the first screen > is enough to explore further in jetspeed. Generally books STOP there, > (first 300 pages) > if one really want to learn/contribute then SRC (downloadable) is the > best. > Additional knowledge of > a) MYSQL (or any database) ( 10 page) > b) TOMCAT (or any webserver) (10 page) > c) JDK (or 1.4+) 'caution: deprecation' (10 page) > d) Frontpage (or equivalent) for html/jsp (10 page) > e) Operating System (Linux, windows, etc) (10 page) > f) ant (3 pages) > g) SOAP (2 pages) > h) jportal (com.bluesunrise.*) > (http://www.bluesunrise.com/jetspeed-docs/PortletHowTo.htm) > ... > ... > ... > (may be some one can complete the list ! to know others especially the > beginners... what is missing) > > > TurbineResources.properties (3 pages) > Torque.properties (2 pages) > Portlets (5 pages) pl. see the above link (my wish: Link should not DIE > at all) > ....... for "hello world portlet " > > with the above information I think 75% book is complete > I would like to read such a book .. (some one can invest on this) with a > price $$$ TAG > > It is my personal opinion... pl. ignore if something wrong... > > > > > > > > -- > M. Karthikeyan, Ph.D., Scientist > _| _| _|_|_| _| > _|_| _| _| _| > _| _| _| _| _| > _| _|_| _| _| > _| _| o _|_|_|o _|_|_|_| > National Chemical Laboratory > Pune - 411 008, INDIA > Ph: +91-(0)20-5893 457 FAX: 5893 973 > http://www.ncl-india.org/ > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
