There are two easiest way from which we can achieve this things.
1. IFrame
2. WSRP
1. IFrames:
- This is one of the easier options
- It is very useful when you have lots of things to expose or to display third party data.
- It provides loose-coupling between Portal and Cognos so as reports change the Portal doesn't need to change
- The portlet will be accessible to logged in user only. Either This portlet has been developed as a custom portlet using Plugins-SDK or OOB Iframe portlet.
- To display third party data in iframe so used iFrame to achieve this functionality. The information is being fetched by the web services.
- Using Iframe in cognos-integration-portlet makes it possible to embed another HTML page inside the current page.
- Furthermore the user can navigate through the embedded page without loosing the context of the portal page.
The configurations for this portlet are stored in portlet.properties file under WEB-INF/src folder. Here is a reference of the same:
cognos.page.targeturl =
cognos.graphic.format=
2. WSRP:
- You can expose cognos portlets running on a WebSphere server as a WSRP (Web Services for Remote Portlets) producer.
- In your portal, you can consume the cognos portlets via the OOB WSRP portlet .
- This provides a good level of decoupling because the Cognos portlets can run on a separate WAS server from your Portal server.
Good Concept...
ReplyDeleteThanks Ritesh,
ReplyDeleteInformative blog. I am going to use these two options, but is there any way to integrate cognos with liferay proxy portlet?
-Vijay
I've achieved the functionality using both the way in my one of project. Please let me know, What are the problems you are facing in your portlets?
ReplyDelete