Changing Activities configuration property values
Configuration settings control how and when various Activities operations take place. You can edit the settings to change the ways that activities behave.
Configure Activities using scripts accessed with the wsadmin client. These scripts use the AdminConfig object available in WebSphere® Application Server wsadmin client to interact with the Activities configuration file. Changes to Activities configuration settings require node synchronization and a restart of the Activities server before they take effect.
- Checking out the Activities configuration files
You can edit the Activities configuration files in two ways: by using the wsadmin client or by editing the configuration XML files directly. In both cases, you must first check out the configuration files and later check them back in using the wsadmin client.
- Activities configuration properties
Edit Activities configuration properties to change the default behavior of the activities that are created by your users.
- Applying property changes in Activities
After you have edited the Activities configuration properties, check the changed configuration file in, and restart the servers to apply the changes.
- Managing uploaded files
There are many ways to include files in an activity. Files can be uploaded and stored in an activity. To avoid uploading files into an activity, add a link in the activity that points to a file stored in a Linked Library or Files. You can also limit the maximum size of files that can be uploaded, add a content store to an activity, or move a content store.
- Completing activities that are not being used
Activities are moved to the Completed view for two reasons, inactivity and the passing of a Due Date. The following help is about how to configure an inactive Activity.
- Emptying the Activities trash on a schedule
Edit configuration property settings to set up a schedule on which to permanently delete the activities and entries that have been moved to the Trash view.
- Monitoring statistics and metrics
Use the Activities statistics gathering application to monitor operations, product usage, and to make configuration adjustments when necessary.
- Purging the Activities log
By default, the Activities events log is purged daily at 2 AM. By modifying the EventLogPurgeJob task, you can specify the time that the log is purged and set the properties that define which entries can be deleted. Deleting old events helps maintain performance and keeps the log from becoming too large. Limiting the size of the event log table limits the database storage needed.
- Managing Activity filters
Edit configuration property settings to filter out Community activities from My activities in the main navigation panel of the Overview page.
Parent topic:Administering Activities