Disable views in Communities 

You can control the pages that display in your organization's deployment of Communities by editing settings in the communities-config.xml file.

About this task

To prevent specific pages from displaying in the Communities user interface, you need to remove the associated tabs from the top banner so that they do not display in the navigation. You also need to disable the pages themselves so that users cannot navigate to them directly.

For example, you might want to disable the Public Communities view so that users can only see the restricted communities that they belong to. Or you might want to disable both the Public Communities and the My Communities views to restrict the display to a single community.

To disable views in Communities...

Procedure

1. Use the wsadmin client to access and check out the Communities configuration files.

   1. Access the Communities configuration files:
      

      execfile("communitiesAdmin.py")

      If prompted to specify a service to connect to, type 1 to pick the first node in the list. Most commands can run on any node. If the command writes or reads information to or from a file using a local file path, pick the node where the file is stored.
      

   2. Check out the Communities configuration files using the following command:
      
      CommunitiesConfigService.checkOutConfig("<working_directory>", "<cell_name>")

      where:
      

      • <working_directory> is the temporary working directory to which the configuration XML and XSD files are copied. The files are kept in this working directory while you make changes to them.
        Note: AIX and Linux™ only: The directory must grant write permissions or the command will not run successfully.
        

      • <cell_name> is the name of the WAS cell hosting the IBM Connections application. This argument is required. If you do not know the cell name, you can determine it by typing the following command in the wsadmin command processor:
        print AdminControl.getCell()
        

      For example:

      CommunitiesConfigService.checkOutConfig("/opt/my_temp_dir", "CommServerNode01Cell")

      
      

2. Open communities-config.xml in a text editor.

3. To disable pages in Communities...as needed:

   1. To disable the Public Communities page, add the following lines after the <comm:tagCloud> element and before the <comm:communityHandle> element:
      

      <!-- Community Page Configuration -->

      <comm:communityPages> <comm:item name="publicCommunities" value="disabled"/> </comm:communityPages>
      

   2. To disable the My Communities page, add the following lines after the <comm:tagCloud> element and before the <comm:communityHandle> element:
      

      <!-- Community Page Configuration -->

      <comm:communityPages> <comm:item name="myCommunities" value="disabled"/> </comm:communityPages>
      

   3. To disable both the Public Communities page and the My Communities page, add the following lines after the <comm:tagCloud> element and before the <comm:communityHandle> element:
      

      <!-- Community Page Configuration -->

      <comm:communityPages> <comm:item name="publicCommunities" value="disabled"/> <comm:item name="myCommunities" value="disabled"/> </comm:communityPages>
      

4. Save your changes.

5. After making changes, check the configuration files back in, and do so during the same wsadmin session in which you checked them out for your configuration changes to take effect. You must also stop and restart the Communities server. See Apply property changes for information about how to save and apply your changes.
   

Results

The disabled page no longer displays in the Communities user interface. If a user tries to navigate to the page by entering its URL directly into the address bar, a message indicating that the page has been disabled displays.

Related tasks

Apply property changes in Communities

+

Search Tips   |   Advanced Search