In DB2 environments, you must modify the DeploymentManager component’s properties for the ATGPublishing server. Without this step, the full deployment you will perform later on will fail.
Note: DB2 deadlocks occur during deployments over multiple Content Administration threads. This problem is due to IBM’s locking strategy (see PMR #42831,756,000), which constrains ATG deployments to a single thread. Use the workaround provided below to avoid this problem.
To modify DeploymentManager properties:
In a UNIX shell, change directories to
<ATG10dir>/home/servers/ATGPublishing/localconfig/atgCreate a
deploymentdirectory.Add a file, named
DeploymentManager.properties, in thedeploymentdirectory.Edit the
DeploymentManager.propertiesfile to contain the following:maxThreads=1
useDistributedDeployment=falseSave the
DeploymentManager.propertiesfile.Continue with the section Starting the Publishing and Production Servers.
