Key concepts

Learn about the following areas of the BMC AMI DevOps for Db2 product.
The following key concepts apply throughout the system and provide the foundation for how database changes are created, validated, deployed, and managed in a DevOps environment.

This section introduces the key ideas that support the product’s functionality.

• Schema change collection
  A schema change collection is a version-controlled bundle of Db2 schema changes (DDL) grouped for deployment. It includes metadata, environment tags, and rollback scripts. Schema change collections are the central unit of work in BMC AMI DevOps for Db2.

• CI/CD integration
  You can integrate the product with modern continuous integration/continuous delivery (CI/CD) tools such as Jenkins, Azure DevOps, GitHub Actions, and GitLab CI/CD, so that you can deploy database changes together with application code. This integration supports continuous delivery and reduces manual intervention.
• Validation and impact analysis
  Before deployment, schema changes are automatically validated for syntax, dependencies, and potential impact. You can review schema standards for business compliance standards. This helps prevent runtime errors and ensures stability across environments.
• Environment deployment
  You can deploy each schema change collection to specific environments, such as DEV, QA, or PROD, ensuring that deployments are targeted and controlled. This supports safe promotion of changes through the release lifecycle.
• Rollback automation
  The product generates and maintains scripts together with deployment scripts, so you can revert failed deployments quickly and safely. This minimizes downtime and supports recovery planning.
• Audit and compliance
  The product logs all user actions and deployment events, providing full traceability in the CI/CD tools. This supports internal governance and external regulatory compliance such as ITIL and SOX.