ATG Oracle Web Commerce, Deployment and TroubleShooting Stuff

Configuring Content Administration (BCC) environment to deploy Single ConfigFileSystem across multiple Physical/Virtual machines (VM). To achive this, we should create a master ConfigFileSystem on one JVM/ATG instance on the VM and slave ConfigFileSystems on rest of the JVM's on the same VM. So only one JVM/ATG instance on a given machine/VM is responsible for file deployments. This configuration can significantly increase performance because deployment data, which can be very large, is sent to one agent rather than all agents. Also deployments won’t affect even if one of the non-essential agent went down during deployment. Note : A shared ConfigFileSystem is supported for switch mode deployments only. Steps to set up Shared ConfigFileSystem: 1. Designate one ATG instance on each machine/VM as the master instance and rest other ATG instances are considered as slave instances. 2. Configure a master ConfigFileSystem.properties file with below content. File: <ATG-Data-...

Symptoms : If there are dead lock issues in BCC while deploying large assets/feeds project either in Staging or Production agents . If it fails after multiple attempts with " java.sql.SQLException: ORA-00060: deadlock detected while waiting for resource " errors in logs, we can try tweaking below configurations to make it successful. (Note: This might solve the issue for temporarily , but you need to look at the error log for exact issue) Solution: 1. Increase the INITRANS  for the affected table (will get the table names from the bcc/pub application logs)   Use this SQL to check current  INITRANS  value of the table :  select ini_trans,max_trans from dba_tables where table_name='table_Name'; Increase the value of INITRANS to good number, this can be determined based on the site.   Also request DBA team to examine the AWR report to detected the high ITL waits on a number of tables. 2. Tweak the default values of the D...

BCC Navigation slowness while browsing unsited catalog Symptoms: After creating merchandising project and browsing unsited catalog assets, if you see slowness  then that could be the problem with large catalog data. Solution: 1.  To resolve this issue, update the below configur ations in DCS-UI module.  2. Go to build server/ATG installed server location <ATG-ROOT>/DCS-UI/config/atg/remote/content/browse/ContentBrowseHierarchy.xml  3. Open the file  ContentBrowseHierarchy.xml and find    <browse-item id="unsited"  section. 4. Update the value from  show-count="true"  to  show-count="false"  5.  After the change the lines will look as below (highlighted in bold)... <!-- The unsited catalog items node --> <browse-item id="unsited"                label-resource="node.unsitedItems.label"                 show...