Add nodes to the Communities catalog

If the primary node stops operating, another node can automatically start collecting data.

1. Log in to IBM Connections as catalog administrator.

2. Before adding nodes, disable scheduled metadata collections.
   Communities | Administration | More actions | Disable Schedule

   This action stops future collections, but does not delete existing metadata from the index.

3. Copy the catalog index folder from an existing node to the new node :

   1. Log in to the WAS console and click...
      Servers | Clusters | WebSphere application server clusters | catalog_cluster_name | Additional Properties | Cluster members | Details

   2. In the table of cluster members, make a note of the nodes that host the cluster members.

   3. Copy the catalog index folder from an existing node to the new node
      /opt/IBM/Connections/data/local/catalog/index/Places

4. Re-enable source metadata collection...
   More actions | Enable Schedule

Parent topic:
Manage the Communities catalog

Related:
Configure catalog index and replication folders
Configure the Communities catalog administrator role