The deployment process is initiated by the /atg/deployment/DeploymentManager component, which is also responsible for sending JMS messages that signal the start of each subsequent deployment phase. The following code sample shows the properties file for the default DeploymentManager component:
//product/DAF/main/Deployment/config/atg/deployment/ DeploymentManager.properties $class=atg.deployment.DeploymentManager deploymentRepository=DeploymentRepository transactionManager=/atg/dynamo/transaction/TransactionManager lockManager=/atg/dynamo/service/ClientLockManager deploymentMessagingSource=messaging/DeploymentMessagingSource serverNameService=/atg/dynamo/service/ServerName transactionBatchSize=250 threadBatchSize=1000 maxThreads=10 maxFailureCount=0 loggingDebug=false loggingThreadDebug=false loggingItemDebug=false loggingPropertyDebug=false loggingFileDebug=false phaseCompletePollingInterval=15000 threadSpawnInterval=1000
Key properties in the DeploymentManager are as follows:
Property | Description | Default |
|---|---|---|
| Specifies the location of the repository used to store deployment status and management data. |
|
| Specifies the Nucleus component that sends the JMS messages used to indicate the status of each deployment phase. |
|
| The number of errors that are allowed before a deployment is declared a failure. By default, the deployment fails on the first error. In some cases, particularly during development or testing, you may want to increase this value so that a deployment can continue even if errors are found. | 0 |
| Specifies whether the | True |
| Specifies the maximum number of threads that can be spawned for each deployment. Increase the value as the number of assets in the system increases. See Configuring DAF Deployment for Performance for more information. | 10 |
| Specifies the number of items that can be processed for each transaction. See Configuring DAF Deployment for Performance for more information. The | 250 |
| Specifies the maximum number of items that can be assigned to each thread. By default this number is 1000, which means that for a deployment containing 2000 items, 2 threads will be created. For 5000 items 5 threads will be created, and so on until the | 1000 |
| Determines whether to perform distributed or local deployments. See Enabling Distributed Deployments. | False |
Enabling Distributed Deployments
By default, deployment events are sent locally and only to the server that initiated the deployment. If you want to use distributed deployment instead, so that deployment events are sent as JMS messages to any configured listener, you must set the useDistributedDeployment property to true. Also, if distributed deployment is enabled, but the number of assets to deploy is less than or equal to the number of assets assigned to each thread, the deployment is changed to be local, because only one thread needs to be spawned. By default, the threadBatchSize is 1000, so all deployments of 1000 assets or less are always local. This behavior can significantly improve performance times for smaller deployments. Note that the default setting of the useDistributedDeployment property is false.
Configuring Error Logging and Debugging
The DeploymentManager includes several properties you can set to configure the amount and type of error and debugging information that is displayed in the ATG console and saved to the debug.log file in the <ATG2007.3dir>\home\logs directory.
Property | Logs this information | Default |
|---|---|---|
| Component-level debugging | False |
| Thread-level debugging | False |
| Debugging for repository items | False |
| Debugging at repository item property level | False |
| Debugging for file assets | False |
Note that enabling the last three properties, loggingItemDebug, loggingPropertyDebug, and loggingFileDebug, can result in very large amounts of output, depending on the number of assets in your system. For performance reasons, it is not recommended that you keep these flags set permanently to true.
You can also use several pieces of the API to view status and error information generated as part of a deployment. See DAF Deployment API.
