In this section, we describe how to add, customize and view social content in the front end as IBM WebSphere Portal using some of the features that are provided in portal like Social Rendering, Connections portlet for Portal, Social Networking Portlets, Integrated Search. Here, we are covering in detail how these features helps a page designer to easily add and customize the social content and give the customer a rich exceptional social web experience. These features makes a user to use limited social capabilities within the context of WebSphere Portal. The user can always step out to IBM Connections from Portal in case, if he wants to do some actions specific to Connections. Here, we have also provided few use cases to demonstrate the social capabilities in a city government portal website.
Why to use social content in the front end Portal
IBM WebSphere Portal provides a platform where all the portlets, application and content are combined and presented to user into one unified presentation. It also delivers a highly personalized experience where a user can personalize his settings based on his role. When Connections content is customized for a user and delivered inside Portal, it gives the user an exceptional social web experience. By displaying the social content in the front end as IBM WebSphere Portal, a user can be well connected, productive, collaborative with his community. By using the various applications that are available inside Portal he can easily access and share information, find the right people, organize the work and activities and be interactive with his community.
How to integrate Connections content inside Portal
Connections integration with Portal can be done in two ways :
1. Using IBM Connections portlet for Portal : Using the Connections portlet available in Lotus greenhouse, the Connections content can be delivered inside WebSphere Portal.
2. Using WCM to render IBM Connections content : Social Rendering features in IBM WebSphere Portal 126.96.36.199 provides capabilities to render the social content in a web page. Using this feature, we can see the IBM Connections web content library and all its content within WCM. We can also utilize the WCM capabilities to customize and render the Connections data within the context of WebSphere Portal.
This section assumes that the products IBM WebSphere Portal 188.8.131.52 and IBM Connection 4.0 with CR02 are installed. WebSphere Portal and Connections are using the same LDAP and SSO is configured between Portal and Connections. All the configurations are tested and they are in a working state.
Now, we will see each of the features available in Portal 184.108.40.206 in details to support Pattern 2: