Introducing the Managed Push API Connector

The Managed Push API connector allows you to use Push API filters on unmanaged connectors. You can use it for unmanaged connectors that are not written in Java.

Recommendation: If your unmanaged connectors are written in Java, use the RScan client connector.

See Also
Configuring the Managed Push API Connector
RScan Client Connector

The Managed Push API connector listens to the PAPI servlet on a dedicated PAPI server, and:

  • Waits for the documents pushed by the unmanaged connectors, since it starts listening continuously when Exalead CloudView starts.

  • Lets you decide whether documents are owned by the unmanaged connector pushing to the Managed Push API Connector, or by the managed connector itself, if you select the Keep source ownership property.

  • Supports the Abort scan operation, which stops the PAPI server (documents can no longer be sent).

When the connector owns the documents it pushes, the ''fetch'' operation can be supported with an external fetch service in the internal configuration: 

<connect:SourceFetchConfig
customFetcherUrl="FETCH_SERVICE_URL"
fetchProtocol="PROTOCOL_VERSION"
allowRawDocumentFetch="true"
/>
Note: For more information, see Push API filters in the Exalead CloudView Connector Programmer's Guide.