Managing Activity filters
Edit configuration property settings to filter out Community activities from My activities in the main navigation panel of the Overview page.
To edit configuration files, you must use the wsadmin client. See Starting the wsadmin client for details.
Activities can be filtered as follows on the Overview page:
- My activities (all activities I own and does not include any community activities).
- Community activities (only community activities).
Activity filtering is disabled by default.
To enable activity filtering, complete the following steps:
Use the wsadmin client to access and check out the Activities configuration files.
Use the following command to access the Activities configuration file:
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, you must pick the node where the file is stored.
Check out the Activities configuration files using the following command:
working_directory is the temporary working directory to which the configuration XML and XSD files are copied and are stored while you make changes to them. Use forward slashes to separate directories in the file path, even if you are using the Microsoft™ Windows™ operating system.
Note: Linux™: The directory must grant write permissions or the command will not run successfully.
cell_name is the name of the WebSphere® Application Server cell hosting the HCL Connections application. This argument is case-sensitive, so type it with care. If you do not know the cell name, you can determine it by typing the following command in the wsadmin command processor:
To change the property value, edit oa-config.xml and set feature.communityActivitiesView.enabled, set to "true" at the end of oa-config.xml as follows:
<properties> <property name="feature.communityActivitiesView.enabled">true</property> </properties>
<properties>...</properties>tagging is already present, do not add it again. Instead, include the property name string in the example shown in the existing properties tags.
After you make changes, you must check the configuration files back in and you must do so during the same wsadmin session in which you checked them out for the changes to take effect. See Applying property changes for details.
Parent topic:Changing Activities configuration property values
Previous topic:Purging the Activities log