You can update configuration settings in the communities-policy.xml
file to disable the ability to invite people to join a community.
Before you begin
To update configuration files, you must use the wsadmin client. See Starting the wsadmin client
About this task
If you do not want community owners or members to be able to invite people to join a community, you can disable this functionality by removing any lines of code containing CommunityInvitePermission
from the communities-policy.xml
Parent topic: Managing membership in Communities
- Start the wsadmin client from the following directory of the system on which you installed the Deployment Manager:
is the WebSphere
® Application Server installation directory and <dm_profile_root>
is the Deployment Manager profile directory, typically dmgr01.
You must start the client from this directory or subsequent commands that you enter do not execute correctly.
- Start the Communities Jython script interpreter.
- Use the following command to access the Communities configuration files:
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:
- <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 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:
- Navigate to the working directory that you specified in the previous step and open the communities-policy.xml file using a text editor.
- Comment out or remove any lines that include the following:
- Comment out or remove any <comm:grant> element that does not contain a valid <comm:permission>.
<!-- Invitee -->
<comm:principal class="com.ibm.tango.auth.principal.Role" name="invitee" />
- Save your changes and then close the communities-policy.xml file.
- Check in the updated policy file using the following command:
- Synchronize your changes across all nodes and then restart the Communities application.