Deploying Marked Targets - trillium_quality - 2.7

Trillium Quality for Dynamics Installation and Developer Guide

Product type
Software
Portfolio
Verify
Product family
Trillium
Product
Trillium > Trillium Quality
Version
2.7
Language
English
Product name
Trillium Quality
Title
Trillium Quality for Dynamics Installation and Developer Guide
Topic type
How Do I
Overview
Configuration
Reference
Administration
Installation
First publish date
2008

After the configuration files have been generated, you are ready to deploy the project.

Note: If a project has been previously deployed, before re-deploying that project you should move, rename or delete the existing deployed project files on the target system. Overwriting an existing deployed project is not recommended.

To deploy the project

  1. In the Project Deployment Manager, click Check for errors.

    Errors, or a success message, will display in the Pre-deployment and deployment related errors and messages box. If there are no errors for the selected host, the host will be flagged with “Yes” in the Deployable column of the host list box.

    Once there are zero errors for a specific host, the project is ready to be deployed on that host.

  2. In the list of target hosts near the top of the window, use the Mark column to indicate hosts to which the project should be deployed.

    Note: For projects that will be deployed manually, such as projects being deployed to a cloud instance, see Deploying Manually.
  3. Click Deploy Marked Targets. When a project is deployed, the Project Deployment Manager creates a directory on the host and places a copy of all of the project configuration files and all other project files (DDL, DDT, DDX, STT, STX) in that directory. It also creates a zip file containing project files.

    A message indicates the number of successfully and unsuccessfully deployed hosts.

    If deployment fails due to a security problem on the target system, enable the Override failed login, the host(s) that failed will be manually deployed option, then manually deploy, as described on Deploying Manually.

  4. Close the Project Deployment Manager.