Bsrhrki

I am trying to create a custom deployer module which runs AFTER the content (in this case a page) has been committed to the broker database. I know that in UDP there are different pipelines, each representing a different stage in the deployment process (called Verbs in the code). By debugging the code and by looking at the deployer-conf.xml that SDL provides, I found out that there are at least the following Verbs (stages):

• Prepare


• Process


• Content


• PreCommit


• Commit


• Rollback

However, as far as I can tell, ALL these stages take place before the database transaction is committed.

I've tried the following XML configurations:

Verb=Process (added my steps to the steps that were already there)

<Pipeline Id="Tridion-Process-Deploy" Action="Deploy" Verb="Process">
 <Steps>
 <Step Id="PageDeploy" Factory="com.sdl.delivery.deployer.steps.TridionExecutableStepFactory">
 <Module Class="com.tridion.deployer.modules.PageDeploy" Type="PageDeploy"/>
 </Step>
<!-- removed other steps for clarity's sake -->
 <Step Id="PageDeployFast" Factory="com.sdl.delivery.deployer.steps.TridionExecutableStepFactory">
 <Module Type="PageDeploy" Class="com.tridion.storage.extension.deployer.SolrPageDeploy" />
 </Step>
</Steps>
</Pipeline>

Verb=Commit (new pipeline created specifically for my module)

<Pipeline Id="Tridion-Commit-Deploy" Action="Deploy" Verb="Commit">
 <Steps>
 <Step Id="PageDeployFast" Factory="com.sdl.delivery.deployer.steps.TridionExecutableStepFactory">
 <Module Type="PageDeploy" Class="com.tridion.storage.extension.deployer.SolrPageDeploy" />
 </Step>
 </Steps>
</Pipeline>

Verb=PreCommit (also a new pipeline)

<Pipeline Id="Tridion-PreCommit-Deploy" Action="Deploy" Verb="PreCommit">
 <Steps>
 <Step Id="PageDeployFast" Factory="com.sdl.delivery.deployer.steps.TridionExecutableStepFactory">
 <Module Type="PageDeploy" Class="com.tridion.storage.extension.deployer.SolrPageDeploy" />
 </Step>
 </Steps>
</Pipeline>

In all cases, my module got triggered AFTER the out of the box page deploy module, but unfortunately BEFORE the database transaction had been committed.

I also tried the verb 'PostCommit' but that doesn't seem to exist. My module does not get triggered at all when I use that.

Is there any way to trigger my custom deployer module AFTER the database transaction has been committed?

You should be able to add a pipeline element after the "Tridion-Commit-TX" pipeline which then should act as a PostCommit. In XO, the same happens:

<!-- Add the following pipelines after the existing "Tridion-Commit-TX" pipelines -->
<Pipeline Id="Tridion-Process-PostCommit" Action="Deploy" Verb="Process">
 <Steps>
 <Step Id="XoContentFragmentDeploy">
 <Transformer Class="com.tridion.transformer.TCDLDefaultTransformer"/>
 </Step>
 </Steps>
</Pipeline>

https://docs.sdl.com/LiveContent/content/en-US/SDL%20Tridion%20Sites-v1/GUID-93347DFB-D6EB-4398-A78D-220B7FD685E3

Go to your Content Deployer's config folder, and open deployer-conf.xml for editing.
Find the last Pipeline section in the file, and add the following two Pipeline sections below the last Pipeline section in the file:

<Pipeline Id="Tridion-Process-PostCommit" Action="Deploy" Verb="Process">
 <Steps>
 <Step Id="XoContentFragmentDeploy">
 <Transformer Class="com.tridion.transformer.TCDLDefaultTransformer"/>
 </Step>
 </Steps>
</Pipeline>
<Pipeline Id="Tridion-Undeploy-PostCommit" Action="Undeploy" Verb="Process">
 <Steps>
 <Step Id="XoContentFragmentUnDeploy" />
 </Steps>
</Pipeline>