Skip to Content

Key features

This page contains the following topics:

Getting started with automated schema change deployment

Automated schema change deployment is the foundation of BMC AMI DevOps for Db2. It enables teams to treat database changes like application code—versioned, validated, and deployed automatically. This reduces manual effort and ensures consistency across environments.

Audience: Application developers, Db2 DBAs, DevOps engineers.
Goal: Automate the deployment of Db2 schema changes using continuous integration/continuous delivery (CI/CD) pipelines.

Key steps:

  1. Create a schema change collection with versioned DDL scripts
  2. Validate the schema change collection
  3. Configure deployment settings
  4. Deploy via CI/CD
  5. Monitor deployment status

Getting started with CI/CD tool integration

CI/CD integration enables automated deployment of database changes and schema validation together with application code. The product supports tools like Jenkins, Azure DevOps, GitHub Actions, and GitLab CI/CD.

Audience: DevOps engineers, application developers.
Goal: Integrate BMC AMI DevOps for Db2 with CI/CD tools.

Key steps:

  1. Install and configure plug-ins or scripts
  2. Define pipeline steps for schema change collection and deployment
  3. Trigger deployments from CI/CD workflows

Getting started with rollback automation

Rollback automation ensures safe recovery when deployments fail. Rollback scripts are generated alongside schema change collection and can be triggered automatically or manually, minimizing downtime and reducing risk.

Audience:  Db2 DBAs, DevOps engineers, application developers.
Goal: Configure and use rollback automation to recover from failed deployments.

Key steps:

  1. Enable rollback script generation
  2. Deploy the generated rollback script
  3. Monitor rollback events and logs

Getting started with validation and impact analysis

Validation and impact analysis at the Db2 level helps prevent errors by checking schema changes for syntax issues and dependencies. Schema can also be reviewed for business compliance standards. This ensures that changes won’t break existing objects or cause runtime failures.

Audience: Application developers, Db2 DBAs.
Goal: Validate schema changes and assess their impact before deployment.

Key steps:

  1. Run pre deployment validation
  2. Review dependency and impact reports
  3. Resolve flagged issues before deployment

Getting started with audit logging and compliance

Audit logging captures all deployment activity, user actions, and system changes in the CI/CD tools. This supports compliance with ITIL, SOX, and internal governance policies.

Audience: Compliance officers, system programmers, Db2 DBAs.
Goal: Track user actions and meet regulatory requirements.

Key steps:

  1. Access and export logs
  2. Monitor user activity

Getting started with environment deployment and configuration

Environment deployment allows users to control where and how schema change collections are deployed. This supports safe promotion and environment-specific configurations.

Audience: Db2 DBAs, DevOps engineers.
Goal: Manage deployments across DEV, QA, and PROD environments.

Key steps:

  1. Deploy schema change collections by environment
  2. Configure deployment rules
  3. Promote collections through lifecycle stages

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC AMI DevOps for Db2 13.1