Forwarding Documents to Other Build Groups

By default, consolidated documents are forwarded to the Indexing Server of a specific build group, for example, bg0. However, for advanced cases, consolidated documents can also be useful for several build groups or other Consolidation Servers. To fulfill these needs, you can define forward rules in your Consolidation configuration to forward consolidated documents to the target of your choice.

This task shows you how to:

See Also
Configuring the Processors
Trigger and Synchronize Consolidation

Context:

The following diagram shows the forward of consolidated documents to another build group on the same Exalead CloudView instance. Documents are sent to another Indexing Server and stored in another Index.

Important: Delete orders are pushed to all build groups without checking forward rules.

Write Forward Rules in the Administration Console

  1. Go to Index > Consolidation > Forward rules.
  2. In Forward to, select the target build group or Consolidation Server on which you want to forward consolidated documents.
  3. In the Document types field, enter the comma-separated list of document types that to forward, that is to say the document types specified in the transformation and aggregation processors. Leave this field empty to forward all document types.
  4. Select Trigger indexing if you want to trigger an indexing job on the target build group or Consolidation Server automatically. This bypasses the commit conditions defined on the target build group or Consolidation Server.
  5. Click Apply.
  6. Clear and reindex your documents with the main Consolidation Server.

Write Forward Rules in the API Console

  1. Open the Exalead CloudView API Console, <HOSTNAME>:<BASEPORT+1>/api-ui/
  2. Click Manage.
  3. Search for the setConsolidationConfigList method.
  4. Edit the AggregationForwardProcessorConfigList node to write your forward rules. 

    <conso:ConsolidationConfig ...>
  <conso:AggregationForwardProcessorConfigList>
    <conso:AggregationForwardProcessorConfig triggerIndexing="true" pushAPIServer="bg1"/>
  </conso:AggregationForwardProcessorConfigList>
</conso:ConsolidationConfig>

  5. Click Save.
  6. Click Apply.
  7. Clear and reindex your documents with the main Consolidation Server.