Spark::red SRSD and JIRA will undergo scheduled maintenance Saturday 16-December-2017 1700-2300 UTC. SRSD + JIRA will be unavailable during this window.

For Production outages, please call the support lines 888.666.5582 or +44.870.820.0056

Child pages
  • ATG Content Administration (CA)
Skip to end of metadata
Go to start of metadata
  • If CA is not clustered, verify that ClientLockManager.useLockServer=false
  • Verify that /atg/deployment/DeploymentManager.maxThreads=20. Adjust up or down based on DAF deployment performance. Oracle services has code to dynamically optimize the number of deployment threads, based on the number of assets being deployed
  • On the agent-side, ensure that DCS.PublishingAgent is started instead of the standard PublishingAgent (this applies to both standard and custom catalogs)
  • Verify that repositories that CA manages don't have tags like "<load-items item-descriptor="x" load-all-items="true" quiet="true" />" in their definitions
  • Ensure that /atg/dynamo/service/ClusterName.useClusterTable=false and that /atg/dynamo/service/ClusterName.clusterName is unique across environments
  • If custom catalogs are used, start DCS.DynamicCustomCatalogs and DCS.DynamicCustomCatalogs.Versioned
  • Ensure that secondary caches are being invalidated following deployments. Price caches, pmdl caches, and droplet caches are examples of secondary caches. They have classes like atg.service.cache.Cache or atg.droplet.Cache
  • Verify that the maximum number of database connections in the connection pools is adequate based on the value of /atg/deployment/DeploymentManager.maxThreads
  • Check that all primary tables in the versioned schema have indexes on workspace_id and checkin_date per product documentation
  • Ensure that all custom tables in the versioned schema have foreign key constraints, unique constraints, and unique indexes removed per product documentation
  • Verify that the transaction timeout has been extended. The timeout should be around 1.5x the time it takes to perform a full deployment. A good starting point is 100,000 assets/hour using a DAF deployment
  • Ensure that unique constraints all have the "asset_version" column as part of them in the versioned schema. Documentation says to drop all unique constraints from the versioned schema, but that's a bad idea. Dropping unique constraints on the versioned schema but not the catalog schemas could lead to deployment failures. Unique constraints should be in place, though they should be composite - column + asset_version
  • Be sure to make one side of all shared table relationships read-only in CA. See product documentation
  • Be sure to thoroughly test the impact that deployments have on the system, especially while the customer-facing site is under heavy load
  • Make sure there is a promotion approval process in place so that business users don't drive large amounts of traffic to the site without technical administrators having fair warning. Technical administrators should always know when business users are driving large volumes of traffic to the site so they have time to prepare if necessary. This secondary approval also helps prevent errors in promotions rules. For instance, a business user could say "100% off order" when he or she meant to say "10% off order"
  • Be sure to have a process in place to validate the HTML of the banner ads. Since they're generally free-form HTML, they could contain any number issues that could impact performance, stability, or security. Any HTML that business users or 3rd parties enter on the site should be thoroughly validated by a technical administrator
  • Make sure there is an approvals process for mass emails so that business users don't drive large amounts of traffic to the site without technical administrators having fair warning. Technical administrators should always know when business users are driving large volumes of traffic to the site so they have time to prepare if necessary
  • Ensure that there is a process in place to detect unwanted cyclical references. For example, if you set a given category as its own parent, that could be bad depending on how the site is coded
  • No labels