You can manually define deployment topology from an XML file, which uses the following DTD:

http://www.atg.com/dtds/publishing_deployment/publishing_deployment_1.0.dtd

The ATG distribution provides a template for creation of this file:

<atg10dir>/Publishing/base/src/config/atg/epub/deploymentTopology.xml

This section provides information about defining a deployment topology in XML and importing it into your ATG Content Administration environment. After you perform these tasks, you can initialize targets from the Admin Console’s Configuration page, as described later in this chapter in Initialize Target Sites.

Sample Deployment Topology XML

The following example shows part of a deploymentTopology.xml file:

<?xml version="1.0" encoding="utf-8"?>

<!DOCTYPE publishing-deployment-topology SYSTEM
    "http://www.atg.com/dtds/publishing_deployment/publishing_deployment_1.0.dtd">

<publishing-deployment-topology>
  <target>
    <target-name>Production</target-name>
    <agent>
      <agent-name>PubAgent</agent-name>
      <include-asset-destination>
        /atg/epub/file/ConfigFileSystem
      </include-asset-destination>
      <include-asset-destination>
        /atg/epub/file/WebAppRefFileSystem
      </include-asset-destination>
      <transport>
        <transport-type>RMI</transport-type>
        <rmi-uri>
          rmi://production1.yourcompany.com:8860/atg/epub/AgentTransport
        </rmi-uri>
      </transport>
    </agent>

    <agent>
      <agent-name>WebAgent1</agent-name>
      <include-asset-destination>
        /atg/epub/file/WWWFileSystem
      </include-asset-destination>
      <transport>
        <transport-type>RMI</transport-type>
        <rmi-uri>
          rmi://production2.yourcompany.com:8860/atg/epub/AgentTransport
        </rmi-uri>
      </transport>
    </agent>

<!--  Order matters. Repository mappings must come after agent tags.
-->

  <repository-mapping>
    <source-repository>/atg/MyRepository</source-repository>
    <destination-repository>/atg/MyRepository_production</destination-repository>
  </repository-mapping>

  <repository-mapping>
    <source-repository>/atg/MyRepository2</source-repository>
    <destination-repository>/atg/MyRepository2_production</destination-repository>
  </repository-mapping>

  <repository-mapping>
    <source-repository>/atg/commerce/catalog/ProductCatalog</source-repository>
    <destination-repository>
       /atg/commerce/catalog/ProductCatalog_staging
    </destination-repository>
  </repository-mapping>

  <repository-mapping>
    <source-repository>
      /atg/commerce/pricing/priceLists/PriceLists
    </source-repository>
    <destination-repository>
      /atg/commerce/pricing/priceLists/PriceLists_staging
    </destination-repository>
  </repository-mapping>

  </target>

  <target>
    <target-name>Staging</target-name>
    <!--  Agents in the Staging target defined here
    ...
    -->
  </target>

</publishing-deployment-topology>

The <repository-mapping> tags specify the source and destination repositories for the deployment.

Defining Targets for One-Off Deployment

By default, a target is defined for use in a project workflow. In order to define a target for One-Off Deployments, nest this tag in the <target> definition:

<target-deploy-type>ONE-OFF</target-deploy-type>

If this tag is not set, the target is available only for deployment within a project workflow. If desired, you can explicitly set a target for workflow deployment as follows:

<target-deploy-type>WORKFLOW</target-deploy-type>

Including and Excluding Asset Destinations

You specify an agent’s deployment responsibilities through two tags:

Tags <include-asset-destination> and <exclude-asset-destination> are set to the deployed repository or VFS’s absolute Nucleus component name on the asset manager server. Multiple instances of the <include-asset-destination> and <exclude-asset-destination> include and exclude multiple asset destinations, respectively.

The <exclude-asset-destination> tag is typically used to exclude a versioned content repository that is listed as a destination for the agent’s target—for example, in cases where that agent does not need to access the given repository. By excluding the repository, you avoid the overhead that the agent otherwise incurs by invalidating the repository cache during a switch.

Note: When manually supplying values in a deploymentTopology.xml file for tags <include-asset-destination> and <exclude-asset-destination>, specify the names of the repositories exactly as they are listed in the VersionManager.

Mapping VFSs

You can configure deployment so a VFS of one name on the asset management server deploys to a VFS of another name on the agent server. You do this through a <vfs-mapping> tag that embeds tags <source-vfs> and <destination-vfs>:

If these tags are omitted, the VFS on the agent and asset management servers are assumed to have the same name.

For example, a deployment topology might include the following VFS for deployment:

<include-asset-destination>/atg/epub/file/WWWFileSystem
</include-asset-destination>

You can map this VFS so it deploys on the agent server to the VFS WWWFileSystemOnAgent, as in the following example:

<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE publishing-deployment-topology SYSTEM
   "http://www.atg.com/dtds/publishing_deployment/publishing_deployment_1.0.dtd">

<publishing-deployment-topology>
<target>
<target-name>AgentMappingTest</target-name>
    <agent>
    <agent-name>TestAgent</agent-name>

    <include-asset-destination>/atg/epub/file/WWWFileSystem
    </include-asset-destination>

    <vfs-mapping>
      <source-vfs>/atg/epub/file/WWWFileSystem</source-vfs>
      <destination-vfs>/atg/epub/file/WWWFileSystemOnAgent</destination-vfs>
    </vfs-mapping>

    <transport>
    <transport-type>RMI</transport-type>
    <rmi-uri>rmi://localhost:8860/atg/epub/AgentTransport</rmi-uri>
    </transport>
    </agent>
</target>
</publishing-deployment-topology>

Importing a Deployment Topology File

You import a deploymentTopology.xml file as follows:

To import a deploymentTopology.xml file: