Before you begin
You must be running the 18.104.22.168 version of the IBM
Connections Portlets of IBM WebSphere
® Portal to use this feature.
Use URIs to identify, access, and display IBM
Connections content and profiles in a portlet. IBM WebSphere
Portal uses Piece of Content (POC) URIs to identify and address specific pieces of content in IBM
Connections independent of the page used to display the content. Using a POC URI, you can precisely identify what content you want to display without knowing where it should be displayed in your WebSphere
Portal server at the time you generate a link. For example, when a user clicks a link in a blogs summary portlet, the POC URI identifies the blog content. Clicking on a link that uses a POC URI displays the blog entry in the Blogs detail portlet on the appropriate page. The evolution to POC URIs provides a greater precision for identifying, retrieving, and displaying content. The URI specifies the identity of the content, not the location of the view of the document. The location of the view to the document is called the portal URL, or simply URL and the information contained in this URL includes the navigational state, or simply state. When working with a POC URI, you do not need to be aware of the page in Portal where a piece of content should be displayed, you only need to know some identifying data about the piece of content to create the URL. The correct WebSphere
Portal page to display the content is retrieved after the user clicks on a link using a POC URI format.
The POC resolver handles navigation in following manner.
- If the piece of content is community content:
- Search the community page for a detail portlet to render the content.
- If no static community page is found , search for a stand-alone page.
- If no stand-alone page is found, navigate to an error page.
- If the piece of content is from a stand-alone page rather than from a community:
- Search the standalone page for a detail portlet to render the content.
- If no standalone page is found , navigate to an error page.
For detailed information on the creating and using custom URIs to access content, see the article Leveraging WebSphere Portal V6 programming model: Part 5. Accessing portal content with custom URLs on IBM developerWorks
About this task
The following steps are an example of how you can wire portlets in an application. You can apply these steps to wiring any of the IBM
Connections portlets in an application.
Configuring the portlets on a page
- Ensure you have followed the install instructions completely. The JAR for the POC handler must be installed as described in Installing the IBM Connections Portlets for IBM WebSphere Portal.
- To configure navigation to community pages, ensure you have set the correct properties when defining the community page as described in Mapping a community page to a community.
- To configure navigation for content not inside a community, or for which a community page does not exist, ensure you have create default pages for each service as described in Configuring the portlets on a page.