You can make a Content Feeder reindex selected contents by invoking JMX operation "reindexByQuery" or "reindexByType" of MBean com.coremedia:type=AdminBackgroundFeed,application=content-feeder.

Reindexing happens in a background thread, and will not block indexing of repository changes. It can be used for example to reindex all content of a specific type after indexing rules for that type have been changed. To this end, the "reindexByType" JMX operation can be used.

The "reindexByQuery" operation is more generic and takes a Unified API query as documented in interface com.coremedia.cap.content.query.QueryService. All contents that match the query (and are not excluded from feeding) will be reindexed.

Both operations can take an optional comma-separated list of com.coremedia.cap.feeder.FeedableAspect IDs. If specified, the Feeder will not reindex whole index documents but uses partial updates for these aspects only. See Section 4.1, “Concepts” for details on partial updates.

If the Content Feeder is stopped during reindexing, it will continue with the next content after restart. The reindexing progress is persisted in a special document in the index itself.

There's another JMX operation "cancel" at the same MBean to cancel a running reindexing operation. The reindexing progress is available with MBean attribute "NumberOfPendingContents".