Home

 

Configure news event log clean-up

Edit settings in the communities-config.xml file to define the interval at which the EventLogCleanup task runs.

To edit configuration files, use the IBM WebSphere Application Server wsadmin client. See Start the wsadmin client for details.

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 IBM Lotus 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, you can do so by changing the WebSphere Application Server Cron schedule for this task.

A Cron schedule has six parts separated by a space. The six parts specify "second minute hourOfDay DayOfMonth Month DayOfWeek". "*" means all values, for example, all days of the week. The seconds must always be specified as zero. For example, "0 30 3 ? * *" means that the task is run daily at 3:30 a.m. "0 30 2 ? * SUN" means that the task is run on Sunday mornings at 2:30 a.m.

For more information about the elements of a Cron schedule, see the following Web page: http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.javadoc.doc/public_html/api/com/ibm/websphere/scheduler/UserCalendar.html To configure the EventLogCleanup task...

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

    1. Access the Communities configuration files:

      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. To view the current configuration settings...

    CommunitiesConfigService.showConfig()

    After updating any of the configuration settings, you can use this command again to display your updates.

  3. 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 you want to set that property.

    The following table displays the EventLogCleanup property and provides additional information regarding the property and the type of data that you can enter for it.


    The EventLogCleanup property

    Header Header
    task.EventLogCleanup.interval Specifies the interval at which the event log cleanup task runs.

    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 Lotus 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 ? * *")
      

  4. After making changes, check the configuration files back in, and do so during the same wsadmin session in which you checked them out for the changes to take effect. See Applying property changes for information about how to save and apply your changes.


Administer Communities

 

Related tasks

Apply property changes

Manage scheduled tasks


+

Search Tips   |   Advanced Search