You must update the Publishing server configuration to ensure that running a full deployment will initiate a baseline index after the deployment is complete.
In DB2 environments, you must modify the DeploymentManager component’s properties for the Publishing server in order for deployments to succeed. 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 Oracle Commerce Platform deployments to a single thread. Use the workaround provided below to avoid this problem.
To enable the ATGPublishing server to trigger the data loading process to run on the ATGProduction server:
In a UNIX shell or command prompt, go to the following directory:
<ATG11dir>/home/servers/ATGPublishing/localconfig/atg/searchAdd a file, named
SynchronizationInvoker.properties, in thesearchdirectory.Edit the
SynchronizationInvoker.propertiesfile to contain the following:host=production-server-host-name
port=production-server-rmi-portNote: The default
production-server-rmi-portis 8860.Save and close the
SynchronizationInvoker.propertiesfile.
(DB2 Only) To modify DeploymentManager properties:
In a UNIX shell or command prompt, change directories to
<ATG11dir>/home/servers/ATGPublishing/localconfig/atg.Create a
deploymentdirectory.Add a file, named
DeploymentManager.properties, in thedeploymentdirectory.Edit the
DeploymentManager.propertiesfile to contain the following:maxThreads=1
useDistributedDeployment=falseSave and close the
DeploymentManager.propertiesfile.
