I wouldn't start by choosing OS and DB, and then the software. I'd start by nailing down the requirements (including scalability), and then selecting software to support it, and only then selecting hardware that can run the software adequately.
100K concurrent users is a big number for a portal, certainly if any kind of customization/personalization is possible. Be prepared to spend serious money for multiple servers.
I18N is something every decent portal does these days, although that goes into the domain of CMSes. In addition to the ones Cameron mentioned, Alfresco is another option in the open source space.
What does "a response time of 7 seconds between the user requests" mean? Does it mean that each of the 10K concurrent users will submit a request every 7 seconds? Or that the server needs to respond to a request within 7 seconds? Or that requests will not come in faster than once every 7 seconds? Something else?
This is important to get right for planning the scalability - 10K concurrent users is a large number. As a very rough estimate, for a highly customizable site (something FaceBook-like) a single server probably won't be able to service much more than 100 requests per second (maybe more if you implement a lot of intelligent caching - which a free portal may not help you with). So if there is a 7 seconds limit in response time, I'd say you're looking at 15 servers to start with (assuming that "10K concurrent users" really means 10K users accessing the site at the same time). [ July 24, 2008: Message edited by: Ulf Dittmer ]
I don't have experience with JetSpeed 2 -I did work with JetSpeed 1, though, which wasn't exactly fast- but in general I see no unsurmountable problems with the software side, provided you get a handle on the scalability issues.
Since we are going to develop a social networking portal similar to Facebook, will LifeRay a good choice? We deal with lot of images/videos between the portal and cell phones.
Here is what comparision study i made on open source portal softwares:
1. Supports Linux and MySQL 2. Supports multilanguage 3. Good security features 4. WML support 5. Supports most of the browsers
LifeRay Portal 4.2:
1. Supports Linux and MySQL 2. Out of the box social networking features 3. Supports most of the browsers 4. Ability to share LifeRay application thro' Facebook or any website 5. But security features not as good as JetSpeed.
Finally we decided to use Jetspeed 2 as our portal server. Now we are left with making a choice on framework that best fits our application.
Amoung the Struts 2 and spring, which one is better? I've used a company proprietaty framework which is similar to struts framework in my earlier company. But very much NEW to spring. Jetspeed supports both of these frameworks.
Now given a choice between these two, which will be better? Any suggestion in this regard is highly appreciated.
Struts and Spring are two totally independent frameworks (struts is mostly frontend crap, while spring is everything; the swiss army knife of frameworks). One thing you might do with Spring may not even cover what can be done with Struts. So if you have a personal preference to passing things forward with the struts framework then go with both. [ August 12, 2008: Message edited by: Ray Carrender ]