Administer > Manage WebSphere Commerce features > Marketing > Marketing services


Copy statistical data 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.


Procedure

  1. From a command line, change to the following directory on the production server: WC_INSTALL\bin

  2. 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 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.

    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 to export. The table to export depends on the requirements from among the following choices:

    • CPGNSTATS for campaign statistics (WebSphere Commerce Accelerator)

    • EXPSTATS for experiment statistics (WebSphere Commerce Accelerator)

    • Deprecated feature:PASTATS for Product Advisor statistics

    • Deprecated feature:PCSTATS for Product Comparison statistics

    • Deprecated feature:PESTATS for Product Explorer statistics

    • Deprecated feature:SASTATS 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.

  3. Transfer the XML file to the development or staging server.

  4. Place the XML file in the following directory on the development or staging server: WC_INSTALL\bin

  5. 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 the 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 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.


+

Search Tips   |   Advanced Search