Preventing members from creating specific community types
You can prevent community members from creating specific community types on a deployment-wide basis.
To update configuration files, you must use the wsadmin client. See Starting the wsadmin client for details.
Disabling the ability to create specific community types means that community members can no longer create certain types of community. Instead, only community owners or administrators can create those types of community.
- To prevent community members from creating a community, complete the following steps:
Start the wsadmin client by completing the following steps:
Open a command prompt and then change to 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 represents the IBM WebSphere Application Server installation directory, for example:
Windows: drive:\Program Files\IBM\WebSphere\AppServer
Where drive is the system drive on which the file directory is stored. For example: C: or D:.
where dm_profile_root is the Deployment Manager profile directory; this directory is usually called dmgr01. For example, on Windows, the directory is C:\Program Files\IBM\WebSphere\AppServer\profiles\Dmgr01\bin.
Attention: You must run the command to start the wsadmin client from this specific directory because the Jython files for the product are stored there. If you start the client from a different directory, the execfile() command does not work correctly.
Enter the following command to start the wsadmin client:
- Linux: ./wsadmin.sh -lang jython -user admin_user_id -password admin_password -port SOAP_CONNECTOR_ADDRESS_PORT
Microsoft Windows: wsadmin -lang jython -user admin_user_id -password admin_password -port SOAP_CONNECTOR_ADDRESS_PORT where:
admin_user_id is the user name of the Administrator role on IBM WebSphere® Application Server. This administrator must be configured at the cell level, not at the cluster, node, or server level.
- admin_password is the password of the WebSphere Application Server administrator.
SOAP_CONNECTOR_ADDRESS_PORT is the SOAP port for the WebSphere Application Server deployment manager server. The default value of the SOAP port is 8879. If you are using the default port value, you do not have to specify this parameter. If you are not using the default value and you do not know the port number, you can look up its value in the WebSphere Application Server Integrated Solution Console. To look up the SOAP port number, complete the following steps:
- Open the WebSphere Application Server Integrated Solution Console for the deployment manager, and then select System Administration > Deployment Manager.
- In the Additional properties section expand Ports, and then look for the SOAP_CONNECTOR_ADDRESS port entry to find the port number. For example:
Linux: ./wsadmin.sh -lang jython -username primaryAdmin -password p@assword -port 8879
- Microsoft Windows: wsadmin -lang jython -username primaryAdmin -password p@assword -port 8879
- Access and check out the Communities configuration files:
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: 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 HCL 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:
From the temporary directory to which you just checked out the HCL Connections configuration files, open the communities-policy.xml file in a text editor.
Comment out one or more of the following permissions corresponding to the community types that users cannot create.
<comm:permission class="com.ibm.tango.auth.permission.CommunityManagementPermission" communityType="public" action="create" /> <comm:permission class="com.ibm.tango.auth.permission.CommunityManagementPermission" communityType="publicInviteOnly" action="create" /> <comm:permission class="com.ibm.tango.auth.permission.CommunityManagementPermission" communityType="private" action="create" />
Save your changes to the communities-policy.xml file.
Check in the updated file, enter the following wsadmin client command:
To exit the wsadmin client, type exit at the prompt.
Stop and restart the server that hosts the Communities application.
Community owners cannot delete communities.
Parent topic:Managing default owner and member permissions