Deprecated feature

Configuring the MassLoadCustomizer.properties file

Configure the MassLoadCustomizer.properties files if you want to change the massload utility behavior.

Feature Pack 6 or later The massload utility is deprecated for WebSphere Commerce Version 7 Feature Pack 6. The Data Load utility is the recommended command-line loading utility. If you are currently using the mass load utility, you are recommended to switch to the Data Load utility to load your CSV and XML input files into your target database. If your system contains scheduled and automated processes that use massload, it is recommended that you update these processes to use the Data Load utility. Other WebSphere Commerce utilities that use the massload utility, such as the acpload utility, continue to use the massload utility in WebSphere Commerce Version 7 Feature Pack 6. If you have business reasons to continue using the massload utility, you can continue to use this utility. For more information about the Data Load utility, see Overview of the Data Load utility. You can switch to the Data Load utility by using the TableObjectMediator to load your data when no business object mediator exists for the data that you are loading. For more about the TableObjectMediator formation, see Data Load utility table-based mediator and builder.

About this task

You can change the behavior in the following ways:

Set the massload utility to ignore elements in the input file.
Adjust how the massload utility manages queue events.
Add more timestamp and date masks.

All of these changes are optional.

Procedure

Open the following file in the text editor:
- WC_installdir/xml/loader/MassLoadCustomizer.properties
- WCDE_installdirxml\loader\MassLoadCustomizer.properties
Set the appropriate values for your database and operating system. To customize one of these items, remove the double-slash comment characters (//) that precede the command in the Loader customizer property file and modify the defaults.
1. Database-connection command
```
DBConnectCommand = connect to {0} user {1} using {2};
```
  Where:
  
  0
  
  Database name
  
  1
  
  Database user
  
  2
  
  user password
2. Database load-table command
```
DBLoadTableCommand = load from {0} of del modified by coldel{1} chardel{2} insert into {3} ({4});
```
  Where:
  
  0
  
  File name
  
  1
  
  Column delimiter
  
  2
  
  Character delimiter
  
  3
  
  Table name
  
  4
  
  Column names, which are separated by commas (,)
3. Database-import command
```
DBImportCommand = import from {0} of del modified by coldel{1} chardel{2}insert_update into {3} ({4});
```
  Where:
  
  0
  
  File name
  
  1
  
  Column delimiter
  
  2
  
  Character delimiter
  
  3
  
  Table name
  
  4
  
  Column names, which are separated by commas (,)
4. Database load command
```
DBLoadCommand = db2clpex DB2 -z {0} -astvf {1}
```
  Where:
  
  0
  
  Log file name
  
  1
  
  Command file name
```
DBLoadCommand = db2 -tvf {1} -z {0}
```
```
DBLoadCommand = sqlldr log={0} control={1} USERID={2}
```
  Where:
  
  0
  
  Log file name
  
  1
  
  Command file name
  
  2
  
  Database user name
5. Setting the Loader to ignore elements in the input file:
  If your input file contains elements that do not map to the target database, you can set the Loader to ignore those elements in the Loader customizer property file. Use IgnoreElements to specify elements to ignore, and separate these elements with a semicolon (;). To ignore the import, literals, and ProductRepository elements, for example:
```
IgnoreElements = import;literals;ProductRepository
```
Set the massload utility to ignore elements in the input file.
If your input file contains elements that do not map to the target database, set the massload utility to ignore those elements in the massload utility customizer property file. Use the IgnoreElements parameter to specify elements to ignore, and separate these elements with a semicolon (;). For example, to ignore the import, literals, and ProductRepository elements, set the IgnoreElements parameter as follows:
```
IgnoreElements = import;literals;ProductRepository
```
By default, the massload utility does not ignore any elements in the input file.
Adjust how the massload utility manages event queues.
The massload utility has two parameters that control how it manages event queues. The QueueHighCount parameter sets the number of elements in the queue that blocks the queue from accepting more events. The QueueLowCount parameter sets the number of elements in the queue that allows a blocked queue to accept more events.
Example:
```
QueueLowCount = 35
QueueHighCount = 90
```
The source of the events that are filling the queue is blocked when the number of elements in the queue reaches the higher limit, preventing more events from queuing up. The queue begins accepting events again when the number of elements in the queue falls below the lower limit.
Enabling the Loader to insert NULL into a column
```
EnableNULLCheck = true
```
For performance reasons, this feature is disabled by default. Use the NULLStringLiteral property to determine the string representation of a null value within your data. To set the Loader so that the string "-" is used to represent a null value, specify the following property and value in the Loader customizer property file:
```
NULLStringLiteral = -
```
By default, the value of this property is "NULL" (with no quotation marks).
Configure how the massload utility handles timestamp and date data.
Save your changes.