Communities configuration properties
Changes require a Communities application or server restart to take effect.
We can check out and modify the following configuration properties in communities-config.xml.
- activeContentFilter.enabled
- When enabled, this property prevents the addition of active content (JavaScript) in any text input field.
true or false
Disabling this filter introduces vulnerability to cross-site scripting (XSS) and other type of malicious attacks. for additional information.
- descriptionSummary.size
- Maximum number of characters in a community description to display in the Public Communities or My Communities view. It gets this information through the seedlist. Integer.
- explicitMembershipEntityLimit
- Maximum number of members that a community can contain. This limit is the total number of 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 decreased limit.
This property takes an integer value
Default is 100000. Values greater than 100000 are not supported.
Decrease the number to improve performance.
- group.enabled
- Enable or disable ability to add groups to communities. When owners click Add Members, they can choose to add Groups in the Members field.
This property accepts the following values: true or false.
- group.membershipCache.maximumAgeOnLoginInSeconds
- When a user logs in, this property determines the maximum age of a group membership cache in seconds.
The value must be 0 or greater.
- group.membershipCache.maximumAgeOnRequestInSeconds
- Maximum age of a group membership cache in seconds across requests for a user
The value must be 0 or greater.
- pagingSupport.communityListTags.pageSize
- Used by API calls that request tags. If we do not specify the count parameter in the API call, then the value listed in pagingSupport.communityListTags.pageSize is used. Integer.
- pagingSupport.dbNameTypeAhead.pageSize
- Maximum number of matching names to display in the type-ahead suggestion field when users start typing the names of people to add to a community. These names are retrieved from the SNCOMM.MEMBERPROFILE database table. Integer.
- pagingSupport.defaultPageSize
- Maximum number of community bookmarks and feed lists displayed on a page. Default is 10. Integer.
Decrease the number to speed paging.
- pagingSupport.ldapNameSearch.pageSize
- Maximum number of LDAP users returned when users click Search Directory to search the LDAP directory for a name when adding members to a community.
- pagingSupport.memberNameTypeAhead.pageSize
- Maximum number of users displayed by the type-ahead application when users click Search Directory to search the LDAP directory for a name when adding members to a community.
- pagingSupport.tagNameTypeAhead.pageSize
- Maximum number of tags displayed by the type-ahead application when users add new tags to a community.
- show.StartCommunity.To.Unauthenticated
- When enabled, this property displays the Start a community button to unauthenticated users.
true or false
- task.EventLogCleanup.enabled
- Enable or disable event log cleanup task.
This property accepts the following values: true or false.
- task.EventLogCleanup.interval
- Interval at which the event log cleanup task runs.
This parameter is specified using Cron format. For more information about using the Cron format, see Scheduling tasks.
When you change the interval property, the new schedule is registered the next time that Communities is started on any server in the Communities cluster (if there is one).
- task.LifecycleRetryQueuedEvents.enabled
- Enable or disable life-cycle retry queued events task.
This property accepts the following values: true or false.
- task.LifecycleRetryQueuedEvents.interval
- Interval at which the life-cycle retry queued events task runs.
This parameter is specified using Cron format. For more information about using the Cron format, see Scheduling tasks.
When you change the interval property, the new schedule is registered the next time that Communities is started on any server in the Communities cluster (if there is one).
Parent topic:
Communities properties
Related:
Secure applications from malicious attack
Scheduling tasks
Protecting against malicious active content
Apply property changes in Communities
Communities administrative commands