Limiting broadcast email to Community owners

You can limit broadcast mail to Community owners.

Before you begin

To update configuration files, you must use the wsadmin client. See Starting the wsadmin client for details.

About this task

The Notifications library sends broadcast email messages in batches. To reduce load in large Communities, you can limit broadcast email messages to Community owners; this procedure disables the Mail Community button for Community members.

Procedure

To limit broadcast email to Community owners, complete the following steps.

Start the wsadmin client from the following directory of the system on which you installed the Deployment Manager:
```
app_server_root\profiles\dm_profile_root\bin
```
where app_server_root 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.
1. 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.
2. Check out the Communities configuration files with 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 change them.
    Note: IBM i,® AIX, and® Linux only: The directory must grant write permissions or the command do not run successfully.
  - cell_name is the name of the WebSphere Application Server cell that hosts the IBM Connections application. 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 with a text editor.

Comment out or remove the following content from the member and explicit-member sections:

class="com.ibm.tango.auth.permission.CommunityBroadcastPermission" 
   action="mail" communityType="public"/> <comm:permission 
class="com.ibm.tango.auth.permission.CommunityBroadcastPermission" 
   action="mail" communityType="publicInviteOnly"/> <comm:permission 
class="com.ibm.tango.auth.permission.CommunityBroadcastPermission" 
   action="mail" communityType="private"/> <comm:permission

The following tags identify the member and explicit-member sections:

<comm:principal class="com.ibm.tango.auth.principal.Role" name="member" />
<comm:principal class="com.ibm.tango.auth.principal.Role" name="explicit-member" />

Add the content that you commented out or removed to the owner section.

class="com.ibm.tango.auth.permission.CommunityBroadcastPermission" 
   action="mail" communityType="public"/> <comm:permission 
class="com.ibm.tango.auth.permission.CommunityBroadcastPermission" 
   action="mail" communityType="publicInviteOnly"/> <comm:permission 
class="com.ibm.tango.auth.permission.CommunityBroadcastPermission" 
   action="mail" communityType="private"/> <comm:permission

The following tag identifies the owner section:

<comm:principal class="com.ibm.tango.auth.principal.Role" name="owner" />

Check in the updated policy file:

CommunitiesConfigurationService.checkInPolicyConfig
   ("working-directory", "cell-name")

Synchronize your changes across all nodes and then restart the Communities application.