Automating the publishing process

Has anyone used the SDL APIs to automate the publishing process? We would like some way to initiate the publishing of multiple publications without having to open each publication in Publication Manager. Plus, when each publication has completed publishing, we would like it automatically copied to a specified server.

And if you have done something similar, did you do it in-house, or did you use SDL Professional Services to accomplish it?

We are currently using LCA 2014, but will be using Tridion Docs 13 soon.

Parents
  • I have built publishing automations using several methods, including web API calls (via Java) to set the output format FISHPUBSTATUS metadata to VPUBSTATUSPUBLISHPENDING to trigger a republish of the output. Using other API calls, you can get the date/time stamp from the output, as well as the baseline information, to determine if the output is up-to-date or needs to be republished. Of course, you could do all these things via the PowerShell library that Dave mentioned in his reply. You may want to consider using Jenkins to control the activity, also, whether you're launching a PowerShell script or Java app or something else (e.g., Python). I've also built some publishing automations that modify the internal publish.wsf script to do certain things (such as push content to a separate server after publishing), but not sure that is the most ideal or recommended way to go. I prefer the API approach to the internal script modification, but both are possibilities depending on your specific requirements.

Reply
  • I have built publishing automations using several methods, including web API calls (via Java) to set the output format FISHPUBSTATUS metadata to VPUBSTATUSPUBLISHPENDING to trigger a republish of the output. Using other API calls, you can get the date/time stamp from the output, as well as the baseline information, to determine if the output is up-to-date or needs to be republished. Of course, you could do all these things via the PowerShell library that Dave mentioned in his reply. You may want to consider using Jenkins to control the activity, also, whether you're launching a PowerShell script or Java app or something else (e.g., Python). I've also built some publishing automations that modify the internal publish.wsf script to do certain things (such as push content to a separate server after publishing), but not sure that is the most ideal or recommended way to go. I prefer the API approach to the internal script modification, but both are possibilities depending on your specific requirements.

Children