You can control whether the Public Communities view
is available in your organization's deployment of Communities
by editing settings in the communities-config.xml file.
Before you begin
To edit configuration files, you must use the IBM® WebSphere® Application
Server wsadmin client. See Starting
the wsadmin client for details.
About this task
You can disable the Public Communities view
so that users can only see the restricted communities that they belong
to.Procedure
- Use the wsadmin client to access and check out the Communities
configuration files.
- Use the following command
to 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,
you must pick the node where the file is stored.
- 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®, Linux , and IBM i only: The directory must
grant write permissions or the command will not run successfully.
- cell_name is the name of the WebSphere Application Server 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")
- Open communities-config.xml in a text
editor.
- To disable the Public Communities view,
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>
- Save your changes.
- After making changes, you must check the configuration
files back in, and you must 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 Applying
property changes in Communities 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.