Deployment topology xml file

-
Deployment topology can be defined in 2 ways: manually creating using BCC or using the deploymentTopology.xml. 

Deployment topology file can be located in the path - <atgxxxdir>/Publishing/base/src/config/atg/epub/deploymentTopology.xml

As described earlier, the structure of the deployment topology contains the target sites, Publishing agents and source – destination repository mapping.

Please find below the reference for deployment topology file for a staging and production instance.

<? Xml version="1.0" encoding="UTF-8" standalone="no"?>
<!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>
<description> Production , full deployment </description>
<target-deploy-type> WORKFLOW </target-deploy-type>
<agent> <agent-name> PublishProdAgent </agent-name>
<principal-asset> REPOSITORY</principal-asset>
<transport> <transport-type> RMI </transport-type>
<rmi-uri> 
rmi://localhost:port1/atg/epub/AgentTransport</rmi-uri>
</transport>
</agent>
<repository-mapping><source- 
repository>/atg/commerce/catalog/ProductCatalog </source- 
repository>
<destination- 
repository>/atg/commerce/catalog/ProductCatalog_production 
</destination-repository>
</repository-mapping>
<repository-mapping><source-
repository>/atg/commerce/priceLists/PriceLists </source-
repository>
<destination-repository atg/commerce/priceLists/PriceLists 
_production </destination-repository>
</repository-mapping> </target>
<target> <target-name> Staging </target-name>
<description> Staging, full deployment </description>
<target-deploy-type> WORKFLOW </target-deploy-type>
<agent> <agent-name> Publish StagAgent </agent-name>
<principal-asset> REPOSITORY</principal-asset>
<transport> <transport-type> RMI </transport-type>
<rmi-uri> 
rmi://localhost:port2/atg/epub/AgentTransport</rmi-uri>
</transport>
</agent>
<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/priceLists/PriceLists </source-
repository>
<destination-repository atg/commerce/priceLists/PriceLists 
_staging </destination-repository>
</repository-mapping> </target>
</publishing-deployment-topology>

Once the file is ready go to the Deployment 
Administration page,click configuration and choose
the option click Import from XML.See Screen shot below


See also how to manually configure deployment in the CA Server.


import from xml option in bcc

Comments

Post a Comment

Popular posts from this blog

BCC site status inaccessible Agent Production in error state

-
Image
The Error Message showing in BCC T he error logs is showing the below message /atg/epub/DeploymentServer Failed to connect to agent 'Production'. This agent not allowed to be absent for  a deployment. The server will continue attempts to  intialize the connection. Set loggingDebug to true for  continued exception and stacktrace logging. Analysis This happens when the target/Production instance is down for some  reason or the RMI configuration which points to the target/Production instance may not be correct one. Fix If this is happening  due to target/Production instance down  then we can restart the target/Production Server,Other wise  correct the RMI configuration from the BCC agent configuration page and reinitialise. Verify the RMI Port in Configuration.properties file.Usually this file will be located in the path C:\ATG\ATG10.2\home\servers\ATGProduction\localconfig\atg\dynamo\Configuration.properties,make sure the
Read more

Weblogic Issues during EAR Deployment Exception in AppMerge flows progression

-
Unable to access the selected application Exception in AppMerge flows progression Bean already exists "weblogic.j2ee.descriptor.ModuleBeanImpl@..../Modules[weblogic.descriptor.internal.Descriptor.Beankey@....] This issue can happen in many scenarios, may be you need to check your deployment descriptors based on Application Servers used, this generally happens due to issue in XML files related to deployment. I got this issue when i mistakenly added the modules twice in the Manifest file, the module 'Store.Storefront' is added more than once in  'ATG-Required'  of my Manifest.MF file,due to this i am seeing the module 'storedocroot.war' is added twice in my application.xml which is located in the  path ATGProd.ear\META-INF\application.xml.Due to this i am not able to deploy my EAR file. I have removed the duplicate entry and deployed the application and everything working fine. ....... <module>         <web>             <web-uri>atg_
Read more

DUseSunHttpHandler=true weblogic.net.http.SOAPHttpsURLConnection Weblogic/Java HttpHandler issues

-
Verify the issue is happening due to the error throwing  from the weblogic class  SOAPHttpsURLConnection,then you need to inform the Application Server which handler implementation you need to use.  add the following option to JAVA_OPTIONS in   setDomainEnv.sh/setDomainEnv.cmd  on Unix/Windows.   -DUseSunHttpHandler=true.  eg:  set JAVA_PROPERTIES=%JAVA_PROPERTIES% %WLP_JAVA_PROPERTIES%  set JAVA_OPTIONS=%JAVA_OPTIONS% %JAVA_PROPERTIES% -  DUseSunHttpHandler=true -Dwlw.iterativeDev=%iterativeDevFlag% -  Dwlw.testConsole=%testConsoleFlag% -Dwlw.logErrorsToConsole=%  logErrorsToConsoleFlag%  This setting tells WebLogic to use the Sun's https Handler   implementation rather than the WebLogic one.  So after this,it will use the  class HttpsURLConnection from the  javax package.   See Also   SSL Handshake error   java.lang.RuntimePermission modifyThread
Read more