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
- On your Content Delivery server environment, access the configuration location of your Content Deployer.
- 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.
- Find the
Stepelement that takes care of indexing content. It has itsIdattribute set toIshSearchIndexDeployStep. - Within this element, find the child element called
Transactions. ItsfailPipelineTransactionOnFatalIndexingErrorattribute specifies whether a fatal indexing error should cause the entire Pipeline transaction to be aborted (valuetrue, the default), or to continue despite the failure (valuefalse). - 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
failtransactiononfatalindexingerrorand set it tofalse. - If you prefer to configure by editing the configuration file itself, in deployer-conf.xml, set the value of the
failPipelineTransactionOnFatalIndexingErrorattribute tofalse. Then save and close deployer-conf.xml.
- If you prefer to configure using environment variables, create an environment variable called