Loading data using the Loader Package

This diagram illustrates the basic steps involved in the loading process.

  1. The loader utilities require the WebSphere Commerce .dtd file. If the .dtd file is available, then go to the next step. Otherwise, use the DTDGenerator utility to generate a .dtd file. The DTDGenerator uses a text file that contains the table names for which the description is required and the output .dtd file name. The result will be a .dtd file containing the description of the database tables.

  2. The WebSphere Commerce XML data file needs to be resolved for unique keys. This requires the ID Resolver utility, which uses the .dtd file, the output file name, and the generated WebSphere commerce XML to produce the output XML data file with resolved identifiers.

  3. The data from the resolved XML data file generated in the previous step is loaded into the WebSphere Commerce database using the Massloader utility. This utility uses the resolved XML file as the input and loads the data into the WebSphere commerce database.

Feedback