Promoting BIRT reports from a dev environment to production - best practices??

John F

<p>I'm new to Actuate/BIRT.. using iHub3 we have separate dev and prod servers.  </p><p> </p><p>Question is - when I design a report in the dev environment how do I promote it (and it's resources) to the prod environment?  Assume the dev and prod server file systems can see each other.  Can the separate iHub instances see each other?  What are most people doing to make this as painless as possible?  </p><p> </p><p>Many thanks - John</p>

GLO_FR

<div>Hi John,</div><div> </div><div>what I mostly saw is that everything which was published on the iHub, was done with an external ressource manager.</div><div> </div><div>The global workflow from one environment to another was something like that</div><div> </div><div>1) From your ressource manager, select in env1 what should be promoted</div><div>2) get the all tagged package (design, resources, libraries...) from env 1</div><div>3) upload/promote to env 2</div><div>4) update ressource manager references</div><div> </div><div>With the iHub API, you can manage the iHub remotely (command line, scripiting, program...), so everything can be done automaticaly in a standard way.</div>