使用 websphere Portal 与 spring mvc（确定 portlet 解决方案是否有保证的指南）
我们正在开发第二代电子商务网站。引入的承包公司正在推动使用 WebSphere Portal，而不是使用 JSP/Spring MVC 等来构建 UI 部分。
新版本的许多部分将基于版本 1。
承包公司是 IBM 合作伙伴 - 因此我认为在确定 UI 的最佳解决方案时存在利益冲突。
因此，我正在联系该小组，了解使用 IBM WebSphere Portal 是否物有所值 - 投资回报率？
展望未来，一旦应用程序上线，我们将使用一家离岸公司来维护应用程序 - 因此我们必须考虑这些技能。
我们向发货人提供网站，允许他们出售/拍卖他们的车辆库存。每个发货人的底层业务逻辑几乎相同，并且在单独的层中处理。问题是，目前我们已经创建了一组核心 UI 和控制器，然后将其扩展到 Consignors 项目中。每个发货人“店面”都是单独的部署。
以下是我对 Portal 的了解或听说：
IBM WebSphere Portal OTB 将处理基本安全性 - 用户登录和他们可以看到的 portlet（Spring Security 可以做同样的事情）
IBM WebSphere Portal OTB 可以根据用户所在的公司处理主题或重新设计 portlet与 相关联。 （标准 UI 实践可以实现同样的效果）
IBM WebSphere Portal 可以提供 Portlet 的重用（不确定我是否购买此产品，因为到目前为止，每个客户都需要自己的屏幕布局以及收集的数据及其显示方式） ）
IBM WebSphere Portal 可以帮助缩短上市时间 - 即从基本参考实施开始，然后向他们展示在 45 - 60 天的周期内可以更改哪些内容。
我对任何能够提供更多使用好处的人持开放态度。
关注问题
回应@Bozho 的声明 - 确定 portlet 解决方案是否有保证的准则（如果有）是什么。
We are in the process of working on our second generation of our eCommerce site. The contracting firm that has been brought in is pushing for the use of WebSphere Portal vs using JSP/Spring MVC etc to build out the UI part.
Many parts of the new release will be based on Version 1.
The contracting firm is an IBM partner - so I assume that there is a conflict in interest in determining the best solution for the UI.
So, I am reaching out to the group to get a feel as to is using IBM WebSphere Portal worth the money - ROI?
Going forward we will be using an off shore company to maintain the application once it goes live - so we have to consider those skills sets.
We provide Web Sites to Consignors to allow them to sell/auction their inventory of Vehicles. The underlaying Business Logic is pretty much the same for each consignor and is handled in a separate tier. The issue is that currently we have created a core set of UI and Controllers which are then extended into a Consignors project. Each Consignor "Store Front" is a separate deployment.
Here is what I know or have been told about Portal:
IBM WebSphere Portal OTB will handle the basic security - user log in and the portlets that they can see (Spring Security can do the same thing)
IBM WebSphere Portal OTB can handle the theming or re-skinning the portlets based on what company the user is associated with. (Standard UI practices can achieve the same thing)
IBM WebSphere Portal can provide re-use of Portlets (Not sure I buy this since so far each customer has demanded their own screen layouts along with the data collected and how it is displayed)
IBM WebSphere Portal can help with time to market - That is start with a base reference implementation and then show them what can be changed in a 45 - 60 day turn around.
I am open to anyone who can also provide more benefits of its usage.
Follow on Question
In response to a statement made by @Bozho - what are the guidelines if any to determine if a portlet solution is warrantied.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
在我的脑海中，IBM 并没有引发任何有关高质量软件的良好参考。以上所有观点都是营销废话。您需要评估两件事：
我无法为您决定这些，但我可以告诉您：
IBM does not trigger any good references in terms of quality software in my head. And all points above are marketing nonsense. There are two things you need to assess:
I cannot decide these for you, but I can tell you that:
这完全取决于你的最终游戏是什么。
看起来供应商推荐了 Websphere Portal，旨在为每个委托人设置一个虚拟门户 - 这样它们就可以单独管理，这是有道理的，因为您可以在每个虚拟门户中部署相同的 portlet，并进行一些自定义和委托人和用户角色也可以通过开箱即用的门户轻松处理。
然而 Portal 是一个相当大的套件。如果您想要集成来自不同来源的内容并根据最终用户的角色等以标准方式向最终用户呈现数据，或者您计划使用其某些现有功能，即在同一页面上动态更新 portlet通过事件、Web 内容库、与远程 Portlet 集成、与协作工具集成、与流程服务器/bpm 任务、博客、wiki 等集成，那么可能值得使用门户解决方案。
然而，如果您想做的只是创建一个 Web 应用程序，那么 Portal 完全是多余的，我只会坚持使用任何框架的应用程序服务器，使工作变得更容易
It entirely depends on what your end game is.
It looks like the supplier has recommended Websphere Portal with a view to setting up a virtual Portal for each Consigner - so they can be managed separately, which make sense as you can just deploy the same portlet in each virtual portal with a bit of customization and also the consigner and user roles can be handled easily by portal out of the box.
However Portal is a pretty big piece of kit. If you want to integrate content from various sources and present the data in a standard way to the end user based on their role,etc, or it you're planning on using some of its existing functionality, i.e. dynamically updating portlets on the same page through events, Web Content library, integration with Remote Portlets, integration with collaboration tools, integration with process server/bpm tasks, blogs, wikis, etc, then it might be worth using a portal solution.
If however all you want to do is essentially create a web app, then Portal's total overkill and I'd just stick to an app server with whatever frameworks make the job easier