The deployment script is the central resource in the deployment
process. When you deploy a deployment script you are issuing commands to change
a DB2 database.
The following figure illustrates the process of deploying changes to a
target database:
Figure 1. The process of deploying changes to your target
database
The deployment script binds the change management resources together and
organizes those resources into a coherent form. You use the deployment script
to deploy changes to your DB2 databases.
The following figure illustrates the process of using a deployment script
to deploy your changes to a database catalog.
Figure 2. Using the deployment script to deploy your changes
The deployment script describes specification resources, change commands,
and metadata about how the change will be issued.
- Specification resources
- Specification resources are the models and deltas that make
up a change. The most important of these resources are the base and target models of the database. Another
important resource are source models.
Source models contain changes to migrate as part of the change and can be
associated by using the deployment script.
The goal of the specification
phase is to create the post-condition of the schema after the change is implemented.
Part of that post-condition might include migrating objects from other database
catalogs or integrating changes that are specified by a delta. These additional
resources can be associated with the change. By associating additional resources
with the change you can:
- Verify your work
- Help others understand the motivation for the change
- Historically tie resources together at points in time
- Change commands
- Change commands describe how the change will be implemented. The deployment
script enables you to order these commands and provides wizards and editors
to manipulate the commands.
- Metadata
- The deployment script provides metadata about the change. Use the Overview
page of the Deployment Script Editor to specify the metadata and resources
that are pertinent to the change, such as the target database connection,
models, and change command files.