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:
# @version $Id: //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 messagingSource=/atg/deployment/messaging/DeploymentMessagingSource serverNameService=/atg/dynamo/service/ServerName clusterNameService=/atg/dynamo/service/ClusterName transactionBatchSize=250 threadBatchSize=1000 maxThreads=10 maxFailureCount=0 loggingDebug=false loggingThreadDebug=false loggingItemDebug=false loggingPropertyDebug=false loggingFileDebug=false phaseCompletePollingInterval=15000 threadSpawnInterval=1000 repositoryMappings=
The following table describes key DeploymentManager
properties:
Property | Description |
---|---|
| The location of the repository used to store deployment status and management data. |
| The Nucleus component that sends the JMS messages used to indicate the status of each deployment phase. Default: |
| 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 might want to increase this value so that a deployment can continue even if errors are found. Default: |
| The frequency in milliseconds of Default: For local deployment, the To expedite large deployments, decrease polling frequency by increasing the value of these properties. |
| Specifies whether to delete from the deployment repository Default: |
| The maximum number of threads that can be spawned for each deployment. Increase the value as the number of assets in the system increases. The value of this property must be less than the number of connections specified in your datasource. For more information, see Configuring DAF Deployment for Performance. Default: |
| The number of items that each transaction can process. See Configuring DAF Deployment for Performance for more information. The Default: |
| 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 are created. For 5000 items 5 threads are created, and so on until the Default: |
| Specifies whether to perform distributed or local deployments. See Enabling Distributed Deployments. Default: |
Enabling Distributed Deployments
By default, deployment events are sent locally only to the server that initiated the deployment. In order to use distributed deployment, where deployment events are sent as JMS messages to configured listeners, set the useDistributedDeployment
property to true. If you enable distributed deployment but the number of assets to deploy is less than or equal to the number of assets assigned to each thread, deployment is local only, because only one thread is required. By default, threadBatchSize
is set to1000, so all deployments of 1000 assets or less are always local. This behavior can significantly improve performance for small deployments. The default setting of useDistributedDeployment
is false.
Configuring Error Logging and Debugging
The DeploymentManager
includes several properties that determine the amount and type of error and debugging information that is displayed in the Oracle Commerce Platform console, and saved to the debug.log
file in the <ATG11dir>\home\logs
directory:
Property | Logs this information: |
---|---|
| Component-level debugging Default: |
| Thread-level debugging Default: |
| Debugging for repository items Default: |
| Debugging at repository item property level Default: |
| Debugging for file assets Default: |
Enabling the 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, set these flags to true only during development and testing.
You can also use the DAF Deployment API to obtain status and error information as it is generated.