The production server logs information about the following items for Oracle ATG Web Commerce:
Site visits
Order submissions
Segments
User profiles
The production server logs the following items for Oracle ATG Web Commerce Search:
Search queries
Document views
Search environment use
Configuring your production server involves two steps. First, enable logging on the server. To enable logging, create a <ATG10dir>/home/servers/
server_name
/localconfig/atg/dynamo/service/DWDataCollectionConfig.properties
file and set the following properties:
enabled=true
defaultRoot=log_file_directory
The log file directory can be any place in your system accessible to both the production and data loader servers. See Log Files.
Oracle ATG Web Commerce Search has an additional logging control for the NLP reports, the atg/search/routing/ReportDataControl
. By default, the enabled
property of this component is configured to point to DWDataCollectionConfig.enabled
, but it can be enabled and disabled separately if you are not interested in reporting on that data. The NLP reports include all Search-related reports except for Search Activity Summary, Search Activity Over Time, and Search Response Time Trends. See the ATG Search Administration Guide for detailed information on Search reports.
Next, configure the data sources for the data warehouse loader repository. To do this, create two properties files in your production server’s localconfig
directory:
/atg/dynamo/service/jdbc/DirectJTDataSource.properties
$class=atg.nucleus.JNDIReference
JNDIName=JDNI
name
for
production
datasource
/atg/dynamo/service/jdbc/DirectJTDataSource_production.properties
$class=atg.nucleus.JNDIReference
JNDIName=JDNI name for production datasource
If you are using Oracle ATG Web Commerce Search with Oracle ATG Web Commerce, add the following configuration properties to the file /atg/commerce/search/catalog/QueryRequest.properties
.
firingSearchEvents=true
saveRequest=true