(15886930) Indexing by SKU fails when using the MSSQL database.

Workaround: In order to write records to the CAS record stores, the document submitters import classes from the Endeca com.endeca.itl.record and com.endeca.itl.recordstore packages. These classes make use of the Apache CXF framework. Using the default CXF configuration results in a large number of informational logging messages. The volume of the messages can result in problems. In particular, environments that use MSSQL and index by SKU will have issues because the logging seizes up the MSSQL server and indexing fails. Therefore, you should reduce the number of logging messages by setting the logging level of the org.apache.cxf.interceptor.LoggingInInterceptor and org.apache.cxf.interceptor.LoggingOutInterceptor loggers to WARNING for all application servers. The way to set these logging levels differs depending on your application server. See the documentation for your application server for information.

(14344350) Indexing may fail on IBM WebSphere Application Server due to a class loader issue.

Workaround: Set the childFirstPrefixes property of the /atg/endeca/index/EndecaIndexClassLoaderService component as follows, and then restart the server:

childFirstPrefixes+=org/apache/ws

(13999034) Startup errors on staging server.
Starting up a staging server may result in a javax.naming.NameNotFoundException and other errors.

Workaround: Create an /atg/dynamo/service/jdbc/DirectJTDataSource_production.properties file in the staging server's localconfig directory, and set the JNDIName property to the name of the production server's datasource. For example, if the JNDIName for the production datasource is ATGProductionDS, the properties file should contain:

JNDIName=ATGProductionDS