Additional Oracle ATG Web Commerce Configuration

Additional configuration is necessary to enable debug message logging for the Assembler on both the Production and Publishing servers. Also, 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 ATG deployments to a single thread. Use the workaround provided below to avoid this problem.

To enable debug message logging:

  1. In a UNIX shell or command prompt, change directories to <ATG10dir>/home/servers/ATGProduction/localconfig/atg/endeca/assembler.

  2. Add a file, named AssemblerTools.properties, in the assembler directory.

  3. Edit the AssemblerTools.properties file to contain the following:

    loggingDebug=true

  4. Save the AssemblerTools.properties file.

  5. Change directories to <ATG10dir>/home/servers/ATGPublishing/localconfig/atg/endeca/assembler

  6. Repeat steps 2 through 4 to create an AssemblerTools.properties file for the Publishing server.

To enable the ATGPublishing server to trigger the data loading process to run on the ATGProduction server:

  1. In a UNIX shell or command prompt, create the following directory:

    <ATG10dir>/home/servers/ATGPublishing/localconfig/atg/search

  2. Add a file, named SynchronizationInvoker.properties, in the search directory.

  3. Edit the SynchronizationInvoker.properties file to contain the following:

    host=production-server-host-name
    port=production-server-rmi-port

    Note: The default production-server-rmi-port is 8860.

  4. Save the SynchronizationInvoker.properties file.

(DB2 Only) To modify DeploymentManager properties:

  1. In a UNIX shell or command prompt, change directories to <ATG10dir>/home/servers/ATGPublishing/localconfig/atg.

  2. Create a deployment directory.

  3. Add a file, named DeploymentManager.properties, in the deployment directory.

  4. Edit the DeploymentManager.properties file to contain the following:

    maxThreads=1
    useDistributedDeployment=false

  5. Save the DeploymentManager.properties file.

Copyright © 1997, 2013 Oracle and/or its affiliates. All rights reserved. Legal Notices