Liferay Portal：与 Websphere Portal 有何不同
我曾使用过 Websphere Portal 6.0、6.1 并使用 JSR 168、JSR 286 Portlet 开发门户应用程序。
现在我正在转向使用 Liferay 门户服务器和 JSR 168、JSR 286 的项目。
我知道根据编程接口 (JSR) 它将是相同的。但想知道与 Websphere Portal 相比，服务器级别（功能、配置、体系结构、开箱即用服务）的主要区别是什么？
谢谢
I have worked with Websphere Portal 6.0,6.1 and developed portal applications usign JSR 168,JSR 286 Portlets.
Now I am moving to project where I will be working with Liferay portal server and JSR 168,JSR 286.
I know that as per programming interface (JSRs) It will be the same. But want to know what are the major difference at server level ( features,configuration,architecture, out-of-box services) when compared to Websphere Portal ?
Thanks
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
Liferay 还支持 JSR168 和 JSR286 portlet，因此您可以使用与 WebSphere Portal 中相同的 API。该产品本身不能轻易与 WPS 进行比较，因为它们具有不同的概念。例如，Liferay 没有凭证库，但它仍然支持 SSO（NTLM 或 CAS）。您的 WebSphere Portal 知识对 Liferay 开发没有多大帮助，因为它是一个完全不同的产品。
Liferay also supports JSR168 and JSR286 portlets, so in respect to that you can use the same API's as you are using in WebSphere Portal. The product itself cannot be easily compared to WPS as they both have different concepts. Liferay doesn't have a credential vault, for example, but it still supports SSO (NTLM or CAS). Your WebSphere Portal knowledge won't help you much in Liferay development, as it is a totally different product.
我同意配置会有所不同，但我认为这会很有帮助，因为您准备好考虑信息架构。
主要区别在于 Liferay 并没有为可扩展性做好充分准备。它使用速度，因此您使用的任何标签都没有帮助（占位符、组件、元素等）。
默认情况下它没有那么多 portlet，因此您必须从起点开始进行大量开发。
检查一下这个，以获得非常好的比较（幻灯片是西班牙语的，并且需要 flash 插件）：
http://www.slideshare.net/mcimino/websphere-portal-vs-liferay-by-gartner-v10
基本上Liferay的弱点在于B2C和支持。如果您需要构建一个严重依赖个性化的网站，您也将有很多工作要做。
希望有帮助
I agree the configuration will be different but I think it will help a lot the fact that you are prepared to think about the information architechture.
The main difference is that Liferay is not really that much prepared for escalability. It uses velocity so neither of the tags you use will help (Placeholders, component, element, etc).
It doesnt have that many portlets by default so you will have to develop a lot from the starter point.
Check this out for a really nice comparision (the slides are in spanish, and require the flash plug-in):
http://www.slideshare.net/mcimino/websphere-portal-vs-liferay-by-gartner-v10
Basically Liferay weaker points are in B2C and support. If you need to build a site that will rely heavily on personalization, you will have much work to do too.
Hope it helps