Enabling Blog Community Service

Make sure that Blog portlet's preferences in the display profile provider definition are correctly configured to talk to the Roller server. To test this, create a channel based on the Blog portlet. Without customizing the portlet channel's preferences, you must be able to use the channel to access weblogs on the server.

The portlet preferences you configure in Blog portlet's display profile provider definition will be used by the blog service in all communities. For example, the Roller AAPP URL and AAPP password will be used by the Blog community service in every community.

The Blog community service is not enabled by default. The process for doing so varies depending on whether the Portal Server 7.1 update 1 software instance is a new install or upgraded from Portal Server 7.1 software. To enable the Blog community service, ensure that the Blog community service is added to a community template.

For a New Install

For the community template with an ID of blogwiki, edit the community template role display profiles for the member (member.xml) and owner (owner.xml) roles and remove the XML comment blocks around the following Blog portlet elements.

• The DP channel entry for the Blog channel in both member.xml and owner.xml files.

• The community container's available and select channel lists in member.xml file.

• The search service's availableDatabases property in member.xml file.

For an Upgraded Install

Add the Blog community service to the existing community templates.

1. Select a template in which to add the Blog community service and add the following Blog channel definition to the community template member role display profile. Override the default preference values as needed.

   <Container name="%COMMUNITY_CONTAINER%" ...>
   	...
   	<Channel name="Blog" provider="__Portlet__blogportlet.BlogPortlet">
   		<Properties>
   			<String name="__Portlet__configMode" value="|wizard-user-only"/>
   
   			<String name="__Portlet__memberPermission" value="|AUTHOR"/>
   			<String name="__Portlet__searchUrl" value="|%COMMUNITY_SEARCH_URL%"/>
   			<String name="__Portlet__searchDatabase" value="|
   				%COMMUNITY_CONTENTS_SEARCH_DB%.blog"/>
   		</Properties>
   	</Channel>
   	...
   </Container>
   ...

2. Add the Blog channel to the community container's available and selected list.

   ...
   <Container name="%COMMUNITY_CONTAINER%" ...>
   	...
   	<Available>
   		<Reference value="%COMMUNITY_CONTAINER%/CommunityInfo"/>
   		<Reference value="%COMMUNITY_CONTAINER%/Search"/>
   		...
   		<Reference value="%COMMUNITY_CONTAINER%/Blog"/>
   		...
   	</Available>
   	<Selected>
   		<Reference value="%COMMUNITY_CONTAINER%/CommunityInfo"/>
   		<Reference value="%COMMUNITY_CONTAINER%/Search"/>
   		...
   		<Reference value="%COMMUNITY_CONTAINER%/Blog"/>
   		...
   	</Selected>
   	...
   </Container>
   ...

3. Add the Blog community service's search database to the search service's set of available search databases.

   ---

   Note –

   The value specified here must match the value specified in the searchDatabase preference in the channel definition.

   ---

   ...
   <Container name="%COMMUNITY_CONTAINER%" ...>
   	...
   	<Channel name="Search" provider="SearchProvider">
   		<Properties>
   			...
   			<Collection name="availableDatabases">
   				<String name="%COMMUNITY_CONTENTS_SEARCH_DB%.blog" value="Blog"/>
   			</Collection>
   			...
   	</Channel>
   	...
   </Container>
   ...

4. Add a channel definition to the owner role DP.

   You can override the default portlet preference values in the community template role display profile Blog portlet channel definitions.

   ...
   <Container name="%COMMUNITY_CONTAINER%" ...>
   	...
   	<Channel name="Blog" provider="__Portlet__blogportlet.BlogPortlet">
   		<Properties>
   			<String name="__Portlet__memberPermission" value="|ADMIN"/>
   		</Properties>
   	</Channel>
   	...
   </Container>
   ...

   With these changes, newly created communities based on the modified template will contain the service. You must log out and log in to force the community templates to be reloaded.