Before you begin
If you are integrating with WebSphere Portal 8.0, portlets are excluded from portal search by default and you do not need to specifically exclude them.
By default, on WebSphere Portal 7.0 servers, the Portal search crawler crawls all the portal pages and active portlets lying on them. Since IBM Connections uses its own seedlists for search, you can exclude the Connections portlets from the default portal indexing. The default crawler user is the default Portal admin user. This user might not be a Connections user, so in order to exclude the IBM Connections Portlets from the Portal indexing; this user should not have access to Connections portlets. To achieve this, create a separate group which lists all Connections users who should have access to IBM Connections portlets. Make sure that the crawler user is not part of this group. IBM Connections portlets should be assigned access permission to this group instead of to the 'All Authenticated Portal users group'. This way when the crawler runs, the default portal indexing will exclude IBM Connections portlets.
Parent topic: Configuring search integration