You can limit the maximum number of members that a community
can contain.
Before you begin
To limit community membership size, you
must edit the explicitMembershipEntityLimit property
in the Communities configuration file using the IBM® WebSphere® Application
Server wsadmin client. See Starting
the wsadmin client for information about how to start the wsadmin
command-line tool.
About this task
The maximum number of members that a community can contain
includes the total number of both people and groups added to a community.
It does not count the number of people contained in a group towards
this limit. The limit only applies to adding new members. If the limit
is reduced, IBM Connections
does not remove people from communities to accommodate the reduced
limit. The member limit property takes an integer value. The default
value and the maximum supported value is 100000. You can decrease
the number to improve performance.You configure the size limit
using scripts accessed with the wsadmin client. These scripts use
the AdminConfig object available in the WebSphere Application Server wsadmin client
to interact with the Communities configuration file. Changes to these
Communities configuration settings require node synchronization and
a restart of the Communities server before they take effect.
Procedure
To limit the maximum number of members that a community
can contain, 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.
- 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")
- To change the member limit property, use the following
command:
CommunitiesConfigService.updateConfig("explicitMembershipEntityLimit",
"value")
where value is
the new membership limit. For example:
CommunitiesConfigService.updateConfig("explicitMembershipEntityLimit", "500")
What to do next
You must check the configuration files back in after making
changes, and they must be checked in during the same wsadmin session
in which they were checked out for the changes to take effect. See Applying
property changes in Communities for details.