Configuring task to retrieve tags

When you integrate Connections with your portal server, the portal uses a task to retrieve tags and related resources from the various Connections features (such as activities, blogs, bookmarks, communities, files, forums, profiles, and wikis). Then, the portal integrates the tags in the portal tag cloud. You can schedule the task to retrieve the tags to run periodically.

Before you begin

The piece of content (POC) resolver is required to render tagged Connections resources within Connections portlets. The instructions for installing the Connections portlets included a step to copy the POC resolver to the portal.

About this task

Depending on your database system, it might be beneficial to reorganize some tables in the community domain. You can also gather current catalog statistics for the tables after an import of Connections data is done. This action helps the SQL optimizer determine an efficient access path. Review your database system documentation for instructions on how to accomplish this task. The database tables that are most affected by an import include:
  • CP_CUSTOMRESOURCE
  • CP_CATEGORY
  • CP_RESOURCE_TAG
  • LOC_DATA
  • LOC_DATA_LOD

You can schedule the FederationTaskHandler to periodically retrieve (import) Connections data. For more information about scheduling the FederationTaskHandler, see Administering tag federation.

Procedure

Using XML access, run com.ibm.wps.cp.tagging.federation.taskhandler.FederationTaskHandler

Results

During the import of the tags if you exceed the number of available connections, increase the value for the configuration parameter max-connections-per-host for the corresponding policy in the Ajax Proxy configuration file proxy-config.xml