Configuring the response to a fatal indexing error

By default, the Content Deployer is configured to abort the entire Pipeline transaction if a fatal indexing error occurs. Only if you have a pressing reason to do so, change this behavior.

Procedure

  1. On your Content Delivery server environment, access the configuration location of your Content Deployer.
  2. Depending on your preference, do one of the following:
    • If you prefer to configure using environment variables, open deployer-conf.xml for viewing.
    • If you prefer to configure by editing the configuration file itself, open deployer-conf.xml for editing.
  3. Find the Step element that takes care of indexing content. It has its Id attribute set to IshSearchIndexDeployStep.
  4. Within this element, find the child element called Transactions. Its failPipelineTransactionOnFatalIndexingError attribute specifies whether a fatal indexing error should cause the entire Pipeline transaction to be aborted (value true, the default), or to continue despite the failure (value false).
  5. If you have a specific reason for wanting to deploy content despite a fatal indexing error, then depending on your preference, do one of the following:
    • If you prefer to configure using environment variables, create an environment variable called failtransactiononfatalindexingerror and set it to false.
    • If you prefer to configure by editing the configuration file itself, in deployer-conf.xml, set the value of the failPipelineTransactionOnFatalIndexingError attribute to false. Then save and close deployer-conf.xml.