Home

 

Change Communities configuration settings

Configuration settings control how and when various Communities operations take place. You can edit the settings to change the ways that communities behave.

To edit configuration files, use the IBM WebSphere Application Server wsadmin client. See Start the wsadmin client for information about how to start the wsadmin command line tool.

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.

To change Communities configuration settings...

1. Use the wsadmin client to access and check out the Communities configuration files:

   1. Access the Communities configuration files:

      • Stand-alone deployment:

        execfile("communitiesAdmin.py")

      • Network deployment:

        execfile("WAS_HOME/communities/Dmgr01/config/bin_lc_admin/communitiesAdmin.py")

      If you are asked to select a server, you can select any server.

   2. Check out the Communities configuration files...

      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 while you make changes to them.

      • cell_name is the name of the WebSphere Application Server cell hosting the Lotus Connections feature. This argument is required even in stand-alone deployments. If you do not know the cell name, do one of the following to determine it:

        • Stand-alone deployment: Look at the name after the following in the file system:

          WAS_HOME\profiles\profile_name\config\cells\
          

      • Network deployment: Type the following command while in the wsadmin command processor:

        print AdminControl.getCell()
        

      For example:

      CommunitiesConfigService.checkOutConfig("/opt/my_temp_dir", "CommServerNode01Cell")
      

2. Optional: To view a list of the valid Communities configuration settings and their current values...

   CommunitiesConfigService.showConfig()

   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.ForumPurgeTrash.interval = 0 0 2 ? * SUN
           task.LifecycleRetryQueuedEvents.interval = 0 1 0-23/3 ? * *
   

3. To change a Communities configuration setting...

   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")
   

4. 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.

5. Optional: Repeat step 3 for each property setting that you want to change.

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.

• Communities configuration properties
  Configuration settings control various configurable 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
  After you have edited the Communities configuration properties, check the changed configuration file in, and restart the servers to apply the changes.

Administer Communities

 

Related tasks

Apply property changes

---

+

Search Tips   |   Advanced Search