Sources are connections to servers or clusters that contain Quickr
places. The servers publish metadata about their communities and places, and sources collect that metadata in an index. Community metadata then displays in lists of communities in the Public Communities
, I’m a Member
, I’m an Owner I’m Following
and I’m Invited
views. By default metadata is collected automatically on a schedule, but you can control collections for each source.
Only places metadata is collected, not the actual community or place content.
To add sources, log in to IBM
Connections as catalog administrator. See Configuring the catalog administrator
- Click any option under Communities and then click the Administration view in the navigator. Then click Add Source.
- Enter the name by which the source is identified in the Name field.
- In the User field, enter the name of the administrator that is used in authentication.
- In the Password field, enter the password that the administrator uses for authentication.
- Enter the address of the server that provides the seedlist in Server URL field.
- Select the type of place metadata to be indexed, like Lotus Quickr for WebSphere® Portal Places
- View the Seedlist URL field. The seedlist URL is the URL composed automatically by concatenating the server URL and the known seedlist postfixes. In most Connections and Quickr installations, the composed URL is correct and there is no need to change it. If you do need to change it, click Change URL.
- Select how frequently this source is crawled for new data to collect in the Collect every field.
Then perform the following tasks to manage sources:
- To see the number of items (communities or places), see the Number of items column.
- To see the status of a source (available or not) see the Status column.
- To edit a source, click Edit Details.
- To manage source metadata collection, click More actions and then do any of the following tasks:
- To have this source crawled for new data to collect now, then select Collect Data.
- To delete the metadata for the source from the index, select Clear Data.
- To disable future scheduled metadata collections, select Disable Schedule. This action stops future collections, but does not delete existing metadata from the index.
In clustered environments, Community Catalog Administration is on the primary node. If you see a message that says that the primary node is not available, an administrator can switch the Community Catalog Administration to a secondary node.
Parent topic: Administering Communities