Deployment groups manage the associations between a set
of artifacts and the server profiles that are used to deploy them.
There are several key benefits to using deployment groups to deploy
and bind artifacts to a database server.
A deployment group is a collection of artifacts and server profiles
that are used to manage the deployment or binding of the artifacts
in the group to the database servers that are associated with the
server profiles in the group. Using the Deployment Manager view, you
can create and manage deployment groups and view or generate reports
for deployment results.
The benefits of using deployment groups include:
- You can manage the deployment or binding of multiple artifacts
at once. This is more efficient than deploying or binding each artifact
individually.
- You can control the order of deployment for artifacts within a
deployment group. This is helpful in situations where artifact dependencies
exist; for example, if you need to create a table before you can create
an index on that table.
- You can use server profiles to manage the settings that you use
to deploy or bind artifacts in one place, so you only have to specify
them once. If you deploy or bind artifacts individually with the Deploy
Routines wizard, you have to specify some of these settings each time
you deploy or bind.
- You can deploy artifacts in a deployment group to multiple servers
or multiple configurations of the same server at the same time.
- You can view the results of each deployment and view and share
reports for each deployment with other team members. This collaboration
allows for better tracking of and communication about each deployment.
- You can compare routines (stored procedures and user-defined functions)
that have been deployed using deployment groups with their source
in the workspace. This comparison allows you to more easily determine
which objects have been modified in the workspace since they were
last deployed.
You can deploy the following types of artifacts from deployment
groups:
- Stored procedures
- User-defined functions
- SQL statements
- PL/SQL packages
- pureQuery DB2® static bind
artifacts:
- An interface that contains pureQuery annotations
or
- A .pdqxml or .xml file that contains SQL statements that can be
static bound against a DB2 server