Loading customer segment members

This sample demonstrates how to load customer segment member data with the Data Load utility. After you load the data, Management Center users can view, manage, and use the customer segment in the Marketing tool.

About this sample

You can load data for adding customer segment members to customer segments in CSV formatted input files. The sample CSV input file and data load configuration files for this sample are in the following directory:
  • AIXLinuxWC_installdir/samples/DataLoad/Member/CustomerSegment
  • WindowsWC_installdir\samples\DataLoad\Member\CustomerSegment
  • WebSphere Commerce DeveloperWCDE_installdir\samples\DataLoad\Member\CustomerSegment

Sample input and configuration files

The following table lists the input files that you use to load the sample data. The table also identifies the business object mediators and business object configuration files that the Data Load utility uses to load the sample data.

Input files for loading promotion folder and folder relationship data

Sample CSV input file Description
TestCustomerSegment.csv This sample file includes only a single column of email addresses. The file does not include any column or file header information. When you are loading a list of email addresses to create a customer segment, you do not need to include any header information.

The Data Load utility uses this sample input file to load the list of email addresses to create a customer segment in the Marketing tool. This sample also populates the customer segment with members.

The Data Load utility uses the following business object mediator to load the data in this input file into the MBRGRP database table.

Business object mediator

com.ibm.commerce.member.dataload.mediator.MemberGroupMemberMediator

The sample directory also includes the following Data Load utility configuration files:
wc-dataload.xml
The data load order configuration file, which identifies the order that the Data Load utility loads the sample CSV files. The load order file also identifies the appropriate business object configuration file to use to load each input file. For more information about load order configuration files, see Configuring the data load order.
wc-dataload-env.xml
The data load environment configuration file, which includes the environment variables for your WebSphere Commerce instance. These variables include the following information:
  • Business context variables, including the store identifier, catalog identifier, and the default language and currency for your store.
  • Database environment settings, including the database type, name, and schema.
wc-loader-customer-segment-email.xml
The business object configuration file that defines how customer segment member group data is loaded into the database. The file also defines the appropriate business object mediator to use to load the data.
These configuration files include values for a default WebSphere Commerce Developer environment that uses an Apache Derby database. If your environment settings are different, you must change the configured values in these files to match your environment.

Procedure

  1. Open a command-line utility and go to the appropriate directory:
    • AIXLinuxWC_installdir/bin
    • WindowsWC_installdir\bin
    • WebSphere Commerce DeveloperWCDE_installdir\bin
  2. Enter the following command to run the sample data load order file and load the information that included in this sample:
    • AIXLinux./dataload.sh ../samples/DataLoad/Member/CustomerSegment/wc-dataload.xml
    • Windowsdataload.bat ..\samples\DataLoad\Member\CustomerSegment\wc-dataload.xml
    • WebSphere Commerce Developerdataload ..\samples\DataLoad\Member\CustomerSegment\wc-dataload.xml
When the load process completes, a new customer segment is created. The customer segment name is the same as the input file name, TestCustomerSegment.

Verifying results

  • Verify that the customer segment data is loaded by reviewing the data load summary report. For more information about the location and contents of this summary report, see Verifying the results of the data load.
  • You can also verify that the sample data is loaded by running the following SQL statements against your WebSphere Commerce database:
    select * from MBRGRP;  
    select * from MBRGRPMBR;
    Ensure that the data within the sample input files exists within the appropriate database tables.
  • In Management Center, verify that you can view the customer segments exist in the Marketing tool.

Removing the sample data from the WebSphere Commerce database

To remove the sample data from your database, run the sample again with the utility in delete mode. Edit the wc-dataload.xml load order configuration file to change the value of the dataLoadMode attribute from "Replace" to "Delete" to run the Data Load utility in delete mode. When you run the utility in delete mode, the utility deletes the data in your database that matches the rows in your CSV file. You do not need to edit the value for Delete column in your input CSV file.

Alternatively, you can run the Cleanup.sql file for this data load sample. The Cleanup.sql file is located within the following directory:
  • AIXLinuxWC_installdir/samples/DataLoad/Member/CustomerSegment
  • WindowsWC_installdir\samples\DataLoad\Member\CustomerSegment
  • WebSphere Commerce DeveloperWCDE_installdir\samples\DataLoad\Member\CustomerSegment
From a command prompt, connect to the database with your user ID and password. Run the following command
Apache Derby
  • ij -f ..\samples\DataLoad\Member\CustomerSegment\Cleanup.sql
DB2
  • AIXLinuxdb2 -tvf ../samples/DataLoad/Member/CustomerSegment/Cleanup.sql
  • Windowsdb2 -tvf ..\samples\DataLoad\Member\CustomerSegment\Cleanup.sql
Oracle
  • AIXLinuxsqlplus user_name/password@ database_name@ ../samples/DataLoad/Member/CustomerSegment/Cleanup.sql
  • Windowssqlplus user_name/password@ database_name@ ..\samples\DataLoad\Member\CustomerSegment\Cleanup.sql
Verify that the data is removed from your database by running the following SQL statements:
select * from MBRGRP;  
select * from MBRGRPMBR;
The data that you loaded with this sample should no longer exist in your database.

In Management Center, verify that you can no longer view the customer segments in the Marketing tool.