One possible reason for search failure is an incorrectly configured data source. To examine your data source configuration, you can use the Dynamo Server Admin (see the ATG Installation and Configuration Guide for information on this tool) to view each Oracle ATG Web Commerce instance in which the DAF.Search module is running. Check the configuration of the /atg/search/service/SearchJTDataSource component.
If
SearchJTDataSourceis aGenericReference, find the value of itscomponentPathproperty by clicking View Service Configuration, and resolve that component.If
SearchJTDataSourceuses aDirectJTDataSource, find the JNDIName property of theDirectJTDataSource:/atg/dynamo/service/jdbc/JTDataSource.properties:
dataSource=/atg/dynamo/service/jdbc/DirectJTDataSource/atg/dynamo/service/jdbc/DirectJTDataSource.properties:
$class=atg.nucleus.JNDIReference
JNDIName=java:/ATG_DB_DSThen make sure the corresponding application server’s data source is configured properly. For example, on JBoss, you can find this is in
<JBdir>/server/server-name/deploy/atg-xxxx-ds.xml:
<local-tx-datasource> <!-- This value matches JNDIName in DirectJTDataSource --> <jndi-name>ATG_DB_DS</jndi-name> <!-- Make sure this URL points to the correct db+schema --> <connection-url>jdbc:type://localhost:1313</connection-url> <!-- The login and password --> <user-name>admin</user-name> <password>admin</password> </local-tx-datasource> $JBOSS_DIR/server/<server-name>/deploy/atg-xxxx-ds.xml <local-tx-datasource> <!-- This value matches JNDIName in DirectJTDataSource --> <jndi-name>ATG_DB_DS</jndi-name> <!-- Make sure this URL points to the correct db+schema --> <connection-url>jdbc:type://localhost:1313</connection-url> <!-- The login and password --> <user-name>admin</user-name> <password>admin</password> </local-tx-datasource>
