How can I run a deployer module after the commit?
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?
==== ANSWER ====
Raimond and Andrew both put me on the right track. The key thing to note is that the pipelines are executed in the order in which they occur in the deployer-conf.xml. There is one pipeline which contains the step to perform the database commit, namely Tridion-Commit-TX. To run a module post commit, just insert a pipeline after this one. Be careful though: you must put it BEFORE the Tridion-Cleanup pipeline, else your module cannot be instantiated anymore because the files on which it is based are gone.
web8.5 deployer deployer-extension sites-9 deployer-conf
|
show 1 more comment
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?
==== ANSWER ====
Raimond and Andrew both put me on the right track. The key thing to note is that the pipelines are executed in the order in which they occur in the deployer-conf.xml. There is one pipeline which contains the step to perform the database commit, namely Tridion-Commit-TX. To run a module post commit, just insert a pipeline after this one. Be careful though: you must put it BEFORE the Tridion-Cleanup pipeline, else your module cannot be instantiated anymore because the files on which it is based are gone.
web8.5 deployer deployer-extension sites-9 deployer-conf
what are you looking for? the markup for a deployer pipeline with custom module in it? tridion.stackexchange.com/questions/18757/…
– Andrew William Ross
Apr 2 at 13:42
I have the markup, and I am able to trigger my module. But it comes too soon in the process, when the database commit has not yet been issued.
– Quirijn
Apr 2 at 13:47
Wait, isn't the XO post commit?
– Marko Milic
Apr 2 at 13:48
I updated the question with the various XML configurations I tried.
– Quirijn
Apr 2 at 13:55
oh so you require transaction to finish, get final state, and after that execute something?
– Marko Milic
Apr 2 at 13:57
|
show 1 more comment
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?
==== ANSWER ====
Raimond and Andrew both put me on the right track. The key thing to note is that the pipelines are executed in the order in which they occur in the deployer-conf.xml. There is one pipeline which contains the step to perform the database commit, namely Tridion-Commit-TX. To run a module post commit, just insert a pipeline after this one. Be careful though: you must put it BEFORE the Tridion-Cleanup pipeline, else your module cannot be instantiated anymore because the files on which it is based are gone.
web8.5 deployer deployer-extension sites-9 deployer-conf
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?
==== ANSWER ====
Raimond and Andrew both put me on the right track. The key thing to note is that the pipelines are executed in the order in which they occur in the deployer-conf.xml. There is one pipeline which contains the step to perform the database commit, namely Tridion-Commit-TX. To run a module post commit, just insert a pipeline after this one. Be careful though: you must put it BEFORE the Tridion-Cleanup pipeline, else your module cannot be instantiated anymore because the files on which it is based are gone.
web8.5 deployer deployer-extension sites-9 deployer-conf
web8.5 deployer deployer-extension sites-9 deployer-conf
edited Apr 3 at 9:03
Quirijn
asked Apr 2 at 13:36
QuirijnQuirijn
4,537931
4,537931
what are you looking for? the markup for a deployer pipeline with custom module in it? tridion.stackexchange.com/questions/18757/…
– Andrew William Ross
Apr 2 at 13:42
I have the markup, and I am able to trigger my module. But it comes too soon in the process, when the database commit has not yet been issued.
– Quirijn
Apr 2 at 13:47
Wait, isn't the XO post commit?
– Marko Milic
Apr 2 at 13:48
I updated the question with the various XML configurations I tried.
– Quirijn
Apr 2 at 13:55
oh so you require transaction to finish, get final state, and after that execute something?
– Marko Milic
Apr 2 at 13:57
|
show 1 more comment
what are you looking for? the markup for a deployer pipeline with custom module in it? tridion.stackexchange.com/questions/18757/…
– Andrew William Ross
Apr 2 at 13:42
I have the markup, and I am able to trigger my module. But it comes too soon in the process, when the database commit has not yet been issued.
– Quirijn
Apr 2 at 13:47
Wait, isn't the XO post commit?
– Marko Milic
Apr 2 at 13:48
I updated the question with the various XML configurations I tried.
– Quirijn
Apr 2 at 13:55
oh so you require transaction to finish, get final state, and after that execute something?
– Marko Milic
Apr 2 at 13:57
what are you looking for? the markup for a deployer pipeline with custom module in it? tridion.stackexchange.com/questions/18757/…
– Andrew William Ross
Apr 2 at 13:42
what are you looking for? the markup for a deployer pipeline with custom module in it? tridion.stackexchange.com/questions/18757/…
– Andrew William Ross
Apr 2 at 13:42
I have the markup, and I am able to trigger my module. But it comes too soon in the process, when the database commit has not yet been issued.
– Quirijn
Apr 2 at 13:47
I have the markup, and I am able to trigger my module. But it comes too soon in the process, when the database commit has not yet been issued.
– Quirijn
Apr 2 at 13:47
Wait, isn't the XO post commit?
– Marko Milic
Apr 2 at 13:48
Wait, isn't the XO post commit?
– Marko Milic
Apr 2 at 13:48
I updated the question with the various XML configurations I tried.
– Quirijn
Apr 2 at 13:55
I updated the question with the various XML configurations I tried.
– Quirijn
Apr 2 at 13:55
oh so you require transaction to finish, get final state, and after that execute something?
– Marko Milic
Apr 2 at 13:57
oh so you require transaction to finish, get final state, and after that execute something?
– Marko Milic
Apr 2 at 13:57
|
show 1 more comment
2 Answers
2
active
oldest
votes
You should be able to add a pipeline element after the "Tridion-Commit-TX" pipeline and before the Cleanup Step, 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>
hahah raimond you had quicker fingers. :D in any case, here is the link: docs.sdl.com/LiveContent/content/en-US/…
– Marko Milic
Apr 2 at 13:54
I guess in my case I should have a Module instead of a Transformer in that step? And does the Id of the Step matter?
– Quirijn
Apr 2 at 14:22
You can create a module or a step if I'm not mistaken. I don't think the Id matters indeed.
– Raimond
Apr 2 at 18:00
3
It works! Only one thing: if your step contains a Module instead of a Transformer (like mine does), you must put it BEFORE the step with the ID Tridion-Cleanup. Otherwise the zip folder is cleaned up, and you will get an NullPointerException during the instantiation of your module. So put it ALMOST at the end, but before the cleanup step!
– Quirijn
Apr 3 at 8:47
True! Good to see it's solved.
– Raimond
Apr 3 at 13:09
add a comment |
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>
1
Hi Andrew, I think the first <Pipeline...> element went missing in your answer. Could you add that? Meanwhile, I will try it out.
– Quirijn
Apr 2 at 14:04
thanks did from my phone.. tricky ;)
– Andrew William Ross
Apr 2 at 14:23
Thanks for your help. You were correct, just like Raimond, but I marked his answer as correct because it had the additional discussion which might be helpful to people in the future. I upvoted your answer too.
– Quirijn
Apr 3 at 8:49
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "485"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftridion.stackexchange.com%2fquestions%2f19954%2fhow-can-i-run-a-deployer-module-after-the-commit%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
You should be able to add a pipeline element after the "Tridion-Commit-TX" pipeline and before the Cleanup Step, 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>
hahah raimond you had quicker fingers. :D in any case, here is the link: docs.sdl.com/LiveContent/content/en-US/…
– Marko Milic
Apr 2 at 13:54
I guess in my case I should have a Module instead of a Transformer in that step? And does the Id of the Step matter?
– Quirijn
Apr 2 at 14:22
You can create a module or a step if I'm not mistaken. I don't think the Id matters indeed.
– Raimond
Apr 2 at 18:00
3
It works! Only one thing: if your step contains a Module instead of a Transformer (like mine does), you must put it BEFORE the step with the ID Tridion-Cleanup. Otherwise the zip folder is cleaned up, and you will get an NullPointerException during the instantiation of your module. So put it ALMOST at the end, but before the cleanup step!
– Quirijn
Apr 3 at 8:47
True! Good to see it's solved.
– Raimond
Apr 3 at 13:09
add a comment |
You should be able to add a pipeline element after the "Tridion-Commit-TX" pipeline and before the Cleanup Step, 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>
hahah raimond you had quicker fingers. :D in any case, here is the link: docs.sdl.com/LiveContent/content/en-US/…
– Marko Milic
Apr 2 at 13:54
I guess in my case I should have a Module instead of a Transformer in that step? And does the Id of the Step matter?
– Quirijn
Apr 2 at 14:22
You can create a module or a step if I'm not mistaken. I don't think the Id matters indeed.
– Raimond
Apr 2 at 18:00
3
It works! Only one thing: if your step contains a Module instead of a Transformer (like mine does), you must put it BEFORE the step with the ID Tridion-Cleanup. Otherwise the zip folder is cleaned up, and you will get an NullPointerException during the instantiation of your module. So put it ALMOST at the end, but before the cleanup step!
– Quirijn
Apr 3 at 8:47
True! Good to see it's solved.
– Raimond
Apr 3 at 13:09
add a comment |
You should be able to add a pipeline element after the "Tridion-Commit-TX" pipeline and before the Cleanup Step, 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>
You should be able to add a pipeline element after the "Tridion-Commit-TX" pipeline and before the Cleanup Step, 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>
edited Apr 3 at 13:09
answered Apr 2 at 13:49
RaimondRaimond
6,9881329
6,9881329
hahah raimond you had quicker fingers. :D in any case, here is the link: docs.sdl.com/LiveContent/content/en-US/…
– Marko Milic
Apr 2 at 13:54
I guess in my case I should have a Module instead of a Transformer in that step? And does the Id of the Step matter?
– Quirijn
Apr 2 at 14:22
You can create a module or a step if I'm not mistaken. I don't think the Id matters indeed.
– Raimond
Apr 2 at 18:00
3
It works! Only one thing: if your step contains a Module instead of a Transformer (like mine does), you must put it BEFORE the step with the ID Tridion-Cleanup. Otherwise the zip folder is cleaned up, and you will get an NullPointerException during the instantiation of your module. So put it ALMOST at the end, but before the cleanup step!
– Quirijn
Apr 3 at 8:47
True! Good to see it's solved.
– Raimond
Apr 3 at 13:09
add a comment |
hahah raimond you had quicker fingers. :D in any case, here is the link: docs.sdl.com/LiveContent/content/en-US/…
– Marko Milic
Apr 2 at 13:54
I guess in my case I should have a Module instead of a Transformer in that step? And does the Id of the Step matter?
– Quirijn
Apr 2 at 14:22
You can create a module or a step if I'm not mistaken. I don't think the Id matters indeed.
– Raimond
Apr 2 at 18:00
3
It works! Only one thing: if your step contains a Module instead of a Transformer (like mine does), you must put it BEFORE the step with the ID Tridion-Cleanup. Otherwise the zip folder is cleaned up, and you will get an NullPointerException during the instantiation of your module. So put it ALMOST at the end, but before the cleanup step!
– Quirijn
Apr 3 at 8:47
True! Good to see it's solved.
– Raimond
Apr 3 at 13:09
hahah raimond you had quicker fingers. :D in any case, here is the link: docs.sdl.com/LiveContent/content/en-US/…
– Marko Milic
Apr 2 at 13:54
hahah raimond you had quicker fingers. :D in any case, here is the link: docs.sdl.com/LiveContent/content/en-US/…
– Marko Milic
Apr 2 at 13:54
I guess in my case I should have a Module instead of a Transformer in that step? And does the Id of the Step matter?
– Quirijn
Apr 2 at 14:22
I guess in my case I should have a Module instead of a Transformer in that step? And does the Id of the Step matter?
– Quirijn
Apr 2 at 14:22
You can create a module or a step if I'm not mistaken. I don't think the Id matters indeed.
– Raimond
Apr 2 at 18:00
You can create a module or a step if I'm not mistaken. I don't think the Id matters indeed.
– Raimond
Apr 2 at 18:00
3
3
It works! Only one thing: if your step contains a Module instead of a Transformer (like mine does), you must put it BEFORE the step with the ID Tridion-Cleanup. Otherwise the zip folder is cleaned up, and you will get an NullPointerException during the instantiation of your module. So put it ALMOST at the end, but before the cleanup step!
– Quirijn
Apr 3 at 8:47
It works! Only one thing: if your step contains a Module instead of a Transformer (like mine does), you must put it BEFORE the step with the ID Tridion-Cleanup. Otherwise the zip folder is cleaned up, and you will get an NullPointerException during the instantiation of your module. So put it ALMOST at the end, but before the cleanup step!
– Quirijn
Apr 3 at 8:47
True! Good to see it's solved.
– Raimond
Apr 3 at 13:09
True! Good to see it's solved.
– Raimond
Apr 3 at 13:09
add a comment |
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>
1
Hi Andrew, I think the first <Pipeline...> element went missing in your answer. Could you add that? Meanwhile, I will try it out.
– Quirijn
Apr 2 at 14:04
thanks did from my phone.. tricky ;)
– Andrew William Ross
Apr 2 at 14:23
Thanks for your help. You were correct, just like Raimond, but I marked his answer as correct because it had the additional discussion which might be helpful to people in the future. I upvoted your answer too.
– Quirijn
Apr 3 at 8:49
add a comment |
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>
1
Hi Andrew, I think the first <Pipeline...> element went missing in your answer. Could you add that? Meanwhile, I will try it out.
– Quirijn
Apr 2 at 14:04
thanks did from my phone.. tricky ;)
– Andrew William Ross
Apr 2 at 14:23
Thanks for your help. You were correct, just like Raimond, but I marked his answer as correct because it had the additional discussion which might be helpful to people in the future. I upvoted your answer too.
– Quirijn
Apr 3 at 8:49
add a comment |
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>
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>
edited Apr 2 at 14:23
answered Apr 2 at 13:56
Andrew William RossAndrew William Ross
1,519718
1,519718
1
Hi Andrew, I think the first <Pipeline...> element went missing in your answer. Could you add that? Meanwhile, I will try it out.
– Quirijn
Apr 2 at 14:04
thanks did from my phone.. tricky ;)
– Andrew William Ross
Apr 2 at 14:23
Thanks for your help. You were correct, just like Raimond, but I marked his answer as correct because it had the additional discussion which might be helpful to people in the future. I upvoted your answer too.
– Quirijn
Apr 3 at 8:49
add a comment |
1
Hi Andrew, I think the first <Pipeline...> element went missing in your answer. Could you add that? Meanwhile, I will try it out.
– Quirijn
Apr 2 at 14:04
thanks did from my phone.. tricky ;)
– Andrew William Ross
Apr 2 at 14:23
Thanks for your help. You were correct, just like Raimond, but I marked his answer as correct because it had the additional discussion which might be helpful to people in the future. I upvoted your answer too.
– Quirijn
Apr 3 at 8:49
1
1
Hi Andrew, I think the first <Pipeline...> element went missing in your answer. Could you add that? Meanwhile, I will try it out.
– Quirijn
Apr 2 at 14:04
Hi Andrew, I think the first <Pipeline...> element went missing in your answer. Could you add that? Meanwhile, I will try it out.
– Quirijn
Apr 2 at 14:04
thanks did from my phone.. tricky ;)
– Andrew William Ross
Apr 2 at 14:23
thanks did from my phone.. tricky ;)
– Andrew William Ross
Apr 2 at 14:23
Thanks for your help. You were correct, just like Raimond, but I marked his answer as correct because it had the additional discussion which might be helpful to people in the future. I upvoted your answer too.
– Quirijn
Apr 3 at 8:49
Thanks for your help. You were correct, just like Raimond, but I marked his answer as correct because it had the additional discussion which might be helpful to people in the future. I upvoted your answer too.
– Quirijn
Apr 3 at 8:49
add a comment |
Thanks for contributing an answer to Tridion Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftridion.stackexchange.com%2fquestions%2f19954%2fhow-can-i-run-a-deployer-module-after-the-commit%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
what are you looking for? the markup for a deployer pipeline with custom module in it? tridion.stackexchange.com/questions/18757/…
– Andrew William Ross
Apr 2 at 13:42
I have the markup, and I am able to trigger my module. But it comes too soon in the process, when the database commit has not yet been issued.
– Quirijn
Apr 2 at 13:47
Wait, isn't the XO post commit?
– Marko Milic
Apr 2 at 13:48
I updated the question with the various XML configurations I tried.
– Quirijn
Apr 2 at 13:55
oh so you require transaction to finish, get final state, and after that execute something?
– Marko Milic
Apr 2 at 13:57