Configuration settings control how and when various Communities
operations take place. You can edit the settings to change the ways
that communities behave.
Before you begin
To edit configuration files, you must use 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
Configure Communities 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 Communities configuration settings require node synchronization
and a restart of the Communities server before they take effect.
Procedure
To change Communities configuration settings, 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:
For example:
CommunitiesConfigService.checkOutConfig("/opt/my_temp_dir", "CommServerNode01Cell")
- Optional: To view a list of the valid Communities
configuration settings and their current values, use the following
command:
CommunitiesConfigService.showConfig()
Here
is some sample output from the
CommunitiesConfigService.showConfig() command:
activeContentFilter.enabled = true
descriptionSummary.size = 300
explicitMembershipEntityLimit = 100000
group.enabled = true
group.membershipCache.maximumAgeOnLoginInSeconds = 120
group.membershipCache.maximumAgeOnRequestInSeconds = 120
handle.enabled = true
pagingSupport.communityListTags.pageSize = 75
pagingSupport.dbNameTypeAhead.pageSize = 50
pagingSupport.defaultPageSize = 10
pagingSupport.ldapNameSearch.pageSize = 50
pagingSupport.memberNameTypeAhead.pageSize = 15
pagingSupport.tagNameTypeAhead.pageSize = 10
show.startCommunity.To.Unauthenticated = true
task.EventLogCleanup.enabled = true
task.EventLogCleanup.interval = 0 30 0-23/3 ? * *
task.LifecycleRetryQueuedEvents.enabled = true
task.LifecycleRetryQueuedEvents.interval = 0 1 0-23/3 ? * *
- To change a Communities configuration setting, use the
following command:
CommunitiesConfigService.updateConfig("property",
"value")
where
property is
one of the editable Communities configuration properties and
value is
the new value with which you want to set that property. See
Communities
configuration properties for a complete list of editable properties.
For
example:
CommunitiesConfigService.updateConfig("descriptionSummary.size", "500")
- Optional: After updating the Communities properties
with new values, use the CommunitiesConfigService.showConfig() command
to display the list of properties and their updated values. These
are the values that will be checked in with the CommunitiesConfigService.checkInConfig() command.
- Optional: Repeat step 3 for each property setting
that you want to change.
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 for details.