在 IBM WebSphere Portal 7 上使用 WSRP 远程呈现 WCM 内容
我们在不同的服务器上使用 WebSphere Portal 7 和 WCM 7。我们已经设置了 WSRP，以便可以在 Portal 服务器上呈现 WCM 内容。我遇到的问题是 JSR 286 Web 内容查看器的推荐设置（关闭动态链接广播功能）会破坏页面其余部分上的链接。如果我打开该功能，则其他链接可以工作，但 WCM 内容中的链接会失败。所有本地链接（到其他虚拟门户或映射的 URL）都被重写（由 Portal）以通过 WsrpProxyPortlet，即使没有必要这样做。
有没有一种方法可以在 Portal 7 和 WCM 7 上使用远程呈现，以便可以在同一页面上使用 WCM 和自定义 portlet，并且来自和到其中任一者的链接仍然有效？
我将排列和尝试每种排列的结果放在一起，不幸的是它的格式不正确，所以我将其粘贴为格式化文本。
+=======================================================================================================+
| Broadcast links to | Receive links from | Portal | WCM | Comment |
+=======================================================================================================+
| | Other portlets and | No | Yes | Portal links to the page with this |
| | this portlet | | | setting do not work |
| Dynamically select a +-------------------------------------------------------------------------------+
| Web content page | This portlet only | Yes | No | WCM Links do not work at all |
| +-------------------------------------------------------------------------------+
| | None | Yes | No | WCM Links do not work at all |
+=======================================================================================================+
| | Other portlets and | No | Yes | Portal links to the page with this |
| | this portlet | | | setting do not work |
| This portal page +-------------------------------------------------------------------------------+
| | This portlet only | Yes | No | WCM Links do not work at all |
| +-------------------------------------------------------------------------------+
| | None | Yes | No | WCM Links do not work at all |
+=======================================================================================================+
| | Other portlets and | No | Yes* | Portal links to this page do not work.|
| | this portlet | | | WCM and Portal links on this page |
| | | | | works, once you get to it. |
| The following portal +-------------------------------------------------------------------------------+
| page | This portlet only | Yes | No | WCM Links do not work at all |
| +-------------------------------------------------------------------------------+
| | None | No* | No | Portal links only work if in the |
| | | | | same context |
+=======================================================================================================+
| | Other portlets and | No* | No* | Neither Portal, nor WCM, links to the |
| | this portlet | | | page work as they should. You can |
| | | | | only get to the page through a |
| | | | | sequence of other pages. Once you get |
| | | | | to it WCM links work, but links to |
| None | | | | other Portal pages break. |
| +-------------------------------------------------------------------------------+
| | This portlet only | No | No | No way to get to this page. |
| +-------------------------------------------------------------------------------+
| | None | No* | No | Portal links to the page work, but |
| | | | | links from the page do not. |
+=======================================================================================================+
We are using WebSphere Portal 7 and WCM 7 on seperate servers. We have set up WSRP so that we can render the WCM content on the Portal server. The problem I am having is that the recommended settings for the JSR 286 Web Content Viewer (to switch the dynamic link broadcasting featuire off) breaks the links on the rest of the page. If I switch the feature on, then the other links work but the links in the WCM content fail. All the local links (to other virtual portals, or mapped URLs) are rewritten (by Portal) to pass through the WsrpProxyPortlet, even though it is not necessary to do so.
Is there a way to use remote rendering on Portal 7 and WCM 7, so that one can use WCM and custom portlets on the same page and the links from, and to, either will both still work?
I put a table together of the permutations and the results of trying each, unfortunately it does not format correctly so I pasted it as formatted text.
+=======================================================================================================+
| Broadcast links to | Receive links from | Portal | WCM | Comment |
+=======================================================================================================+
| | Other portlets and | No | Yes | Portal links to the page with this |
| | this portlet | | | setting do not work |
| Dynamically select a +-------------------------------------------------------------------------------+
| Web content page | This portlet only | Yes | No | WCM Links do not work at all |
| +-------------------------------------------------------------------------------+
| | None | Yes | No | WCM Links do not work at all |
+=======================================================================================================+
| | Other portlets and | No | Yes | Portal links to the page with this |
| | this portlet | | | setting do not work |
| This portal page +-------------------------------------------------------------------------------+
| | This portlet only | Yes | No | WCM Links do not work at all |
| +-------------------------------------------------------------------------------+
| | None | Yes | No | WCM Links do not work at all |
+=======================================================================================================+
| | Other portlets and | No | Yes* | Portal links to this page do not work.|
| | this portlet | | | WCM and Portal links on this page |
| | | | | works, once you get to it. |
| The following portal +-------------------------------------------------------------------------------+
| page | This portlet only | Yes | No | WCM Links do not work at all |
| +-------------------------------------------------------------------------------+
| | None | No* | No | Portal links only work if in the |
| | | | | same context |
+=======================================================================================================+
| | Other portlets and | No* | No* | Neither Portal, nor WCM, links to the |
| | this portlet | | | page work as they should. You can |
| | | | | only get to the page through a |
| | | | | sequence of other pages. Once you get |
| | | | | to it WCM links work, but links to |
| None | | | | other Portal pages break. |
| +-------------------------------------------------------------------------------+
| | This portlet only | No | No | No way to get to this page. |
| +-------------------------------------------------------------------------------+
| | None | No* | No | Portal links to the page work, but |
| | | | | links from the page do not. |
+=======================================================================================================+
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
提示：将浏览器指向 WCM 服务器，路径为 /wps/wcm/myconnect/WCM-library/content-path/。通过预览内容项获取示例路径。远程呈现只是使用 http 客户端并传递 LTPA cookie 向 servlet 请求内容。您还可以快速将链接重写为您的 portlet（或其他 portlet - 在其他门户页面上）的参数 - 即时。
这就是 IBM 用来实现官方远程渲染 portlet（至少在 6.1 上仍然可用）的方式，如果您再也找不到实际的非 wsrp 远程渲染 portlet，那么您可以很容易地自行构建。
Hint: Point your browser to the WCM server, at path /wps/wcm/myconnect/WCM-library/content-path/. Get example paths by previewing content items. Remote rendering is just asking that servlet for content, using http client and passing the LTPA cookie. You can also quickly rewrite the links to be parameters to your portlets (or other portlets - on other portal pages) - on the fly.
That's how IBM used to implement the official remote rendering portlet (available still at least on 6.1), and it's quite easy to build yourself if you can't find the actual non-wsrp remote rendering portlet anymore.