Browse Prior Art Database

A customizable, high performance table based data load tool Disclosure Number: IPCOM000209858D
Publication Date: 2011-Aug-17
Document File: 5 page(s) / 95K

Publishing Venue

The Prior Art Database


Disclosed is a table based data load tool enhanced with plug-in (or handler) framework support in order to provide web-based retail companies with a system for updating their content that is cost-effective, customizable, and has a high performance level.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 44% of the total text.

Page 01 of 5

A customizable, high performance table based data load tool

As companies move their retail business to the Internet to allow shoppers to buy their goods and services online, they need to constantly refresh their catalog content in the commerce database to maintain the website. For example, they need to daily or weekly add new products, update product prices, or include new promotions.

To refresh the content data, the business users can use the existing commerce business line of tools to manually update the content, but this is a lot of work if there are many changes. They usually use a data loading tool to automatically load the data. The commerce database tables are usually very complicated. Each customer has different requirements and different custom tables. The effort to develop a custom data load solution is one of the largest costs for commerce site development.

There are two existing data loading tools in WebSphere* Commerce to help the customers to load data:

1. Mass load tool. The limitations of the mass load tool are:

• The input data file is an Extensible Markup Language (XML) file which must be mapped to the database tables and columns one-to-one

• Creating the mass loadable input XML file is very difficult. The user must understand the details in the database schema, all foreign key relations, and unique indexes. The raw input data are mixed with the database schema related information in the input XML file.

• The tool is not customizable. If the input data cannot be easily mapped to the database tables and columns one-to- one, then the tool us unusable.

• The performance is slow, especially for a large input file.

2. Data load tool. There are two types of data load:

• Business object based data load. The existing business object based data load tool has some limitations:

- Data must be modeled using a business object which is a service data object (SDO) and the input data must be mapped to the fields in the business object

- It is customizable, but to write the custom data load mediators requires a lot of written code; the customization effort is high.

• Table based data load. The table based data load still has some limitations similar to mass load:

- The input comma separated value (CSV) file must be mapped to the database tables and columns one to one

- It is not customizable

To load a CSV file with the existing table based data load which is shipped in the


Page 02 of 5

WebSphere Commerce V7, the user must define the data mapping configuration XML file. For example, a user wishes to load an administrator user into commerce database with the following CSV file (the first line contains the column header information):

MemberType,MemberState,DistinguishedName,RegistrationType,ProfileType,ParentID, Sequence,Status,PolicyAccount,LogonID,Password
U,1,"uid=admin,o=root organization",A,B,-2001,1,1,-2,admin,3fdBFMFoiGNQ0zUStB865w==

It is loaded into four database tables: USERREG, MEMBER, USERS and MBRREL. The...