Configuring the Managed Push API Connector

Follow the procedure below to configure the managed Push API connector.

Before you begin: This section implies that the connector has already been added. See Creating a Standard Connector.
See Also
Introducing the Managed Push API Connector
  1. Configure the following options.

    Parameter

    Description

    PAPI port

    Specifies the network port of the Push API server run by this connector. Specify the same port for the unmanaged connectors that must push documents to this connector.

    Keep source ownership

    If selected, Exalead CloudView considers that documents pushed by this connector are owned by the real source connector. Otherwise, it considers this connector as the owner of all pushed documents, and the fetch operation is not supported.

    Recommendation: Select this option if the source connectors implement the fetch operation. In that case, the source connectors and this managed connector must have different names so that Exalead CloudView can distinguish them.

    No. threads

    Specifies the number of threads available for the Push API server.

    If you specify a value inferior or equal to 0, the Push API server creates as many threads as required, but reuses available ones.

  2. Click Apply.

    You do not have to click Scan for this connector as it scans document continuously.

  3. Go to the Deployment tab and disable the Buffer operations property.

    When you add a managed connector, a buffer is implicitly added to batch operations between the connector and the indexing server. The buffer is flushed from time to time at the end of the connector scan.

    This is however problematic with the Managed Push API Connector as its scan never ends, and Push API operations can remain stuck in the buffer. That is why we recommend disabling the Buffer operations property.