Mapping a community page to a communityAdded by IBM on May 8, 2014 | Version 1 (Original)
|Map a community page to an IBM® Connections community so the portlets can interact with community content.
Follow the steps to map the community pages to a community based on what WebSphere Portal Server
® you are using.
- To map community pages to a community on a WebSphere Portal 7 server:
- Log into Portal as an administrator.
- Navigate to the page that you want to map to a community.
- Click Actions -> Edit Page Properties.
- Expand the Advanced options section and click I want to set parameters.
- Add the following new parameters:
|Parameter Key||Parameter Value|
|ibm.community.id ||The ID of the connections community. To get this value, open the Connections community in a browser and copy the ID following communityUid= in the community URL.|
|ibm.community.home||Set to TRUE if the page is identified as the home page for the community. There can be only one home page. In the case where there are multiple homepages set, the first page is selected.|
|ibm.community.page||Set to FALSE if this is the home page; otherwise, set to TRUE. |
Note: If you are creating a page which has a parent page that is mapped to a community, follow steps c and d , but you must explicitly set the parameters set in step e. To do this, click the Edit icon for each parameter, click OK, then explicitly set the parameters.
- To map community pages to a community on a WebSphere Portal 8 server, follow the steps in the article Managing community associations in the WebSphere Portal product wiki.
- Assign access to the page.
If the community has restricted membership, you can secure the page so that only members of the community can see the page in the Portal navigation. You can also access assign on community pages mapped to public or moderated communities, but doing so does not restrict access to the content in the community. There are other mechanisms, including APIs, mobile clients, connectors and search and portlets on other pages which may expose the content outside the community page. Membership lists in Connections communities should have the correct level of access to community content and Portal pages should reflect that level . Before you use communities for access control on pages, follow the steps in Integrating community membership with Portal security
- Navigate to Administration -> Manage Pages and find the community page for which you want to set access.
- Click Set Page Permission (lock icon).
- Uncheck Allow Inheritance for all rows and click Apply.
- Click on the Edit Role button in the Privileged User and User columns and make sure no users or groups are added that you do not want to access this page.
- Click on the Edit Role button in the Privileged User or User column, depending on what level of access you want to grant to community members. See the Roles topic for a description of roles in WebSphere Portal.
- Click Add.
- Change Search by to displayName.
- Enter the name of the community in the search box and click Search.
- Check the box next to the group representing the community and click OK.
If successful, the group appears in the list of members in the role and a message indicates that the members were successfully added to the role.
- Before adding portlets to your community page, make sure that the corresponding widget exists in the community. For example, before you add a Blogs portlet to the community page, make sure the IBM Connections community contains a blog. If not, add the Blogs widget to the IBM Connections community using the browser interface.
If the portal administrator configures a portlet with a new connections server URL for a community page, then the changes will take effect only after the community page is configured with a valid community ID for the new connections server, by editing the portal page parameters settings to include the new community ID.
Parent topic: Community Pages