Disable community invitations 

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, use the wsadmin client. See Starting the wsadmin client for details.


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 file.


Procedure

  1. From the dmgr host:

      cd $DMGR_PROFILE/bin
      ./wsadmin.sh -jython
      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.checkOutPolicyConfig("<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.checkOutPolicyConfig("/opt/my_temp_dir", "CommServerNode01Cell")

  • 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>.

  • 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.


    Parent topic

    Manage membership in Communities


       

     

    });