Content Provider Development Guide › About Content Provider Development

About Content Provider Development

The CA DataMinder Content Services consist of three components (outlined in green in the diagram):

• Content Indexer,
• Content Proxy,
• Content Database

The Content Indexer runs configurable jobs which pull events and their data from a CMS database. Then the Content Indexer pushes the events to the Content Database for indexing. The Content Proxy turns content search requests into queries for the Content Database, and returns search results.

The Content Database stores the indexed content data. The Content Database consists of a third-party database system which interfaces with the rest of the Content Services through a Content Provider.

Content Providers form an abstraction layer for the rest of the Content Services. A Content Provider provides an abstraction for a specific database system, and contains all database-specific code. The Content Indexer and Content Proxy are database-agnostic.

• (Green) Content Services components provide the indexing and searching services.
• (Blue) Current consumers of the services:

  The Content Indexer Console (for indexing) connects to the Content Indexer; the iConsole web server (for searching) connects to the Content Proxy. In the Content Indexer’s case, connection is direct, through COM, to the Content Indexer Server. In the Content Proxy’s case, connection is through COM to the Content Proxy Client, which communicates proprietarily with the Content Proxy Server. The Content Indexer Server also communicates directly with the CMS from which it draws the events to index.

• (Red) The Content Database provides indexing and searching capabilities to the Content Indexer and the Content Proxy. The Content Provider provides the interfacing layer (using COM) for the Content Database to the Content Indexer and the Content Proxy.