Configure news event log clean-up
Edit settings in communities-config.xml.to define the interval at which the EventLogCleanup task runs.
Communities has a database table called EVENTLOG. When certain predefined events occur in communities, those events are written to the table, which increases in size as more and more events are added. The EventLogCleanup task is used to clean up the EVENTLOG database table by removing events that are older than 30 days. When you install Connections, by default, the EventLogCleanup task is scheduled to run every day, every 3 hours, and to delete events older than 30 days. To modify the default schedule to run more or less frequently, we can do so by changing the WAS Cron schedule for this task. For more information about the WAS scheduler, see Scheduling tasks.
To configure the EventLogCleanup task.
- Access the Communities configuration files:
cd app_server_root/profiles/Dmgr01/bin
./wsadmin.sh -lang jython
execfile("communitiesAdmin.py")
CommunitiesConfigService.checkOutConfig("/tmp", "cell_name")To get cell name...
print AdminControl.getCell()
- To view the current configuration settings:
CommunitiesConfigService.showConfig()
After updating any of the configuration settings, we can use this command again to display the updates.
- To modify the setting for the scheduled task:
CommunitiesConfigService.updateConfig("property", "value")
where:
- property is one of the editable Communities configuration properties.
- value is the new value with which to set that property.
The following table displays the EventLogCleanup property and provides additional information regarding the property and the type of data that we can enter for it.
Property Description task.EventLogCleanup.enabled Enable or disable event log cleanup task. This property accepts the following values: true or false.
For example:
CommunitiesConfigService.updateConfig("task.EventLogCleanup.enabled", "true")
task.EventLogCleanup.interval Interval at which the event log cleanup task runs. The parameter is specified in 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).
When you install Connections, the default setting for this task is 0 30 0-23/3 ? * *, which means that it will run every 3 hours at 30 minutes past the hour.
In the following example, the EventLogCleanup task is set to run once every hour at 32 minutes past the hour.
CommunitiesConfigService.updateConfig("task.EventLogCleanup.interval", "0 32 0-23/1 ? * *")
- After making changes, check the configuration files back in, and we must do so during the same wsadmin session in which you checked them out for the changes to take effect. See Applying property changes in Communities for information about how to save and apply the changes.
Parent topic:
Administer Communities
Related:
Related: