We’re looking for a way of triggering batch scripts when a publishing job finishes under Rx6.5. Tech Support have advised that we can’t hook into post-publishing events (or similar), but have kindly suggested the following “classic” workaround:
[li]Create a process that monitors (polls) a certain directory for a certain file (for example: trigger.txt)
[/li][li]Publish a file with the given name (trigger.txt) as the last content list in an edition
[/li][li]The polling process calls the batch file to complete whatever processing is required
[/li][li]As the batch job completes it removes the file (trigger.txt)
We wondered whether anyone here has implemented a system such as this? If so, would you have any words of wisdom?
The ability to run tasks both before and after publishing was implemented in Version 6.6. A simple example is illustrated in the “Full Publish Edition” procedure in the Version 6.6 Implementation Guide, p. 328; specifically, see Step 10 on p. 330.