Change Communities configuration property valuesConfiguration settings control how and when various Communities operations take place. You can edit the settings to change the ways that communities behave.
Before you beginTo edit configuration files, use the IBM WAS wsadmin client. See Starting the wsadmin client for information about how to start the wsadmin command-line tool.
About this taskConfigure Communities using scripts accessed with the wsadmin client. These scripts use the AdminConfig object available in the WAS 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.
ProcedureTo change Communities configuration settings...
- From the dmgr host:
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, 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: AIX and Linux only: The directory must grant write permissions or the command will not run successfully.
- <cell_name> is the name of the WAS 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:
Optional: To view a list of the valid Communities configuration settings and their current values, use the following command:
Here is some sample output from the CommunitiesConfigService.showConfig() command:
wsadmin>CommunitiesConfigService.showConfig() Configuration properties: activeContentFilter.enabled = true descriptionSummary.size = 300 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.interval = 0 30 0-23/3 ? * * task.LifecycleRetryQueuedEvents.interval = 0 1 0-23/3 ? * *
To change a Communities configuration setting, use the following command:
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.
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 nextYou 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 Apply property changes for details.
Communities configuration properties
Configuration properties control various features within Communities and also help in the optimization of server performance. They require a Communities application or server restart to take effect.
Apply property changes in Communities
After you have edited the Communities configuration properties, check the changed configuration file in, and restart the servers to apply the changes.
Parent topicAdminister Communities
Apply property changes in Communities