Copying marketing statistics from the production server

Typically, statistics regarding how customers are using your site are captured on the production server. A system administrator can transfer that data from the production server to the development or staging server for analysis by running a series of commands, whenever the information is required.

Attention: Instead of following the procedure in this topic, you can use the DownloadStatistics scheduled job to transfer your marketing and search rule statistical data from your production server to your staging server. For more information, see Scheduling the DownloadStatistics job to copy marketing and search statistics.

Procedure

From a command line, change to the following directory on the production server:
WC_installdir\bin
Run the ExportStats command:
```
ExportStats.bat -Ddatabase_type -Ndatabase_name -Udatabase_user_id 
  -Pdatabase_password -Foutput_file_name -Ttable_name
```
```
ExportStats.sh -Ddatabase_type -Ndatabase_name -Udatabase_user_id 
      -Pdatabase_password -Foutput_file_name -Ttable_name
```
Where:
database_type

The type of database you are using, either DB2 or Oracle.
The type of database you are using, DB400.
database_name
Enter the simple name of the database.
Identify the database using the following format: hostname:port:sid identifying the host name of the database server, the port number of the server, and the system ID.
database_user_id
The user ID of the database owner.
This ID is also known as the instance user profile.
database_password
The password for the database owner ID.
output_file_name
The path and name of the output file with an .xml extension (if no path is specified, the default is the current directory).

table_name
The name of the database table that you want to export. The table to export depends on your requirements from among the following choices:

CPGNSTATS for campaign statistics (WebSphere Commerce Accelerator)

EXPSTATS for experiment statistics (WebSphere Commerce Accelerator)

Deprecated featurePASTATS for Product Advisor statistics

Deprecated featurePCSTATS for Product Comparison statistics

Deprecated featurePESTATS for Product Explorer statistics

Deprecated featureSASTATS for Guided Sell statistics
DMELESTATS for Web activity and experiment statistics (Management Center)
DMEMSPOTSTATS for e-Marketing Spot statistics (Management Center)
DMEXPSTATS for experiment statistics (Management Center)
This creates an XML file.
Transfer the XML file to the development or staging server.
Place the XML file in the following directory on the development or staging server:
WC_installdir\bin
Run the ImportStats command by entering the following:
```
ImportStats.bat -Ddatabase_type -Ndatabase_name -Udatabase_user_id 
      -Pdatabase_password -Finput_file_name
```
```
ImportStats.sh -Ddatabase_type -Ndatabase_name -Udatabase_user_id 
      -Pdatabase_password -Finput_file_name
```
Where

database_type

The type of database you are using, either DB2 or Oracle.
The type of database you are using, DB400.
database_name
The name of your database. DB2 users enter the simple name of their database.
Identify the database using the following format: hostname:port:sid identifying the hostname of the database server, the port number of the server, and the system ID.

database_user_id
The user ID of the database owner.
This is also known as the instance user profile.
database_password
The password for the database owner ID.
input_file_name
The path and name of the output file that is created with the ExportStats utility in step 2 (if no path is specified, the default is the current directory).

Results

This deletes any statistical information in the development or staging server database, and imports the statistics.