Deploying change commands from the Deployment Script Editor

Change commands can be deployed from the Deployment Script Editor and issued against a DB2 database catalog.
Prerequisite: You must have a working connection to your existing databases and models of those databases in the Data Project Explorer before deploying your changes.
To deploy changes to the database catalog, complete the following steps:
  1. From the Deployment Script Editor, review and verify the information for your deployment script.
  2. Click Deploy Changes to the Target Database from the Overview page or the Change Commands page to start the Deployment wizard.
  3. Complete the steps in the Deployment wizard to deploy your changes.

    The Deployment wizard checks to see if your base model matches the database catalog. If the base model does not match the catalog the change might not deploy correctly.

    For more information on what to do if the base model is out of synch with the database catalog see the Common Problems topic.

Your changes have now been issued to the DB2 database catalog. The DB2 database catalog is updated and contains your changes. You can view the deployment results for each change command in the Data Output view. DB2® Change Management Expert also creates a deployment log file.

DB2 Change Management Expert manages the deployment and records the model version and other information for audit purposes.

Related concepts
Auditing
Related tasks
Generating change commands from the Deployment Script Editor
Refreshing a base model


Feedback

Copyright IBM Corporation 2006, 2007. All Rights Reserved.