You define a target site on its Details tab, where you supply data for the following fields, then click Save Changes. After you define deployment target sites, you can return to the workflows that your environment uses and specify these targets in the appropriate task elements.
You can also use the Details tab to delete a target site.
Caution: Before deleting a target site, make sure no active project uses a workflow that includes that target.
Site Name
Supply the target site’s name—for example, Staging, or Production. See Identify Deployment Target Sites for more information.
Note: The Installed Workflows that ATG provides predefine one or two target sites with the following identifiers:
Productionis the sole target defined in the Production-Only workflow.StagingandProductiontargets are defined in the Staging/Production workflow.
In order to use a workflow with these predefined target site identifiers, you must define the deployment topology with site names that correspond exactly to these identifiers. You must also set the following property to false:
/atg/epub/Configuration.queryWorkflowTargetByID
Site Type
Choose one of the following options:
Workflow target: A target that is defined in a project workflow. Project assets are deployed to this target only after they are approved for deployment
One-off target: A target that is available for deployment from any project at any workflow stage. Development sites that are used to test code or performance are typically suitable for this designation. For more information, see One-Off Deployments in the Deployment Concepts chapter.
After the target site is initialized, its site type designation cannot be changed.
Site Initialization Options
Choose one of the following options:
Flag Agents Only: Select if the data on the target site was imported for use as the starting data for the versioned database on the asset management server. If so, a full deployment is unnecessary when this target is initialized, because the same data is being sent back to the target site. Flag Agents Only initializes the target only with data that changed since the original data was imported.
Do a Full Deployment: Select if target site data differs from versioned data on the asset management server. This option ensures that data is the same on both. Be aware that a full deployment can be time-consuming.
Site Description
Enter text you can use to identify this target. The description appears in the Deployment Administration Overview list for this target. You can edit the description later if required.
Source Repository and Destination Repository
You use the Source Repository and Destination Repository to set up mappings between this target’s source and destination repositories. For each mapping, follow these steps:
Choose a versioned source repository whose assets you wish to deploy to this target.
This list is populated with all versioned repositories in the application’s configuration path. If the items you need do not appear, make sure all appropriate modules are included in your application.
If you are using direct DQL deployment (see Configure Direct SQL Deployment), specify a prefix or a suffix.
Use a prefix to specify one of the following:
MSSQL linked server and schema name
The prefix must end with a dot ( . ).
Use a suffix to specify the name of an Oracle database link. The suffix must begin with the @ symbol.
Note that if you are using switching datasources, you must configure links for both of them as shown in the following screen shot.
Example 1: For an Oracle database where the schemas are on different machines, if the destination schema is named PROD and the Oracle database link name is PROD_LINK, use the following:
Prefix:
PROD.Suffix:
@PROD_LINKExample 2: For an MSSQL database using linked servers, use the following:
Prefix:
remote_host_name.remote_schema_name.dboSuffix: (empty)
Example 3: For an MSSQL or Oracle database where the schemas are on the same machine, use the following:
Prefix:
PRODSuffix: (empty)
Choose the matching destination repository on the asset management server. This is the repository that is configured to point to the target server’s database; for more information, see Configure Deployment Data Sources and Destination Repositories.
Click Add. The mapping is added to the Source Repository list.
To remove a mapping from this list, click X.
