Create CFS notifications to scan Content Manager with ControlPoint

1 Likes

When you scan Content Manager with ControlPoint, don’t forget to activate CFS notifications on Content Manager side.

This populates the TSNOTIFICA table in Content Manager that is used by ControlPoint connector to get the files.

Labels:

How To-Best Practice
Comment List
Parents
  •  

    Ingestion process involves connector -> connector framework -> metastore.

    Until all of those have completed it is not ingested.

    This is what I would normally check to confirm ingestion has finished:

    Monitor no more activity in these logs:
    ======================================
    connector synchronize.log
    connector framework import.log
    connector framework indexer.log

    Check metastore in progress queues (queued and running) are empty:
    =================================================================
    localhost:4500/action=queueinfo&queuename=ingest&queueaction=getstatus&state=queued
    localhost:4500/action=queueinfo&queuename=ingest&queueaction=getstatus&state=running


    Check IDOL cache flushed to disk
    ================================
    The final stage of the IDOL indexing process consists of files being written here:
    C:\Program Files\Micro Focus\HP ControlPoint\Indexer\Content\status

    This contains the intermediate files representing the index cache just before it is flushed to disk.

    A DRESYNC will occur automatically overtime to flush the cache to disk so the index is updated.
    You can trigger this to occur manually yourself to speed up the process:

    e.g.

    http://localhost:9001/DRESYNC

    If activity is still ongoing some may remain in C:\Program Files\Micro Focus\HP ControlPoint\Indexer\Content\status
    The backlog will eventually be cleared as the index cache is written to disk.


    You can also check IDOL and metastore directly via:
    ==================================================

    After issuing these commands scroll down to relevant section for repository and check document count.


    IDOL host
    ========
    localhost:9000/action=getstatus


    Metastore host
    =============
    localhost:4500/action=getstatus


    IDOL indexing status
    ====================
    localhost:9000/a=IndexerGetStatus


    Check individual queues in the content engines
    ==============================================
    localhost:32000/a=getstatus
    change port number if you have additional content engines to value assigned to Port in ControlPoint Content.cfg.

Comment
  •  

    Ingestion process involves connector -> connector framework -> metastore.

    Until all of those have completed it is not ingested.

    This is what I would normally check to confirm ingestion has finished:

    Monitor no more activity in these logs:
    ======================================
    connector synchronize.log
    connector framework import.log
    connector framework indexer.log

    Check metastore in progress queues (queued and running) are empty:
    =================================================================
    localhost:4500/action=queueinfo&queuename=ingest&queueaction=getstatus&state=queued
    localhost:4500/action=queueinfo&queuename=ingest&queueaction=getstatus&state=running


    Check IDOL cache flushed to disk
    ================================
    The final stage of the IDOL indexing process consists of files being written here:
    C:\Program Files\Micro Focus\HP ControlPoint\Indexer\Content\status

    This contains the intermediate files representing the index cache just before it is flushed to disk.

    A DRESYNC will occur automatically overtime to flush the cache to disk so the index is updated.
    You can trigger this to occur manually yourself to speed up the process:

    e.g.

    http://localhost:9001/DRESYNC

    If activity is still ongoing some may remain in C:\Program Files\Micro Focus\HP ControlPoint\Indexer\Content\status
    The backlog will eventually be cleared as the index cache is written to disk.


    You can also check IDOL and metastore directly via:
    ==================================================

    After issuing these commands scroll down to relevant section for repository and check document count.


    IDOL host
    ========
    localhost:9000/action=getstatus


    Metastore host
    =============
    localhost:4500/action=getstatus


    IDOL indexing status
    ====================
    localhost:9000/a=IndexerGetStatus


    Check individual queues in the content engines
    ==============================================
    localhost:32000/a=getstatus
    change port number if you have additional content engines to value assigned to Port in ControlPoint Content.cfg.

Children
No Data
Related
Recommended