Configuring the Processors

By default, the consolidation configuration pushes the documents they receive without transformation.

For more information, see Writing Transformation and Aggregation Processors and the examples provided in Use Cases.

This task shows you how to:

See Also
Trigger and Synchronize Consolidation
Forwarding Documents to Other Build Groups

Define a Consolidation Configuration

  1. Go to Index > Consolidation.
  2. The documents received by the Consolidation Server first go through transformation processor(s). The purpose of this transformation step is mainly to add arcs between documents to create the object graph.

    Note: If you are using a custom connector, you can configure it to handle the generation of arcs directly. For more information, see Consolidation Server directives in the Exalead CloudView Connector Programmer's Guide.

  3. The second step is the definition of the aggregation processor(s), which creates a consolidation view on top of the object graph.
  4. Once processors are defined, click Apply.
  5. Go to the Home page and under the connectors list, click Scan for the connectors managed by the Consolidation Server.

In the Connectors list, a consolidation-<instance name> row displays status information about consolidation.

Take into Account New Transformation Processors

Before you begin: To take into account changes made on your transformation processors, you need to rescan the impacted sources. You can clear the sources and scan them again or clear the Consolidation Server as described in Clearing the Consolidation Server.
  1. Go to the Home page.
  2. Clear the source connectors’ documents.
  3. Re-scan your connectors.

Take into Account Aggregation Processors

  1. In the Administration Console, go to the Home page
  2. Clear the index.
  3. Under Consolidation, start a Force aggregation operation.

    Note:

    You can also start Force aggregation from the API Console.

    A force aggregation behaves as a commit operation. The consolidation storage is fully synchronized at the end of the operation.

    If you specify a type, the force aggregation operation is not managed as a commit operation. If the consolidation storage has not yet been synchronized (either by triggering an aggregation or with a force commit operation), it stays in the same state after the operation. It only aggregates the targeted content of the consolidation storage.

    Important: Dynamically computed impact rules are based on old aggregation jobs. If you change your aggregation processors, these rules may no longer be consistent. To get back to a correct behavior, you either have to start a full Force aggregation operation or clear the Consolidation Server and rescan all its source connectors.