17. Deployment Templates
Deployment Templates allow you to define default settings and their appearance and save them to be used as the basis for a new Package. Almost every subset of a Package's options and settings can be defined in a template. However, certain areas, such as Package dependencies, cannot be retained in a template as they pertain to specific application or Package information.
Why use deployment templates?
- If you are deploying using the same deployment scenario repeatedly, saving the initial Package as a template and then using this template to create subsequent Packages saves time and ensures consistency in the deployment options and settings.
- By using templates, you can greatly limit the amount of information displayed on the Package Control Panel - thus reducing the amount of time it takes to define or assemble a new Package. You can specify that an option is hidden from view, not allowed to be changed, or be visible and editable. This means that there may only be a handful of options to select and some of these options may be highlighted as "must be considered".
A set of predefined templates are supplied with the Deployment Tool. These are described in 17.4 Supplied Deployment Templates.
Also see
17.1 Create a Deployment Template
17.2 Review, Change or Delete a Deployment Template
17.3 Deployment Template Options & Settings
17.4 Supplied Deployment Templates
