Typically, TDV developers and administrators use a development life cycle which is a sequence of environments (for example, development, test, and production environments) to build and test new features and functions. As testing and validation are performed, the code needs to be migrated to the next environment. The architecture of Deployment Manager supports the migration of resources from one environment to another as shown here:

Deployment Manager is structured around a “site”, which is an instance of TDV. Deployment Manager provides the tools for you to easily define a TDV site, create bundles of resources, retain resource relationships, user and group permissions, and so on which you can then migrate to another site. The specific resources you can migrate include:

You can also define how the data sources and principals (users, groups, and domains) are mapped to the target site. You can use the source site data source connection properties and principal names by default, or map them to something different on the target site.

A single instance of Deployment Manager can connect to all TDV source and target sites with the correct credentials. If a site is not available or accessible (perhaps it is a remote production site, offline, or on a different network), you can define the site as offline and create a deployment plan that includes the offline site. A deployment plan can be exported and executed on a remote site at a later time.

An example of the resources that you might define for a source site is illustrated here:

After you’ve defined the source and target sites and the source site resource and principal bundles and their mappings, you can create a deployment plan. The deployment plan specifies the resource and principal bundles you want to migrate, resources that you want to remove from the target site (if any), and any procedure calls to execute that further customize the deployment.

See these sections for more overview information about Deployment Manager: