Webcenter 中的本地 portlet
我开始使用 webcenter 10.3.5（最新版本）开发一个门户，据我所知，我只能通过 WSRP 使用 portlet，即使它们是本地的。我不想引发性能问题，因此我尝试寻找本地 portlet 的替代方案来维护 webcenter 的自定义功能（例如，将删除 portlet 添加到 webcenter 编辑器中的页面）。就我而言，维持 portlet 范例并且同时不会引发性能问题的最佳解决方案是什么？
附带说明一下，我已经进行了一些调查，并且我知道我可以将 ADF 任务流公开为 portlet，目前我认为这是唯一的方法。我想知道是否还有另一种方法可以做到这一点...
更详细地说明一下，我们正在设计的门户是一个针对拥有合理数量客户的电信公司的自助门户。大多数时候，他们不会进行长时间的交易，他们希望完成一些任务，例如给手机充值、发送短信、交换定价计划等。从业务角度来看，他们希望在此门户和其他门户之间共享 portlet他们有。我的第一个（也可能是乌托邦）方法是将所有内容都视为 portlet，因为所有需求都是在设计时考虑到这一点的，即所有内容都应该是可重用的。然而，我很难找到在 webcenter 中仅使用通过 wsrp 协议访问的 portlet 构建的网站的在线参考。我们还要求某些 Portlet 的出现应遵循一些因客户端而异的规则，因此一切都将非常动态。此外，在某些情况下，他们希望通过 Webcenter Composer 配置页面应显示的 portlet。考虑到所有这些，我想知道考虑一种所有内容都由 wsrp portlet 组成的方法是否合理。从我的角度来看，另一种选择是进行混合，即某些部分是通过 wsrp 协议访问的 portlet，即外部 portlet，其他部分是任务流，也可以通过 webcentercomposer 进行组合
I'm starting to develop a portal with webcenter 10.3.5 (latest version) and from what I could gather I can only consume portlets through WSRP even if they are local. I would not like to incur in performance problems so I'm trying to find alternatives for local portlets maintaining the customization capabilities of webcenter (add remove portlets to a page in webcenter composer for example). In my case what is the best solution to maintain the portlet paradigm and at the same time do not incur into performance problems ?
As a side note I have made some investigations and I know that I can expose ADF taskflows as portlets, for now I think it's the only way. I was wondering if there's another way of doing it...
Giving a little more detail the portal that we are designing is a selfcare portal for a telecommunications company that has a reasonable number of customers. Most of the time they will not engage in long transactions, they want to accomplish some task like topping up a cell phone, send an SMS, swap pricing plan etc. From a business point of view they want to share portlets between this and other portals that they have. My first and probably utopic approach was to consider everything as a portlet, since all the requirements were designed with that in mind, i.e. everything should be reusable. However I'm having a hard time finding online references for sites that were built like this in webcenter using only portlets accessed through the wsrp protocol. We also have requirements that state that some portlets should appear according with some rules that change from client to client so everything will be very dynamic. Also in some cases they want to configure via webcenter composer the portlets that a page should display. Considering all of this I'm wondering if it's reasonable to consider an approach were everything is composed with wsrp portlets. The alternative from my point of view is to do a mix i.e. some parts are portlets accessed through the wsrp protocol namely external portlets the others are taskflows which can be also composed also through webcenter composer
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
根据您的问题（谈论 WSRP 和 ADF），我假设您正在谈论 网络中心门户。为清楚起见，WebCenter Portal 的当前版本是 11.1.1.4< /a>（11g 补丁集 3）。
至于您关于 portlet 和其他可重用组件的问题：
WebCenter Portal 没有本地 portlet 概念，所有 portlet 都是远程的，并且可以通过 WSRP 访问。这是有益的，因为您可以独立于门户（消费者）扩展您的 portlet。同时，还存在一定量的开销（这似乎是您所关心的）以及管理的复杂性。当使用该产品的最新版本时，我不会过度担心 WSRP 开销。
但是，如果这对您来说是一个主要问题，您始终可以考虑使用本机 ADF 任务流。这些是本地组件，执行它们时没有 SOAP 开销。同时，它们按顺序执行（与并行运行的 portlet 不同）。
正如您在问题中提到的，您也可以将 ADF 任务流公开为 JSR 286 portlet（同样，通过 WSRP 2.0 进行远程使用）。
在这里您还可以找到一些关于该主题的有用数据帖子。
希望这有帮助...
Based on your question (talking about WSRP and ADF) I assume you're talking about WebCenter Portal. Just for clarity, the current version of WebCenter Portal is 11.1.1.4 (11g Patch Set 3).
As for your questions on portlets and other reusable components:
WebCenter Portal doesn't have a local portlet concept, all portlets are remote, and can be accessed through WSRP. This is beneficial, because you can scale out your portlets independently of your portal (consumer). At the same time, there's a certain amount of overhead (and this is what you seem to be concerned about), as well as management complexities. When using such a recent version of the product, I wouldn't be overly concerned about the WSRP overhead.
However, if this is a major issue for you, you can always consider using native ADF task flows. These are local components, no SOAP overhead when executing them. At the same time, they're executed sequentially (unlike portlets that are running in parallel).
And as you mentioned in your question, you can expose ADF task flows as JSR 286 portlets as well (again, for remote consumption through WSRP 2.0).
Here you find a couple of useful data posts as well on the topic.
Hope this helps...