How to Extend IBM Urbancode Deploy's Automation Capabilities to the Database
A database continuous delivery solution provides enforced version control and reliable deployment automation for the database.
Join the DZone community and get the full member experience.Join For Free
in the ever-competitive software space, businesses are constantly striving to make more changes faster, without becoming exposed to excessive risk.
ibm urbancode deploy orchestrates
and automates the deployment of applications, middleware configurations, and database changes into development, test, and production environments.
there is a need to safely include the database component within the existing deployment processes of the application tiers, from building (generating upgrade sql scripts ), to verifying that the environments are identical (no drifts), to deploying (executing the planned upgrade sql scripts), while documenting the changes.
to accomplish this, you need a database continuous delivery solution that provides enforced version control and reliable deployment automation for the database. a common continuous delivery process consists of various applicative and database components. dbmaestro teamwork offers an integration with ibm urbancode deploy by enhancing it with the required functionality to include database build & deployment tasks.
this post covers the integration of urbancode deploy with dbmaestro.
after completing the installation of the dbmaestro teamwork plugin, get started by creating a process. first, apply a label on the source environment. dbmaestro teamwork will automatically generate the database deployment script. then, apply a label on the target environment. it will be used as backup.
enable deployment mode, which allows executions of the script and modification of the objects. next, execute the script using an sql plugin or any other tool. after executing the script, exit the deployment mode. at this point, dbmaestro teamwork identifies the changed objects and marks them as being checked out.
check on the objects and ensure the repository is being updated to have the same definition as the database. apply a label on the target after deployment is completed successfully. this will be used as a baseline for the next execution of the process.
when the process is completed, it can be integrated with the rest of the application automation. dbmaestro teamwork will pause the automation process in case of conflicts. these conflicts can arise as a result of working in parallel mode or critical fix release.
once your integration is set up, explore how you can bring complete automation to your delivery pipeline, supporting your continuous delivery or devops initiatives.
join a free online demo here.
Published at DZone with permission of Yaniv Yehuda, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.