You can define deployment topology through this XML file:
<ATG2007.3dir>/Publishing/base/src/config/atg/epub/deploymentTopology.xml
The tags are described in the previous section and also within the XML file itself.
The following example shows part of a deploymentTopology.xml file.
<publishing-deployment-topology> <target> <target-name>Production</target-name> <agent> <agent-name>PubAgent</agent-name> <principal-asset>NONE</principal-asset> <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> <principal-asset>NONE</principal-asset> <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>
You specify an agent’s deployment responsibilities through three tags:
<
principalasset>can be set toALL,REPOSITORY,VFS, orNONE<includeassetdestination>includes this asset destination for the given agent.<excludeassetdestination>excludes this asset destination for the given agent
Tags <includeassetdestination> and <excludeassetdestination> are set to the destination’s absolute component name in Nucleus. Multiple instances of the <includeassetdestination> and <excludeassetdestination> include and exclude multiple asset destinations, respectively. For example, if you set <principalasset> to REPOSITORY, you can then further define the deployment responsibilities for that agent through include and exclude tags.
Note: When manually supplying values in a deploymentTopology.xml file for tags <includeassetdestination> and <excludeassetdestination>, specify the names of the repositories exactly as they are listed in the Version Manager.
The <repositorymapping> tags specify the source and destination repositories for the deployment.
Importing a previous version
You can import a deploymentTopology.xml file used with a previous version of ATG Content Administration.
To import a deploymentTopology.xml file:
Access the ATG Business Control Center, and log in as a user with access rights to the Admin Console.
In the Home page, under Content Administration click Admin Console
From the Deployment Administration page, click Configuration
From the Deployment Administration Configuration, click Import from XML
